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

Add "Facility Details" to Encounter Info #2506

Closed
10 tasks
emmastephenson opened this issue Sep 6, 2024 · 1 comment · Fixed by #2614
Closed
10 tasks

Add "Facility Details" to Encounter Info #2506

emmastephenson opened this issue Sep 6, 2024 · 1 comment · Fixed by #2614
Assignees
Labels
FHIR conversion required This ticket will need FHIR conversion work needs design review The PR for this issue will need design review before merging Streamline eCR Issues for Streamline eCR team to work on

Comments

@emmastephenson
Copy link
Collaborator

emmastephenson commented Sep 6, 2024

User Story

As a case investigator or eCR coordinator, I want to be able to see what facility an eCR encounter occurred at. This will help inform my investigation and which health care facility I should follow up with.

Acceptance Criteria

  • New Facility Details section is added to Encounter Info
  • The following fields are added to that section in the order specified below:
    • Facility Name
    • Facility Address
    • Facility Contact
    • Facility Contact Address
    • Facility Type
    • Facility ID
  • The data in the fields should match the data found in the componentOf > encompassingEncounter > location > healthCareFacility section of the xml
  • If these fields are not present in the eCR document, they are added to the Unavailable Info section

Scenarios

Scenario 1:

  • When viewing an eCR, I want to know about the facility where the patient encounter took place
  • When I scroll down to the Encounter Info section, I can see Facility Details section in the Viewer
  • The fields are listed in this order:
    • Facility Name
    • Facility Address
    • Facility Contact
    • Facility Contact Address
    • Facility Type
    • Facility ID
  • The data that I can see in this section corresponds exactly to the data I see in the componentOf > encompassingEncounter > location > healthCareFacility section of the xml
  • When I scroll down to Unavailable Info section, I see any fields we didn't have data for in the correct order

Design Notes

Link to Figma design in Dev mode

Screenshots below should not be used for working on this ticket - always refer to Figma design for most up-to-date designs:

this screenshot doesn't have ALL fields, refer to list above or spreadsheet for all fields
Screenshot 2024-09-06 at 1.55.27 PM.png

Additional context

There's a good deal of similar, author-related information within an eCR - facility, provider, author, encounter location, etc. We weren't previously displaying the encounter facility information, but it's very important for case investigators (this organization is who they would follow up with about a case.)

This spreadsheet has more information about where in the eCR spec facility information can be found: eCR Viewer Field Mapping

area to look at in spreadsheet highlighted in red box:
Screenshot 2024-09-12 at 10.12.27 AM.png

@emmastephenson emmastephenson added FHIR conversion required This ticket will need FHIR conversion work needs design review The PR for this issue will need design review before merging Streamline eCR Issues for Streamline eCR team to work on labels Sep 6, 2024
@emmastephenson emmastephenson changed the title Copy of Add eRSD warnings to the eCR Viewer Add "Facility Details" to Encounter Info Sep 6, 2024
@emmastephenson
Copy link
Collaborator Author

We may already be converting this data to FHIR and showing it under different headers - this will need some investigation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
FHIR conversion required This ticket will need FHIR conversion work needs design review The PR for this issue will need design review before merging Streamline eCR Issues for Streamline eCR team to work on
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants