Why Digital Health Fails When It Tries to Skip the Middle Layer

May 06, 2026

10 min read

6 views

86%

The hidden question behind every health app

What if the real problem in digital health is not technology, but translation?

A prescription network that routes medicine efficiently across thousands of pharmacies sounds like a triumph of modern infrastructure. A mobile wallet that helps low-income patients save for care sounds equally promising. Yet in both cases, the hardest work is not building the digital tool. It is persuading a messy human system to trust it, use it, govern it, and sustain it.

That is why digital health so often arrives with grandeur and leaves behind a trail of pilots, dashboards, and half-adopted platforms. The usual story says innovation is held back by weak connectivity or limited funding. The deeper story is sharper: health systems do not mainly fail because they are analog, they fail because they are fragmented. Digital tools do not automatically fix that fragmentation. Sometimes they reveal it. Sometimes they intensify it. And sometimes they become a glossy layer on top of the same coordination problem.

The real puzzle is not whether digital health works. It is: what must already exist for digital health to become more than a temporary experiment?

The promise of direct connection is also its trap

The seductive idea in digital health is directness. A patient can reach a pharmacy through a network. A community worker can reach a clinic through a phone. A donor can reach data through a dashboard. A poor household can reach insurance through a mobile wallet. The pitch is always some version of the same dream: skip the friction, remove the middleman, connect people faster and more cheaply.

This is why digital health feels so aligned with the broader language of leapfrogging. If mobile money could sidestep banks, why should health financing not sidestep paper forms, cash handling, and slow bureaucracies? If phones made communication universal, why should they not also make care access universal?

But the promise of directness is also the trap. Health care is not a transaction in the narrow sense. It is a chain of dependencies: diagnosis, prescription, dispensing, payment, follow-up, regulation, trust, and sometimes social support. Remove too many intermediaries and you do not get efficiency, you get thinness. The system becomes faster at moving information, but not necessarily better at producing care.

A useful way to think about this is to distinguish between connection and coordination.

Connection means two points can exchange information.
Coordination means the exchange changes behavior across the whole system in a reliable way.

Digital health is very good at connection. It is much harder at coordination. A prescription can be routed electronically to a pharmacy network, but that does not automatically mean the clinic, pharmacy, insurer, patient, and regulator are aligned on what should happen next. A wallet can collect funds for care, but that does not guarantee the money can be used where it is needed, at the time it is needed, by the person who needs it.

Digital health often succeeds first as a channel, not as a system.

That distinction matters more than most policy discussions admit.

When innovation becomes a market, the system gets smaller

One of the most revealing tensions in digital health is this: projects often speak the language of universal coverage while behaving like market experiments.

That is not necessarily hypocrisy. It is structure. Many digital health initiatives are funded, evaluated, and scaled through a logic that rewards measurable uptake, investor interest, donor visibility, and quick proof of concept. In that environment, the project that looks most inclusive on paper may still serve a narrow segment in practice. It may be more valuable as a demonstration than as infrastructure.

This creates a strange inversion. The more a system is built to attract innovation capital, the more it may privilege what is testable over what is durable. A pilot can show impressive usage among early adopters, but fail to survive the boring realities that define public health: regulation, interoperability, reimbursement, maintenance, training, and political turnover.

Think of it like constructing bridges only for one festival. The bridge may be elegant, popular, and heavily photographed. But if it is not built into the road network, reinforced over time, and governed as public infrastructure, it will never become the ordinary route people rely on every day.

The same logic applies to digital health. Many projects are designed to be legible to donors and investors, which means they are optimized for:

Visible results instead of hidden resilience.
Short timelines instead of long institutional learning.
Scalable narratives instead of local fit.
Data extraction instead of system repair.

This is why some digital health ecosystems become surprisingly crowded and yet strangely brittle. They are rich in prototypes but poor in permanence.

The phrase “vibrant testing ground” sounds positive until you ask a harder question: testing ground for whom, and toward what end? A community can become a testing ground for innovation without ever becoming a site of lasting benefit.

The middle layer is not a bureaucratic nuisance, it is the real infrastructure

The most important insight buried in these examples is that the middle layer of health systems, the layer between a user and a platform, is not redundant. It is the actual mechanism by which care becomes reliable.

In the American context, electronic prescribing works at scale because it sits inside an established network used by most community pharmacies and office-based providers. That is not just a technical achievement. It is a governance achievement. Prescriptions can move across organizations because enough of the system shares standards, incentives, and infrastructure. The technology is useful precisely because it is not trying to bypass every intermediary. It is trying to standardize the middle.

That is a radically different model from the fantasy of direct digital access. In mature systems, the goal is not to eliminate institutions. It is to make institutions interoperable.

In many low- and middle-income settings, by contrast, digital health is often asked to do the opposite. It is expected to substitute for absent institutions, not complement them. A mobile phone becomes a clinic receptionist, a wallet becomes an insurer, a platform becomes a regulator, a dashboard becomes a planning office. This is a recipe for overloading the tool and underbuilding the system.

