Function long LOS(): Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) mNo edit summary |
Ttenbergen (talk | contribs) |
||
| Line 10: | Line 10: | ||
|DIC_backlogged=No | |DIC_backlogged=No | ||
}} | }} | ||
== Earlier notes == | == Earlier notes == | ||
This was probably implemented much earlier, but can't find reference before this. | This was probably implemented much earlier, but can't find reference before this. | ||
Revision as of 14:18, 2022 April 21
| 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, Admit DtTm, Dispo DtTm field |
| Firmness: | soft check |
| Timing: | complete |
| App: | CCMDB.accdb |
| Coding: | Function long_LOS() |
| Uses L Problem table: | not relevant for this app |
| Status: | needs review |
| Implementation Date: | 2014-01-01 |
| Backlogged: | No |
Earlier notes
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 LOS as per Function LOS() 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: |