Uploaded image for project: 'V2 Specification Feedback'
  1. V2 Specification Feedback
  2. V2-25764

HL7V2-FHIR: OBX-5 mapping

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • V2 to FHIR (V2)
    • 1.0
    • Orders & Observations
    • Observation/Result to FHIR Observation (OBX)
    • 18.164.1
    • Hide

      Motion to find persuasive and map OBX-5 iterations based on OBX-2 value that determines where to map based on data type.  Attachment is one of the options.  Per general guidance, a local system can always adjust, but has to be cautious whether it will be mapped to a FHIR resource consistent with the expectations on where to find binary data.

      Show
      Motion to find persuasive and map OBX-5 iterations based on OBX-2 value that determines where to map based on data type.  Attachment is one of the options.  Per general guidance, a local system can always adjust, but has to be cautious whether it will be mapped to a FHIR resource consistent with the expectations on where to find binary data.
    • Hans Buitendijk / Riki Merrick: 8-0-1
    • Enhancement
    • Compatible, substantive

    Description

      Existing Wording Proposed Wording Ballot Comment
      Observation.component[forEachOBX-5Instance].#ext-valueAttachment# Observation.component[forEachOBX-5Instance].#ext-valueAttachment# OR
      Observation.derivedFrom (Referece/DocumentReference)

      This can technically be mapped to valueAttachment (also a proposal for R5), but in that case users have multiple options with respect to binary data store. If it is a document, it should be added as documentreference with a binary attachment. Individual observations can be derived based on that. Users should be allowed a choice based on their implementation considerations - like size of the base64 data. Suggestion is to allow users to have a choice between valueattachment and documentReference/binary

      Attachments

        Activity

          People

            hbuitendijk Hans Buitendijk
            shashank.shekhar@philips.com Shashank Shekhar (Inactive)
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: