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

CA Transform: Remove Accession Number #1299

Open
29 tasks
JohnNKing opened this issue Sep 9, 2024 · 0 comments
Open
29 tasks

CA Transform: Remove Accession Number #1299

JohnNKing opened this issue Sep 9, 2024 · 0 comments

Comments

@JohnNKing
Copy link
Contributor

JohnNKing commented Sep 9, 2024

Story

As UCSD, so that I can ingest an NBS result message, I need the accession number OBX removed (as this uses a local code that can't be supported).

Pre-conditions

  • n/a

Acceptance Criteria

  • For ORUs sent by ReportStream to UCSD, the accession number OBX (as identified by OBX-3.4 as '99717-5' AND OBX-3.6 as 'L') is removed.
  • The Observation set ID (OBX-1) values for all OBX segments are renumbered to be sequential (Note: This happens automatically as part of the RS FHIR => HL7 conversion; if not, we should discuss this as a team to see how essential this scope is)

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

@scleary1cs scleary1cs added story and removed foundational A foundational backlog task labels Sep 10, 2024
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

2 participants