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”.
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.
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 healthcare system:
* See endnote 2.
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
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 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.
* See endnote 2.
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
Challenges | Potential Solutions |
---|---|
Data conversion is labor intensive. |
|
EHR systems use different structures and terminology, which can be difficult to reconcile. |
|
Data conversion can result in inaccurate, missing, corrupted, or inaccessible data.1,6 |
|
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. |
|
* See endnote 1.
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:
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.
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.
Create your free account to access 1 resource, including the latest research and webinars.
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
Never miss out on the latest innovative health care content tailored to you.
You've reached your limit of free insights
Never miss out on the latest innovative health care content tailored to you.
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
Never miss out on the latest innovative health care content tailored to you.
This is for members only. Learn more.
Never miss out on the latest innovative health care content tailored to you.