Skip to main content

Availability

Which public FHIR endpoints answered, and how often

88 of 88 endpoints have enough recorded observations to state a share. Each kind is ordered on its own; an EHR vendor's sandbox and a payer's production Patient Access API are not the same kind of thing, and one table over both would be a comparison this data does not support.

A position here orders one measurement: whether a public address answered a request for its /metadata document, from three hosts on one provider's network, over the recorded window. It is not a service-level measurement, not an uptime guarantee, and not a statement about an organization. A run where no vantage reached an endpoint is published as not reached from that network on that day, which is a fact about the measurement as much as about the endpoint. See how we grade.

EHR vendor sandboxes

EHR vendor sandboxes, ordered by measured answered share
PositionEndpointAnswered shareAnswered of observedFull record
1Medplum public API100%58 of 58every observation
2Oracle Health (Cerner) open sandbox100%58 of 58every observation
3Epic on FHIR public sandbox98%57 of 58every observation

Payer Patient Access APIs

Payer Patient Access APIs, ordered by measured answered share
PositionEndpointAnswered shareAnswered of observedFull record
1Aetna Patient Access (public demo instance)100%58 of 58every observation
2Blue Cross Blue Shield of Minnesota Patient Access API (preview)100%58 of 58every observation
3Capital Blue Cross Patient Access API100%58 of 58every observation
4Cigna Patient Access API100%58 of 58every observation
5CMS Blue Button 2.0 (Medicare)100%58 of 58every observation
6HealthPartners Patient Access API100%58 of 58every observation
7Health Plan of San Mateo Patient Access API100%56 of 56every observation
8Santa Clara Family Health Plan Patient Access API100%56 of 56every observation
9AmeriHealth Caritas Next (Florida) Patient Access API100%45 of 45every observation
10AvMed Patient Access API100%45 of 45every observation
11Florida Blue Patient Access API (CMS Interoperability conformance endpoint)100%45 of 45every observation
12AmeriHealth Caritas Next North Carolina Patient Access API100%30 of 30every observation
13Blue Cross and Blue Shield of North Carolina Patient Access API100%30 of 30every observation
14Blue KC Patient Access API100%30 of 30every observation
15CareSource Patient Access API100%30 of 30every observation
16Cox HealthPlans Interoperability API100%30 of 30every observation
17Group Health Cooperative-SCW Patient Access API100%30 of 30every observation
18Louisiana Blue Patient Access API100%30 of 30every observation
19MercyCare Health Plans Patient Access API100%30 of 30every observation
20Network Health Patient Access API100%30 of 30every observation
21Paramount Health Care Interoperability API100%30 of 30every observation
22Priority Health Patient Access API100%30 of 30every observation
23Quartz Patient Access API100%30 of 30every observation
24Security Health Plan Member API100%30 of 30every observation
25Wellmark Patient Access API100%30 of 30every observation
26AmeriHealth Caritas Next (Delaware) Patient Access API100%16 of 16every observation
27Blue Cross and Blue Shield of Alabama Patient Access API100%16 of 16every observation
28Blue Cross and Blue Shield of Nebraska Patient Access API100%16 of 16every observation
29Premera Blue Cross Patient Access API100%16 of 16every observation
3022 Health (Community Care Plan) Patient Access API98%44 of 45every observation
31Inland Empire Health Plan Patient Access API96%54 of 56every observation
32Humana Patient Access API91%53 of 58every observation
33Kaiser Permanente Health Plan Patient Access API89%50 of 56every observation
34AmeriHealth Caritas Next Louisiana Patient Access API87%26 of 30every observation
35Sharp Health Plan Patient Access API73%41 of 56every observation
36Imperial Health Plan Patient Access API0%0 of 46every observation
37Wellpoint Patient Access API0%0 of 46every observation
38Anthem Blue Cross Blue Shield Patient Access API (Elevance)0%0 of 30every observation
39Aspirus Health Plan Patient Access API0%0 of 30every observation
40Blue Cross Blue Shield of Arizona Patient Access API0%0 of 30every observation

Payer Provider Directory APIs

