Collaboration Diagrams

Triage

This is the collaboration diagram for the triage process. The patient starts by creating a triage request. The request is placed into a queue where the nurse will pick it up and add their notes based on the symptoms described by the patient. Afterwards, the path of action branches slightly. The nurse can choose to send an emergency response team to the patient or simply book an appointment for the patient. Either way, the results of the triage are sent to the patient after the nurse concludes the triage.

Log In

This is the collaboration diagram for the user log in. The process is fairly linear; the user enters their log in credentials. Based on whether the credentials match an account in the database, the user will either be notified their credentials are incorrect or be given access to their account and redirected to the homepage.

Log Out

This is the collaboration diagram for logging out. It is a straightforward process where the user confirms a log out in the gui before being removed from their session and placed back to the log in page. There are no alternative paths for this process.

Create Account

This is the collaboration diagram for creating a user account. The user enters their prefered account credentials (username and password) and confirms their selection. The credentials are checked for a duplicate username in the database. If there is a duplicate user, then the database notifies the user that the account creation failed along with the reason. If there is no duplicate user, the account is added to the database, the user notified of the success, and the gui redirects the user to the log in page.

Support Ticket

This is the collaboration diagram for a user creating and submitting a support ticket. The user enters the ticket details in full and submits it. The ticket is added to the database and ticket queue for an admin to resolve later. The user is then notified of the ticket creation being completed. It is assumed that the ticket fields are validated before being sent.

This is the collaboration diagram for an admin resolving a support ticket. The admin gets the next ticket in the queue, changing the ticket to an "in progress" state. The user is notified of this while the admin works on completing the ticket. When the ticket is reolved, the admin can mark the ticket as finished with optional notes to send to the user. The ticket is moved to a "resolved" state and the user is then notified that their ticket has been resolved (or not, in which case the notes would explain why). Finally, the admin is shown confirmation that the ticket has been changed to a resolved state.

Dispatch Request

This is the collaboration diagram for an EMT handling a dispatch request (sent by the nurse in the triage). The EMT will check the request and decide whether or not they are equipped to handle it. In the scenario where the EMT can not handle the request, the request is sent to the next nearest EMT to the request location and the process starts again from step 1. In the scenario that the EMT can respond to the request, the EMT accepts the request on their UI and the system ensures the EMT will not get assigned requests while they are resolving the current one. Upon finishing the request, the EMT interacts with the ui to declare the request as complete. The request is then marked as complete and the EMT is then marked as open to further requests. Just like the sequence diagram, the EMT actor can represent an EMT team or a team leader in charge of organizing requests.