Patient Billing Software Version 1.

0
Software Requirements Specification 28th Feb 2011
The Killers

The Killers

Patient Billing Software

Software Requirements Specification

Version 1.0

Team Guide:( Faculty Guide’s Name ):- Sakshi Vijay

Members:(Team members name) Member1:- Satyam Vijay

Member2:-Killer Satyam

College Name: JSS Academy Of Technical Education, NOIDA (JSSATEN).

Department: -Computer Science and Engineering

State:- Uttar Pradesh (INDIA)

The Killers / JSSATEN Page 1

The Killers / JSSATEN Page 2
Patient Billing Software Version 1.0
Software Requirements Specification 28th Feb 2011
The Killers

Revision History

Date Version Description Author

28-2-11 1.0 Synopsis The Killers

The Killers / JSSATEN Page 3

 Patient Billing Software Version 1.0
Software Requirements Specification 28th Feb 2011
The Killers

Table of Contents

Description Page No.

1.0 Introduction 5

1.1 Purpose 5
1.2 Scope
5-6
1.3 Definition, Acronyms, and Abbreviations
6
1.4 References
7
1.5 Technologies to be used
8
1.6 Overview

2.0 Overall Description

2.1 Product Perspective 8

2.2 Software Interface 8-9

2.3 Hardware Interface 10

2.4 Product Function 10

2.5 User Characteristics 11

2.6 Constraints 11

2.7 Architecture Design 11

2.8 Use Case Model Description 11-12

The Killers / JSSATEN Page 4

 Patient Billing Software Version 1.0
Software Requirements Specification 28thFeb2011
The Killers

2.9 Class Diagram ........................................................................ 12

2.10 Database Design .................................................................... 12

2.11.1 ER Diagram ............................................................... 13

2.11.2 Schema ...................................................................... 13

2.12 Assumptions and Dependencies 13

3.0 Specific Requirements

3.1 Use Case Reports 14

3.2 Supplementary Requirements 14

The Killers / JSSATEN Page 5

Patient Billing Software Version 1.0

Patient Billing Software Version 1.0

Software Requirements Specification 28thFeb2011
The Killers

Software Requirements Specification

1.0 Introduction:

1.1 Purpose:

To make a software for any hospital which enables the employees to calculate the total payment to be
made by any patient availing the services provided by the hospital system. Also, the software includes the
details of all the employees of the hospital and the patients and the resources of the hospital.

1.2 Scope: The Scope of the Patient Billing Software includes:

This software is applicable for any hospital or a private medical firm wanting to keep track of its
infrastructure and the total billing of the patients treated. Also, total record of the assets of the hospital are
taken care of.

1.3 Definitions, Acronyms, and Abbreviations:

• 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.

• Apache TOMCAT 6.0 : It is an application server that runs and supports the J2EE and the

web service applications.

• MySQL : 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.

The Killers / JSSATEN Page 5

Patient Billing Software Version 1.0

Patient Billing Software Version 1.0

Software Requirements Specification 28thFeb2011
The Killers

• 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.

• NetBeans 6.9.1 and JDK 1.6: It is the IDE(Integrated Development Environment) provided

by Sun Microsystems for the development of java applications which include both desktop

and web applications.

1.4
References:

The references for the project are taken from the following sources:

 HTML-The Complete Reference-II Edition.

 JavaScript & Ajax For Dummies.

 MySQL Bible- Steve Suehring.

 J2EE- The Complete Reference-Jim Keogh.

 Java Servlet Programming – J .Hunter.

 www.google.com

The Killers / JSSATEN Page 6

Patient Billing Software Version 1.0

Patient Billing Software Version 1.0

Software Requirements Specification 28thFeb2011
The Killers

1.5 Technologies to be used:

The technologies used in the project are as follows:

• J2EE: (Servlet, JSP, JAXP, Java Beans) Application

architecture.

• JAVA: Application architecture.

• Apache TOMCAT 6.0: Web Server.

• MySQL: Database.

• Ajax: Asynchronous Java Script and XML.

• XML: Extension Markup Language.

Web 2.0: RSS Feed 2.0.

• Localization: 2 Languages - Hindi and English.

• HTML : Used in the creation of static web pages.

The Killers / JSSATEN Page 7

Patient Billing Software Version 1.0

Patient Billing Software Version 1.0

Software Requirements Specification 28thFeb2011
The Killers

1.6 Overview: The SRS includes two sections, namely:

-I- Overall Description: This section describes the major

components of the system, interconnections, and external
interfaces.

-I- SpecificRequirements: This section describes the functions of

actors, their roles in the system and the constraints faced by the
system.

2.0 Overall Description:

2.1 Product Perspective:
The product describes the relationship between the employees of the Hospital
System and the patients of the Hospital . The employees which include the
support staff, the administrator, the doctors, the managers and every other
resource associated to the Hospital, whereas the patients are the entities
availing the services provided by the Hospital.

The software acts as an overall interface between the various actors, the
product also as the name suggests PATIENT BILLING SOFTWARE performs
its basic operation of calculating the total bill to be paid by each patient after
the treatment operation.

2.2 Software Interface:

-I- Front End Client:

The front end client gets to view the interface in which there are
following properties:

➢ The first page gives the information about the hospital for which
the software is used, basically the USER interface.
➢ The employees of the organization through the first page can
login to the system for any advancements with their valid user
id’s and passwords provided to them by the administrator.
➢ Then the authenticated user whether the user is a staff member
recruited for specific billing purpose or a doctor of the

The Killers / JSSATEN Page 8

Patient Billing Software Version 1.0

Organization can update his/her information or make the bills for

the patients.

➢ The basic software requirement for the client side is a system

with a WINDOWS OS installed on it with a compatible Web
Browser such as Internet Explorer 8, Firefox 3.6 or Google
Chrome.
➢ The basic software requirement for the server side needs the
installation of the following technologies:
 Windows operating system (XP or above).
 NetBeans 6.9.1 and JDK 1.6.
 Apache Tomcat 6.0.
 MySQL Server 5.5.8.
 MySQL-connector-java-5.1.14(JDBC).
 Web Browser :- Internet Explorer 8, Firefox 3.6 or Google
Chrome.

-I- Web Server (Not Applicable for End User):

The web server used is Apache Tomcat 6.0 run on a windows operating
system but the client or the end user does not need the server as the
software will be needed to be hosted on the domain by administrator and
the user only has to open the related URL.

-I- Data Base Server (Not Applicable For The End User):

The Database Server is MySQL server 5.5.8 which needs to be installed

on the server side.
4- Back End:

The Back End is the MySQL server 5.5.8 which is used to store all the
information provided by the actors. The following information is stored in
the database:
✔ The information of the employees of the organization.
✔ The information of the patients of the hospital.
✔ The information of the assets of the organization such as the
number of beds free or occupied, the wards free or occupied by
patients etc.

The Back End also uses MySQL-connector-java-5.1.14(JDBC) so as to

make a connection between the java application and the MySQL server.

The Killers / JSSATEN Page 9

Patient Billing Software Version 1.0
Software Requirements Specification 28thFeb2011
The Killers

2.3 Hardware Interface:

4- Client Side:
The hardware interface on the client side includes the following
characteristics:
• A system with a minimum of 512 MB of RAM (Depending on the
Operating System).
• The processor can be Intel P4 or above.
• 80 GB or above secondary storage.
• The product requires only a compatible web browser for working
since no installation is required for end user.
4- Server Side:

The Server Side hardware interface includes the following requirement

characteristics:
• A server with memory capabilities to handle the size of the
organization. The memory storage capability of the web server
depends on the size of the organization.
• The System should have necessary specifications to meet the
traffic needs of the organization.
• The domain hosting specifications would be required.

2.4 Product Functions:

The various functions which the product will specifically perform are:

○ Login to the system through the first page of the application.

○ Enter / edit the organization code and address.
○ Enter the ward number for the patient either in the general ward
or the ICU.
○ Settle all bills pending to be paid by a patient before the
patient’s discharge.
○ Keep a track of all beds occupied / free in both the ward and the
ICU.
○ Keep a track of all transfers of patients from the general ward to
the ICU and vice versa.
○ View information of all patients details, their admit time and the
amount to be paid based on the treatment given and the ward
selected.
○ Update the table fields (patient details, the amount to be paid /
any balance remaining, the ward number, the bed number, the
registration number, case number, etc.) as soon as a new
patient.
○ Help-pages of the application in the form of Q&A.

Pag
e 10
2.5 User Characteristics:

The characteristics which the user needs to possess to use the product are:

➢ The user should be acquainted with the knowledge of using the

