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

Update FHIRRouter Azure Events to Store LOINC Code Info #14331

Open
1 task
arnejduranovic opened this issue May 7, 2024 · 3 comments
Open
1 task

Update FHIRRouter Azure Events to Store LOINC Code Info #14331

arnejduranovic opened this issue May 7, 2024 · 3 comments
Assignees
Labels
High Priority Issue State label to flag an issue that is a high priority platform Platform Team

Comments

@arnejduranovic
Copy link
Collaborator

arnejduranovic commented May 7, 2024

User Story

As a ReportStream developer troubleshooting issues,
I want to see the LOINC code alongside the condition ReportStream mapped it to,
so I can evaluate its accuracy when needed.

Description/Use Case

Update AzureEventUtils.getObservations to include the code and display fields in the second to last box pictured below

image

Risks/Impacts/Considerations

Dev Notes

Acceptance Criteria

  • ReportAcceptedEvent and ReportRoutedEvent both include test performed LOINC code and display alongside the mapped condition info
@arnejduranovic arnejduranovic added the platform Platform Team label May 7, 2024
@Andrey-Glazkv
Copy link
Collaborator

@Andrey-Glazkv
Copy link
Collaborator

Please add your planning poker estimate with Zenhub @JFisk42

@Andrey-Glazkv
Copy link
Collaborator

Please add your planning poker estimate with Zenhub @david-navapbc

@Andrey-Glazkv Andrey-Glazkv added the High Priority Issue State label to flag an issue that is a high priority label May 7, 2024
@adegolier adegolier self-assigned this May 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
High Priority Issue State label to flag an issue that is a high priority platform Platform Team
Projects
Development

No branches or pull requests

3 participants