| ID | Requirements |
|---|---|
| 1 | Login Page |
| 1.1 | Alternative flow for 1 – Forgot Password Case |
| 2 | Find Patient |
| 3 | Start Patient's Visit |
| 4 | Create New Patient |
| 5 | Create a new Concept |
| 6 | Find Concept |
| 7 | Capture Vitals |
| 8 | Create an appointment |
| Use Case | Login Page |
|---|---|
| Id | 1 |
| Brief Description | The doctor/user wants to login on the web platform |
| Primary Actors | User |
| Secondary Actors | System |
| Preconditions | - |
| Main Flow | 1. The user accessed the OpenMRS platform and can view the login screen. 2. The user enter their credentials (username and password) to login. 3. The user selects the log in option. 4. The system will display the Home Page |
| PostCondition | The user is logged onto the platform. |
| Alternative Flows | Forgot PasswordCase Help Case |
| Use Case | Alternative flow for 1 – Forgot Password Case |
|---|---|
| Id | 1.1 |
| Brief Description | The user has forgotten their password |
| Primary Actors | User |
| Secondary Actors | System |
| Preconditions | - |
| Main Flow | 1. If the user forgot their password, they will be redirected to the “Forgot Password” Page 2. The user needs to type in their username. 3. The password will then be changed. |
| PostCondition | |
| Alternative Flows | - |
| Use Case | Find Patient |
|---|---|
| Id | 2 |
| Brief Description | The user wants to find a patient |
| Primary Actors | User |
| Secondary Actors | System |
| Preconditions | The user is logged in |
| Main Flow | 1. The user accesses the "Find/Create Patient" tab on the menu. 2. The user will be redirected to the "Find Patient" page. In the Patient Search, the user can type in the patient's name (let's say "John") or identifier. 3. A list with all the patients called "John" will be displayed. The user can access the data of the patient by clicking on the table row. 4. The user will be redirected to the patient page where they can access several information (the overview tab which presents data regarding the Patient Actions, Programs, Relationships, Allergies, Problem List; the visits page which presents information on the last patient's visits; the demographics tab which presents the patient's name as well as the address, the graph tab which shows a graph depending on the concepts chosen - for example: pulse; and the form entry tab which gives data on the registered encounters.) |
| PostCondition | - |
| Alternative Flows | - |
| Use Case | Start Patient's Visit |
|---|---|
| Id | 3 |
| Brief Description | The user wants to start a patient's visit |
| Primary Actors | User |
| Secondary Actors | System |
| Preconditions | The user is logged in |
| Main Flow | 1. The user accesses the "Find/Create Patient" tab on the menu. 2. The user will be redirected to the "Find Patient" page. In the Patient Search, the user can type in the patient's name. 3. A list with all the patients having the inputed name will be displayed. The user can access the data of the patient by clicking on the table row. 4. The system will redirect the user to the Patient's Page. By clicking the "Start Visit" button, the user will be redirected to the a new page where they need to complete a form with visit details and ecounters. 5. In the Visit Details Tab the user needs to input the patient's name, visit type, start time and end time of the visit, the location and indication (concept name or id). 6. In the encounters'tab the user can add new encounters. 6. The user can then save the formed which will then be saved in the sever's database. |
| PostCondition | A new visit has been added to the patient's page and saved into the server's database. |
| Alternative Flows | - |
| Use Case | Create New Patient |
|---|---|
| Id | 4 |
| Brief Description | The user wants to create a new patient |
| Primary Actors | User |
| Secondary Actors | System |
| Preconditions | The user is logged in |
| Main Flow | 1. The user has to access the Create/Find Patient Tab in the Home Menu. 2. In the Create Patient tab the user needs to introduce the data of the new patient. (person name, birthday/age, gender) 3. By clicking on the Create Patient Button, the user will be redirected on a new page where they have to input more patient's data such as id number, demographics and address. |
| PostCondition | A new patient has been created. |
| Alternative Flows | - |
| Use Case | Create a new Concept |
|---|---|
| Id | 5 |
| Brief Description | The user wants to create a new concept. |
| Primary Actors | User |
| Secondary Actors | System |
| Preconditions | The user is logged in |
| Main Flow | 1. The user has to access the Create/Find Patient Tab in the Home Menu. 2. In the Create Patient tab the user needs to introduce the data of the new patient. (person name, birthday/age, gender) 3. By clicking on the Create Patient Button, the user will be redirected on a new page where they have to input more patient's data such as id number, demographics and address. |
| PostCondition | A new patient has been created. |
| Alternative Flows | - |
| Use Case | Find Concept |
|---|---|
| Id | 6 |
| Brief Description | The user wants to find a concept in the database. |
| Primary Actors | User |
| Secondary Actors | System |
| Preconditions | The user is logged in |
| Main Flow | 1. The user has to access the Dictionary Tab in the Home Page. 2. The user will then write the name or the id of the concept in the "find concept" tab. 3. Information about the concept will be displayed. |
| PostCondition | Information about the concept will be displayed. |
| Alternative Flows | 1. Cancel Form Use Case 2. Delete Concept Use case |
| Use Case | Capture Vitals |
|---|---|
| Id | 7 |
| Brief Description | The user wants to capture patient's vitals. |
| Primary Actors | User |
| Secondary Actors | System |
| Preconditions | The user is logged in |
| Main Flow | 1. The user selects the "capture vitals" option from the menu. 2. A list with all the patients will be displayed. 3. The user selects one of the patients. 4. The user will fill in a form with the patient's vitals. (height, weight, pulse, heart rate etc) 5. The user will select the save option to save the form. |
| PostCondition | The information will be stored in the server's database. |
| Alternative Flows | 1. Cancel Form Use Case |
| Use Case | Create an appointment |
|---|---|
| Id | 8 |
| Brief Description | The user wants to create a new appointment. |
| Primary Actors | User |
| Secondary Actors | System |
| Preconditions | The user is logged in |
| Main Flow | 1. The user selects the "Appointements" option from the menu. 2. In the Existing Appointements tab the user will choose the "Schedule new appointment" option. 3. The user will be asked to choose between "Schedule New Appointment" and "Add Walk-In Appointment". 4. After choosing the "Schedule new Appointment" option, the user will be redirected to the "Create Appointment" page 5. The user will have to fill in a form with their details as well as appointment properties (location, provider, date), select a time and also enter any additional notes. 6. The user will then save the form. |
| PostCondition | A new appointment for the upatient has been created. |
| Alternative Flows | Cancel Form Use Case |