Payer Provider Directory APIs, ordered by measured answered share
PositionEndpointAnswered shareAnswered of observedFull record
1Cigna Provider Directory API100%58 of 58every observation
2Central California Alliance for Health Provider Directory API100%56 of 56every observation
3Community Health Group Provider Directory API100%56 of 56every observation
4L.A. Care Health Plan Provider Directory API100%56 of 56every observation
5Santa Clara Family Health Plan Provider Directory API100%56 of 56every observation
6UnitedHealthcare Provider Directory API100%46 of 46every observation
722 Health (Community Care Plan) Provider Directory API100%45 of 45every observation
8AmeriHealth Caritas Next (Florida) Provider Directory API100%45 of 45every observation
9Florida Blue Provider Directory API (CMS Interoperability conformance endpoint)100%45 of 45every observation
10AmeriHealth Caritas Next Louisiana Provider Directory API100%30 of 30every observation
11AmeriHealth Caritas Next North Carolina Provider Directory API100%30 of 30every observation
12Blue Cross and Blue Shield of North Carolina Provider Directory API100%30 of 30every observation
13Blue Cross Blue Shield of Michigan Provider Directory API100%30 of 30every observation
14Blue KC Provider Directory API100%30 of 30every observation
15CareSource Provider Directory API100%30 of 30every observation
16CommunityCare Provider Directory API (commercial)100%30 of 30every observation
17CommunityCare Provider Directory API (marketplace)100%30 of 30every observation
18Medical Mutual of Ohio Provider Directory API100%30 of 30every observation
19MercyCare Health Plans Provider Directory API100%30 of 30every observation
20Quartz Provider Directory API100%30 of 30every observation
21Security Health Plan Provider Directory API100%30 of 30every observation
22AmeriHealth Caritas Next (Delaware) Provider Directory API100%16 of 16every observation
23Blue Cross and Blue Shield of Alabama Provider Directory API100%16 of 16every observation
24Premera Blue Cross Provider Directory API100%16 of 16every observation
25Elevance Health shared Provider Directory API98%45 of 46every observation
26Imperial Health Plan Provider Directory API98%45 of 46every observation
27Inland Empire Health Plan Provider Directory API91%51 of 56every observation
28Blue Cross and Blue Shield of Kansas Provider Directory API87%26 of 30every observation
29Sharp Health Plan Provider Directory API73%41 of 56every observation
30Centene Provider Directory API (Ambetter)10%3 of 30every observation
31CHRISTUS Health Plan Provider Directory API0%0 of 46every observation
32Health Care Service Corporation Provider Directory API0%0 of 46every observation
33AvMed Provider Directory API0%0 of 45every observation
34Aspirus Health Plan Provider Directory API0%0 of 30every observation
35Group Health Cooperative-SCW Provider Directory API0%0 of 30every observation
36Network Health Provider Directory API0%0 of 30every observation
37Priority Health Provider Directory API0%0 of 30every observation

Provider and health system APIs

Provider and health system APIs, ordered by measured answered share
PositionEndpointAnswered shareAnswered of observedFull record
1VA Lighthouse Patient Health API (production)100%58 of 58every observation

Reference and test servers

Reference and test servers, ordered by measured answered share
PositionEndpointAnswered shareAnswered of observedFull record
1Firely public test server100%58 of 58every observation
2HAPI FHIR public test server (R4)100%58 of 58every observation
3HAPI FHIR public test server (R5)100%58 of 58every observation
4ONC Inferno reference server (US Core / SMART)100%58 of 58every observation
5Firely public test server (R5)98%57 of 58every observation
6SMART Health IT open sandbox (R4)97%56 of 58every observation
7SMART Health IT open sandbox (STU3)97%56 of 58every observation

Endpoints below the reporting floor

None. Every one of the 88 endpoints in the registry has at least 14 recorded observations.

Why fourteen

An answered share over two or three observations moves by tens of points on a single missed day, so it reports the sampling rather than the endpoint. Fourteen is the floor this project already applies to the availability sentence on every scorecard, and the same number governs here so that two surfaces of the same record cannot disagree. The full record for every endpoint, above the floor or below it, is at the observation record.