Article — Position paper · ○ Open access

Four dimensions, one arbitration layer

Under operational constraint, the orchestration layer does not merely render distributed care, place, time and cost comparable: it renders certain trajectories calculable and others invisible.

Jérôme Vetillard · · Twingital Institute · 10 pages · 9 min read
🇫🇷 Lire en français ↓ Download PDF

The thesis in one sentence: four sliders, or one parameterization layer?

The hospital that steps outside its walls presents itself with a compact promise, imported from the vocabulary of value-based care: the right care, in the right place, at the right time, at the right cost. The formula is serious, and its inscription in the real is no slogan. French hospitalisation à domicile treated 184,400 patients in 2024 (ATIH), medical telesurveillance entered mainstream coverage through the decrees of 3 and 31 March 2026 (HAS, Légifrance), and British virtual wards counted close to 11,635 beds by March 2025 (NHS England). Distributed care exists, works, and keeps part of its promise.

But the promise rests on a presupposition it never names: that its four rights are separate objectives, which one could tune one by one, like four independent sliders. This text defends the opposite thesis. Right care, right place, right time, and right cost are not four sliders. They are four effects of one and the same parameterization layer, and the mechanism that produces them is not arbitration between competing objectives. It is deeper, and less visible: under operational constraint, the orchestration layer constitutes the space within which these objectives become calculable.

From Triple Aim to Quintuple Aim: the genealogy of a separable promise

The genealogy of the formula is well known. It descends from the Institute for Healthcare Improvement’s Triple Aim (better population health, better care experience, controlled cost), extended into the Quadruple Aim by Bodenheimer and Sinsky in 2014 (adding clinician well-being), then into the Quintuple Aim by Nundy, Cooper and Mate in 2022 (adding equity). Market discourse reformulated it as an orchestration imperative: a performant system would be one that orchestrates interoperable data, digital clinical programs, access experience, and payment structures.

Presented this way, the four rights look like a dashboard. Four dials, four dimensions of value, a pilot who adjusts at the margin. The metaphor reassures because it presupposes the dials independent: one would pull on cost without deforming care, advance the moment without displacing the place, and the only difficulty would be one of weighting. It is false, and for a technical, not ideological, reason. The four rights do not live in the same measurement space, and that space is not given in advance.

Why each “right” depends on a perimeter of observability, not on a fact of the world

Let us pose the question the promise sidesteps: what defines “right,” and on what does that definition depend? The right care is defined relative to an observed need, and need is not observed in itself: it is inferred from what the system captures. A degradation emitting no instrumented signal is not a need for the system; it is a silence. The right place is defined relative to a map of resources, and that map is not neutral: it references what is contracted, instrumented, connected. The right time is defined relative to a detection, hence to a threshold and a sampling frequency. The right cost, finally, is defined relative to a perimeter of counted costs: a cost just over a narrow perimeter, the avoided day, may be unjust over the full pathway, the deferred readmission.

None of these four perimeters is a fact of the world. All are fixed by the parameters of orchestration. Hence a distinction the dashboard erases: that between the objective and the measurement space in which the objective is defined. Optimizing an objective presupposes a stable measurement space. Yet the measurement space of distributed care is not stable: it is itself a product of parameterization. Metrology has known this for a long time. What changes here is not the principle but the scale. No longer an isolated instrument in a laboratory, but a continuous clinical orchestration, under constraint, over an entire population, with direct consequences for patient addressability.

Five runtime forces that manufacture visibility under constraint

If this shared decision space were only a static projection, it would remain a conceptual elegance. The decisive point lies elsewhere: in execution, under constraint, the measurement space is not built once, it is continuously reduced, deformed, recomputed. It is not a projection. It is a dynamic compression. Five runtime forces perform this compression, none of which appears on the dashboard.

First, the feedback loop: what the system rendered visible yesterday conditions what it can detect today, and a class underrepresented in the history remains underdetected in the present. Second, the recalibration temporality: between two recalibrations, the system measures the present with the measurement space of the past. Missing data is not a neutral hole in a matrix, it is a trajectory that exits the field. Capacity dependence makes routing follow capacity as much as need: when the downstream bed is missing, the effective escalation threshold shifts, whether or not the written rule says so. Finally, saturation does not uniformly tighten priorities, it reconfigures them: the same modeling that, in nominal regime, jointly optimizes triage, staffing, and beds produces, under saturation, a different hierarchy. Hospital-operations digital twins in this line claim emergency-department wait-time reductions of 20% to 40%, figures with strong vendor coloration that hold as an indicator of operational efficiency on the measured observable rather than as consolidated proof.

A clinical scene: saturation displaces the threshold without any written rule

A heart-failure patient is monitored at home by telesurveillance. One evening, the downstream beds of the reference cardiology unit are saturated. No written rule states it, but the effective escalation threshold rises: for lack of a place to refer to, the system reclassifies as “stable” what it would, in nominal regime, have flagged as “to be monitored.” The patient’s weight and heart-rate variations remain beneath the threshold thus displaced. No alert fires. The patient is not poorly monitored: they are correctly monitored in a measurement space that has tightened, without anyone having decided so. Decompensation arrives a few days later. Late. One will conclude it was not predictable. It was. The trajectory had simply never become calculable.

The system did not observe a stable patient: it instituted the patient’s stability, as a side effect of a capacity constraint. This is the hardest point in the text, and it lends itself to two misreadings that must be set aside. It is not the sociotechnical commonplace that every system shapes what it measures: here the object shaped is not the measurement, but the set of trajectories that become clinically actionable. Nor is it a constructivism denying the real: the patient’s degradation is real, what the system constitutes is its calculability, that is, whether it becomes an object of decision. Tuning a threshold does not move a value on the scale, it moves the scale itself.

