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

Test UCSD Production Connection #1637

Open
2 of 31 tasks
GilmoreA6 opened this issue Dec 2, 2024 · 0 comments
Open
2 of 31 tasks

Test UCSD Production Connection #1637

GilmoreA6 opened this issue Dec 2, 2024 · 0 comments

Comments

@GilmoreA6
Copy link
Contributor

GilmoreA6 commented Dec 2, 2024

Story

As UCSD, so that I can review and provide patient care based on NBS findings, I need sample result messages sent by ReportStream to appear in my EHR production environment.

Pre-conditions

Acceptance Criteria

  • An ORU message sent by ReportStream to the UCSD receiver appears in their production EHR environment.
  • Transmission uses TLS 1.2 or greater and a strong cipher

Tasks

  • Confirm successful authentication to Epic's OAuth endpoint for UCSD production
  • Verify receipt of messages
  • Verify result is filed correctly in the healthcare provider view of Epic
    • Verify micro/mu character appears correctly within the test result observations

Definition of Done

  • Documentation tasks completed
    • Documentation and diagrams created or updated
      • Implementation guide (/ig folder)
      • 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant