Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

LA Results LRIv5 Transformation #1355

Open
32 tasks
JohnNKing opened this issue Sep 24, 2024 · 2 comments
Open
32 tasks

LA Results LRIv5 Transformation #1355

JohnNKing opened this issue Sep 24, 2024 · 2 comments

Comments

@JohnNKing
Copy link
Contributor

JohnNKing commented Sep 24, 2024

Story

As Ochsner, so that our EHR can ingest results messages from ReportStream, I need all but one of the OBR segments removed.

Pre-conditions

n/a

Acceptance Criteria

  • The OBR for "54089-8" remains unchanged
  • All other OBR are removed from the outgoing HL7 ORU message
  • All OBXs appear under the sole remaining OBR
  • Numeric OBX IDs are sequential and unique
  • Write a RS E2E test that covers this transformation similar to Implementation: Automated TI <> RS tests #1255.

See #639 for the same effort that was done for CA.

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
    • Code is reviewed or developed by pair; 1 approval is needed but consider requiring an outside-the-pair reviewer
    • Code quality checks passed
  • Security & Privacy tasks completed
    • Security & privacy gates passed
  • Testing tasks completed
    • Load tests passed
    • Unit test coverage of our code >= 90%
  • 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

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
@JohnNKing JohnNKing changed the title LA Results Flattening LA Results LRIv5 Transformation Sep 24, 2024
@saquino0827
Copy link
Contributor

Current outgoing questions:

  1. We have specific UCSD identifiers R797 and R508. Are there identifiers we can leverage for LA?
  2. Do we have up-to-date LA sample files?

@pluckyswan
Copy link
Contributor

Branch for this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants