35 | | '''3.5. Postconditions''' |
36 | | Describe the state of the system at the conclusion of the use case execution. Number each postcondition. Examples: |
37 | | 1. Администраторот на системот да може да ги креира докторите, медицинските сестри и шалтерските работници, а пациентите да може да ги гледаат истите |
38 | | 2. Докторот да може да додаде пациент, а администраторот да може да го одобри и да биде креирана корисничка сметка и потоа пациентот да може да ја користи истата исто така медицинските сестри и шалтерските работници да може да ги гледаат додадените пациенти. |
| 36 | 1. Information for the new user of type ''patient'' must be accessible (name, surname, PIN, genre). |
| 37 | 2. Information for the new user of type ''doctor'' or ''nurse'' must be accessible (name, surname, PIN, genre, specialization*, working_time). |
| 38 | |
| 39 | '''3.5. Post-conditions''' |
| 40 | |
| 41 | 1. The system administrator has added doctors, nurses and patients. |
| 42 | 2. A doctor has added patients. |
| 43 | 3. The staff can have a look at the patients list in the hospital. |
| 44 | 4. The patients can have a look at all the staff information (name, surname, specialization, working_time/shift and room). |
| 45 | 5. Each doctor has an access to the full report data for all patients at which they are assigned to be a GP. |
41 | | 1. Администраторот се најавува на системот оди во соодветните модули за додавање на Доктори,медицински лица,шалтерски работници и креира нови корисници во соодветните модули. |
42 | | 2.Докторот се најавува на системот оди во модулот за додавање на пациенти и креира нов пациент. |
43 | | 3.Шалтрскиот работник се најавува на системот оди во модулот за додавање на пациенти и креира нов пациент |
| 48 | |
| 49 | 1. A system administrator or a doctor login into the system. |
| 50 | 2. Go to the module for adding new user. |
| 51 | 3. The new user's profile information are entered. |
| 52 | 4. The new user (patient/employee) is created. |
| 62 | '''3.9. Includes''' |
| 63 | |
| 64 | This scenario goes along with use cases for editing and deleting user profiles. |
| 65 | |
| 66 | '''3.10. Priority''' |
| 67 | |
| 68 | High priority. |
| 69 | |
| 70 | '''3.11. Frequency of Use''' |
| 71 | |
| 72 | Estimation: 2 patients per day. |
| 73 | |
| 74 | '''3.12. Business Rules''' |
| 75 | |
| 76 | All patients must be registered into the system before they are able to make appointments and visit the doctor. Exception can be emergency cases only. |
| 77 | |
| 78 | '''3.13. Special Requirements''' |
| 79 | |
| 80 | The system must be available 99% of the time during the hospital working hours, plus 95% of the time that is not during the working hours. |
| 81 | |
| 82 | '''3.14. Assumptions''' |
| 83 | |
| 84 | All patients agree to give their data to be kept into the system and be accessible by their doctors. |
| 85 | |
| 86 | '''3.15. Notes and Issues''' |
| 87 | |
| 88 | Issue 1: *task description*, assigned to: *name*, (a link to the task can be added here instead writing for each); |
| 89 | |
| 90 | Issue 2: Add a special table for the doctors specialists? Nurse and Doctor inherit out of Employee. |
| 91 | |
| 92 | Note 1: Field ''specialization'' is optional. It is required only for doctors specialists. The GP and nurses can have a default value of this attribute 'GP' or 'nurse' respectively. |
| 93 | |
| 94 | Note 2: Is it needed an admin to approve the patient that the doctor has added and why? |
| 95 | |
| 96 | === 4. Use Case List === |
| 97 | |
| 98 | System administrator |
| 99 | * Click button ''Add new *user*'', where user can be either a patient, a nurse or a doctor. |
| 100 | * Fill in information. |
| 101 | * Click ''Save'' |
| 102 | |
| 103 | Doctor |
| 104 | * Click button ''Add new patient''. |
| 105 | * Fill in information. |
| 106 | * Click ''Save'' |