Check pre acute consistent: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
Created page with "Pre acute living situation field {{Discuss | who=Tina | question= need analyze further. }}"
 
mNo edit summary
Line 1: Line 1:
{{Data Integrity Check
| DIC_summary = what is the check (one-liner)
| DIC_related_concepts = list of related pages (probably the one it's on, but there might be others...)
| DIC_firmness = hard check (not allowed) or soft check (allowed, but give error; in CFE this means it has to go into the ... table, and cross checks have to consider that table)
| DIC_timing =
| DIC_app = CCMDB.mdb
| DIC_coding = query '''Check Renal IncompatibleDxs'''
| DIC_status = needs review
| DIC_implementation_date = 2009-09-30
}}
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]]
[[Pre acute living situation field]]
[[Dispo_field]]
[[Previous_Location_field]]


{{Discuss | who=Tina | question= need analyze further. }}
{{Discuss | who=Tina | question= need analyze further. }}

Revision as of 20:55, 15 October 2018

Data Integrity Checks
Summary: what is the check (one-liner)
Related: list of related pages (probably the one it's on, but there might be others...)
Firmness: hard check (not allowed) or soft check (allowed, but give error; in CFE this means it has to go into the ... table, and cross checks have to consider that table)
Timing:
App: CCMDB.mdb
Coding: query Check Renal IncompatibleDxs
Uses L Problem table: not relevant for this app
Status: needs review
Implementation Date: 2009-09-30
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