Query s tmp QASeptic Dx no tmp ICD10: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
Created page with "{{Data Integrity Check | DIC_summary = If "QAInf" entry is present in L_TmpV2 then * program must be "CC" * the '''corresponding''' diagnosis must exist | DIC_related_conc..."
 
mNo edit summary
Line 1: Line 1:
{{Data Integrity Check
{{Data Integrity Check
| DIC_summary = If "QAInf" entry is present in [[L_TmpV2]] then
| DIC_summary = Has [[QA Septic Shock]] dx and no tmp entry
* program must be "CC"
| DIC_related_concepts = [[QA Septic Shock]]
* the '''corresponding''' diagnosis must exist
| DIC_related_concepts = [[QA Infection]], [[QA Infection CLI]], [[QA Infection VAP]]
| DIC_firmness = hard check
| DIC_firmness = hard check
| DIC_app = CCMDB.mdb
| DIC_app = CCMDB.mdb
Line 12: Line 10:


Approximate implementation date, this is the first mention in a change log so it was present before.
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 ==
== ICD10 dxs ==

Revision as of 10:45, 25 September 2018

Data Integrity Checks
Summary: Has QA Septic Shock dx and no tmp entry
Related: [[QA Septic Shock]]
Firmness: hard check
Timing: always
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.

ICD10 dxs

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


  • Cargo


  • Categories

Related articles

Related articles: