Diagnostic Codes Development

From OpenEMR Project Wiki
Revision as of 23:26, 3 December 2011 by Bradymiller (talk | contribs)

Overview

OpenEMR currently supports ICD9 diagnostic codes by default (although the codes need to be imported via phpmyadmin). It is also important to support ICD10 and SNOMED as an option; this wiki page will track the development of this. This was started after active discussion in the icd10 sourceforge forum thread.

The vital pieces here are the 'codes' and 'code_type' sql tables. It seems a lot of the codebase relies on hard-coded 'ct_id' elements in the 'codes' table to identify the code set. However, to get things to work smoothly, one option is to consider refactoring the code to instead use join in the mysql queries in order to instead use the 'ct_key' elements in the 'code_type' table to identify the code set.

ICD9

Already integrated and working on a default OpenEMR installation(although the codes need to be imported via phpmyadmin).
  • For ease of use, could consider mechanism that has these codes installed by default, but that needs to be turned "on" to use.
  • Create a mechanism to search for ICD9 codes by category.

ICD10

Article on transition from ICD9 to ICD10 in the US: Guest Article: Actionable advice on how to make tangible progress in ICD-9 to ICD-10 migration
Appears that some users have got this working.
  • For standardization, propose following:
  • Create an entry in code_types table(with id of 100+). See Code Types wiki page for details.
  • Support this in the codebase

SNOMED

Can currently import the SNOMED datasets into the OpenEMR databasae, however it is currently not integrated with the OpenEMR codebase.
  • For standardization, propose following:
  • Create an entry in code_types table(with id of 100+). See Code Types wiki page for details.
  • Support this in the codebase

DSMIV

Appears that some users are working on this
  • For standardization, propose following:
  • Create an entry in code_types table(with id of 100+). See Code Types wiki page for details.
  • Support this in the codebase