Page Status: updated 2022-03-24

MedicationDispense scenarios

Page index

Introduction

There is one Provenance profile, NLLProvenanceMedicationDispense, defined for documenting valid data combinations for a Provenance related to a MedicationDispense.

This provenance profile documents scenarios related to both the scenario when the dispense is authorized by a prescription in electronic format, NLLMedicationDispense, and dispenses which are autorized by paper prescriptions NLLDispensePaperPrescription.

Details

The differences between the NLLProvenanceMedicationDispense profile and the general NLLProvenance profile are highlighted in black in the rendered structure below, i.e. common rules are grayed out.

When creating or updating a patient's dispenses there are a number of additional constraints:

  • the 'target' must point to a MedicationDispense resource. (NB! If the state of a MedicationRequest is affected by the activity in the provenance, that MedicationRequest will be referenced in the provenance as well. This is calculated by the National Medication List. )
  • the 'reason' may only be given as text (not a code)
  • the 'activity' must be from the value set medication-dispense-activity-types
  • the 'agent.who' must point to a Practitioner resource

targetS Σ I1..*Reference(NLLMedicationDispense | NLLDispensePaperPrescription | NLLMedicationRequest)
occurredDateTimedateTime
recordedS Σ1..1instant
policy0..*uri
locationI0..1Reference(Location)
textS Σ0..1string
systemS Σ0..1uri
versionS Σ0..1string
codeS Σ1..1code
displayΣ0..1string
userSelectedΣ0..1boolean
textΣ0..1string
typeS Σ1..1CodeableConceptBinding
role0..*CodeableConcept
whoS Σ I1..1Reference(NLLPractitioner)
onBehalfOfI0..1Reference(Practitioner | PractitionerRole | RelatedPerson | Patient | Device | Organization)
roleΣ1..1codeBinding
whatΣ I1..1Reference(Resource)
agent0..*see (agent)
signature0..*Signature