Link suspect negative transit time query

From CCMDB Wiki
Revision as of 13:24, 24 March 2022 by Ttenbergen (talk | contribs)
Jump to navigation Jump to search
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:

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 the 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)
  • 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.

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

Related articles: