HOSPITAL MANAGEMENT SYSTEM | 194549115

Project Synopsis
on

Hospital
Submitted to the School of Computer and
Information Sciences, IGNOU
In partial fulfillment of the requirements
For the award of the degree
Bachelor of Computer Applications (BCA)
Submitted By:
Name :- Akash kumar
Enrollment No: - 194549115
Study Centre Code: - 07162P

Indira Gandhi National Open University

MaidanGarhi

1
HOSPITAL MANAGEMENT SYSTEM | 194549115

New Delhi – 1100681

Hospital
Management
System

2
HOSPITAL MANAGEMENT SYSTEM | 194549115

Table of contents
S. Contents Page
No no

1 Title of Project 4

2 Introduction 4

3 Objectives 7

4 Project Category 9

5 Analysis 10-17

5.1 DFD

5.2 ER-Diagram

6 Complete Structure 18-28

6.1 Number of modules and description of module

6.2 List of tables.

6.3 process logic

7 Tools , Platform, hardware and software requirements 29-35

8 Are you doing the project for industry or organization..?? 36

9 Future scope and further enhancements 37

10 Reference 38

3
HOSPITAL MANAGEMENT SYSTEM | 194549115

1. Title of Project

HOSPITAL MANAGEMENT
SYSTEM
2. Introduction
 The software is for the automation of the automation of hospital
management.
 It maintains two levels of clerk, Manager level.
 It can be used in any hospital, clinic or dispensary for maintain
patient details and their result.
 The details given the doctor staff and patient details include
doctor’s appointment and the billing system.
 Maintain patient details providing presentation and health advice

Providing and maintain all kinds, billing and report generate.

 The hospital management system has been developed to override

the problems prevailing in the practicing manual system.
 This software is supported to eliminate and in some cases reduces
the hard ships faced by this existing system.
 The application is reduced as much as possible to avoid error while
entering the data.
 It also provides error message while entering invalid data. No
formal knowledge is needed for the user to use this No formal
knowledge is needed for the user to use this system. Thus by this
all it proves it is user friendly. It can assist the user to concentrate
on their other activities on the record keeping. Thus it will help
organization in better utilization of resources.
 Every organization , where big small has challenges to overcome
and managing the information of doctor, employee

4
HOSPITAL MANAGEMENT SYSTEM | 194549115

medicine ,test every hospital management system has different

hospital needs , therefore we design exclusive employee
management system that are adapted to your managerial
requirement.
 The purpose of hospital management system is automating the
existing manual system by the help of computerized equipment’s
and full fledges.
 Computer software fulfilling their requirement .So that their
valuable data/information by stored for longer period with easy
accessing and manipulation of the same .The required software and
hardware are easily available and easy to work with.
 It can assist the user contraction their other activates rater to
contraction on the record keeping .the organization can maintain
computerized record without redundant entries so that their
valuable data /information can be stored for a longer period with
easy accessing and manipulation of the same basically the
project describes how to manager for good performance and
better services for the clients.

User Domains
a) Clerk
b) Manager
c) Doctor
d) Patient

A clerk is able to:-

 Patient details and register.
 Resource allocation.
 Pharmaceutics management.
 Billing and payment.

5
HOSPITAL MANAGEMENT SYSTEM | 194549115

 User interface conforming to usability guideline.

 Patient admits date and discharge date.
 Forget password.
 View feedback.
 View, book to appointment.
 Revenue information.
 Hospital database update.

An Admin is able to:-

 Patient register.
 Made a appointment schedule.
 Billing and payment.
 Staff management work roster, availability, schedules, etc.
 Management function report generation, according to hospital.
 Recourse allocation booking room ac/non ac operating, theatres, etc.
 Update patient details.
 Update doctor details.
 Provide confirmation of booking to the users.
 Hospital revenue information.
 Change the password.
 View feedback.

A doctor is able to:-

 Check patient report.
Check profile.
 Updates profiles
 View feedback
 View book appointment.
 Treat the patient.

A patient isable:-
6
HOSPITAL MANAGEMENT SYSTEM | 194549115

 Book appointment.
 Give a feedback.

3. Objectives:-
The aim of this project is to develop a database with the following objectives:-
 Admission:-Patients admit in hospital.

 Patient details:- Patient bio data.

 Doctor: Doctor details appointment.

 Improve patient care and record management

 Streamline operations and improve administrative and control

functions

 Facilitate pro-active monitoring of quality health service indicators

 Provide an integrated state-level holistic view of resource utilization

The main objective of the hospital management system is to manage the details of
hospital doctor, patient, employee; test .It manages at the information about
hospital, medicine test hospital.

4. Functionalities provided by hospital:-

 Searching facilities based on various factors .such as hospital patient
employee, test.
 Hospital management system also manages the medicine details online
for employee details, test details, hospital.
 It track all the information of doctor medicine, employee etc.
 Manage the information of doctor.
 Show the information and description of the hospital, patient.
 Increase efficiency of managing the hospital, doctor.
 It deals with monitoring the information and transaction of employee.
 Manage the info of hospital

7
HOSPITAL MANAGEMENT SYSTEM | 194549115

 Edit adding and updating of record is improved which result in process

resource management of hospital doctor
 Mange the information of employee.

5. Report of hospital:-
 It generates the report on hospital, doctor’smedicine.
 Provide filter report on patient, employee, and test.
 You can easily employee. Export pdf for the hospital, medicine ,
 Application also provides excel export of or doctor, patient, test.

6. Input data and validation of hospital:-

 All the felids such as hospital, patient, test are validation and does not
takes invalid values.
 Each from for hospital, doctors, medicine cannot accept blank value
fields.
 Modification done for the error found during testing.
 Testing the modules with all the possible test data.
 Test of functionally invalid all type of calculation etc.

7. Hospital requirements:-
 System needs store information about new entry of hospital.
 System needs to help the internal staff to keep information of doctors and
find then as various quires.
 System need to maintain quantity record.
 System need to keep the record of patient.
 System need to update and delete the record.
 System also needs a search area.
 It also needs a security system to prevent data.
8. Feasibility study:-
Feasibility study includes consideration of all the possible ways to provide
a solution to given problem the proposed solution should satisfy the entire
user requirement and should .Be easily done based on the future upcoming
requirement.
9. Features of the hospital:-
 Product and component based.
 Creating & changing issue of ease.
 Reporting &charting in more comprehensive way.
8
HOSPITAL MANAGEMENT SYSTEM | 194549115

 Query issue list to any depth.

 User accounts to control the access and maintains security
 Simple status & resolution.
 Multi-level priorities &severities.
 Targets & milestones for guiding the programmers.
 Robust database back-end.
 It contains better storage capacity.
 Various a lot of reports available with a lot of filter criteria’s.

10. Project Category:-relational database management system (RDBMS)

this is an RDBMS based project which is currently using derby all the transaction
statement .derby is an open source RDBMS system.
Introduction about RDBMS DBMS:-
A relational database management system (RDBMS) is a database
management system (DBMS) that is based on the relational model as invented by
E.F adds of IBMS research laboratory. Many popular databases currently in use are
RDBMS have become a predominant choice for the storage of information in new
database used for financial records manufacturing and, logistical information.
Personal data and much more since the relational database have often replaced
ligancy hierarchical database easier to understand and use. However relational
database have been challenged by object data base which were introduction in an
attempt to impendence mismatch in relational database and xml database.

9
HOSPITAL MANAGEMENT SYSTEM | 194549115

5.Analysis
DFD (Data Flow Diagram)
A Data Flow Diagram (DFD) is a graphical representation of the "DFD (Data Flow
Diagram flow" of data through an information system, modeling its process
aspects. Often, they are a preliminary step used to create an overview of the system
which can later be elaborated. DFDs can also be used for the visualization of data
processing (structured design). A DFD shows what kinds of information will be
input to and Output from the system, where the data will come from and go to, and
where the data will be stored. It does not show information about the timing of
processes, or information about whether processes will operate in sequence or in
parallel.

10
HOSPITAL MANAGEMENT SYSTEM | 194549115

Level 0

11
HOSPITAL MANAGEMENT SYSTEM | 194549115

Level 1 DFD

12
HOSPITAL MANAGEMENT SYSTEM | 194549115

2ndlevel

13
HOSPITAL MANAGEMENT SYSTEM | 194549115

14
HOSPITAL MANAGEMENT SYSTEM | 194549115

ER Diagram

15
HOSPITAL MANAGEMENT SYSTEM | 194549115

The Entity-Relationship model is a data model for high-level descriptions of

conceptual data models, and it provides a graphical notation for representing such
data models in the form of entity-relationship diagrams. Such data models are
typically used in the first stage of information-system design; they are used, for
example, to describe information needs and/or the type of information that is to be
stored in the database during the requirements analysis.

Basic elements in ER models:

Entities

