Page Status: updated 2022-03-24

MedicationRequest scenarios

Page index

Introduction

There are three different Provenance profiles for documenting valid data combinations for a Provenance related to a MedicationRequest.

In all MedicationRequest scenarios there are the following constraints on the general NLLProvenance profile.

  • the 'target' must point to a MedicationRequest resource.
  • the 'activity' must be from the value set medication-request-activity-types
  • the 'agent.who' must point to a Practitioner resource

Details

The differences between each specialtized profile and the general Provenance profile, NLLProvenance, are highlighted in black in the rendered structures below, i.e. common rules are grayed out.

Stopping (sv Avsluta) a prescription / MedicationRequest

The profile NLLProvenanceMedicationRequestStopped documents the valid data combinations in a Provencance when stopping a prescription.

When stopping a prescription there is one additional constraint:

  • the reason is mandatory (The reason when stopping can be either of the type "reason for cancellation" or "reason for change", i.e. all codes in nll-reason-for-provenance are allowed).

targetS Σ I1..1Reference(NLLMedicationRequest)
occurredDateTimedateTime
recordedS Σ1..1instant
policy0..*uri
locationI0..1Reference(Location)
systemS Σ0..1uri
versionS Σ0..1string
codeS Σ1..1code
displayΣ0..1string
userSelectedΣ0..1boolean
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

Cancelling (sv Makulera) a prescription / MedicationRequest

The profile NLLProvenanceMedicationRequestCancelled documents the valid data combinations in a Provencance when cancelling a prescription.

When cancelling a prescription there is one additional contraint

targetS Σ I1..1Reference(NLLMedicationRequest)
occurredDateTimedateTime
recordedS Σ1..1instant
policy0..*uri
locationI0..1Reference(Location)
systemS Σ0..1uri
versionS Σ0..1string
codeS Σ1..1code
displayΣ0..1string
userSelectedΣ0..1boolean
textS Σ0..0string
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

All other types of creating or updating a prescription / MedicationRequest

The profile NLLProvenanceMedicationRequestOther documents the valid data combinations in a Provencance when performing all other types of creating or updating on a patient's prescriptions.

When performing any other types of creating or updating a prescription there is one additional constraint.

  • the reason must be of the type "reason for change" nll-snomed-reason-for-change. When updating or replacing a prescription (sv uppdatera, ersätta) the reason is mandatory, otherwise it is optional and the only code allowed is "OTH" (Other).

targetS Σ I1..1Reference(NLLMedicationRequest)
occurredDateTimedateTime
recordedS Σ1..1instant
policy0..*uri
locationI0..1Reference(Location)
systemS Σ0..1uri
versionS Σ0..1string
codeS Σ1..1code
displayΣ0..1string
userSelectedΣ0..1boolean
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