scleary1cs commented 6 months ago

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

n/a

Acceptance Criteria

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

Tasks

[ ] Register production certificate with fhir.epic.com
[ ] Configure production private key in ReportStream
[ ] Receive transport details (e.g. API endpoint URLs)
[ ] Confirm headers will be similar to staging
[ ] Confirm successful authentication to Epic's OAuth endpoint for UCSD production
[ ] Add production organization settings in ReportStream production (via request to RS, or via the admins on our team)
[ ] 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

basiliskus commented 2 weeks ago

John's comment from slack: "Will need Jeffery & Dean to clarify prod API and remaining steps for production configuration in advance of go-live. More on this next week…"

JohnNKing commented 1 week ago

It looks like we also need a new cert added to fhir.epic.com. I suspect the staging cert was used as a placeholder for prod -- as the hashes appear to match.