Interoperability Challenges: Why Everyone Agrees — and Nothing Connects

On a Saturday morning in a Caribbean marketplace, everything appears independent.

The fish vendor calls out his prices. The woman selling callaloo arranges her bundles. The spice merchant measures by instinct. The fruit seller negotiates with a regular customer. Each stall is its own enterprise.

But look closer and you see something else.

The market works because it is coordinated. There are shared rhythms. Shared rules. Shared expectations. The fisherman knows when the boats arrive. The vendor knows which produce will be ready in season. Prices move in relation to one another. Customers walk from stall to stall without confusion because the ecosystem — though informal — is integrated.

No one stall runs the market.
But the market only works because everything connects.

Caribbean digital health, on the other hand, too often resembles the market without the shared rhythm.

Ask any Caribbean health leader whether interoperability matters and the answer is immediate: yes. Ask what is actually interoperable today — and the conversation becomes cautious.

We have platforms. We have surveillance systems. We have laboratory information systems. We have claims systems. We have pharmacy software. We have electronic medical records.

What we do not consistently have is connection.

This gap between agreement and execution is not accidental. Interoperability sounds technical. In reality, it is political. It forces systems to confront power, standards, transparency, and autonomy — all at once.

That is why so many systems talk about interoperability while quietly designing around it.

Interoperability Is Not a Feature — It Is a Decision

Interoperability is often described as something software will eventually deliver: APIs, interfaces, data exchange modules. But software does not decide to connect. Systems do.

In many Caribbean jurisdictions, multiple electronic health records operate in parallel. Laboratories send PDFs instead of structured data. Pharmacy systems do not communicate with prescribing platforms. Claims systems operate blind to clinical context. Public and private providers function in digital universes that rarely intersect.

The technology to connect these systems exists.

What is missing is authority to require connection.

In the marketplace, no one can simply refuse to use the common currency. In digital health, we allow that refusal daily — in the name of autonomy, vendor preference, or convenience.

Ask any Caribbean health leader whether interoperability matters and the answer is immediate: yes.

Ask what is actually interoperable today — and the conversation becomes cautious.

Why Small Systems Struggle More, Not Less

There is a persistent belief that small systems should find interoperability easier. Fewer hospitals. Fewer vendors. Fewer moving parts.

In practice, small Caribbean systems face a different reality.

Vendor leverage is stronger when markets are small. Technical capacity to build custom integrations is limited. Informal coordination — phone calls, personal relationships, WhatsApp messages — compensates for structural gaps. And political sensitivity around private sector independence makes mandates uncomfortable.

Fragmentation persists not because leaders disagree on the goal, but because no one wants to force the first standard.

Every stall optimises locally. The market suffers globally.

The Barriers We Rarely Name

Interoperability exposes dynamics that are easier left unexamined.

Vendor lock-in is often reframed as “stability.” Platforms are selected because they work internally. Data export or structured exchange is postponed to a later phase. That later phase rarely comes. Vendors are rational. Without contractual or regulatory requirements, interoperability is a cost center — not a priority.

Visibility creates discomfort. Interoperability makes utilisation patterns visible. It reveals duplication. It surfaces referral delays. It exposes variation in practice. In systems where informal workarounds have held things together, that transparency can feel threatening.

Avoiding interoperability becomes a way of avoiding accountability.

Governance fragmentation compounds the issue. Public systems digitise one way. Private providers digitise another. Insurers build their own platforms. No single authority governs exchange rules. Integration becomes negotiation, not obligation.

And then there is identity — the quiet foundation of everything. Without reliable patient and provider identification, data exchange becomes unsafe. Many Caribbean systems still rely on inconsistent identifiers or demographic matching. This is not a software problem. It is a governance decision deferred.

Interoperability does not require perfection. It requires discipline.

Fragmentation Is No Longer Harmless

There was a time when fragmentation was merely inefficient.

Now it is dangerous.

As telemedicine expands, as AI-supported diagnostics emerge, as digital pharmacy systems scale, as regional data exchange becomes plausible — fragmentation multiplies cyber risk, increases clinical error probability, and complicates accountability.

You cannot secure what you cannot clearly map.
You cannot govern what you cannot see.

Cybersecurity and interoperability are inseparable. One depends on the other.

What Interoperability Actually Requires

Interoperability does not require perfection. It requires discipline.

It requires mandating data standards through procurement — not suggesting them politely. It requires contractual obligations for data export and API access. It requires selecting vendors not only for feature sets, but for their willingness to connect.

It requires defining minimum viable interoperability: patient identity, medications, laboratory results, discharge summaries, referrals. Not everything at once. The flows that matter.

It requires separating system ownership from data governance. Providers may own their platforms. Patients have rights to their data. The system must define exchange rules. Without that distinction, every integration becomes a negotiation.

And it requires shared services — identity registries, terminology services, exchange layers — rather than bespoke interfaces built and abandoned one by one.

In the marketplace, everyone uses the same weights and measures. Digital health requires the same clarity.

The Caribbean Opportunity

Ironically, our constraints create an advantage.

Populations are small. Provider networks are finite. Care pathways are known. We are not trying to connect infinite complexity. We are trying to connect repeatable flows:

• Overseas referrals.
• Shared laboratories.
• Medication continuity.
• Claims validation.

These are not abstract ambitions. They are solvable design problems — if we are willing to decide.

The Decisions We Keep Postponing

Interoperability will not advance until leaders answer uncomfortable questions:

• Who has authority to mandate standards across sectors?
• Which data must be shared — and under what conditions?
• How will patient identity be resolved nationally?
• What happens when a vendor cannot comply?
• How will transparency be used — for improvement or punishment?

“Alignment” is not enough. Collaboration without rules becomes delay.

Interoperability requires enforcement. And enforcement requires courage.

In the Caribbean marketplace, no one stall can thrive if the pathways between them collapse. The fish vendor depends on the produce seller bringing customers. The spice merchant depends on steady foot traffic. The ecosystem is interdependent.

Digital health is no different.

Interoperability is not about connecting software. It is about deciding that we are building a system — not a collection of stalls.

The region does not lack technology. It does not lack intelligence. It does not lack consensus.

What it has lacked, so far, is the willingness to decide — and to enforce.

Because in digital health, what does not connect does not remain independent.

Eventually, it simply breaks.