Dental anatomy
bodySite makes a tooth or oral structure and its qualifiers available as structured data inside a clinical record. The clinical SCTextended code must express the same intended anatomical scope. This page shows the relationship; Clinical coding explains the SNOMED CT slices and validation workflow.
Open Dental BodySite profile on Simplifier ↗
Dental BodySite is a profiled CodeableConcept, not a separate patient resource. Its single body-structure extension holds the anatomical fields.
| Definition | Role in a clinical record |
|---|---|
| Dental BodySite | Defines the permitted bodySite format: one inline body-structure extension, with no coding or text on the outer CodeableConcept. Text may be supplied inside the extension, for example in location.text or description. |
| Inline body-structure extension | Defines the fields inside that format: location, locationQualifier, laterality, morphology and description. It is reused inside Dental BodySite; it is not a second anatomy record. |
The fields follow Xt-EHR EHDSBodyStructure 1.0.0. That logical model prefers SNOMED CT but does not specify these concrete ValueSets. The required terminology bindings and the dental selections below are DigiDOT choices.
location, locationQualifier and laterality are MustSupport but optional. If a qualifier or laterality is supplied, location is required in the same anatomical group. Their SNOMED CT codings reuse SCTpre, including the edition release. The primary bindings define the permitted coded scope; additional bindings identify focused dental selections without excluding non-tooth anatomy.
| Field | Required coded scope | Focused dental selection |
|---|---|---|
location |
SNOMED CT Body Structures: a tooth or another appropriate structure. | Additional preferred binding to Teeth — National Core, refset 598051000202104, for numbered teeth. |
locationQualifier |
Anatomical Location Qualifier Values: a relevant qualifier of the selected structure. | Additional UI binding to Tooth Surface Qualifier Values — Draft. Repeat the field for multiple surfaces on the same tooth. |
laterality |
Anatomical Laterality: Left or Right, where appropriate. | Do not duplicate the side already encoded by a numbered tooth. |
Tooth surfaces are part of the DigiDOT anatomy model. Record each surface as a locationQualifier attached to its tooth. The focused ValueSet currently lists Mesial 710099007, Distal 46053002, Occlusal 710098004 and Incisal 710097009; the broader binding also permits other appropriate qualifiers. See Terminology work for the remaining work on complete surface coverage.
The national Tooth Surfaces and Regions refset, 598041000202102, contains body-structure concepts, not qualifier values. It is retained as national reference terminology; it does not replace the qualifier selection. Use in clinical expressions requires a reviewed template.
For non-tooth anatomy, the same fields remain available: for example 21974007 |Tongue structure| as location, with 255554000 |Dorsal| as locationQualifier. The dental subset is not a restriction on this use.
Keep each tooth with its surfaces
Draft structure example: the fragment below shows how to keep a tooth and its qualifiers together in bodySite. It does not supply or approve a corresponding SNOMED expression. The expression proposal is separated below for terminology review.
For a record concerning tooth 15 with three surfaces, the tooth is the location. Each surface is a locationQualifier in the same group. A second tooth has its own group; its surfaces must remain attached to that tooth.
The containing resource determines whether anatomy can repeat. Condition, Procedure and ServiceRequest can carry several bodySite groups; Observation permits at most one bodySite, and separate site-specific results use separate Observations.
JSON: one tooth with three surfaces
{
"bodySite": [
{
"extension": [
{
"url": "https://novari.no/fhir/digidot/StructureDefinition/digidot-ehds-body-structure",
"extension": [
{
"url": "location",
"valueCodeableConcept": {
"coding": [
{
"system": "http://snomed.info/sct",
"version": "http://snomed.info/sct/51000202101/version/20260715",
"code": "36492000",
"display": "Structure of permanent maxillary right second premolar tooth"
}
],
"text": "Tooth 15 (ISO 3950)"
}
},
{
"url": "locationQualifier",
"valueCodeableConcept": {
"coding": [
{
"system": "http://snomed.info/sct",
"version": "http://snomed.info/sct/51000202101/version/20260715",
"code": "710099007",
"display": "Mesial (qualifier value)"
}
],
"text": "Mesial surface"
}
},
{
"url": "locationQualifier",
"valueCodeableConcept": {
"coding": [
{
"system": "http://snomed.info/sct",
"version": "http://snomed.info/sct/51000202101/version/20260715",
"code": "710098004",
"display": "Occlusal (qualifier value)"
}
],
"text": "Occlusal surface"
}
},
{
"url": "locationQualifier",
"valueCodeableConcept": {
"coding": [
{
"system": "http://snomed.info/sct",
"version": "http://snomed.info/sct/51000202101/version/20260715",
"code": "46053002",
"display": "Distal (qualifier value)"
}
],
"text": "Distal surface"
}
}
]
}
]
}
]
}
This is an anatomical fragment, not a complete clinical record. The recall-to-treatment scenario shows the workflow and references in complete example resources; its tooth–surface expressions remain proposals under terminology review.
Representation and meaning
The inline extension can also describe morphology, laterality and a textual description. Open its definition for permitted fields and cardinalities. The nested JSON is deliberate: FHIR R4 permits a complex extension with named child extensions. Here the outer extension keeps one anatomical group together; its children carry the five Xt-EHR fields. The group is an inline value, not a separate BodyStructure resource.
The sending EHR or integration must preserve the recorded tooth and surface information when generating FHIR data. For example, tooth 46 with a distal surface must retain both the tooth and the surface. This does not require a separate copy of the clinician's original wording alongside every code.
DENT is responsible for checking submitted data against the agreed profile and terminology rules. Those checks cannot detect a surface omitted from both the clinical code and bodySite before submission. The sending system must identify mapping failures and report them for resolution; this guide does not define a fallback that discards known anatomical detail or marks a less precise record as complete.
Record left/right in laterality, even though the broad locationQualifier scope also contains side concepts. A tooth without a surface is appropriate when the information concerns the whole tooth or no surface was recorded. This is different from losing a known surface during export.
When bodySite is present, check that SCTextended covers the same complete anatomical scope. A single sufficiently specific SNOMED concept is enough if it already expresses that meaning; otherwise use a validated postcoordinated expression. For several teeth, keep each tooth with its own qualifiers and check the full coded scope. Clinical coding covers the expression validation and normal-form workflow.
The inline anatomy design remains under review. It draws on the Xt-EHR logical body-structure model; it is not a claim of EHDS or exchange-profile conformance.
Terminology work
Complete dental surface coverage is required. DigiDOT's dental and terminology reviewers must complete the focused selection for buccal/labial and lingual/palatal surfaces and verify the corresponding SNOMED expression templates, including root-surface detail. Suppliers must not work around these gaps by omitting recorded surfaces. An anatomical description does not by itself establish that a coded mapping is complete.
Background: earlier surface qualifiers and the SNOMED proposal
Use active qualifier values from the bound release. Buccal 261062005, Lingual 261121002, Labial 261114002 and Palatal 261145003 were inactivated in December 2022 during the SNOMED specific-site descriptor cleanup. Their historical alternatives describe body structures, such as cheek and tongue; they are not replacements for a tooth-surface qualifier. The SNOMED dental surface proposal addresses new, unambiguous surface qualifiers. Those draft concepts are not included as published codes here.
Model proposal: expression and anatomy correspondence
Terminology review required. The following expression proposes how tooth and surface might correspond to bodySite. Its separate site groups do not establish which surface belongs to which tooth. Do not use it as an approved postcoordination template.
Inspect the proposal, comparison and JSON
code.coding:SCTextended80967001 |Dental caries| :
{ 363698007 |Finding site| =
866005003 |Structure of permanent mandibular right first molar tooth| }
{ 363698007 |Finding site| =
83473006 |Structure of occlusal surface of tooth| }bodySite
location- Tooth 46 (ISO 3950)SNOMED CT:
866005003
Structure of permanent mandibular right first molar tooth locationQualifier- Occlusal surfaceSNOMED CT:
710098004
Occlusal (qualifier value)
locationSurface ↔ locationQualifierSame colour shows the intended correspondence. Yellow marks tooth 46; blue marks the occlusal surface. The tooth uses a body structure code in both places. The surface uses a body structure code in the expression and a qualifier value in bodySite. The colours do not establish that the expression assigns that surface to that tooth.
Labels between |...| make the expression readable; they do not change the concept identifiers. The JSON below uses the compact expression and adds readable display and text values.
The recall-to-treatment scenario includes this same proposal as a Condition. The intended design is for SCTextended to carry the complete coded meaning and for bodySite to expose the same anatomy for uses such as a tooth chart. That equivalence has not yet been established for this expression. Generate both from the same source and review both if the site changes.
Expression format and validation
The example uses two separate groups, each containing one Finding site: tooth 46 first, then the occlusal surface. Their display order mirrors location and locationQualifier; changing group order alone does not change the coded meaning. Commas between adjacent groups are optional in SNOMED CT compositional grammar. This format differs from combining concepts with +; the two forms must not be assumed equivalent.
Acceptance by a generic code-validation endpoint does not establish an approved dental template, verified normal form or clinical equivalence with bodySite. Separate site groups do not themselves encode which surface belongs to which tooth. That relationship must be confirmed in the terminology/template review, especially for multiple teeth. The JSON uses the edition release required by the current profiles.
See draft example in JSON: SCTextended and bodySite
This is a fragment of the Condition in the scenario. Coding.id = SCTextended selects the slice; Coding.code contains the postcoordinated expression. All codings use the same SNOMED CT edition and release. The surface is 83473006 |Structure of occlusal surface of tooth| in the expression and 710098004 |Occlusal| in bodySite. This is the intended surface mapping; the expression's full tooth-and-surface scope remains to be verified. display and text do not establish semantic equivalence.
{
"code": {
"coding": [
{
"system": "http://snomed.info/sct",
"version": "http://snomed.info/sct/51000202101/version/20260715",
"code": "80967001:{363698007=866005003}{363698007=83473006}",
"display": "Dental caries on the occlusal surface of tooth 46",
"id": "SCTextended"
}
],
"text": "Dental caries, tooth 46, occlusal surface"
},
"bodySite": [
{
"extension": [
{
"url": "https://novari.no/fhir/digidot/StructureDefinition/digidot-ehds-body-structure",
"extension": [
{
"url": "location",
"valueCodeableConcept": {
"coding": [
{
"system": "http://snomed.info/sct",
"version": "http://snomed.info/sct/51000202101/version/20260715",
"code": "866005003",
"display": "Structure of permanent mandibular right first molar tooth"
}
],
"text": "Tooth 46 (ISO 3950)"
}
},
{
"url": "locationQualifier",
"valueCodeableConcept": {
"coding": [
{
"system": "http://snomed.info/sct",
"version": "http://snomed.info/sct/51000202101/version/20260715",
"code": "710098004",
"display": "Occlusal (qualifier value)"
}
],
"text": "Occlusal surface"
}
}
]
}
]
}
]
}
View the complete example on Simplifier or open the complete scenario for the full Condition with patient, status and contact references.