Hospital Management System
Short Description
Case study on Hospital Management System...
Description
HOSPITAL MANAGEMENT SYSTEM
Prepared by-
Page 1
ACKNOWLEDGEMENT
It is our pleasure to acknowledge the help I have received from different individuals, institutions and ‘ABC hospital’ during the project based training period. Our first sincere appreciation and gratitude goes to Professor A. Ghaisas for his guidance, constructive comments, valuable suggestions and inspirations. During entire project, we have received endless help from him. Finally, I wish to say thanks to all people of the company for their kind cooperation.
Page 2
Table of Contents Sr. No.
Particulars
Page No.
1
Introduction
2
Business Objectives
3
System Objectives
4
Scope of the Project
5
Functional Decomposition Diagram
6
Data Flow Diagram
7
Entity Relationship Diagram
8
Table Design
9
Screen Design
10
List of Reports
Page 3
Introduction Brief description of business:
The hospital which we have studied for the assignment is ABC Hospital Ltd.
The hospital has following departments : Inward patient department , Outward patient department ,Pathology lab , X-ray , CT csan,Operation Theatre , Yoga center , Account dept , admin dept ,etc.
Details about hospital: No of doctors in the hospital 25 Total bed capacity 60 Types of ward : general, deluxe, super deluxe, semi –deluxe, ICCU, ICU No of nurse : 35 No of ward boys : 15
To narrow down the scope, four modules were selected for the assignment. The modules are as follows: 1) Patient registration 2) IPD 3) OPD 4) Pathology lab
Page 4
1) Patient registration: As soon as a patient enters the hospital for first time he/she should get registered (irrespective of ipd or opd) .Information such as personal details, family details, etc is recorded and a registration id is issued. Every time a patient is treated at the hospital he/she will be referred by this number.
2) IPD: Patient’s admission details such as reason for admission, ward details, operation details (if any), etc. are recorded whenever he/she is admitted. A discharge card is issued to the patient at the time of discharge stating the treatment summary. Also, a bill is prepared against the various services availed by the patient.
3) OPD: Consulting details of the patient are recorded and a bill is prepared (including the services such as pathology lab availed by the patient)
4) Pathology lab: Pathology lab is used for both ipd and opd. Depending on the test prescribed, tests are performed and results are recorded. Also, the charges are included in the bill given to the patient.
Page 5
Business objectives: •
The objective of the hospital management system is consistent growth of the Hospital, through continual improvement in the processes.
•
To provide quick, reliable, quality and error free service by making use of high end technology to ease the management of the patients.
•
To help administration in efficient management of the organization very smoothly by achieving high competency.
System Objectives: •
Transition of manual to Automated system
•
User Friendly
•
Time saving and more efficient
•
Reduce work load
•
Record maintenance
•
Security
•
Proper login name and password so that only valid user can assess the system.
•
Generate Information which helps in decision making for management purpose.
•
Manage activities of the hospital such as bed and Doctor Assignment, operations scheduling, personnel management and administrative issues.
Page 6
Functional Requirements Patient Registration Every patient who visits the hospital has to get registered prior to getting any consultation, treatment or investigations done. Registration of patients involves accepting certain general and demographic information about the patient. The patient is allocated a unique Registration number and a Patient Identification number. The Patient ID will remain same for his all subsequent visits to the hospital whereas he will be allocated a new registration number on every visit. The consultation charges (if applicable) can also be collected for the OPD patients during registration and a receipt will be generated.
The following information is required for the registration of OPD Patient: Patient Details like Name, Age, Sex, Address, Contact number, Nationality, etc. Referring Source and Sponsorship / Penal Details Department & Consultant to be visited.
For Inpatient the additional information requirements are: Room / bed requirement. Consultant In charge Treatment required Authorisation from Sponsor/Penal if required
After registration an OPD Card is printed for the OPD patients, which list all his registration information. This card is used for the prescription writing by the consultant. An Admission form is printed with all the registration details for Indoor patients, which serves as the cover page of the patient file.
Page 7
Receipt For billing of any OPD service like Pathology Tests, or any imaging investigation, the patient moves to OPD billing counter. Here the services are charged as per the rates already defined for various categories/ penal/ time etc to the patient with his Patient ID. The Payment is collected for the service provided and a receipt is generated. The receipt is generated at the service desk. All services will be automatically entered into the respective modules wherever required like lab & Imaging reporting.
The Salient features of this module are:
i.
Record Charges to be taken from the patient.
ii.
Record details of the concession & concession authority.
iii.
Consultant charges are automatically picked according to general or emergency charges.
iv.
The charges for the services are automatically picked according to the category or panel of the patient.
v.
The charges are also dependent on time when the service is being given to patient.
vi.
When patient revisits his information will be automatically picked using his identification number.
vii.
Patient can be defined under Cash & Credit OPD.
viii.
All relevant information is transferred to the Investigation departments.
Page 8
Billing: Indoor billing module has a supervisory role. The entries for billing are automatically transferred to the patient bill by the respective departments, which provide the service. The services are charged as per the category/panel/package applicable.
Here the bill is compiled and the payment collected from time to time. Provisional and Final bills are generated which provides complete information about the Services availed, its Charges, Advance collected, appropriate Receipts, Refunds, Credit notes, Concession allowed, etc.
Salient Features: i.
Collection of Payment by Cash/Credit Card/ DD or Cheque.
ii.
Receipts, refunds, Credit Note Generation.
iii.
Provisional & Final Bills.
iv.
Department wise services availed.
v.
Automatic scrutiny of the credit limit available to the patient
vi.
Provision to bill a patient against another account (LIC account/company account/Donors account etc.)
vii.
Additional payment for Ambulance/attendants at discharge if required.
Page 9
Medicine The Medicine Module deal with the Retail Sale of medicines to OPD patients and Issue of medicines to the In-patients in the hospital. Its function includes, online drug prescription, inventory management and billing of drugs, consumables and sutures. This module is closely linked to the Billing Module and Inpatient Module. All the drugs required by the patient can be indented from the various sub stores.
Salient Features: i.
This module enables complete control on pharmacy including Purchase & Issue of medicine to IPD or OPD Patient.
ii.
Total amount of the bill for IPD Patient will automatically get added in his bill.
iii.
The Medicine can acknowledge the return of items and issue Credit notes.
iv.
Items cannot be issued after the expiry date.
Bed This module deals with the allocation of bed to the in house patients. It has an interface with the billing module. The charges levied to any bed are automatically added to the final bill.
Salient Features: i.
This module enables complete control on the allocation of beds.
ii.
The beds are of various types (i.e, ICU, General etc.).
iii. iv.
A single patient may change the type of bed allotted to him during his period of stay at the hospital. The bed charges are added to the boll automatically.
Page 10
Other functionalities: Security: Each member is required to enter an individual password when accessing the site. Administrators have the option of increasing the level of password security their members must use. The data on your site is secured through multiple layers of protection. One of those security layers involves member passwords. For maximum security of your site, each member must protect their password.
Performance requirements: The performance of our product is at its best if stored locally, as the response time will be much faster. If the product accessed via Internet, the performance is limited by the connection speed. The only foreseen limitation is that of web-server response.
Safety: Humans are error-prone, but the negative effects of common errors should be limited. E.g., users should realize that a given command will delete data, and be asked to confirm their intent or have the option to undo.
User Documentation The form generation language will be separately documented.
Page 11
Scope of application software: Login: • • • •
Allows the doctors, attendants, and management to login to the system using their respective login ids. Doctors will be able to manage their information (like input their availability for the week or day), view patient case history, treatment details, test reports etc. Attendants will be able to help the patients to view their case history, treatment details, appointment with the doctors, bill details, wards, medical services provided, test results etc. Management will be able to view some overall records pertaining to them and then see reports.
Patient registration: As soon as a patient enters the hospital for first time he/she should get registered (irrespective of ipd or opd) .Information such as personal details, family details, etc is recorded and a registration id is issued. Every time a patient is treated at the hospital he/she will be referred by this number.
IPD: Patient’s admission details such as reason for admission, ward details, operation details (if any), etc. are recorded whenever he/she is admitted. A discharge card is issued to the patient at the time of discharge stating the treatment summary. Also, a bill is prepared against the various services availed by the patient.
OPD: Consulting details of the patient are recorded and a bill is prepared (including the services such as pathology lab availed by the patient)
Pathology lab: Pathology lab is used for both ipd and opd. Depending on the test prescribed, tests are performed and results are recorded. Also, the charges are included in the bill given to the patient.
Page 12
FDD:
Page 13
Context Level DFD
Page 14
First level DFD
Doctor Administrator
Doctor master maintenance Medicine master maintenance
1
Bed Master Maintenance Service Master Maintenance
Medicine Master Maintenance
Lab Master Maintenance Maintenance notification Bed
Service Test
Page 15
Test Details
Patient
Enquire general service
2
Appointment details
Medicine Service
Medicine Details
Test Change of bed details Bed
Service Doctor
Patient Patient
Enquire consulting doctor
3
Pay Consulting fees Test details
Medicine
OPD
Medicine details Provide Prescription
Doctor
Doctor Consulting Payment
Page 16
Bill
Patient Patient
Admission
Receipt Medical services
4 Medicine
Bed allotment Tests and treatment
Doctor
IPD Bed
Provide diagnosis/treatment details
Doctor Test Bill
Service
Page 17
Patient Patient Details
Patient
Services Services details Doctor Consultation details
5
Billing
Medicine
Bill
Receipt
Bill
Page 18
Patient
Payment Details
Patient Bill details
6 Bill
Receipt details
A/C receivable
Receipt
Page 19
Patient
Patient Discharge details Followup details
Doctor
7
Discharge Card
Page 20
Discharge
Patient Administrator
Queries
Receipt Reports
8
Reports
Medicine Bed Doctor Test Bill
Service
Page 21
Admin
User Access details Sign in details
User
9
Login
Security confirmation
Page 22
Second level DFD
1- Master maintainence 1.1 Bed Master 1.1 Maintainence
Bed master details
Medical master details
Bed
1.2 Medical Master Maintainence
Medicine
1.3 Service master details Administration
Service Master Maintainence
Service
Doctor master details 1.4 Lab master details Doctor Master Maintainence
Doctor
1.5 Lab Master Maintainence
Page 23
Test
2- Services
Service 2.1 Patient
Avail a service
Patient
General Services
Service details
Medicine 2.2 Patient
Medical prescription
Purchase Medicine
Patient
Issue of medicines
2.3 Patient
Change request
Change Bed
Availability status
Bed Patient
Page 24
2.5 Patient
Test details
Doctor Appointment
Test report details
Test Patient
3-OPD
3.1 Patient
Appointment Details Test report details
Doctor
Consulting Doctor
Provide Prescription
Doctor Patient
Doctor
Patient
Doctor Prescription Details Bill details
3.2 Bill
Bill Payment
Page 25
Patient
4-IPD
Services Fetched Details 4.1 Patient
Patient Details Bed allotment details
Doctor
Admittance details
Bed
Allotment of room
Patient
Services
4.2 Doctor
Patient Treatment details Doctor
Diagnosis Treatment
Provide Treatment Prescription
Patient Medicine
Bill
Receipt
Page 26
5- Billing Patient 5.1 1.1 Compute Doctor Charges Doctor consultation details
Services details
Bed alloted details Patients
5.2 .2 Compute Services Charges
Bed Doctor
Patient Medicine Service
5.3 3 Compute bed charges
Patient Bed
Medicine details 5.4
Final bill generation
Compute Medicine charges
5.5
Taxes and issue bill
Patient Medicine Test
Patient Test Medicine
Page 27
ERD:
Page 28
TABLE AND DATA DICTIONARY TABLE DESIGN:
Service:
Attribute
Type
Width
Key
Constraint
Description
Ser_id
Number
6
Primary
Not Null, Unique
Gives the Unique service Id No
Key Ser_name
Varchar2
10
Not Null
Gives the service Name
Ser_desc
Varchar2
15
Not Null
Describe the service
Cost_per_unit
Number
5
Not Null
Gives the cost per unit for each service
Page 29
Doctor: Attribute
Type
Width
Key
Constraint
Description
Doc_id
Number
6
Primary
Not Null, Unique
Unique for every doctor
key Doc_name
Varchar2
20
Not Null
The doctor’s name
Doc_contact
Number
14
Not Null
Doctor’s Contact Details
Doc_address
Varchar2
50
Not Null
Doctor’s Address
Doc_Specialization
Varchar2
20
Not Null
Doctor’s Field Of Specialization
Doc_ Cons_Fees
Number
6
Not Null
Consultation Fees
Doc_dpt
Vacrchar2 15
Not Null
Type of department
Page 30
Medicine:
Attribute
Type
Width
Key
Constraint
Description
Med_id
Varchar2
6
Primary
Not Null, Unique
Gives the Medicine Id
key Med_desc
Varchar2
10
Not Null
Medicine Details
Manf_Name
Varchar2
10
Not Null
Name of the Medical Manufacturer
Med_type
Varchar2
10
Not Null
Type of medicine
Med_cost_per_unit
Number
5
Not Null
Cost per unit of medicine
Attribute
Type
Width
Key
Constraint
Description
Bed_id
Varchar2
6
Primary
Not Null, Unique
Gives the Bed Id
Bed:
key Bed_type
Varchar2
10
Not Null
Gives the type of bed
Bed_Cost_per_day
Number
6
Not Null
Gives the bed
Page 31
cost per day
Registration:
Attribute
Type
Width
Key
Constraint
Description
Reg_id
Varchar2
6
Primary
Not Null, Unique
Is Unique For Every Registration
key Reg_By
Varchar2
20
Registration Incharge
Reg_reason
Varchar2
30
Reason for admittance
Patient_Id
Varchar2
6
Foreign Key
Page 32
Not Null
A reference to the patient id
Patient: Attribute
Type
Width Key
Constraint
Description
Patient_id
Varchar2
6
Not Null, Unique
Is Unique For Every patient
Not Null
Name of the patient
Not Null
Date of birth of the person
Not Null
Sex of the patient
Primary key
Patient_name
Varchar2
Patient_dob
Date
Patient_sex
Varchar2
20
10
Patient contact number
Patient_contact_no Number
14
Patient_Address
Varchar2
50
Patient_type
Varchar2
10
Patient of opd or ipd
Patient_category
Varchar2
20
Company candidate or normal
Not Null
Page 33
Address of the patient
Bill:
Attribute
Type
Width
Key
Constraint
Description
Bill_No
Varchar2
6
Primary
Not Null, Unique
Generated Automatically and is unique
Not Null
Generated When bill is printed
key Bill_date
Date
Bill_amt
Number
10
Not Null
Generated with the bill
Reg_Id
Varchar2
6
Not Null
A reference to registration
Attribute
Type
Width
Key
Constraint
Description
User_Id
Varchar2
6
Primary
Not Null, Unique
Unique user id
Not Null
User name
Not Null
Access to system
User
key User_Name
Varchar2
Access
Varchar2
10
Page 34
Receipt: Attribute
Type
Width Key
Constraint
Description
Rec_No
Number
6
Not Null, Unique
Is Unique for every patient
Not Null
Date of receipt generation
Not Null
Amount for which the receipt is generated
Not Null
A reference to registration
Not null
Mode Of Payment
Primary key
Rec_date
Date
Rec_amt
Number
10
Reg_Id
Varchar 2
6
Payment_Mode
Varchar2
10
Foreign key
Page 35
Dicharge_Card: Attribute
Type
Width
Key
Constraint
Description
Discharge_card_id
Varchar2
6
Primary
Not Null, Unique
Gives the Uniques service Id No
Not Null
Gives the patient Id
key Foreign key
Patient_Id
Varchar2
6
Follow_up
Varchar2
100
Not Null
Gives the follow up
Doc_details
Varchar2
50
Not Null
Gives the doctor details
Next_ appointment_date
Date
Not Null
Gives the next appointment date
Reg_id
Varchar2
Not Null
A reference to the registration
6
Foreign key
Page 36
Test: Attribute
Type
Width
Key
Constraint
Description
Test_id
Varchar 2
4
Primary key
Not Null, Unique
Gives the unique test id
Test_name
Varchar 2
20
Not Null
Name of the test
Test_desc
Varchar 2
30
Not Null
Description of the test
Test_type
Varchar 2
20
Not Null
Type of test
Rate
Number
(6,2)
Rate of test
Page 37
Input Form Medicine_Master_Form:
Page 38
Doctor_Master_Form:
Page 39
Service_Master_Form:
Page 40
Bed_Master_Form:
Page 41
Registration_Master_form
Page 42
Bill_Form:
Page 43
Medicine_Purchase_Form:
Page 44
Discharge_Card_Form:
Page 45
Receipt_Form:
Page 46
Doctor_View_Form:
Page 47
REPORTS Month Wise Revenue Report: Name of the Report Purpose User
: Month wise revenue generated : To analyze monthly revenue generated from different department : Lower Level Management
Tables referred : doctor, patient, bill
Page 48
Quarterly Revenue Report:
Name of the Report Purpose User
: Quarterly revenue generated : To analyze quarterly revenue generated from different department : Middle Level Management
Tables referred : doctor, patient, bill
Page 49
Yearly Revenue Report:
Name of the Report Purpose User
: Yearly Revenue Collected From different Department : To analyze Yearly revenue generated from different department : Top Management
Tables referred : doctor, patient, bill
Page 50
Number of Patients Referred Report: Name of the Report Purpose User
: Yearly Number of Patients Referred : To analyze number of patients referred by a doctor : Management
Tables referred : doctor, patient, test, medicine
Page 51
Yearly Category wise Patients Report: Name of the Report Purpose User
: Yearly category wise patient Report : To analyze different category of patients : Management
Tables referred : patient, service, medicine, bill
Page 52
Yearly Company wise Patients underwent Treatment Report:
Name of the Report Purpose Users
: Company wise number of Patient undergone treatment in hospital : To analyze revenue generated from a company : Management
Tables referred : patient, service, medicine and bill
Page 53
Bed wise allocation Report: Name of the Report Purpose Users
: bed wise allocation report : To provide bed to the patient unambiguously : Lower level Management
Tables referred : patient, bed, medicine and discharge card
Page 54
Bed wise availability Report: Name of the Report Purpose Users
: bed wise availability status report : To provide bed status to the patient : Lower level Management
Tables referred : bed, service, patient
Page 55
Hospital Bill Report: Name of the Report Purpose Users
: Hospital Bill : To provide Bill to the patient at the time of discharge : Lower level Management
Tables referred : patient, bill, doctor, discharge card, service
Page 56
OPD/IPD Registration Report: Name of the Report Purpose Users
: OPD/IPD registration report : To provide details of patient at OPD/IPD : Lower level Management
Tables referred : patient, service, doctors
Page 57
View more...
Comments