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 | Included in the pinned 23 July 2026 cross-version Java-parity report |
| 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 |
R4 · Tested
What the status means
R4 is supported, but the dated 536/536 report combines in-scope R4, R5, R6, and unversioned JSON comparisons rather than measuring R4 alone or guaranteeing later builds.
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. The cross-version headline lane is not a package-coverage claim.
R6 · Preview
Preview boundary
R6 findings retain an explicit limited-support status and must not be presented as production-equivalent coverage.
Server interoperability
Records reads the capability the server declares.
Records connects through standard FHIR APIs, then resolves resource types, interactions, search parameters, paging, and authentication in the context of that server. A vendor name alone is not a compatibility guarantee.
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.
Search compatibility
Carry a supported SearchParameter into the real Browse workflow.
The inventory shows what the connected server declares. The next frames prove that Records can turn that declaration into an exact, reviewable cohort instead of treating search support as a static checklist.
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.
Need a package or server combination not listed here? Request a scoped compatibility review.
Make missing profile context visible before it changes a result.
The profile overlay shows the hidden state, the selected scope, and the required context that is still missing—without changing source data.