Pareto front and endogenous measurement space: the engineer’s objection

The objection must be given its full force. An engineer will say that all of this is a multi-objective optimization problem already solved: a Pareto front handles competing objectives with explicit trade-offs, and sharing sensors is not sharing an objective. The objection is correct on its own terrain, and it is the terrain that is in question. A Pareto front presupposes objectives defined on a stable measurement space. Here, the space is endogenous to the optimized parameters: moving a threshold moves both the objective’s value and the set of trajectories over which that value is defined. One does not arbitrate on a fixed front, one deforms the front by moving along it.

The terrain of this text is the hospital outside its walls, but the mechanism is in no way specific to hospital-at-home. The same layer governs emergency-room triage, waitlist prioritization, imaging routing, primary-care to hospital coordination, remote monitoring platforms, oncology coordination, critical-flow management. Wherever a distributed clinical architecture arbitrates under constraint, it manufactures the observable before measuring it.

The cost of non-observation: non-detection, non-escalation, non-reconstructibility

Once it is granted that the layer manufactures the observable, “right cost” changes nature. It is not a financial quantity measured after the fact. It is pre-inscribed in the thresholds, routes, priorities, and filters that decide who will be seen, when, where, and with what level of escalation: a clinical arbitration prior to any measurement. What remains is to count a cost that classical economic analysis does not know how to see, because it bears on what the system did not observe. It is not a bag in which to dump every negative externality. It has a causal structure in three stages that follow the path of a signal.

First stage, the cost of non-detection: the degradation that never crossed the threshold, or crossed it too late. A claimed sensitivity above 80%, consistent with a literature predominantly North American on remote monitoring, leaves at most one degradation in five beneath the threshold, and visibility delay belongs to the same stage: a detection arriving after the point where it would have changed the outcome is a non-detection unaware of itself. Second stage, the cost of non-escalation: the detectable trajectory that the system did not escalate, for lack of downstream capacity or because saturation had reconfigured priorities. Third stage, the cost of non-reconstructibility: after an unfavorable outcome, the impossibility of reconstituting which parameters tipped the trajectory. The error becomes an event without assignable cause.

An awkward fact in the data illuminates this. A systematic review of hospital-at-home care (2018 indexed prices) reports differences ranging from savings of more than €8,000 to additional costs of more than €2,000 per patient. Case-mix explains part of the dispersion, but it does not predict a change of sign. An independent cost slider would produce a tight distribution around an average saving; what one observes is a swing, consistent with a cost that emerges from local parameterization rather than one piloted as an autonomous quantity. Consistent is not proven: the thesis remains structural.

Four engineering requirements for an execution-grade governance

This observation does not call for denunciation. It requires an engineering discipline, in four design requirements. First, the arbitration function must be explicit and inspectable: an unreadable objective function does not suppress the clinical decision, it renders it unassignable, and soon irreconstructible as a clinical act. The problem is not the absence of decision, it is the loss of its author. Second, the perimeter of observability must be declared in the specification, including the missing-data policy and the recalibration temporality: a system that conceals how it handles data absence conceals half of what it decides. Third, every cost or capacity lever must be traceable to its effect on the observable, failing which tuning becomes an unqualified clinical act. The doctrinal corpus this text extends names this requirement enforceable executory qualification, which places a function with clinical effect among clinical functions and not among technical utilities. Fourth, tuning must be reconstructible: not recording everything, but being able to replay a trajectory together with its parameters and the state of saturation in which it played out. A log attests that things happened, it does not say how they were rendered calculable. Reconstruction is not logging.

The more a system performs on its observable, the less the cost of what it does not observe is reconstructible. The efficiency curve and the silence curve can rise together. An orchestration system can genuinely improve its indicators, fewer readmissions, shorter lengths of stay, as some North American programs claim, while increasing the share of trajectories it does not render calculable.

Domain of validity, explicit falsifier, and what the thesis does not entail

Three limits bound what this analysis authorizes one to conclude. It is structural, not empirical: platform arbitration functions are proprietary, and no direct evidence of the mechanism is produced here. Hence the falsifier, which serves as guardrail: the thesis falls if one exhibits, in a real architecture, a cost or capacity lever whose modification leaves the distributions of access, routing, and escalation invariant. If the observable does not move when one reparameterizes, it is not manufactured, and the analysis is wrong.

It holds only under constraint: a well-instrumented system, at ample capacity, recalibrated often, manufactures little differential visibility. The thesis bites as distribution, constraint, and recalibration debt increase. It describes finally a tendency, not a fatality: that the layer institutes the observable does not require doing so in silence. This is the entire purpose of the four requirements.

Conclusion: what a system cannot render calculable, it eventually ceases to treat

The promise of the four rights is tenable, though not necessarily in the terms in which it formulates itself. It presupposes four independent sliders; it operates through a single layer that, under constraint, decides what becomes calculable. The true subject of distributed care is neither cost, nor place, nor time, nor quality: it is the manufacture of the observable, which trajectories a system knows how to render visible, and at the cost of what invisibility for the others.

So long as this manufacture remains implicit, the efficiency measured after the fact will appear neutral. It is not: it measures only what the layer was willing to render observable. The rest figures in no dashboard, it becomes a blind spot, then an out-of-perimeter item, without anyone having had to decide it should be so. What a system cannot render calculable, it eventually ceases to treat, for lack of ever having decided to. Making this mechanism explicit is not a moral demand: it is the first technical specification of a distributed care for which one could still answer.

Read the document