All apps

Market Access & HEOR · Market access / HEOR / payer strategy

CuRE Corridor

Market access & HEOR — AMCP/HTA value dossiers, CEA/BIA models, and payer RWE for reimbursement, built on the platform's governed real-world-evidence moat.

Part of Commercial

What it does

Market access & HEOR — AMCP/HTA value dossiers, CEA/BIA models, and payer RWE for reimbursement, built on the platform's governed real-world-evidence moat. The real-world-evidence moat becomes market-access leverage: payer value dossiers and CEA/BIA are built on the platform's own governed RWD via Calculate + Conduct, not licensed third-party datasets.

Key capabilities

  • AMCP-format value dossiers + HTA submissions with a submission-lifecycle state machine (NICE, G-BA/IQWiG, HAS, CADTH-CDA-AMC, PBAC)
  • 21 CFR Part 11 value-dossier & budget-impact (BIA) system-of-record: immutable WORM version seals + e-signed reviewer sign-off (ADR-COR-003)
  • Value-based-contract evidence design — a mutable design sealed to a WORM / e-signed package, bound to Calculate outcomes (ADR-COR-002/-004)
  • Cost-effectiveness (CEA) + budget-impact (BIA) models on Calculate artifacts (consumed, not re-implemented)
  • Payer real-world evidence for reimbursement — commissioned and consumed over Curtain-release-gated Conduct aggregates
  • Grounded-AI dossier drafting + HTA-response Q&A — cite-or-refuse over the tenant's governed evidence via the Clarion gateway
  • Payer/segment landscape, price & access records, and the value-message library
  • Partner-emit egress: value/evidence artifacts emitted into commercial systems (Veeva, Model N, Vistex) — integrate, not become (ADR-COR-005)
  • Read-only Crucible portfolio/eNPV lineage seam — the payer value case linked back to its ex-ante program-economics assumptions (ADR-COR-001)
  • Org-private commercial-value domain (cure_corridor), no cross-tenant read path
  • Indirect treatment comparison (MAIC/STC/NMA)
  • EU JCA / PICO dossier workspace
  • IRA/IPAY payer-evidence workspace

What sets it apart

  • CEA/BIA and MAIC/STC/NMA indirect comparisons run on the platform's own governed RWD via Calculate — the value case built on the RWE moat, not licensed third-party data.
  • The value dossier is a 21 CFR Part 11 system-of-record, not a document store: each submitted version freezes to an immutable WORM seal and releases only under an e-signed reviewer sign-off, with the meaning-of-signature bound into a hash-chained ledger — so the payer-value case is tamper-evident and inspection-ready (ADR-COR-003 / ADR-PLT-046).
  • The real-world-evidence moat becomes market-access leverage: payer value dossiers and CEA/BIA are built on the platform's own governed RWD via Calculate + Conduct, not licensed third-party datasets bolted on.
  • Consume-not-reimplement (the Caliber-from-Calculate shape, ADR-PLT-008): Corridor owns the commercial-value domain and the market-access buyer surface; Calculate owns the CEA/BIA/RWE methodology it consumes as version-pinned artifacts — never re-implemented (ADR-PLT-044).
  • A clean clinical→commercial firewall (ADR-COR-001 D3): Corridor holds no PHI and does no record linkage — it consumes only Curtain-release-gated, disclosure-safe aggregates, so there is no re-identification or clinical-consent-laundering path in the commercial plane.
  • Commercial-value data is org-private by default under an app-layer market-access governance persona (org_id-only tenancy, ADR-CRU-002) — a distinct governance surface from the clinical consent / DUA stack, not a reuse of it.
  • Founding app of the Commercial bundle alongside Crucible (portfolio & decision economics, ADR-PLT-132) — the market-access / HEOR buyer surface, distinct from the corp-dev / portfolio-strategy one.
  • Grounded-AI dossier drafting and HTA-response Q&A run cite-or-refuse over the tenant's own governed evidence via the Clarion AI gateway — grounded in the actual model and data, not a generic template; commercial-data-partner ingestion extends the surface further.

See CuRE Corridor in action

Every research ecosystem is unique. Let's discuss how CuRE can be configured for your needs.