Function long LOS()

From CCMDB Wiki
Revision as of 16:51, 2019 March 20 by Ttenbergen (talk | contribs)
Jump to navigation Jump to search
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.mdb
Coding: Function long_LOS()
Uses L Problem table: not relevant for this app
Status: implemented
Implementation Date: 2014-01-01
Backlogged: true
  • Cargo


  • SMW
"CCMDB.mdb" is not in the list (SAP, not entered, Centralized data front end.accdb, DSM Labs Consistency check.accdb, CCMDB.accdb, TISS28.accdb) of allowed values for the "DICApp" property. 
  • Categories:  
  • form:

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

Log

  • 2019-03-20 - updated s_dispo table.meanLOS3STD with new values from Julie

Related articles

Related articles: