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 Gap Analysis - Test Results #1092

Open
8 of 34 tasks
JohnNKing opened this issue May 14, 2024 · 1 comment
Open
8 of 34 tasks

LA Gap Analysis - Test Results #1092

JohnNKing opened this issue May 14, 2024 · 1 comment

Comments

@JohnNKing
Copy link
Contributor

JohnNKing commented May 14, 2024

Story

As LA HCO, to ensure we'll receive all needed results data to an EHR, we need to relate the ReportStream results information to what will be received by the EHR.

Pre-conditions

  • n/a

Acceptance Criteria

  • Message profiles are now finalized
  • Publish list of transformation requirements for Intermediary
  • Get approvals
  • Create explicit stories for Intermediary transformation requirements

Tasks

  • Document side-by-side comparison of sender & receiver profiles
  • Identify/highlight differences (gaps)
  • Confirm gap solutions (3 possible actions)
    • 1. Sender will update configurations/message mappings to align with receiver profile
    • 2. Receiver will update message processing to align with sender profile
    • 3. Intermediary will transform/translate messages mid-stream to alleviate burden on sender & receiver
  • Update message profiles (if sender or receiver are making changes to accommodate)

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

@JScott-JMC
Copy link

@JohnNKing @brick-green

All tasks for this story are complete. I think we can move this to Done.

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

4 participants