A
Project Report
On
Website For Hospital Information System BCA Semester - VI
Submitted To
Acharya Motibhai Patel Institute of Computer Studies
Ganpat University
Guided By
Prof. Hiral B. Patel
Submitted To
Patel Mona S.[11032211182]
Patel SweetyR.[11032211225] Group No- D 20
AMPICS LIBRARY
Page 1 of 83
Project Profile
Project Titles Website for Hospital Information System
Organization Karnavati Hospital, Ahmedabad
Objective To provide all information regarding Hospital
Front-End Microsoft Visual Studio 2010 (ASP.NET)
Back-End Microsoft SQL Server
Developed for Acharya Motibhai Patel Institute Of
Computer Studies,
Ganpat University, Kherva -382712
Internal Guide Ms. Hiral B. Patel
Group No D 20
Developed By Patel Mona S. [11032211182]
Patel Sweety R. [11032211225]
AMPICS LIBRARY
Page 2 of 83
About Organization
• The organization name is Karnavati Hospital.
• Hospital owner name is Dr. Kamal Powal.
• The Date of establishment is 27-07-2005.
• The Facility of room is 3 semi special, 4 special, 2 deluxe, 2 ICU,
1 OPD, 3 general.
• Hospital have one big Medical store.
• The Surgery like Plastic surgery, Cancer surgery,
Ganicsurgery, Urosurgery, Nurosurgery, Authopadicsurgery.
• When any critical case the visiting doctor from any another Hospital will be called for handling.
• Address :
Opp. Saijpur Tower,
Naroda Road,Ahmedabad
Ph.(079)22804823,22804824
AMPICS LIBRARY
Page 3 of 83
Existing System
• The Existing system is based on manually and computerized.
• Disadvantages • Patient will come and case register then after doctor will
check diseases.
• If report is required for checkup then do it otherwise tack the medicence and leave the hospital.
• This system is time consuming.
• More man power required.
• This Hospital has not any website.
• Existing system is costly.
• All details regarding hospital is maintain in separate file so
to display information for public it not possible.
AMPICS LIBRARY
Page 4 of 83
Need For New System
• Advantage • Data stored in computerized.
• This system is faster.
• All the hospital information is on website so patient can easily
• use this system.
• Less time required.
• All the schedule of doctor is prescribed.
• Hospital about all information is regarding in website.
• Online case register facility available.
• Patient can see the schedule regarding surgery of time of particular doctor.
• Website information like staff member, surgery, hospital images, appoinment time, feedback, and services.
• Save money and time.
• The main purpose of website is advertisements.
AMPICS LIBRARY
Page 5 of 83
Hardware & Software Requirement
Client Side (Recommended)
Hardware Requirement
Processor :-Intel core Dual
RAM :-512MB
Hard Disk :-10 GB
Software Requirement
Operating System :-Window or Above
Software Explorer :-Internet Explorer 6.0 or Above
AMPICS LIBRARY
Page 6 of 83
Hardware & Software Requirement
Server Side (Recommended)
Hardware Requirement
Processor :-Intel core Dual
RAM :-2GB
Hard Disk :-40GB or Above
Software Requirement
:-Internet Information Service (IIS)
:-Window Server 2003 And Above
:-Microsoft SQL Server 2008
:-Crystal Report 10
AMPICS LIBRARY
Page 7 of 83
User Name
Password
login
Modify Ward room
detail
Modify Doctor info
Modify facility info
No
Yes
Admin
A
Start
AMPICS LIBRARY
Page 9 of 83
Modify Appointment info
View Query
Modify Staff info
Give Response
A
Modify Timetable info
Modify Patient info &
View Registration info
End
Generate Report
AMPICS LIBRARY
Page 10 of 83
Patient
View Website
View Ward
Room detail
View Doctor
info View Facility
View Other
details Staff
info
View Time Table Medicle store,
Canteen,
Laboratory
Contact Us
About us
Tack Appointment
Query
form
Login and fill
Registration form
Start
End
AMPICS LIBRARY
Page 11 of 83
mA
0.0
WEBSITE
FOR
HOSPITAL
INFORMA
TION
DOCTOR
ADMIN
Context level for DFD
PATIENT
Manage Hospital
info View Hospital
details
Take Appointment
Check Appointment Appointment Details
Query details
AMPICS LIBRARY
Page 14 of 83
ADMIN 1.0
LOGIN
2.0
WARD
ROOM
3.0
DOCTO
R
First level DFD for Admin
Id/Password
Login response
Id /Password info
login detail
Manage Wardroom
detail Wardroom info
Wardroom info View Wardroom detail
Manage Doctor info Doctor info
Doctor info View Doctor detail
Login info
Wardroom info
Doctor info
TABLOGIN
TABWARDROOM
TABDOCTOR
AMPICS LIBRARY
Page 15 of 83
ss
ADMIN 4.0
FACILIT
Y
5.0
PATIENT
®IST
RATION
6.0
TIMET
ABLE
Manage Facility
info Facility info
Facility info View Facility detail
Facility info
Manage Patient&
Registration info
Patient &
Registration info
View Patient &
Registration detail Patient & registration info
TABFACILITY
TABPATIENT
TABTIMETABLE
Manage Timetable
info Timetable info
View Timetable detail Timetable info
Patient info
Timetable
info
AMPICS LIBRARY
Page 16 of 83
ADMIN
7.0
APPOI
NTME
NT
8.0
STAFF
9.0
QUERY
Manage Appointment
Appointment info
Appointment info
View Appointment detail
Manage Staff detail Staff info
Staff info View Staff detail
Manage Query info Query info
Query info View Query detail
Appointment info
Staff info
TABAPPOINTMENT
TABSTAFF
TABQUERY
AMPICS LIBRARY
Page 17 of 83
PATIENT 1.0
WARD
ROOM
2.0
DOCT
OR
3.0
TIME
TABLE
First level DFD for Patient
Request for Ward room
detail
View Ward room
info Ward room detail
Request for Doctor info
View Doctor info Doctor detail
Timetable info
View Timetable info Timetable detail
Ward room info
Doctor info
Timetable info
TABWARDROOM
TABDOCTOR
TABTIMETABLE
AMPICS LIBRARY
Page 19 of 83
s
PATIENT
4.0
APPO
INTM
ENT
5.0
LOGIN
®I
STRATI
ON
6.0
FACIL
ITY
Request for
Appointment info
View Appointment
info Appointment detail
Appointment info
Request for Login&
Registration info
Login & Registration detail View Login &
Registration info
TABAPPOINTMENT
TABLOGIN
TABFACILITY
Request for Facility info
Facility detail View Facility info
Login & registration info
Facility info
AMPICS LIBRARY
Page 20 of 83
PATIENT
8.0
QUERY
Request for Query
Query detail
TABQUERY
7.0
STAFF
Request for Staff
info
View Staff info Staff detail
TABSTAFF
Staff info
View Query response
AMPICS LIBRARY
Page 21 of 83
DOCTOR 1.0
LOGIN
2.0
CHECK
APPOI
NTME
NT
First level DFD for Doctor
Regi/login details
Login response
Regi/login info
Verify login details
Appointment details
View Appointment
info
Check Appointment info Appointment details
Login info
TABLOGIN
TABAPPOINTMENT
AMPICS LIBRARY
Page 22 of 83
ADMIN Manage WARDROOM
View
PATIENT
Manage APPOINTMENT Get
Manage
QUERY
DOCTOR
Manage
View
Get
Loginid
User Name
Password
Wardroomid
Wardname
Patientid
First name
Appointmentid Date
Gender
Firstname
Doctorid
Queryid
Patientid
1 1 1
1 M
M
M
M
M
M
M M
1
1
M
AMPICS LIBRARY
Page 24 of 83
TABLOGIN
No. Field Name Data Type Size Constraint Description
1 Loginid Int _ Primary Key Store loginid
2 Username Varchar 30 Not Null Store Username
3 Password Varchar 10 Not Null Store Password
4 Patientid Int - Not Null Store Patientid
AMPICS LIBRARY
Page 26 of 83
TABPATIENT
No. Field Name Data Type Size Constraint Description
1 Patientid Int _ Primary Key Store Patientid
2 Firstname Varchar 50 Not Null Store Firstname
3 Lastname Varchar 50 Not Null Store Lastname
4 Address Varchar 200 Not Null Store Address
5 Pincode Numeric 6,0 Not Null Store Pincode
6 Mobileno Numeric 10,2 Not Null Store Mobilesno
7 Email Varchar 100 Null Store Email
AMPICS LIBRARY
Page 27 of 83
TABPATIENT
No. Field Name Data Type Size Constraint Description
8 Gender Varchar 6 Not Null Store Gender
9 Height Numeric 5,2 Not Null Store Height
10 Weight Numeric 5,2 Not Null Store Weight
AMPICS LIBRARY
Page 28 of 83
TABDOCTOR
No. Field Name Data Type Size Constraint Description
1 Doctorid Int _ Primary Key Store Doctorid
2 Firstname Varchar 50 Not Null Store Firstname
3 Lastname Varchar 50 Not Null Store Lastname
4 Mobileno Numeric 10,2 Not Null Store Mobileno
5 Email Varchar 100 Not Null Store Email
6 Specialist Varchar 100 Not Null Store Specialist
AMPICS LIBRARY
Page 29 of 83
TABDOCTOR
No. Field Name Data Type Size Constraint Description
7 Degree Varchar 100 Not Null Store Degree
8 Image Varchar 100 Not Null Store Photo
9 Gender Varchar 6 Not Null Store Gender
AMPICS LIBRARY
Page 30 of 83
TABSTAFF
No. Field Name Data Type Size Constraint Description
1 Staffid Int _ Primary Key Store Doctorid
2 Firstname Varchar 50 Not Null Store Firstname
3 Lastname Varchar 50 Not Null Store Lastname
4 Address Varchar 200 Not Null Store Address
5 Pincode Numeric 6,0 Not Null Store Pincode
6 Mobileno Numeric 10,2 Not Null Store Mobileno
7 Email Varchar 100 Null Store Email
AMPICS LIBRARY
Page 31 of 83
TABSTAFF
No. Field Name Data Type Size Constraint Description
8 Photo Varchar 100 Not Null Store Photo
9 Gender Varchar 6 Not Null Store Gender
AMPICS LIBRARY
Page 32 of 83
TABWARDROOM
No. Field Name Data Type Size Constraint Description
1 Wardroomid Int _ Primary Key Store Wardroomid
2 Wardname Varchar 50 Not Null Store Wardname
3 Wardescription Varchar 200 Not Null StoreWarddescription
4 Image Varchar 200 Not Null Store Image
AMPICS LIBRARY
Page 33 of 83
TABFACILITY
No. Field Name Data Type Size Constraint Description
1 Facilityid Int _ Primary Key Store Facilityid
2 Facilityname Varchar 50 Not Null Store Facilityname
3 Facilitydescription Varchar 300 Not Null Store
Facilitydescription
4 Image Varchar 200 Not Null Store Image
AMPICS LIBRARY
Page 34 of 83
TABTIMETABLE
No. Field Name Data Type Size Constraint Description
1 Timetableid Int _ Primary Key Store Timetableid
2 Doctorid Int _ Foreign Key Store Doctorid
3 Day Varchar 20 Not Null Store Day
4 Intime Varchar 20 Not Null Store Intime
5 Outtime Varchar 20 Not Null Store Outtime
AMPICS LIBRARY
Page 35 of 83
TABAPPOINTMENT
No. Field Name Data Type Size Constraint Description
1 Appointmentid Int _ Primary Key Store
Appointmentid
2 Date Datetime _ Not null Store Date
3 Patientid Int _ Foreign key Store Patientid
AMPICS LIBRARY
Page 36 of 83
TABQUERY
No. Field Name Data Type Size Constraint Description
1 Queryid Int _ Primary Key Store Queryid
2 Patientid Int _ Foreign Key Store Patientid
3 Contentdate Date _ Not Null Store Contentdate
4 Contentdetail Varchar 20 Not Null Store Contentdetail
AMPICS LIBRARY
Page 37 of 83
Brief Description Of Process
Admin:-
Login :- System is being with the login process. Admin enter his username and
pass ord if it’s ro g the pro ess has ee stop a d if su essfully logi the process will be continue.
Ward Room:- Admin has the all manage the wardroom details.
Doctor:- Admin has the manage the add update and delete the manage information
in doctor.
Facility:- Admin has the manage all facility in system.
Patient & Registration :- Admin has the manage patient details and view
Patient registration.
Timetable:-Admin has the manage all doctor timetable.
Appointment:- Admin has the manage all information of appointment.
Staff:- Admin has the manage all information of staff.
Query:- Admin has view query and give response of query.
AMPICS LIBRARY
Page 39 of 83
Brief Description Of Process
Patient :-
Login :- System is being with the login process. Patient enter his username and
pass ord if it’s ro g the pro ess has ee stop a d if su essfully logi the process will be continue.
View website :- Patient view website information is wardroom detail, doctor
information, timetable detail, staff information and tack appointment then after fill up
the registration form.
View facility :- Patient view hospital facility is medical store, cantina and leboratory.
View other detail :- Patient show other details like about us, contact us.
Query :- Patient has any query so fill the query form.
Doctor:-
Login :- System is being with the login process. Doctor enter his username and
pass ord if it’s ro g the pro ess has ee stop a d if su essfully logi the process will be continue.
Appointment :- Doctor check the appointment.
AMPICS LIBRARY
Page 40 of 83
Process Algorithm For Admin Step 1:- Start.
Step 2:- Insert username and password.
Step 3:- If login then go to step4 else go to step2.
Step 4:- Admin manage wardroom details.
Step 5:- Admin manage doctor information.
Step 6:- Admin manage patient detail and view registration information.
Step 7:- Admin manage timetable details.
Step 8:- Admin manage appointment information.
Step 9:- Admin manage staff information.
Step 10:- Admin view query.
Step11:- Admin give response.
Step12:- End
AMPICS LIBRARY
Page 41 of 83
Process Algorithm for Patient Step 1:- Start.
Step 2:- Insert username and password.
Step 3:- If login then go to step4 else go to step2.
Step 4:- View website information.
Step 5:- View wardroom detail.
Step 6:- View doctor info and timetable detail then after tack appointment and fill up the
registration form.
Step 7:- View facility like medical store, canteen, laboratory.
Step 8:- View other detail contact us and about us.
Step 9:- View staff information and ask any query.
Step 10:- End.
AMPICS LIBRARY
Page 42 of 83
Process Algorithm for Doctor
Step 1:- Start.
Step 2:- Insert username and password.
Step 3:- If login then go to step4 else go to step2.
Step 4:- Check appointment.
Step 5:-End.
AMPICS LIBRARY
Page 43 of 83
The Testing is the process of executing a program with the explicit information of finding error that is making in the program.
Generally , there are three tests used for testing software.
1. Code Testing.
2. Unit Testing.
Code Testing :-
The code testing strategy examines the logic of the program. the analyst develop Test case the result in executing every instruction in the program or module.
Every path through the program is tested.
Unit Testing :-
Unit testing focuses first on the modules independently of one another to locate Errors . This enable the tester to detect errors in coding and logic that are contained within that program alone the test case needed for unit testing should exercise each Condition and option.
Unit testing can be performed from the button-up starting with the smallest and Lowest level proceeding at a time.
AMPICS LIBRARY
Page 77 of 83
Reviews are taken until system fulfills user requirements. After
implementation it is easy to manage the system and solve the
difficulties.
After the system is implemented and conversion is completed a
re ie of perso al is Good. They are satisfied ith this WEB“ITE FOR HO“PITAL INFORMATION a d also fro ork. The most fundamental concern post implementation review is
determining whether the System has met its objective; that is analyst
want to know if the performance level of user Has improved and if the
system is producing the result intended if neither is happening One may
question whether the system can be considered successful.
Post implementation review is used for taking review of project.
AMPICS LIBRARY
Page 79 of 83
We think that not a single project is ever consider as complete forever
Because our mind is always thinking new and our necessities also are
growing day by day.
We always want something more that want we have. Our application
also, if you see at the glance that you find it to be complete but we want
to make it still mature and fully automatic.
Some are the expansion which we have thought of are :
• Try to make system online hospital manage.
• Accounting system can include the system.
• Medicals accounting also include the system.
AMPICS LIBRARY
Page 81 of 83
During the development of project I have use following books and
some website for reference.
Websites:-
www.w3school.com
www.code4asp.com
www.apoolo.com
Books :-
- The Complete Reference ASP.NET
Matthew MacDonald
- Microsoft Asp.net
Shayam N. Chawada
- Database Management System C.J.Date
AMPICS LIBRARY
Page 83 of 83