HOSPITAL DEVICE MANAGEMENT SYSTEM

MINOR PROJECT REPORT Submitted by SATYA SHRIVASTAVA (0206CS091092) PRIYANSHI KHARE (0206CS091076) PRIYA SHRIVASTAVA (0206CS091071) RUCHIKA SINGH RAJPUT(0206CS091089) In partial fulfillment for the award of the degree Of

BACHELOR OF ENGINEERING
In

COMPUTER SCIENCE &ENGINEERING

DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING

GYAN GANGA INSTITUTE OF TECHNOLOGY & SCIENCES JABALPUR (M.P.)

RAJIV GANDHI PRODYOGIKI VISHWAVIDYALAYA, BHOPAL (M.P.) MAY - 2012

CERTIFICATE

This is to certify that the Minor Project Report entitled HOSPITAL submitted DEVICE by MANAGEMENT SYSTEM

Satya

shrivastava,priyanshi

khare,priya shrivastava,Ruchika singh rajput has been carried out under my guidance & supervision. The minor project report is approved for submission towards partial fulfillment of the requirement for the award of degree of BACHELOR OF ENGINEERING in COMPUTER SCIENCE & ENGINEERING from RAJIV GANDHI PROUDYOGIKI VISHWAVIDYALAYA,

BHOPAL (M.P).

Mr. Prashant Dutta Guide

Mr. Ashok Verma H.O.D

Dept. of Computer Science & Engg

Dept of Computer Science & Engg

CERTIFICATE

This is to certify that the Minor Project Report entitled HOSPITAL DEVICE MANAGEMENT SYSTEM submitted by Satya shrivastava,priyanshi singh rajput for khare,priya the partial

shrivastava,Ruchika

fulfillment of the requirement for the award of degree of BACHELOR OF ENGINEERING in COMPUTER SCIENCE & ENGINEERING from RAJIV GANDHI PROUDYOGIKI

VISHWAVIDYALAYA, BHOPAL (M.P).

Internal Examiner Date :

External Examiner Date :

DECLARATION

We hereby declare that the project synopsis entitled HOSPITAL DEVICE MANAGEMENT SYSTEM which is being submitted in partial fulfillment of the requirement for award of the Degree of Bachelor of Engineering in Computer Science and Engineering to RAJIV GANDHI PROUDYOGIKI VISHWAVIDYALAYA, BHOPAL (M.P.) is an authentic record of our own work done under the guidance of Computer Mr. Prashant & Dutta , Department of GYAN GANGA Science Engineering,

INSTITUTE OF TECHNOLOGY & SCIENCES, JABALPUR.. The matter has not been submitted earlier for the award of any other degree.

Dated : 27/04/12 Place: Jabalpur

Satya shrivastava Priyanshi khare Priya shrivastava Ruchika singh rajput

ACKNOWLEDGEMENT

We sincerely express indebtedness to esteemed and revered guide Mr.Prashant Dutta, assistant professor in Computer Science Department for his invaluable guidance, supervision and encouragement throughout the work. Without his kind patronage and guidance the synopsis would not have taken shape. We take this opportunity to express deep sense of gratitude to Mr. Ashok Verma, Head of Computer Science Department for his encouragement and kind approval. Also we thank him in providing the computer lab facility. We would like to express our sincere regards to him for advice and counseling from time to time. We owe sincere thanks to all the lecturers in Computer Science Department for their advice and counseling time to time.

Dated :

27/04/12

Satya shrivastava Priyanshi khare Priya shrivastava Ruchika singh rajput

Place: Jabalpur

Abstract

In current scenario TIME is very precious from every aspects of life, so time should be consumed efficiently. A very large part of time consumption is wasted in interacting with other. So the time for interaction should also be optimized to optimize overall time. The system is required for the people who are directly responsible for the allocation and monitoring of the devices. By keeping this in mind we developed our HOSPITAL DEVICE MANAGEMENT SYSTEM to reduce time consumption in interaction with peoples for the allocation of devices in the case of emergency. We made our project very easy and user friendly so that people with even basic knowledge of computer can understand its working.

Table of contents
1. List of tables 2. List of figures 3. Introduction 4. Motivation and objective 5. Scope of the project 6. Requirement analysis 6.1. Functional Requirements 6.2. Non-Functional Requirements 7. Overall design 7.1. ER Diagram 7.2. Use Case Diagram 7.3. Class Diagram 8. References

1.

List of Tables
1. Register table 2. Department table 3. Device table 4. Doctor_request table 5. Purchase table 6. Repair table

2.

List of Figures

1. Entity Relationship Diagram 2. Use Case Diagram 3. Class Diagram

3.

Introduction
The purpose of this document is to describe all the requirements for the Hospital device Management System (HDMS). These include, necessarily limited to, the following: administrators ,staff, doctors. The hospital device management and its team members should use this document and its revisions as the primary means to communicate confirmed requirements to the administrative team. The administrative team expects many face-to-face conversations that will undoubtedly be among the doctors and the staff. Please note that only the requirements that appear in this document or a future revision, however, will be used to define the scope of the system. The system is required for the people who are directly responsible for the allocation and monitoring of the devices.

MODEL USED:
Our project is based on INCREMENTAL MODEL.
Incremental model is an evolution of waterfall model. The product is designed, implemented, integrated and tested as a series of incremental builds. It is a popular model software evolution used many commercial software companies and system vendor. Incremental software development model may be applicable to projects where: Software Requirements are well defined, but realization may be delayed. The basic software functionality are required early

