Personal tools

Diagnostic Codes Development

From OpenEMR Project Wiki

Jump to: navigation, search

Contents

Overview

OpenEMR 4.1.0 supports ICD9 diagnostic codes by default (although the codes need to be imported via phpmyadmin).

OpenEMR 4.1.1 (planned release by September 2012) is much more flexible in diagnostic code and billing code support. See the Code Types wiki page for descriptions and instructions on how to use these advanced features that include easy importing and use of ICD9/ICD10/SNOMED codes along with a modular mechanism to add support for more codesets in the future (such as DSMIV and translated versions of ICD10/SNOMED etc.).

For historical purposes, leaving this page here (and to track the TODOs of this project). This project was started after active discussion in the icd10 sourceforge forum thread.

ICD9

  • In OpenEMR 4.1.0, already integrated and working on a default OpenEMR installation(although the codes need to be imported via phpmyadmin).
  • In OpenEMR 4.1.1, much easier to import codes, which is described in the Code Types wiki page.
  • See the TODOs section for work that is still ongoing.

ICD10

  • In OpenEMR 4.1.1, easy to import codes and they are fully integrated, which is described in the Code Types wiki page.
  • See the TODOs section for work that is still ongoing.
  • Rest of content in below ICD10 section is only being kept for historical purposes.
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 in OpenEMR 4.1.0.
  • active (will allow placing multiple code sets without them being used unless chosen)
  • external (0 for using the codes tables to hold codeset and then 1 or greater to use an external table(s) mechanism)
  • label (for displaying the code set name"
  • Modularize functions and place these functions in the custom/code_types.inc.php script.
  • Plan to import codes via the UI mechanism (like SNOMED and RXNORM)
  • The latest raw data file packages can be downloaded from
  • See the following forum threads for ongoing progress on this project:

SNOMED

  • In OpenEMR 4.1.0, easy to import codes, but they were not integrated.
  • In OpenEMR 4.1.1, easy to import codes and they are fully integrated, which is described in the Code Types wiki page.
  • In OpenEMR 4.1.2, also added ability to import the US Extension SNOMED codes and added the ability to import the Spanish translation SNOMED set.
  • See the TODOs section for work that is still ongoing.
  • Rest of content in below SNOMED section is only being kept for historical purposes.
  • Create an entry in code_types table(with id of 100+). See Code Types wiki page for details.
  • Support this in the codebase

DSMIV

  • In OpenEMR 4.1.0 and 4.1.1, no standard importing mechanism set up yet (once imported, they would be fully integrated, though in OpenEMR 4.1.1 as described in the Code Types wiki page).
  • See the TODOs section for work that is still ongoing.
  • Create an entry in code_types table(with id of 100+). See Code Types wiki page for details.
  • Support this in the codebase
  • Importing of codes
  • Use same mechanism as the ICD9/ICD10/SNOMED (and soon to be ICD9)
  • Need to find a standard offering of the codes (such as the CMS or WHO for ICD10), which can then use to import.
  • To distribute DSMIV codes, sounds like need to possibly get permission (which we have been told they will give). See this thread for details:

TODO

The TODO list:
  1. The fee sheet only shows the code (and not the code type) when selecting a justification code. Will also show the code type (ie. ICD9:258.12 rather than 258.12). (COMPLETED 6/19/12)
  2. The justify sql column in the billing table will also include the code types of the codes (ie. ICD9:258.12 rather than 258.12) (COMPLETED 6/19/12)
  3. The ar_activity table will have a code_type column since it has a code column (akin to the billing table), otherwise not clear what code set the code is actually from. This will also be fixed in Z&H's recent code submission that placed the COPAY from billing table into the ar_activity/ar_session tables. (COMPLETED 7/3/12)
  4. Deal with hard-coding of ICD9, CPT4, HCPCS in the claims code (COMPLETED 7/3/12)
  5. Have the CDR diagnosis searching in rule edit use the modular code search function (COMPLETED 6/16/12)
  6. Place an index on the code_type column in the codes table (COMPLETED 7/5/12)
  7. Increase size of code_type column in the billing table (varchar(15)) (COMPLETED 7/5/12)
  8. Increase size of modifier column in the codes and ar_activity table (varchar(12)) (COMPLETED 7/5/12)
  9. Place code_types (inactive) for CPTII, ICD9-SG, and ICD10-PCS (Change the labels of the ICD/SNOMED dx code types and External methods to make it clear) (COMPLETED 7/5/12)
  10. Importing mechanism for ICD9/ICD10 codes (COMPLETED 7/17/12)
  11. Fix hard-coding of ICD/CPT4 related stuff throughout codebase (COMPLETED 7/18/12)
  12. The syndromic surveillance only works with ICD9 codes. I modified the Administration->Fees to allow setting any code as reportable, however the Syndromic Surveillance report will still only show the ICD9 ones(because is involved in HL7 creation, so need to ensure it tests well with other code types before implementing). So, will need to get the report to support other code sets(and ensure it tests well since this module is needed for meaningful use).(may do this for the next release instead of 4.1.1)
  13. Add pertinent codes to the CDR engine (plan to do this for the next release - not planned for the 4.1.1 release)
  14. Consider adding support for DSMIV codeset
  15. Consider mechanisms to improve the searching (for example, real-time population of search via ajax or searching by categories etc.)
  16. Consider supporting other ICD10 sets and languages. For example, current ICD10 codes are from the CMS in the US. We can also support importing of the WHO ICD10 codes along with it on other languages.
  17. Consider supporting other SNOMED languages. (COMPLETED 02/07/2013)
  18. Consider improving the performance of the SNOMED searching. Will await feedback from the community on the performance of the current algorithm. If we needed to improve this, there is a nice discussion of this (and sample code) on the following thread: http://sourceforge.net/projects/openemr/forums/forum/202506/topic/6686760