Clinical coding

This page explains how Condition, Observation, Procedure and ServiceRequest use SNOMED CT in their clinical code fields. For teeth, surfaces and the relationship between a code and bodySite, continue to Dental anatomy.

Choose a concept or an expression

A precoordinated concept is one SNOMED CT concept whose defined meaning already covers the intended detail. A postcoordinated expression combines a focus concept and refinements using SNOMED CT compositional grammar. It is one coded meaning, not a list of unrelated codes. See SNOMED CT expressions.

Clinical meaning Coding choice
Dental caries with no more specific anatomy recorded A suitable single caries concept can be enough.
Caries on the occlusal surface of tooth 46 The complete code must also express the tooth and surface: use a sufficiently specific concept or a valid refinement.

Do not discard known detail to make a broad concept appear sufficient. Postcoordination is the preferred approach for additional clinical or anatomical detail. The name SCTextended does not mean that every code must be postcoordinated; one concept is sufficient when it carries the complete meaning.

Read a postcoordinated expression

Model proposal under review: this example explains the syntax. Its tooth–surface grouping is not an approved implementation template; see the anatomy review point.

Inspect the proposed caries expression

The caries finding in the recall-to-treatment scenario has this SCTextended.code:

80967001:{363698007=866005003}{363698007=83473006}
Part How to read it in this example
80967001 The focus concept: dental caries.
: and {363698007=...} A refinement begins; the grouped attribute is finding site.
866005003 Tooth 46, in the first Finding site group; the same tooth is recorded in bodySite.location.
83473006 Occlusal surface, in a separate Finding site group; intended to correspond to the qualifier in bodySite. The grouping must still be reviewed.

The whole string is one expression in one Coding.code. Its structure helps a reader see the intended meaning; correct SNOMED grammar, allowed attributes, concept activity and clinical equivalence still need terminology validation. See the SNOMED expression syntax guide. Dental anatomy shows the same tooth and surface in bodySite.

How to read the two coding slices

The four profiles slice code.coding by the literal Coding.id, not by the SNOMED concept identifier in Coding.code:

Coding.id Cardinality when code is present Role
SCTextended 1..1 The complete intended meaning: one sufficiently specific concept or a valid postcoordinated expression.
SCTpre 0..1 An optional, compatible single-concept companion. It cannot replace a more precise SCTextended coding.

Both codings use system = http://snomed.info/sct and identify the same SNOMED CT edition and release in version. If SCTpre is broader, it must not be mistaken for the full detail in SCTextended. Do not duplicate an identical code just to populate SCTpre. Do not add a broader companion solely to match a national core list.

code is required in Condition, Observation and Procedure. ServiceRequest can omit it for a general recall identified by category and timing; when code is present, the two-slice pattern applies. See ServiceRequest use.

Which ValueSet applies where?

For Condition and Procedure, use the following selection and validation rules:

  1. Start with the national core. Choose a core concept when it represents the intended meaning. For postcoordination, prefer a suitable core concept as the focus. If the core does not cover the meaning, use another suitable concept in the corresponding hierarchy.
  2. Send the complete meaning in SCTextended. A single concept or a valid postcoordinated expression is allowed. SCTpre remains an optional single-concept companion; do not add it solely to satisfy the core selection.
  3. Validate the complete coding against the required hierarchy ValueSet, using its SNOMED edition and release. Checking only the focus concept is insufficient. Expression syntax and concept-model rules must also be checked.
Profile Preferred core on code Required scope on both coding slices
Condition Dental Findings — National Core: refset 598071000202105 Standard FHIR Clinical Findings, << 404684003
Procedure Dental Procedures — National Core: refset 598061000202101 Standard FHIR Procedure Codes, << 71388002

The local ValueSets select core concepts in compose.include. A new expression built from a core concept is not itself a member of that refset; it is permitted when the complete expression satisfies the required hierarchy ValueSet. The core binding is preferred, so failure to match the core alone is not a conformance error.

Use ValueSet/$validate-code with the required ValueSet and the complete Coding, including version. Checking membership in a returned $expand list is insufficient for expressions. The terminology service must support postcoordination; an unsupported check or structural validation alone does not establish conformance. See FHIR R4 SNOMED CT.

Observation and ServiceRequest retain their existing required bindings on code and both coding slices:

Profile Required ValueSet Allowed clinical scope
Observation Observation Codes Observable entity, << 363787002
ServiceRequest Planned Procedure Situations Planned Situation with a specific associated procedure

In all four profiles, SCTpre permits one numeric concept identifier and SCTextended permits a concept or a valid expression. Terminology tooling must check the selected SNOMED release, hierarchy membership, expression syntax and concept-model rules. A passing structural check does not establish these semantic properties.

Similar detail, different clinical meaning

