Function long LOS(): Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) |
Ttenbergen (talk | contribs) |
||
| Line 18: | Line 18: | ||
== Log == | == Log == | ||
also see [[s_dispo.meanLOS3STD#Log]] for updates to that field that would affect this function's results | |||
* 2025-09-26 - query had never actually run properly but instead failed silently; updated so it runs | * 2025-09-26 - query had never actually run properly but instead failed silently; updated so it runs | ||
== Related articles == | == Related articles == | ||
Revision as of 14:05, 28 September 2025
| 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.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
also see s_dispo.meanLOS3STD#Log for updates to that field that would affect this function's results
- 2025-09-26 - query had never actually run properly but instead failed silently; updated so it runs
Related articles
| Related articles: |