Review status and releases

This page shows the current DigiDOT profile versions and project readiness. Readiness describes the stage of development and review; it is separate from version numbers and FHIR publication status.

What the readiness labels mean

Readiness Meaning
Experimental Early modelling for comparison and discussion; scope and design may change substantially.
In development Design, documentation and examples are being developed; fields and rules may change.
In review Internal review of the profiles, rules, guidance and examples is in progress; changes may follow.
Ready for supplier review Internal review of the identified revision is complete. Suppliers can read the profile and provide optional feedback; this is not a formal consultation round or production approval.

Current progress

Profiles are listed by version, highest first. Names link to their definitions on Simplifier. No profile is currently Ready for supplier review.

Profile Version Readiness
Condition 0.6.7 In review
Observation 0.6.7 In review
Procedure 0.6.7 In review
MedicationRequest 0.6.5 In review
MedicationAdministration 0.6.5 In review
MedicationStatement 0.6.5 In review
ServiceRequest 0.6.4 In review
Encounter 0.6.4 In review
Appointment 0.6.3 In review
EpisodeOfCare 0.6.3 In review
AllergyIntolerance 0.5.1 In development
Dental Contact Note 0.4.5 In development
Device 0.4.1 In development
ChargeItem 0.1.2 Experimental
Claim 0.1.2 Experimental
Shared datatypes and extensions

These definitions have their own readiness labels. Dental BodySite and its body-structure extension are two parts of the same inline anatomy format.

Definition Version Readiness
SCTextended coding 0.4.0 In development
SCTpre coding 0.4.0 In development
Dental BodySite 0.4.0 In development
Body-structure extension 0.4.0 In development
Health group 0.4.0 In development
Effective dose period 0.4.0 In development
Off-label use 0.4.0 In development
Rendered dosage instruction 0.4.0 In development

See Profile map for how the definitions and ValueSets are used together.

Versions and releases

All DigiDOT profiles and extensions listed here have FHIR publication status draft. The readiness labels are project labels, not FHIR maturity (FMM) levels. Completing a Jira task does not automatically change a profile's readiness.

A profile version identifies one revision; a package version identifies a set of definition revisions and dependencies. Neither indicates readiness or approval. Current definitions use numeric versions without -test; their canonical URLs retain their identity.

The Definition index lists versions and dependencies. The version identifier map records previous identifiers. Earlier review and validation results retain the versions actually checked.

Examples and validation

The example scenario shows how the records fit together. See validation scope and limitations for the recorded checks. FHIR structural validation is separate from terminology validation and clinical acceptance.

This guide is a working draft for review and mapping, not a frozen implementation baseline. National profiles have their own publication status; see Norwegian base profiles.