TL;DR
- The certification, Medicare and information-blocking rules define EHR terms and never define “EMR”. Federal usage follows: the eCQI glossary (updated June 2026) lists “electronic medical record” as another name for an EHR.
- Where people still split the terms, the line is sharing: an EMR is one organization’s chart, an EHR is built to travel between organizations.
- Certification duties attach to certified products, and information-blocking duties to providers, developers of certified health IT and health information networks. A vendor with no CHPL listing carries neither, so the contract is your protection.
- Epic’s products are certified EHRs on CHPL, and all 22 active products with “EMR” in their name are certified for electronic health information export (CHPL, October 25, 2026).
- The label still matters in three places: your RFP, your contract and your exit plan. Write criteria there, and name the CHPL listing.
What Is the Difference Between an EMR and an EHR?
No federal rule draws a difference: the certification, Medicare and information-blocking rules never define “EMR”. Where people separate the two, the line is how far the record travels.
Federal usage points the same way. The eCQI Resource Center glossary entry, last updated on June 11, 2026, defines an EHR as “a digital record of a patient’s health information created over time from one or more visits and across care settings.” Then it adds the line that settles the naming question: an EHR is “also called an electronic patient record, electronic medical record, or computerized patient record.” A glossary carries no legal weight. It shows how federal programs use the words.
The split you’ll read on most vendor sites is older. In January 2011, Peter Garrett and Joshua Seidman at ONC (the Office of the National Coordinator for Health IT) wrote on the agency’s blog that the difference between the two terms “is actually quite significant”. They described EMRs as “a digital version of the paper charts in the clinician’s office” and said that with an EHR, “the information moves with the patient.” That post still ranks on page one of Google for this question. So most pages still draw a hard line.
So two federal documents, written fifteen years apart, use the words differently, and neither is a rule. The rules themselves, covered below, settle it by never defining “EMR”.
In practice, people now use the words like this:
- EMR: the chart inside one practice or hospital, built around diagnosis and treatment.
- EHR: the same chart built to be exchanged with labs, hospitals, specialists, payers and the patient.
- PHR: a personal health record the patient keeps. That one really is different, and our page on EHR vs PHR covers it.
What the record does is a separate question from what it’s called. The core EHR functions guide walks through the eight jobs a record system has to do. For what an EMR does well on its own, see the advantages of electronic medical records.
EMR vs EHR: How Do They Compare Side by Side?
The table below separates how vendors use each word from what the federal rules require. Every row in the third column comes from rule text, as of October 2026.
| “EMR” as vendors use it | “EHR” as vendors use it | What the federal rules say | |
|---|---|---|---|
| Where the meaning comes from | ONC’s 2011 blog: “a digital version of the paper charts in the clinician’s office” | ONC’s 2011 blog: “the information moves with the patient” | eCQI glossary (June 2026): one term, with EMR listed as another name |
| Typical scope | One practice or one organization | Several organizations and care settings | No scope test. Certification is granted per product or module and listed on CHPL |
| Sharing | Often manual: fax, printed summaries, file export | Structured exchange: care summaries and APIs | A Base EHR must be certified to transitions of care, §170.315(b)(1), and the FHIR API, (g)(10) (45 CFR 170.102) |
| Getting data out | Depends on the vendor contract | Depends on the vendor contract | A certified product that stores patient data must offer single-patient and population export, §170.315(b)(10) (45 CFR 170.402(a)(4)) |
| Patient and app access | Portal, if the vendor offers one | Portal plus third-party apps | (g)(10) API for one patient or a group, using US Core and USCDI v3 (45 CFR 170.315, 170.213) |
| Information blocking | Covers the vendor only if it develops certified health IT | Same | 45 CFR 171.102 defines the covered “actor” as “a health care provider, health IT developer of certified health IT, health information network or health information exchange.” A vendor with no certified module on CHPL isn’t covered as a developer |
| What to check before you buy | The CHPL listing | The CHPL listing | The CHPL listing ID and the exact criteria it’s certified to |
Sources: eCQI Resource Center (updated June 11, 2026); ONC blog, January 4, 2011; eCFR, 45 CFR parts 170 and 171, up to date as of October 22, 2026.
The first two columns describe habits of speech; the third is the one a vendor can be held to.
Is Epic an EHR or an EMR? (And Other Examples)
By federal terms, Epic’s products are certified EHRs. For any product, the listing on ONC’s Certified Health IT Product List (CHPL) tells you more than the name on the brochure.
Epic certifies two base products, “EpicCare Ambulatory Base” and “EpicCare Inpatient Base”, with a separate listing for each version. Both are certified to EHI export and to the FHIR API. The same check works on any product in a proposal, including the ones that call themselves EMRs.
Examples of certified EHR products, by what their names say (CHPL, October 25, 2026)
| Product (developer) | Name uses | EHI export, §170.315(b)(10) | FHIR API, §170.315(g)(10) |
|---|---|---|---|
| EpicCare Ambulatory Base (Epic Systems) | neither | ✓ | ✓ |
| EpicCare Inpatient Base (Epic Systems) | neither | ✓ | ✓ |
| athenaClinicals (athenahealth) | neither | ✓ | ✓ |
| Oracle Health Millennium (Clinical) (Oracle Health) | neither | ✓ | ✓ |
| MEDITECH 6.1 Ambulatory Electronic Health Record (MEDITECH) | EHR | ✓ | ✓ |
| NextGen Enterprise EHR (NextGen Healthcare) | EHR | ✓ | ✓ |
| Practice Fusion EHR (Practice Fusion) | EHR | ✓ | ✓ |
| Veradigm EHR (Veradigm) | EHR | ✓ | ✓ |
| Elation EMR (Elation Health) | EMR | ✓ | ✓ |
| MicroMD EMR (MicroMD) | EMR | ✓ | ✓ |
| Experity EMR (Experity) | EMR | ✓ | not on this listing |
Source: CHPL, active listings, pulled October 25, 2026. A listing can cover one module of a larger product, so a criterion missing from one listing can sit on a sibling listing from the same developer.
Across all 729 active CHPL listings that day, 22 products carry “EMR” in their name. All 22 are certified for EHI export, and 11 of the 22 for the FHIR API. Another 105 listings carry “EHR” or “health record” in the name: 104 of them have EHI export and 66 the FHIR API. Across every active listing, 663 of 729 have EHI export and 298 have the FHIR API. The name doesn’t predict either number.
People also ask for the “top 3 EHR systems”. For hospitals, ASTP/ONC’s Data Brief No. 83 (June 2026) gives 2024 market share: Epic supplied 50.8% of non-federal acute care hospitals, Oracle Health 20.1% and MEDITECH 15.6%, three developers serving “over 4 in 5 hospitals.” That’s market share, which says nothing about fit, and the companion Data Brief No. 84 finds smaller physician practices “more likely to use a wider range of EHRs.” Our guide to the best EHR vendors compares the large ones on published facts.
To check a product yourself:
- Open CHPL and search the product or developer name.
- Filter to active listings and open the newest version.
- Look for 170.315(b)(10), (g)(10) and (b)(1) in the criteria list, and copy the listing ID and the API documentation link into your RFP.
Build interoperability without replacing your EMR or EHR
Do the Regulations Treat EMRs and EHRs Differently?
No. The rules that certify these systems, pay for their use and police data access define EHR terms and never define “EMR”.
Take the four rule sections that define what a certified EHR is and how it’s used (45 CFR 170.102, 170.315, 171.102 and 42 CFR 495.4). As the eCFR reads on October 22, 2026, “EMR” and “electronic medical record” appear zero times.
Three definitions do the work:
- Base EHR (45 CFR 170.102): an electronic record that includes demographics and clinical information and has the capacity “to exchange electronic health information with, and integrate such information from other sources,” certified to a set list of criteria, including the FHIR API.
- Certified EHR technology, or CEHRT (42 CFR 495.4): what hospitals and clinicians must use to report Medicare’s Promoting Interoperability program.
- Information blocking (45 CFR 171.103): a practice likely to interfere with access, exchange or use of electronic health information. It applies to the “actors” listed in 45 CFR 171.102: “a health care provider, health IT developer of certified health IT, health information network or health information exchange.” Whether a vendor is covered turns on whether it has a certified module, never on what its product is called.
ASTP/ONC reports that hospital EHR adoption reached 99% by 2018 (Data Brief No. 83) and that nine in ten office-based physicians used a certified EHR in 2024 (Data Brief No. 84, June 2026). For most of the charts a CIO inherits, the certification criteria are the common floor.
Building your own system? Our EHR certification requirements guide covers the criteria, and the HTI-1 final rule explainer covers the 2024 changes.
Buy when a certified product fits the workflow you run. Keep and connect when the system you have works and only the exchange is missing. Build when the workflow is the product you sell.
For most practices and hospitals, buying is the right call, and the best EHR vendors guide is the place to start a shortlist. A digital health company is different. When the clinical workflow is your product, an off-the-shelf EHR forces it into someone else’s screens, and that’s where a build makes sense.
We build custom EHRs around your workflow, and we build integrations with Epic, Oracle Health and athenahealth. For a precision medicine practice, the initial platform was live in under ninety days.
Where the platform holds an ONC listing (check CHPL), certifying your EHR built on it is a separate step: scope it from day one. What a build costs, by approach, is in our EHR software cost guide.
How Does a Patient’s Record Travel Between Systems?
A record leaves the system that holds it in one of three ways: as a care summary document, through an API call, or through a query across a health information network. Each route has its own rule behind it.
Take a common referral. A patient’s primary care clinic sends her to a cardiologist at a hospital, and she later opens a heart-health app on her phone.
- The care summary. When the clinic refers her, its system sends a referral summary in the C-CDA document format over secure Direct messaging. That’s the transitions-of-care criterion, §170.315(b)(1), and the receiving system has to validate and display it.
- The API. The app asks the clinic’s system for her data through the standardized FHIR API, §170.315(g)(10). The same API can return data for a group of patients at once, which is how a hospital or an analytics team pulls a population in bulk. Since January 1, 2026, the data set those certified APIs carry is USCDI version 3: the version 1 adoption expired that day under 45 CFR 170.213.
- The network. The cardiologist’s system queries a health information exchange, or a national network under TEFCA (the Trusted Exchange Framework and Common Agreement), for records from places the clinic never sent anything to. Our TEFCA guide explains how that network is governed.
None of the three routes asks whether the sending system calls itself an EMR or an EHR. They ask whether it’s certified to the criterion and whether the data arrives in the standard the criterion names.
Exchange breaks on details. Two systems code the same lab test differently. One patient shows up as two people because a birth date was keyed wrong, or a summary arrives as a document the receiving team never reconciles into the chart. Those are mapping and matching problems. They’re why the coordination gains described on our page about the benefits of EHR systems for patients depend on the exchange being mapped and tested. The common failure points in a rollout are covered in our guide to the challenges of implementing an EHR.
Where Does the EMR vs EHR Label Still Matter?
In three documents you control: the RFP, the contract and the exit plan. In each of them, write the criteria and the listing, and let the vendor call the product whatever it likes.
The rules give you a floor, and the contract decides how easy it is to stand on it. EHI export under §170.315(b)(10) requires a certified product to let a user “timely create an export file(s) with all of a single patient’s electronic health information,” plus an export of the whole patient population, “in a computable format,” with “the publicly accessible hyperlink of the export’s format” included. Under §170.402(a)(4), a developer of certified health IT whose product stores that information must certify to it.
If the vendor is one of those developers, holding data back can also count as information blocking. None of that tells you how often you can run the export, who on your side holds the right, or what happens on the last day of the contract. The contract has to say it.
That matters most when a product isn’t on CHPL. Then none of the certification duties apply to that vendor: no required export, no certified API, and no information-blocking exposure as a developer of certified health IT. Your protection is whatever the contract says, which is why the six clauses below carry more weight for an uncertified product.
Six clauses I’d put in any EHR contract or RFP, whatever the product is called:
- The CHPL listing ID for each product and version you’re buying, and the criteria you rely on: (b)(1), (b)(10) and (g)(10) at minimum.
- Single-patient and population export under (b)(10), in the documented format, with the format documentation link delivered with each export.
- How often you can run a population export, and who on your side holds the system-administrator role the rule allows the vendor to require.
- The (g)(10) API base URL and documentation link (CHPL publishes both), and how your own apps get registered against it.
- Exit help: what the vendor does in the last 90 days of the contract, and in what format the final export arrives.
- A legacy read-only period after cutover of 30-90 days, set by your retention and audit needs.
Moving the data is its own project. Our guide to EHR data migration covers mapping, validation and cutover, and Mindbowser moved 180 production databases.
What’s Changing Next for EHR Rules?
The certification program is set to shrink, and the two criteria buyers lean on most survive in the proposal.
- HTI-5, proposed. ASTP/ONC published the HTI-5 proposed rule on December 29, 2025. In its own words, “out of the 60 certification criteria that are currently in effect, we propose to remove 34 and revise seven”, 24 of them as of a final rule’s effective date and the other 10 on January 1, 2027. That’s more than half the program. It keeps EHI export, (b)(10), and the FHIR API, (g)(10), and would remove the older app-access criteria, (g)(7) through (g)(9). It also proposes removing the TEFCA Manner Exception from the information-blocking rules.
- Still not final. As of October 25, 2026, the Federal Register shows no HTI-5 final rule, and CMS’s fiscal year 2027 inpatient payment final rule of August 4, 2026 still describes it as “the HTI-5 proposed rule”.
- USCDI v3 is the only data baseline. The version 1 adoption expired on January 1, 2026 (45 CFR 170.213).
- The adoption numbers stop. ASTP/ONC says Data Brief No. 84 (June 2026) “represents ONC’s final formal reporting of physician EHR adoption statistics.”
What does that mean for the table above? If HTI-5 is finalized as proposed, a CHPL listing will carry fewer criteria, and the export and API rows will matter more, because they’re among the criteria left. I don’t know when the final rule lands or how much of the proposal survives comment. Recheck the criteria list on CHPL before you sign anything long.
Should You Buy an EHR, Keep Your EMR, or Build Your Own?
Buy when a certified product fits the workflow you run. Keep and connect when the system you have works and only the exchange is missing. Build when the workflow is the product you sell.
For most practices and hospitals, buying is the right call, and the best EHR vendors guide is the place to start a shortlist. A digital health company is different. When the clinical workflow is your product, an off-the-shelf EHR forces it into someone else’s screens, and that’s where a build makes sense.
We build custom EHRs around your workflow, and we build integrations with Epic, Oracle Health and athenahealth. For a precision medicine practice, the initial platform was live in under ninety days.
Where the platform holds an ONC listing (check CHPL), certifying your EHR built on it is a separate step: scope it from day one. What a build costs, by approach, is in our EHR software cost guide.








BLOGS
NEWSROOM
CASE STUDIES
WEBINARS
PODCASTS
ASSET HUB
EVENT CALENDAR 


















