Current endpoint responses:

Endpoint Counts by Developer and FHIR Version

All Endpoint Responses

All HTTP response codes ever received and count of endpoints which returned that code at some point in history

*An endpoint is considered to be an "Indexed Endpoint" when it has been queried by the Lantern system at least once. If an endpoint has never been queried by the Lantern system yet, it will not be counted towards the total number of "Indexed Endpoints".

The URL for each endpoint in the table below can be clicked on to see additional information for that individual endpoint.

* An asterisk after a 'true' value in the 'Capability Statement Returned' field indicates that the returned Capability Statement for the endpoint is not of kind 'instance', which is the kind Lantern expects.

These files include the endpoint data over time in JSON format.

Endpoint Organizations

NPI Organization Matches

Endpoints can be linked to organizations in two ways, either by the National Provider Identifier (NPI) as found in the National Payer and Provider Enumeration System (NPPES), which is preferred, or by the organization name as reported by a Certified API Developer. Links made between organizations and endpoints using an NPI ID are given a match confidence value of 100%, which is higher than any possible confidence value for matches made using the organization name. In instances where a unique identifier to match an organization to an endpoint is not provided, Lantern uses the organization name which each endpoint list provides, and the primary and secondary organization names provided by the NPPES NPI data set to match npi organizations to endpoints based on their names and assign a match confidence score. This table shows matches with a match confidence of 97% and up.

Map of Endpoints Linked to an Organization

This map visualizes the locations of endpoints which Lantern has associated with an organization name in NPPES. An endpoint will have an entry on the map for each version of FHIR which it supports. Caution should be taken when gathering insights from this map as linking an API Information Source to an organization name in NPPES based on reported organization name may not be done with 100% confidence. See note below the map for more information.

The points on the map, below, represent the zip code associated with the primary address of matched organizations. The location reported by NPPES may not be the physical location of the API Information Source serviced by a given endpoint, may not represent a physical location where services are provided, or may not be the geolocation of any individual endpoint. This is especially true for API Information Sources which may have more than one physical location, which may vary by facility type and geographic location.

Endpoint List Organization Matches

This table shows the organization name listed for each endpoint in the endpoint list it appears in.

CapabilityStatement / Conformance Resource Size

Resource Count

FHIR Implementation Guides

This is the list of FHIR implementation guides reported by the CapabilityStatement / Conformance Resources from the endpoints.

Implementation Guide Count

FHIR CapabilityStatement / Conformance Fields

This is the list of fields included in the FHIR CapabilityStatements / Conformance Resources from the endpoints.

Required Fields

Optional Fields

Supported CapabilityStatement / Conformance Fields

FHIR CapabilityStatement / Conformance Extensions

This is the list of extensions included in the FHIR CapabilityStatements / Conformance Resources from the endpoints.

Supported Extensions:

Supported CapabilityStatement / Conformance Extensions

Values of FHIR CapabilityStatement / Conformance Fields

This is the set of values from the endpoints for a given field included in the FHIR CapabilityStatement / Conformance Resources.

Field Values

Endpoints that Include a Value for the Given Field

For information about the validation rules that Lantern evaluates, including their descriptions and references, please see the documentation available here.

Validation Results Count

The ONC Final Rule requires endpoints to support FHIR version 4.0.1, but we have included all endpoints for reference

*Note: The messagingEndptRule is not broken, there is an issue with the Capability Statement invariant (cpb-3). The invariant states that the Messaging endpoint has to be present when the kind is 'instance', and Messaging endpoint cannot be present when kind is NOT 'instance', but the FHIRPath expression is "messaging.endpoint.empty() or kind = 'instance'", which is not consistent with the expectation for the invariant and will not properly evaluate the conditions required.

Validation Details

Click on a rule below to filter the validation failure details table.

Validation Failure Details

The URL for each endpoint in the table below can be clicked on to see additional information for that individual endpoint.

A green check icon indicates that an endpoint has successfully returned a Conformance Resource/Capability Statement. A red X icon indicates the endpoint did not return a Conformance Resource/Capability Statement.

This is the list of security authorization types reported by the CapabilityStatement / Conformance Resources from the endpoints.

Endpoints by Authorization Type

The URL for each endpoint in the table below can be clicked on to see additional information for that individual endpoint.

This is the SMART-on-FHIR Core Capabilities response page. FHIR endpoints requiring authorization shall provide a JSON document at the endpoint URL with /.well-known/smart-configuration appended to the end of the base URL.

Endpoints by Well Known URI support

This is the list of endpoints which have returned a valid SMART Core Capabilities JSON document at the /.well-known/smart-configuration URI.

The URL for each endpoint in the table below can be clicked on to see additional information for that individual endpoint.

Lantern Logo