The Great Mind Challenge 2011

PAPERLESS HOSPITAL SERVICE

Software Requirements Specification

VaagdeviEngineering College
Warangal 506005
Team Members
Awase Ahmed

08UK1A1234

K.Dayeshwar

08UK1A1203

B.Sandeep

08UK1A1214

B.Mounica

08UK1A1258

Project Guide
Mr.Murali Krishna
Department of Information Technology

Vaagdevi

Table Contents

1.0 Introduction
1.1
Purpose
..
1.2
Scope

1.3
Definitions,
Acronyms
and
Abbreviations
.
1.4
References

..
1.5
Technologies
to
be
used
.
1.6
Overview

..

2.0

Overall Description

2.1
Product
Perspective
.
2.3 Software
Interface
.
2.3
Hardware
Interface
.
2.4

Product
Function
..

2.5 User
Characteristics
..
2.6 Constraints
..
2.7

Architecture
Design
..

2.8

Use
Case
Model
Description
..

2.9

Class
Diagram


2.10

Sequence

Diagram

.
2.11
Database
Design

2.11.1 ER
Diagram

.
2.11.2 Schema
..
2.12 Assumptions
and
Dependencies

3.0

Specific Requirements

3.1
Use
Case
Reports
.
3.2
Supplementary
Requirements

1.0 Introduction
1.1 Purpose
Paperless Hospital Service (Healthcare Domain)is a web application.
Objective of this project is to leverage paperless hospital service where
patient need not do any paper-work while getting admitted to the hospital by
providing seamless application that will handle the thousands of patient
information and provide efficient healthcare service. It is to align with SMART
PLANET theme of IBM.

1.2 Scope
Scope of the project includes:
1. Patient/Relative
2. Admitting Clerk
3. Department Admin
4. Doctor/Nurse
5. Billing Department
6. Healthcare Insurance Providers (External Actor)

Patient will go to hospital and get admitted by giving their information

to the Admitting Clerk. If Patient is in serious state, relative will help in
giving information about the patient to the Admitting Clerk.
If the incoming patient is New, then Admitting Clerk will create a new
record in Web Portal and store the patient information by collecting all
necessary details and also about health history. And will provide Patient
ID which will be sent via sms to patients mobile number.
Admitting Clerk will assign the In-coming Patient Record to the
Department Admin and direct the Patient to meet the Department
Admin.
Department Admin will assign the Patient to the respective Department
like ENT, ICU, Surgery, etc and also will assign Doctors/Nurses who will
be responsible to treat the Patient
Doctor will get patient information by querying on Patient ID and will
conduct series of tests and will update their test report along with
comments in the Application
Billing Department will calculate the expense and will be responsible to
verify if Patient has Insurance Policy, if so then they will open a secure
session to charge the cost to Insurance providers.

1.3

If Patient doesnt have Insurance Policy, then he must pay either in

cash or credit/debit cards
Insurance Providers will verify the claim and will confirm whether the
Insurance ID and policy coverage is valid or not
Following operations are exposed in Web service:
a. Create Patient Record
b. Modify Patient Record
c. View Patient Record
d. Delete a Patient Record
e. Bill to Insurance Providers
f. Bill to Patient

Definitions, Acronyms, and Abbreviations:

PHS (Paperless Hospital Service):

It is an offline application
HTML (Hyper Text Markup Language):
It is used to create static web pages.
JSP (Java Server Pages):
It is used to create dynamic web content.
J2EE (Java 2 Enterprise Edition):
It is a programming platform, belonging to the Java platform, which is
used for developing and running distributed java applications.
WASCE (Web Sphere Application Server Community Edition):
It is an application server that runs and supports the J2EE and the web
service applications.
WSAD (Web Sphere Studio Application Developer):
It is a designer toolkit which is designed to develop more complex
projects by providing a complete dynamic web service.

DB2 (IBM Database 2):

It is a database management system that provides a flexible and

