Controlling Dx Type for ICD10 codes

From CCMDB Wiki
Jump to navigationJump to search
Data Integrity Checks
Summary: Controlling Dx Type for ICD10 codes
Related: ICD10 Diagnoses
Firmness: hard check
Timing: complete
App: CCMDB.mdb
Coding: how to find this in containing program, eg. SAS file, function name, query name...
Uses L Problem table: not entered
Status: needs review
Implementation Date: date change was rolled out / first applied


Poindexter.jpg Charlson Admit Como - this is part of that discussion
  • I have emailed Allan the table with all Dxs to set them as Como_allowed, Admit_allowed, Acquired_allowed. Will set up infrastructure to contain this once I have data. Ttenbergen 12:31, 2019 February 13 (CST)
    • Ignore until at least April.

Many of the items on the ICD10 Diagnosis List are not suitable as certain Dx Types.


We would like a way to detect when such inconsistencies happen.

Proposed Solution 1

  • Add three columns to the s_ICD10 table:
    • como_not_allowed
    • admit_not_allowed
    • acquired_not_allowed
  • populate the columns
    • default answers: NO in comorbid and YES in Admit, Acquired
  • put cross checks into CCMDB.mdb to prevent bad entries

why do this change outside the wiki?

The change will require editing every single record in the ICD10 Diagnosis List, so doing it on the wiki would be time-prohibitive. If we do it externally the new fields would be imported into the wiki, which would then again be the master repository for this.

  • We will use a tool like AutoWikiBrowser] or similar to get the changes integrated into pages.


It was decided that this is worth doing, and that the above is a reasonable way to do it.

Swiss Army Knife.svg not needed at go-live; Need to export the list and plan process that includes the extra items below. To export, see S_ICD10_table#Query_to_populate_s_ICD10_table_from_wiki.

If we do this, should we do more?

Related Articles

Related articles: