Query check prev pre-admit consistent: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
mNo edit summary
m removed
 
(4 intermediate revisions by 2 users not shown)
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 WRHA, [[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 =
| DIC_app = CCMDB.mdb
| DIC_app = CCMDB.accdb
| DIC_coding = function ''prev_pre_admit_consistent'',  query ''check prev pre-admit consistent''
| DIC_coding = function ''prev_pre_admit_consistent'',  query ''check_prev_pre-admit_consistent''
| DIC_status = implemented
| DIC_status = implemented
| DIC_implementation_date = 2016-05-01
| DIC_implementation_date = 2016-05-01

Latest revision as of 10:35, 2022 February 9

Data Integrity Checks
Summary: for inpatient transfers within the WRHA, 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.accdb
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


  • Categories:  
  • form:

approximate implementation date

Related articles

Related articles: