Query check prev pre-admit consistent: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
m Text replacement - "DIC_timing = complete always" to "DIC_timing ="
mNo edit summary
Line 1: Line 1:
{{Data Integrity Check
{{Data Integrity Check
| DIC_summary = for inpatient transfers within the region, [[Previous Location field]] and [[Pre-admit Inpatient Institution field]] should be same.
| DIC_summary = for inpatient transfers within the region, [[Previous Location field]] and [[Pre-admit Inpatient Institution field]] should be same.
| DIC_related_concepts = [[Previous Location field]], [[Pre-admit Inpatient Institution field]]
| DIC_related_concepts = Previous Location field; Pre-admit Inpatient Institution field
| DIC_firmness = hard check
| DIC_firmness = hard check
| DIC_timing =
| DIC_timing =

Revision as of 20:58, 26 October 2018

Data Integrity Checks
Summary: for inpatient transfers within the region, Previous Location field and Pre-admit Inpatient Institution field should be same.
Related: Previous Location field, Pre-admit Inpatient Institution field
Firmness: hard check
Timing:
App: CCMDB.mdb
Coding: function prev_pre_admit_consistent, query check prev pre-admit consistent
Uses L Problem table: not relevant for this app
Status: implemented
Implementation Date: 2016-05-01
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:

approximate implementation date

Related articles

Related articles: