Link suspect mismatch pre inpt should be ours incomplete query

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

• Cargo

• SMW

• Categories:  

• form:

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 to see the admission the patient
• 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
• 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

PTorres 13:59, 2022 March 24 (CDT)

You say "Sometimes the error continuous admission the second admission was admitted to ER" - that woldn't come up in this query, though, right? What are you actually telling someone who is doing vac relief with this? Ttenbergen 14:24, 2022 March 24 (CDT) After we talked I initially thought that this was essentially CCMDB Query check prev pre-admit consistent. But it clearly is something different and I still don't understand what it does. We'll need to discuss again. Ttenbergen 16:03, 2022 April 5 (CDT)

• SMW

• Cargo

• Categories

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

???