internet so that he/she can access the internet.
➢ The user must be familiar with the different browsers used.
➢ Users must know the level of interaction with the software.
➢ Users must know how to operate on the corresponding Operating
System.
➢ Users must know to handle Excel sheets or PDF format files.
➢ User must be aware of the various departments of the organization
and the task that each department performs.

2.6 Constraints:

The constraints on the product are:

This is only a kind of billing software which keeps the billing records for
a hospital and not a total storage schema.
The software is only a local software system.
The product does not take the interface between the customer and the
employees into consideration i.e the interaction between the patients
and the employees is out of its domain.
The interaction of this software is only with two categories:
1. The Employees of the organization.
2. The Administrators.

2.7 Architecture Design:

The architectural design of the software in the database is:

Database ‘Hospital’ is the major database for the system. The various
components of the Database include:
➢ Table ‘Departments’ includes all the various departments that the
hospital has.
➢ Table ‘Organization’ includes the details of all the characteristics
of the organization.
➢ Table ‘Users’ includes all the users and their details which is
updated and maintained by the system administrator.
➢ Table ‘GenWards’ includes the various number of general wards
for the patients and the characteristics of each ward.
➢ Table ‘ICUWards’ includes the various number of ICU wards for
the patients and the characteristics of each ward.
➢ Table ‘Patients’ carrying the information regarding the patients
treated by the hospital.
➢ Table ‘Services’ gives the data regarding the services provided
by the hospital.

2.8 Use Case Diagram :

The use case diagram for the product will contain following elements:
Page 11

2.9 Class Diagram:

The class diagram will consist of the following elements of the class:
➢ The classes will be formed according to the database schema.
➢ Each of the classes will represent the amount of information to be
stored with respect to the product.

2.10 Sequence Diagrams:

2.10.1 Database Design:
The design of the database as explained earlier is as follows:
Database ‘Hospital’ is the major database for the system. The various
components of the Database include:
➢ Table ‘Departments’ includes all the various departments that the
hospital has.
➢ Table ‘Organization’ includes the details of all the characteristics
of the organization.
➢ Table ‘Users’ includes all the users and their details which is
updated and maintained by the system administrator.
➢ Table ‘GenWards’ includes the various number of general wards
for the patients and the characteristics of each ward.
➢ Table ‘ICUWards’ includes the various number of ICU wards for
the patients and the characteristics of each ward.
 Pag
e12
➢ Table ‘Patients’ carrying the information regarding the patients
treated by the hospital.
➢ Table ‘Services’ gives the data regarding the services provided
by the hospital.

2.10.2 ER Diagram:
The ER Diagram for the various relationships will be as follows:

2.11 Assumptions and Dependencies:

The assumptions made are:
✔ The administrator is equipped with all the technical details.
✔ The administrator knows how to configure the software.
✔ The end user or the employees of the organization know the technical
details for running and using the software.
✔ The software is run on the correct set of requirements.
The dependencies of the software are:
✔ The software is dependent on the end user.
✔ The software since it runs on a single domain, it makes it dependent on
the server hosting it and the machne on which the various softwares are
installed to run the product.
 Pag
e 13

3. Specific Requirements:

3.1 Use Case Reports:

The use-case diagrams shown earlier represents the way in which each of the
different actors are related together by the software. The various points about
the diagram are:

• The main spearhead is the administrator who is the controller of the

software.
• The end users are the staff members mainly, who will be responsible
for producing the bills for the hospital.
• The next end users are the doctors who are a part of the organization
and are responsible for the treatment of the patients.
• The managers though specifically not an actor but does avail the
resources the software provides in their assessment.
• The PATIENTS are actually NOT the actors but they are the main
resources on which the software works.

3.2 Supplementary Requirements:

The other supplementary requirements needed would be:

• An alternative server in case the man server crashes.
• There must be adequate security measures taken to secure the billing
procedure and keep the data of users secure. The various security
measures taken can be:

 The use of secure web protocol such as SSL(Secure Socket

Layer) to keep data secure.
 The use of firewall to filter various packets of data.
 The use of routers to route the network path.
 Proper patches need to be applied for the corresponding
Operating System.
• The provision of the establishment of the proper network so that the
availability to end users remains consistent.
• The facilities can be provided so that employees of the organization can
also use the software from other places.
The Killers/JSSATEN. Page 14