Function long LOS(): Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) mNo edit summary |
Ttenbergen (talk | contribs) m Text replacement - "| DIC_app" to "| DIC_timing = complete always | DIC_app" |
||
| Line 3: | Line 3: | ||
| DIC_related_concepts = [[LOS]] | | DIC_related_concepts = [[LOS]] | ||
| DIC_firmness = soft check | | DIC_firmness = soft check | ||
| DIC_timing = complete always | |||
| DIC_app = CCMDB.mdb | | DIC_app = CCMDB.mdb | ||
| DIC_coding = Function long_LOS() | | DIC_coding = Function long_LOS() | ||
Revision as of 11:57, 2018 September 25
| 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]] |
| Firmness: | soft check |
| Timing: | complete always |
| 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: |