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: MHVvitalsOx - Mappings

Page standards status: Trial-use Maturity Level: 4

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

Mappings for VIA to mhv-fhir-phr (VitalSignTO)

Informative map to available elements in MHV FHIR API

MHVvitalsOx
ObservationVitalSignTO
   identifier{StationNbr} and {VitalSignTO.type.id}
   status`final` if not `entered-in-error`
   category`vital-signs`
   code
      coding (PulseOx)LOINC 59408-5
      coding (O2Sat)LOINC 2708-6
      textVitalSignTO.type.name

VITAL_TYPE - 120.5-.03 VITAL TYPE

   subjectpatient

PATIENT - 120.5-.02 PATIENT

   effective[x] (effectiveDateTime)VitalSignTO.timestamp

DATE_TIME_TAKEN - 120.5-.01 Date/Time Vitals Taken

   performercontained VitalSignTO.recorder, contained VitalSignTO.observer

120.5-.06 ENTERED BY

,
      extension (site)Location(VitalSignTO.location)

120.5-.05 HOSPITAL LOCATION

   value[x]VitalSignTO.value1 and VitalSignTO.units

MEASUREMENT - 120.5-.1.2 RATE

Mappings for eVault-PHR to MHV-PHR (VitalSignTO)

Informative map to include only the elements available in eVault PHR

MHVvitalsOx
ObservationVitalSignTO

eVault

   status`final` if not `entered-in-error`
   category`vital-signs`
   code
      coding (PulseOx)LOINC 59408-5
      coding (O2Sat)LOINC 2708-6
      textVitalSignTO.type.name

VITAL_TYPE - 120.5-.03 VITAL TYPE

   subjectpatient

patient - 120.5-.02 Patient

   effective[x] (effectiveDateTime)VitalSignTO.timestamp

DATE_TIME_TAKEN - 120.5-.01 Date/Time Vitals Taken

   value[x]VitalSignTO.value1 and VitalSignTO.units

MEASUREMENT - 120.5-.1.2 RATE

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

MHVvitalsOx
ObservationEvent
   identifierEvent.identifier
   identifier (TOid)Event.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)

MHVvitalsOx
Observation< 363787002 |Observable entity|
   status< 445584004 |Report by finality status|
   code< 363787002 |Observable entity| OR < 386053000 |Evaluation procedure|
   value[x]< 441742003 |Evaluation finding|
   component
      code< 363787002 |Observable entity| OR < 386053000 |Evaluation procedure|
      value[x]363714003 |Interprets| < 441742003 |Evaluation finding|
      interpretation< 260245000 |Findings values|

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

MHVvitalsOx
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.
   identifier (TOid)OBX.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.
      useN/A
      typeCX.5
      systemCX.4 / EI-2-4
      valueCX.1 / EI.1
      periodCX.7 + CX.8
      assignerCX.4 / (CX.4,CX.9,CX.10)
   statusOBX-11
   category
   category (VSCat)
      codingC*E.1-8, C*E.10-22
         systemC*E.3
         versionC*E.7
         codeC*E.1
         displayC*E.2 - but note this is not well followed
         userSelectedSometimes implied by being first
      textC*E.9. But note many systems use C*E.2 for this
   codeOBX-3
      codingC*E.1-8, C*E.10-22
      coding (PulseOx)C*E.1-8, C*E.10-22
      coding (O2Sat)C*E.1-8, C*E.10-22
      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
   dataAbsentReasonN/A
   componentcontainment by OBX-4?
      codeOBX-3
      value[x]OBX.2, OBX.5, OBX.6
      dataAbsentReasonN/A
      interpretationOBX-8
      referenceRangeOBX.7

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

MHVvitalsOx
ObservationEntity. Role, or Act, Observation[classCode=OBS, moodCode=EVN]
   textAct.text?
   containedN/A
   extensionN/A
   modifierExtensionN/A
   identifierid
   identifier (TOid)id
      idn/a
      extensionn/a
      useRole.code or implied by context
      typeRole.code or implied by context
      systemII.root or Role.id.root
      valueII.extension or II.root if system indicates OID or GUID (Or Role.id.extension or root)
      periodRole.effectiveTime or implied by context
      assignerII.assigningAuthorityName but note that this is an improper use by the definition of the field. Also Role.scoper
   statusstatus Amended & Final are differentiated by whether it is the subject of a ControlAct event with a type of "revise"
   category.outboundRelationship[typeCode="COMP].target[classCode="LIST", moodCode="EVN"].code
   category (VSCat).outboundRelationship[typeCode="COMP].target[classCode="LIST", moodCode="EVN"].code
      idn/a
      extensionn/a
      codingunion(., ./translation)
         idn/a
         extensionn/a
         system./codeSystem
         version./codeSystemVersion
         code./code
         displayCV.displayName
         userSelectedCD.codingRationale
      text./originalText[mediaType/code="text/plain"]/data
   codecode
      idn/a
      extensionn/a
      codingunion(., ./translation)
      coding (PulseOx)union(., ./translation)
      coding (O2Sat)union(., ./translation)
      text./originalText[mediaType/code="text/plain"]/data
   subjectparticipation[typeCode=RTGT]
   effective[x]effectiveTime
   effective[x] (effectiveDateTime)effectiveTime
   performerparticipation[typeCode=PRF]
      idn/a
      extensionn/a
      extension (site)
         idn/a
         urlN/A
         value[x]N/A
      referenceN/A
      typeN/A
      identifier.identifier
      displayN/A
   value[x]value
   dataAbsentReasonvalue.nullFlavor
   componentoutBoundRelationship[typeCode=COMP]
      idn/a
      extensionn/a
      modifierExtensionN/A
      codecode
      value[x]value
      dataAbsentReasonvalue.nullFlavor
      interpretationinterpretationCode
      referenceRangeoutboundRelationship[typeCode=REFV]/target[classCode=OBS, moodCode=EVN]

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

MHVvitalsOx
Observation
   identifierFiveWs.identifier
   identifier (TOid)FiveWs.identifier
   statusFiveWs.status
   categoryFiveWs.class
   category (VSCat)FiveWs.class
   codeFiveWs.what[x]
   subjectFiveWs.subject[x], FiveWs.subject
   effective[x]FiveWs.done[x]
   effective[x] (effectiveDateTime)FiveWs.done[x]
   performerFiveWs.actor
   component
      codeFiveWs.what[x]

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

MHVvitalsOx
Observation
   code116680003 |Is a|
   value[x]363714003 |Interprets|
   component
      value[x]363714003 |Interprets|
      interpretation363713009 |Has interpretation|