QI-Core Implementation Guide: STU 4 (v4.0.0 for FHIR 4.0.1)

QI-Core Implementation Guide - This is the current published version.. See the Directory of published versions

D.4.1.4 StructureDefinition: qicore-medicationdispense - Mappings

Mappings for the StructureDefinition-qicore-medicationdispense Profile.

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

QICoreMedicationDispense
MedicationDispenseEvent
   identifierEvent.identifier
   partOfEvent.partOf
   statusEvent.status
   statusReason[x]Event.statusReason
   medication[x]Event.code
   subjectEvent.subject
   contextEvent.context
   performerEvent.performer
      actorEvent.performer.actor
   authorizingPrescriptionEvent.basedOn
   whenHandedOverEvent.occurrence[x]
   noteEvent.note

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

QICoreMedicationDispense
MedicationDispenseEntity. Role, or Act, Supply[moodCode=EVN]
   textAct.text?
   containedN/A
   extensionN/A
   modifierExtensionN/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
   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]
      idn/a
      extensionn/a
      modifierExtensionN/A
      functionparticipation[typeCode=PRF].functionCode
      actor.role
   location.participation[typeCode=LOC].role
   authorizingPrescription.outboundRelationship[typeCode=FLFS].target[moodCode=RQO]
   type.code
   quantity.quantity
   daysSupplyeffectiveUseTime
   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]
      idn/a
      extensionn/a
      modifierExtensionN/A
      sequence.text
      text.text
      additionalInstruction.text
      patientInstruction.text
      timing.effectiveTime
      asNeeded[x].outboundRelationship[typeCode=PRCN].target[classCode=OBS, moodCode=EVN, code="as needed"].value=boolean or codable concept
      site.approachSiteCode
      route.routeCode
      method.doseQuantity
      doseAndRate
         idn/a
         extensionn/a
         dose[x].doseQuantity
         rate[x].rateQuantity
      maxDosePerPeriod.maxDoseQuantity
      maxDosePerAdministrationnot supported
      maxDosePerLifetimenot supported
   substitution.outboundRelationship[typeCode=COMP].target[classCode=SUBST, moodCode=EVN]
      idn/a
      extensionn/a
      modifierExtensionN/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)

QICoreMedicationDispense
MedicationDispense
   identifierFiveWs.identifier
   statusFiveWs.status
   medication[x]FiveWs.what[x]
   subjectFiveWs.subject[x], FiveWs.subject
   supportingInformationFiveWs.context

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

QICoreMedicationDispense
MedicationDispense
   identifierCombinedMedicationDispense.id
   statusCombinedMedicationDispense.SupplyEvent.statusCode
   medication[x]CombinedMedicationRequest.component1.AdministrationRequest.consumable
   authorizingPrescriptionCombinedMedicationDispense.inFulfillmentOf
   typeCombinedMedicationDispense.SupplyEvent.code
   quantityCombinedMedicationDispense.SupplyEvent.quantity
   whenPreparedCombinedMedicationDispense.SupplyEvent.effectiveTime
   whenHandedOverCombinedMedicationDispense.SupplyEvent.effectiveTime
   destinationCombinedMedicationDispense.SupplyEvent.destination
   receiverCombinedMedicationDispense.SupplyEvent.receiver
   substitutionCombinedMedicationDispense.substitutionMade
      typeCombinedMedicationDispense.substitutionMade.code
      reasonCombinedMedicationDispense.substitutionMade.reasonCode
      responsiblePartyCombinedMedicationDispense.substitutionMade.ResponsibleParty

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

QICoreMedicationDispense
MedicationDispense
   medication[x]RXD-2-Dispense/Give Code
   subjectPID-3-Patient ID List
   authorizingPrescriptionORC-2 Placer Order Number
   typeRXD-33-Dispense Type
   quantityRXD-4-Actual Dispense Amount / RXD-5.1-Actual Dispense Units.code / RXD-5.3-Actual Dispense Units.name of coding system
   daysSupplyTQ1.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
   whenPreparedRXD-3-Date/Time Dispensed
   whenHandedOverRXD-3-Date/Time Dispensed
   destinationRXD-13 Dispense-to Location; RXD-30 Dispense to Pharmacy; RXD-31 Dispense to Pharmacy Address
   noteRXD-9 Dispense Notes
   dosageInstruction
      sequenceTQ1-1
      textRXO-6; RXE-21
      additionalInstructionRXO-7
      patientInstructionRXO-7
      asNeeded[x]TQ1-9
      siteRXR-2
      routeRXR-1
      methodRXR-4
      doseAndRateTQ1-2
         typeRXO-21; RXE-23
         dose[x]RXO-2, RXE-3
         rate[x]RXE22, RXE23, RXE-24
      maxDosePerPeriodRXO-23, RXE-19
   substitution
      typeRXO-9-Allow Substitutions / RXE-9-Substitution Status