Skip to main content

Curated cohort / fixed public roster

Indiana marketplace issuer cohort

The Patient Access and Provider Directory APIs of every issuer selling an individual-market qualified health plan on HealthCare.gov in Indiana for 2026, graded on the same public surfaces as every other endpoint here.

5organizations reviewed

5published a base URL we could verify

8endpoints listed

6answered on this run

5 of 5 member organizations publish a FHIR base URL this project could verify from public documentation, which is a curation record with a date on it, not a live figure; 8 verified endpoints are listed below. Of those, 6 answered when this page was generated, which is the measured number: it comes from this run's probes, and it moves when the endpoints do. The rest of the roster is recorded with the reason it could not be listed, because for a cohort whose membership is public and finite, the gap is itself a finding.

Membership is CMS's own file, not a list assembled here. Filtered to Indiana, the QHP Landscape PY2026 Individual Medical dataset carries 4,429 plan-county rows, 5 HIOS issuer IDs, and 5 issuer names. The roster was frozen before any URL was probed and is committed beside this file as indiana-marketplace.roster.csv.

Every member either points at endpoints already carrying their verification in data/registry.json or carries an exclusion with a dated review record and the source that was read. An exclusion is a statement about what this project could find on the date it looked, never a statement about whether an issuer meets an obligation.

Several members point at endpoints already in the registry. Where a carrier publishes one national surface, the same entry is cited from more than one cohort rather than duplicated, because listing one address under several names would misstate how many endpoints exist.

Membership sources

Listed endpoints

Verified public FHIR endpoints of cohort members
PlanPrograms EndpointCategoryGrade
Ambetter Health (Centene)Indiana individual marketplace (HealthCare.gov)Centene Provider Directory API (Ambetter)Payer Provider Directory APIsnot observed
Anthem Blue Cross and Blue Shield (Elevance Health)Indiana individual marketplace (HealthCare.gov)Anthem Blue Cross Blue Shield Patient Access API (Elevance)Payer Patient Access APIsnot observed
Anthem Blue Cross and Blue Shield (Elevance Health)Indiana individual marketplace (HealthCare.gov)Elevance Health shared Provider Directory APIPayer Provider Directory APIsC
CareSourceIndiana individual marketplace (HealthCare.gov)CareSource Patient Access APIPayer Patient Access APIsA
CareSourceIndiana individual marketplace (HealthCare.gov)CareSource Provider Directory APIPayer Provider Directory APIsA
Cigna HealthcareIndiana individual marketplace (HealthCare.gov)Cigna Patient Access APIPayer Patient Access APIsA
Cigna HealthcareIndiana individual marketplace (HealthCare.gov)Cigna Provider Directory APIPayer Provider Directory APIsA
UnitedHealthcareIndiana individual marketplace (HealthCare.gov)UnitedHealthcare Provider Directory APIPayer Provider Directory APIsC

Grades are comparable within a category only: a Patient Access API and a Provider Directory API answer to different expectations and are never ranked against each other.

What "did not answer" was

The condition each listed endpoint that did not answer was observed in on this run, kept apart by category and never added together. An endpoint that answered and declined this request is running; an endpoint that produced no document is a different fact about a different thing. This project reports the condition and reads neither of them as a choice or as a defect.

Payer Patient Access APIs: 1 listed endpoint did not answer
EndpointConditionWhat it means
Anthem Blue Cross Blue Shield Patient Access API (Elevance)Answered, and declined this requestthe surface answered, and declined to serve this request
Payer Provider Directory APIs: 1 listed endpoint did not answer
EndpointConditionWhat it means
Centene Provider Directory API (Ambetter)Answered, and declined this requestthe surface answered, and declined to serve this request

What the listed endpoints declare

How many of the listed endpoints with a readable CapabilityStatement declare each resource and each interaction on it, counted within a category and never across one. Declared, not tested.

Observational snapshots of public discovery surfaces. Not audits, not compliance determinations, and not statements about care quality. Publishing a base URL to unregistered visitors is not required by any rule this project reads, and a plan that does not is not violating anything; it is only not independently checkable from outside.