Certified Health IT - continuous compliance

FHIR R4 Conformance Monitor

45 CFR 170.404(b)(2) requires certified health IT developers to publish their service base URLs in a machine-readable FHIR R4 Bundle of Endpoint and Organization resources. This monitor checks a published Bundle against the standard, observes the endpoints it advertises, and produces an evidence package a reviewer can re-derive. It is a working demonstration of continuous, auditable compliance monitoring over public artifacts.

Reads only publicly published conformance artifacts. No authentication is sent, no patient data is requested, and nothing is stored.

FHIR R4 conformance

Endpoint status, connectionType, payloadType and address validated at true specification cardinality, plus Organization and Bundle cross-references.

Real-world observation

Live retrieval of the unauthenticated CapabilityStatement, R4 version and server-mode checks, and endpoint drift between snapshots.

Evidence, not opinion

Every finding cites its authority. Every observation carries a SHA-256, timestamp, status and headers so a reviewer can re-derive it.

No PHI by construction

Clinical FHIR paths are refused in code. Only public conformance artifacts are ever requested.

What is checked, and on whose authority

Endpoint cardinality is enforced as published in the FHIR R4 specification: status, connectionType and address are 1..1, payloadType is 1..*. Endpoint.status is validated against the EndpointStatus value set. Organization is checked against FHIR constraint org-1, then against the name, location, facility identifier and endpoint-reference expectations for a Service Base URL list. Availability failures are classified into the standard taxonomy: not found, timeout, redirect that obscures the published location, malformed response, inaccessible content, and content that is not machine-readable. Every finding names the rule it comes from, so a program rule is never mistaken for a FHIR rule.

Outbound requests are restricted to public https hosts on the default port. Private, loopback and link-local addresses are refused, and the check is repeated on every redirect. Clinical FHIR paths are refused outright: this monitor requests conformance metadata only and is not capable of retrieving patient data.