Single-endpoint report

HAPI FHIR public test server (R4): 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.

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.

What would change this

Ordered by the points each would recover. Every item below comes from a check that actually ran on this run; nothing derived from a check that did not run appears here. The three dimensions are weighted, so recovering points does not guarantee a different letter — how we grade gives the weights.

1. Declare the implementation guide's canonical URLs. Any of five conformance elements is read: rest.resource.supportedProfile, rest.resource.profile, instantiates, imports, or meta.profile. The finding above names where this project looked and what it found there.

   Worth up to 40 of the 100 points in Interop readiness.

   This run observed: 151 profile canonical(s) declared in CapabilityStatement.instantiates, rest.resource.profile, rest.resource.supportedProfile, none of them US Core, CARIN, or Da Vinci; also checked instantiates, imports, meta.profile

   I1: what this check isSpec ↗

2. Publish .well-known/smart-configuration at the base URL, carrying at least authorization_endpoint and token_endpoint.

   Worth up to 35 of the 100 points in Interop readiness.

   This run observed: SMART .well-known/smart-configuration absent or incomplete

   I2: what this check isSpec ↗

3. Declare the authorization surface in the CapabilityStatement itself, at rest[].security.service, as well as in SMART discovery.

   Worth up to 25 of the 100 points in Interop readiness.

   This run observed: no OAuth security service declared

   I3: what this check isSpec ↗

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

live CapabilityStatement fetch; publisher confirmed as HAPI FHIR reference server (recorded 2026-08-04). 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 'HAPI FHIR Server 8.11.16-SNAPSHOT/7e7129efb5/2026-07-08'.

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.