Link suspect negative transit time query: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
Ttenbergen (talk | contribs) mNo edit summary |
||
| (One intermediate revision by the same user not shown) | |||
| 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= | |DIC_coding=''link_suspect_negative_transit_time'' query | ||
|DIC_status=implemented | |DIC_status=implemented | ||
|DIC_LProblem=Yes | |DIC_LProblem=Yes | ||
| Line 14: | Line 14: | ||
== log == | == 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 | * 08:58, 2019 January 30 (CST): fixed problem with field name in query | ||
Revision as of 14:05, 2021 October 7
| 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: | Yes |
| Status: | implemented |
| Implementation Date: | not entered |
| Backlogged: | true |
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