VBC SUCCESS IS POSSIBLE. HERE’S HOW.
Get our latest insights and exclusive case studies.
Learn more

Expert Insight

4 questions to ask yourself before an EHR data conversion

Historically, the EHR data conversion process has been tedious, error prone, and costly. But advance planning can mitigate risks, streamline workflows, and safeguard patient data.

Data conversion is one of the most important parts of switching from one electronic health record (EHR) system to another. To make sure that critical data can be easily found and understood in the new EHR,1 health systems must map both the legacy and new EHR systems to correctly label and transfer data. Historically, this process has been a challenge — a lack of healthcare data standardization has resulted in “messy” data, which can make the data conversion process difficult to plan, tedious, error-prone, and costly.  

How health systems deal with this challenge depends on many factors, such as system size, the capabilities of legacy and future EHRs, and available staffing. But while there is no silver bullet for converting EHR data,1 there are opportunities for health systems to develop partnerships and adopt technologies that can make the process easier. For example, generative artificial intelligence (AI) can speed up certain data conversion activities.

This piece delves into four questions health systems should ask themselves before tackling EHR data conversion. It accompanies “How to effectively prepare for (and implement) an EHR switch.

1. Which — and how much — data should be transferred to the new EHR?

How much data a health system integrates into a new EHR will depend on the records needed in each department to support ongoing patient care. For example, an outpatient clinic may choose to convert only the most recent imaging scans with normal results, as well as a more comprehensive set of abnormal scans. Similarly, while a hospital may need to save detailed patient histories, converting progress notes, operative reports, or completed lab orders may serve little benefit for patients.1

The amount of data converted may also depend on an organization’s size and capabilities. Large datasets may require electronic transfer, whereas much smaller datasets can be converted manually.


Case snapshot 1: Implementing Epic: The largest IT project in NYC history*

The challenge

A public safety net healthcare system in New York City served more than one million people through 11 hospitals, five acute care facilities, a home care agency, more than 70 neighborhood centers, and a correctional health services unit. The disparate EHR systems that were serving this sprawling system had led to a lack of standardization and fragmented care. Providers had to share patient information across multiple EHR systems, leading to wasted time, a high administrative burden, and the potential for data errors and leaks.

The solutions

The healthcare system:

  • Appointed an interim executive leadership team that was fully responsible for both setting project strategy and ensuring project success.
  • Deployed a team of physicians, nurses, pharmacists, and technical experts to support specific needs — including ensuring acceptable ED throughput, physician education, and pharmacy needs — at each stage of the implementation process.
  • Created a steering committee and governance structure to identify issues and mitigate risks.
Results

8,000 users trained

17 Epic system modules deployed

36 ancillary systems, including labs, blood bank, and radiology

90%-100% Leapfrog quality and safety scores, up from 50% on same metrics before the system went live

* See endnote 2.


2. Should data be converted manually or electronically?

Manual conversion involves extracting data from the legacy EHR and entering it into the new EHR by hand, whereas electronic conversion uses mediating software (often called an “interface engine”) to transfer large amounts of data automatically. Because of the complexity of healthcare data, EHR conversion processes are almost always a hybrid of electronic and manual approaches. For example, lab test codes need manual clinical review during data conversion, because test codes are not standardized among hospitals. Appointment records are another common example. Because appointment data is entangled with other patient data — such as Medicare or Medicaid eligibility — it is too complex to be transferred automatically.

How heavily an organization relies on either approach will depend — among many other things — on the amount of data to be converted, organizational budget, and capacity.1

  • Manual conversion doesn’t need an interface engine to transfer data between EHRs. Health systems can also more easily choose which aspects of each record to convert. That said, manual transfer requires a lot of time and personnel. Although using manual transfer avoids extensive testing after the data is transferred, health systems must still account for human error. All records need to be verified by a second person during the transfer process. Because the cost of manual transfer is based on personnel capacity and calculated per provider, larger health systems face a much higher cost.1
  • Electronic conversion requires a different set of skills and capabilities. After transfer and before the system goes live, the new EHR needs extensive testing to ensure that the data is complete and accurate. Because electronic conversion is expensive, it may not be a practical option for smaller practices with fewer records to convert.1 In some cases, AI support tools may help speed up the data conversion process and prevent inaccurate or missing data.

Case snapshot 2: Mergers and integrations: Quickly migrating a large medical group into an existing Epic environment*

The challenge

When a large New Jersey medical group merged with a New York-based provider organization, they decided to sunset multiple legacy EHRs and integrate with a single Epic instance used nationwide. To do this, the New Jersey medical group had to redesign certain workflows to align with a single Epic service area. On top of that, the medical group was working against the clock and would have to pay additional expenses if they didn’t transition from their legacy systems by the end of 2023.

The solution

The medical group partnered with Optum Advisory to access a cost-effective resource model and develop dynamic staffing, instead of creating a new Epic team from scratch.3 As a result, the group was able to integrate with a modernized Epic instance on time and under budget.

Results

$38.1 million total gross charges dropped

Command center closed 2 weeks early

Overall Net Promoter Score of 94 across all training classes

93% of opened tickets resolved as part of Epic Go-Live

* See endnote 2.


3. What are the challenges and risks of EHR data conversion for my organization?

If not planned and implemented carefully, EHR data conversion can lead to lost or corrupted data, increased patient wait times, disrupted provider recommendations and workflows — and can even threaten patient safety.1,4 Every health system will encounter different risks and obstacles, so identify the challenges and solutions that are specific to your organization for a smooth conversion process.5

Possible challenges and solutions related to EHR data conversion*

ChallengesPotential Solutions

