LA Order Transformation - Collecting Facility

[JScott-JMC]

Story

As the LA PHL, so that Collecting Facility metadata can be properly conveyed in the Ochsner NBS test orders, I need the Intermediary to map The Collecting Facility ID from an OBX segment into the ORC.21.10 field.

Pre-conditions

• A test order is received in RS from the LA Ochsner NBS system (MSH.3 = "13^1.2.840.114350.1.13.286.2.7.2.695071^ISO")
• The order message contains an OBX segment with an OBX.3.1 value of "PLT3351"

Acceptance Criteria

• The Collecting Facility ID in OBX.5.1 (when OBX.3.1 = PLT3351) is mapped to the ORC.21.10 field in the message
• The original OBX containing the PLT code in OBX.3.1 is not present in the outgoing order message
• This transformation is successfully performed for all NBS test orders received from the LA Ochsner system
• This transformation is not performed for NBS test orders received from other hospital systems

Tasks

• Request PLT code
• Confirm and document the PLT code (OBX.3.1) that will trigger this transformation in a message
• Confirm and document the Sending Application OIDs (MSH.3) that will trigger this transformation in a message
• Obtain an Ochsner-specific example order message that captures the Collecting Facility ID as identified above.
• Create a new transform that copies the proper OBX 5.1 value to ORC.21.10.
  • Clarify if we can re-use an existing transform or if a new one will be needed.
• Configure the transform above and remove OBX transform for Ochsner
• Add assertion to the automated tests for this scenario.

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

Notes

• Optional: Any reference material or thoughts we may need for later reference

[JScott-JMC]

@JohnNKing @brick-green

This need is still pending confirmation. The Ochsner team has not yet verified they will be able to extract the Collecting Facility to place in an OBX. IF they are able to do this, the requirements above are stable.