Why 'Interoperability' Failed Healthcare—And What Actually Works

“Interoperability” has been healthcare IT’s golden promise for two decades. Connect all the systems. Share all the data. Seamless care coordination. Better outcomes. Lower costs.

The industry invested billions. Mandated standards like HL7 and FHIR. Built bridges between electronic health records, laboratory systems, pharmacy platforms, and insurance networks.

And it made everything worse.

Not because the technology didn’t work—it connected systems beautifully. But because interoperability without verification is just automated fraud distribution.

I know this because interoperability nearly destroyed my life.

When “Seamless Data Exchange” Becomes a Prison

Remember my mountain bike accident from the previous blog? Dislocated shoulder, dislocated clavicle-thorax joint, ripped ligaments, torn tendons, fused disks in my neck, bulging disks in my lower back.

The hospital sent me home diagnosing “inflammation.” Billed $4,500. Had an MD in Texas sign off on care delivered in California.

Here’s what I didn’t tell you: The real nightmare started after I left the emergency room.

The Interoperability Trap

Within 24 hours of my discharge, the hospital’s EHR system had seamlessly transmitted my records to my insurance company via secure, HIPAA-compliant, industry-standard interoperability protocols.

What was transmitted:

• Diagnosis: Inflammation
• Treatment: One X-ray, observation
• Disposition: Stable, discharged home
• Assessment: No significant injury

What was reality:

• Multiple severe injuries requiring specialist care
• Misdiagnosed due to inadequate examination
• Sent home in excruciating pain
• Progressive worsening of untreated injuries

But according to the interoperable data exchange, I was fine.

The Cascade of Consequences

I sought follow-up care with specialists. Orthopedic surgeons. Physical therapists. Pain management doctors.

Every single one accessed the same interoperable record. And every single one saw: “Patient presented with shoulder pain. Diagnosed with inflammation. No significant findings.”

When I explained my actual injuries—visible asymmetry, inability to move my arm properly, constant pain—doctors looked at me with skepticism.

“The ER didn’t find anything significant.”

“The X-ray shows only minor inflammation.”

“Sometimes pain perception can be amplified by anxiety.”

The interoperable data had become my medical reality. And that reality said I was essentially fine.

When Experience Meets Interoperability

I finally found doctors with over 30 years of experience who were willing to do comprehensive examinations independent of what the interoperable records claimed.

They discovered the full extent of my injuries. Multiple specialists confirmed: severe damage requiring months of treatment.

But then they told me something that made my blood run cold:

“You may have to move to a different state to get proper care.”

Why? Because most doctors avoid taking on existing cases where insurance already has a diagnosis from another provider. The interoperable record creates a medical history that’s nearly impossible to override.

If they diagnosed me differently than the ER, they risked:

• Insurance denying claims (contradicting prior diagnosis)
• Liability for “unnecessary treatment” (if ER said inflammation only)
• Accusations of “doctor shopping” (patient seeking diagnosis they want)
• Audit flags (billing for services insurance thinks are unwarranted)

The interoperable system had created a false medical reality—and locked me inside it.

What Interoperability Actually Achieved

Let me be explicit about what “seamless data exchange” did in my case:

1. Propagated False Information at Scale

The hospital’s malpractice—wrong diagnosis, inadequate care, fraudulent billing—wasn’t contained to one institution. It was instantly distributed to:

• My insurance company
• My primary care physician’s EHR
• The pharmacy network (for discharge medications)
• Any provider who looked up my records

One bad diagnosis became the official truth across the entire healthcare ecosystem.

2. Created Systemic Bias Against Correction

Once data is in the interoperable network, correcting it is nearly impossible because:

• Each system has its own data governance rules
• Amendments require coordinating multiple entities
• Original records are preserved for legal/audit purposes
• Insurance has already processed claims based on initial data
• New providers see the “official” history and trust it

I wasn’t fighting one hospital’s error. I was fighting the entire networked healthcare system.

3. Automated Fraud Distribution

Remember: The hospital billed using CPT codes for services that never happened. An MD who was never in the same state “examined” me.

Without interoperability, this fraud would have required manual claims submission. Someone might have noticed the geographic impossibility.

Instead, the automated data exchange:

