Link suspect negative transit time query: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
mNo edit summary
PTorres (talk | contribs)
No edit summary
Line 2: Line 2:
|DIC_summary=Used in [[Correcting suspect links]] to find records where an earlier record for a patient with that [[PHIN]] has a [[Dispo DtTm]] that is later than the next record's [[Arrive DtTm]].
|DIC_summary=Used in [[Correcting suspect links]] to find records where an earlier record for a patient with that [[PHIN]] has a [[Dispo DtTm]] that is later than the next record's [[Arrive DtTm]].
|DIC_related_concepts=PHIN; Arrive DtTm field; Dispo DtTm field
|DIC_related_concepts=PHIN; Arrive DtTm field; Dispo DtTm field
|DIC_firmness=hard check  
|DIC_firmness=hard check
|DIC_coding=''link_suspect_negative_transit_time'' query
|DIC_coding=''link_suspect_negative_transit_time'' query
|DIC_status=implemented
|DIC_status=implemented
|DIC_LProblem=Yes
|DIC_LProblem=no
|DIC_app=Centralized data front end.accdb
|DIC_app=Centralized data front end.accdb
|DIC_backlogged=No
}}
}}
Follow steps in [[Processing errors in patient data]] to fix errors found.
Follow steps in [[Processing errors in patient data]] to fix errors found.

Revision as of 15:17, 18 March 2022

Data Integrity Checks
Summary: Used in Correcting suspect links to find records where an earlier record for a patient with that PHIN has a Dispo DtTm that is later than the next record's Arrive DtTm.
Related: PHIN, Arrive DtTm field, Dispo DtTm field
Firmness: hard check
Timing: always
App: Centralized data front end.accdb
Coding: link_suspect_negative_transit_time query
Uses L Problem table: no
Status: implemented
Implementation Date: not entered
Backlogged: No
  • Cargo


  • SMW


  • Categories:  
  • form:

Follow steps in Processing errors in patient data to fix errors found.

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

  • 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: