Your EHR Is Lying to You: Clinical Data Myths That Cost You Time

Ninety-six percent of U.S. non-federal acute care hospitals had adopted certified health IT by 2021, up from just 28 percent in 2011. That's a stunning adoption curve. It's also a trap. You might look at that number and assume clinical data now moves freely between systems. It doesn't. Adoption and interoperability are different problems, and conflating them is the single biggest mistake I see clinicians and informaticists make. If you're still copying lab values between screens, the problem isn't that your hospital lacks an EHR. It's that you're treating data exchange as someone else's job. Stop doing that.

I'm going to walk through the questions I actually get asked, and I'm going to be blunt about which ones rest on myths.

Isn't the EHR supposed to solve all my data problems?

No. An Electronic Health Record is a digital system that stores a patient's medical information and supports clinical decision-making. That's it. It's a repository and a workflow tool, not an interoperability engine. The fact that 4 in 5 office-based physicians had adopted a certified EHR by 2021 doesn't mean those systems talk to each other. Most don't, at least not natively.

Here's the distinction that matters: health information technology is the broader category — hardware and software used to store, share, retrieve, and analyze health information among patients, providers, and payers. Your EHR is one slice of that. If you want data to move, you need to think in terms of standards and interfaces, not vendor logos.

HL7 v2 is dead, right? Isn't everything FHIR now?

This is the myth I hear most from developers who've never set foot in a hospital basement. HL7 Version 2 was first published in 1987 and is still used by more than 95 percent of U.S. healthcare organizations. Version 2.7, the latest update, came out in 2011. That's not a dead standard. That's the load-bearing wall of your hospital's data plumbing.

FHIR is the future, sure. FHIR R4 (version 4.0.1) was published on December 27, 2018 and was the first release with normative content. FHIR R5 landed on March 26, 2023 as a Standard for Trial Use, defining 157 resources. But here's the practical reality: HL7 v2 still handles high-throughput legacy workflows, while FHIR shines for developer-facing, mobile, and cloud-native apps. You need both. Stop treating it as a religious war.

So what actually makes clinical data usable across systems?

Vocabulary. You can have perfect pipes and still send garbage. If one system records a sodium level as "Na" and another as "Sodium, serum," your interface engine is just moving noise faster.

This is where terminology standards earn their keep. LOINC is the international standard for identifying health observations, measurements, and documents. Version 2.82, released February 24, 2026, contains 109,325 total concepts — 66,861 lab concepts and 28,635 clinical concepts. SNOMED CT handles clinical terms, and it's a designated standard for U.S. federal systems, maintained by SNOMED International with NLM as the U.S. release center. RxNorm normalizes clinical drug names and links to pharmacy vocabularies like First Databank and Multum. ICD-11, adopted by the World Health Assembly in May 2019 and effective January 1, 2022, handles diagnostic classification.

If your team is building an interface without a terminology mapping plan, you're building a bridge to nowhere.

Does HIPAA actually prevent me from sharing data?

This misconception is expensive. HIPAA was signed in 1996 to set national standards for protecting medical records, but it does not forbid appropriate sharing. The Privacy Rule limits uses and disclosures without authorization; the Security Rule protects electronic PHI. The minimum necessary standard requires reasonable efforts to limit PHI to what's needed for the purpose — it doesn't say "share nothing."

And since the 21st Century Cures Act of 2016, sharing electronic health information is the expected norm. Information blocking — a practice likely to interfere with access, exchange, or use of EHI — is prohibited for providers, health IT developers, and HIEs, unless an exception applies under 45 CFR Part 171. The applicability date moved to April 5, 2021. If you're still citing HIPAA as a reason to stonewall a patient's data request, you're on the wrong side of the law.

Warning: "We've always done it this way" is not an information blocking exception.

What about penalties — should I really care?

You should care about the right penalties. HIPAA civil monetary penalties were adjusted on January 28, 2026, raising the calendar-year cap from $2,134,831 to $2,190,294. The maximum per violation is $73,011 for Tiers 1–3, and $2,190,294 for Tier 4 willful neglect not corrected within 30 days. Those numbers are real, but they're not the ones that will bite most clinicians first.

The faster pain is MIPS. For the CY 2026 performance period, CMS finalized a performance threshold of 75 points. Clinicians scoring between zero and one-fourth of that threshold get a negative payment adjustment factor of 9 percent. The Promoting Interoperability category is 25 percent of your MIPS score. That's a quarter of your grade riding on how well you handle clinical data. Ignore it and you're leaving money on the table.

Can't I just wait for TEFCA to fix everything?

TEFCA is ONC's nationwide network-of-networks framework, formally announced in 2022. In December 2023, the first Qualified Health Information Networks were designated and data began flowing. The Sequoia Project serves as the Recognized Coordinating Entity under a 5-year ONC contract awarded in August 2023. It's real progress.

But TEFCA is infrastructure, not a magic wand. It won't clean your local terminology mess, and it won't force your favorite specialist's office to stop faxing. You still need local governance.

What should I actually prioritize?

Don't boil the ocean. Focus on these three things in order:

• Map your top 20 lab and medication concepts to LOINC and RxNorm. If you can't do that, nothing downstream works.
• Audit your information blocking posture. Know your exceptions and document them.
• Check your Promoting Interoperability score quarterly. It's 25 percent of MIPS and entirely within your control.

USCDI v3 became the baseline data standard in the ONC Health IT Certification Program on January 1, 2026. If your vendor isn't there yet, ask why. In writing.

What I'd actually do

If I ran a mid-sized practice, I'd stop waiting for perfect interoperability and start treating clinical data governance as a clinical quality issue, not an IT ticket. I'd assign one clinician and one analyst to own terminology mapping and information blocking compliance. I'd review the MIPS Promoting Interoperability dashboard monthly, not annually. And I'd stop signing contracts that don't include FHIR R4 APIs with US Core profiles — because the CMS Patient Access API has required FHIR R4.0.1 since January 1, 2021, and that train left the station years ago. You don't need a new EHR. You need to own your data. Start this week.

Sources

• ONC / HHS (Report to Congress) - https://healthit.gov/news/onc-outlines-health-it-interoperability-progress-report-congress/
• HL7 International - https://www.hl7.org/fhir/
• LOINC (loinc.org) - https://loinc.org/
• ONC / HHS (Information Blocking) - https://www.healthit.gov/topic/information-blocking
• Federal Register (CY 2026 Physician Fee Schedule) - https://www.federalregister.gov/documents/2025/11/05/2025-19787
• ONC / HHS (TEFCA) - https://www.healthit.gov/topic/interoperability/policy/trusted-exchange-framework-and-common-agreement-tefca