Shared modelling rules

Use these pages while mapping EHR information. Each explains a decision shared across profiles; the profile definitions remain the source for exact field constraints.

Topic Use it to understand
Clinical coding How to use SNOMED CT concepts, expressions, coding slices, clinical reasons and terminology validation.
Dental anatomy How tooth and surface groups in bodySite relate to the complete coded meaning.
Health groups Patient classification periods, contact-specific history and update responsibilities.
References and identifiers How records identify patients, professionals and one another, and how source identifiers differ from FHIR IDs.
Reading the profiles FHIR glossary, Simplifier tables and flags, terminology bindings, source population and validation.

Status rules are profile-specific. Use a status that reflects the source information and is permitted by the consuming profile. Several profiles exclude unknown; MedicationStatement retains the standard FHIR R4 status codes, including unknown. Do not substitute a guessed status to make a record pass validation. Resolve unsupported source states in the mapping process.

The Profile map lists shared formats, extensions and project ValueSets in one place.

For a complete clinical context, open the recall-to-treatment scenario. For the applicable definition, use the Profile guide.