Profile guide

Choose a profile: match the information in your EHR to a record in the tables below. Profile names open the formal definitions on Simplifier; the guidance links explain when to use each record and show examples.

ServiceRequest is grouped with planning because it describes future care, although the requested service and its reason are clinical information. Based on identifies the inherited profile or resource; reference targets are specified separately in each profile.

See current profile readiness for the current status.

Patient classification (draft)

DigiDOT Patient, based on no-basis Patient, records health-group assignments with non-overlapping validity periods. Existing clinical reference targets remain no-basis Patient. See Health groups for Patient history, the optional Encounter classification and API responsibilities.

Planning and care

Profile Purpose Based on Guidance
ServiceRequest Requested or planned care, referral and recall needs. FHIR R4 ServiceRequest Guidance and examples
Appointment Proposed or booked scheduling. no-basis-Appointment Guidance and examples
Encounter One actual clinical contact. FHIR R4 Encounter Guidance and examples
EpisodeOfCare An optional period of organisational care responsibility, potentially covering several contacts. FHIR R4 EpisodeOfCare Guidance and examples

Clinical data

Profile Purpose Based on Guidance
Condition Diagnoses and clinical problems. FHIR R4 Condition Guidance and examples
Observation What was measured or assessed, and its result. FHIR R4 Observation Guidance and examples
Procedure Performed, attempted or explicitly not-performed treatment activity. FHIR R4 Procedure Guidance and examples
Dental Contact Note Authored narrative for an Encounter, or a record correction/deletion request note. Links to supporting or affected records. no-basis-Composition Guidance and examples
Device An identifiable implant, prosthesis, appliance or other relevant device. FHIR R4 Device Guidance and examples

Clinical coding explains SCTextended and its optional SCTpre companion. Dental anatomy shows how the coded meaning matches structured bodySite.

Medication and allergy

Profile Purpose Based on Guidance
MedicationRequest An authoritative medication request in dental care. FHIR R4 MedicationRequest Guidance and examples
MedicationAdministration A completed medication administration during dental care. FHIR R4 MedicationAdministration Guidance and examples
MedicationStatement Medication use reported by a person with knowledge of that use; not imported SFM/PLL information. FHIR R4 MedicationStatement Guidance and examples
AllergyIntolerance Reported allergy or intolerance when no corresponding structured record is already available; see the scope in the guidance. FHIR R4 AllergyIntolerance Guidance and examples

Finance (draft)

Profile Purpose Based on Guidance
ChargeItem Priced service with quantity and total fee, linked to one Procedure. FHIR R4 ChargeItem Guidance and examples
Claim Tariff claim to a benefit payer or insurer, with Procedure and mandatory ChargeItem links. FHIR R4 Claim Guidance and examples
Coverage Minimal patient coverage and payer record required by Claim; reused across claims. FHIR R4 Coverage Guidance and examples

Use Profile connections to inspect permitted links, or Profile map to browse shared formats, extensions and ValueSets. The Definition index is a compact lookup entry point; Norwegian base profiles explains national reuse.

For parents and other related people, see RelatedPerson and contact information. The guide reuses the national profile rather than introducing a separate DigiDOT profile.

EHDS and FHIR release assessment

The individual profile pages explain modelling choices and workflows. Use the linked formal profiles for cardinalities, permitted fields, bindings and validation rules. Shared coding, anatomy and reference guidance is linked rather than repeated on each page.

The migration notes were reviewed against published FHIR R5 (5.0.0), the R6 continuous build (6.0.0-snapshot1) and Xt-EHR EHDS Logical Information Models 1.0.0 on 5 November 2026. EHDS logical models describe information needs; they are not profiles of the FHIR resources with similar names. Xt-EHR states that these models remain subject to refinement through the EHDS implementing-act process.

HL7 Europe Base and Core provides European FHIR profiles and mapping work to assess for an actual exchange. A reference to that work is not an inheritance or conformance claim. DigiDOT's selected package dependencies and profile base definitions remain authoritative.

DigiDOT currently uses R4. R5 changes are published migration considerations; R6 development content may still change. No migration is implied by these notes. Adopting another release requires a decision on the target guide and version, mapping of existing data, updated profiles and examples, and validation of the intended exchange.