Link suspect mismatch from ours incomplete query: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) mNo edit summary |
Ttenbergen (talk | contribs) mNo edit summary |
||
Line 3: | Line 3: | ||
|DIC_related_concepts=PHIN field; Previous Location field | |DIC_related_concepts=PHIN field; Previous Location field | ||
|DIC_firmness=hard check | |DIC_firmness=hard check | ||
|DIC_coding= | |DIC_coding=''Link_suspect_mismatch_from_ours__incomplete'' query | ||
|DIC_status=implemented | |DIC_status=implemented | ||
|DIC_LProblem=no | |DIC_LProblem=no |
Revision as of 13:51, 2022 May 26
Data Integrity Checks | |
Summary: | Used in Correcting suspect links to find records where a later record with that PHIN has a Previous Location entry corresponding to one of our sites as per the s_dispo table.real_collection table, but an earlier corresponding entry doesn't exist for that location. |
Related: | PHIN field, Previous Location field |
Firmness: | hard check |
Timing: | always |
App: | Centralized data front end.accdb |
Coding: | Link_suspect_mismatch_from_ours__incomplete query |
Uses L Problem table: | no |
Status: | implemented |
Implementation Date: | not entered |
Backlogged: | No |
Follow steps in Processing errors in patient data to fix errors found.
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
Related articles
Related articles: |