Public surface / Payer Patient Access APIs
22 Health (Community Care Plan) Patient Access API
This endpoint answers publicly but declares little about itself.
Observed surface
- Base URL
https://ccpcmsioapi.zeomega.com/t/ccpprd.com/fhir/r4- Category
- Payer Patient Access APIs
- Availability
- answered 44 of the last 45 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
| Vantage | Result | What it saw | Condition |
|---|---|---|---|
github-actions/macos-latest | reached | answered in 274 ms | HTTP 200 |
github-actions/ubuntu-latest | reached | answered in 427 ms | HTTP 200 |
github-actions/windows-latest | reached | answered in 266 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-20; 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 | 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 | 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 4 and not client-confidential-asymmetric | SMART discovery: capabilities |
| Declares system-level scopes | declared | 1 of 4 scopes_supported are system/ scopes | SMART discovery: scopes_supported |
| Declares an export operation | declared | export is declared on the whole server | 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. The base URL is printed verbatim, in a table headed 'Base URLs for connecting to these APIs are', on the issuer's own /api/ page; the host is the vendor's (ZeOmega HealthUnity), so attribution rests on the plan printing this exact string on its own domain. Two things the document declares are recorded rather than tidied: fhirVersion is 4.0.0, not the 4.0.1 every other listed endpoint declares, and it carries no software element, identifying itself only as 'ZeOmega FHIR R4 Implementation' dated 2021-01-01. The Drug Formulary base URL printed in the same table answers 404 and is in the candidate log (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.
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.