Compatibility

What Records connects to, validates against, and supports today. Continuous proof for your FHIR infrastructure.

Native support for the two most dominant release standards and their core data structures.

Tested extensively against HAPI, Firely, Medplum, Blaze, Spark, and SMART Health IT.

Deep engine coverage across Structure, Profiles, Terminology, References, Invariants, Custom Rules, Metadata, and Anomaly.

Validation capabilities for German MII/ISiK, NHS UK, US Core, and other international IGs.

Technical surface

Details on exactly what we support and how we connect.

FHIR version	R4, R5 (R6 preview — structural + profile validation only)
German profiles	MII, ISiK, KBV
International profiles	NHS UK, Synapxe (Singapore), CH EPR (Switzerland), Nictiz (Netherlands), HL7 Europe, IPS, US Core
Tested servers	HAPI, Firely (Vonk), Blaze, Spark, Medplum, SMART Health IT
Terminology servers	HL7 tx.fhir.org (R4, R5), CSIRO Ontoserver, custom
Authentication	OAuth2 Client Credentials, Basic Auth, Bearer Token, Open
Resource types	All R4/R5 types (auto-discovered from server capability statement)
Validation aspects	Structure, Profile, Terminology, Reference, Invariants, Custom Rules, Metadata, Anomaly
Deployment	On-prem (Docker/K8s), air-gapped, SaaS