A PROJECT REPORT FOR DEPICTION OF

HOSPITAL MANAGEMENT SYSTEM

SUBMITTED BY: KANIKA SHRIDHAR SANIA MAHAJAN KUNAL GUPTA

INTRODUCTION
The " HOSPITAL MANAGEMENT " system forms a basic entity of the management of a Hospital. Hence, it is very important for the system to be reliable, user friendly, and should be properly functional for a long time without cropping up of any errors. To start with the system study we visited Bhagat Hospital in Janak Puri. There we took the help of Dr. C.M. Bhagat. He showed us the project which he is using in his daily life for management of his hospital. This project gave me the idea of the different fields that ought to be in a Hospital Management System such as patient registration, his/her advance payment, the records, the details etc.. and also that how a software system can make the work easy both for the hospital staff and the patient. Moreover, the evaluation helped me to arrive at the conclusion that the automated software are far more superior to the manual ones. The database structure was then taken into account based on the input and output data. The ERD's (Entity Relationship Diagram) and the DFD's (Data Flow Diagrams) and various flowcharts are also drawn showing the flow of information and data.

CERTIFICATE

This is to certify that the project entitled HOSPITAL MANAGEMENT submitted by Kanika Shridhar , Sania Mahajan and Kunal Gupta has been carried out under our supervision. The project is submitted in fulfillment of the requirement for the 4th semester of Computer Sc. (H).

Teacher-in-charge

ACKNOWLEDGEMENT
On the successful completion of our project entitled HOSPITAL MANAGEMENT, we would like to express our sincere gratitude to everyone who helped us throughout in the making of this report. We are sincerely thankful to Ms. Bhawna, the Project Incharge, for being the constant source of help, knowledge and encouragement. We express our sincere gratitude to Ms. Deepali for her cooperation and are thankful to Ms. Anita and Mr. Negi for their help in gathering the software tools required for the project. Kanika Shridhar Sania Mahajan Kunal Gupta
4

CONTENTS

1. SYSTEM REQUIREMENT 2. REQUIREMENT SPECIFICATION 3. FLOWCHARTS 4. ANALYSIS MODELING 5. TEST PLAN 6. FUTURE ENHANCEMENTS 7. BIBLIOGRAPHY 8. SUGGESTIONS

SYSTEM REQUIREMENT
1. FUNCTIONAL REQUIREMENTS 2. NON- FUNCTIONAL REQUIREMENTS

SYSTEM REQUIREMENT
1. FUNCTIONAL REQUIREMENTS The software is to atomize the Hospital Management: The user is the non-remedial staff such as receptionist.

 The system should provide the facility for storing the information in the database and hence perform modification as required. The system should have a user-friendly interface so that the user can adapt to the new system easily. The database should be reliable and developed such that if at some time later stage the software has to be upgraded, the database is not affected.

2. NON FUNCTIONAL REQUIREMENTS

EFFICIENCY: The software should not make wasteful use of the system resources such as memory and processor cycles. The response time should be kept minimum. PORTABILITY: The software should be portable and not hardware dependent. DELIVERY OF THE SYSTEM: The project should be completed within a period of one month.

REQUIREMENT SPECIFICATION

REQUIREMENT SPECIFICATION
HOSPITAL MANAGEMENT
REGISTRATION: Register the patient. Provide the facility for adding new patient details and modify the record or print the record if necessary.
1.

FACILITIES: Services provided by the hospital to the patient. Doctors Codification: The details of the doctor dealing with the patient. Beds Codification: Information about the room type, bed type and charges.
2.

3. MEDICAL RECORDS: Diagnosis: The disease which the patient is suffering from is diagnosed. Treatment: It deals with the treatment done by the doctor for a particular patient.
9

4. RECORD:

Admission Discharge record Charges / Bills : Visiting fees Diagnosis charges Treatment charges Miscellaneous charges

FLOWCHARTS
1. 2. 3. 4. 5. PATIENT REGISTRATION BEDS CODIFICATION DOCTORS CODIFICATION DIAGNOSIS AND TREATMENT MISCELLANEOUS CHARGES

10

11

PATIENT REGISTRATION
START

REGISTER THE PATIENT

ENTER PATIENT DETAIL

ENTER ROOM NO

NO

IS ROOM EMPTY E YES

ASSIGN DOCTOR

STOP

12

BEDS CODIFICATION
START

ENTER CODE

MODIFY THE RECORD

INSERT ROOM TYPE, BED TYPE AND CHARGES

PRINT THE RECORD

GENERATE THE BILL

SEARCH THE RECORD

STOP

13

DOCTORS CODIFICATION
START

ENTER CODE

MODIFY THE RECORD

INSERT DOCTORS DETAILS AND VISIT CHARGES TYPE, BED TYPE AND CHARGES

PRINT THE RECORD

GENERATE THE BILL

SEARCH THE RECORD

STOP

14

DIAGNOSIS AND TREATMENT

START

ENTER CODE

MODIFY THE RECORD

