HL7 FHIR Implementation Guide: Sri Lanka
0.1.0 - STU1

HL7 FHIR Implementation Guide: Sri Lanka, published by Jembi Health Systems. This is not an authorized publication; it is the continuous build for version 0.1.0. This version is based on the current content of https://github.com/jembi/Sri-Lanka and changes regularly. See the Directory of published versions

## Resource Profile: DrugDispensation - Mappings

Active as of 2023-11-10

Mappings for the drug-dispensation resource profile.

### Mappings for Workflow Pattern (http://hl7.org/fhir/workflow)

DrugDispensation
MedicationDispense | Event
identifier | Event.identifier
partOf | Event.partOf
status | Event.status
statusReason[x] | Event.statusReason
medication[x] | Event.code
medication[x] (medicationCodeableConcept) | Event.code
subject | Event.subject
context | Event.context
performer | Event.performer
actor | Event.performer.actor
authorizingPrescription | Event.basedOn
whenHandedOver | Event.occurrence[x]
note | Event.note

### Mappings for RIM Mapping (http://hl7.org/v3)

DrugDispensation
MedicationDispense | Entity. Role, or Act, Supply[moodCode=EVN]
text | Act.text?
contained | N/A
extension | N/A
modifierExtension | N/A
identifier | .id
partOf | .outboundRelationship[typeCode=COMP]/target[classCode=PROC,moodCode=EVN]
status | .statusCode
statusReason[x] | .outboundRelationship[typeCode=RSON]/target[classCode=OBS,moodCode=EVN, code="not done reason"].value
category | .inboundRelationship[typeCode=COMP].source[classCode=OBS, moodCode=EVN, code="type of medication dispense"].value
medication[x] | .participation[typeCode=PRD].role
medication[x] (medicationCodeableConcept) | .participation[typeCode=PRD].role
subject | .participation[typeCode=SBJ].role[classCode=PAT]
context | .inboundRelationship[typeCode=COMP].source[classCode=ENC, moodCode=EVN, code="type of encounter or episode"]
supportingInformation | .outboundRelationship[typeCode=PERT].target[A_SupportingClinicalStatement CMET minimal with many different choices of classCodes(ORG, ENC, PROC, SPLY, SBADM, OBS) and each of the act class codes draws from one or more of the following moodCodes (EVN, DEF, INT PRMS, RQO, PRP, APT, ARQ, GOL)]
performer | .participation[typeCode=PRF]
id | n/a
extension | n/a
modifierExtension | N/A
function | participation[typeCode=PRF].functionCode
actor | .role
location | .participation[typeCode=LOC].role
authorizingPrescription | .outboundRelationship[typeCode=FLFS].target[moodCode=RQO]
type | .code
quantity | .quantity
daysSupply | effectiveUseTime
whenPrepared | .effectiveTime[xmi:type=IVL_TS].low
whenHandedOver | .effectiveTime[xmi:type=IVL_TS].high
destination | .participation[typeCode=DST].role
receiver | .participation[typeCode=RCV].role
note | .inboundRelationship[typeCode=SUBJ]/source[classCode=ACT,moodCode=EVN]
dosageInstruction | .outboundRelationship[typeCode=COMP].target[classCode=SBADM, moodCode=INT]
substitution | .outboundRelationship[typeCode=COMP].target[classCode=SUBST, moodCode=EVN]
id | n/a
extension | n/a
modifierExtension | N/A
wasSubstituted | .actionNegationInd
type | .code
reason | .reasonCode
responsibleParty | .participation[typeCode=PFM].role[classCode=ASSIGN]
detectedIssue | .inboundRelationship[typeCode=SUBJ]/source[classCode=ALRT,moodCode=EVN].value
eventHistory | .inboundRelationship(typeCode=SUBJ].source[classCode=CACT, moodCode=EVN]

### Mappings for FiveWs Pattern Mapping (http://hl7.org/fhir/fivews)

DrugDispensation
MedicationDispense |
identifier | FiveWs.identifier
status | FiveWs.status
medication[x] | FiveWs.what[x]
medication[x] (medicationCodeableConcept) | FiveWs.what[x]
subject | FiveWs.subject[x], FiveWs.subject
supportingInformation | FiveWs.context

### Mappings for V3 Pharmacy Dispense RMIM (http://www.hl7.org/v3/PORX_RM020070UV)

DrugDispensation
MedicationDispense |
identifier | CombinedMedicationDispense.id
status | CombinedMedicationDispense.SupplyEvent.statusCode
medication[x] | CombinedMedicationRequest.component1.AdministrationRequest.consumable
medication[x] (medicationCodeableConcept) | CombinedMedicationRequest.component1.AdministrationRequest.consumable
authorizingPrescription | CombinedMedicationDispense.inFulfillmentOf
type | CombinedMedicationDispense.SupplyEvent.code
quantity | CombinedMedicationDispense.SupplyEvent.quantity
whenPrepared | CombinedMedicationDispense.SupplyEvent.effectiveTime
whenHandedOver | CombinedMedicationDispense.SupplyEvent.effectiveTime
destination | CombinedMedicationDispense.SupplyEvent.destination
receiver | CombinedMedicationDispense.SupplyEvent.receiver
substitution | CombinedMedicationDispense.substitutionMade
type | CombinedMedicationDispense.substitutionMade.code
reason | CombinedMedicationDispense.substitutionMade.reasonCode
responsibleParty | CombinedMedicationDispense.substitutionMade.ResponsibleParty

### Mappings for HL7 v2 Mapping (http://hl7.org/v2)

DrugDispensation
MedicationDispense |
medication[x] | RXD-2-Dispense/Give Code
medication[x] (medicationCodeableConcept) | RXD-2-Dispense/Give Code
subject | PID-3-Patient ID List
authorizingPrescription | ORC-2 Placer Order Number
type | RXD-33-Dispense Type
quantity | RXD-4-Actual Dispense Amount / RXD-5.1-Actual Dispense Units.code / RXD-5.3-Actual Dispense Units.name of coding system
daysSupply | TQ1.6 Timing/Quantity Segment Service Duration. Prior to v2.5, ORC.7.3 Common Order Segment / Quantity/Timing / Duration component. This is a formatted string, first character for the time unit (e.g., D=days), followed by the value. For example, “D14” represents “14 days supply” From v2.5 on, TQ1.6 Timing/Quantity Segment / Service Duration. This is a CQ data type (<Quantity (NM)> ^ <Units (CWE)>), thus for days supply, assuming the unit of measure is “days”, the numeric value is TQ1.6.1 (…|14^ For backwards compatibility, ORC.7 was permitted through v2.6. Both forms (field and segment) may be present in v2.5, v2.5.1, and v2.6
whenPrepared | RXD-3-Date/Time Dispensed
whenHandedOver | RXD-3-Date/Time Dispensed
destination | RXD-13 Dispense-to Location; RXD-30 Dispense to Pharmacy; RXD-31 Dispense to Pharmacy Address
note | RXD-9 Dispense Notes
substitution |
type | RXO-9-Allow Substitutions / RXE-9-Substitution Status