Function long LOS(): Difference between revisions

(9 intermediate revisions by 2 users not shown)

Line 1:

{{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; ~~Arrive~~ DtTm ~~field~~; Dispo DtTm field

|DIC_related_concepts=LOS; Admit DtTm; Dispo DtTm field

|DIC_firmness=soft check

|DIC_timing=complete

Line 10:

|DIC_backlogged=No

}}

~~== Needs review after [[Change from Service Location to Service, Boarding Loc and Transfer Ready DtTm tmp entry]] ==~~

~~{{Discuss | who = Julie |~~

[[Change from Service Location to Service, Boarding Loc and Transfer Ready DtTm tmp entry]] changed [[Service/Location]] to aggregate values for the whole stay in a program. The values used in [[s_dispo table]] for the longest likely LOS were filled with previous entries from the same program, but should likely be longer now, since an aggregate stay would on average be longer. Once we have some data with the new aggregate model we should update these values.

** I will re-run using the first service dttm and dispo dttm. --[[User:JMojica|JMojica]] 15:38, 2022 January 19 (CST) }}

~~== Earlier notes ==~~

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.

~~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~~.

== [[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.

~~The function compares the difference between [[Dispo DtTm field]] and [[Arrive 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~~

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 ==

@@ Line 1: / Line 1: @@
 {{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; Arrive DtTm field; Dispo DtTm field
+|DIC_related_concepts=LOS; Admit DtTm; Dispo DtTm field
 |DIC_firmness=soft check
 |DIC_timing=complete
@@ Line 10: / Line 10: @@
 |DIC_backlogged=No
 }}
-== Needs review after [[Change from Service Location to Service, Boarding Loc and Transfer Ready DtTm tmp entry]] ==
-{{Discuss | who = Julie |
-[[Change from Service Location to Service, Boarding Loc and Transfer Ready DtTm tmp entry]] changed [[Service/Location]] to aggregate values for the whole stay in a program. The values used in [[s_dispo table]] for the longest likely LOS were filled with previous entries from the same program, but should likely be longer now, since an aggregate stay would on average be longer. Once we have some data with the new aggregate model we should update these values.
-** I will re-run using the first service dttm and dispo dttm. --[[User:JMojica|JMojica]] 15:38, 2022 January 19 (CST) }}
-== Earlier notes ==
+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.
-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.
+== [[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.
-The function compares the difference between [[Dispo DtTm field]] and [[Arrive 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
+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}}