Function Dispo Chronological(): Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
mNo edit summary
mNo edit summary
Line 26: Line 26:


[[Category:2016 Time and Place changes]]
[[Category:2016 Time and Place changes]]
[[Category:CCMDB Data Integrity Checks]]
[[Category:Registry checks]]

Revision as of 11:38, 26 October 2018

Data Integrity Checks
Summary: Checks that the registry times are in a sensible chronological order.
Related: [[Arrive DtTm, Accept DtTm, Transfer Ready DtTm, Dispo DtTm ]]
Firmness: hard check
Timing: always
App: CCMDB.mdb
Coding: Function Dispo Chronological()
Uses L Problem table: not relevant for this app
Status: implemented
Implementation Date: 2016-05-25
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. Property "DICRelatedConcepts" (as page type) with input value "Arrive DtTm]], Accept DtTm, Transfer Ready DtTm, [[Dispo DtTm" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.
  • Categories:  
  • form:

The check will generate an error if:

No checks on Visit Admit DtTm field since taken direct from EPR, so it is what it is.

Transfer time rule

Template:Discussion Will want to reconcile Transfer time rule

Related checks