ira_mfp_exposure

Ira Mfp Exposure

What it answers

Returns the cross-payer federal exposure for an IRA-eligible drug: IRA Maximum Fair Price (when in the IPAY-2026 cohort) + Part D total spend + Part B total spend + Medicaid SDUD total spend, anchored to a specific data year. Reference demos, MEASURED 2026-08-01 against live Athena: STELARA DY2023 = Part D $2,987,778,599.90 + Part B $27,614,584.61 + Medicaid SDUD $3,302,074,349.03 = $6,317,467,533.54 combined, IRA MFP $4,695.00/dose CY2026. ELIQUIS DY2023 = Part D $18,273,451,967.00 + Medicaid SDUD $2,233,903,339.92 = $20,507,355,306.92 combined, IRA MFP $237.25/dose CY2026. (This description previously read 'Stelara ... = $20.5B'. $20.5B is real but it is ELIQUIS; Stelara is $6.32B. The label was on the wrong drug, which is why the tool looked ~3x low against its own demo.)

SOURCE COVERAGE: IRA MFP (fact_drug_reimbursement) covers 10 IPAY-2026 drugs only; queries outside that cohort return ira_mfp_unit_price_usd=null with a coverage_gap caveat (federal-payor spend is still answered). Part D + Part B PUFs publish annually. Medicaid SDUD has per-cell suppression (suppression_used=true rows excluded from totals with a suppression_warning caveat).

ALIAS RESOLUTION: M-6 parent_alias + FDA dim_drug fallback applied to drug_name — brand inputs (Stelara) resolve to generic (ustekinumab) and vice-versa. Aliases used are surfaced in the response envelope.

KNOWN PUBLICATION GAPS: see gap_registry entries ira_mfp_partial_cohort_ipay_2026, medicaid_sdud_suppression_used_flag, part_d_puf_annual_grain_only.

Inputs

drug_name

string · required

acknowledge_era_break

boolean · optional

default: false

data_year

integer · optional

default: 2023

top_n

integer · optional

default: 20

Call it

From an agent: connect the Vlada MCP once (one click for Claude, ChatGPT, Cursor, VS Code) and ask in plain English; the agent selects ira_mfp_exposure when the question fits. From code: the same tool over REST with an API key. The schema endpoint needs no key.

curl -X POST https://api.vladahealth.com/v1/tools/ira_mfp_exposure \
  -H "Authorization: Bearer $VLADA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"drug_name":"<drug_name>"}'

curl https://api.vladahealth.com/v1/tools/ira_mfp_exposure/schema      # the JSON schema, no auth
# MCP endpoint (Streamable HTTP): https://mcp.vladahealth.com/mcp

What comes back

Typed rows plus provenance on every answer: the public source file, its vintage, the methodology, and a response_hash you can replay. Prove and replay tools turn any number into a re-runnable receipt. A number the data cannot support comes back as “not in the data”, never as zero.

Sources behind it

drug_silver.fact_drug_reimbursement#ira_mfp
drug_silver.fact_drug_spending_part_d
drug_silver.fact_drug_spending_part_b
drug_silver.fact_drug_medicaid_utilization
drug_silver.dim_drug

tables: drug_silver.fact_drug_reimbursement · drug_silver.fact_drug_spending_part_d · drug_silver.fact_drug_spending_part_b · drug_silver.fact_drug_medicaid_utilization · drug_silver.dim_drug

Known limits

ira_mfp_partial_cohort_ipay_2026
medicaid_sdud_suppression_used_flag
part_d_puf_annual_grain_only

As of the 2026-09-19 build of the served surface · machine-readable catalog · the live server may run a different version; the schema endpoint above is authoritative for what is deployed.