HOSPITAL MANAGEMENT

PREPARED BY: -Dodiya Twinkle G.

B.C.A-6th sem
Guided By:-Pradip vanpariya
Keyur zala
M. & N. Virani Science College
 INDEX

NUM DESCRIPTION PAGE NUM

1 Acknowledgement 3
2. Introduction to project 4
 Project profile 5
 Abstract 6
 Project Summary 7
3. System Analysis & Requirement 8
 Software Requirement 10
 Hardware Requirement 11
 Analysis 14
4. Tools & Technology 20
 ASP.NET 22
 MS SQL 2005 23
 Microsoft Visual Studio 2008 24
5. Project Risk 26
6. User Requirements 27
7. System Design 28
 Database 29
 Data Flow Diagram 34
8. Screen Layout 36
9. Software Testing 46
10. Appendix 51
 Limitations of Project 52
 Future Application of Project 53
 Bibliography 54

2
 ACKNOWLEDGEMENT

This project requires a lot of people support to complete this project. We take
this opportunity to acknowledge their support to me.

My Deepest thanks to our Trainers Mr. Pradip vanpariya and Mr. Keyur Zala
for guiding and correcting various documents of my project with attention and
care. They have taken pain to go through the project and make necessary
correction as when needed. They express their gratitude for guidance and who
kept the things on track. Their helpful solutions and comers enriched by his
experience for the betterment of the project and also to all other faculty
members who helped us directly or indirectly.

Last but not list, we would like to thank our department and all faculty
members. We also extend our heartfelt thanks to friends and my parents and my
sister who helped me directly throughout the project duration and have been the
source of encouragement.

Finally we would like to thank everyone who directly or indirectly helped us in

this project.

3
INTRODUCTION TO PROJECT

4
 PROJECT PROFILE

Developed on : HOSPITAL MANEGEMENT SYSTEM

Developed by : Twinkle Dodiya

Developed at : Shree M & N. Virani Science College, Rajkot

Operating System : Window XP & Higher version

Web Server : SQL Server

Web Browser : Internet Explorer / Mozilla Firefox

Tools : Microsoft visual Studio

ASP.NET

C#

Database : My SQL

Guided by : Mr. Pradip vanpariya

Mr. Keyur zala

Submitted to : Saurashtra University

Year : 2011-12

5
 ABSTRACT
The present system is desktop base application. My proposed system is totally
web based application by which hospital can manage and all the records
maintain in database.

I am developing a website for Hospitals using Asp.Net. This application enables

the users to register and book an appointment online. The information about
each and every user who has registered and is kept for future use and even the
medical history of the user can be viewed. This system covers all the
functionality and services provided by the hospital so it is useful to manage the
hospital. The website is for the automation of hospital management. Doctor can
check the patient report from anywhere. The external patient can see what is the
facility provided by hospital and what is the charges and doctor‟s schedule.

6
 PROJECT SUMMARY

This web site is “Hospital Management System”, This system covers the all the
functionality and services provided by the hospital so ,It is useful to manage the
hospital. Doctor can check the status of patient online, the patient can check
their status like what is his blood report?, urine report etc.

The website is for the automation of hospital management. It maintains two

levels of users administrator level and patient level. The website includes
maintaining patient details, providing health instruction and maintaining all
kinds of tests for a patient like billing and report generation.

The scope of this website is it can be used in any clinic, hospital, dispensary or
pathology labs for maintaining patient details and their test results.

7
SYSTEM ANALYSIS &
REQUIREMENT

8
 SYSTEM REQUIREMENT
SPECIFICATION

Before designing an information system it is essential to understand the user‟s

requirements. So, to understand the user‟s requirements correctly, it is necessary
to prepare a document that effectively specifies user‟s requirements.

Types of Requirements:

 Non-Functional Requirement
 Functional Requirement

9
NON FUNCTIONAL REQUIREMENT

SOFTWARE REQUIREMENT

Client on Intranet

 Operating System (Windows 2000, XP, Vista )

 Web browser (Internet Explorer, Mozilla Firefox)

