Skip to content
This repository has been archived by the owner on Feb 7, 2025. It is now read-only.

OBX Repeating Fields #1692

Open
1 of 28 tasks
JohnNKing opened this issue Jan 14, 2025 · 0 comments
Open
1 of 28 tasks

OBX Repeating Fields #1692

JohnNKing opened this issue Jan 14, 2025 · 0 comments

Comments

@JohnNKing
Copy link
Contributor

JohnNKing commented Jan 14, 2025

Story

As a sender of orders or results, so I don't lose important clinical information, I need observation data sent as HL7 repeating fields to make it through the Intermediary.

Pre-conditions

  • An example OML is available that shows a field repeat used in OBX. (see file in Drive)
    OBX|3|CWE|67704-7^All Feeding Since Birth||LA16914-6^Breast milk^LN~LA16915-3^Lactose formula^LN||||||F|||20241219140951|||||||||||||||QST

Acceptance Criteria

  • For OBX segments, the Intermediary supports repeating of OBX.5, OBX.8, and OBX.10.
  • Supported repeating fields on an incoming OBX segment are included in the outgoing OBX (unless modified by an existing transformation or translation)
  • Integration tests have been added that cover OBX repeat fields

Tasks

Research

  • Research work needed to complete the story
  • Foundational: High-level research that will support this and future efforts

Engineering

  • Engineering work needed to complete the story
  • Foundational: Technical runway work to support this and future efforts

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
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant