Skip to main content

Single-endpoint report

MercyCare Health Plans Patient Access API: endpoint report

Everything this project observed about this one endpoint, everything it did not observe, and what would change the result. Free to read, link, print and hand on; there is nothing here behind a sign-in and nothing to buy.

Built to print. Use your browser’s print or “Save as PDF” to keep a dated copy; the page carries its own address and observation date.

Grade on this run

Grade
A
Category
Payer Patient Access APIs
Base URL observed
https://epicproxy.mhsjvl.org/FHIRproxy/api/FHIR/R4
Reach on this run
Reached from 3 of 3 reporting vantages, sitting on 1 network. Vantages on one network are one network's view sampled several times.
Last answered
2026-10-03 (answered on this run)
Availability
answered 30 of the last 30 daily checks (100%)
Observed
2026-10-03 15:21 UTC

What was observed, and what was not

This report covers 9 checks. 9 ran. 0 were asked from every reporting vantage and answered by none. 0 were never asked, because nothing was retrieved for them to read. The three are different facts and none of them is a zero: a check that did not run publishes no number, no mark against this endpoint, and nothing below to act on.

Reachability

Reachability: 100 out of 100
CheckStateWhat this run observed
R1 Pass/metadata answers with HTTP 2xx over HTTPS: 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
R2 Pass/metadata responded in 233 ms (median across 3 reachable vantages on one network)

Capability transparency

Capability transparency: 100 out of 100
CheckStateWhat this run observed
T1 PassfhirVersion declared: '4.0.1' (expected 4.x)
T2 Passsoftware name and version declared
T3 Pass59 resource types declared
T4 Pass59/59 declared resources document their interactions

Interop readiness

Interop readiness: 100 out of 100
CheckStateWhat this run observed
I1 PassUS Core / CARIN / Da Vinci profiles declared in CapabilityStatement.instantiates, rest.resource.supportedProfile
I2 PassSMART discovery document present and complete
I3 PassOAuth/SMART security service declared in CapabilityStatement

What each vantage saw

reached from 3 of 3 reporting vantages, on 1 network
VantageResultWhat it sawCondition
github-actions/macos-latestreachedanswered in 155 msHTTP 200
github-actions/ubuntu-latestreachedanswered in 313 msHTTP 200
github-actions/windows-latestreachedanswered in 233 msHTTP 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.

What would change this

Nothing is listed here: every check that ran passed. Checks that did not run are in the section above, and they are not failures.

If this does not match what you see

Every number here describes two public documents at one moment, read from the vantages listed above. If it does not match what you serve, the difference is worth knowing.

Correct or dispute this record. There is no sign-in, no fee, and nothing to buy: this report is free to read, link, print and hand on, and this project collects nothing about the people who read it.

Where this came from

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.

The same run, as data: this endpoint's JSON, what its CapabilityStatement declares, resource by resource, and every observation on record for it, with the dates it answered and the dates it did not.

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. Grades are comparable within a category only. See how we grade.