Query check cooling vs arrest: 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 = [[Cardiac arrest]], [[Whole body cooling]]
| DIC_related_concepts = [[Cardiac arrest]], [[Whole body cooling]]
| DIC_firmness = hard check
| DIC_firmness = hard check
| DIC_timing = complete always
| DIC_timing =
| DIC_app = CCMDB.mdb
| DIC_app = CCMDB.mdb
| DIC_coding =   
| DIC_coding =   

Revision as of 11:56, 25 September 2018

Data Integrity Checks
Summary: Whole body cooling can only be used if there is a Cardiac arrest dx
Related: [[Cardiac arrest, Whole body cooling]]
Firmness: hard check
Timing:
App: CCMDB.mdb
Coding:
Uses L Problem table: not relevant for this app
Status: ready to implement
Implementation Date:
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 "Cardiac arrest]], [[Whole body cooling" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.
  • Categories:  
  • form:
Retrieved from "https://ccmdb.kuality.ca/index.php?title=Query_check_cooling_vs_arrest&oldid=120027"