Below are the gaps and missing PIH use cases based on the Active Visits mock up and the current Queue implementation.
Have a queue per service/location
Able to add a patient to a queue who already has an active visit
I want to remove a patient from a queue and not add them to another queue
System allows for a customizable queue table (e.g. displaying different columns of data) depending on the service
I want to be able to manually add the date/time a patient was added to queue in case they are not added in real time
Summary
- Current design of the queues app contains workflows that are tightly coupled with Appointments and Visits. We would like to remove the coupling with Appointments, and reduce the coupling of Visits to just ensuring that patients have active visits being added to queues.
- We would like to have a queue table view that allows us to view a specific queue and a specific queue filtered by status.
- We would like to have a queue table that can be configued to have custom columns.
- We would like to be able to modify more fields in queue entries (status, priority, start time). With consideration f orretroactive for retroactive data entry.
- We would like more flexible ways to configure priority and statuses for each queue.
Further Reading
Queue Entry Management
...
- Currently, the "Bell Button" takes a queue entry's status to "In Service". We need to account to for queues with multiple possible statuses and be able to change it to any status.
- Currently, the esm-patient-service-queues module allows configuration to designate the Emergency Priority for the purpose of sorting. We need to account to for multiple possible priorities and be able to change it to any priority.