Doctor - SENG-350-2024-fall/Team4 GitHub Wiki
Item | Description |
---|---|
Use Case | 2.1. Send patient information to other departments. |
Description | Doctor can refer patient to primary care physician or any other specialists. |
Actors | Doctor |
Assumptions | The contact information for other offices has already been added into the system. |
Steps | 1. Sign in to the application 2. Click on patient being virtually triaged 3. Send file to an other office 4. Notify patient of the referral |
Variations (optional) | N/A |
Non-Functional (optional) | N/A |
Issues | Potential delays in the transfer of patient files due to network issues or system outages could hinder timely referrals. |
Item | Description |
---|---|
Use Case | 2.2. Request the patient for in-person follow up. |
Description | The doctor can request the patient to attend an in-person follow-up if deemed necessary based on the virtual triage. |
Actors | Doctor |
Assumptions | Patient has access to receive notifications and transportation to the ED. |
Steps | 1. Sign in to the application 2. Review patient's virtual triage information 3. Click "Request in-person follow-up" 4. Notify patient of the required follow-up appointment |
Variations (optional) | N/A |
Non-Functional (optional) | N/A |
Issues | Network or system outages could delay the delivery of follow-up requests. |
Item | Description |
---|---|
Use Case | 2.3. Monitor ED load. |
Description | Allows the doctor to monitor the current capacity and patient load in real-time at the emergency department. |
Actors | Doctor |
Assumptions | System has access to real-time data on ED load and patient queue information. |
Steps | 1. Sign in to the application 2. Access the "Monitor ED load" dashboard 3. View the current number of patients and estimated wait times 4. Adjust triage or suggest alternative actions if ED load is critical |
Variations (optional) | N/A |
Non-Functional (optional) | N/A |
Issues | System latency or lack of real-time data updates could affect decision-making. |
Item | Description |
---|---|
Use Case | 2.4. Access patient medical history. |
Description | The doctor can access and review the patient’s previous medical records to make informed triage decisions. |
Actors | Doctor |
Assumptions | Patient records are properly stored and integrated within the system. |
Steps | 1. Sign in to the application 2. Search for the patient by name or ID 3. View the medical history, including past treatments, medications, and hospital visits |
Variations (optional) | N/A |
Non-Functional (optional) | N/A |
Issues | Privacy concerns and ensuring patient consent to access their medical data. |
Item | Description |
---|---|
Use Case | 2.5. Adjust triage prioritization. |
Description | The doctor can adjust the prioritization of patients based on virtual triage data or new information provided. |
Actors | Doctor |
Assumptions | Doctors have the admin role to make triage adjustments in real-time. |
Steps | 1. Sign in to the application 2. Access the virtual triage results 3. Modify the triage level (e.g., critical, urgent, non-urgent) 4. Notify patient of the updated triage status |
Variations (optional) | N/A |
Non-Functional (optional) | N/A |
Issues | Inaccurate or delayed adjustments could result in delayed patient care. |
Item | Description |
---|---|
Use Case | 2.6. Review virtual triage results. |
Description | Doctors review the results of a patient’s virtual triage to determine the appropriate course of action. |
Actors | Doctor |
Assumptions | |
Steps | 1. Sign in to the application 2. Review the virtual triage results for each patient 3. Decide whether the patient should visit the ED, contact a GP, or follow an alternative course of action 4. Notify patient of the decision |
Variations (optional) | N/A |
Non-Functional (optional) | N/A |
Issues | Misinterpretation of virtual triage data could lead to incorrect recommendations. |