A data entity is anything real or abstract about which we want to store the data.
Entity type falls into five classes: roles, events, location, tangible things or
concepts.

Attributes

A data attribute is a characteristic common to all or most instances of a particular

entity. An attribute or combination of attributes that uniquely identifies one & only
one instance of an entity is called primary key or identifier.

Relationships

Relationship provides the structure needed to draw information from multiple

entities. It is a natural association that exists between one or more entities.

Cardinality

16
HOSPITAL MANAGEMENT SYSTEM | 194549115

Cardinality defines the number of occurrences of one entity for a single occurrence
of related entity. Cardinality can be 1 to 1, 1 to many or vice versa and many to
many.

17
HOSPITAL MANAGEMENT SYSTEM | 194549115

 Module description

LOGIN MODULE

This Module manages the login functionality of the project when anyone
want to login inside the system, the system authenticate the person
through user id ,admin id and password. With the help of login module user
or admin can login and get home or main page where user and admin can
perform many types of task on books ,notes , schedule , various type of
practice , performance , group and notifications.

 SIGN UP MODULE

With the help of signup module new user can create new account for
them. New user can create new account with the help of new user id and
password, these user id and password help them to login

 FORGET PASS MODULE

With the help of Forget pass module user or admin can create new
password. If user or admin forgot his or her password in that condition s/he
can use this module to get a new password. To create new password with
the help of forget pass user have to provide many information to the forget
pass module as like user or admin name , g mail , phone number , address ,
any old password etc.

18
HOSPITAL MANAGEMENT SYSTEM | 194549115

 FEEDBACK MODULE

in feedback module can see his/her performance report of text that s/he
has performed. User can report of objective ,user take id password can
login the side and the than he\she performance of hospital manegment.

 Admin can view the feedback .

 NOTIFICATION MODULE

With the help of notification module user can see some important
information related to exam , subject , text etc. Suppose if any important
test is going to happen then with the help of notification module users will
be able to know about that test. User can also see some important
notification about final paper and date of final paper etc.

Admin is responsible to add, modify and delete the information of

notification module. Admin is responsible to add, modify and delete the
information about final paper.

19
HOSPITAL MANAGEMENT SYSTEM | 194549115

 CHANGE PASS MODULE

With the help of change password module user can create new password
for him/her. Users have to provide current password to generate new
secure password. User can change password for the security purpose.

Admin also can change password for the security purpose.

Admin also have to provide current password to generate new password.

 Search paitent
In which a user can search patient take the patient
id ,name,flowerand than search the paitent .
Clerk search the patient and ask the query.

 ADD DOCTOR
The admin can add doctor take the doctor name,gender,age,specialist and
then the add doctor
This module are show the add doctor And pefromance show the doctor

 Bill module
This module work for generate the bill many patient .the take the medicine
prise and lab fee.
Hospital charge and the generate the bill with bill id and will time.

 Add staff
This moduls are work for add staff take staff name,age,Id,gender,and some
Details and them add them.
This modul are olnyprformed by clerk and maneger,thise are update,delet,
Are prformed.

20
HOSPITAL MANAGEMENT SYSTEM | 194549115

 View appointment
User book appointment take patient name,age,addr,gender
And whatsaproblem for book appointment and who attender with
patint .
Clerk view the appointement and fix time and date.

List of Tables:
1. User_Login Table

Description: Contains the information of the users.

Attribute Type
Examples of values

User name Varchar(30) Harshita

User type Varchar(30) XYZ

User id Varchar(50) xyz@gmail.com

Password Varchar(30) Abc123

User ID varchar (50)

Primary Key
NULL
Foreign Keys
CREATE TABLE User Login(Name varchar(30),email
id varchar(50) primary key);

21
HOSPITAL MANAGEMENT SYSTEM | 194549115

2. Employe table

Attribute Type
Examples of
values
Employe_name Varchar(30) Pushpak

E_id Varchar(50) Abcd

E-contact Varchar(50) 764431298554

E_gender Varchar(50) Male

E _age Varchar(100) 22

E_salary Varchar(30) 20000

E_idvarchar(30)
Primary Key
NULL
Foreign Keys

SQL Code
CREATE TABLE
Employee(E_idvarchar(50) primary
key, E name varchar(50), Contact
varchar(15),age varchar (10) salary
varchar(30));

22
HOSPITAL MANAGEMENT SYSTEM | 194549115

3.Doctor Table

Description: Contains the information about doctor.

Attribute Type
Examples of values
D_Name varchar(50) Mani

D_specialist Varchar(50) physician

Contacts Varchar(50) 123

email- Varchar(50) 123

D-id
Primary Key
NULL
Foreign Keys
CREATE TABLE doctor(name
SQL Code
varchar(30),contactvarchar(50),email_idvarchar(50)
D_idvarchar(5));

23
 HOSPITAL MANAGEMENT SYSTEM | 194549115

4.Book Appointment Table

Description: Stores the payment information.
Attribute Type
Examples of values
patient_Name varchar(30) Mani

doctor_Name varchar(30) Dr.uni

Date/time varchar(50) 23/11/2017 1:13 am.

D_id Varchar(30)

D_id
Primary Key
D_id
Foreign Keys
CREATE TABLE Query(patient name
SQL Code
varchar(30), doctor-name varchar(50),date _time
varchar(100) primary key(d_id) forgein
key(d_id)refrence doctor(d_id));

5. Patient table
24
HOSPITAL MANAGEMENT SYSTEM | 194549115

Attribute Type
Examples of value
Name varchar(30) Mani

Id varchar(30) 1001

Gender varchar(30) female

Id_type Varchar(30) xyz

Attnder Varchar(30) brother

Address varchar(30) delhi

Primary key P_id prof

Foreigen key NULL

CREATE TABLE
SQL Code
Query(patient_namevarchar(30),gender
varchar(50),id_typevarchar(100) attender
varchar(30) primary key(p_id),foregion
key null());

6 Bill table

25
HOSPITAL MANAGEMENT SYSTEM | 194549115

Medicine varchar(30) Combiflam,thyroxine

name

medicine prize varchar(30) 250

Date/time varchar(30) 23/11/2017 2:30am.

Total amount varchar(30) 5000

Bill id Varchar()30 1234

Primary key Bill id

Foreigen key P_id

