Skip to content

Mobile-ID Digital TrustISO/IEC 27001:2022 · SIS351224I008Published certification scope

View evidence

DEVELOPER

FHIR R4 Profiles

Exchange supported FHIR R4 resources with stable identifiers, profile validation, terminology discipline and source provenance.

01 / CONCEPT

Integration contract

01

Identifiers

Preserve assigning system and source identifier; do not merge identities from value alone.

02

Core resources

Patient, Observation, DiagnosticReport, Appointment and Consent are profiled by use case.

03

Terminology

Use configured code systems/value sets and explicit UCUM-like units where the implementation profile requires them.

04

Validation

Return actionable OperationOutcome-style diagnostics for profile or terminology failure.

02 / WORKFLOW

From sandbox to evidence

01Resolve profile and identifier policy
02Construct resource with profile metadata
03Validate required elements/terminology
04Submit synthetic resource
05Handle OperationOutcome
06Preserve provenance/version on correction

03 / EXAMPLE

Manage Consent

cURL / pseudocode

POST /fhir/Consent  # synthetic consent state; preserve version/provenance

04 / SECURITY & PRODUCTION

Production is an evidence decision

FHIR conformance requires the supported profile, identifier/terminology policy and correction/provenance behavior; generic FHIR R4 validity alone is not sufficient.