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

BUG: Categorize empty Misc Notes section as Unavailable Data #2601

Open
3 tasks
angelathe opened this issue Sep 20, 2024 · 0 comments
Open
3 tasks

BUG: Categorize empty Misc Notes section as Unavailable Data #2601

angelathe opened this issue Sep 20, 2024 · 0 comments
Labels
🐛 bug Something isn't working low Low priority issues Streamline eCR Issues for Streamline eCR team to work on

Comments

@angelathe
Copy link
Collaborator

Description

Please fix the bug in the eCR below where a section is incorrectly displayed as available information, even though no actual data is present.

Steps to reproduce

If a section has no available data, it should automatically be categorized under the Unavailable Data section.

  1. View this eCR: ff7023af-515e-42ac-9f2b-5e4dace9ea16
  2. Open the Clinical Info section -> Miscellaneous Notes.
  3. The "Miscellaneous Notes" field displays "Not on file documented in this encounter." This should have triggered the evaluateData function to categorize it under the Unavailable Info section. However, it is incorrectly being shown as available information instead.

Expected Result

In the eCR below, the Clinical info section should display "No clinical information was found in this eCR." because there is no available info in the whole section.

Screenshot 2024-09-20 at 12.47.57.png

Actual result

Screenshot 2024-09-20 at 12.46.03.png

Priority

Provide an estimate for level of impact the bug has today by placing an X in the applicable bracket

Priority

  • Low priority The bug does not have to be fixed immediately. High and medium priority bugs should be addressed first.
  • Medium priority Typically, medium-priority bugs do not affect customers directly and therefore can be fixed in the normal course of testing and development.
  • High priority High priority bugs must be addressed immediately. They often affect the app’s functionality and impact customers and their user experience. They must take priority.

Notes

Relevant files:

  • evaluateClinicalData in containers/ecr-viewer/src/app/view-data/components/common.tsx
@angelathe angelathe added Streamline eCR Issues for Streamline eCR team to work on 🐛 bug Something isn't working labels Sep 20, 2024
@emmastephenson emmastephenson added the low Low priority issues label Sep 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛 bug Something isn't working low Low priority issues Streamline eCR Issues for Streamline eCR team to work on
Projects
None yet
Development

No branches or pull requests

2 participants