Function long LOS(): Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) m Text replacement - "Site/Location check" to "Service/Location check" |
Ttenbergen (talk | contribs) No edit summary |
||
| (15 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
{{Data Integrity Check | {{Data Integrity Check | ||
| DIC_summary = [[LOS]]/Length of Stay should not be unlikely long based on historical [[LOS]] for a given ward ([[Service/Location field]]). | |DIC_summary=[[LOS]]/Length of Stay should not be unlikely long based on historical [[LOS]] for a given ward ([[Service/Location field]]). | ||
| DIC_related_concepts = LOS; | |DIC_related_concepts=LOS; Admit DtTm; Dispo DtTm field | ||
| DIC_firmness = soft check | |DIC_firmness=soft check | ||
| DIC_timing = | |DIC_timing=complete | ||
|DIC_coding=Function long_LOS() | |||
| DIC_coding = Function long_LOS() | |DIC_implementation_date=2014-01-01 | ||
|DIC_status=needs review | |||
| DIC_implementation_date = 2014-01-01 | |DIC_app=CCMDB.accdb | ||
|DIC_backlogged=No | |||
}} | }} | ||
The function compares the [[LOS]] as per [[Function LOS()]] to [[s_dispo.meanLOS3STD]] and gives a warning (an error that can be OK'd past) if the current patient has been there longer. | |||
== [[Duplicate error messages]] == | |||
This is implemented as a soft check, so will come up repeatedly over the course of collection for a record. It should only trigger for less than 1% of records, but for those it will come up every time. If this becomes problematic for collectors, we should discuss it at Task. | |||
== 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 | |||
* long ago | |||
** This was probably implemented much earlier, but can't find reference before this. | |||
== Related articles == | == Related articles == | ||
{{Related Articles}} | {{Related Articles}} | ||
Latest revision as of 14:44, 7 October 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 |
The function compares the LOS as per Function LOS() to s_dispo.meanLOS3STD and gives a warning (an error that can be OK'd past) if the current patient has been there longer.
Duplicate error messages
This is implemented as a soft check, so will come up repeatedly over the course of collection for a record. It should only trigger for less than 1% of records, but for those it will come up every time. If this becomes problematic for collectors, we should discuss it at Task.
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
- long ago
- This was probably implemented much earlier, but can't find reference before this.