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

Page standards status: Trial-use Maturity Level: 1

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

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

MHVlabTest
ObservationLabTestTO / LabResultTO
   identifier{StationNbr} and {LabTestTO.id}
   status`final`
   category`laboratory`
   code
      codingLabTestTO.loinc
      textLabTestTO.name
   effective[x] (effectiveDateTime){DiagnosticReport.effectiveDate}
   issued{DiagnosticReport.issued}, labReportTO/result/timestamp
   performerGetPractitioner(DiagnosticReport.performer)
   value[x] (valueString)LabResultTO.value
   specimen{Specimen}

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

MHVlabTest
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)

MHVlabTest
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] (valueString)< 441742003 |Evaluation finding|
   specimen< 123038009 |Specimen|

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

MHVlabTest
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
   codeOBX-3
      codingC*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)
   issuedOBR.22 (or MSH.7), or perhaps OBX-19 (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] (valueString)OBX.2, OBX.5, OBX.6
   specimenSPM segment

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

MHVlabTest
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 (Laboratory).outboundRelationship[typeCode="COMP].target[classCode="LIST", moodCode="EVN"].code
   codecode
      idn/a
      extensionn/a
      codingunion(., ./translation)
      text./originalText[mediaType/code="text/plain"]/data
   subjectparticipation[typeCode=RTGT]
   effective[x]effectiveTime
   effective[x] (effectiveDateTime)effectiveTime
   issuedparticipation[typeCode=AUT].time
   performerparticipation[typeCode=PRF]
   value[x]value
   value[x] (valueString)value
   specimenparticipation[typeCode=SPC].specimen

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

MHVlabTest
Observation
   identifierFiveWs.identifier
   identifier (TOid)FiveWs.identifier
   statusFiveWs.status
   categoryFiveWs.class
   category (Laboratory)FiveWs.class
   codeFiveWs.what[x]
   subjectFiveWs.subject[x], FiveWs.subject
   effective[x]FiveWs.done[x]
   effective[x] (effectiveDateTime)FiveWs.done[x]
   issuedFiveWs.recorded
   performerFiveWs.actor

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

MHVlabTest
Observation
   code116680003 |Is a|
   value[x]363714003 |Interprets|
   value[x] (valueString)363714003 |Interprets|
   specimen704319004 |Inherent in|