Function Dispo Chronological()

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 (CCMDB.accdb, Centralized data front end.accdb, TISS28.accdb, SAP, DSM Labs Consistency check.accdb, not entered) of allowed values for the "DICApp" property. 

• Categories: 

• form:

The check will generate an error if:

• Arrive DtTm has to be before or equal to Accept DtTm
• Arrive DtTm has to be before or equal Transfer Ready DtTm
• Arrive DtTm has to be before Dispo DtTm
• Transfer Ready DtTm has to be before Dispo DtTm
• Dispo DtTm has to be before Now() / today

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

Transfer vs (accept vs arrive)

I just came across the error “Arrive_DtTm can't be greater than Transfer_Ready_DtTm.” in CCMDB. It made me wonder… I suppose that a TR could be before Arrive if it’s after Accept. First, Trish, do you think I am right about that? Second, if so, do we need to adjust this? How does this work with Julie’s reports now, and how would it work if changed.

• SMW

• Cargo

• Categories

Transfer time rule

Will want to reconcile Transfer time rule

• SMW

• Cargo

• Categories

Related checks

• Check Function Panelling admit transfer same