• Transmitted discharge summary (signed by Texas MD)
• Sent billing codes (for examination that never occurred)
• Shared treatment notes (describing care that wasn’t delivered)
• Updated insurance records (marking claims as processed)

All within 24 hours. All automatically. All fraudulently.

Interoperability didn’t detect the fraud—it accelerated it.

4. Made Patient Advocacy Nearly Impossible

When I tried to dispute the charges and diagnosis, I faced:

At the hospital: “Our records show appropriate care was delivered.”

At my insurance: “Our records match the hospital’s. Claim is valid.”

At specialist offices: “Your records show you were diagnosed with inflammation.”

Everyone was looking at the same interoperable data. And because it was “standardized” and “secure” and “compliant,” everyone assumed it was true.

The technology designed to empower patients had disempowered me completely.

The Interoperability Illusion

The healthcare IT industry sold interoperability as the solution to fragmented care. But they fundamentally misunderstood the problem.

The problem was never that systems couldn’t talk to each other.

The problem was that systems never verified what actually happened.

What Current Interoperability Connects

Let’s look at what today’s “interoperable” systems actually exchange:

Laboratory Information Systems (LIS) → EHR:

• Test results
• Not: Was the specimen actually collected? Was the chain of custody maintained? Was the test performed or just ordered?

Pharmacy Management → EHR:

• Medication dispensing records
• Not: Did the patient actually receive it? Was it properly stored? Did someone divert it?

Radiology PACS → EHR:

• Images and reports
• Not: Did a qualified radiologist review it? What was their interpretation process? Were they actually present?

EHR → Insurance:

• Diagnosis codes, procedure codes, provider signatures
• Not: Did the services actually occur? Was the provider actually present? Were the codes accurate?

What gets transmitted is data. What doesn’t get transmitted is truth.

My Experience in Public Health: Interoperability Enabling Systematic Fraud

In my previous blog, I described the corruption I witnessed in public health. Interoperability made all of it worse.

The Medication Diversion Scheme—Interoperable Version

Remember the facility where 1,000 antibiotic units arrived, 400 were stored, 600 vanished, but 800 “administrations” were recorded?

Here’s how interoperability turbocharged that fraud:

1. Procurement system records: 1,000 units received
2. Pharmacy system records: 400 units in inventory
3. EHR records: 800 patient administrations
4. Billing system submits: 800 reimbursement claims

Each system talked to the others perfectly. HL7 messages flowed seamlessly. FHIR resources were beautifully formatted. Data exchanged in real-time.

But nobody verified:

• Where did 600 units go?
• How were 800 administrations recorded when only 400 units existed?
• Why didn’t inventory reconciliation trigger alerts?

Because interoperability systems were designed to move data, not validate it.

The Ghost Provider Network

Interoperability enabled something even more sinister: providers who existed only in the network.

How it worked:

1. Create provider credentials in one EHR system
2. Submit claims from that provider across the interoperable network
3. Services billed, claims paid, no questions asked
4. The “provider” never sees a patient, never touches equipment, never exists physically

Why did this work? Because credentialing databases were interoperable but not verified.

The system checked: Is this provider ID in the database? The system didn’t check: Is this provider actually licensed? Actually present? Actually practicing?

Just like the MD in Texas who “examined” me in California—interoperability made geographic impossibilities seem legitimate.

The COVID Breaking Point

During COVID, I saw interoperability fail catastrophically at scale.

Pallets of supplies arrived. PPE, testing kits, medications. The interoperable supply chain systems registered everything:

• Procurement platforms confirmed orders
• Shipping systems confirmed delivery
• Inventory management confirmed receipt
• Financial systems processed payments

All systems green. All data flowing. Perfect interoperability.

Then you’d walk into the storage area and find:

• Expired masks still in shrink wrap
• Testing kits nobody knew how to use
• Medications incompatible with facility protocols
• Equipment that required training nobody had received

The interoperable systems said we were prepared. Reality said we were drowning in unusable supplies.

Why? Because the systems exchanged purchase orders, delivery confirmations, and payment approvals—but never verified:

• Can staff actually use this equipment?
• Is this compatible with existing protocols?
• Will this expire before we can use it?
• Does this meet the actual clinical need?

Interoperability connected the systems. But it didn’t connect the systems to reality.

The False Promise of FHIR and HL7

