Query check CCI TISS NrDays GT LOS: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) mNo edit summary |
Ttenbergen (talk | contribs) mNo edit summary |
||
| Line 1: | Line 1: | ||
{{Data Integrity Check | {{Data Integrity Check | ||
| DIC_summary = There | | DIC_summary = There are more [[Px_Date]]s than there are days between the first [[Service tmp entry]] and [[Dispo DtTm]] | ||
| DIC_related_concepts = CCI Picklist; | | DIC_related_concepts = CCI Picklist; Service tmp entry; Dispo DtTm | ||
| DIC_firmness = hard check | | DIC_firmness = hard check | ||
| DIC_timing = complete | | DIC_timing = complete | ||
Revision as of 11:18, 2021 January 21
| Data Integrity Checks | |
| Summary: | There are more Px_Dates than there are days between the first Service tmp entry and Dispo DtTm |
| Related: | CCI Picklist, Service tmp entry, Dispo DtTm |
| Firmness: | hard check |
| Timing: | complete |
| App: | CCMDB.accdb |
| Coding: | query check_CCI_TISS_NrDays_GT_LOS |
| Uses L Problem table: | not relevant for this app |
| Status: | ready to implement |
| Implementation Date: | |
| Backlogged: | true |
Will replace Query TISS Errors missing days; Query TISS Errors NrTISSDays NE LOS
Likely implementation: Count the datevalue(px_dates) for the Pat_ID. There have to be at least as many PX dates as there are days between Accept and Dispo. That would not look for continuity explicitly, but it would do so implicitly when combined with the date check that doesn’t allow dates outside of the admission range.
Log
- 2021-01-20 - check defined