INSERT TREATMENT DETAILS AND CHARGES HARGES

PRINT THE RECORD

GENERATE THE BILL

SEARCH THE RECORD

STOP

15

MISCELLANEOUS CHARGES
START

ENTER CODE

MODIFY THE RECORD

INSERT MISCELLANEOUS ITEMS AND THEIR CHARGES HARGES

PRINT THE RECORD

GENERATE THE BILL

SEARCH THE RECORD

STOP

16

ANALYSIS MODELING
1. ERD 2. DFD 3. DATA DICTIONARY

17

ENTITY RELATIONSHIP DIAGRAM

18

Bill Reciept no. A.C. & Heater Canteen

All Charge s

Date Amount

Final Bill

Facilities available

Patient Name

Patient ID

Avail facilities

Patient

Diagnosis, Treatmen t

Registere d

Doctor

Room No. Room Room type

Doctor ID

Doctor name

Entity Relationship Diagram (ERD)

19

DATA FLOW DIAGRAM

20

Patient

Healthy Person

Gets admitted

discharged HOSPITAL MANAGEMENT

LEVEL - 0 Data Flow Diagram (DFD)

21

PATIENT
Gets admitted

DISCHARGED

REGISTER

BILL PAID

TREATMENT

LEVEL 1 Data Flow Diagram (DFD)

22

Total Bill Paid

Discharged

Patient
Bills Generated Diagnosis & Treatment

Allot room if empty

rooms Codification Diagnosis & Treatment

Patient Registration Assign Doctor Doctors Codification

LEVEL - 2 Data Flow Diagram (DFD)

23

DATA DICTIONARY

24

TABLE 1 :
NAME : PURPOSE :
patientreg It stores the details of the patient.

STRUCTURE :
FIELD NAME pc pn age sex bg addp phno. doa toa rn bn reln addr dc dn refby DATA TYPE Number Text Number Text Text Text Number Text Text Number Number Text Text Number Text Text DESCRIPTION Patient code Patient name Patient Age Patient sex Patient blood group Patient address Patient phone no. Date of admission Time of admission Room no. Bed no. Relative name Relative address Doctor code Doctor name Referred by

25

TABLE 2:
NAME : diagnosis and treatment PURPOSE : It stores the investigations , diagnosis and surgery
related to particular patient . charges

STRUCTURE:
FIELD NAME Pc Inv Surch Theach Delich Pedch DATA TYPE Number Text Number Number Number Number DESCRIPTION Patient code Investigation Surgery charges Theatre charges Delivery charges Pediatrician charges

26

TABLE 3:
NAME : doctor codification PURPOSE : It stores the details of the doctor dealing with a particular
patient .

STRUCTURE:
FIELD NAME Pc Spec Phno Vch Vdt Vech DATA TYPE Number Text Number Number Text Number DESCRIPTION Patient code Doctor specialization Doctor phone no Visit charges Visit date Emergency visit charges

27

TABLE 4 :
NAME : miscellaneous charges. PURPOSE : It stores the miscellaneous items and their charges. STRUCTURE:
FIELD NAME Pc Acch Rhch Interch Cantch DATA TYPE Number Number Number Number Number DESCRIPTION Patient code AC charges Room heater charges Intercom charge Canteen charges

28

TEST PLAN

29

TEST PLAN
Why we need testing in any project?
As without get tested a project by a third party one cannot determine the various errors that may be there in the project or may come in future , that gradually becomes defects while implementing the project. So, to make an efficient project it should be properly tested.

UNIT TESTING is one of the white-box oriented testing. Unit

testing focuses verification efforts on the smallest unit of software design- the software component and module. As in this project various modules are: Patient registration module, doctors codification module , generating charges modules , providing facilities module and so on .So, various modules are independently tested here to ensure that information properly flow into and out of the various modules

INTEGRATION TESTING
Integration testing is a technique to uncover errors associated with interfacing. The objective is to take unit testing components and build a program structure. Here interfaces can be between patient and doctor , between patient and facilities between patient and charges, between patient and rooms and so on. Therefore these interfaces are properly tested.

SYSTEM TESTING
Software in incorporated with other system elements(such as people, information , hardware) thus a series of system integration and validation tests are conducted. It is actually a series of different test whose primary purpose is to fully exercise the computer based system.
30

FUTURE ENHANCEMENTS

31

FUTURE ENCHANCEMENTS
At a later point of time we plan to enhance our software. The following points would be given emphasis on : 1) The facility of Blood-bank would be provided. Various plans to organize blood donation camps would also be implemented. 2) The facility of payments of bills by credit cards also be provided. 3) The facilities such as speech therapy , physiotherapy , acupressure would also be provided.

32

BIBLIOGRAPHY
1. SOFTWARE ENGINEERING A Practitioners Approach - By ROGER S. PRESSMAN 2. SOFTWARE ENGINEERING - By PANKAJ JALOTE 3. AN APPROACH TO SOFTWARE ENGINEERING - By K.K.KHANNA

33

SUGGESTIONS

34