Capacity
Engine 2 · Distributed Healthcare · Capacity · Kaiser-style integrated provider organizations

Kaiser-style integrated provider organizations

Where direct federal operation doesn't fit, RFI/RFQ contracts with integrated provider organizations (Kaiser, Geisinger, Intermountain, Mayo) deliver care on capacity-payment terms.

HealthcareArchitectureRolloutCapacityGovernanceTransitions
Capacity overview

Universal coverage requires capacity to deliver it. The architecture builds capacity through four channels: VHA expansion to non-veteran enrollment where headroom exists; rural hospital stabilization or takeover when fee-for-service economics fail; telehealth and mobile health for geographic reach; and Kaiser-style integrated provider organizations under capacity-payment contracts where direct federal operation doesn't fit.

1 · Summary

Where direct federal operation isn't the right fit — regional culture, existing strong physician networks, established integrated systems — the architecture contracts with integrated provider organizations on Kaiser-Permanente-style capacity-payment terms. The provider organization handles the full clinical operation (primary, specialty, hospital, ancillary services); Distributed Healthcare pays per enrolled life with statutory quality, access, and anti-cream-skimming requirements.

The Kaiser-style channel is one of three operational modes for delivering the floor — alongside direct federal operation (VHA expansion, hospital takeovers) and contracted clinician staffing (community health centers, rural clinics on capacity-payment). The mode is selected per region based on existing infrastructure and local clinical-culture fit, not as a uniform national choice.

2 · Why this exists

Direct federal operation is not optimal everywhere. In regions with established integrated provider organizations operating well — Kaiser Permanente in California and the Pacific Northwest, Geisinger in Pennsylvania, Intermountain in the Mountain West, Mayo in the upper Midwest, Cleveland Clinic in Ohio — replacing functioning systems with federal operation would destroy operational capability for no benefit. The architecture's pragmatic answer is to contract with these organizations on capacity-payment terms that deliver the floor while preserving their operational integrity.

Strategic reasoning: capacity-payment with strict quality, access, and anti-cream-skimming requirements aligns provider-organization economics with floor-delivery objectives. The provider organization is paid for population-health outcomes, not procedures, so cost-control discipline operates through provider design rather than payer-side gatekeeping. Where this alignment is achievable, contracted operation is more efficient than direct federal operation.

The selection is not ideological — it's operational. AHQB and Distributed Healthcare administration evaluate per region whether direct or contracted operation produces better floor delivery, and contract accordingly.

3 · How it works mechanically

RFI/RFQ contracting. AHQB issues regional requests-for-information and requests-for-qualifications for floor delivery contracts. Eligible bidders are integrated provider organizations meeting clinical-quality, financial-stability, and population-health-track-record thresholds. Contract terms specify per-enrolled-life capacity payment with adjustments for population characteristics (age, chronic-condition prevalence, social-determinants risk), quality-metric performance, and access-metric performance.

Statutory floor obligations. Contracted organizations must accept all enrolled lives in their service area — no medical underwriting, no exclusion of high-cost populations, no narrow networks. They must meet AHQB-defined access standards (wait-time thresholds, geographic-access thresholds, language-access thresholds). They must report quality metrics on AHQB schedules with audit access.

Anti-cream-skimming enforcement. Contract design includes statutory enforcement against cream-skimming — practices, marketing, network-narrowing, or service-design choices that would systematically exclude high-cost populations are explicitly prohibited and enforceable. AHQB monitors enrollment patterns, complaint patterns, and quality-of-care patterns; deviations from non-cream-skimming norms trigger contract review and, where warranted, contract termination with substitution to direct federal operation.

Capacity-payment formula transparency. Per-life payment formulas are AHQB-published and uniform across contracted providers. Provider organizations cannot negotiate special rates; they accept or decline contracts on standard terms. This prevents the contracting process from becoming a price-negotiation marketplace and preserves the architecture's central-pricing discipline.

4 · Interactions with other healthcare components

