US Healthcare Ecosystem — PM Visual Guide

Five diagrams plus a PM components playbook: participant incentives, claims/prior-auth friction, payment model shifts, and the operational levers that reduce admin burden while protecting outcomes.

Diagram 1

Healthcare Participant Flow — Incentive Relay

Horizontal map of how value, authorization, and payment decisions move across participants from member demand to regulated supply and oversight.

Demand: Patients / Members

Members initiate care demand and absorb premium, deductible, copay, and access friction.

Individuals Families Employer Plans

Care Delivery: Providers

Hospitals and clinicians deliver treatment, document codes, and submit claims for payment.

Hospitals Physicians Labs Pharmacies

Decision Layer: Payers

Coverage policy, network contracts, utilization controls, and adjudication logic sit here.

Commercial Plans Medicare / Medicaid

Execution Infrastructure

EHR, clearinghouse, and interoperability rails route data and claims across fragmented institutions.

Epic / Cerner Change / Availity HL7 / FHIR / EDI

Pharmacy & Drug Economics (Cross-Cutting)

PBMs and manufacturers influence formulary access, rebate economics, and patient out-of-pocket burden.

Express Scripts CVS Caremark OptumRx Drug Manufacturers

Regulatory Guardrails (System Constraints)

FDA, CMS, HHS, and state regulators constrain product speed and define compliance boundaries.

FDA CMS HHS State DOI

System reality: no single actor controls the full journey. PM leverage comes from reducing handoff friction between care delivery, coverage decisions, and infrastructure constraints.

Diagram 2

Claims Flow — How a Medical Bill Gets Paid

Medical and pharmacy claims share actors but have radically different latency: weeks for medical adjudication, seconds for pharmacy.

Patient

Provider

Clearinghouse

Payer

PBM (Rx)

Bank

Care delivery and claim submission

Receives care

Documents encounter in EHR + coding

Scrubs/validates CMS-1500 or UB-04 claim

Adjudication and benefit calculation

Forwards clean claim to payer

Eligibility + allowed amount + member cost share

Payment and patient billing

Receives EOB and later balance bill

Posts ERA payment, bills patient remainder

Sends EOB + remittance (835)

Transfers settlement funds

Architecture implication: medical claims systems optimize batch accuracy and denial management; pharmacy systems optimize sub-second reliability and uptime at checkout.

Diagram 3

Prior Authorization Sequence

Prior auth is a pre-approval gate for selected treatments, often causing delays even when care is ultimately approved.

Decision Flow

Provider orders treatment/procedure.
Check payer rules: prior auth required?
No: proceed and submit normal claim.
Yes: submit PA request with clinical documentation.
Payer reviews medical necessity criteria.
Approved: treatment proceeds.
Denied: accept, appeal, or external review.
Pending: more documents requested; delays continue.

Operational Paths

Standard review: typically 3-14 days.

Urgent review: 24-72 hours for acute scenarios.

Appeal path: provider peer-to-peer review with payer medical director, then external independent review if unresolved.

Outcome reality: many denials are reversed, implying workflow friction is often administrative rather than clinical.

34%Initial prior auth denial rate

82%Denials overturned on appeal

7 daysAverage delay window

~25%Share of care delays tied to PA

Core tension: prior auth aims to control unnecessary utilization, but high reversal rates suggest many requests are delayed rather than genuinely inappropriate.

Diagram 4

Fee-for-Service vs Value-Based Care

Payment model determines behavior. FFS rewards activity volume; VBC rewards outcomes and cost control.

Fee-for-Service (FFS)

Mechanism: bill and get paid per service/procedure/test.
Incentive: volume growth.
Quality linkage: weak by default.
Risk holder: payer bears most financial risk.
Market share: still dominant (~60% of payments).
Failure mode: overuse and cost inflation.

FFS (volume) → Shared savings → Bundled payments → Capitation → VBC (outcomes)

Value-Based Care (VBC)

Mechanism: payment tied to outcomes and total cost improvement.
Incentive: prevention and longitudinal health management.
Quality linkage: explicit (readmissions, HEDIS, satisfaction).
Risk holder: provider shares or assumes financial risk.
Adoption: growing (~40%), accelerated by CMS policy.
Challenge: requires strong data + risk adjustment infrastructure.

PM takeaway: products designed for FFS claims optimization won’t automatically succeed in VBC environments that need population-level analytics and care coordination workflows.

Diagram 5

