|
|
| Line 46: |
Line 46: |
|
| |
|
| == Integrity checks after import == | | == Integrity checks after import == |
| Please note here if any are needed.
| | {{Data Integrity Check List}} |
|
| |
|
| === D_IDs in CFE for which no DSM labs exist === | | === queries for which we have no page yet === |
| This could happen if
| | ==== Duplicate RequestNo ==== |
| * we have a bad MRN / PHIN
| | Should never happen due to how import works. I am not even sure what that would check for. |
| * we change/fix a D_ID after we request data
| |
| | |
| {{discuss | who = Julie | question =
| |
| * This could also be true where no labs were sent for, eg a patient who dies shortly after arrival. In the past we would have entered a "no labs" for these. Do we want to do something similar? It would have to be Pagasa that does it. Might be a lot of extra work. Need to review. (ex. wrong D_ID when exported but found it error and so fixed it before the data for import comes back). '''For now we do not have an entry like that. And it might not be worth it - what would Pagasa do to check that the no-labs are legit?''' }}
| |
| | |
| === D_IDs in DSM data for which no CFE record exists === | |
| Could happen if we change/fix a D_ID after requesting. Problem is, we can find if one doesn’t exist, but not if one was changed, but the one that was in the export is actually in present now. Not sure how we would catch that.
| |
| | |
| === Duplicate RequestNo === | |
| Should never happen due to how import works, but can check anyway. | |
|
| |
|
| == Known issues == | | == Known issues == |