Curated cohort / fixed public roster
West Virginia marketplace issuer cohort
The Patient Access and Provider Directory APIs of every issuer selling an individual-market qualified health plan on HealthCare.gov in West Virginia for 2026, graded on the same public surfaces as every other endpoint here.
2organizations reviewed
1published a base URL we could verify
2endpoints listed
2answered on this run
1 of 2 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; 2 verified endpoints are listed below. Of those, 2 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 West Virginia, the QHP Landscape PY2026 Individual Medical dataset carries 2,035 plan-county rows, 2 HIOS issuer IDs, and 2 issuer names. The roster was frozen before any URL was probed and is committed beside this file as west-virginia-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
- CMS / CCIIO: QHP Landscape PY2026 Individual Medical (individual_market_medical.zip, issued 2026-08-04, modified 2026-08-10) (retrieved 2026-09-13)
Listed endpoints
| Plan | Programs | Endpoint | Category | Grade |
|---|---|---|---|---|
| CareSource | West Virginia individual marketplace (HealthCare.gov) | CareSource Patient Access API | Payer Patient Access APIs | A |
| CareSource | West Virginia individual marketplace (HealthCare.gov) | CareSource Provider Directory API | Payer Provider Directory APIs | A |
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 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.
- What its Payer Patient Access APIs endpoints declare
- What its Payer Provider Directory APIs endpoints declare
Members reviewed and not listed
Each exclusion records how far the review went, on what date, and where to check it. A review that found nothing is not proof that nothing exists: if one of these plans publishes a base URL we missed, please tell us.
| Plan | Programs | Why it is not listed |
|---|---|---|
| Highmark Blue Cross Blue Shield West Virginia | West Virginia individual marketplace (HealthCare.gov) | Highmark Blue Cross Blue Shield West Virginia's APIs are published on the Highmark Health Interoperability Developer Portal, and no base URL for them appears in any document this project could retrieve. The portal's API catalog is browsable without an account and lists the FHIR Patient Access and Provider Directory APIs by name, but each entry's host and base path are rendered by the portal's own JavaScript and were not served to an automated client; Highmark's member-facing CMS and ONC interoperability page names the entity and prints no address either. The portal presents its six FHIR APIs under one 'Highmark Health Organization' heading rather than per legal entity, and Highmark's interoperability page lists Highmark West Virginia Inc. as one of the five entities the rule reaches. (the plan's own documentation was reviewed, 2026-09-13; source) |
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.