| Data Integrity Checks
|
| Summary:
|
What is description
|
| Related:
|
|
| Firmness:
|
hard check
|
| Timing:
|
always
|
| App:
|
Centralized data front end.accdb
|
| Coding:
|
link_suspect_mismatch_pre_inpt_should_be_ours__incomplete query
|
| Uses L Problem table:
|
no
|
| Status:
|
implemented
|
| Implementation Date:
|
not entered
|
| Backlogged:
|
No
|
Generally follow steps in Processing errors in patient data to fix errors found.
Specific error fixing info for this query
- You have to click the hand shake for the late admission's record to see the story
- Likely causes for error, and corresponding corrections are:
- Most of the error on this query the discharged date of the first admission is after the second admission, if the case is this scenario, I just change the discharged date without looking the EPR
|
- Is this because the Dispo DtTm of the first admission being after the Admit DtTm of the second admission causes incorrect linking? That scenario should be caught by Link suspect negative transit time query - is it not? Or does this query simply run earlier and therefore catches it? If that's the case I should cause them to run in a different order, since the problem is easier to understand in the negative transit query. Ttenbergen 15:22, 2022 September 22 (CDT)
|
|
|
- Sometimes this query triggers as a side effect for errors that are actually link_suspect_mismatch_pre_inpt_should_be_ours__incomplete query, ie error continuous admission the second admission was admitted to ER
- I don't understand what you are saying here. You seem to say that this query triggers as a side effect of itself? I don't understand the ie either... could you give an example? Ttenbergen 15:22, 2022 September 22 (CDT)
|
Still shows records after errors are fixed
If after correcting the errors in this query it still shows entries, re-do Populate linking pairs and it will update the linking error.
Organ donor inconsistencies
We have Guideline for coding organ donation after death which might lead to some cross checks flagging an error for patient transfers. This situation is somewhat complex, so instead of changing queries to exclude these cases, just add them to L Problem table as usual after confirming that transfer info was indeed as entered.
log
- 2022-09-22 - tweaked the query and confirmed it worked by introducing an error to test; the query has not had any errors in it for some time so there had been concerns whether it still works.
Related articles