Procedure
Readiness: In review.
Open Procedure profile on Simplifier
Profile base: FHIR R4 Procedure. The selected no-basis-Procedure 2.2.2 permits at most one SNOMED CT coding in its SNOMED slice. DigiDOT's extended coding plus optional companion requires a different slicing design, so this profile derives directly from R4.
Design choices
Procedure records the clinical action, while ServiceRequest represents what was planned and ChargeItem represents a financial line. Keeping these meanings separate supports a change of plan, treatment across several contacts and financial reporting without duplicating the clinical event.
The shared SNOMED and anatomy design preserves both the treatment meaning and its tooth or oral site. See Clinical coding and Dental anatomy for the reasoning and examples.
Device references remain available for concrete traceability needs. They are not a requirement to catalogue every material. A general product description can remain in the procedure note; a separately identified implant can be followed through later actions.
Use in practice
The restoration scenario connects the performed restoration to its treatment contact, request and caries finding. When treatment spans contacts, each actual action retains its own context while referring to the applicable request. An artificial parent Procedure is not needed merely to group the treatment plan.
A cancelled appointment does not prove that a specific clinical procedure was attempted or explicitly not performed. Preserve the source's actual event and explanation. A reason for refusing or stopping treatment is also different from the diagnosis that justified offering it; patient refusal must not become an invented Condition.
A completed action does not automatically establish a successful outcome or resolve the underlying diagnosis. Preserve assessment, advice and decisions in the relevant clinical records and contact note. The source's performer and recorder may differ from the importing user.
A technical action may be part of a medication administration when it is separately documented. Do not create a second record solely to repeat the same injection. See Device for implant and equipment examples and Documents and attachments for procedure reports.
EHDS and later FHIR versions
The EHDS Procedure model includes the action, time, reason, performer, anatomy, devices, outcomes and complications. Some of that wider structured content is closed in the current dental draft. Future exchange must assess those gaps; retaining narrative alone does not establish that a structured EHDS requirement is met.
FHIR R5 Procedure replaces performed[x] with occurrence[x] and combines coded/reference reasons and used items into CodeableReference structures. The R6 development model changes anatomy to bodyStructure. These require mapping of the existing event, links and inline anatomy. See the shared assessment.