Developers · Compatibility
Compatibility is a matrix, not a badge.
FHIR release support, server interoperability, profile coverage, and published validation evidence are separate questions. Records states each one explicitly.
Product contract reviewed 25 August 2026
FHIR release support
A public entry point accepting a version is not the same as a published conformance result for that version.
| FHIR release | Public entry points | Validation status | Published evidence |
|---|---|---|---|
| R4 | Supported | Tested | Historical archive and a dated September diagnostic comparison |
| R4B | Supported | Compatibility | Release identity and hl7.fhir.r4b.core#4.3.0 pin preserved |
| R5 | Supported | Supported | Version-aware core and implementation-guide loading |
| R6 | Accepted | Preview | Pinned hl7.fhir.r6.core#6.0.0-ballot4 base package |
Evidence reviewed on 28 September 2026: the 21 September diagnostic run contains unresolved R4, R5, MII and EPS comparisons, and no completed precision measurement. Read the dated results and their limits before interpreting the historical archives as evidence for a current package.
R4 · Tested
What the status means
R4 support is package-specific. The 21 September diagnostic report retains two failed comparisons under explicit gate exceptions. Historical archives do not establish a current-package conformance score.
R4B · Compatibility
What the status means
The current engine uses the explicit R4 maintenance adapter internally; treat package-specific behavior as a compatibility question.
R5 · Supported
What the status means
Coverage depends on the exact package, terminology source and validation aspect. Four comparisons failed in the 21 September diagnostic run; historical results are not a current-package coverage claim.
R6 · Preview
Preview boundary
R6 findings retain an explicit limited-support status and must not be presented as production-equivalent coverage.
Compare the declared server surface with a concrete target.
Records turns the CapabilityStatement into a reviewable readiness result for a pinned target such as ISiK, IPS, IPA, or an EU Patient Summary lane.
Test another requirement against the same resource.
Compare the same synthetic Patient against FHIR R4 and ISiK Patient 5.1.3. Inspect the patient-number requirement, add the MR identifier type, then verify the correction under the same ISiK profile.
This compares an instance under selected requirements. It does not prove that one profile is compatible with another for every conforming instance.
Profile and implementation-guide coverage
Coverage belongs to the exact package and version used by a run, not to a country or programme label.
Measured evidence
Validator parity lane
Review the pinned test-suite commit, executed comparisons, and exclusions behind the published result.
Market context
German profile packages
See package-specific status for ISiK, MII, KBV, and related German implementation contexts.
Evidence lane
HL7 Europe Base/Core
Inspect a concrete package, field-level finding, and resulting evidence record.
Records
Apply a supported search parameter
Choose a supported Patient search parameter, apply a value and inspect the matching source resource.
Records
Find resources declaring a profile
Filter Browse by an exact canonical profile while retaining the selected server context.
Need a package or server combination not listed here? Request a scoped compatibility review.