1 2 3 4 5 Merged

INTEGRATED HEALTH CARE
MANAGEMENT SYSTEM
A REPORT
submitted by
MENDE SHASHI PREETHAM (22MIC0136)
ANAMPALLI ESHWAR (22MIC0098)
VISSHAL E (22MIC0192)
D SAI DHARANIDHAR REDDY (22MID0223)
JANARTHANAN N S (22MID0351)
for
CSI1007-Software Engineering Principles
School of Computer Science and Engineering
April 2024
VELLORE INSTITUTE OF TECHNOLOGY, VELLORE – 632014
SCHOOL OF COMPUTER SCIENCE AND ENGINEERING
BONAFIDE CERTIFICATE
Certified to be the bonafide record of the work done by

_______________________________________ of Winter Semester M.Tech.( Integrated) Degree in
Vellore Institute of Technology of School of Computer Science and Engineering in the CSI1007 -
Software Engineering Principles (ELA) Laboratory during the academic year 2023-2024.
LAB IN-CHARGE
Submitted for the Final Assessment examination held on ________________
EXTERNAL EXAMINER INTERNAL EXAMINER

Chapter No. Table of Contents Page No
1. Introduction 1
2. Requirements 2
1. SRS
2.2 ER Diagram
2.3 DFD Diagram (upto level-2)
2.4 Gantt Chart
3. UML Design Diagrams 5
1. Use Case Diagram
2. Use Case Description
3. Class Diagram
4. Sequence Diagram
5. State Chart Diagram
6. Interaction Diagrams
7. Package Diagrams
8. Component Diagrams
9. Deployment Diagrams
4. Modules Design and Implementation 10
4.1 User Interface Design
4.2 Module-1
4.3 Module-2
4.4 Module-3
4.5 Input and output Design
5. Testing
5.1 Unit Testing
5.2 Integration Testing
5.3 Whitebox Testing
5.4 Blackbox Testing
6. Results and Discussion
6.1 Results
6.2 Discussion on Results
7. Conclusion
8. References
9. Appendix-I (Sample source code, screenshots, etc)
Any other Appendix (pictures of your model, photos of the model, etc)
CHAPTER 1
INTRODUCTION
1.1 Purpose
The purpose of this document is to provide information on Hospital Management System Project. It
will try to explain the functionalities of the project and the features it provides. It is helpful for
receptionists to book an appointment for patients, and to login and maintain everything and access
the portal easily due to its user friendly nature.
1.2 Document Conventions

Arial is the font size used with the font sizes 11,14,18,32. Priorities for higher level requirements
are assumed to be inherited by detailed requirements.
1.3 Intended Audience and Reading Suggestions

This software requirements document is intended for
- Developers who can review the project's capabilities and can understand the features in order to
make necessary changes in design and code for future development.
- Project testers can also use this document as base for their testing strategies as it will be easier for
them to find bugs using this document.
- End users of this website can use this document; to know about the functionalities of this project.
1.4 Product Scope

This Hospital management system is an easy-to-use website which helps is recording information
from patients and doctors. It helps receptionists to book an appointment for patients,
and to generate bills, check for availability of beds and rooms and also to provide the services
available in the hospital to patients.
1.5 Product Perspective

Our project, Hospital Management System e follows manual procedures to keep track of its day to
day activities. When scenarios such as patient information handling, employee handling, financial
analysis and report generation is taken into consideration there exists many issues with regard to
efficiency, security, accuracy and reliability. Due to improperly managed details medical center
faces quite a lot of difficulties in accessing past data as well as managing present data. The manual
file systems which are being used at present require storage facilities which is also another
overhead.
The fully functional automated hospital management system which will be developed through this
project will eliminate the disadvantages caused by the manual system by improving the reliability,
efficiency and performance. The usage of a database to store patient, employee, stock details etc.
will accommodate easy access, retrieval, search and manipulation of data.
After analyzing the requirements we have decided to take iterative model for our project.
Reasons for choosing Iterative Waterfall Model for SDL(System Development Lifecycle) are:
• Iterative waterfall model is simple and easy to design.
• We will be able to identify the error as close to it’s point of inception or in the same phase as
it was created.
• By this the cost of rectifying the error will be reduced.
• We are not using any new technology in our project.
• Requirements are very well known
• Other models like spiral and incremental requires a lot of understanding in non – technical
management and increments need to be done. Hence they were not preferred.
1.6 Product Functions

1. Login details: This tool helps to enter into hospital web page
2. Doctor details: This tool helps Management to know about entire information of the doctors such
as contact info, qualifications etc..
3. Add/Delete/Edit details: This tool helps to Add/Delete/Edit details of the doctors about their
personal information and patient details.
4. Patient Admission Info: This tool is used to get the details of the Patients such as doctor allocated
,Disease being suffered and their admit date etc..
5. Service Info: This tool is used by management to provide services to patients such as various
types of Rooms and Vacancy of Rooms.
6. Billing Info: This tool helps the Hospital Management to get the billing information of the
patient and help them to get paid .
1.7 Operating Environment

This Hospital Management System is a website, hospital staff can access through laptop, pc or
mobile. It is compatible with all devices and operating systems.
1.8 Design and Implementation Constraints

The website is used by all hospital staff. Hence the design of the website should be simple and
functions should be easy to use, to make it easy for receptionists at the Hospital.
CHAPTER 2
2.1 SOFTWARE REQUIREMENTS SPECIFICATION
INTRODUCTION
The Integrated Healthcare Management System (IHMS) is a comprehensive software solution aimed at
facilitating the efficient management of healthcare facilities. IHMS integrates various functionalities
including patient management, electronic health records (EHR), appointment scheduling, billing, and
reporting to streamline operations and enhance patient care. This document outlines the functional and
non-functional requirements of the IHMS.
SCOPE
The IHMS will provide healthcare facilities with a centralized platform to manage patient information,
appointments, billing, and reporting. The system will support multiple user roles including
administrators, healthcare providers, and patients. Key features of the IHMS include:
- Patient Management: Registration, demographics, medical history, and visit records.
- Electronic Health Records (EHR): Digital storage and retrieval of patient health information.
- Appointment Scheduling: Booking, rescheduling, and cancellation of appointments.
- Billing and Invoicing: Generation of bills, payment tracking, and invoicing.
- Reporting: Generation of various reports including patient demographics, revenue, and operational
efficiency.
FUNCTIONAL REQUIREMENTS
1. User Management
- The system shall support multiple user roles including administrators, healthcare providers, and
patients.
- Administrators shall have the authority to add, modify, and deactivate user accounts.
2. Patient Management
- Patients shall be able to register and update their demographic information.
- Healthcare providers shall have access to patient demographics, medical history, and visit records.
- The system shall support the creation and maintenance of electronic health records (EHR) for each
patient.
3. Appointment Management
- Patients shall be able to schedule, reschedule, and cancel appointments through the system.
- Healthcare providers shall have access to their appointment schedules and be able to manage them.
4. Billing and Invoicing
- The system shall generate bills based on services rendered and patient information.
- Patients shall be able to view and pay bills online.
- Administrators shall have access to billing and invoicing reports.
5. Reporting
- The system shall generate various reports including patient demographics, revenue, and appointment
statistics.
- Reports shall be exportable in common formats such as PDF and Excel.
NON-FUNCTIONAL REQUIREMENTS
1. Performance
- The system shall be able to handle concurrent user sessions without significant degradation in
performance.
- Response time for common tasks such as appointment scheduling shall be less than 2 seconds.
2. Security
- The system shall comply with industry standards for data security including encryption of sensitive
information.
- User authentication shall be required for accessing patient health records and other confidential data.
3. Scalability
- The system architecture shall be scalable to accommodate the growing needs of healthcare facilities.
- Additional servers and resources shall be easily added to handle increased user load.
4. Usability
- The user interface shall be intuitive and easy to navigate for users with varying levels of technical
expertise.
- The system shall provide contextual help and guidance to assist users in performing tasks.
CONCLUSION
The Integrated Healthcare Management System (IHMS) is designed to streamline operations and
enhance patient care in healthcare facilities. By integrating patient management, electronic health
records, appointment scheduling, billing, and reporting functionalities, IHMS provides a
comprehensive solution to meet the needs of modern healthcare organizations.
GLOSSARY
IHMS: Integrated Healthcare Management System
EHR: Electronic Health Records

2.2 ER DIAGRAM
2.3 DFD DIAGRAM

DATA FLOW DIAGRAM (DFD)
A data-flow diagram is a way of representing a flow of data through a process or a system
(usually an information system). The DFD also provides information about the outputs and
inputs of each entity and the process itself.
0 Level DFD – Hospital Management System: -
The 0 level dfd known as context level data flow diagram. The context level data flow diagram
(dfd) is describing the whole system. The (o) level dfd describe the all user modules who run the
system. Below context level data flow diagram of hospital management system project shows the
one Admin user can operate the system. Admin do all activities after login to system.
1st level DFD – Hospital Management System: -

The Admin side DFD describe the functionality of Admin. Admin is a responsible person who run
the project. After login to system admin can first Add Patient Details and Doctor Details and then
provides service and then gives appointments accordingly. And admin can manage patient reports
and generates bill details.
2nd LEVEL DFD –LEVEL 1.0
2nd LEVEL DFD – LEVEL 2.0

2.4 GANTT CHART
CHAPTER 3
UML DESIGN DIAGRAMS
3.1 Use Case Diagram
3.2 Use Case Description

3.3 Class Diagram
3.4 Sequence Diagram

3.5 State Chart Diagram
3.6 Interaction Diagram
3.7 Package Diagram

3.8 Component Diagram
3.9 Deployment Diagram

CHAPTER 4
MODULES DESIGN AND IMPLEMENTATION
4.1 USER INTERFACE DESIGN
4.2 MODULE-1
4.3 MODULE-2
4.4 MODULE-3
4.5 INPUT & OUTPUT DESIGN

Generate the code as per your developed language. (If for your
language, the plugins are not available, then generate the code in
JAVA).
Display your output as File Name and File Content for each file
generated.
Login.java
import java.util.*;
/**
*
*/
public class LOGIN {
/**
* Default constructor
*/
public LOGIN() {
}
/**
*
*/
private STRING USERNAME;
/**
*
*/
private STRING PASSWORD;
/**
* @param USERNAME
* @param PASSWORD
* @return
*/
public BOOLEAN LOGIN_VERIFICATION(STRING USERNAME, STRING
PASSWORD) {
// TODO implement here
return null;
}
Receptionist.java
import java.util.*;
/**
*
*/
public class RECEPTIONIST extends BILL {
/**
*/
public RECEPTIONIST() {
}
/**
*
*/
private STRING NAME;
/**
*
*/
private STRING RECEPTIONISTID;
/**
*
*/
private FLOAT PHONENUMBER;
/**
* @param NAME
* @param RECEPTIONISTID
* @param PHONENUMBER
* @return
*/
public STRING VIEWPROFILE(STRING NAME, STRING RECEPTIONISTID, FLOAT
PHONENUMBER) {
return null;
}
/**
* @param NAME
* @param PATIENTID
* @param AGE
* @param MOBILENO
* @param HEALTHISSUE
* @return
*/
public STRING EDITPATIENTDETAILS(STRING NAME, INT PATIENTID, INT AGE,
FLOAT MOBILENO, STRING HEALTHISSUE) {
return null;
}
/**
* @param NAME
* @param DOCTORID
* @param SPECIALIZATION
* @param MOBILENO
* @return
*/
public STRING EDITDOCTORDETAILS(STRING NAME, INT DOCTORID, STRING
SPECIALIZATION, FLOAT MOBILENO) {
return null;
}
Patient.java
import java.util.*;
/**
*
*/
public class PATIENT extends BILL {
/**
*/
public PATIENT() {
}
/**
*
*/
/**
*
*/
private INT PATIENTID;
/**
*
*/
private INT AGE;
/**
*
*/
private STRING HEALTHISSUE;
/**
*
*/
private FLOAT MOBILENO;
/**
* @param NAME
* @param PATIENTID
* @param AGE
* @param HEALTHISSUE
* @param MOBILENO
* @return
*/
public STRING VIEWDETAILS(STRING NAME, INT PATIENTID, INT AGE, STRING
HEALTHISSUE, FLOAT MOBILENO) {
return null;
}
Doctor.java
import java.util.*;
/**
*/
public DOCTOR() {
}
/**
*
*/
/**
*
*/
private INT DOCTORID;
/**
*
*/
private STRING SPECIALIZATION;
/**
* @param NAME
* @param DOCTORID
* @param SPECIALIZATION
* @param MOBILENO
* @return
*/
public STRING VIEWDETAILS(STRING NAME, INT DOCTORID, STRING
SPECIALIZATION, FLOAT MOBILENO) {
return null;
}
Service Info.java
import java.util.*;
/**
/**
*/
public SERVICE INFO() {
}
/**
*
*/
private INT ROOMNO;
/**
*
*/
private INT BEDNO;
/**
*
*/
private STRING ROOMTYPE;
/**
* @param ROOMNO
* @param BEDNO
* @param ROOMTYPE
* @return
*/
public STRING VIEWDETAILS(INT ROOMNO, INT BEDNO, STRING ROOMTYPE)
{
return null;
}
Bill.java
import java.util.*;
/**
*
*/
private class BILL {
/**
*/
private BILL() {
}
/**
*
*/
private INT APPOINTMENTFEE;
/**
*
*/
private INT ROOMFEE;
/**
*
*/
private INT EXTRAFEE;
/**
* @param APPOINTMENTFEE
* @param ROOMFEE
* @param EXTRAFEE
* @return
*/
public INT VIEWBILLDETAILS(INT APPOINTMENTFEE, INT ROOMFEE, INTEXTRAFEE)
{
return null;
}
/**
* @param APPOINTMENTFEE
* @param ROOMFEE
* @param EXTRAFEE
* @return
*/
public INT PATIENTPAYSBILL(INT APPOINTMENTFEE, INT ROOMFEE, INTEXTRAFEE)
{
return null;
}
}
CHAPTER 5
TESTING
5.1 UNIT TESTING:

Unit testing involves the design of test cases that validate that the internal program
logic is functioning properly, and that program input produce valid outputs. All
decision branches and internal code flow should be validated. It is the testing of
individual software units of the application it is done after the completion of an
individual unit before integration. This is a structural testing, that relies on knowledge
of its construction and is invasive. Unit tests perform basic tests at component level
and test a specific business process, application, and/or system configuration. Unit
tests ensure that each unique path of a business process performs accurately to the
documented specifications and contains clearly defined inputs and expected results.
5.2 INTEGRATION TESTING:

Integration tests are designed to test integrated software components to determine if
they actually run as one program. Testing is event driven and is more concerned with
the basic outcome of screens or fields. Integration tests demonstrate that although the
components were individually satisfaction, as shown by successfully unit testing, the
combination of components is correct and consistent. Integration testing is
specifically aimed at exposing the problems that arise from the combination of
components.
Software integration testing is the incremental integration testing of two or more
integrated software components on a single platform to produce failures caused by
interface defects.The task of the integration test is to check that components or
software applications, e.g. components in a software system or - one step up -
software applications at the company level - interact without error.
Test Results: All the test cases mentioned above passed successfully. No defects
encountered.
5.3 WHITE BOX TESTING:

White Box Testing is a testing in which in which the software tester has knowledge of
the inner workings, structure and language of the software, or at least its purpose. It is
purpose. It is used to test areas that cannot be reached from a black box level.
5.4 BLACK BOX TESTING
Black Box Testing is testing the software without any knowledge of the inner
workings, structure or language of the module being tested.
Black box tests, as most other kinds of tests, must be written from a definitive source
document, such as specification or requirements document, such as specification or
requirements document. It is a testing in which the software under test is treated, as a
black box. you cannot "see"into it. The test provides inputs and responds to outputs
without considering how the software works
CHAPTER 6
RESULTS AND DISCUSSION
6.1 Results
6.2 Discussion on Results
SNAP SHOTS OF IMPLEMENTATION OF WORK
Loginpage.html:
<html>
<body>
<h1ALIGN="center">NANDIKA HOSPITALS</h1>
<imgsrc="E:\HOS\LOGO.jpg"alt="Avatar"class="avatar">
<h2>Username</h2>
<inputtype="text">
<h2>Password</h2>
<inputtype="text"><br><br><br>
<ahref="E:\HOS\HOMEPAGE1.html"target="blank"><buttonclass="button">LOGIN</butt
on></a>
</body>
<style>
h1 {
color: black;
font-family: Times New Roman;
font-size: 300%;
text-shadow: 2px2px;
}
img.avatar {
border-radius: 50%;
height: 100px;
width: 100px;
}
.button {
border: none;
color: black;
padding: 15px32px;
text-align: center;
text-decoration: none;
display: inline-block;
font-size: 16px;
margin: 4px2px;
cursor: pointer;
}
body{
background-image: url('https://thumbs.dreamstime.com/b/healthcare-technology-
doctor-using-digital-tablet-icon-medical-network-hospital-background-
162019727.jpg');
padding-top: 50px;
padding-right: 150px;
padding-bottom: 300px;
padding-left: 150px;
text-align: center;
background-position: center;
background-repeat: no-repeat;
background-size: cover;
}
</style>
</html>
This is login page of our hospital management project where

receptionist (User) have to enter the username and password to get the
access to homepage.
HOMEPAGE.html:
<STYLE>
body{
background-image: url('https://thumbs.dreamstime.com/b/healthcare-
technology-doctor-using-digital-tablet-icon-medical-network-hospital-
background-162019727.jpg');
padding-top: 50px;
text-align: center;
}
.imgcontainer {
text-align: center;
margin: 24px012px0;
img.avatar {
border-radius: 50%;
height: 100px;
width: 100px;
}
h1 {
color: black;
font-size: 300%;
}
p {
color: MediumSeaGreen;
font-size: 160%;
}
.button {
border: none;
color: blue;
padding: 15px32px;
text-align: center;
font-size: 16px;
margin: 4px2px;
cursor: pointer;
}
</STYLE>
<bodystyle="background-color: bisque;">
<h1>NANDIKA HOSPITALS</h1>
<divclass="imgcontainer">
<imgsrc="https://thumbs.dreamstime.com/b/hospital-logo-template-hospital-
logo-template-117487677.jpg"alt="Avatar"class="avatar">
</div>
<ahref="E:\HOS\PATIENT.HTML"target="blank">
<buttonclass="button button1"> PATIENT DETAILS</button></a>
<ahref="E:\HOS\editing.html"target="blank">
<button
class="button button2">DOCTOR DETAILS</button></a>
<ahref="E:\HOS\SERVICE.html"target="blank"><buttonclass="button
button3">SERVICE INFO</button></a>
<ahref="E:\HOS\bill.html"target="blank"><button
class="button button4">BILL DATA</button></a>
<ahref="E:\HOS\loginpage.html"target="blank"><buttonclass="button
button7">LOGOUT</button></a>
</body>
After logging in, user enters into the home page of our project where it
has several options (functionalities) as patient details, doctor details,
service info, bill data and logout
PATIENT.html:
<style>
body{
padding-top: 50px;
text-align: center;
}
</style>
<body>
<br>
<br>
<form>
<h1align="center">PATIENT DETAILS</h1>
<label>Firstname: </label><br>
<inputtype="text"name="firstname"><br><br>
<label>Middlename: </label><br>
<inputtype="text"name="middlename"><br><br>
<label>Lastname: </label><br>
<inputtype="text"name="lastname"><br><br>
<label> AGE </label> <br>
<inputtype="text"name="AGE"><br><br>
<label>
DISEASE TYPE :
</label>
<select>
<option>HEART</option>
<option>DIABETES</option>
<option>DENGUE</option>
<option>CORONA</option>
</select>
<br>
<br>
<label>
Gender :
</label><br>
<inputtype="radio"name="male"/> Male <br>
<inputtype="radio"name="female"/> Female <br>
<inputtype="radio"name="other"/> Other
<br>
<br>
<label>
Phone :
</label>
<inputtype="text"name="country code" value="+91"size="2"/>
<inputtype="text"name="phone"size="10"/><br><br>
Address
<br>
<textareacols="80"rows="5"value="address">
</textarea>
<br><br>
<ahref="E:\HOS\dialogue.html"><inputtype="button"value="Submit"/></a>
</form>
</body>
On clicking patient details option, it will be redirected into patient

details portal where user has to enter the details of the patient such as
name, age, disease that the patient is suffering from, gender, contact
and address of the patient.
SAVED SUCCESSFULLY.html:
<!DOCTYPEhtml>
<style>
body{
162019727.jpg');
padding-top: 50px;
text-align: center;
}
</style>
<html>
<body>
<BR><BR><BR><BR><BR>
<dialogopen><H2STYLE="COLOR:BLUE">SAVED SUCCESSFULLY</H2></dialog>
</body>
</html>
When user submits the details of the patient, it shows the message as
saved successfully.
DOCTOR.html:
<style>
body{
padding-top: 50px;
text-align: center;
}
.imgcontainer {
text-align: center;
margin: 24px012px0;
img.avatar {
border-radius: 50%;
height: 100px;
width: 100px;
}
h1 {
color: black;
font-size: 300%;
}
p {
color: MediumSeaGreen;
font-size: 160%;
}
.button {
border: none;
color: blue;
padding: 15px32px;
text-align: center;
font-size: 16px;
margin: 4px2px;
cursor: pointer;
}
</style>
<bodystyle="background-color: bisque;">
<h1>NANDIKA HOSPITALS</h1>
<divclass="imgcontainer">
<imgsrc="https://thumbs.dreamstime.com/b/hospital-logo-template-hospital-
logo-template-117487677.jpg"alt="Avatar"class="avatar">
</div>
<ahref="E:\HOS\docediting.html"target="blank"><buttonclass="button
button1"> EDIT DETAILS</button></a>
<ahref="E:\HOS\doctor.html"target="blank"><buttonclass="button
button2">NEW DETAILS</button></a>
</body>
On clicking doctor details, it shows two options as edit details and new
details to be updated or added by user.
EDIT DETAILS.html:
<STYLE>
body{
padding-top: 50px;
text-align: center;
}
</STYLE>
<body>
<formalign = "center">
<label><H1>ENTER THE DOCTOR ID</H1></label>
<inputtype="text"placeholder="enter Id here"><br><br>
<inputtype="button"value="submit">
</form>
</body>
When user clicks on edit details, it asks to enter the doctor id so that the
user can edit the details of the doctor
NEW DETAILS.html:
<style>
body{
padding-top: 50px;
text-align: center;
}
h1{
text-align: center;
color:black;
font-family:'Times New Roman', Times, serif;
font-size: 300%;
}
</style>
<!DOCTYPEhtml>
<htmllang="en">
<head>
<metacharset="UTF-8">
<metaname="viewport"content="width=device-width, initial-scale=1.0">
<metahttp-equiv="X-UA-Compatible"content="ie=edge">
<title>Doctor Information Form</title>
<scriptsrc="https://ajax.googleapis.com/ajax/libs/jquery/3.3.1/jquery.min.js">
</script>
<scriptsrc="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/js/bootstrap.min.j
s"></script>
<linkrel="stylesheet"href="style.css">
</head>
<bodystyle="background-color:CadetBlue;">
<divclass="main">
<divclass="a">
<h1align="center"><br/>Doctor Details</h1>
<formclass="myForm"method="get"enctype="application/x-www-
form-urlencoded"action="/html/codes/html_form_handler.cfm">
</br>
<h3><br/>Doctor Name</h3>
<p>
<label>First Name:
<inputtype="text"name="first_name"placeholder="Enter first name"required>

</label>
<label>Middle Name:
<inputtype="text"name="middle_name"placeholder="Enter middle name">

</label>
<label>Last Name:
<inputtype="text"name="Last_name"placeholder="Enter last name"required>

</label>
</p>
<p>
<label>Date of Birth:
<inputtype="datetime-
local"name="doc_dob"required>
</label>
<fieldset>
<legend>Gender:</legend>
<p><labelclass="choice"><inputtype="radio"name="gender"requiredvalue="male">Ma
le</label></p>
<p><labelclass="choice"><inputtype="radio"name="gender"requiredvalue="female">
Female</label></p>
<p><labelclass="choice"><inputtype="radio"name="gender"requiredvalue="others">
Others</label></p>
</fieldset>
<label>Date of appointment:
<inputtype="datetime-
local"name="appointment_time"required>
</label>
</p>
</br>
<h3>Educational Qualifications:</h3>
<tableid = "table">
<tr>
<th>Serial</th>
<th>Degree</th>
<th>Board/Institute</th>
<th>Year</th>
<th>Division/CGPA</th>
<th>Position</th>
</tr>
<tr>
<td><label>1.</label></td>
<td>SSC/O'Levels</td>
<td><inputtype="test"name="inst_name"placeholder="insert institute
name"required></td>
<td><inputtype="test"name="year"placeholder="insert year of
graduation"required></td>
<td><inputtype="test"name="div/cgpa"placeholder="insert
division/cgpa"required></td>
<td><inputtype="test"name="position"placeholder="insert
position"required></td>
</tr>
<tr>
<td>HSC/A'Levels</td>
<td><inputtype="test"name="inst_name"required></td>
<td><inputtype="test"name="year"required></td>
<td><inputtype="test"name="div/cgpa"required></td>
<td><inputtype="test"name="position"required></td>
</tr>
<tr>
<td>MBBS</td>
<td><inputtype="test"name="inst_name"required></td>
<td><inputtype="test"name="year"required></td>
<td><inputtype="test"name="div/cgpa"required></td>
<td><inputtype="test"name="position"required></td>
</tr>
<tr>
<td><inputtype="test"name="degree"placeholder="insert degree"></td>
<td><inputtype="test"name="inst_name"></td>
<td><inputtype="test"name="year"></td>
<td><inputtype="test"name="div/cgpa"></td>
<td><inputtype="test"name="position"></td>
</tr>
<tr>
<td><inputtype="test"name="degree"></td>
<td><inputtype="test"name="inst_name"></td>
<td><inputtype="test"name="year"></td>
<td><inputtype="test"name="div/cgpa"></td>
<td><inputtype="test"name="position"></td>
</tr>
</table>
</br>
<h3>Experience:</h3>
<tableid = "table">
<tr>
<th>Serial</th>
<th>Job Designation</th>
<th>From</th>
<th>To</th>
<th>Organization</th>
</tr>
<tr>
<td><inputtype="test"name="job_desg"placeholder="insert job
designation"required></td>
<td><inputtype="date"name="from"placeholder="insert starting
date"required></td>
<td><inputtype="date"name="to"placeholder="insert regination
date"required></td>
<td><inputtype="test"name="org_name"placeholder="insert name of
organization"required></td>
</tr>
<tr>
<td><inputtype="test"name="job_desg"></td>
<td><inputtype="date"name="from"></td>
<td><inputtype="date"name="to"></td>
<td><inputtype="test"name="org_name"></td>
</tr>
<tr>
</tr>
<tr>
</tr>
<tr>
</tr>
</table>
<br/>
<fieldset>
<legend>Membership:</legend>
<labelclass="choice"><inputtype="radio"name="membership"requiredvalue="BMA">BM
A</label>
<labelclass="choice"><inputtype="radio"name="membership"requiredvalue="brit_me
d">British Medical Society</label>
<labelclass="choice"><inputtype="radio"name="membership"requiredvalue="amer_me
d">American Medical Society</label>
<labelclass="choice"><inputtype="radio"name="membership"requiredvalue="others"
>Others</label></p>
</fieldset>
<p><button>Submit</button></p>
</form>
</div>
<divclass="footer">
</div>
</div>
</body>
</html><SCRIPTLanguage=VBScript>
When user clicks on new details, it shows several details of the new
doctor to be added such as name, date of birth, gender, date of joining,
educational qualifications, experience and membership.
SERVICEINFO.html:
<style>
body{
padding-top: 50px;
text-align: left;
}
h1{
text-align: center;
color:black;
font-family:'Times New Roman', Times, serif;
font-size: 300%;
}
p{
color: darkred;
}
</style>
<body>
<form>
<h1>SERVICE INFO</h1>
<p><b>NOTE: </b>This is only applicable for patients who are admitting in
hospital</p>
<label>PATIENT NAME</label><br><br>
<inputtype="text"placeholder="enter the patient name"><br><br>
<label>AGE</label><br><br>
<inputtype="text"placeholder="enter the patient age"><br><br>
<label>
Gender :
</label><br>
<inputtype="radio"name="male"/> Male <br>
<inputtype="radio"name="female"/> Female <br>
<inputtype="radio"name="other"/> Other
<br>
<br>
<label>ROOM TYPE</label><br>
<inputtype="radio"name="AC"/> AC<br>
<inputtype="radio"name="NON_AC"/>NON-AC<br><br>
<label>WARD</label><br>
<select>
<option>General</option>
<option>single patient room</option>
<option>Double patient room</option>
<option>Triple patien room</option>
</select><br><br>
<label>Do you want food provided by the hospital</label><br>
<inputtype="radio"name="yes"/> YES <br>
<inputtype="radio"name="no"/> NO <br>
<label>Do you want special care taker</label><br>
<inputtype="radio"name="yes"/> YES <br>
<inputtype="radio"name="no"/> NO <br><br>
<ahref="E:\HOS\dialogue1.html"><inputtype="button"value="submit"></a>
</form>
</body>
When user clicks on service info, it will be rediected into service info
portal where user has to enter the details like name, age, gender of the
patient and should enter the room type, ward type, whether the patient
needs to be provided food and care taker based on patient’s interest.
SAVED SERVICES.html:
<!DOCTYPEhtml>
<style>
body{
162019727.jpg');
padding-top: 50px;
text-align: center;
}
</style>
<html>
<body>
<BR><BR><BR><BR><BR>
<dialogopen><H2STYLE="COLOR:BLUE">SELECTED SERVICES ARE GRANTED</H2></dialog>
</body>
</html>
When the user clicks on the submit button, it shows the message as
selected services are granted.
BILLDATA.html:
<!doctypehtml>
<html>
<head>
<style>
body{
margin:20px;
border: 5pxsolidblack;
background-image: url('https://encrypted-
tbn0.gstatic.com/images?q=tbn:ANd9GcSXStr9XdbZpjnY_oW9sM8pClFMJ6ZKHnUC1h_3-
M81XiNYoAJJomPW25fr50ugTZac7XU&usqp=CAU');
padding-top: 50px;
text-align: center;
}
h1{
text-align: center;
color:black;
font-size: 300%;
}
p{
color: darkred;
}
</style>
<script>
functionadd(){
varnum1,num2,num3,num4,num5,num6;
num1=Number(document.getElementById("first").value);
num2=Number(document.getElementById("second").value);
num3=Number(document.getElementById("third").value);
num4=Number(document.getElementById("fourth").value);
num5=Number(document.getElementById("fifth").value);
num6=num1+num2+num3+num4+num5 ;
document.getElementById("answer").value= num6;
}
</script>
</head>
<body>
<divalign ="center">
<h1>BILL</h1>
<label><h4>Enter the appiontment charges</h4></label>
<inputtype="number" id="first"><br>
<label><h4>Enter the operations charges<h4></label>
<inputtype="number" id="second"><br>
<label><h4>Enter the Medical charges<h4></label>
<inputtype="number" id="third"><br>
<label><h4>Enter the Service charges<h4></label>
<inputtype="number" id="fourth" ><br>
<label><h4>Any additional charges<h4></label>
<inputtype="number" id="fifth"><br>
<br><br>
<buttononclick="add()">Total</button><br>
<h3>Amount To Be Paid:<inputid="answer"></h3>
<p><b>NOTE:</b> if you have any questions regarding this invoice please
contact hospital management</p>
</div>
</body>
</html>
When user clicks on bill data, it shows to enter the amount of

appointment charges, operation charges, medical charges, service
charges, and any additional charges and when clicks on total , it shows
the entire amount to be paid by patient.
Logout.html:
On clicking logout button by user (receptionist), it will be redirected into

login page of our project.
CHAPTER 7
CONCLUSION
Healthcare is a field where information has to be maintained properly. This field
needs to create a user-friendly system, which guides users at all steps they need to
perform in it. The information provided by the users must be kept secured, as the
healthcare information is very much confidential. The prescriptions for a certain
patient are forwarded electronically to the pharmacy. This avoids the unnecessary
time taken by the patient to carry the prescription to the pharmacy.
Thus our healthcare is much secured providing authentication to the user.
Our project guides the user to the action they need to perform. Our project is user-
friendlier than all other e-healthcare systems with voice messages and blue tooth
enhancement. Our e-healthcare system currently focuses on the relationships between
patients, physicians and pharmacists. We plan to extend the system to other
healthcare facilities and professionals, such as laboratory technicians who perform
and report tests and analyses requested by physicians. We also plan to investigate
whether our Clinic and Pharmacy modules can be interfaced to applications supplied
by pharmaceutical companies that provide information on medications and dosages
and warn of interactions between medications. In addition, we plan to investigate
drug delivery devices, such as e-pillboxes, that prompt and monitor the regular and
timely consumption of medications.
CHAPTER 8
REFERENCES
8.1 Book References

1. A Distributed e-Healthcare System Based on the Service Oriented Architecture
Kart, F. Gengxin Miao Moser, L.E. Melliar-Smith, P.M.Dept of Elect: & Comput.
Eng., Univ. of California, Santa Barbara, CA;
2. Towards a flexible, process-oriented IT architecture for an integrated healthcare
network-Nicosia, Cyprus
3. A Service Oriented Architecture for a Health Research Data Network Rohan Baxter
and Ross Sparks and Uma Srinivasan and Mark Cameron and Laurent Lefort
4.Unconfined E-healthcare system using UMTS-WLAN H. Qu, Q. Cheng, and E.
Yaprak
5.Understanding and Classifying Requirements for Computer-Aided Healthcare
workflows Xiping Song Hwong, B. Matos, G. Rudorfer, A. Siemens Corp. Res.Inc.,
Princeton;
6. E-healthcare system design: a consumer preference approach Zhiping Walter and
Y. Alex Tung 78
8.2 Web References

1. www.webreference.com/programming/soa/
2. www.java.sun.com/developer/technicalArticles/WebServices/soa2/
3. www.research.ibm.com/journal/sj/444/niblett.html
4. www.sap.com/platform/soa/customers/index.epx
5.www.ieeexplore.ieee.org/iel5/4026873/4026874/04026976.pdf
tp=&isnumber=&arnumber=4026976
—THE END—

1 2 3 4 5 Merged

Uploaded by

Copyright:

Available Formats

1 2 3 4 5 Merged

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

1 2 3 4 5 Merged

Uploaded by

Copyright:

Available Formats

INTEGRATED HEALTH CARE

School of Computer Science and Engineering

Certified to be the bonafide record of the work done by

Submitted for the Final Assessment examination held on ________________

EXTERNAL EXAMINER INTERNAL EXAMINER

1.2 Document Conventions

1.3 Intended Audience and Reading Suggestions

1.4 Product Scope

1.5 Product Perspective

1.6 Product Functions

1.7 Operating Environment

1.8 Design and Implementation Constraints

- Patient Management: Registration, demographics, medical history, and visit records.

- Appointment Scheduling: Booking, rescheduling, and cancellation of appointments.

- Billing and Invoicing: Generation of bills, payment tracking, and invoicing.

- Patients shall be able to register and update their demographic information.

4. Billing and Invoicing

- Patients shall be able to view and pay bills online.

- Administrators shall have access to billing and invoicing reports.

- Reports shall be exportable in common formats such as PDF and Excel.

IHMS: Integrated Healthcare Management System

EHR: Electronic Health Records

2.3 DFD DIAGRAM

1st level DFD – Hospital Management System: -

2nd LEVEL DFD – LEVEL 2.0

3.2 Use Case Description

3.4 Sequence Diagram

3.7 Package Diagram

3.9 Deployment Diagram

4.1 USER INTERFACE DESIGN

4.5 INPUT & OUTPUT DESIGN

5.1 UNIT TESTING:

5.2 INTEGRATION TESTING:

5.3 WHITE BOX TESTING:

This is login page of our hospital management project where

On clicking patient details option, it will be redirected into patient

<inputtype="text"name="first_name"placeholder="Enter first name"required>

<inputtype="text"name="middle_name"placeholder="Enter middle name">

<inputtype="text"name="Last_name"placeholder="Enter last name"required>

<dialogopen><H2STYLE="COLOR:BLUE">SELECTED SERVICES ARE GRANTED</H2></dialog>

When user clicks on bill data, it shows to enter the amount of

On clicking logout button by user (receptionist), it will be redirected into

8.1 Book References

8.2 Web References

You might also like