Database Server

 MS SQL Server 2005

Development End

 HTML, JavaScript, CSS

 ASP.NET(C#)

Tools

 Visual Studio 2008/2010

10
HARDWARE REQUIREMENT

Internet Explorer 6.0 /Mozilla Firefox / Or any Browser that supports Applet.

Server Side SQL server

11
 FUNCTIONAL REQUIREMENT

Maintainability

The malignance of the project should be easy and the cost required for the
project maintenance must be low. The design patterns used are very adaptive, so
that if any change required in system, it will be very easy.

Security

We are using .Net Framework 3.5 and C#.Net as the front end which provides
more security. The user wants that the data stored in the database must be
secure and can‟t get by unauthorized user which can damage the system. After
login only you can access system, so if you don‟t have your username or
password, you are not able to use system.

Usability

The interface should use terms and concepts, which are drawn from the
experience of the people who will make most of the system.

Accuracy

The user should require that data are getting from database and stored in the
database must be accurate. The data entered by user are verified by validation
controls.

12
Interface Issue

The system must provide easy and fast access without consuming more cost.
The system must also be user- friendly so that user can easily access the system.

Constraints

User should never be surprised by the behaviour of the system and it should also
provide meaningful feedback when errors occur so that user can recover from
the errors.

Readability

The user among the project must be able to proceed further easily and without
facing any problem.

Modularity

The project must be built up in modules so things are not missed up and
complexity reduces. So it‟s easier to find out errors in modules.

Portability

The project should be run on any system satisfying hardware and software
requirements successfully without making more changes.

Traceability

The system should be such that each module can be traced from any module.

13
 ANALYSIS

INFORMATION GATHERING

The first step was to understand the Structure of the system. The next most
important step was to understand the Business Logic of the respective modules
of the system. After studying the system it was the time for gathering
requirements and information about the system. The information was collected
and consolidated by conducting a series of interviews with the Project Manager.
This was supplemented with collection of documents that form the part of the
present physical system. Simultaneously, a study of the Development tools was
carried out.

The requirements were documented and depending on these, the prototype of

the system was designed and documented to form the requirement catalogue.
This catalogue was put forward before the Project Manager. Then after detailed
data dictionary was designed. Most of the requirements and design of the
database were given by the Project Manager, then also while implementing the
system some design issues regarding database were encountered that we were
solved by discussion with the Project

14
FEASIBILITY ANALYSIS

Feasibility is the measure of how beneficial or practical the development of

information system will be to an organization. Feasibility analysis is a process
by which feasibility is measured. In today‟s fast going technical environment it
is impressive for any organization-be it corporate or government one-to use the
power of information technology. The benefits of computerization will not only
make the process flow simple but also uplift standards of manpower working in
an organization and increase efficiency and productivity.

It is very important to do preliminary investigation regarding the development

of the system; the likelihood the system will be useful for the organization. Thus
before implementing the project, it is necessary to test the feasibility of the
project. As an outcome of feasibility analysis phase, the feasibility of the system
is determined.

There are three types of feasibility.

 Economic feasibility
 Technical feasibility
 Operational feasibility
 Implementation Feasibility

15
ECONOMIC FEASIBILITY

 Cost-Benefit analysis is to be done to determine the overall cost &

benefits against the cost.

 SPARK Hospitals site uses all the free technologies to implement and
does not require a high-end PC to function successfully at client side.

 We being the trainees in the organization, we develop the application free

of cost. The site does not require any license to use in future.

 The plug-ins required at client-side is freely available on the Internet.

16
TECHNICAL FEASIBILITY

 ‘Connectivity Database Management System’ application in practically

possible to implement.
 The system is to be developed using familiar software and hardware
environments/tools (Visual Studio 2008/2010, MS SQL Server 2005)
with the advent technology.
 The required technology is available „in-house‟.
 High speed processors in GHz, Infrastructures available system become
more feasible.

17
OPERATIONAL FEASIBILITY

 Performance:- This application allows you to connect to the Hospital

website and book an appointment and have a chat with Doctor in case of
instant medication or when you cannot meet Doctor due to some reasons.

 Information:- This site allows you to register and book an appointment with
a Doctor. It even allows you chat with Doctor.

 Economy:- Instantaneous actions can save lot of time as well as information

is presented in digital form so can reduce the cost of stationary items of
information archive.

 Control:- Authentication based access to the system. Prevents also from

SQL Injection attacks. Information is available only to the authorized users
of the system.

 Efficiency:- All the available resources can be utilized at maximum.

 Services:- All the facilities provided by website are reliable and the system
can be expandable for future enhancements.

18
IMPLEMENTATION FEASIBILITY

 The organization provides us well-configured system with all the tools

and technology required to develop the website.

19
 Tools
and
Technology

20
 TOOLS SPECIFICATION

There are many tools required for the preparation of this website. A developer
no matter, how skilled is dependent on the tools and technology at his disposal.
There are numerous free tools to aid in .net development; from source control to
debugging and from documentation to profiling. I have used following software
whose brief introduction is given below:

 ASP.NET
 Ms SQL Server
 Microsoft visual studio

21
 ASP.NET
 ASP.NET is a free technology that allows anyone to create a modern web
site.
 ASP.NET is a powerful platform for developing software.
 ASP.NET is a web application framework developed and marketed by
Microsoft to allow programmers to build dynamic web-sites, web-
application and web-services.
 It was first released in January 2002 with version 1.0 of the .Net
Framework and is the successor to Microsoft's Active Server Pages
(ASP) technology.
 Framework 3.5 is released in November 19; 2007.It is released with
Visual Studio 2010 and Windows Server 2008.
 .NET Framework 3.5 supports WCF, WPF, LINQ and WORKFLOW.

22
 MS SQL SERVER 2005
 Microsoft SQL Server is a relational model database server produced by
Microsoft.
 Its primary query languages are T-SQL and ANSI SQL.
 SQL Server 2005 (codenamed Yukon), released in October 2005, is the
successor to SQL Server 2000.
 It included native support for managing XML data, in addition to
relational data.
 It allows DML and DDL functionality.
 SQL Server is a relational database management system (RDBMS)
from Microsoft that's designed for the enterprise environment. SQL
Server runs on T-SQL (Transact -SQL), a set of programming extensions
from Sybase and Microsoft that add several features to standard SQL,
including transaction control, exception and error handling, row
processing, and declared variables.

 Code named Yukon in development, SQL Server 2005 was released in

November 2005. The 2005 product is said to provide enhanced
flexibility, scalability, reliability, and security to database applications,
and to make them easier to create and deploy, thus reducing the
complexity and tedium involved in database management. SQL Server
2005 also includes more administrative support.

23
 MICROSOFT VISUAL STUDIO
Ms Visual Studio is one of the very powerful IDE Integrated development
environment from Microsoft. It supports many language, integrated web-server,
code completion, refectory tools, debugger etc.

Microsoft Visio is a diagramming program for Microsoft Windows that uses

vector graphics to create diagrams. Microsoft Office 2008 makes it easy and
business professionals to visualize, explore, and communicate complex
information. It is used to develop console and graphical user interface
applications along with Windows Forms applications, web sites, web
applications, and web services in both native code together with managed for all
platforms supported by Microsoft Windows, Windows Mobile, Windows
CE, .NET Framework, Framework and Microsoft Silver light.

Visual Studio includes a code editor supporting IntelliSense as well as code

refactoring. The integrated debugger works both as a source-level debugger and
a machine-level debugger. Other built-in tools include a forms designer for
building GUI applications, web designer, class designer, and database
schema designer. It accepts plug-ins that enhance the functionality at almost
every level including adding support for source systems
(like Subversion and Visual SourceSafe) and adding new toolsets like editors
and visual designers for domain-specific languages or toolsets for other aspects
of the software development lifecycle (like the Team Foundation Server client:
Team Explorer).

24
Visual Studio supports different programming languages by means of language
services, which allow the code editor and debugger to support (to varying
degrees) nearly any programming language, provided a language-specific
service exists. Built-in languages include C/C++, VB.NET , C# , and F#.
Support for other languages such as Python, and Ruby among others is available
via language services installed separately.

It also supports XML/XSLT, HTML/XHTML, JavaScript and CSS. Individual

language-specific versions of Visual Studio also exist which provide more
limited language services to the user: Microsoft Visual Basic, Visual J#, Visual
C#, and Visual C++.

25
 PROJECT RISK
Risk Management is due to creating a project and having coding mistake, if put
any query in other place than it create distinguish mistakes in project.

Risk is the factor that make a project having more efficiency and more reliable
for use that kind of project.

Risk analysis and management are a series of steps that help a software team to
understand and manage uncertainty. But, regardless of the outcome, it's a really
good idea to identify it, assess its probability of occurrence, and estimate its
impact.

Risk management aims at dealing with all kinds of risks that might affect a
project. Having many types of risk, but here we can judge only getting some
types of errors and also get any kind of working drawback of project designing
and data.

Risk can also get by introducing our project in market scenario or client
scenario. Risk identification is a systematic attempt to specify threats to the
project plan.

By identifying known and predictable risks the project manager takes step
toward avoiding them when possible and controlling them when necessary. One
method for identifying risks is to create a risk item checklist.

26
 USER REQUIREMENTS

As the whole organization is going to use the application, the application should
serve the purpose of each person associated with the organization. Depending
on the business logic of each module, the corresponding forms should help the
user to automate the processing in such a way that the physical documents can
be easily mapped to forms available in the application.

The system should eliminate data redundancy and make the data readily
available throughout the organization. In the freelance section I have to focus
on catering the requirements of users of the module. The system should
authenticate the user who will use this system. The system should provide the
central login facility for all the modules so that the user who logon to the one
module can use functionalities of all the modules. As my focus is on the
freelance module I should take care that when user first time logon to the
system his account should be activated by filling up the registration form.

In the freelance section, contact information of the buyers and sellers should not
be displayed to each other. Otherwise, they will communicate with each other
and there is no need of this section.

27
SYSTEM DESIGN

28
 DATABASE

Appointment table

29
Department Table

30
Login table

31
Doctor table

32
Registration table

33
 DATA FLOW DIAGRAM

System diagram

View
(SignUp.aspx,SignIn.as
Home.aspx,Alogin.
px,User.aspx,ForgotPa
aspx,Registration.
ssword.aspx,ChangePa
aspx,Appointment
ssword.aspx,Profile.as SQL SERVER
.aspx,Chat.aspx,A
px,ProfileSelect.aspx,P (Database)
bout.aspx,Contact
rofileUpdate.aspx,Cha Model (Country,Educatio
.aspx t.aspx) Login_id,login
(LINQ to SQL) n,Language,Logge
name,passwo
(modelsignup.cs,m dinUsers,Message
rd,address,Do
odelsignin.cs,mode
Dataclass.dbm ,Profile_Info,Relati
lprofile.cs,modelch ctor_id,Apmt
onship,Relegion,S
l
angepassword.cs, _Id,Dept_Id,D
ecret_Question,U
Controller
(C# class) modelchat.cs) epartmentNa
ser_General_Info,
(logicsignup.cs,logicsig me,etc
User_Userid_Info)
Home.aspx.cs,Registration.as
nin.cs,logicprofile.cs,l
px.cs,Alogin.aspx.cs,Appoint
Dataclass.dbm
(All stored
ment.aspx.cs,chat.aspx.cs,co
ogicchangepassword.c
ntact.aspx.cs,Class1.cs,Class2 l procedures )
s,logicchat.cs)
.cs,loginregiatration.cs

34
35
Screen Layout

36
 SCREEN SHOTS
HOME PAGE

The gateway of the application from where users Sign in into the system.

37
 ABOUT

The first time user can know about the hospital with the help of About page.

38
 CONTACT

The user can get the details like locality of the hospital or the emergency no
through contact page

39
 REGISTRACTION PAGE

The gateway of the application from where users get registered to the site.

40
 AFTER REGISTRACTION

After successful registration the patient gets a mail to his mail Id from
sparkhospitals.com

41
AFTER LOGIN

42
 APPOINMENT PAGE OF DOCTOR

The doctors page when doctor has few appointmets for that day

43
The doctors page when doctor has no appointmet for that day.

44
 APPOINTMENT PAGE OF PATIENT

The user can book appointment through appointment page

45
Software Testing

46
 TESTING

Testing is software quality assurance activity. Which is a very important to

work the system successfully and achieve high quality of software. The main
objective of testing is to find yet an undiscovered error and at the same time
checking the quality and reliability of system.

System testing makes logical assumptions that if all the parts of the system are
correct, the goal will be successfully achieved. The system should be checked
logically. Validations and cross checks should be there. Avoiding duplication of
records, which causes redundancy of data.

This system is tested by the following steps and prepared for the final
implementation. Using review at different stages we ensured that

 Error in function, logic or implementation is uncovered.

 Software meets its requirements.
 To achieve software that is developed in a uniform manner.

47
 UNIT TESTING

In the web based application smallest testable unit is web page itself. So the
web pages of the site are to be unit tested. Each web page contains content,
navigational links and processing elements (scripts, event handlers, etc.). The
testing will be driven by the content processing and links contained in the site.

Using black box testing technique web pages are tested unit by unit for whether
they receive input properly and give output in proper format or redirect to
specific web page. It is also tested that the error message are properly displayed
and give user-friendly information.

48
 INTEGRATED TESTING

We have used top down testing strategy for integrating web pages. The
separately generated web pages will be integrated and for checking that they
work properly after their integration, tests will be conducted to ensure their
proper functionality

Using dummy web pages it is checked that whether output of pages will redirect
to specific web page

After that registration testing strategy help us to ensure that changes do not
introduce unintended behaviour or additional errors.

49
 SYSTEM TESTING

The uncovered weakness that was not found in earlier tested are removed in
system testing. The system is corrected such away that is it does not affect the
forced system failure. This testing is done with low volume of transaction
based on live data. Finally the total system is also tested to ensure that no data
are lost.

Following testing on the completed system will be performed and order to find
the errors before they become defects and correct them.

 In order to eliminate navigational errors the site will be reviewed and

tested. The use cases scenario that we have developed in the same
document while requirement analysis activity will be considered to
uncover in the navigational links.

 Web pages of the site will be unit tested. For the web pages sometimes
the smallest testable unit is the single web page itself. Each web page
contains content, navigational links and processing elements. The testing
will be driven by the content processing and link contained in the site.

 The separately generated web pages will be integrated and for checking
that they work properly after their integration, tests will be conducted to
ensure their proper functionality.

 The functionality of the site will be checked with the different versions of
the browsers and wherever necessary it will be attended to change the
implementation of the not working for some browser fir some case and of
course without losing the purpose of the functionality, if possible.

50
Appendix

51
 LIMITATIONS OF PROJECT

 The computer needs continues electricity, in case of power failure.

 All works have to be done manually.
 Speed of the program depends on the computer processor and RAM.
 This system will not be able to run on the network environment.

52
 FUTURE APPLICATION OF
PROJECT

We expect to expand and add some of the f12eatures to this system in near
future.

These features are……

 To make system more users friendly.
 Configuration features can be changed according to user‟s
Requirements
 Payment method can be easier.
 To provide more security to its users.
 To allow the user to send the mail to his Doctor and tell about
The problem
 Detailed Medical History of the patient can be viewed by Doctor.
.

53
 BIBLIOGRAPHY
Website

 www.google.com
 www.wikipedia.org
 http://www.w3schools.com
 https://www.irctc.co.in/

Book

 Microsoft ASP.NET by Shyam N. Chawda

 ASP.NET Black Book

54