Function long LOS(): Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) mNo edit summary |
Ttenbergen (talk | contribs) m Text replacement - "CCMDB.mdb" to "CCMDB.accdb" |
||
| Line 4: | Line 4: | ||
| DIC_firmness = soft check | | DIC_firmness = soft check | ||
| DIC_timing = | | DIC_timing = | ||
| DIC_app = CCMDB. | | DIC_app = CCMDB.accdb | ||
| DIC_coding = Function long_LOS() | | DIC_coding = Function long_LOS() | ||
| DIC_status = implemented | | DIC_status = implemented | ||
Revision as of 10:43, 2019 September 22
| 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: |