The healthcare IT industry will tell you: “We just need better standards!”

HL7 version 2, then version 3, then FHIR (Fast Healthcare Interoperability Resources). Each generation promised to fix the problems of the last.

None of them address the fundamental issue: verification.

What FHIR Does Well

FHIR is actually elegant technology. It defines data structures for:

• Patient demographics
• Clinical observations
• Medications
• Procedures
• Diagnostic reports

It uses modern web APIs (RESTful, JSON). It’s extensible. It’s well-documented.

If you want to move healthcare data between systems, FHIR is excellent.

What FHIR Doesn’t Do

FHIR has no mechanism to verify:

• Did this observation actually occur?
• Was this medication actually administered?
• Did this procedure actually happen?
• Is this diagnostic report actually valid?

FHIR can tell you that “Patient received Medication X at 2:47 PM” got transmitted from System A to System B.

FHIR cannot tell you if Patient actually received Medication X at 2:47 PM.

FHIR is a data transport protocol. It’s not a truth verification system.

The Blockchain Delusion

“Put healthcare records on blockchain!”

I hear this constantly. And it misses the point entirely.

Blockchain provides immutable storage. Once data is written, it can’t be altered. This is valuable for preventing retroactive tampering.

But blockchain doesn’t verify that the data was true when it was written.

If I write to blockchain: “Patient examined by MD in Texas” when patient was actually in California—the blockchain preserves that lie immutably and distributes it across every node.

Immutable lies are still lies.

The same problem applies to:

• Distributed ledgers: Great for preventing after-the-fact changes, useless for preventing initial fraud
• Zero-knowledge proofs: Verify data properties without revealing data, but don’t verify data accuracy
• Smart contracts: Execute automatically based on conditions, but can’t verify if conditions actually occurred

What Would Actually Work

After experiencing interoperability failure as a patient and witnessing it as a healthcare worker, I understand what’s actually needed.

Not better data exchange. Better data creation.

1. Verify at the Point of Origin

Data should be validated when it’s created, not after it’s distributed.

Current model:

• Event happens (or doesn’t)
• Someone records it in a system
• System transmits to other systems
• Everyone assumes the original data was accurate

Required model:

• Event happens with cryptographic proof (biometric, geolocation, device attestation)
• Multiple parties verify (patient, provider, equipment)
• System records only after verification
• Transmission includes verification chain

Example: My mountain bike accident

• MD must biometrically authenticate at patient location (can’t sign from Texas)
• X-ray equipment must timestamp and geolocate images (proves what was actually done)
• Patient must confirm services received (I can flag “no MD examination”)
• Insurance receives verified data, not just claimed data

2. Track Physical Items, Not Just Data

Interoperability exchanges information about items. We need to track the items themselves.

Current model:

• Medication ordered → system records order
• Medication dispensed → system records dispense
• Medication administered → system records administration
• No verification that the physical medication matched these digital events

Required model:

• Medication arrives → scanned with lot number, expiration, temperature log
• Medication stored → scanned into specific location, temperature-monitored storage
• Medication retrieved → scanned out by specific provider at specific time
• Medication administered → scanned at patient bedside with patient confirmation
• Medication disposal → scanned with witness verification

Chain of custody, not chain of data.

When 1,000 units arrive and 800 administrations are recorded, the system automatically flags: “Where are the other 200 units?“

3. Multi-Party Verification for Critical Events

High-value transactions should require consensus, not single-party assertion.

Current model:

• One person marks procedure “complete”
• System accepts and transmits
• Everyone downstream trusts it

Required model:

• Technician confirms: “I performed this step”
• Equipment confirms: “I was operational during this time”
• Provider confirms: “I reviewed and approved”
• Patient confirms: “I received this care”
• Consensus required before data is considered valid

This is how blockchain actually becomes useful—not for storage, but for multi-party verification before commitment.

4. Patient-Visible Transaction Log

Every piece of data transmitted about me should be visible to me in real-time.

If I could have seen:

• “MD [Name] in Texas signed your discharge at 11:47 PM”
• “Procedure code: Comprehensive examination”
• “Diagnosis transmitted to insurance: Inflammation”

I could have immediately flagged:

• “No MD examined me”
• “I never had a comprehensive examination”
• “I have severe injuries, not inflammation”

