Query check CCI TISS NrDays GT LOS: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) m Ttenbergen moved page Query check CCI TISS each day to Query check CCI TISS NrDays GT LOS without leaving a redirect: need to break the check in two, one can run early |
Ttenbergen (talk | contribs) mNo edit summary |
||
Line 5: | Line 5: | ||
| DIC_timing = complete | | DIC_timing = complete | ||
| DIC_app = CCMDB.accdb | | DIC_app = CCMDB.accdb | ||
| DIC_coding = query '' | | DIC_coding = query ''check_CCI_TISS_NrDays_GT_LOS'' | ||
| DIC_status = ready to implement | | DIC_status = ready to implement | ||
| DIC_implementation_date = | | DIC_implementation_date = |
Revision as of 11:11, 2021 January 21
Data Integrity Checks | |
Summary: | There has to be a TISS entry in CCI Picklist with a Px_Date for each date between Accept DtTm and Dispo DtTm |
Related: | CCI Picklist, Accept DtTm, 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