MedicationAdministration
Readiness: In review.
Open MedicationAdministration profile on Simplifier
Profile base: FHIR R4 MedicationAdministration.
Design choices
The current scope is a completed administration during dental care. It preserves what was actually given, separately from a prescribing decision or a patient's account of medication use. An order alone is not evidence of administration.
The profile records the clinical drug directly as a code rather than requiring a separate Medication instance. That supports the narrow event record; it does not provide a comprehensive medicinal-product catalogue or an external prescribing workflow.
Procedure is retained only where there is a distinct clinical action to document. Creating a second Procedure solely to repeat the same administration would add duplication without another clinical meaning.
Use in practice
A dose administered during treatment belongs to that contact. A separate prescription for later use remains a MedicationRequest, and a patient's account of taking the medicine remains a MedicationStatement.
The current administration profile does not support a direct request link. An integration must not infer an order-to-administration relationship from the same patient and date. If reliable order fulfilment becomes a requirement, that gap needs an explicit profile decision.
EHDS and later FHIR versions
The EHDS Medication administration model includes status, administered medication, time, reason and dosage. Its lifecycle is broader than this completed-event scope. Future exchange must assess both event coverage and the representation of medication details.
FHIR R5 MedicationAdministration changes medication and performer representation to CodeableReference and changes the timing and encounter fields. Migration must preserve the actual event and attribution; it does not automatically reopen the local workflow scope. See the shared assessment.
See Medication and allergy for the comparison of orders, administrations and reported use.