Public surface / Payer Provider Directory APIs
Community Health Group Provider Directory API
This endpoint declares a complete, interoperable public surface.
Observed surface
- Base URL
https://api-chgsd-prd.safhir.io/v1/api/provider-directory- Category
- Payer Provider Directory APIs
- Availability
- answered 56 of the last 56 daily checks (100%)
- Last answered
- 2026-10-03 (answered on this run)
- Vantage agreement
- reachable from 2 of 3 vantages; not reached from github-actions/macos-latest (HTTP 429)
What each vantage saw
| Vantage | Result | What it saw | Condition |
|---|---|---|---|
github-actions/macos-latest | not reached | HTTP 429 | HTTP 429, unclassified |
github-actions/ubuntu-latest | reached | answered in 426 ms | HTTP 200 |
github-actions/windows-latest | reached | answered in 327 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
Observed since 2026-08-08; no changes to declared capability recorded.
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.
| Question | Answer | What the document says | Where it is declared |
|---|---|---|---|
| Declares private_key_jwt client authentication at the token endpoint | not listed | token_endpoint_auth_methods_supported lists 1 and not private_key_jwt | SMART discovery: token_endpoint_auth_methods_supported |
| Declares the client_credentials grant, which SMART Backend Services uses | not listed | grant_types_supported lists 1 and not client_credentials | SMART discovery: grant_types_supported |
| Declares the client-confidential-asymmetric capability | not listed | capabilities lists 12 and not client-confidential-asymmetric | SMART discovery: capabilities |
| Declares system-level scopes | not listed | none of 44 scopes_supported is a system/ scope | SMART discovery: scopes_supported |
| Declares an export operation | not listed | 0 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, 8 Plan-Net resource types). The document identifies no deployment: it is the Da Vinci PDex Plan-Net implementation guide's own CapabilityStatement served verbatim, with publisher 'HL7 Financial Management Working Group' and the canonical hl7.org url. Attribution to Community Health Group rests on the plan publishing this exact capability-statement URL at https://www.chgsd.com/about-us/fhir-developer-api; the host is the Onyx SAFHIR platform (recorded 2026-08-07). Re-checked 2026-08-19: live CapabilityStatement re-fetch from the davis-ca residential vantage; fhirVersion 4.0.1, 8 resource types, publisher 'HL7 Financial Management Working Group', software 'no software name'.
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/chg-provider-directory/">
<img src="https://fhir.chelseakr.com/badge/chg-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.