Review status and releases

This guide is under development. The published profiles, guidance and examples describe the current draft and may change as review and testing continue.

The use of no-basis Practitioner, PractitionerRole, Organization and Location, including stored-resource versus identifier-only references, is still being assessed. This may change reference targets, reference forms and related examples. The current constraints on each field apply to the published draft; the assessment does not introduce an alternative reference policy yet.

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

FHIR status = draft identifies a definition under development or review. The separate experimental flag identifies content intended for testing, education or evaluation rather than genuine use. Use experimental = false for definitions intended for the actual solution, even while their status is draft. This does not indicate production approval. The project readiness label describes review progress; it does not automatically set either FHIR field.

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

Names link to the current definitions on Simplifier, where their versions are maintained. No profile is currently Ready for supplier review.

Profile Readiness
Procedure In review
Observation In review
Encounter In review
Condition In review
ServiceRequest In review
MedicationRequest In review
MedicationAdministration In review
MedicationStatement In review
Appointment In review
EpisodeOfCare In review
AllergyIntolerance In development
Dental Contact Note In development
Device In development
ChargeItem In development
Claim In development
Coverage Experimental
Transaction Bundle 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 Readiness
SCTextended coding In development
SCTpre coding In development
Dental BodySite In development
Body-structure extension In development
Patient health-group history In development
Patient Health Group extension In development
Health group In development
Effective dose period In development
Off-label use In development
Rendered dosage instruction In development

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

Dental terminology and health groups

These readiness labels cover the dental ValueSets and CodeSystems reviewed here. Medication and allergy terminology retains its existing metadata and separate review ownership.

Definitions Readiness
Health Group CodeSystem and Health Groups ValueSet In review
Other current dental terminology selections and workflow code systems, excluding the test lists below In development
Contact-type comparison lists and fictional tariff/fee codes Experimental

Retired definitions keep status = retired for historical interpretation. Terminology readiness does not change the readiness of the Patient/Encounter profiles or their extensions.

Versions and releases

All DigiDOT profiles and extensions listed here have FHIR publication status draft. The readiness labels are separate from FHIR maturity (FMM) levels.

Packages and the working draft

Open DigiDOT packages (digidot.ny) to select a published release and its download, examples and dependencies. A published package is a fixed release; the Simplifier project and this current guide are updated during development. Synchronising project files does not publish a new package.

Release gap — checked 10 November 2026: the package list still shows 0.2.6 as latest. It predates this guide's current draft. A matching package release is still needed; do not validate current project examples against 0.2.6 or treat it as the implementation baseline for this draft.

For repeatable validation, keep the package version, its declared dependencies and the matching example together. During draft review, use an agreed export of the current definitions and dependencies when no matching package is available. The profile-version rules below govern submissions once EHR systems are integrated.

Profile versions

During the project period, profile changes are not individually versioned. Once EHR systems are integrated, every profile change requires a new version.

For integrated EHR systems, DigiDOT requires the profile's canonical URL and version in meta.profile on each submitted resource, including resources inside a Bundle. A Bundle's declaration does not replace those on its entries.

Example metadata fragment:

{
  "meta": {
    "profile": [
      "https://novari.no/fhir/digidot/StructureDefinition/digidot-Observation-no|0.7.0"
    ]
  }
}

Use StructureDefinition.url and StructureDefinition.version from the latest published version of the applicable profile. Use the profile version, not the package version or meta.versionId. The number above is illustrative; the submitted resource must conform to the version it declares.

DENT must reject submissions with a missing profile/version or an outdated or unsupported version. Support for multiple concurrent versions may be considered later.

The Definition index links to the definitions and guide dependencies. See FHIR R4 canonical references for the versioned reference format.

Examples and validation

The JSON catalogue identifies the type and purpose of each example. Start with the single clinic Encounter.

Validate your data

  1. Load matching definitions. Configure a FHIR R4 validator with the selected DigiDOT package or agreed draft export and its declared dependencies. Check the release gap above before using the project Encounter example.
  2. Validate the instance. Download the Encounter JSON and validate it against the DigiDOT Encounter profile version it declares in meta.profile. For a Bundle, validate the entries and their reference context together. Correct structural errors and inspect any unresolved references.
  3. Check terminology. Use a terminology service supporting the required systems and SNOMED CT edition/release. For postcoordination, validate the complete expression; see Clinical coding. A missing terminology service or unsupported check is an incomplete result.
  4. Review the result. Resolve errors and review warnings, retaining the outcome and definition versions used. Repeat with your own synthetic EHR data. Successful profile validation does not establish clinical equivalence or acceptance by the receiving service.

The FHIR R4 validation guidance describes validator tools and their scope. For the Encounter example, this checks the recorded contact; it does not create it in DENT or prove that its Patient exists there.

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.