Advantages Generates working software quickly and early during the software life cycle. More flexible - less costly to change scope and requirements. Easier to test and debug during a smaller iteration. Easier to manage risk because risky pieces are identified and handled during its iteration. Disadvantages Each phase of an iteration is rigid and do not overlap each other. Problems may arise pertaining to system architecture because not all requirements are gathered up front for the entire software life cycle.

4. Motivation and Objectives

The main objective of this document is to illustrate the requirements of the project hospital and device management website. The document gives the detailed description of the both functional and non functional requirements proposed.The objective of this software is to provide easy assistance to the users of this software with proper database and information. Throughout the project the focus will be on presenting information and comments in an easy and intelligible manner.The project is very useful for locating the devices in a hospital if needed. The process made computerized to reduce human errors and to increase the efficiency.

5. Scope of the project

The proposed software product is the Hospital Device Management System (HDMS). The system will be used to assign device to doctors in designated wards as need arises. Staff can also use the system to keep track of the devices assigned to the doctors. The current system in use is a paper-based system. It is too slow and cannot provide updated lists of devices within a reasonable timeframe. The intentions of the system are to reduce over-time pay and increase the number of patients that can be treated accurately. Requirements statements in this document are both functional and non-functional.

6.
6.1.

Requirement analysis

FUNCTIONAL REQUIREMENTS

This project has the following functionalities: A Home page This is the page where the user will be navigated. It will display administrator info, head of departments info, eye bank info,holiday list, contact info, login, new register and about us. Admin This is the page where the user can view a note from the admin of the hospital which includes the contacting details too. Contact info This is the page where the user can contact us, can view the contact details . Hods This page includes the name of the heads of the deparments in the hospital. Eye bank This page will give the info about the eye donation facility provided by the hospital.

Holiday list The user can view the holiday related information. Managing user accounts User can login using login page and logout using the logout button. New reg The user who wants to register in the website can fill the sign up form.

6.2.

NON-FUNCTIONAL REQUIREMENTS

Simple and effective interface design appropriate for general users

Performance
Processes user requests (searching, browsing, ordering, etc.) immediately, or with only minimum acceptable delay Capable of dealing with large number of users simultaneously, with little or no degradation of performance

Security
Secure processing of user information

Flexibility
Our project should be so flexible that whenever we want to make changes in it very easily it can be done on. Hardware Requirements
Processor RAM Hard Disk Drive Key Board Monitor Display adapters Floppy Drive CD Drive NIC : Any new generation processor : Reasonable for the processor : More than 128 MB recommended : Standard Keyboard recommended : Any color monitor recommended : Super VGA : Not necessary : Not necessary : Required

Software Requirements
Operating System Front End Back End : Widows 98 and above : JAVA : Apache Derby Server

7. Overall Design
Database tables
Sample table listed below -

1.
Table Name
Description Primary Keys email Field Name Fname Mname Lname Email Password Mobile Designation

Newreg
Newreg
This table will contain the information of the user who wants to register for the first time in our website. email Data type Int(50) varchar(50) varchar(50) varchar(30) varchar(30) Varchar(50) varchar(50) Constraints NN NN NN PK NN NN NN

Table Name Description Primary Keys Field Name Department_name Department_head Contact_info

Department This table will contain the information of the department and their respective head details. Department_name Department_name Constraints varchar(50) PK varchar(50) varchar(20) NN NN

2.

Department

3.
Table Name Description

Device
Device This table will contain the information of the devices available in the hospital . Idn Data type Constraints varchar(50) NN numeric(10) PK varchar(100) NN Varchar(50) NN numeric(50) NN date(10) NN

Primary Keys Field Name Device_name Idn Description Department_name Cost Purchase_date

4.
Table Name Description

Doctor Request
Doctor_request This table will contain the information of the request send by the doctor to the staff . Idn Data type Constraints varchar(50) NN numeric(10) PK varchar(50) NN numeric(20) NN char(1) NN date(10) NN

Primary Keys Field Name Device_name Idn Doctor_name Ward_no status Purchase_date

5.

Purchase

Table Name Description Field Name Device_name Department_name

purchase This table will contain the information of the detail send by the staff to admin for purchasing the devices. Data type Constraints varchar(50) NN varchar(50) NN

6. Repair
Table Name Description Primary Keys Field Name Device_name Idn Department_name Feedback status Repair This table will contain the information of the damaged device detail send by the staff to admin . Idn Data type Constraints varchar(50) NN numeric(10) PK varchar(50) NN varchar(500) NN char(1) NN

7.1

ENTITY RELATIONSHIP DIAGRAM

id

pass

id

pass Mad e requ est handl ereq devices

id

pas s doctor

administrator

Exch ange info

Front-desk staff

repai r

bu y

reqr epair

reqb uy

componentdetail deptnam e dname

devicesinf o

deptna me devices

dnam e name devicepurchas feedback dname

ID N dept

be lo ng

idn DOE dnam e

dnam e

deptname deptna me reqtost aff deptname device dnam e

depname

departmenname

war d

7.2 Use Case Diagram

Handle the Device buying process Administer get request for buying the devices
admin

Inform back to the staff about repairing devices Change the database for purchasing the devices Allot the requested device to particular ward

Change the database for repair devices and alotted devices

staff

Give request to admin h about repairing the devices when they get back available Notify to doctor that device is allotted

Give request to admin about purchasing the devices

Give the request of the device to the staff

7.3

Class Diagram

c. Activity Diagram

d. Data Flow Diagram

Level-2 DFD

8. References
1. Database management system by Korth and Sudarshan 2. Software Engineering by Roger S.Pressman

1. http://www.agakhanhospitals.org/mumbai/services.asp 2. http://gmchassam.gov.in/index.html 3. http://www.wikipedia.org/ 4. http://www.fortishealthcare.com/