Query check prev pre-admit consistent: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
← Older editNewer edit →
m Text replacement - "| DIC_app" to "| DIC_timing = complete always | DIC_app"
m Text replacement - "DIC_timing = complete always" to "DIC_timing ="
Line 3: Line 3:
| 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 = complete always
| DIC_timing =
| DIC_app = CCMDB.mdb
| DIC_app = CCMDB.mdb
| 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''

Revision as of 12:04, 25 September 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. Property "DICRelatedConcepts" (as page type) with input value "Previous Location field]], [[Pre-admit Inpatient Institution field" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.
  • Categories:  
  • form:

approximate implementation date

Related articles

Related articles:
Retrieved from "https://ccmdb.kuality.ca/index.php?title=Query_check_prev_pre-admit_consistent&oldid=120086"