efficient database platform to raise a strong "on demand" business
applications.
HTTP (Hyper Text Transfer Protocol):
It is a transaction oriented client/ server protocol between a web
browser and a web server.
UML (Unified Modeling Language):
Itis a standard language for writing software blueprints. The UML may
be used to visualize, specify, construct and document
XML (Extensible Markup Language):
It is a markup language that was designed to transport and store data.
AJAX(Asynchronous Java Script and XML):
It is a technique used in java script to create dynamic web pages.
Web 2.0:
It is commonly associated with web applications which facilitate
interactive information sharing, interoperability, user-centered design and
collaboration on the World Wide Web.

1.4

References:

Object Oriented Modeling and Design with UML-Michael Blaha, James

Rambaugh.
Software Engineering, Seventh Edition, Ian Sommerville.
IBM Red Books.
IBM TGMC Sample Synopsis.
IBM www.ibm.in/developerworks .
Java - www.sun.com
www.w3schools.com
Wikipedia - www.wikipedia.com

Database Management Systems Navathe.

Complete Reference - J2EE Keogh.

1.5

Technologies to be used:

Application Architecture:

J2EE :( Servlet , JSP , Java Beans)

Java Platform, Enterprise Edition or Java EE is a widely used

platform for server programming in the Java programming language. The
Java platform (Enterprise Edition) differs from the Java Standard Edition
Platform (Java SE) in that it adds libraries which provide functionality to
deploy fault-tolerant, distributed, multi-tier Java software, based largely
on modular components running on an application server.

JAVA:
Java is an object-oriented programming language developed by Sun
Microsystems a company best known for its high end UNIX workstations.
Java language was designed to be small, simple, and portable across
platforms, operating systems, both at the source and at the binary level,
which means that Java programs (applet and application) can run on any
machine that has the Java virtual machine (JVM) installed.

WASCE :( Web sphere Application Server Community Edition):

Web server.
Web Sphere Application Server Community Edition (from now
on WASCE) is a free, certified Java EE 5 server for building and managing
Java applications. It is IBM's supported distribution of Apache Geronimo
that uses Tomcat for servlet container and Axis 2 for web services. Over
15 WASCE developers are committers in the Apache Geronimo project.
DB2:IBM Database.
DB2 Database is the database management system that delivers a
flexible and cost effective database platform to build robust on demand
business applications and supports the J2EE and web services standards.

Eclipse IDE: Development tool.

Eclipse is a multi-language software development environment
comprising an integrated development environment (IDE) and an
extensible plug-in system. It is written mostly in Java and can be used to

develop applications in Java and, by means of various plug-INS, other

programming languages

1.6 Overview:
The SRS will include two sections, namely:
Overall Description: This section will describe major components of the
system, interconnections, and external interfaces.
Specific Requirements: This section will describe thefunctions of actors,
their roles in the system and the constraints faced by the system.
Existing System:
Registration for patients
Filling of Application forum
Paper-based system
Drawbacks:
No effective interaction
Long service times
Patients are being repeatedly asked same category questions
A doctor struggling to read handwritten notes
Reluctance to share medical knowledge
Patients are being kept waiting in ward
No use of IT anywhere
Proposed System:
Paperless hospital service (Healthcare Domain)
Secure access of confidential data (users details). SSL can be used.
24 X 7 availability
Better component design to get better performance at peak time
Flexible service based architecture will be highly desirable for future
extension
Our Plan:
Registration for users.
Online maintenance of health record.
User friendliness.
Accessible to more number of users.
Development of the Electronic Patient Record.
Aweb portal will provide continuous improvement of economic
efficiency and the delivery of patient care.

Interface among different departments like Administrative, Patient

Billing and Accounts departments.
Online prescription from doctor.
Online appointment facility.
Patient reviews and ratings for doctor.
IT-based not paper-bas.

2.0 Overall Description:

2.1 Product Perspective:
This Paperless Hospital System is a self-contained system that manages
activities of the hospital as providing appointments, operations scheduling,
personnel management and administrative issues. The architecture of
product function is shown below:

