Query check previous location vs service inconsistent: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
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]], [[Previous Service field]]
| DIC_related_concepts = [[Previous Location field]], [[Previous Service 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 ''previous_location_vs_service_inconsistent'', query ''check previous location vs service inconsistent''
| DIC_coding = function ''previous_location_vs_service_inconsistent'', query ''check previous location vs service inconsistent''

Revision as of 12:04, 25 September 2018

Data Integrity Checks
Summary: patients with Previous Location field in medicine must have Previous Service field medicine; ICU (except STB ACCU, STB CICU/ICCS) must have previous service "critical care".
Related: [[Previous Location field, Previous Service field]]
Firmness: hard check
Timing:
App: CCMDB.mdb
Coding: function previous_location_vs_service_inconsistent, query check previous location vs service inconsistent
Uses L Problem table: not relevant for this app
Status: implemented
Implementation Date: date change was rolled out / first applied
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]], [[Previous Service field" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.
  • Categories:  
  • form:

Related articles

Related articles: