Terminology sources and draft status

A DigiDOT ValueSet selects codes for a field; it does not necessarily introduce new codes. The code system identifies who defines their meaning. Always use the system URI specified by the selected coding, not the ValueSet URL.

Source Examples What DigiDOT defines
SNOMED CT and national reference sets Teeth, tooth surfaces, dental findings and procedures Selection rules and profile bindings; the clinical concepts remain SNOMED CT concepts.
HL7/FHIR terminology Encounter classes and request/contact statuses The permitted subset of standard codes.
Supplied business classification Health groups A local CodeSystem publishing the supplied list and a ValueSet selecting its codes. Source ownership and lifecycle still need confirmation.
Local draft classifications Clinical categories Interim definitions requiring review of standard alternatives and clinical/workflow needs.
Test and historical terminology Demo tariffs; historical local Observation codes Demo tariffs have no official financial meaning. Historical Observation codes are retained for interpretation and must not be used in new current-profile instances.

Selection lists and allowed scope

Condition and Procedure use the national dental refsets as preferred selections on code. Their coding slices have required bindings to the standard FHIR hierarchy ValueSets, allowing other suitable concepts and expressions when the core does not cover the meaning. Prefer a suitable core focus concept when postcoordinating. Observation and ServiceRequest retain their existing required clinical bindings. See the binding table.

The local core ValueSets select refset members in compose.include; they do not combine the refset with the entire hierarchy. Teeth and Tooth Surfaces are anatomical helpers; use the actual location and locationQualifier bindings and the dental anatomy guidance.

Encounter.type uses a preferred SNOMED CT selection: five existing contact concepts, informed by US Core and the Norwegian dental procedures core. The selection is explicit; no local contact-type CodeSystem is required.

Local code governance

The local tariff CodeSystem publishes its complete currently defined list, even though its status remains draft. Complete content does not mean clinical approval. Case-sensitive code comparison is explicit; use the published spelling. Observation.method now reuses the standard FHIR SNOMED-based ValueSet. Device.type likewise reuses the standard FHIR SNOMED-based Device Type ValueSet. The earlier local Device Types, Observation Methods and unbound Personnel Types lists are retired and retained for historical interpretation. Qualifications, workplace roles and application permissions require distinct representations.

Observation methods and category markers are not declared equivalent to SNOMED or national codes solely because their labels look similar. Proposed replacements need an agreed meaning, mapping and migration path. ServiceRequest recall behavior depends on its existing local category codes.

Examples and validation

Use the selected examples in Examples in JSON. The historical section identifies older scenarios containing local Observation coding and an earlier health-group classification. Their preservation does not imply conformance to current profiles.

SNOMED expression syntax, ValueSet membership and clinical/anatomical agreement are separate checks. Validate the complete expression against its required ValueSet using the stated SNOMED edition and release. A numeric expansion or structural validation alone is insufficient. Verify the integration terminology service with both accepted expressions and expressions outside the required hierarchy; unsupported validation is not successful validation. See Clinical coding.

For exact current ValueSet and CodeSystem references, use the profile map and the profile bindings.