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.
45 endpoints listed
40 answered on this run
33 organizations
45 is how many endpoints the registry lists and this run graded; 40 is how many answered /metadata during the run that generated this page, from at least one vantage. 5 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.
- 18 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.
9A5B2C2not observed - 16 endpointsPayer Provider Directory APIs
Provider Directory APIs are required to be reachable without authentication, so they are not graded on an authorization surface they must not have.
6A4C3D3not 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.
2A1B - 7 endpointsReference and test servers
Open test servers used by the FHIR community. Included as a baseline, not as a judgement about anyone's production systems.
1A2B4C
Coverage with a denominator
Curated cohorts
Fixed public rosters make missing endpoints visible instead of silently dropping them.
- California payer cohort: 8 of 27 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
- Texas marketplace issuer cohort: 6 of 15 member organizations listed, the rest recorded with the reason they could not be
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.