Check pre acute consistent

Data Integrity Checks
Summary:	consistency of Pre acute living situation field, Dispo, Postal Code and Previous Location
Related:	[[Pre acute living situation field, Dispo, Postal Code), Previous_Location_field]]
Firmness:	soft check
Timing:	complete
App:	CCMDB.mdb
Coding:	query check pre acute consistent
Uses L Problem table:	not relevant for this app
Status:	needs review
Implementation Date:
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. Property "DICRelatedConcepts" (as page type) with input value "Pre acute living situation field]], Dispo, Postal Code), [[Previous_Location_field" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.

• Categories: 

• form:

The collector will receive an escapable warning if:

need analyze further.

• SMW

• Cargo

• Categories

Background

Julie found cases where the pre acute living situation for direct admits are not consistent with Previous Location and/or Dispo. We want the DC to be aware that the pre acute living situation has a relationship with the Previous Location or Dispospecifically for PCH cases.

Examples:

• pre acute living situation = assisted living; Previous Location = Winnipeg PCH
• pre acute living situation = supportive home; Previous Location = St Amant

I rely on the combination of pre acute living situation, Previous Location, Postal Code) and Dispo fields to identified new or already PCH residents prior to admission. Data collectors must understand that Assisted Living and Supportive Housing are not PCH and must be entered as simply HOME as confirmed by Dr Roberts .