Function long 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 = [[LOS]]/Length of Stay should not be unlikely long based on historical [[LOS]] for a given ward ([[Service/Location field]]). | | DIC_summary = [[LOS]]/Length of Stay should not be unlikely long based on historical [[LOS]] for a given ward ([[Service/Location field]]). | ||
| DIC_related_concepts = LOS | | DIC_related_concepts = LOS; Arrive DtTm field; Dispo DtTm field | ||
| DIC_firmness = soft check | | DIC_firmness = soft check | ||
| DIC_timing = | | DIC_timing = | ||
Revision as of 16:01, 2018 October 26
| Data Integrity Checks | |
| Summary: | LOS/Length of Stay should not be unlikely long based on historical LOS for a given ward (Service/Location field). |
| Related: | LOS, Arrive DtTm field, Dispo DtTm field |
| Firmness: | soft check |
| Timing: | |
| App: | CCMDB.mdb |
| Coding: | Function long_LOS() |
| Uses L Problem table: | not relevant for this app |
| Status: | implemented |
| Implementation Date: | 2014-01-01 |
| Backlogged: | true |
This was probably implemented much earlier, but can't find reference before this.
The statistician provided mean LOS + 3 standard variations. This is stored in s_dispo table field meanLOS3STD.
The function compares the difference between Dispo DtTm field and Arrive DtTm field (not Accept DtTm field) to this meanLOS3STD and gives a warning (an error that can be OK'd past) if the current patient has been there longer.
Related articles
| Related articles: |