HL7-FHIR-HL7 ORU-R01 Mapping: PRT -> PractionerRole/Device/RelatedPerson

[arnejduranovic]

User Story

As a Sender of ORU-R01 HL7v2 messages to RS, I expect my HL7v2 messages get delivered to the intended receiver in either the FHIR or HL7v2 format without losing data

Description/Use Case

To ensure RS is mapping ORU-R01 messages losslessly, RS needs to map HL7v2 segment to FHIR resource and FHIR resources to HL7v2 segments as described by the mapping inventory.

This ticket shall focus on creating HL7v2->FHIR and FHIR->HL7v2 mappings for the following resource(s) from the PRT segment:

• PractitionerRole
• Device
• RelatedPerson

Please reference the aforementioned ORU-R01 mapping inventory for guidance on what segments and resources need to be mapped.

Risks/Impacts/Considerations

Dev Notes

• Reuse the datatypes that were created as part of epic #11655
• Mapping decisions or interpretations made due to ambiguity in the mapping inventory should be documented to enable future follow-up with the owning organization

Acceptance Criteria

• [ ] Mappings created for segments/resource
• [ ] Decision points documented

[mkalish]

Decision was made to defer implementing all of the PRT segments for a few reasons:

• They are not in the target spec (ELR IG)
• The FHIR inventory is inconsistent and contradictory in terms of how they should be mapped; one example is that the mapping targets ServiceRequest.requester twice even though the FHIR property only supports a single value

This work will be easier to accomplish after completing #12752 which will design how we will handle multiple HL7 specs; once that is complete we can add code to support HL7 2.7.1 and complete all the mappings.

The work that had been partially completed is here: platform/feature/add-prt-support and can be used to complete this ticket.