Query s tmp QAInf tmp no dx: 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 3: Line 3:
* program must be "CC"
* program must be "CC"
* the '''corresponding''' diagnosis must exist
* the '''corresponding''' diagnosis must exist
| DIC_related_concepts = [[QA Infection]], [[QA Infection CLI]], [[QA Infection VAP]]
| DIC_related_concepts = QA Infection; QA Infection CLI; QA Infection VAP
| DIC_firmness = hard check
| DIC_firmness = hard check
| DIC_timing =
| DIC_timing =

Revision as of 14:55, 26 October 2018

Data Integrity Checks
Summary: If "QAInf" entry is present in L_TmpV2 then
  • program must be "CC"
  • the corresponding diagnosis must exist
Related: QA Infection, QA Infection CLI, QA Infection VAP
Firmness: hard check
Timing:
App: CCMDB.mdb
Coding: Query s tmp QAInf dx no tmp
Uses L Problem table: not relevant for this app
Status: needs review
Implementation Date: 2009-12-29
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, this is the first mention in a change log so it was present before.

This query uses the following sub-queries:

  • s_tmp_QAInf__dx
  • s_tmp_QAInf__tmp

ICD10 dxs

  • what will be the ICD10 codes to use for this cross check?
  • SMW


  • Cargo


  • Categories

Related articles

Related articles: