Milestone 1: Receptionist Diagram and Use Cases - SENG-350-2024-fall/Team-13 GitHub Wiki
***
| Use case | Register Patient |
|---|---|
| Description | Registers patients, verifying their information then adds them onto the waitlist |
| Actors | Receptionist, patient |
| Assumptions | The waiting list has space for another Patient has information ready |
| Steps | Receptionist gets information from patient Receptionist verifies information registers and adds patient onto waiting list |
| Variations | There may be no need to add to waiting list |
| Non-Functional | Should not take longer than 30 minutes |
| Issues | The patient is not comfortable sharing information |
| Use case | Schedule Appointments |
|---|---|
| Description | Schedules appointment for patients |
| Actors | Receptionist, patient |
| Assumptions | There is available space for the appointment |
| Steps | Patient goes through registration receptionist looks at doctors schedule and makes an appointment that works for both parties |
| Variations | Patient can also request to reschedule |
| Non-Functional | N/A |
| Issues | There is no available appointment |
| Use case | Notify Patient |
|---|---|
| Description | Receptionist sends notification to patient |
| Actors | Receptionist, patient |
| Assumptions | The patient gave correct contact information |
| Steps | Receptionist sends patient a notification |
| Variations | Patient can also request to reschedule |
| Non-Functional | Notification should be sent within 10 minutes |
| Issues | The patient’s device cannot be reached |
| Use case | Verify Patient Information |
|---|---|
| Description | Receptionist verifies patient details |
| Actors | Receptionist |
| Assumptions | The patient gave the correct contact information |
| Steps | Check and compare information on file and information given |
| Variations | Can request missing documents and update information |
| Non-Functional | Verification should take less than 10 minutes, and information should remain private |
| Issues | Could lead to false information by human error |
| Use case | Manage Waiting List |
|---|---|
| Description | Manges waiting list by adding and removing patients |
| Actors | Receptionist |
| Assumptions | The list has been updated correctly |
| Steps | Look up current list information/remove from the list |
| Variations | Move people around to accommodate when needed urgent cases do not need to wait |
| Non-Functional | Should be updated in real-time |
| Issues | There can be a slight delay while updating |