Advantages of using pureXML:

Paperless Hospital rules will change and so do the return forms. Every
year the forms need to accommodate new change and still be able to
process them effectively. This is where the XML design will make it
flexible and the developer will be easily able to handle this change in
design with minimum impact on the application. The database design
does not change.
Because of the use of XForms which generate XML data as input, its
easy to consume (gather) all user information in a single XML
document and store it as a single entity without breaking it up into
pieces as done is case of relational database.
Since the data will be stored in a single XML document, its easy to
fetch it using a simple XQuery without any complex joins.

Since the data is stored as XML, it is vey easy to construct SOAP

messages from this XML content as no relational to XML transformation
is required.
Use of XSLT to report data in multiple format is now possible because
of the XML data model

Pictorial

Representation:

JSP/J2EE App

IBM Lotus Forms

App

JAXP & SAX

Java App

Web Service
Pure
XML is
used

JAXP & SAX

DB2

Fig 2.2: Pictorial Representation of Using PureXML

2.2 Software Interface:

Front End (Client)

Web Browser, Operating System (any)
Web Server
WASCE, Operating System (any)
Data Base Server

DB2, Operating System (any)

Back End (Development End)
Technologies to be used:
UML, J2EE, XML, e-Forms, XForms/Java/C,C++, AJAX, Web
2.0, Web-services, SOA
Tools to be Used:
Lotus Form Designer/Eclipse/RAD
WebSphere Portal/ WAS, Webservices/SOA
DB2 Express

2.3 Hardware Interface:

Minimum Requirements:
Client Side

Internet Explorer 6

Processor

RAM

Disk Space

Intel Pentium III or

AMD - 800 MHz

128 MB

100 MB

RAM

Disk Space

1 GB

3.5 GB

Server Side
Processor
Eclipse
DB2 - 9.5

Intel Pentium III or

AMD - 800 MHz

500 MB
256 MB

(Excluding Data
Size)

Processor

RAM

Disk Space

All Intel or AMD - 1

GHZ

256 MB

100 MB

RAM

Disk Space

Recommended Requirements:
Client Side

Internet Explorer 6

Server Side
Processor

Eclipse

DB2 - 9.5

2 GB
All Intel or AMD - 2
GHZ

3.5 GB
500 MB

512 MB

(Excluding Data
Size)

2.4Product Function:
1. Patient will go to hospital and get admitted by giving their information
to the Admitting Clerk. If Patient is in serious state, relative will help in
giving information about the patient to the Admitting Clerk.
2. If the incoming patient is New, then Admitting Clerk will create a new
record in Web Portal and store the patient information by collecting all
necessary details and also about health history. And will provide
Patient ID which will be sent via sms to patients mobile number.
3. Admitting Clerk will assign the In-coming Patient Record to the
Department Admin and direct the Patient to meet the Department
Admin.
4. Department Admin will assign the Patient to the respective
Department like ENT, ICU, Surgery, etc and also will assign
Doctors/Nurses who will be responsible to treat the Patient
5. Doctor will get patient information by querying on Patient ID and will
conduct series of tests and will update their test report along with
comments in the Application
6. Billing Department will calculate the expense and will be responsible
to verify if Patient has Insurance Policy, if so then they will open a
secure session to charge the cost to Insurance providers.
7. If Patient doesnt have Insurance Policy, then he must pay either in
cash or credit/debit cards
8. Insurance Providers will verify the claim and will confirm whether the
Insurance ID and policy coverage is valid or not
9. Following operations are exposed in Web service:
a. Create Patient Record
b. Modify Patient Record
c. View Patient Record
d. Delete a Patient Record
e. Bill to Insurance Providers
f. Bill to Patient
.

2.5

User Characteristics:

Following operations are exposed in Web service:

2.6

Create Patient Record

Modify Patient Record
View Patient Record
Delete a Patient Record
Bill to Insurance Providers
Bill to Patient

Constraints:

GUI is only in English.

Login and password is used for the identification of users.
Only registered users will be authorized to use the services.
Limited to HTTP/HTTPS.
This system is working for single server.

2.7 Architecture Design:

2.8 Use Case Diagram :

Patient/Relative:

Patients/Relative can search for doctor and make online appointments. They
also can view their health record, labreports, doctors prescription, medical
expenses and pay bill through cash or credit/debit cards. They can view as
well as update their profile.

Admitting Clerk:
If the incoming patient is New, then Admitting Clerk will create a new record
in Web Portal and store the patient information by collecting all necessary
details and also about health history. And will provide Patient ID which will be
sent via sms to patients mobile number. Admitting Clerk will assign the Incoming Patient Record to the Department Admin and direct the Patient to
meet the Department Admin. Admitting Clerk can view as well as update
their profile.

Department Admin:
Department Admin will assign the Patient to the respective Department like
ENT, ICU, Surgery, etc and also will assign Doctors/Nurses who will be
responsible to treat the Patient. Department Admin can view as well as
update their profile.

Doctor/Nurse:
Doctor will get patient information by querying on Patient ID and will conduct

series of tests and will update their test report along with comments in the
Application. Doctors can give appointments, prescription and can update
and view patients health record. They can also view as well as update their
profile.

Billing Department:
Billing Department will calculate the expense and will be responsible to verify
if Patient has Insurance Policy, if so then they will open a secure session to
charge the cost to Insurance providers. If Patient doesnt have Insurance
Policy, then he must pay either in cash or credit/debit cards. They can also
view as well as update their profile.

Insurance Providers:
Insurance Providers are the external actors. They will verify the claim and will
confirm whether the Insurance ID and policy coverage is valid or not.

Administrator:
Administrator has the authority to add/delete users, grant permission to
users and view logs. He is responsible for creating Departments, assigning
staff to departments, assigning system rights to staff and maintenance of
system Database. He can also view as well as update their profile.

2.9 Class Diagram:

2.10 Sequence Diagrams:

2.10.1 Sequence Diagram for Login System:

Fig:2.10.1 Sequence diagram for login system

2.10.2 Sequence Diagram for Patient:

Patient

PHS

DataBase

login
check authentication
validate information
authorized user
display patient page
if authorized
else error

view/update profile
get details of patient

search/update details

display his/her latest profile

get profile
search/choose doctor and take appointment
send queries
search
display list of doctors and free appointments
get doctors list and appointment
view reports,take prescription and paybill
send queries
search and update bill
display receipt
get receipt

Fig 2.10.2: Sequence Diagram for Patient

2.10.3 Sequence Diagram for Admitting Clerk:

Admitting Clerk

PHS

DataBase

login
check authentication
validate information
authorized user
if authorixed
else error

display admitting clerk page

view/update profile
get profile
search/update profile
display profile
get profile
register patient or create patient record
send registration request
process request
display patient registration form
get patient registration form
fill registration form
send new patient details
save details
display registration successful
search/view/update patient record
send queries

search/update patient record

display updated patient record
get requested patient record

Fig 2.10.3: Sequence Diagram for Admitting Clerk:

2.10.4 Sequence Diagram for Department Admin:

Department
Admin

PHS

DataBAse

login
check authentication
validate user
authorized user
if authorized
else error

display department admin page

view/update profile
send queries

search/update profile
display his/her latest profile
get updated profile
search/view patient record or doctor/nurse details
send request
search
display patient record or doctor/nurse details
get patient record or doctor/nurse details
assign patient to respective department
send queries
save information
display successful
assign doctors/nurses to treat patient
send ionfromation
save information
display successful

Fig 2.10.4: Sequence Diagram for Department Admin

2.10.5 Sequence Diagram for Doctor:

Doctor

PHS

DataBase

login
check authentication
validate information
authorized user
display doctor page
if authorized
else error

view/update profile
send details

search/update profile
display his/her updated profile
get latest profile
view/approve appointments
send qureies
search/save appointments
display list of appointments
get appointment list