Data conversion is labor intensive.

  • Work with an external partner to streamline the conversion process.
  • Clearly define the roles and responsibilities of all partners and staff.
  • Train existing staff and hire new staff to help convert data. Roles may include subject matter experts (SMEs) in the legacy EHR, conversion architecture, interface engines, medical coding, and pharmacy.6
  • Consider AI support tools to relieve pressure on staff.
EHR systems use different structures and terminology, which can be difficult to reconcile.
  • Thoroughly map both old and new EHR systems, paying close attention to the differences between them.
  • Ensure that you have clinical SMEs to effectively map the data.6
  • Deploy AI support tools that can map both legacy and destination EHR systems.
Data conversion can result in inaccurate, missing, corrupted, or inaccessible data.1,6
  • For electronic conversion, conduct thorough testing after migration and before go-live.
  • For manual conversion, assign more than one person to verify the data as it’s being transferred.
  • Maintain access to the legacy EHR system so the original data remains available for a set amount of time after go-live.1
Slow transfer process is disruptive to workflows and could lead to a delay in data being available in the new EHR when patients need it.
  • Build in extra time for the conversion process.
  • Initiate electronic transfer only at less busy times of day.
  • Maintain access to the legacy EHR system for a set amount of time.
  • Consider AI support tools to speed up the data conversion process.

* See endnote 1.

4. How can AI tools mitigate the risks and challenges of data conversion?

AI tools are increasingly available to accelerate data conversion and improve quality by automating parts of the data conversion process. For example, AI tools can map fields in both the legacy and destination EHRs, analyze their similarities and differences, and remove conflicts between data models.

And, because AI allows health systems to review and analyze large amounts of data, generative AI can help refine the data conversion process itself. By training AI on historical data conversions, health systems can leverage past processes to create new conversion models — and continue to learn and refine those models for future data conversions.

Using automated support can ensure a smooth transition and uninterrupted care delivery by:

  • Shortening the conversion timeline and reducing workflow disruptions
  • Reducing inaccurate, missing, or corrupted data
  • Alleviating the administrative burden of data conversion for staff
  • Lowering costs

As innovative as generative AI can be for EHR migration, it’s important to ground the data conversion process with human support and oversight. That could mean including IT teams to manage data conversion, having a physician-led team available to support the process, or deploying EHR-trained medical coders to validate data.    

The process of EHR data conversion is still challenging, but careful planning and setting up a framework of technological and human support can create a positive experience for health systems.

Healthcare consulting services

Need help integrating data in an EHR switch? Optum Advisory has partnered with health systems nationwide to provide insight, mitigate potential challenges, and ensure a smooth EHR transition.

1 Schrieber R, Garber L. Data Migration: A Thorny Issue in Electronic Health Record Transitions — Case Studies and Review of the Literature. ACI Open. March 12, 2020.

2 All information in this case study came from Optum Advisory interviews with officials from the medical group.

3 Advisory Board is a subsidiary of Optum. All Advisory Board research, expert perspectives, and recommendations remain independent.

4 Peleg M, Keren S, Denekamp Y. Mapping computerized clinical guidelines to electronic medical records: Knowledge-data ontological mapper (KDOM). Journal of Biomedical Informatics. May 16, 2007.

5 Huang C, et al. Transitions from One Electronic Health Record to Another: Challenges, Pitfalls, and Recommendations. Applied Clinical Informatics. November 11, 2020.

6 Maher T, Bloemer L. Data Conversion Best Practices. Hayes Management Consulting. April 7, 2011.


SPONSORED BY

INTENDED AUDIENCE

AFTER YOU READ THIS
  • You’ll know how to decide which data to transfer to the new EHR.
  • You’ll see how manual and electronic approaches are used in the conversion process.
  • You’ll understand how AI tools can help with data conversion.

AUTHORS

Carol Chouinard

Vice president, Provider technology advisory services, Optum Advisory

Kevin Cahalane

Senior director, EHR services, Optum Insight

TOPICS

INDUSTRY SECTORS

Don't miss out on the latest Advisory Board insights

Create your free account to access 1 resource, including the latest research and webinars.

Want access without creating an account?

   

You have 1 free members-only resource remaining this month.

1 free members-only resources remaining

1 free members-only resources remaining

You've reached your limit of free insights

Become a member to access all of Advisory Board's resources, events, and experts

Never miss out on the latest innovative health care content tailored to you.

Benefits include:

Unlimited access to research and resources
Member-only access to events and trainings
Expert-led consultation and facilitation
The latest content delivered to your inbox

You've reached your limit of free insights

Become a member to access all of Advisory Board's resources, events, and experts

Never miss out on the latest innovative health care content tailored to you.

Benefits include:

Unlimited access to research and resources
Member-only access to events and trainings
Expert-led consultation and facilitation
The latest content delivered to your inbox

This content is available through your Curated Research partnership with Advisory Board. Click on ‘view this resource’ to read the full piece

Email ask@advisory.com to learn more

Click on ‘Become a Member’ to learn about the benefits of a Full-Access partnership with Advisory Board

Never miss out on the latest innovative health care content tailored to you. 

Benefits Include:

Unlimited access to research and resources
Member-only access to events and trainings
Expert-led consultation and facilitation
The latest content delivered to your inbox

This is for members only. Learn more.

Click on ‘Become a Member’ to learn about the benefits of a Full-Access partnership with Advisory Board

Never miss out on the latest innovative health care content tailored to you. 

Benefits Include:

Unlimited access to research and resources
Member-only access to events and trainings
Expert-led consultation and facilitation
The latest content delivered to your inbox
AB
Thank you! Your updates have been made successfully.
Oh no! There was a problem with your request.
Error in form submission. Please try again.