Payment design (architecture/payment-design) is the operational mechanism — Kaiser-style capacity-payment is one application of the broader payment-design canon. Hospital-takeovers (capacity/hospital-takeovers) are the operational alternative for regions where private-provider organization isn't a viable contracting partner. AHQB anti-cream-skimming monitoring (governance/anti-cream-skimming) is the enforcement layer.

Phase 1-2 deployment includes Kaiser-style contracting for regions where it's the operational fit; Phase 3-4 expands the contracted footprint as middle/small employer-insured and Medicare populations transition.

5 · Cost and revenue

Contracted capacity-payment is funded through Distributed Healthcare federal payment. Per-life rates are AHQB-set and consistent across contracted organizations. Total contracted-payment cost is included in the Year 10 ~$5.55-6.25T full-deployment estimate.

Cost discipline mechanism: capacity-payment with quality-and-access guardrails aligns provider-organization economics with cost-control. The provider organization is incentivized to keep enrolled lives healthy rather than to generate procedure volume. AHQB monitoring prevents under-treatment by monitoring outcome quality and access metrics.

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

Quality and access metrics are AHQB-defined and contractually-enforced. Failure to meet metrics produces contract review with corrective-action requirements; sustained failure produces contract termination with substitution to direct federal operation or alternative contracted partner.

Anti-cream-skimming monitoring is intensive for contracted organizations. Enrollment patterns, complaint patterns, and quality-by-population-segment patterns are tracked; deviations from non-cream-skimming norms are detected through statistical anomaly monitoring and corrective action triggered.

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

For populations served by Kaiser-style contracted providers, the visible delivery is similar to current Kaiser/Geisinger/Intermountain/Mayo experience: integrated primary, specialty, and hospital care; coordinated electronic medical records; unified scheduling. Distributed Healthcare integration adds: floor coverage with no premium, expanded scope (dental, vision, hearing, mental health, SUD, LTC), simplified administration.

For populations in regions where direct federal operation is selected instead, contracted operation isn't visible — the floor delivery looks federal. Patients in transitional periods or near regional boundaries may interact with both modes; floor coverage is uniform regardless of operational mode, so the experience is consistent.

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.

  • RFI/RFQ contract specifications: detailed contract templates, per-life rate formulas, and quality-metric definitions are pending v10.2 AHQB specification.
  • Contract duration and renewal: contract terms (5-year? 10-year?) and renewal/competitive-rebid mechanics are pending.
  • Existing Kaiser/Geisinger/Intermountain/Mayo enrollment integration: how current commercial enrollment integrates into Distributed Healthcare floor coverage during Phase 3-4 transitions is pending.
  • Regional contracting boundaries: whether contracts are state-bounded, multi-state-regional, or sub-state-regional is pending operational specification.
References: Payment design · Hospital-takeovers · Anti-cream-skimming · AHQB · DNA Chapter 11· Blueprint reference: Chapter 11
Continue reading
Same category
VHA expansion
VHA's existing 172 medical centers + 1,138 outpatient sites become the architectural backbone for Phase 1 enrollment, with documented capacity headroom + workforce expansion.
Same category
Rural hospital stabilization + takeovers
Capacity-payment stabilizes rural hospitals where fee-for-service economics fail. Federal takeover at fair market value preserves access where stabilization fails.
Same category
Telehealth + mobile + Post Office 2.0 health kiosks
Telehealth is the architecture's primary capacity-multiplier. Mobile clinics serve geographic deserts. Post Office 2.0 kiosks deliver low-acuity care in every ZIP code.
Architecture
Payment design — capacity vs. fee-for-service
AHQB sets reimbursement centrally on objective indices. Capacity-based payment for rural and low-volume facilities; fee-for-service where volume sustains it. No provider-by-provider negotiation.
Governance
Anti-cream-skimming + geographic equity
Provider cream-skimming, patient cream-skimming, and geographic inequity prevention through central reimbursement-setting + objective indices + AHQB monitoring.
Governance
American Healthcare Quality Board (AHQB)
Clinical-authority Expert Board. Sets reimbursement schedules, defines safe-harbor practice guidelines, monitors quality, and exercises rollback authority during transitions.