Add GT1 Mapping in ReportStream

[brick-green]

Story

As a sender of Orders, so that I can send insurance information, I need the GT1 segment to be read on incoming OML messages and output in OML messages.

Pre-conditions

• Example OMLs are available with GT1 segments present

Acceptance Criteria

• All fields in the GT1 segment present in the OML are exactly the same on the output file are they are in the input sample file
• Integration tests have been added for all fields that are mapped in ReportStream

Notes

• See https://github.com/HL7/v2-to-fhir/tree/master/mappings/segments -- please note that GT1 is currently not mapped.
• See https://confluence.hl7.org/pages/viewpage.action?pageId=49644444 for HL7 work to date regarding GT1

Tasks

Research

• Review mapping inventory and confluence pages to find mapping guidelines

Engineering

• Add mapping to ReportStream
  • HL7 => FHIR
  • FHIR => HL7
• Add integration tests for mappings

Definition of Done

• Documentation tasks completed
  • Documentation and diagrams created or updated
    • ADRs (/adr folder)
    • Main README.md
    • Other READMEs in the repo
    • If applicable, update the ReportStream Setup section in README.md
  • Threat model updated
  • API documentation updated
• Code quality tasks completed
  • Code refactored for clarity and no design/technical debt
  • Adhere to separation of concerns; code is not tightly coupled, especially to 3rd party dependencies
• Testing tasks completed
  • Load tests passed
  • Additional e2e tests created
  • Additional RS e2e assertions created in the rs-e2e project for any new transformations. Includes improvements to the assertion code required to make the new assertions
• Build & Deploy tasks completed
  • Build process updated
  • API(s) are versioned
  • Feature toggles created and/or deleted. Document the feature toggle
  • Source code is merged to the main branch

Note: Please remove any DoD items that are not applicable

Research Questions

• Optional: Any initial questions for research

Decisions

• Optional: Any decisions we've made while working on this story

[JohnNKing]

Split into 2 or 3 stories?

1. Inbound HL7 => FHIR
2. Outbound FHIR = > HL7
3. Spike for determining FHIR mappings (as these are non-standard)

[brick-green]

Typically the segment mappings are completed as one ticket for the HL7 to FHIR and FHIR to HL7. The data mapping integration tests will test the round trip from HL7 to FHIR then back to HL7 so it's helpful to do all the mapping in one PR. There could be an opportunity to split out tickets for any new data types that are part of GT1 but not currently mapped.

[GilmoreA6]

Branch for GT1 Mapping https://github.com/CDCgov/prime-reportstream/tree/Flexion/jgilmore/GT1-mapping-OML

[GilmoreA6]

Added Account resource to RS FHIR R4 mapping model for OML.

After discussion we are going to map all fields in GT1 to a newly created extension https://reportstream.cdc.gov/fhir/StructureDefinition/gt1-account and then also map any fields in accordance with the linked confluence document.

On the FHIR->HL7 side we will then set conditions so that the extension values are used first if available, then if not to use the other mappings. This ensures that we will faithfully return the input value for each field even if it differs from the official guidance

[GilmoreA6]

Mapped GT1-1 -> GT1-20 for HL7-> FHIR onto branch

[GilmoreA6]

exception to mapping strategy made for GT1.13 and GT1.14 to follow IN1 pattern