search patient information

send request
search
display patient history
get history of patient
treat patient and provide prescription
send infromation
save information
display successful
view/conduct tests
send queries
search/update test reports
display test reports
get test reports

Fig 2.10.5: Sequence Diagram for Doctor

2.11.ER Diagram:

Doct
or

ACC
section

Hospital
Users

Reco
rds

Nurs
e

Name
Bed
no.

Clerk

Age
Patient
info

Addres
s

Sex

Fees
deposited

Tests/Treatme
nts
Diagnosis
Report

Doctor
Incharge
Date of
admission
Can
see/mod
ify

Doctor

Nam
e
Doc
ID

Nurse

Nam
e

Nurse
ID

Billing
Dept.

Nam
e

ACC
ID

Fig.2.11 ER DIAGRAM OF PAPERLESS HOSPITAL

SYSTEM

2.12Assumptions and Dependencies:

This application is to be used in a server so that the hospitals, admin and
users can get the information. Every user should have their user id and
password. Administrator should have all the rights to remove or add
anything. A user is expected to have internet connectivity to use this
application. It is assumed that one hundred IBM compatible computers will
be available before the system is installed and tested. It is assumed that the
Hospital will have enough trained staff to take care of the system.

3.0 Specific Requirements:

3.1 Use Case Reports:
3.1.1 Use Case Report for Administrator:

Fig 3.1: Use Case Diagram for Administrator

Use Case
Login
Assign
System
Rights to Staf
Authenticate
Users
View Profile
Update Profile
Search
View Reports
View Logs

Description
Administrator need to login first to perform any action
Admin assigns privileges to the hospital staff which
includes doctors, nurses, clerks, etc.
Admin is responsible to authenticate users.
Note: Unauthenticated users have no access to the
website
Admin has his/her own profile containing personal and
professional details.
Admin has the option to update his/her own profile.
Admin can search for a particular item in website by
entering the keyword.
Admin can view reports of the patients.
Admin have an option to view all the logs of different

Delete User
Create
Department
Assign staf to
Department
Maintain System
Database

users
Admin have authority to delete any user provided by
an option Delete.
Admin can also create any department like ENT, ICU,
Surgery, etc
Admin can assign staff to respective departments
Admin is responsible to maintain system database

3.1.2 Use Case Report for Patient/Relative:

Fig 3.2: Use Case Diagram for Patient/Relative

Use Case
Description
Register
The Patient need to be registered initially
Registered
By New patients gets registered by admitting clerk
Admitting Clerk
SMS Patient ID to Patient ID will be provided via SMS when patient gets
Patients Mobile
registered
Login
The Patient need to login first to perform any action
View Profile
Every registered patient has his/her own profile
containing personal and professional details.
Update Profile
The Patient has the option to update his/her own
profile.
Select Doctor
The patient can select doctor based on various

criteria.
The patient can request for an appointment to a
particular doctor.
Cancel
Patient has an option to cancel his/her appointment
Appointment
with the doctor
Take Prescription
Patient takes prescription provided by doctor.
Search
The patient can search for a particular item in
website by entering the keyword.
View Reports
The Patient can view his/her reports provided by
doctor.
Pay Bill
The Patient can pay his/her bill.
Cash
or The Patient has an option to pay the bill via cash or
Credit/Debit cards
credit/debit cards
Take Appointment

3.1.3 Use Case Report for Admitting Clerk:

Fig 3.3: Use Case Diagram for Admitting Clerk

Use Case
Register
Approval
Administrator
Login

Description
Admitting Clerk need to be registered initially
from Registration of Admitting clerk must be approved
by Administrator
Admitting Clerk have to login first to perform any
action

Register Patient
SMS Patient ID
patient mobile
View Profile

Admitting Clerk can register new patients

