Public surface / Payer Patient Access APIs
MercyCare Health Plans Patient Access API
This endpoint declares a complete, interoperable public surface.
Observed surface
- Base URL
https://epicproxy.mhsjvl.org/FHIRproxy/api/FHIR/R4- Category
- Payer Patient Access 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
| Vantage | Result | What it saw | Condition |
|---|---|---|---|
github-actions/macos-latest | reached | answered in 155 ms | HTTP 200 |
github-actions/ubuntu-latest | reached | answered in 313 ms | HTTP 200 |
github-actions/windows-latest | reached | answered in 233 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-09-04; 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 | declared | grant_types_supported lists client_credentials among 5 | SMART discovery: grant_types_supported |
| Declares the client-confidential-asymmetric capability | declared | capabilities lists client-confidential-asymmetric among 17 | SMART discovery: capabilities |
| Declares system-level scopes | not listed | none of 5 scopes_supported is a system/ scope | SMART discovery: scopes_supported |
| Declares an export operation | not listed | 3 operations are declared and none is named export | 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
base URL published by the plan at https://www.mercycarehealthplans.com/interoperability-patient-access-rule/, section 'App developers API support', under the literal anchor text 'Patient Access API'; corroborated by the plan's own developer-guidance .docx tabling this server against 'Clinical Data, Medical Claims'. Co-hosting disclosed: epicproxy.mhsjvl.org is Mercyhealth's Epic proxy, so the payer surface and the health system's EHR appear to share one Epic instance. Recorded as the payer API because the plan publishes it as such and asserts it carries the plan's medical claims. Live CapabilityStatement retrieved (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/mercycare-patient-access/">
<img src="https://fhir.chelseakr.com/badge/mercycare-patient-access.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.