Condition

Readiness: In review.

Open Condition profile on Simplifier

Profile base: FHIR R4 Condition. The selected no-basis 2.2.2 package has no Condition profile.

Design choices

A Condition gives a finding or diagnosis an identity that can be followed across visits. Measurements supporting it remain Observations, and treatment remains Procedure. This avoids creating a new diagnosis whenever the same finding is discussed or treated.

The clinical coding and anatomy follow the shared DigiDOT design. See Clinical coding and Dental anatomy for the rationale and examples.

For categorisation, DigiDOT reuses the FHIR workflow categories and the dental marker from HL7 Dental Data Exchange STU1. The latter is an existing HL7 CodeSystem with draft status within that publication, not a DigiDOT invention or an EHDS requirement. Reusing its code does not mean inheriting the US profile. A missing dental marker must not be interpreted as non-dental.

Use in practice

In the recall-to-treatment scenario, caries is found at the examination and treated later. The original finding is reused, retaining the contact where it was recorded. A later note can discuss it without moving that originating contact.

Completing a Procedure does not automatically resolve the Condition. Clinical state and diagnostic certainty answer different questions: a resolved finding can still be confirmed, while an assertion recorded in error is a different case. Historical records with unknown clinical state need an agreed source mapping rather than an invented status; the current profile's status requirement remains a review point for that mapping.

Preserve who made the assertion and who recorded it when known. An importing user or an Encounter participant does not automatically take either role. Supporting measurements and source documents should be linked only where an evidence relationship is established. Assessment and reasoning can remain in an authored Dental Contact Note.

EHDS and later FHIR versions

The EHDS Condition model distinguishes the problem, clinical state, diagnostic certainty and anatomy. These are relevant mapping concepts. Its wider content, including severity and staging, must be assessed against the selected exchange use case; the narrow DigiDOT profile does not establish complete EHDS coverage.

FHIR R5 Condition replaces recorder/asserter with participants, changes evidence to CodeableReference and changes clinical-status requirements. The R6 development model changes anatomy to bodyStructure. A migration must therefore map attribution, status and the existing inline anatomy explicitly. See the shared assessment.