Function long LOS(): Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) m Text replacement - "CCMDB.mdb" to "CCMDB.accdb" |
Ttenbergen (talk | contribs) m Text replacement - "Site/Location check" to "Service/Location check" |
||
| Line 24: | Line 24: | ||
[[Category:2016 Time and Place changes]] | [[Category:2016 Time and Place changes]] | ||
[[Category:Length of stay]] | [[Category:Length of stay]] | ||
[[Category: | [[Category:Service/Location check]] | ||
[[Category:Registry checks]] | [[Category:Registry checks]] | ||
Revision as of 12:00, 2020 March 2
| 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.accdb |
| 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.
Log
- 2019-03-20 - updated s_dispo table.meanLOS3STD with new values from Julie
Related articles
| Related articles: |