Public surface / Payer Provider Directory APIs

Imperial Health Plan Provider Directory API

This endpoint answers publicly but declares little about itself.

Current grade C

Reachability100

Capability transparency100

Interop readiness0

Observed surface

Base URL: https://members.imperialhealthplan.com/api/fhir
Category: Payer Provider Directory APIs
Availability: answered 45 of the last 46 daily checks (98%)
Last answered: 2026-10-03 (answered on this run)
Vantage agreement: reachable from all 3 vantages, which are 3 hosts on one network (github-actions): one network's view sampled 3 times, not 3 independent networks

What each vantage saw

reached from 3 of 3 reporting vantages, on 1 network
Vantage	Result	What it saw	Condition
`github-actions/macos-latest`	reached	answered in 2450 ms	HTTP 200
`github-actions/ubuntu-latest`	reached	answered in 2106 ms	HTTP 200
`github-actions/windows-latest`	reached	answered in 2186 ms	HTTP 200

Vantages on one network are one network’s view sampled several times. A rule applied to that network’s address space reaches every one of them at once and reads exactly like agreement.

Interpretation

A grade describes two public discovery documents at one point in time. It does not inspect patient data, authenticated behavior, or clinical quality.

Read the scoring method →

This endpoint's full report: what was observed, what was not, and what would change it →

What its CapabilityStatement declares, resource by resource →

Findings

Reachability100

Pass: /metadata answers with HTTP 2xx over HTTPS: reachable from all 3 vantages, which are 3 hosts on one network (github-actions): one network's view sampled 3 times, not 3 independent networksR1 Spec ↗
Pass: /metadata responded in 2186 ms (median across 3 reachable vantages on one network)R2 Spec ↗

Capability transparency100

Pass: fhirVersion declared: '4.0.1' (expected 4.x)T1 Spec ↗
Pass: software name and version declaredT2 Spec ↗
Pass: 146 resource types declaredT3 Spec ↗
Pass: 145/146 declared resources document their interactionsT4 Spec ↗

Interop readiness0

Needs attention: 146 profile canonical(s) declared in rest.resource.profile, none of them US Core, CARIN, or Da Vinci; also checked rest.resource.supportedProfile, instantiates, imports, meta.profileI1 Spec ↗
Note: SMART discovery not applicable: a Provider Directory API is public by designI2 Spec ↗
Note: OAuth security not applicable: a Provider Directory API is public by designI3 Spec ↗

Declared capability changes

2026-09-03: software_version: '5.0.23' -> '5.0.34'
2026-09-05: software_version: '5.0.34' -> '5.0.35'
2026-09-10: software_version: '5.0.35' -> '5.0.55'
2026-09-24: software_version: '5.0.55' -> '5.0.65'
2026-10-01: software_version: '5.0.65' -> '5.0.86'

Declared app-to-server access

What the endpoint's own documents declare about app-to-server access, observed on this run. Nothing here was requested or exercised, and none of it is graded. An absent field is reported as absent, not as a refusal: a document that does not mention a field has not said anything about it.

What the SMART discovery document and the CapabilityStatement declare about SMART Backend Services and Bulk Data
Question	Answer	What the document says	Where it is declared
Declares private_key_jwt client authentication at the token endpoint	not retrieved on this run	the SMART discovery document was requested and not served on this run	SMART discovery: token_endpoint_auth_methods_supported
Declares the client_credentials grant, which SMART Backend Services uses	not retrieved on this run	the SMART discovery document was requested and not served on this run	SMART discovery: grant_types_supported
Declares the client-confidential-asymmetric capability	not retrieved on this run	the SMART discovery document was requested and not served on this run	SMART discovery: capabilities
Declares system-level scopes	not retrieved on this run	the SMART discovery document was requested and not served on this run	SMART discovery: scopes_supported
Declares an export operation	not listed	13 operations are declared and none is named export	CapabilityStatement: rest.operation and rest.resource.operation
Instantiates the Bulk Data Access implementation guide	not listed	0 canonicals are instantiated and none is Bulk Data's	CapabilityStatement: instantiates

Registry provenance

How this entry was verified

live CapabilityStatement fetch (fhirVersion 4.0.1, 146 resource types). The document names the platform vendor, not the plan: publisher 'Microsoft', software 'Azure Healthcare APIs' 5.0.23, and it carries no implementation block at all. Attribution to Imperial rests on the plan printing four resource URLs under this base on its own interoperability page at https://exchange.imperialhealthplan.com/interoperability/, describing them as resources that 'do not require any authentication to retrieve data', on an Imperial-controlled domain. The same page prints https://ihh-public.azurehealthcareapis.com/metadata, which answers identically and is the vendor-controlled name for what appears to be the same service; the issuer-controlled host is listed (recorded 2026-08-19). No later re-check is recorded, so the date above is the last time anyone checked this entry against the live endpoint.

Share this endpoint's grade

Link the badge back to this evidence page so readers can inspect the current findings.

<a href="https://fhir.chelseakr.com/endpoint/imperial-provider-directory/">
<img src="https://fhir.chelseakr.com/badge/imperial-provider-directory.svg"
alt="FHIR Scorecard: grade C"></a>

This is an observational snapshot of a public, unauthenticated surface. It is not an audit, a ranking of care quality, or a statement about anyone's regulatory compliance. See how we grade.

Every observation on record for this endpoint, with the dates it answered and the dates it did not.