Check pre acute consistent

Revision as of 19:56, 15 October 2018 by Ttenbergen (talk | contribs)
Data Integrity Checks
Summary:
Related:
Firmness: hard check (not allowed) or soft check
Timing:
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 (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:


I found cases where the pre-living situation for direct admits are not consistent with previous location and/or dispo. I want the DC to be aware that the pre-living situation has relationship with the previous location or dispo specifically for PCH cases.

Example pre-living situation = assisted living; previous location = Winnipeg PCH

              pre-living situation = supportive home;   previous location = St Amant 

I rely on the combination of pre-living situation, previous location, postal code and dispo fields to identified new or already PCH resident prior to admission. Data collectors must understand that assisted living and supportive home are not PCH and must be entered as simply HOME as confirmed by Dr Roberts .


Pre acute living situation field Dispo_field Previous_Location_field

need analyze further.

  • SMW


  • Cargo


  • Categories