Edit Data Integrity Check: Link suspect mismatch from ours incomplete 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_mismatch_from_ours__incomplete'' 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:

Follow steps in [[Processing errors in patient data]] to fix errors found. {{Organ donor inconsistencies}} == Log == * 2022-05-26 - changed the linking from previous to next to use <>s_dispoIDs and [s_dispo_early_location].[real_collection]<>[s_dispo_late_previous].[location_name]; without these, the a change we had made that turned “STB_SICU” into “STB_SICU (Legacy)” would result in false positives; also changed query to only compare up to 2018 == 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