Capacity
Engine 2 · Distributed Healthcare · Capacity · Capacity payment and transport

Capacity payment and transport

Standby capability funded directly, with transport as the funded backstop where a local unit cannot be sustained.

HealthcareArchitectureCoverageTransitionCapacityGovernanceLimits
Capacity overview

Coverage is universal from day one and never partial. What improves over time is the distribution of travel times — a mean, a spread and a tail — moved down by density and staffing. A distribution has no completion state, so access is never reported as a percentage complete. It is measured by condition and time to definitive care, and its honest milestone is the crossover year when as many sites open as close: net-negative today, and plausibly a twenty-year horizon. This clock runs separately from the transition, and for longer.

1 · Summary

Ambulance deserts — populated areas more than 25 minutes from an ambulance station — contain roughly 4.5 million Americans, about half of them rural though rural residents are 14% of the population. Eight Western and Plains states have fewer than three ambulances per 1,000 square miles.

The cause is payment design. Ambulance service is reimbursed only on transport, which cannot cover fixed cost where call volume is low and drives are long.

2 · Why this exists

This is a fee-for-service failure against a fixed-cost service. Health systems do not acquire ambulance services because the line is unprofitable, so rural EMS runs on volunteers.

Capacity payment fixes the category error rather than raising the price. A fire department is not funded per fire.

3 · How it works mechanically

Ground EMS receives readiness funding in addition to transport and treatment payment. Regional dispatch, mutual aid, medication, communications and clinical protocols follow. Roughly 11,500 existing rural agencies are stabilized in Year 1.

Air transport is brought under public or contracted-nonprofit operation on capacity payment. Helicopter EMS consolidated into for-profit operators that sited fleet capacity where reimbursement was rather than where need was, produced the worst surprise-billing category in American medicine, and carries a serious safety record with cancellation rates correlated to the weather that generates calls. The remedy is ownership and payment structure, not restriction of the indication.

Maternal and neonatal transport is core funded infrastructure, not a marginal intervention.

Where a local unit cannot be sustained — for financial reasons or because the clinicians left — transport is the funded backstop. The retrieval network, the designated receiving centre and its standing acceptance obligation are already in the bundle and already paid for. Degraded is not absent, and the two should not be described in the same words.

A catchment relying on transport reports as such: share of births beyond 30 minutes from surgical delivery capability, plus transport time to the receiving centre. That keeps the situation visible instead of letting a closure quietly become the permanent arrangement, which is how most rural obstetric loss has actually happened.

4 · Interactions with other healthcare components
Detailed mechanism pending v10.2 specification. The summary above is the canonical landing-page entry; deeper detail will be added as the v10.2 architecture cycle resolves the open specification work for this component.
5 · Cost and revenue
Detailed mechanism pending v10.2 specification. The summary above is the canonical landing-page entry; deeper detail will be added as the v10.2 architecture cycle resolves the open specification work for this component.
6 · Anti-cream-skimming and equity
Detailed mechanism pending v10.2 specification. The summary above is the canonical landing-page entry; deeper detail will be added as the v10.2 architecture cycle resolves the open specification work for this component.
7 · Quality and safety
Detailed mechanism pending v10.2 specification. The summary above is the canonical landing-page entry; deeper detail will be added as the v10.2 architecture cycle resolves the open specification work for this component.
8 · Workforce implications
Detailed mechanism pending v10.2 specification. The summary above is the canonical landing-page entry; deeper detail will be added as the v10.2 architecture cycle resolves the open specification work for this component.
9 · Patient experience
Detailed mechanism pending v10.2 specification. The summary above is the canonical landing-page entry; deeper detail will be added as the v10.2 architecture cycle resolves the open specification work for this component.
9.5 · Red-team
Strongest objection

Capacity payment invites thin service — collecting a fixed payment while running a minimal operation.

Mitigation

Real, and it requires audited staffing and readiness standards with clawback, at genuine administrative cost that partially offsets savings claimed elsewhere. Rate-setting across thousands of heterogeneous facilities is an unsolved administrative problem: the cost-report infrastructure does not exist in usable form.

10 · Open questions and v10.2 work

Honesty about gaps. Distributed Healthcare has more unresolved specification than other Engines because operational complexity is higher; the items below are flagged for v10.2 specification or for outside expert review.

  • Transport capacity must be sized as a contingency load rather than a steady state — when a unit closes, the receiving centre absorbs volume and the retrieval network absorbs transfers.