Function long LOS(): Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
 
(21 intermediate revisions by 2 users not shown)
Line 1: Line 1:
<onlyinclude>Function long LOS() checks that the [[LOS]]/Length of Stay for patients is not unlikely long based on historical [[LOS]] for a given ward.</onlyinclude>
{{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_related_concepts=LOS; Admit DtTm; Dispo DtTm field
|DIC_firmness=soft check
|DIC_timing=complete
|DIC_coding=Function long_LOS()
|DIC_implementation_date=2014-01-01
|DIC_status=needs review
|DIC_app=CCMDB.accdb
|DIC_backlogged=No
}}
== Earlier notes ==
This was probably implemented much earlier, but can't find reference before this.  


== {{CCMDB Data Integrity Checks|implemented}}==
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 ==
* 2022-04-21 - updated [[s_dispo table]].meanLOS3STD with data from Julie
* 2019-03-20 - updated [[s_dispo table]].meanLOS3STD with new values from Julie


The [[statistician]] provided mean LOS + 3 standard variations. This is stored in [[s_dispo table]] field meanLOS3STD.
== Related articles ==
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.
{{Related Articles}}


[[Category:2016 Time and Place changes]]
[[Category:2016 Time and Place changes]]
[[Category:Length of stay]]
[[Category:Length of stay]]
[[Category:CCMDB Data Integrity Checks]]
[[Category:Service/Location check]]
[[Category:Registry checks]]

Latest revision as of 13:19, 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
  • Cargo


  • SMW


  • Categories:  
  • form:

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

  • 2022-04-21 - updated s_dispo table.meanLOS3STD with data from Julie
  • 2019-03-20 - updated s_dispo table.meanLOS3STD with new values from Julie

Related articles

Related articles: