Dental Contact Note

Readiness: In development.

Open Dental Contact Note profile on Simplifier

Profile base: no-basis-Composition, including its Norwegian journal-note classification.

Design choices

Composition brings the clinician's narrative and selected supporting records together without turning every sentence into a separate coded resource. Structured findings, measurements and treatment remain independently usable. There is no fixed journal template: a brief note can be short, while a complex assessment can have several sections.

DigiDOT stores the note as a separately addressable Composition. This supports linking and updating it alongside other clinical records. A complete FHIR document requires document packaging; a transaction used to store the note is a different exchange mechanism. See FHIR R4 documents.

The project chose one responsible practitioner author per note. Clinicians documenting the same contact can each produce a separate note, while one note can discuss several Conditions. Authorship, actual attestation and the person submitting data have different responsibilities.

Use in practice

A contact note can explain the assessment, treatment choices, advice actually given and agreed follow-up. Link existing findings when relevant rather than recreating them at every visit. A later note can discuss an earlier Condition without changing the finding's originating Encounter.

The narrative also preserves information that is not fully represented by a code, such as why treatment was deferred. Planned instructions do not prove advice was delivered, and a retained referral letter does not prove it was sent. When documenting an actual disclosure, retain what was shared, its recipient, time and responsible sender; the referral example illustrates this distinction. The note does not itself enforce access restrictions.

Requests to correct or delete journal information

The same profile is reused for a separate note about a record-correction or deletion request. This avoids creating a second note profile or an artificial contact merely to document an administrative decision. The workflow determines when a contact link is applicable; this distinction is not enforced by a profile invariant.

For example, a new note can record the patient's request to remove a passage, the affected note version, the refusal and its reasons, and what was communicated to the patient. That decision note does not itself amend or delete the original entry.

Updating a note or adding another note

An amendment changes the same logical note. A separately authored addendum adds another record to be read with the original. A replacement or translation similarly has its own identity and a relationship to the earlier note. The profile defines the identifiers, statuses and relationship codes for each case.

Preserving the earlier clinical state requires retained history and, where needed, references to specific versions. An unversioned link to a changing clinical record does not freeze its content. Finishing an Encounter, finalising a note and recording an attestation are separate events; none alone establishes a digital signature.

EHDS and later FHIR versions

The EHDS Document model provides a comparison for document identity, authorship, versions and attestation. Sharing an EHDS patient summary or report would also require the applicable document profile, content and packaging; a local contact note alone is not that exchange document.

FHIR R5 Composition changes document relationships to RelatedArtifact, changes attestation mode and introduces a business version. The R6 development model revises the relationship structure again. Amendment and attestation mappings must therefore be checked against the chosen release. See the shared assessment.

Example Scenario
Minimum note / contact-and-note transaction Note content and atomic submission are separate concerns.
Two Conditions One note discusses more than one finding.
Attestation / amendment history / addendum Different document lifecycle events; the history example is not a submission transaction.
Refused deletion / refused correction / reference context Separate decision notes identifying the affected record.
Allergy and reported medication context Selected supporting records retain their own meaning and provenance.

For attached PDFs and other documents, see Documents and attachments. The use of no-basis DocumentReference remains subject to the separate document-reference assessment.