Different kinds of tools are used in analysis of which interview is a common one.Our application will help the doctors to treat the patients effectively. Our application will help the doctor to access the data anytime of the day without much trouble. He can directly search for a specific data such as patient’s record or to know the details of a disease. To know the cause of a disease, to know the treatment methods used to treat for that specific disease.
Use case modelling
HMS Use case1
HMS Use Case2
HMS Use Case3
Detailed Use cases
HMS DUC-1
| Use Case: Admin Actions |
| ID: HMSUC-1 |
| Actors: 1.Admin 2.Doctor 3. Receptionist 4. Patient |
| Preconditions:1)User should have Admin role authorization 2)User should have Doctor role authorization 3) User should have Receptionist role authorization 4) User should have Receptionist role authorization |
| Flow of Events:
1. The use case starts when Admin logins into the system 2. Doctor edit doctor details 3. Receptionist confirms appointment 4. Patient makes appointment and consult doctor |
| Post conditions:
1. Admin will be adding the different users to the system and adding services to the users 2. Receptionist will edit appointment for patient 3. Patient edits patient details 4. Patient will be receiving notification regarding his updated appointment with doctor |
HMSDUC-2
| Use case: Edit Appointment for patient |
| ID: HMSUC-2 |
| Actors:
1. Receptionist 2. Doctor |
| Preconditions:
1. User should have Receptionist role authorization 2. User should have Doctor role authorization |
| Flow of Events:
1. The receptionist will accept fee and print slip 2. Doctor can modify the schedule and print slip |
| Post conditions:
1. Receptionist will be editing an appointment for patient with doctor 2. Doctor will be receiving notification regarding his updated appointment with patient 3. Patient will be receiving notification regarding his updated appointment with doctor |
HMSDUC-3
| Use case: Add service to patient |
| ID: HMSUC-3 |
| Actors:
1. Receptionist |
| Preconditions:
1. User should have Receptionist role authorization |
| Flow of Events:
1. The use case starts when Receptionist logins into the system 2. The Receptionist will schedule patient hospital admission 3. The receptionist will update in-patient and out-patient details 4. The receptionist will add service to the patient |
| Post conditions:
1. Receptionist will add the service to the patient 2. Patient will be receiving the details regarding his service |
- Requirement tracebility matrix
| Requirements | Use case diagrams |
| 1. Registration | |
| 2. Report generation |
- Initial Snapshots
Glossary
- HMS- Hospital Management system
- Admin
- Receptionist
- Doctor
- Patient
- HMSUC-x- Hospital Management System- x – denotes the number of use case model
- Roles- HMS Users Authorization role
References
- http://websiteonlinesolution.com/hospital-management-system/
- http://www.sitepoint.com/database-design-management/
- https://en.wikipedia.org/wiki/Agile_management
- http://www.w3schools.com/js/
- https://www.codecademy.com/learn/javascript
- https://www.google.com
- https://diagram.ly
- https://www.umldiagram.org
Contributions :
Team Members
Member 1: Designing the requirements specification
Member 2: Designing the use case diagrams
Member 3: Designing the snapshots
Member 4 :Designing the detailed use case diagrams