The result is a mismatch between technical ambition and institutional reality.

A better model is to think in three layers:

1. The access layer

This is the visible front end: phone, app, wallet, interface, prescription portal.

2. The coordination layer

This is the hidden middle: standards, reimbursement rules, referral pathways, identity verification, pharmacy workflows, data exchange agreements.

3. The legitimacy layer

This is the social and political base: trust, regulation, accountability, community acceptance, and public purpose.

Most digital health projects obsess over the access layer. Some manage to build part of the coordination layer. Very few pay enough attention to legitimacy. Yet without legitimacy, even the best-designed system is fragile. People may use it, but they will not fully rely on it.

That is why some platforms survive as islands while never becoming ecosystems.

Why “leapfrogging” can be a useful myth and a dangerous excuse

Leapfrogging is one of the most powerful ideas in development technology. It offers hope: countries do not have to repeat the same long, expensive path taken by richer nations. Mobile phones, mobile money, and off-grid energy all seem to prove that infrastructure can arrive in new forms.

But leapfrogging is often misunderstood. It does not mean skipping institutions. It means skipping one kind of hardware while still building the social, regulatory, and financial scaffolding that makes the new system reliable.

That is the missing piece in many digital health conversations. We celebrate the leap and forget the landing.

A mobile health wallet can look like leapfrogging because it avoids the old banking model. Yet if it depends on fragile connectivity, unclear rules, uneven reimbursement, and donor subsidies, it is not a leap to a stable future. It is a leap into dependency on another unstable layer. In that sense, digital health can replace one bottleneck with another: from queues and paper to platforms and pilots.

This is why older, non-digital solutions should not be treated as relics. Sometimes the most effective intervention is still the less glamorous one: transport vouchers, expanded staffing, clinic hours, local procurement, public insurance, or community health workers who already understand the social terrain.

The deeper principle is simple: do not confuse digitization with transformation.

Digitization changes the medium. Transformation changes the operating logic.

If a digital tool does not improve the operating logic of the system, it becomes a nicer interface on top of the same broken process. And sometimes it becomes worse, because it makes the failure look modern.

A practical framework: build for durability, not just adoption

If the goal is not merely to launch digital health, but to make it last, then the design question changes. Instead of asking “Can we get users?” ask “Can this become boring in the best possible way?” In infrastructure, boring is a compliment. It means dependable, routine, and taken for granted.

Here is a simple test for whether a digital health initiative is moving toward durability.

The Four Questions of Durable Digital Health

Can it survive without constant enthusiasm? If the platform needs endless hype, external funding, or charismatic champions, it is not yet infrastructure.
Can it interoperate with what already exists? If it requires a parallel universe of forms, workflows, or data standards, it is creating friction rather than reducing it.
Who bears the cost of failure? If patients, nurses, or local clinics absorb the burden when the system glitches, then the technology has merely relocated risk.
Does it strengthen public purpose, or just data visibility? Data transparency is not the same as accountability. A system can be highly measurable and still do little for access, quality, or equity.

These questions matter because digital health is often judged by the wrong metric. Adoption numbers can be impressive while resilience is absent. Pilot success can be real while long term sustainability is impossible. A project may scale geographically while shrinking in social usefulness.

The challenge is to design not for the first year, but for the fifth. Not for the demo, but for the handoff. Not for the donor report, but for the ordinary Tuesday when no one is watching.

The best digital health systems do not feel digital. They feel dependable.

Key Takeaways

Separate connection from coordination. A tool that links people is not automatically a system that aligns behavior.
Treat the middle layer as infrastructure. Standards, workflows, reimbursement, and governance matter as much as apps and devices.
Be skeptical of pilot theater. A successful trial can still be a failure if it cannot survive financing, regulation, and routine use.
Use digitization to strengthen public systems, not bypass them. The goal is interoperability and legitimacy, not shiny substitution.
Ask whether the tool creates durability. If it cannot function with low excitement and ordinary maintenance, it is not yet ready to carry care.

Conclusion: the future of digital health is less about phones than about institutions

The most misleading thing about digital health is that it looks like a technology story. In fact, it is an institution story.

A phone can reach across distance, but it cannot manufacture trust. A platform can gather data, but it cannot on its own create coordination. A wallet can hold money, but it cannot guarantee treatment. What turns digital tools into real health infrastructure is not innovation alone, but the slow, unglamorous work of building standards, accountability, and shared purpose around them.

That is the deepest lesson hidden in both mature prescription networks and experimental mobile health platforms. The future does not belong to the systems that move fastest. It belongs to the systems that can make new tools ordinary without making care fragile.

So the next time a digital health project promises to leap over old constraints, ask a better question: what middle layer is it strengthening, and what middle layer is it pretending does not matter?

The answer will tell you whether you are looking at the beginning of a real health system, or just another impressive pilot.