HealthTech Business Models

Healthtech monetization varies by buyer (consumer, employer, payer, provider, pharma) and evidence burden.

D2C Telehealth

Model: Direct-to-consumer virtual care.

Revenue: Subscription or per visit.

Payer: Patient (cash or mixed insurance).

Challenge: CAC and clinical quality scrutiny.

B2B2C Health Platform

Model: Sell to employers/payers, serve members.

Revenue: PEPM contracts.

Payer: Employer or insurer.

Challenge: Long sales cycles, ROI proof.

Digital Therapeutics (DTx)

Model: Prescription-grade software treatment.

Revenue: Per-prescription reimbursement.

Payer: Insurance formularies.

Challenge: FDA and coverage pathways.

EHR / Infrastructure

Model: Core provider workflow software.

Revenue: License + implementation + maintenance.

Payer: Provider organizations.

Challenge: Massive switching and integration costs.

Claims & Revenue Cycle

Model: Denial prevention and payment acceleration.

Revenue: Per-claim fee or subscription.

Payer: Providers/health systems.

Challenge: Integration and regulation complexity.

Health Data & Analytics

Model: De-identified data + analytics licensing.

Revenue: Data subscriptions and insight products.

Payer: Pharma, payers, research orgs.

Challenge: Privacy, data quality, consent governance.

Reference

Healthcare Components — PM Lens

For healthcare PM interviews: focus on admin burden, clinical outcomes, and payment incentives — not just app features.

How this connects to the diagrams: Participant Map shows incentive conflicts, Claims Flow and Prior Auth show where delay is introduced, and FFS vs VBC explains why behavior differs by reimbursement model.

Claims Adjudication Platform

What it does: Applies contract logic, coverage rules, and coding policies to price and approve claims.

PM metrics: First-pass resolution, denial rate, rework volume, adjudication cycle time.

Pitfall: Rule complexity scales faster than teams expect, causing provider abrasion and appeal backlog.

Prior Auth Orchestration

What it does: Routes authorization requests across payers, policies, and documentation requirements.

PM metrics: Approval latency, auto-approval rate, fax/manual touch rate, abandonment due to delays.

Pitfall: Faster submission UX without payer integration still leaves outcomes unchanged.

Interoperability & Data Exchange

What it does: Connects EHR, payer APIs, clearinghouses, labs, and pharmacies through standards (FHIR/EDI).

PM metrics: Data completeness, integration uptime, normalized record accuracy, retrieval latency.

Pitfall: Integration count looks good on slides, but low data quality kills automation gains.

Interview shortcut: structure healthcare answers around time-to-treatment, administrative cost, and outcome quality. If your feature improves all three, that’s product gold. If it improves one while worsening the others, call out the tradeoff explicitly.

Common PM Failure Patterns

Workflow-only fix

Improving provider UI without payer-side integration leaves real approval latency unchanged.

Automation without data quality

Decision automation fails when clinical/coding data is incomplete or non-normalized.

Ignoring incentives

Feature assumptions break when reimbursement model rewards volume over outcomes.

Compliance as afterthought

Late HIPAA/regulatory integration causes rework, launch delays, and trust damage.

Decision Matrix — What to Optimize For

Situation	Optimize For	Guardrail Metrics	Avoid
High prior-auth backlog	Latency reduction + auto-approval logic	TAT, auto-approval %, denial overturn rate	Manual ops headcount as only fix
Provider abrasion spikes	Administrative simplicity	Rework rate, touch count per request	Adding docs requirements without evidence
Value-based contract rollout	Outcome visibility + risk adjustment	Readmission, quality scores, total cost of care	FFS-era metrics as primary KPI set
Interoperability initiative	Data completeness + reliability	Record match rate, integration uptime, retrieval latency	Counting integrations instead of usable data

Interview Scenarios + Strong Answer Angles

“Prior auth takes 9 days. How would you improve it?”

Angle: map top denial pathways, pre-fill required clinical data, implement payer-priority integrations, and track turnaround by service line.

“Providers complain your tool adds clicks.”

Angle: optimize for touch reduction per episode, embed in existing EHR flow, and tie changes to measurable time saved.

“Leadership wants VBC outcomes in 1 quarter.”

Angle: set phased targets (process → intermediate clinical → financial outcomes) and align incentives before forcing outcome accountability.

US Healthcare Ecosystem Visual Guide · PM Prep Papers Series · fullstackpm.tech · March 2026