Function long LOS()

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:	needs review
Implementation Date:	2014-01-01
Backlogged:	true

• Cargo

• SMW

• Categories: 

• form:

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

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.

• SMW

• Cargo

• Categories

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