Galen Healthcare Solutions: Allscripts Consultants Enterprise EHR

This piece is the first of a two part series discussing the transition to ICD-10. The ICD-10 transition should be a high priority concern in healthcare.

Today, the healthcare industry is rapidly moving closer to the compliance date for ICD-10. That date is October 1, 2013.  As that date draws closer, organizations will need to actively take action to successfully be compliant.  The Centers for Medicare and Medicaid Services (CMS) is actively providing resources to assist in achieving this success.

FAQ Fact Sheet

CMS posted a downloadable PDF FAQ “transition basics” fact sheet indicating sixteen question and answers.  This tip sheet gives an excellent and informative overview to the transition to ICD-10.

Among these Q/A’s are:

• What does ICD-10 compliance mean?
• ICD-10 compliance means that all Health Insurance Portability and Accountability Act (HIPAA) covered entities are able to successfully conduct health care transactions on or after October 1, 2013 using the ICD-10 diagnosis and procedure codes. ICD-9 diagnosis and procedure codes can no longer be used for health care services provided on or after this date
• What is the transition to ICD-10 happening?
• The transition is occurring because ICD-9 codes have limited data about patients’ medical conditions and hospital inpatient procedures. ICD-9 is 30 years old, has outdated and obsolete terms, and is inconsistent with current medical practice.
• Also, the structure of ICD-9 limits the number of new codes that can be created, and many ICD-9 categories are full.
• A successful transition to ICD-10 will be vital to transforming our nation’s health care system.
• What type of training will providers and staff need for the ICD-10 transition?
• Training should take place in late 2012 or early 2013 for most staff. Training needs will vary for different organizations. For example, physician practice coders will need to learn ICD-10 diagnosis coding only, while hospital coders will need to learn both ICD-10 diagnosis and ICD-10 inpatient procedure coding.
• Look for specialty-specific ICD-10 training offered by societies and other professional organizations. Take into account that ICD-10 coding training will be integrated into the CEUs that certified coders must take to maintain their credentials.
• ICD-10 resources and training materials will be available through CMS, professional associations and societies, and software/system vendors. Visit http://www.cms.gov/ICD10 regularly throughout the course of the transition to access the latest information on training opportunities.

As we move closer to the deadline, CMS will certainly provide more information on the ICD-10 transition. Visit their Latest News page to sign up for notifications, industry updates, attend teleconferences, and obtain other valuable resources.

The second part of this series will discuss implementation and producing results.  Look for that piece next week!

Tags: Centers for Medicare and Medicaid Services, Clinical Conversion, CMS, Compliance, Data Conversion, Healthcare IT, ICD-10, ICD9, October 2013

Drawing on our past experience and expertise with data conversions, we recently assisted one of our clients with a conversion of administrative ICD9 diagnostic data extracted from their Practice Management system to clinical Medcin-based  problem data within the EHR. The project ultimately saved a tremendous amount of data entry time. Upon completion of the data-conversion, clinicians were then able to review the problem list in “Past Medical History” section of the patient chart within the EHR and categorize by either choosing to make the problem “active” or mark redundant or resolved problems as “Entered in Error”.

As with any data conversion, one must be cautious in terms of negative implications. For instance, administrative data has its limitations, and an example or where the process can go wrong is the highly-publicized case of e-Patient Dave.  Ultimately, problem conversions can be useful, but the data needs to be reviewed, and almost treated as suspect.  The value in the conversion is saving the entry of the problems that are accurate – say 80-90%.  Any that are incorrect, will be reviewed with the patient and can easily be marked EIE.

Statistics:

• 1,007,238 problems were loaded to the EHR for 205,831 patients via the interface engine, taking about 11 hours to process totally.
• PM Extract file statistics:
  • Total matchups of ICD9s to patients: 5,405,874
  • Total Unique ICD9s: 8346
  • ICD9s that only match up with 1 patient:1295
  • ICD9s that match up with 100 or more patients: 2027

Approach and Components:

• Master approved “ICD9” list provided by client
• Extract of ICD9 data from PM system provided by PM vendor
• Automated macro that attempts to match ICD9 to Medcin. Potential matches include the following:
  • 1 to 1
  • One to many (20 or less)
  • One to many (20 plus)
  • One to none
  • Each of the different flavors of matches were marked with an annotation (highlighted via an asterisk) to identify to clinicians the logic that was used in importing the problems:

• Once the translation was finalized, it was loaded into the interface engine and mapping logic loaded problems into the patient chart in the EHR via the API (existing stored procedure).

Known Issues Mitigated:

• Due to incorrect logic, some ICD9s were linked to patient profiles improperly. To mitigate this, a script was run to mark these problems as “entered in error”
• Problems were loaded to the “Past Medical History” section of the patient chart with a status of active. However, given this status, it didn’t facilitate providers to easily change the problem to be an active problem linked to a note.

Lessons Learned:

• Execute a proof-of-concept and as with any technical project, get clinician feedback. The client had a pilot group of 5 clinicians to vet out issues and bless the data before the live conversion was run.
• Do NOT use spreadsheets to track the cross-walk between administrative ICD9 diagnoses and clinical Medcin problems. Rather utilize a staging DB to serve as a single repository in developing ICD9 to Medcin translations. Also, the data from flat-file export from PM can be loaded into a staging environment via SSIS such that it can be analyzed and summarized while facilitating persistence.
• Make sure to tie the problem conversion load to a specific provider, that way if side effects or issues are identified after the fact, there is a clear way to identify which problems were loaded in the conversion via the provider they are tied to. The interface log should also have a record of this, but most organizations set the retention time to 90 days.
• Workflow validation – ensure that the workflow to move problems from PMH to Active will not be a barrier to use.

If your organization is looking for assistance in data conversion, please contact sales@galenhealthcare.com and visit our website for more information regarding our technical service offerings.

Tags: Allscripts, Allscripts Enterprise EHR, Data Conversion, ICD9, Interfaces, Medcin, Problem Conversion, TouchWorks Problem