12
INTRODUCTION Aim of this assignment is to develop a web application that can be used to keep track of the patients registering in a hospital. Also, this system should support features such as- accessing the previous visit histories of any patient, search for patients by name and other attributes, etc. • It maintains two levels of users:- Administrator Level User Level • The Software includes:- Maintaining Patient details. Providing Prescription, Precautions and Diet advice. Providing and maintaining all kinds of tests for a patient. Billing and Report generation. It can be used in any Hospital, Clinic, Dispensary or Pathology labs for maintaining patient details and their test results. Explanation of some frequently used terms for this system- 1. Patient - a patient is the person who visits the hospital for treatment/consultation 2. Doctor - a doctor will be assigned to each patient. 3. Bed - if patient type is "In Patient", a bed will be assigned to the user. 4. Visit - a patient can visit the hospital any number of times. Some of the most general requirements of the system are: • Registration of patients • Users are either normal users or admin; they need to login before using the system • Users of this system can search for patients by name, admission date and discharge date • Users can view the previous visit histories of any patient • System can maintain the list of doctors in the hospital • System can maintain the list of beds/rooms available in the hospital

UML DIAGRAMS for Hospital Management

Embed Size (px)

DESCRIPTION

UML for HMS

Citation preview

Page 1: UML DIAGRAMS for Hospital Management

INTRODUCTION

Aim of this assignment is to develop a web application that can be used to keep track of the patients registering in a hospital. Also, this system should support features such as- accessing the previous visit histories of any patient, search for patients by name and other attributes, etc.

• It maintains two levels of users:- Administrator Level User Level

• The Software includes:- Maintaining Patient details. Providing Prescription, Precautions and Diet advice. Providing and maintaining all kinds of tests for a patient. Billing and Report generation.

It can be used in any Hospital, Clinic, Dispensary or Pathology labs for maintainingpatient details and their test results.

Explanation of some frequently used terms for this system-

1. Patient - a patient is the person who visits the hospital for treatment/consultation2. Doctor - a doctor will be assigned to each patient.3. Bed - if patient type is "In Patient", a bed will be assigned to the user.4. Visit - a patient can visit the hospital any number of times.

Some of the most general requirements of the system are:

• Registration of patients• Users are either normal users or admin; they need to login before using the system• Users of this system can search for patients by name, admission date and discharge date• Users can view the previous visit histories of any patient• System can maintain the list of doctors in the hospital• System can maintain the list of beds/rooms available in the hospital• Patients can be categorized into "In Patients" and "Out Patients"

Our Web system has the following basic pages

1. Login page for the booking staffHome Page for the hospital- this page should contain some details about the hospital with a banner at the top.2. Site Map- This page is the gateway to the website and should depict the website structure and it should contain click-able links to all the pages.3. Privacy Policy- Has all the copyright and privacy policy information. Any website that deals with credit card transactions has to have one of these. 

Goal of Proposed System

Page 2: UML DIAGRAMS for Hospital Management

1. Planned approach towards working: - The working in the organization will be well planned and organized. The data will be stored properly in data stores, which will help in retrieval of information as well as its storage.

2. Accuracy: - The level of accuracy in the proposed system will be higher. All operation would be done correctly and it ensures that whatever information is coming from the center is accurate.

3. Reliability: - The reliability of the proposed system will be high due to the above stated reasons. The reason for the increased reliability of the system is that now there would be proper storage of information.

4. No Redundancy: - In the proposed system utmost care would be that no information is repeated anywhere, in storage or otherwise. This would assure economic use of storage space and consistency in the data stored.

5. Immediate retrieval of information: - The main objective of proposed system is to provide for a quick and efficient retrieval of information. Any type of information would be available whenever the user requires.

6. Immediate storage of information: - In manual system there are many problems to store the largest amount of information.

7. Easy to Operate: - The system should be easy to operate and should be such that it can be developed within a short period of time and fit in the limited budget of the user.

A Hospital is a place where Patients come up for general diseases. Hospitals providefacilities like:-

1. Consultation by Doctors on Diseases.2. Diagnosis for diseases.3. Providing treatment facility.4. Facility for admitting Patients (providing beds, nursing, medicines etc.)5. Immunization for Patients/Children.

Various operational works that are done in a Hospital are:-1. Recording information about the Patients that come.2. Generating bills.3. Recording information related to diagnosis given to Patients.4. Keeping record of the Immunization provided to children/patients.5. Keeping information about various diseases and medicines available to cure them.

These are the various jobs that need to be done in a Hospital by the operational staff and Doctors. All these works are done on papers.

