During the squad call today, we proposed / discussed some changes to the Patient Chart Visits page, as part of the work on the new visit table (ticket here):
Visits Summary
Currently, the visits page displays visits as summary cards in a “infinite scroll” view. It loads 5 cards at a time, with a “Load more” button to load 5 more cards each time. We propose getting rid of this view in favor of the new Visit Table. This should help with pagination UX (especially for users who want to view very old visits) and performance.
Old:
New:
Each row in the new Visit Table should be clickable / expandable to a visit summary card (the ones we currently have now in the “infinite scroll” view.)
All Encounters table
We would like to keep the “All encounters” table, but how we fetch / filter data in the table will change.
- Currently, the “All encounters” table doesn’t actually fetch encounter data directly. Instead, it loops through the visits data loaded in “Visit summaries” and gets the encounters from each visit. We propose changing it to load encounters directly from the
/encounterREST endpoint. This improves the pagination UX.- Currently, the search filtering is done client-side. With this change, we need to switch to sever-side filtering.
- We will keep the “Filter by encounter type” option, but since there can be many encounter types (ref app has dozens, some implementation have +100), we will switch it to a Combobox.
- We will get rid of the free text search filtering for the table.
- Currently, the search filtering is done client-side. With this change, we need to switch to sever-side filtering.
Please let me know if you have suggestions or concerns about this.