Download Hospital Management System-Computer Sciences-Project Report and more Study Guides, Projects, Research Applications of Computer Sciences in PDF only on Docsity!
1 Hospital Management System
HMS is an integrated health information system, which addresses the critical requirements of hospitals. It provides the benefits of streamlining of operations, enhanced administration and control, improved response, cost control and improved profitability. It provides easy access to critical information there by enabling the management to take better decisions on time. The idea behind this project is to provide the hospital, under the supervision of Sultana Foundation, with a system with the help of which it can get rid of the manual procedures. A system is needed that can maintain hospital’s daily routine of patient’s registration, checkup, medicine prescription, laboratory tests, medical stock’s acquiring and can generate reports required by the hospital. The software composes of four modules i.e. patients, doctors, laboratory and medical store. This HMS is a high performance database system designed specifically for keeping records for patients, doctors, laboratory test results for each patient, medicine stock in medical store and medicine prescribed to each patient.
1.1 Summary of Work Done
The summary of the work done until now is as follows:
1.1.1 6 th^ Semester Work:
Software Requirement Specification Software Project Management Plan
1.1.2 Summer Break Work:
Software lifecycle Literature survey (books, www, papers)
1.1.3 7th Semester Work:
Mid Term Progress: Data flow diagrams
Entity relationship model Data model Design architecture 7th semester final work done: Revision of ERD Relational model Scenario based model (use case diagrams, activity diagrams) Class model Behavioral model (state, sequence diagrams)
Doctor
Medical store
User
AdministratorSystem
Receptionist
Laboratory
examine Patient
AppointmentSchedule
register
provideinfo
accountissues
is a
medicine^ get from
done at^ tests view
view upgrade
1
N
M
1
1 1
N N 1
N
1 1
1
1
1
N
N
1
N
1
1
1 1
Figure 1: Entity-Relationship Diagram
3 Relational Model
3.1 Mapping Regular Entities
3.1.1 Doctor:
Doctor_id FName LName gender address nationality qualification date_of_joining specialization NIC_no
3.1.2 Patient:
Patient_id FName LName gender DOB height weight Test_report
3.1.3 Laboratory:
Test_name Test_desc
3.1.4 Medical Store:
Medicine_name Total_quantity Consumed_medicines
Available_quantity Date_of_acquiring Billing_info
3.1.5 Administrator:
FName LName Admin_id
3.1.6 Receptionist:
Rec_id FName LName gender NIC_no address Nationality Qualification
3.1.7 User:
User_id Password FName LName
3.3.2 Many-One Relations:
There are five N: 1 relationships in the ERD as follows
- Receptionist -> Appointment schedule (view)
- Receptionist -> Appointment schedule (upgrade)
- Doctor -> Appointment schedule (view)
- Patient -> Laboratory (get tests done at)
- Patient -> Medical store (get medicine from)
View: Doctor_id Patient_id
Appointment schedule: Doctor_id Patient_id Appointment_time Available_time Appointment_date
Upgrade: Doctor_id Patient_id
Appointment schedule: Doctor_id Patient_id Appointment_time Available_time Appointment_date
View: Appointment_date Appointment_time Doctor_id Patient_id
Appointment schedule: Doctor_id Patient_id Appointment_time Available_time Appointment_date
Get tests done at: Test_name Start_date Finish_date
Laboratory: Test_name Test_desc
Get medicine from: Medicine_name
Medical store: Medicine_name Total_quantity Consumed_medicines
Available_quantity Date_of_acquiring Billing_info
3.4 Mapping of Multi-valued Attributes
Following are the two multi-valued attributes in the ERD.
3.4.1 User_job/title:
User_id Job/title
User: User_id Password FName LName
3.4.2 Patient_type:
Patient_id Patient_type
Patient: Patient_id FName LName gender DOB height weight Test_report
3.5 Mapping of N-ary Relationship
Is a: Rec_id Medicine_name Test_name Lab assistant Store_keeper
Provides info: Rec_id Medicine_name Test_name Number_of_patients Number_of_tests_done Test_charges Medicines_acquired
4.1.2 Patient:
pay for medicines (from
Patient (f rom Actors)
provide registration details (from
4.1.3 Receptionist:
keep appointment schedule (from
doctor visit schedule (from
Receptionist (f rom Actors)
extract patient history (from
register patient (from
Figure 4: Use case Diagram for Receptionist The receptionist can be any junior doctor or sisters. He/She handles various enquiries about the patient's registration as well as Doctor Consultation and Scheduling, Time Allocation. Doctor visit schedule Doctor appointment scheduling Patient registration Find history of patient
4.2 Activity Diagrams
Activity diagram is a variation of a state chart diagram that focuses on a flow of activity driven by internal processing within an object rather than by events that are external to it. In an activity diagram most or all states are action states each of which represents the execution of an operation. Following are the elements of activity diagrams. Activity: some behavior that may persist for the duration of the state Transition: caused by the completion of previous activity Synchronization bar: provides a way to express things like waiting for all subtasks to finish before proceeding and starting several subtasks in parallel Decision diamond: used to show decisions Start and stop markers: to show the start and stop of the process
4.2.1 Register Patient:
request to register patient
already registered?
update patient table (^) yes
no
Figure 8: Activity Diagram for Register Patient When a patient arrives, if he has not been registered, he will have to register himself. The receptionist will register the patient using information provided by the patient. The
registration information will be updated in the patient’s record. If he is already registered, the registration process ends.
4.2.2 Patient History Provided to the Doctor:
check if patient is registered
extract patient history
provide doctor with compiled history
register patient
no
yes
Figure 9: Activity Diagram for Patient History When the patient arrive the hospital, if he is not register, he will have to register himself. Otherwise he can go to consult doctor. The receptionist will extract patient’s history and provide the doctor with the compiled history of the patient.
4.2.4 Laboratory:
take test samples
perform prescribes test
update patient table generate report about test result
deliver report to patient
Figure 11: Activity Diagram for Laboratory At the laboratory, the lab assistant will get the sample for the test, perform the prescribed test and update the result in the patient’s table as well as generate the test report. Then the patient will get the report.
4.2.5 Appointment Schedule:
check the consultant'savailable time
appoint patient
Figure 12: Activity Diagram for Appointment Schedule Receptionist will check the consultant’s appointment schedule, and assign the appointment time with the patient.
4.2.6 System Administrator:
check modules' performance
grant permissions
generate monthly progress report assign login account toeach user
select job
Figure 13: Activity Diagram for System Administrator The system administrator will select the job. If he is going to create user accounts, he will grant permissions to different kind of users. And assign login accounts to them. If he wants to get information from the modules he will select the other job. He will generate the report using gathered information like, no. of patients per month (paying or free of cost), no. of tests done and their charges, medicines acquired and consumed in a month.
4.2.8 Medical Store:
ask for medicine
enter billing record
available
type of customer
get medicine
no yes
paying free of cost
Figure 15: Activity Diagram for Medical Store When the customer arrive the medical store, he will ask for the medicine. If the named medicine is available, the store keeper will check if the customer is paying or free of cost. This information will be provided by the patient’s registration information. If he is paying customer, he will get the medicine and his billing record will be updated. Both customers will get the medicine.
4.2.9 Overall Processing in the System:
The patient will be registered first. Then he can consult the doctor. After patient’s examination by the doctor, he will get the prescribed medicines or get the tests done at the hospital’s laboratory. Following activity diagram shows this. Each activity has its sub-activities embedded inside.
get medicine from medical store
get prescribes tests done
patient examination by doctor
register patient
Figure 16: Activity Diagram for Overall Processing of the System
