Public surface / Payer Patient Access APIs
Santa Clara Family Health Plan Patient Access API
This endpoint declares a solid public surface with minor gaps.
Observed surface
- Base URL
https://fhir.scfhp.com/baseR4- Category
- Payer Patient Access APIs
- Availability
- answered 56 of the last 56 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
| Vantage | Result | What it saw | Condition |
|---|---|---|---|
github-actions/macos-latest | reached | answered in 801 ms | HTTP 200 |
github-actions/ubuntu-latest | reached | answered in 384 ms | HTTP 200 |
github-actions/windows-latest | reached | answered in 813 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
- Needs attention: 147 profile canonical(s) declared in CapabilityStatement.instantiates, rest.resource.profile, none of them US Core, CARIN, or Da Vinci; also checked rest.resource.supportedProfile, instantiates, imports, meta.profileI1Spec ↗
- Pass: SMART discovery document present and completeI2Spec ↗
- Pass: OAuth/SMART security service declared in CapabilityStatementI3Spec ↗
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 declared: the field is absent | the document has no token_endpoint_auth_methods_supported | SMART discovery: token_endpoint_auth_methods_supported |
| Declares the client_credentials grant, which SMART Backend Services uses | not declared: the field is absent | the document has no grant_types_supported | SMART discovery: grant_types_supported |
| Declares the client-confidential-asymmetric capability | not listed | capabilities lists 9 and not client-confidential-asymmetric | SMART discovery: capabilities |
| Declares system-level scopes | not listed | none of 2 scopes_supported is a system/ scope | SMART discovery: scopes_supported |
| Declares an export operation | declared | export is declared on Group, Patient, the whole server | CapabilityStatement: rest.operation and rest.resource.operation |
| Instantiates the Bulk Data Access implementation guide | declared | instantiates http://hl7.org/fhir/uv/bulkdata/CapabilityStatement/bulk-data | CapabilityStatement: instantiates |
Registry provenance
How this entry was verified
live CapabilityStatement fetch (fhirVersion 4.0.1, 146 resource types); the publisher field reads 'Not provided', so identity rests on implementation description 'FHIR Endpoint powered by SCFHP' plus control of the scfhp.com domain, and on the plan publishing this base URL in its own developer documentation at https://www.scfhp.com/for-developers/documentation/ (recorded 2026-08-07). Re-checked 2026-08-19: live CapabilityStatement re-fetch from the davis-ca residential vantage; fhirVersion 4.0.1, 146 resource types, publisher 'Not provided', software 'no software name'.
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.