The case uses postcoordination in four kinds of record. The focus concept and the attribute describing a site depend on what the record means:

Profile and case record Read the expression as Keep outside code
Condition: caries A finding at tooth 46, occlusal surface Clinical and verification status.
Observation: pocket depth The assessment at tooth 25, distal surface The result, 4 mm, in valueQuantity.
Procedure: restoration An action performed at tooth 46, occlusal surface Procedure status and time.
ServiceRequest: restoration request A planned situation containing that intended action and site Request status, intent and timing.

The same tooth and surface appear in three different statements in this case:

Condition caries finding + finding site = tooth 46, occlusal surface ServiceRequest planned situation + intended work = restoration at that site Procedure restoration done + procedure site = tooth 46, occlusal surface

This is a reading aid, not SNOMED expression syntax. Do not copy one record's code to another just because the anatomy matches. In the request, 363589002=(234789004:{...}) nests the intended restoration's coded meaning inside the planned Situation; it is not a FHIR reference to a performed Procedure. The separate Procedure record describes what was actually done. Likewise, the Observation expression identifies a pocket-depth assessment at tooth 25; its 4 mm result belongs in valueQuantity, outside the expression. Use each profile's binding and coding rules.

Case expressions — anatomical templates remain under review

Condition — caries finding:

80967001:{363698007=866005003}{363698007=83473006}

Observation — pocket depth at tooth 25:

286546002:{704327008=(23226009+90933009)}

Procedure — composite restoration at tooth 46:

234789004:{363704007=866005003}{363704007=83473006}

ServiceRequest — planned composite restoration at tooth 46:

129125009:{408730004=397943006,408731000=410512000,408732007=410604004,363589002=(234789004:{363704007=866005003}{363704007=83473006})}

These are the example Bundle's stored codes, not general templates. Their full MRCM, template, normal-form and clinical-equivalence validation has not been established. Use the selected SNOMED edition and the relevant profile before generating another expression.

Clinical reasons

ServiceRequest, Appointment and Procedure use the same Clinical Reasons ValueSet for optional reasonCode. Each reason has exactly one precoordinated SNOMED CT Coding, with its edition/release and a readable term when available.

Permitted hierarchy Meaning
<< 404684003 · Clinical finding Clinical findings, including disorders and diagnoses.
<< 413350009 · Finding with explicit context Findings with explicit context, including history, absence or family history.

Select a concept that describes the actual indication. A history or absent finding must retain that context; it does not assert a current diagnosis. When the reason is separately stored, use the consuming profile's permitted reasonReference targets. SNOMED hierarchy membership and clinical suitability need terminology validation. See SNOMED context representation.

Check anatomy consistency

The same rules apply to Condition, Observation, Procedure and ServiceRequest:

Check What it establishes
FHIR structure and coding slices The resource follows the profile. SCTextended may be used without an SCTpre companion.
SNOMED edition and release The inline anatomical codings and SCTextended use the same release. This is enforced by a separate version-comparison invariant in all four profiles.
Anatomy and grouping The code and bodySite describe the same tooth or structure, surfaces and applicable side. Each surface must remain associated with its own tooth. Equal sets of codes alone are insufficient.
Terminology and clinical meaning Concepts are valid in that release, refinements follow the applicable SNOMED rules, and the complete anatomical meaning agrees. This also applies when a single concept already includes anatomy.

A different numbered tooth or surface is a conflict. A mapping or expression form that has not been verified is unresolved, not a successful consistency check. Do not discard source detail or change the clinical code merely to make a comparison pass. A FHIR validation result alone does not establish anatomical equivalence.

Validate the meaning and return a normal form

For postcoordinated expressions, the intended integration flow is:

  1. Build the close-to-user expression from the clinical choice and record its SNOMED CT edition and release.
  2. Validate the FHIR resource against the selected DigiDOT profile, including Coding.id slices and the applicable ValueSet binding.
  3. Send the expression to a SNOMED CT terminology service with postcoordination support, such as a suitably configured Snowstorm deployment. Check compositional grammar, active concepts in the stated release, MRCM rules and any applicable clinical template.
  4. Return the validated close-to-user expression and its necessary normal form. Put the close-to-user expression in SCTextended.code; use the normal form for semantic comparison and queries, together with the release used to produce it. Report explicitly if the service cannot produce a normal form.

The necessary normal form is an inferred representation and can differ from what the clinician entered. Do not silently replace the close-to-user meaning with it. SNOMED expression forms explain the distinction. Snowstorm capabilities depend on the deployed product and configuration; SnowstormX postcoordination support is one documented implementation, not a guarantee for every endpoint.

The SCTextended profile checks only a basic code shape; a successful FHIR validation or expression parse cannot establish full clinical equivalence. The Dental anatomy page shows how to compare an expression's anatomical meaning with bodySite.