Before the data propagated across the entire healthcare network.

Patient transparency isn’t just about rights—it’s about quality control.

5. Jurisdiction-Specific Validation

The system should enforce basic logic that current interoperability ignores.

Examples:

• Provider in State A cannot sign off on care in State B without proper licensing
• Equipment must be calibrated/functional to generate valid test results
• Procedures requiring specialist certification can’t be performed by non-specialists
• Medications requiring specific storage conditions can’t be used if storage wasn’t verified

These aren’t complex algorithms. They’re basic sanity checks that interoperable systems never implemented.

The Real Interoperability We Need

True interoperability isn’t about connecting databases—it’s about connecting reality to data.

Current interoperability connects:

• System to system
• Data to data
• Transaction to transaction

Needed interoperability connects:

• Physical events to digital records
• Multiple verifiers to single truth
• Patients to their own data
• Reality to what gets billed

This requires completely different technology architecture:

Not: “How do we move data between systems?”

But: “How do we ensure data represents truth before moving it?”

Why the Industry Resists This

The healthcare IT industry has no incentive to build verification-based interoperability because:

1. Current systems are profitable: Vendors sell integration engines, middleware, data transformation tools—all unnecessary if data was verified at origin

2. Fraud is a feature, not a bug: Hospitals, insurers, and providers benefit from opacity that allows billing optimization

3. Complexity creates moats: Companies with 2,700 subsidiaries (like UnitedHealth) thrive on interoperability that obscures rather than clarifies

4. Standards bodies are captured: HL7 and FHIR are driven by vendors who profit from the status quo

As I wrote in “The Bell Curve of Politics,” corruption doesn’t wear a color—it’s gray, quiet, and deeply entrenched. The same forces that benefit from political division benefit from healthcare opacity.

The Human Cost

My interoperability nightmare lasted months:

• Doctors who wouldn’t treat me based on false records
• Insurance denying coverage based on incorrect diagnosis
• Specialists afraid to contradict the “official” data
• Being told I might need to move states to escape my own medical history

But I’m not alone:

Every patient with:

• Misdiagnosis propagated across networks
• Medication allergies not properly verified
• Procedures billed but not performed
• Test results that “don’t match” their symptoms

Is trapped in the same system I was.

Interoperability promised to liberate patient data. Instead, it imprisoned patients in webs of false information they can’t escape.

Building the Alternative

This is why AENTE exists.

Not to build better interoperability in the traditional sense—we’re building verified interoperability.

Every data point includes:

• Cryptographic proof of origin
• Multi-party verification consensus
• Physical chain-of-custody when relevant
• Patient visibility and confirmation
• Jurisdiction-specific validation

The result:

• Geographic impossibilities (Texas MD in California) → Prevented by system logic
• Phantom services (billed but not delivered) → Prevented by multi-party verification
• Supply chain fraud (missing medications) → Prevented by physical item tracking
• Patient powerlessness → Eliminated by real-time transparency

We’re not political. We’re not ideological. We’re mathematical.

Fraud becomes thermodynamically expensive when every transaction requires cryptographic proof, multi-party consensus, physical verification, and patient confirmation.

Honest practice becomes the path of least resistance.

From Victim to Builder

I spent months trapped in a medical record system that said I was fine when I was severely injured. Told I might need to move states to escape false data about my own body.

That experience taught me: Interoperability without verification is worse than no interoperability at all.

At least with disconnected systems, errors are contained. With “seamless data exchange,” one lie becomes universal truth instantly.

The invisible cage I described in my previous blog? Interoperability built it. And locked it. And distributed copies of the key to everyone except the patient inside.

But cages can be broken—if we build technology that serves truth instead of convenience.

That’s what I’m building. Not because I believe in technology. But because I believe in accountability.

And accountability requires systems that can’t lie—no matter how seamlessly they exchange data.

---

Next in this series: “The Automation Apocalypse for Physicians—And How to Survive It”

AENTE is building verified interoperability—where every data point includes cryptographic proof, multi-party verification, and patient transparency. Born from experiencing interoperability failure firsthand, we’re creating systems where data exchange requires truth verification, not just data transmission. Learn how we’re making fraud thermodynamically expensive at www.aente.health

← Back to blog