Public surface / Payer Provider Directory APIs

CareSource Provider Directory API

This endpoint declares a complete, interoperable public surface.

Current grade A

Reachability100

Capability transparency100

Interop readiness100

Observed surface

Base URL: https://orchestrateserver.caresource.careevolution.com/api/fhir/provider-directory
Category: Payer Provider Directory APIs
Availability: answered 30 of the last 30 daily checks (100%)
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 42 ms	HTTP 200
`github-actions/ubuntu-latest`	reached	answered in 755 ms	HTTP 200
`github-actions/windows-latest`	reached	answered in 375 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 375 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: 45 resource types declaredT3 Spec ↗
Pass: 45/45 declared resources document their interactionsT4 Spec ↗

Interop readiness100

Pass: US Core / CARIN / Da Vinci profiles declared in CapabilityStatement.instantiates, rest.resource.supportedProfileI1 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-16: software_version: '0.55.3' -> '0.56.0'
2026-09-22: software_version: '0.56.0' -> '0.58.0'

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	declared	token_endpoint_auth_methods_supported lists private_key_jwt among 3	SMART discovery: token_endpoint_auth_methods_supported
Declares the client_credentials grant, which SMART Backend Services uses	declared	grant_types_supported lists client_credentials among 2	SMART discovery: grant_types_supported
Declares the client-confidential-asymmetric capability	declared	capabilities lists client-confidential-asymmetric among 13	SMART discovery: capabilities
Declares system-level scopes	declared	46 of 163 scopes_supported are system/ scopes	SMART discovery: scopes_supported
Declares an export operation	declared	export is declared on Group, Patient	CapabilityStatement: rest.operation and rest.resource.operation
Instantiates the Bulk Data Access implementation guide	not listed	7 canonicals are instantiated and none is Bulk Data's	CapabilityStatement: instantiates

Registry provenance

How this entry was verified

base URL printed verbatim under 'API endpoint:' on the specification page CareSource links as 'Provider Directory Open API Specification', and cited a second time in the same page's 'Authorization / Authentication:' accordion: 'CareSource supports non-authenticated public directory endpoints.' The spec page states 'Read-only. Does not require authentication.' Live CapabilityStatement retrieved unauthenticated (recorded 2026-09-04). 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/caresource-provider-directory/">
<img src="https://fhir.chelseakr.com/badge/caresource-provider-directory.svg"
alt="FHIR Scorecard: grade A"></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.