to On registration, an SMS of Patient ID will be sent
to patient mobile
Every registered Admitting clerk has his/her own
profile containing personal and professional
details.
Update Profile
Admitting Clerk has the option to update his/her
own profile.
Create Patient Record Admitting Clerk have an option to create patient
record
View Patient Record
Admitting Clerk can view patient records
Update Patient Record Admitting Clerk can also update patient record
Search
Admitting Clerk can search for a particular item in
website by entering the keyword.
View Reports
Admitting Clerk can also view patients reports
Assign Patient Record Admitting clerk assigns in-coming patient record
to Department Admin to Department Admin

3.1.4 Use Case Report for Department Admin:

Fig 3.4: Use Case Diagram for Department Admin:

Use Case
Description
Register
Department Admin need to be registered initially
Approval from
Registration of Department Admin must be
Administrator
approved by Administrator
Login
Department Admin have to login first to perform
any action
Search
Department Admin can search for a particular item

View Profile
Update Profile
View Patient Details
Assign Patient to
respective
Department
Select Department
Assign Doctor/Nurse
Search Doctor/Nurse

in website by entering the keyword.

Every registered Department Admin has his/her
own profile containing personal and professional
details.
Department Admin has the option to update his/her
own profile.
Department Admin can view patient details
registered
Department Admin have to assign patient to
respective department
Department Admin can select department
Department Admin assigns doctor or nurse to
patients
Department Admin can search for a doctor/nurse

3.1.5 Use Case Report for Doctor/Nurse:

Fig 3.5 Use Case Diagram for Doctor/Nurse

Use Case
Register
Approval from
Administrator
Login
View Profile
Update Profile
Get Patient
Information
View
Appointments
Search Patient
View Patient
History
Approve
Appointments
Treat Patient
Provide
Prescription
Conduct Tests
View Test
Reports
Update Test
Reports
Comment

Description
Doctor/Nurse need to be registered initially
Registration of Doctor/Nurse must be approved by
Administrator
Doctor/Nurse have to login first to perform any action
Every registered Doctor/Nurse has his/her own profile
containing personal and professional details.
Doctor/Nurse has the option to update his/her own
profile.
Doctor/Nurse can get patient information by querying
patient ID
Doctor/Nurse can view the appointments by the
patients
Doctor/Nurse can search for a particular patient in
website by entering the patient ID
Doctor/Nurse has an option to view patients history
Doctor/Nurse
patients
Doctor/Nurse
Doctor/Nurse
patients
Doctor/Nurse
Doctor/Nurse
reports
Doctor/Nurse

can approve the appointments for

can treat patients
has an option to provide prescription for
can conduct series of tests for patients
also have an option to view the test
can update test reports

Doctor/Nurse ahs an option to comment in the

application

3.1.6 Use Case Report for Billing Department:

Fig 3.6: Use Case Diagram for Billing Department

Use Case
Register
Approval
from
Administrator
Login
View Profile
Update
Profile
Calculate
Expense

Change Entry
View Patients
Insurance
Policy
Open Secure
Session
Bill to

Description
Billing Departmentneed to be registered initially
Registration of Billing Departmentmust be approved by
Administrator
Billing Departmenthave to login first to perform any action
Every registered Billing Departmenthas his/her own profile
containing personal and professional details.
Billing Departmenthas the option to update his/her own
profile.
Billing Department will calculate the expense and will be
responsible to verify if Patient has Insurance Policy, if so
then they will open a secure session to charge the cost to
Insurance providers.
If Patient doesnt have Insurance Policy, then he must pay
either in cash or credit/debit cards
Billing Department will change the entry in the bills
Billing Departmentwill be responsible to verify if Patient has
Insurance Policy or not
If Patient has Insurance Policy, then Billing Department will
open a secure session
Billing Department charge the cost to Insurance providers

Insurance
Provider
Bill to Patient
Payment
Process
Cash or
Credit/Debit
Cards

for patients with valid Insurance Policy

Billing Department provides bill to patient if patient does
not have valid Insurance Policy
Billing Department have an option to select payment
process
Billing Department accepts payment via cash or
credit/debit cards

3.17Activity diagram: