The Hidden Economics of Shared Information: Why Good Systems Fail When They Stop at the Border

May 05, 2026

10 min read

5 views

84%

What do patient summaries and vaccination policy have in common?

At first glance, almost nothing. One is about a compact medical record that can move across hospitals, regions, and countries. The other is about the economics of immunization, with its thorny questions of incentives, public intervention, and social cost. But both are really about the same problem: how to make decisions in a system where the benefits of one actor’s action spill over to everyone else.

That is the uncomfortable truth beneath both topics. A patient summary is not valuable because it contains everything. It is valuable because it contains the right minimum information at the moment a new clinician needs to act. Vaccination is not valuable only because it protects the vaccinated person. It is valuable because it changes the risk landscape for everyone around them. In both cases, the challenge is not just creating something useful in theory. The challenge is aligning private behavior with public value when the value lives partly outside the individual decision-maker.

The deepest systems failures happen when the person who pays the cost is not the same person who receives the full benefit.

That sentence connects digital health interoperability and vaccination economics more tightly than it may first appear. One deals with information, the other with biology. Yet both reveal a general law of coordination: when benefits are shared but costs are local, good systems need more than goodwill. They need design.

The illusion of completeness

A common mistake in system design is to assume that more information, more intervention, or more detail automatically produces better outcomes. The opposite is often true. The International Patient Summary works precisely because it is minimal and not exhaustive. It does not try to preserve every lab value, note, or historical oddity. It prioritizes the essentials: medications, allergies, problems, and other critical facts needed during a care transition.

That restraint is not a weakness. It is the design principle.

Imagine a physician in another country trying to treat a traveler who arrives in the emergency room. A 200 page chart would be useless if the clinician needs to know, in the next 30 seconds, whether the patient is allergic to penicillin, what medications they are taking, and whether they have a chronic condition that changes the treatment plan. In that moment, selective clarity beats total recall. The patient summary is not a warehouse of data. It is a decision aid.

Vaccination policy has the same hidden constraint. The naive question is, “How do we get everyone vaccinated?” But that is too blunt. The real question is: vaccinated in what population, against what disease, with what vaccine, under what costs, and with what social structure? The economics of vaccination turns out to depend delicately on context. Population characteristics matter. Disease dynamics matter. Vaccine availability and efficacy matter. A policy that looks optimal in one setting can be inefficient or even counterproductive in another.

This is the first shared lesson: systems that touch many people cannot be governed by simplistic maximization. They require a theory of what matters most under uncertainty, constraint, and coordination failure.

Borders are where value is lost

The phrase “international patient summary” sounds like something designed for passports and customs desks. But the real importance of the IPS is broader. It is built for any care transition, especially the moments when a person moves from one clinical context to another. That might be from one country to another, but it might also be from a primary care office to a specialist, or from one hospital information system to another across town.

Those are not just administrative borders. They are points where information gets degraded, delayed, or lost.

Think of a border like a river crossing. If there is no bridge, every traveler must improvise. Some carry detailed paper records. Some rely on memory. Some arrive with nothing. The result is not only inconvenience, but risk. The clinician may repeat tests, miss allergies, prescribe interactively dangerous medications, or waste precious time reconstructing history. The problem is not a lack of data somewhere in the world. The problem is that the data has failed to arrive where the decision is being made.

Vaccination faces an analogous border problem. The benefits of immunization spill beyond the individual. When enough people vaccinate, transmission drops, vulnerable groups are protected, outbreaks are contained, and the whole social environment becomes safer. But those benefits are not fully captured by the person deciding whether to vaccinate. The result is a familiar economic gap: private incentives can understate social value.

That is why the case for public intervention is strong in principle, but also subtle in practice. It is not enough to say vaccines create positive external effects. One must ask how large the externality is, what the costs are, what constraints exist, and how behavior changes as coverage rises. A simplistic policy can overshoot, undershoot, or misallocate resources if it ignores the local structure of the problem.

So in both domains, the border is where value is lost. In health records, value is lost at the boundary between systems. In vaccination, value is lost at the boundary between private choice and collective welfare.

The real unit of design is not the individual, but the transition

This is the most useful frame for connecting the two ideas: the transition is the unit of design.

Traditional thinking often starts with the individual object. The record, the vaccine, the patient, the policy. But the hard part is not the object in isolation. It is what happens when the object must move, scale, or interact.

The patient summary matters because patients do not live inside a single hospital system. They move. Their care crosses organizational borders, and the relevant information must move with them. Similarly, vaccination policy matters because disease does not stay inside individual bodies. It moves through contact networks. A person’s choice affects the exposure environment of others.

This suggests a broader mental model: every system with spillovers has to solve a translation problem.

Translation can mean moving information from one record format to another, which is why standards like ISO 27269, CDA, FHIR, SNOMED CT, and document compositions matter. But translation also means converting private choices into socially intelligent behavior, which is why economics, incentives, subsidies, mandates, and public communication matter. In both cases, the core task is to make local action legible and useful at a larger scale.

A useful analogy is a well-run airport. Security, ticketing, baggage handling, and gate operations are different subsystems with different technologies, but passengers experience them as one continuous journey. If one handoff fails, the entire travel experience collapses. Similarly, healthcare interoperability is not just about storing data. It is about creating a reliable sequence of handoffs. Vaccination policy is not just about dosing individuals. It is about creating a reliable sequence of protective effects across a population.

Good systems do not merely optimize parts. They protect the handoffs between parts.

That is why minimal standardization can be more powerful than total centralization. The IPS does not need to know everything to be useful. It needs to ensure that the right essentials survive the handoff. Vaccination policy does not need to control every decision to be effective. It needs to nudge, enable, or require enough participation that collective protection emerges.

The ethics of minimum necessary completeness

There is a temptation in both medicine and policy to equate ethical seriousness with comprehensiveness. If some information is good, more must be better. If some intervention helps, stronger intervention must help more. But real systems punish this instinct.

The patient summary embodies minimum necessary completeness: enough information to support safe care, but not so much noise that the receiving clinician is overwhelmed. This is an ethical as well as a technical principle. Too much data can hide the signal. Too little data can endanger the patient. The art lies in knowing what is essential at a moment of transition.

Vaccination economics has an ethical parallel. Since the social cost of disease includes more than direct medical expenses, policy must account for broader harms. But it also must avoid treating all interventions as if they are equally justified in every setting. A public health tool can be valuable without being universally appropriate in identical form. Ethical policy is not a blunt moral gesture. It is a calibrated response to the actual structure of risk.

This leads to a more mature view of intervention. The question is not, “Should society act?” The question is, what level of coordination best internalizes the externality while respecting context, cost, and feasibility?

That question matters because systems fail in two opposite ways. One failure mode is undercoordination, where every actor optimizes only for themselves and the shared system frays. The other is overcoordination, where the system becomes bloated, rigid, or intrusive and loses usability. The patient summary guards against the first by making transition safe. Vaccination policy guards against the first by making collective protection possible. Both also warn against the second by reminding us that effective design depends on restraint and context.

A practical framework: four questions for any spillover problem

If you want a single model that unifies these ideas, use this four question test whenever a decision creates benefits beyond the decision-maker:

What is the transition? Identify where value is most likely to be lost. Is it a care handoff, a border crossing, a change of system, or a behavioral threshold in a population?
What is the minimum essential signal? In records, this is the critical clinical summary. In policy, this is the core incentive or intervention that changes behavior without unnecessary complexity.
Where are the externalities? Ask who benefits and who bears the cost. If the same person does both, markets and individual choice may work well. If not, coordination or public intervention may be needed.
What is the smallest effective bridge? Do not solve the whole problem at once. Build the lightest mechanism that preserves value across the boundary. For patient records, that may mean a standardized summary. For vaccination, that may mean subsidies, reminders, mandates in specific contexts, or targeted outreach.

This framework is powerful because it shifts the question from “How do we maximize?” to “How do we preserve value across a boundary?” That is a much more realistic lens for complex systems.

Here is a concrete example. A person with diabetes travels from one region to another and visits an unfamiliar clinic. The receiving physician does not need the entire history of every appointment the patient ever had. They need enough to avoid dangerous errors and continue care. Now compare that with a seasonal flu campaign in a city where uptake is uneven. The policy goal is not merely to vaccinate abstractly. It is to reduce transmission in the right subpopulations, protect the vulnerable, and avoid wasting scarce resources. In both cases, the smartest move is not maximum volume. It is strategic continuity.

Key Takeaways

Look for spillovers first. If the value of an action extends beyond the actor, default solutions based only on individual choice or complete data are likely insufficient.
Design for transitions, not totals. The most important unit is often the handoff, not the static object. Ask what must survive the move from one setting to another.
Use minimum necessary completeness. More information or stronger intervention is not automatically better. Identify the smallest useful set of signals or actions.
Match policy to context. The optimal response depends on population structure, disease dynamics, system capacity, and the real cost of coordination.
Protect the bridge. In complex systems, the interface is where failures become expensive. Standardization, incentives, and workflow design should focus there.

The deeper lesson: systems are judged by what crosses between them

The most interesting thing about both the patient summary and vaccination economics is that neither is really about the thing itself. One is about records, the other about shots. But in both cases, the true test is whether value survives movement across a boundary.

A patient summary proves its worth when a stranger can safely treat you. A vaccine policy proves its worth when a person’s decision contributes to a healthier community, not just a healthier self. In both cases, success is measured not by local elegance but by cross-boundary reliability.

That is a useful way to rethink many modern problems. We often obsess over collection, scale, and completeness. But the real question is simpler and harder: what happens when one part of the system depends on another part it does not control?

If you can answer that well, you can design better health records, better vaccination strategies, and probably better institutions overall. Because in the end, the highest-performing systems are not the ones that contain the most. They are the ones that lose the least when value has to travel.