UML Sequence Diagram for Notify Use Case

[lapis2002]

Description

Participant:

• Patient (Actor)
• Login Page (type: PageUI)
• Triage Result Page (type: PageUI)
• Notification Module (type: NotificationSvc)
• Patient Database (type: Database)
• HealthService Database (type: Database)

Combined Fragments:

• Alt Fragment for the suggestion process
• Ref Fragment to Login Use case
• Ref Fragment to Check ER Capacity and Assign Patient to ER Queue

Process:

• When the triage result is available, the Notification Service will send a notification to patient via email or text message.
• Then the patient can click on the link attached in the email/text message to be redirect to the login page.
• The patient is required to log in first before viewing their triage result. Therefore, the diagram refers to the sequence diagram of authentication use case.
• After patient logs in successfully, the system will redirect user to the result page, the UI also send request to get the triage results summary from Patient Database, and display the information to the patient.
• Based on the result, there would be 3 different scenarios:
  • If the patient is suggested to take counter medicine, the triage page will display a message suggesting patient to take counter medication, the user can click on the button and the UI will send request to get patient info, such as location, allergies, as well as list of pharmacies near-by patient's location, then display that to patient.
  • If the patient is suggested to contact nurses/clinician, the triage page will display a message suggesting patient to take contact nurses/clinician, the user can click on the button to get more help and the UI will send request to get patient info, such as location, health record, as well as list of available nurses/clinic near-by patient's location and their contact, then display that to patient.
  • If the patient is suggested to visit the ER, the triage result page will display a message suggesting patient to visit ER, and ask if the patient wants the system to help them book and be placed in ER queue. If the patient agrees, they will be redirect to Booking ER page to the Check ER current capacity and assign patient to ER Queue Use case.
• Alternatively, patient can click on the button to view the detail of their triage result instead of summary.

[OllieWare]

Looks good, just watch for the overlap that has happened on the user login to system tile, between the REF and display page function. Otherwise, awesome job!

[dhuruvan13]

Looks good to me.

[milesrose13]

Great job definitely displays the use case very well!
minor spelling mistake for "displaceMedandPharmacyList" probably meant to be "displayMedandPharmacyList"

[lapis2002]

Great job definitely displays the use case very well! minor spelling mistake for "displaceMedandPharmacyList" probably meant to be "displayMedandPharmacyList"

Thanks for spotting that. Updated!

[minhn201]

Very detailed and comprehensive. Well done :)

[lapis2002]

Description

Participant:

• Patient (Actor)
• Login Page (type: PageUI)
• Triage Result Page (type: PageUI)
• Notification Module (type: NotificationSvc)
• Patient Database (type: Database)
• HealthService Database (type: Database)

Combined Fragments:

• Alt Fragment for the suggestion process
• Ref Fragment to Login Use case
• Ref Fragment to Check ER Capacity and Assign Patient to ER Queue

Process:

• When the triage result is available, the Notification Service will send a notification to patient via email or text message.
• Then the patient can click on the link attached in the email/text message to be redirect to the login page.
• The patient is required to log in first before viewing their triage result. Therefore, the diagram refers to the sequence diagram of authentication use case.
• After patient logs in successfully, the system will redirect user to the result page, the UI also send request to get the triage results summary from Patient Database, and display the information to the patient.
• Based on the result, there would be 3 different scenarios:
  • If the patient is suggested to take counter medicine, the triage page will display a message suggesting patient to take counter medication, the user can click on the button and the UI will send request to get patient info, such as location, allergies, as well as list of pharmacies near-by patient's location, then display that to patient.
  • If the patient is suggested to contact nurses/clinician, the triage page will display a message suggesting patient to take contact nurses/clinician, the user can click on the button to get more help and the UI will send request to get patient info, such as location, health record, as well as list of available nurses/clinic near-by patient's location and their contact, then display that to patient.
  • If the patient is suggested to visit the ER, the triage result page will display a message suggesting patient to visit ER, and ask if the patient wants the system to help them book and be placed in ER queue. If the patient agrees, they will be redirect to Booking ER page to the Check ER current capacity and assign patient to ER Queue Use case.
• Alternatively, patient can click on the button to view the detail of their triage result instead of summary.

[minhn201]

The description looks spotless to me.