Public surface / Payer Provider Directory APIs
Health Care Service Corporation Provider Directory API
This endpoint could not be reached from any vantage on this run, so nothing about what it publishes was observed.
Observed surface
- Base URL
https://api.hcsc.net- Category
- Payer Provider Directory APIs
- Availability
- answered 0 of 2 checks so far; availability is reported once 14 observations exist
- Vantage agreement
- not reached from any of the 3 vantages tried, all on one network (github-actions), so this run cannot separate an endpoint that is down from one that does not answer this network: HTTP 500
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 →Findings
Observed since 2026-08-19; no changes to declared capability recorded.
Registry provenance
How this entry was verified
Listed on the organization's own publication of this base URL, not on a retrieved conformance document: base URL printed verbatim on Health Care Service Corporation's own interoperability site, on the Provider Directory API page, as 'API endpoint base url: https://api.hcsc.net', with the instruction to substitute it for {environmentBaseUrl} in the paths the downloadable API spec gives. The page covers the Blue Cross and Blue Shield plans HCSC operates in Illinois, Montana, New Mexico, Oklahoma and Texas, so the entry is named for the corporation rather than for the Texas brand: one address serves five state plans and nothing in it distinguishes them. Blue Cross and Blue Shield of Texas's own domain publishes no interoperability or developer page at all; its 583-URL sitemap contains none (recorded 2026-08-19). Published at https://interoperability.hcsc.com/s/provider-directory-api. On the verification date this probe observed: HTTP 500 to a GET of /metadata. TLS is clean from this vantage with and without certificate verification, so the host is live and the server is erroring at the conformance path FHIR R4 requires every server to publish. The page prints this string as a base URL to substitute into spec paths rather than as a FHIR base, which is recorded here rather than repaired: no other address for this surface is printed, and constructing one would be a guess. 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 status
Link the badge back to this evidence page so readers can inspect the current findings.
<a href="https://fhir.chelseakr.com/endpoint/hcsc-provider-directory/">
<img src="https://fhir.chelseakr.com/badge/hcsc-provider-directory.svg"
alt="FHIR Scorecard: not observed on the latest run"></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.