Edit Data Integrity Check: Link suspect negative transit time query

Are you logged on?

You do not have permission to edit this page, for the following reason:

The action you have requested is limited to users in the group: CCMDB_legit.

Summary (what is the check, one-liner):
links to related pages:
Firmness (is this a warning only (soft check) or will it stop sending (hard check) - applicable only in CCMDB.accdb app):	None/unknown hard check soft check
Timing (does this query run for all records or only complete ones):	None/unknown complete always
Name of the function or query this is implemented as:	''link_suspect_negative_transit_time'' query
Implementation date:
Implementation Status:
L_Problem (are false positive special cases addressed in table L_Problems - applicable only in CFE):	None/unknown Yes No
App:
Backlogged (is this query cleaned up to date or backlogged? Applicable only in CFE):

Free text:

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 [[Cat button|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 == 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. == log == * 2022-07-13 - updated to only show if diff is > 30min * 2022-04-05 - updated to use [[Admit DtTm]] * 2021-10-07 - changed overlap threshold to 1s because we were getting false positives since arrive dttm and dispo dttm come in at different precision/resolution from Cognos * 08:58, 2019 January 30 (CST): fixed problem with field name in query == Related articles == {{Related Articles}} [[Category:Data Processing]] [[Category:Multiple Encounter linking]] [[Category:Multiple encounter longitudinal consistency check]] [[Category:Registry checks]]

Explain your edit, if you think it needs explanation (e.g. "as discussed with ...", or "content moved to ...", or "duplicate content, see ..."):

This is a minor edit

Watch this page

Cancel