Procedure when there are differences between L Log and L PHI: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
Ttenbergen (talk | contribs) |
||
| (19 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
[["Pulling" Centralized data.mdb]] should result in consistent data sets being copied, but sometimes differences appear between L_PHI and L_Log. Usually this happens when something goes wrong during [[sending]] or during [[PHI copy automation]] or when a patient is deleted in one but not the other table. | [["Pulling" Centralized data.mdb]] should result in consistent data sets being copied, but sometimes differences appear between L_PHI and L_Log. Usually this happens when something goes wrong during [[sending]] or during [[PHI copy automation]] or when a patient is deleted in one but not the other table. | ||
You would usually find out about this when you | You would usually find out about this when you click the [["Re-connect Data" button]] in [[CFE]] and get an error that the number of records in L_Log and L_PHI is not the same. | ||
== More records in L_Log than in L_PHI == | |||
In that case, 1_In_L_Log_but_NOT_in_L_PHI will show you which record. | |||
* inform the collector whose [[Laptop identifier|whose laptop]] caused the error to [[Re-sending data|re-send data]] | |||
* set the relevant records from [[RecordStatus]] "sent" to "incomplete" as needed | |||
* | |||
* | * to ask them to send now: | ||
Your send did not go through correctly today, please reset the "sent" records to "complete" and then re-send. I have pushed the data and it is ready for you to re-send now. Please let me know when done so I can pull again to make sure that the error is fixed. | |||
or | |||
* | * to ask them to send when ready: | ||
Your send did not go through correctly today, please reset the "sent" records to "complete" and then re-send. I don't need you to re-send right now, just '''don't delete your sent records''' and send at your usual time. | |||
If this does '''not''' fix it, then: * | |||
* check [[X:\]]CCMDB/PHI/PHI_CSV. You want to make sure there is no CSV file sitting in this folder that was not uploaded to PHI.mdb | |||
* this could mean a problem with [[PHI copy automation]] | |||
* | == More records in L_PHI than in L_Log == | ||
In that case, query 1_In_L_Phi_but_NOT_in_L_Log triggers. | |||
*If file was a test, or error, you can delete it from L_Log and/or L_PHI, whichever still has part of the record. | * inform the collector [[Laptop identifier|whose laptop]] caused the error to [[Re-sending data|re-send data]] (see email snippet above) | ||
{{ex| Today Pam sent with that problem and her error message say "Invalid SQL statement expected Delete,Insert,Procedure,Select or Update" message. Also I need to change in the master CFE the Record Status Complete to Incomplete so collector can send no problem.}} | |||
== Test records == | |||
* If file was a test, or error, you can delete it from L_Log and/or L_PHI, whichever still has part of the record. Usually you would have heard from Tina or whoever is doing the testing in that case. | |||
== Related articles == | == Related articles == | ||
| Line 31: | Line 34: | ||
[[Category:Centralized data push pull]] | [[Category:Centralized data push pull]] | ||
[[Category:Data Processing]] | [[Category:Data Processing]] | ||
[[Category:Re-sending]] | |||
Latest revision as of 15:51, 2022 April 5
"Pulling" Centralized data.mdb should result in consistent data sets being copied, but sometimes differences appear between L_PHI and L_Log. Usually this happens when something goes wrong during sending or during PHI copy automation or when a patient is deleted in one but not the other table.
You would usually find out about this when you click the "Re-connect Data" button in CFE and get an error that the number of records in L_Log and L_PHI is not the same.
More records in L_Log than in L_PHI
In that case, 1_In_L_Log_but_NOT_in_L_PHI will show you which record.
- inform the collector whose whose laptop caused the error to re-send data
- set the relevant records from RecordStatus "sent" to "incomplete" as needed
- to ask them to send now:
Your send did not go through correctly today, please reset the "sent" records to "complete" and then re-send. I have pushed the data and it is ready for you to re-send now. Please let me know when done so I can pull again to make sure that the error is fixed.
or
- to ask them to send when ready:
Your send did not go through correctly today, please reset the "sent" records to "complete" and then re-send. I don't need you to re-send right now, just don't delete your sent records and send at your usual time.
If this does not fix it, then: *
- check X:\CCMDB/PHI/PHI_CSV. You want to make sure there is no CSV file sitting in this folder that was not uploaded to PHI.mdb
- this could mean a problem with PHI copy automation
More records in L_PHI than in L_Log
In that case, query 1_In_L_Phi_but_NOT_in_L_Log triggers.
- inform the collector whose laptop caused the error to re-send data (see email snippet above)
| Example: |
Today Pam sent with that problem and her error message say "Invalid SQL statement expected Delete,Insert,Procedure,Select or Update" message. Also I need to change in the master CFE the Record Status Complete to Incomplete so collector can send no problem. |
Test records
- If file was a test, or error, you can delete it from L_Log and/or L_PHI, whichever still has part of the record. Usually you would have heard from Tina or whoever is doing the testing in that case.
Related articles
| Related articles: |