MyHealtheVet PHR FHIR API
0.3.9-current - ci-build United States of America flag

MyHealtheVet PHR FHIR API, published by VA Digital Services. This guide is not an authorized publication; it is the continuous build for version 0.3.9-current built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/department-of-veterans-affairs/mhv-fhir-phr-mapping/ and changes regularly. See the Directory of published versions

Resource Profile: MHVimmunizationReaction - Mappings

Page standards status: Trial-use Maturity Level: 1

Mappings for the VA.MHV.PHR.immunizationReaction resource profile.

Mappings for VIA to mhv-fhir-phr (Immunization.reaction)

MHVimmunizationReaction
ObservationImmunizationTO
   status`final`
   code
      textImmunizationTO.reaction
   value[x] (valueCodeableConcept)SCT#410515003

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

MHVimmunizationReaction
ObservationEvent
   identifierEvent.identifier
   statusEvent.status
   codeEvent.code
   subjectEvent.subject
   effective[x]Event.occurrence[x]
   effective[x] (effectiveDateTime)Event.occurrence[x]
   performerEvent.performer.actor

Mappings for SNOMED CT Concept Domain Binding (http://snomed.info/conceptdomain)

MHVimmunizationReaction
Observation< 363787002 |Observable entity|
   status< 445584004 |Report by finality status|
   code< 363787002 |Observable entity| OR < 386053000 |Evaluation procedure|
   value[x]< 441742003 |Evaluation finding|
   value[x] (valueCodeableConcept)< 441742003 |Evaluation finding|

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

MHVimmunizationReaction
ObservationOBX
   identifierOBX.21 For OBX segments from systems without OBX-21 support a combination of ORC/OBR and OBX must be negotiated between trading partners to uniquely identify the OBX segment. Depending on how V2 has been implemented each of these may be an option: 1) OBR-3 + OBX-3 + OBX-4 or 2) OBR-3 + OBR-4 + OBX-3 + OBX-4 or 2) some other way to uniquely ID the OBR/ORC + OBX-3 + OBX-4.
   statusOBX-11
   codeOBX-3
      textC*E.9. But note many systems use C*E.2 for this
   subjectPID-3
   effective[x]OBX-14, and/or OBX-19 after v2.4 (depends on who observation made)
   effective[x] (effectiveDateTime)OBX-14, and/or OBX-19 after v2.4 (depends on who observation made)
   performerOBX.15 / (Practitioner) OBX-16, PRT-5:PRT-4='RO' / (Device) OBX-18 , PRT-10:PRT-4='EQUIP' / (Organization) OBX-23, PRT-8:PRT-4='PO'
   value[x]OBX.2, OBX.5, OBX.6
   value[x] (valueCodeableConcept)OBX.2, OBX.5, OBX.6

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

MHVimmunizationReaction
ObservationEntity. Role, or Act, Observation[classCode=OBS, moodCode=EVN]
   textAct.text?
   containedN/A
   extensionN/A
   modifierExtensionN/A
   identifierid
   statusstatus Amended & Final are differentiated by whether it is the subject of a ControlAct event with a type of "revise"
   codecode
      idn/a
      extensionn/a
      text./originalText[mediaType/code="text/plain"]/data
   subjectparticipation[typeCode=RTGT]
   effective[x]effectiveTime
   effective[x] (effectiveDateTime)effectiveTime
   performerparticipation[typeCode=PRF]
   value[x]value
   value[x] (valueCodeableConcept)value

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

MHVimmunizationReaction
Observation
   identifierFiveWs.identifier
   statusFiveWs.status
   codeFiveWs.what[x]
   subjectFiveWs.subject[x], FiveWs.subject
   effective[x]FiveWs.done[x]
   effective[x] (effectiveDateTime)FiveWs.done[x]
   performerFiveWs.actor

Mappings for SNOMED CT Attribute Binding (http://snomed.org/attributebinding)

MHVimmunizationReaction
Observation
   code116680003 |Is a|
   value[x]363714003 |Interprets|
   value[x] (valueCodeableConcept)363714003 |Interprets|