The work is done as follows:-1. Information about Patients is done by just writing the Patients name, age and gender. Whenever the

patient comes up his information is stored freshly.2. Bills are generated by recording price for each facility provided to Patient on a separate sheet and at

last they all are summed up.3. Diagnosis information to patients is generally recorded on the document, which contains Patient

information. It is destroyed after some time period to decrease the paper load in the office.4. Immunization records of children are maintained in pre-formatted sheets, which are kept in a file.

Page 3: UML DIAGRAMS for Hospital Management

5. Information about various diseases is not kept as any document. Doctors themselves do this job by remembering various medicines.

All this work is done manually by the receptionist and other operational staff and lot of papers are needed to be handled and taken care of. Doctors have to remember various medicines available for diagnosis and sometimes miss better alternatives as they can’t remember them at that time.

Problems with conventional system

1. Lack of immediate retrievals: -The information is very difficult to retrieve and to find particular information like- E.g. - To find out about the patient’s history, the user has to go through various registers. This results in inconvenience and wastage of time.

2. Lack of immediate information storage: - The information generated by various transactions takes time and efforts to be stored at right place.

3. Lack of prompt updating: - Various changes to information like patient details or immunization details of child are difficult to make as paper work is involved.

4. Error prone manual calculation: - Manual calculations are error prone and take a lot of time this may result in incorrect information. For example calculation of patient’s bill based on various treatments.

5. Preparation of accurate and prompt reports: - This becomes a difficult task as information is difficult to collect from various registers.

Page 4: UML DIAGRAMS for Hospital Management

Use Case Diagram

Sequence Diagram

Delivery Normal Treatment Diagnosis

By Cash By Credit

ReceptionistTaking Appointment

Surgeon

Operation

Nurse

Assisting OperationAdmin

Generates a Bill

Patient

Payment of Bill

Doctor

Takes Treatment

Page 5: UML DIAGRAMS for Hospital Management

Collaboration Diagram

P1:Patient R1:Receptionist D1:Doctor N1:Nurse

Takes Appointment Takes Appointment

From Doctor

Doctor AvailableConfirms Appointment

Consults Doctor

Treats Patient

Patient OK

Assist Doctor

Ask For payment

Pays Fees

Page 6: UML DIAGRAMS for Hospital Management

D1:Doctor

P1:Patient R1:Receptionist

N1:Nurse

1: Takes Appointment10: Pay Fees

4: Confirms Appointment9: Ask For Payment

5: Consults Doctor8: Patient OK

7: Treats Patient

2: Takes Appointment from Doctor

3: Doctor Available

6: Assist Doctor

Page 7: UML DIAGRAMS for Hospital Management

State Chart Diagram

Idle

Patient Admitted

Validate

Operated Bill Generation

Patient Discharge

Event Of Patient

Patient approach hospital when ill

Page 8: UML DIAGRAMS for Hospital Management

Senior surgeon

specialization in

non-senior surgeon

specialization in

1..*

1

Surgeon

nameiddesignation

operate()

1

1..*

1..*

1

Operation theatre

operation_id

1

1..*

Nurses

nameidward_no

assisting()checking paitent health()

1

1..*

Hospital

nameidplace

administration()maintain info()add patient()add surgeon()

works for

works in

Patient Operation

nameoperation_idtypepatient_idsurgeon_idcost_of_operation

conducts

1..*1

Ward

ward_nopatient_admitted...nurse_assigned

assigned to

Patient

nameidtype_of_treatmentward_no

admitted in

undergoes admitted to1..*

1

Patient takes appointment

receptionist checks for doctor

patient needs to be operatedDoctor attains

patient

no

doctor is not available

no

undergoes operation

yes

patient consult doctor

Yes

surgeon operates paitent

nurse assist surgeon

patient gets operated

patient ok

discharge

yes

no

CLASS DIAGRAM

Page 9: UML DIAGRAMS for Hospital Management

ACTIVITY DIAGRAM

Page 10: UML DIAGRAMS for Hospital Management

COMPONENT DIAGRAM

DEPLOYMENT DIAGRAM

HOSPITAL MANAGEMENT SYSTEM LOCAL SERVER

HOSPITAL MANAGEMENT DATABASE

Utility

<<use>>

<<reside>>

HMS DATA PROCESSING

equipment database

<<use>>

User Interface

<<use>>

Desktop client

HOSPITAL LOCAL SERVER

Printer

Database server

<<Primary network>>

<<Private network>>

<<Private network>>

Page 11: UML DIAGRAMS for Hospital Management