CREATE TABLE Query(patient name

SQL Code
varchar(30),Medicin price
varchar(50),bill price varchar(100)
primary key bill id,foreigen key (p_id)
(reference patient(p_id) , total amnt(30)
bill_id(30));+

26
HOSPITAL MANAGEMENT SYSTEM | 194549115

27
HOSPITAL MANAGEMENT SYSTEM | 194549115

28
HOSPITAL MANAGEMENT SYSTEM | 194549115

TESTING PHASE

Software Testing is an empirical investigation conducted to provide stakeholders

with
information about the quality of the product or service under test, with respect to
the context
in which it is intended to operate. This includes, but is not limited to, the process of
executing
a program or application with the intent of finding software bugs. It can also be
stated as the
process of validating and verifying that a software program/application/product
meets the
business and technical requirements that guided its design and development, so
that it works
as expected and can be implemented with the same characteristics.
A primary purpose for testing is to detect software failures so that defects may be
uncovered and corrected. This is a non-trivial pursuit. Testing cannot establish that
a product

29
HOSPITAL MANAGEMENT SYSTEM | 194549115

functions properly under all conditions but can only establish that it does not
function
properly under specific conditions.[11] The scope of software testing often
includes
examination of code as well as execution of that code in various environments and
conditions
as well as examining the aspects of code: does it do what it is supposed to do and
do what it
needs to do. In the current culture of software development, a testing organization
may be
separate from the development team. There are various roles for testing team
members.
Information derived from software testing may be used to correct the process by
which
software is developed.
Defects and failures
Not all software defects are caused by coding errors. One common source of
expensive defects is caused by requirements gaps, e.g., unrecognized requirements,
that
result in errors of omission by the program designer. A common source of
requirements gaps
is non-functional requirements such as testability, scalability, maintainability,
usability,
performance, and security.
Software faults occur through the following process. A programmer makes an error
(mistake), which results in a defect (fault, bug) in the software source code. If this
defect is
executed, in certain situations the system will produce wrong results, causing a
failure.[12]
Not all defects will necessarily result in failures. For example, defects in dead code
will
never result in failures. A defect can turn into a failure when the environment is
changed.
Examples of these changes in environment include the software being run on a new
hardware
- 133 -
platform, alterations in source data or interacting with different software.[12] A
single defect
may result in a wide range of failure symptoms.
Compatibility
30
HOSPITAL MANAGEMENT SYSTEM | 194549115

A frequent cause of software failure is compatibility with another application, a

new
operating system, or, increasingly, web browser version. In the case of lack of
backward
compatibility, this can occur (for example...) because the programmers have only
considered
coding their programs for, or testing the software upon, "the latest version of" this-
or-that
operating system. The unintended consequence of this fact is that: their latest work
might not
be fully compatible with earlier mixtures of software/hardware, or it might not be
fully
compatible with another important operating system. In any case, these
differences, whatever
they might be, may have resulted in (unintended...) software failures, as witnessed
by some
significant population of computer users.
This could be considered a "prevention oriented strategy" that fits well with the
latest
testing phase suggested by Dave Gelperin and William C. Hetzel, as cited below
[13].
Input combinations and preconditions
A very fundamental problem with software testing is that testing under all
combinations of inputs and preconditions (initial state) is not feasible, even with a
simple
product. This means that the number of defects in a software product can be very
large and
defects that occur infrequently are difficult to find in testing. More significantly,
nonfunctional
dimensions of quality (how it is supposed to be versus what it is supposed to do) --
for example, usability, scalability, performance, compatibility, reliability -- can be
highly
subjective; something that constitutes sufficient value to one person may be
intolerable to
another.
Static vs. dynamic testing
There are many approaches to software testing. Reviews, walkthroughs or
inspections
are considered as static testing, whereas actually executing programmed code with
a given
31
HOSPITAL MANAGEMENT SYSTEM | 194549115

set of test cases is referred to as dynamic testing. The former can be, (and
unfortunately in
practice often is...) omitted, whereas the latter takes place when programs begin to
be used
for the first time - which is normally considered the beginning of the testing stage.
This may
actually begin before the program is 100% complete in order to test particular
sections of
- 134 -
code (modules or discrete functions). For example, Spreadsheet programs are, by
their very
nature, tested to a large extent "on the fly" during the build process as the result of
some
calculation or text manipulation is shown interactively immediately after each
formula is
entered
1. UNIT TESTING:
This is the smallest testable unit of a computer system and is normally tested using
the white box testing. The author of the programs usually carries out unit tests.
2. INTEGRATION TESTING:
In integration testing, the different units of the system are integrated together
to form the
complete system and this type of testing checks the system as whole to ensure
that it is doing
what is supposed to do. The testing of an integrated system can be carried out
top-down,
bottom-up, or big-bang. In this type of testing, some parts will be tested with
white box
testing and some with black box testing techniques. This type of testing plays
very important
role in increasing the systems productivity. We have checked our system by
using the
integration testing techniques.
3. SYSTEM TESTING:
A part from testing the system to validate the functionality of software against the
requirements, it is also necessary to test the non-functional aspect of the system.
Some
examples of non-functional tools include tests to check performance, data security,
usability/user friendliness, volume, load/stress that we have used in our project to
test the
32
HOSPITAL MANAGEMENT SYSTEM | 194549115

various modules.
System testing consists of the following steps:
1. Program(s) testing.
2. String testing.
3. System testing.
4. System documentation.
5. User acceptance testing.
- 135 -
4. FIELD TESTING:
This is a special type of testing that may be very important in some projects. Here
the system
is tested in the actual operational surroundings. The interfaces with other systems
and the real
world are checked. This type of testing is very rarely used. So far our project is
concerned;
we haven't tested our project using the field testing.
5. ACCEPTANCE TESTING:
After the developer has completed all rounds of testing and he is satisfied with the
system,
then the user takes over and re-tests the system from his point of view to judge
whether it is
acceptable according to some previously identified criteria. This is almost always a
tricky
situation in the project because of the inherent conflict between the developer and
the user. In
this project, it is the job of the bookstores to check the system that whether the
made system
fulfills the goals or not.
WHY SYSTEM TESTING?
Testing is vital to the success of the system. System testing makes a logical
assumption that
if all the parts of the system are correct, the goal will be successfully achieved.
Inadequate
testing results in two types of problems:
1. The time lag between the cause and the appearance of the problem.
2. The effect of system errors on the files and records within the system.
6.2 ACTIVITY NETWORK FOR SYSTEM TESTING
The test plan entails the following activities:
1. Prepare test plan.
2. Specify conditions for user acceptance testing.
33
HOSPITAL MANAGEMENT SYSTEM | 194549115

3. Prepare test data for program testing.

4. Prepare test data for transaction path testing.
5. Plan user training.
6. Compile/assemble programs.
7. Prepare job performance aids.
8. Prepare operational documents.
- 136 -
PREPARE TEST :A workable test plan must be prepared in accordance with
established design specifications. It includes the following items:
Outputs expected from the system.
Criteria for evaluating outputs.
A volume of test data.
Procedure for using test data.
Personnel and training requirements.
SPECIFY CONDITIONS FOR USER ACCEPTANCE TESTING
Planning for user acceptance testing calls for the analyst and the user to agree on
conditions
for the test.
PREPARE TEST DATA FOR PROGRAM TESTING
As each program is coded, test data are prepared and documented to ensure that all
aspects of
the program are properly tested.
PREPARE TEST DATA FOR TRANSACTION PATH TESTING
This activity develops the data required for testing every condition and transactions
to be
introduced into the system. The path of each transaction from origin to destination
is
carefully tested reliable results.
PLAN USER TRAINING
User training is designed to prepare the user for testing and converting the system.
User
involvement and training take place parallel with programming for three reasons:
• The system group has time available to spend on training while the
programs are
being written.
• Initiating a user-training program gives the systems group a clearer image of
the
user's interest in the new system.
• A trained user participates more effectively in system testing.

34
HOSPITAL MANAGEMENT SYSTEM | 194549115

The training plan is followed by preparation of the user training manual and other
text
materials.
- 137 -
COMPILE / ASSEMBLE PROGRAMS
All programs have to be compiled / assembled for testing.
PREPARE JOB PERFORMANCE AIDS
In this activity the materials to be used by personnel to run the system are specified
and
scheduled. This includes a display of materials.
PREPARE OPERATIONAL DOCUMENTS
During the test plan stage, all operational documents are finalized including copies
of the
operational formats required by the candidate system.
SYSTEMS TESTING
The computer department to ensure that the system functions as specified does this
testing.
This testing is important to ensure that a working system is handed over to the user
for
acceptance testing.
ACCEPTANCE TESTING
The user to ensure that the system functions, as the user actually wanted performs
this
testing. With prototyping techniques, this stage becomes very much a formality to
check the
accuracy and completeness of processing. The screen layouts and output should
already have
been tested during the prototyping phase.
An error in the program code can remain undetected indefinitely. To prevent this
from
happening the code was tested at various levels. To successfully test a system, each
condition, and combinations of conditions had to be tested. Each program was
tested and
linked to other programs. This unit of program is tested and linked to other units
and so on
until the complete system has been tested.
The purpose of testing is to ensure that each program is fully tested. To do so a test
plan had
to be created. The test plan consists of a number of test runs such as the valid paths
through
35
HOSPITAL MANAGEMENT SYSTEM | 194549115

the code, and the exception and error handling paths. For each test run there is a
list of
conditions tested, the test data used and the result expected. The test plan was then
reviewed
to check that each path through the code is tested correctly. It is the responsibility
of the
programmer to collect the data that will produce the required test condition.

9. REPORT GENERATION
Report are used to display Information from database as per requirement.
Report will be designed by using HTML tag and CSS tag. JSP will fetch
data from data tables and HTML,CSS will be used to format and design the
requested information on the web page. From above modules different
reports are generated. Reports
 Patient Reports: Gives customers details.
 Feedback Reports: Gives customer feedback details.
 File Details: Gives file details, Issued file handled by the employee.
 Employee Details: Give employee details.
 File Status: Status of all the files that a hospital is handling.
7. TOOLS, DATABASE, HARDWARE AND
SOFTWARE REQUIREMENTS:
7.1 Tool:Net Beans 8.0.2
7.2 Database:Derby
7.3 Hardware Requirements:
DEVELOPMENT TIME DEPLOYMENT TIME
 Monitor
 Processor – dual core
 RAM 1GB  Standard cabinet
 Back,end-derby configuration

36
HOSPITAL MANAGEMENT SYSTEM | 194549115

7.4
DEVELOPMENT TIME DEPLOYMENT TIME

 Netbeans 8.0.2  Any operating system

 Notepad  Browser
 Windows 7 or above
 Browser

8. Are you doing this project for industry or

organization..??

NO, we are not doing this project for any industry or any organization.
This project is developed for Academic purpose. .we make this project
under the guidance “ Arunesh Sir”,” Vijay Sir” Regarding this
internship, we had gain lots of knowledge about making website.
9. Future scope and further enhancement:

This website is designed to a stand-alone, single user system. It is proposed

to make the multiuser system.that a patient there family members would
not going to stand in queue for there entering data in hospital system.
They directly book there appointment and consult with referred doctor.

37
HOSPITAL MANAGEMENT SYSTEM | 194549115

10. References:

http://www.slideshare.net/ieeexploreprojects/academic-project
http://www.w3schools.com
http://www.draw.io
http://www.erdplus.com

38