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 a v3.1 eCR #2916

Open
emmastephenson opened this issue Nov 15, 2024 · 0 comments
Open

Test a v3.1 eCR #2916

emmastephenson opened this issue Nov 15, 2024 · 0 comments
Labels
Streamline eCR Issues for Streamline eCR team to work on

Comments

@emmastephenson
Copy link
Collaborator

What needs to be done

Run a v3.1 eCR through the DIBBs pipeline and into the eCR Viewer, and determine which (if any) fields are unable to convert.

Why it needs to be done

eICR version 3.1 will start being sent by providers early next year, and we need to ensure that the eCR Viewer can handle it.

Acceptance Criteria

  • 3.1 eCR sent through the eCR Viewer and our QA process followed to identify missing data or errors
  • Bug tickets created for these issues

Technical Notes

  • Sample 3.1 eCRs attached (we don't have any from actual providers yet - Epic is only enabling 3.1 for their providers in Jan/Feb 2025.)
  • Sample eICR on Github
  • 3 additional eCRs can be found in Drive (Alice, Cathy, and Jeffrey)

3.1_Sample (2) (1).zip

@emmastephenson emmastephenson added the Streamline eCR Issues for Streamline eCR team to work on label Nov 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Streamline eCR Issues for Streamline eCR team to work on
Projects
None yet
Development

No branches or pull requests

1 participant