The transition is accelerated to 4–6 years (down from earlier 7–10 year framings) but remains strictly capacity-gated. Phase 0 (Months 0–9) builds infrastructure before any patient transitions. Phases 1–4 enroll populations on a schedule that prioritizes the largest coverage gap (uninsured) first and back-loads the most politically sensitive groups (Medicare) for safety. No phase proceeds if it degrades access, wait times, or quality.
The nine-month preparation phase that precedes any patient enrollment. The capacity-first principle requires that infrastructure exists before populations are transitioned; Phase 0 builds that infrastructure. Provider RFI/RFQ identifies Kaiser-style integrated providers; payment systems and claims rails are stress-tested; VHA capacity is assessed facility-by-facility; financial-distress monitoring on rural hospitals is activated.
No patient enrollment occurs during Phase 0. The architecture's commitment is that infrastructure precedes population — the failure modes of universal-coverage rollouts are typically infrastructure gaps that surface only after enrollment begins.
Universal-coverage rollouts that have failed at scale (state-level Medicaid expansions with capacity shortfalls, the ACA exchange launch in 2013, certain provincial Canadian Medicare rollouts) typically failed because capacity, IT infrastructure, or operational coordination was insufficient at the moment population enrollment began. The architectural lesson: build infrastructure before enrolling populations.
Phase 0 is the architecture's structural commitment to that lesson. Nine months between enactment and Phase 1 patient enrollment provides time for facility-by-facility capacity assessment, provider contracting at scale, payment-system stress-testing, and the operational rehearsal that catches failure modes before they affect patient experience.
The duration (Months 0–9) is calibrated to allow the work without artificially delaying patient enrollment. Shorter would compress capacity assessment to surface-level; longer would delay the populations who most need coverage.
Phase 0 has six parallel work streams that coordinate through AHQB and a federal Phase 0 Operations Office.
Capacity mapping. AHQB conducts a facility-by-facility capacity assessment of the existing federal delivery infrastructure (172 VHA medical centers, 1,138 outpatient sites) plus a national assessment of contracted private capacity that could be brought into Distributed Healthcare. Specialty-specific capacity is assessed separately from total capacity (some specialties have headroom; others — cardiology, certain surgical specialties — are constrained earlier). Per-facility intake caps for non-veteran civilians are established before Phase 1 begins.
Provider contracting via RFI/RFQ. The Kaiser-style integrated provider organizations that will serve regions where direct federal operation doesn't fit are identified through formal RFI/RFQ processes. Multi-region service commitments are required (preventing geographic cream-skimming at contract origination). Capacity-payment terms are negotiated. AHQB approves contracted designs before Phase 1.
Telehealth network launch. The national telehealth network for primary-care + mental-health delivery launches operationally in Phase 0. Provider onboarding, technology platform stress-testing, payer-rail integration, and patient-facing UX testing all happen before Phase 1 enrollment. By the start of Phase 1, telehealth is a working channel, not a planned channel.
Mobile-health deployment. Mobile clinics for underserved geographies begin deployment in Phase 0. Initial focus on rural maternity deserts, frontier emergency-services gaps, and urban primary-care deserts identified via COMPASS measurement. The mobile fleet doesn't reach full deployment in Phase 0 but reaches operational launch — Phase 1 enrollment can route patients to mobile clinics from Day 1.
VHA capacity assessment. The detailed Phase 0 work product. Each VHA medical center and outpatient site receives an intake-capacity figure, broken down by specialty, with quarterly re-assessment scheduled. The capacity figure is the binding cap on Phase 1 non-veteran enrollment at that facility.
Hospital-distress monitoring. Rural and at-risk hospitals are placed under continuous financial-distress monitoring per AHQB indicators. Phase 0 establishes the monitoring infrastructure; Phase 1 begins triggering capacity-payment stabilization or federal takeover where the indicators flag closure risk.
Payment-system + claims-rail testing. The federal payment infrastructure (FedCard for benefits delivery, claims-rail for provider reimbursement) is stress-tested at scale before Phase 1 enrollment. End-to-end testing covers enrollment, eligibility verification, claim submission, payment authorization, and dispute resolution.
- VHA expansion
- Phase 0 capacity assessment defines the per-facility intake caps that govern Phase 1 non-veteran enrollment.
- Hospital takeovers
- Phase 0 distress-monitoring activation is the input to Phase 2 takeover triggers.
- Telehealth + mobile
- Phase 0 launches operational delivery; Phase 1 begins patient enrollment onto these channels.
- Kaiser-style providers
- Phase 0 RFI/RFQ produces the contracted designs that Phase 2 ramps to operational scale.
- AHQB
- Phase 0 establishes AHQB's monitoring infrastructure and pre-approval pipeline that operate continuously through Phases 1–4.
Phase 0 costs are infrastructure investment — capacity assessment teams, RFI/RFQ procurement processes, telehealth and mobile-health initial capital, payment-system development. These are non-trivial (likely tens of billions over the nine-month window) but bounded; the return is operational readiness for Phases 1–4.
The architectural commitment: Phase 0 is paid from the federal general fund as enactment-cycle appropriation, not from payroll tax revenue (payroll tax collection doesn't begin until Phase 1 employer cutover starts in Phase 2). This preserves the architecture's revenue-side timeline while allowing infrastructure investment to precede revenue collection.
The fundamental quality protection: no patient is enrolled during Phase 0. Quality-degradation risk during Phase 0 is zero by construction — patients are still in their existing coverage arrangements until Phase 1 begins. The work that does happen (capacity assessment, contracting, infrastructure testing) has no patient-care interface until validated.
This is the architecture's strongest protection against the "rollout begins, infrastructure isn't ready, quality degrades" failure mode. Phase 0 buys nine months of infrastructure work before any patient is at risk.
Phase 0 is workforce-build phase. Federal hiring at AHQB (Phase 0 Operations Office staffing), VHA (clinician hiring + residency-program expansion), and Kaiser-style contractor organizations (workforce build under contracted terms). The architecture's training-pipeline acceleration begins in Phase 0 — accelerated residency-position growth, allied-health training expansion, and Skills Wallet retraining for displaced insurance-industry workers (early-mover insurance employees who see the writing on the wall and choose retraining ahead of Phase 3–4 displacement).
Patients experience nothing in Phase 0. Existing coverage arrangements continue without change. The architecture's commitment to patient communication is to inform — public-facing communication about the timeline, what changes when in subsequent phases, what to expect, where to ask questions — without creating false expectations of immediate change.
Nine months is too long to wait. Public attention spans are short; political momentum decays. By the time Phase 1 begins, the political coalition that enacted Distributed Healthcare may have weakened, and the rollout may face resistance that wasn't present at enactment.
Phase 0 is the architecture's commitment to operational reality over political momentum. The alternative — beginning patient enrollment immediately on enactment, before infrastructure is ready — is the failure mode that has destroyed prior universal-coverage attempts. The 2013 ACA exchange launch failure is the canonical example: rushing to patient-facing operations before infrastructure was ready produced the most visible early-stage failure of any major US program in recent memory.
The architecture's commitment to public communication during Phase 0 (what changes when, what to expect, where to ask questions) maintains political momentum without compromising operational readiness. Phase 1 — when 27 million currently-uninsured Americans gain coverage in a single year — is itself a major political event that re-energizes the coalition. Phase 0 is the price paid to make Phase 1 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.
- Phase 0 Operations Office governance: where it sits in the federal organization chart and how it coordinates with AHQB is pending v10.2 specification.
- Telehealth-network operating model: federal-direct vs. contracted vs. hybrid for the national telehealth backbone is pending.
- Hospital-distress indicator thresholds: the specific financial metrics that flag closure risk vs. ordinary stress are pending v10.2.