Independent public-interest infrastructure
What does a health API reveal before you log in?
FHIR Scorecard reads the public discovery surface and turns it into evidence a person can check: reachable or not, clearly documented or not, ready to interoperate or not.
Latest registry snapshot
Every dot is a public endpoint.
88 endpoints listed
72 answered on this run
60 organizations
88 is how many endpoints the registry lists and this run graded; 72 is how many answered /metadata during the run that generated this page, from at least one vantage. 16 were not observed on this run and are not counted as answering.
Browse the evidence
Different surfaces, different expectations
Grades are only comparable within a category. Each surface is evaluated against the implementation guides and public behavior that apply to it.
- 40 endpointsPayer Patient Access APIs
Patient Access APIs let a member pull their own claims and coverage data into an app they choose. These grades describe what each endpoint publicly declares.
11A17B5C7not observed - 37 endpointsPayer Provider Directory APIs
Provider Directory APIs are meant to be readable by anyone - required to be, for Medicare Advantage organizations under 42 CFR 422.120, with parallel provisions for Medicaid and CHIP - so they are not graded on an authorization surface they should not have.
14A1B11C2D9not observed - 1 endpointsProvider and health system APIs
APIs published by health systems and provider organizations.
1A - 3 endpointsEHR vendor sandboxes
Sandboxes published by EHR vendors for developers evaluating their platforms. Graded separately from payer APIs, which answer to different expectations.
2A1C - 7 endpointsReference and test servers
Open test servers used by the FHIR community. Included as a baseline, not as a judgment about anyone's production systems.
1A6C
Coverage with a denominator
Curated cohorts
Fixed public rosters make missing endpoints visible instead of silently dropping them.
- Alabama marketplace issuer cohort: 3 of 4 member organizations listed, the rest recorded with the reason they could not be
- Alaska marketplace issuer cohort: 1 of 2 member organizations listed, the rest recorded with the reason they could not be
- Arizona marketplace issuer cohort: 5 of 7 member organizations listed, the rest recorded with the reason they could not be
- California payer cohort: 8 of 27 member organizations listed, the rest recorded with the reason they could not be
- Delaware marketplace issuer cohort: 2 of 3 member organizations listed, the rest recorded with the reason they could not be
- Florida marketplace issuer cohort: 9 of 15 member organizations listed, the rest recorded with the reason they could not be
- Indiana marketplace issuer cohort: 5 of 5 member organizations listed, the rest recorded with the reason they could not be
- Iowa marketplace issuer cohort: 3 of 6 member organizations listed, the rest recorded with the reason they could not be
- Kansas marketplace issuer cohort: 4 of 6 member organizations listed, the rest recorded with the reason they could not be
- Louisiana marketplace issuer cohort: 5 of 6 member organizations listed, the rest recorded with the reason they could not be
- Michigan marketplace issuer cohort: 5 of 7 member organizations listed, the rest recorded with the reason they could not be
- Mississippi marketplace issuer cohort: 3 of 5 member organizations listed, the rest recorded with the reason they could not be
- Missouri marketplace issuer cohort: 5 of 7 member organizations listed, the rest recorded with the reason they could not be
- Nebraska marketplace issuer cohort: 3 of 5 member organizations listed, the rest recorded with the reason they could not be
- North Carolina marketplace issuer cohort: 5 of 6 member organizations listed, the rest recorded with the reason they could not be
- Ohio marketplace issuer cohort: 6 of 11 member organizations listed, the rest recorded with the reason they could not be
- Oklahoma marketplace issuer cohort: 4 of 7 member organizations listed, the rest recorded with the reason they could not be
- Texas marketplace issuer cohort: 6 of 15 member organizations listed, the rest recorded with the reason they could not be
- West Virginia marketplace issuer cohort: 1 of 2 member organizations listed, the rest recorded with the reason they could not be
- Wisconsin marketplace issuer cohort: 10 of 12 member organizations listed, the rest recorded with the reason they could not be
- Wyoming marketplace issuer cohort: 1 of 2 member organizations listed, the rest recorded with the reason they could not be
How much of the federal marketplace frame has a publicly checkable endpoint, with the organizations nobody has reviewed yet counted separately from the ones that publish nothing.
What the curation found
The URL is often the first barrier.
Most payers with a base URL on a public developer portal expose a readable CapabilityStatement, and most grade well. The difficult part is locating that URL at all: payer base URLs are not predictable, so the registry is verified one portal at a time.
Read the research note and its corrections →Open by construction
Inspect the result—or the machinery.
Observational snapshots of public surfaces. Not audits, not rankings of care quality, not statements about anyone's regulatory compliance.