Query check ICD10 duplicates: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
Created page with "{{Data Integrity Check | DIC_summary = ICD10 Diagnoses can't be entered in duplicate. | DIC_related_concepts = ICD10 Diagnosis | DIC_firmness = hard check | DIC_timin..."
 
m moved here from Query Check Dx UniqueDx
Line 1: Line 1:
{{Data Integrity Check
{{Data Integrity Check
| DIC_summary = [[ICD10 Diagnoses]] can't be entered in duplicate.
| DIC_summary = [[ICD10 Diagnoses]] can't be entered in duplicate.
| DIC_related_concepts = [[ICD10 Diagnosis]]
| DIC_related_concepts = ICD10 Diagnosis
| DIC_firmness = hard check  
| DIC_firmness = hard check  
| DIC_timing = complete
| DIC_timing = complete
Line 9: Line 9:
| DIC_implementation_date = 2018-10-01
| DIC_implementation_date = 2018-10-01
}}
}}
* [[Comorbid Diagnosis]], [[Admit Diagnosis]]: there can be no duplicates
* [[Acquired_Diagnosis_/_Complication#repeating_complications]]: no repeat with exceptions
If these are changed we need to ensure the collection instructions are still consistent with the checks.
{{Discuss | who = All | question =
* Could there be duplication across bins? eg can something be a como and a complication? These might be special case scenarios, but if we put a hard check in place collectors may code garbage just so they can send and go home :-)
  currently we allow same dx in como and complication.  maybe keep this for now. --[[User:JMojica|JMojica]] 13:42, 2018 November 20 (CST)}}


== Related articles ==
== Related articles ==

Revision as of 17:39, 22 November 2018

Data Integrity Checks
Summary: ICD10 Diagnoses can't be entered in duplicate.
Related: ICD10 Diagnosis
Firmness: hard check
Timing: complete
App: CCMDB.mdb
Coding: query check ICD10 duplicates
Uses L Problem table: not relevant for this app
Status: implemented
Implementation Date: 2018-10-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. 
  • Categories:  
  • form:

If these are changed we need to ensure the collection instructions are still consistent with the checks.

  • Could there be duplication across bins? eg can something be a como and a complication? These might be special case scenarios, but if we put a hard check in place collectors may code garbage just so they can send and go home :-)
 currently we allow same dx in como and complication.  maybe keep this for now. --JMojica 13:42, 2018 November 20 (CST)
  • SMW


  • Cargo


  • Categories

Related articles

Related articles: