Compatibility
What Records connects to, validates against, and supports today. Continuous proof for your FHIR infrastructure.
FHIR R4 & R5
Native support for the two most dominant release standards and their core data structures.
6 Server Implementations
Tested extensively against HAPI, Firely, Medplum, Blaze, Spark, and SMART Health IT.
7 Validation Aspects
Deep engine coverage across Structure, Profiles, Terminology, Invariants, and Custom Rules.
8 Profile Ecosystems
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) |
| 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 | 146+ (auto-discovered from server capability statement) |
| Validation aspects | Structure, Profile, Terminology, Reference, Invariants, Custom Rules, Metadata |
| Deployment | On-prem (Docker/K8s), air-gapped, SaaS (coming soon) |
Profile ecosystems
International Implementation Guides tested with the Records validation engine.
- ·MII Kerndatensatz (Person, Labor, Diagnose)
- ·ISiK Basismodul (Patient, Diagnose)
- ·KBV (eRezept, eAU)
- ·NHS Digital Patient
- ·UK Core
- ·Synapxe Patient (Healthier.sg)
- ·CH EPR (Vaccination Record)
- ·CH VACD
- ·nl-core-patient (Nictiz)
- ·IKNL Oncology (ACP)
- ·HL7 Europe ePrescription (EU EPS)
- ·IPS (International Patient Summary)
- ·US Core
- ·AU Base
Don't see your stack?
Records validates FHIR-conformant servers via standard REST API. If your server speaks FHIR, Records can validate it.