Paperless Hospital Service

Paperless Hospital Management System

Software Requirements Specification

16-May-2013

Daya Deepak-201204100110093 Gadhiya Amit-201204100110102 Morya Aakash-201204100110117 Software Engineering

Prepared for

SHRIMAD RAJCHANDRA INSTITUTE OF MANAGEMENT AND COMPUTER APPLICATION

Paperless Hospital Service

Revision History

Date <date>

Description <Version 1>

Author <Your Name>

Comments <First Revision>

Document Approval The following Software Requirements Specification has been accepted and approved by the following: Signature Printed Name <Your Name> Title Lead Software Eng. Date

Paperless Hospital Service

Table of Contents Revision History ...........................................................................................................2 1. Introduction.............................................................................................................4 1.1 1.2 1.3 1.4 2.1 2.2 2.3 2.4 2.5 Purpose ..............................................................................................................4 Scope .................................................................................................................4 Definitions, Acronyms, and Abbreviations ..........................................................5 References ..........................................................................................................6 Product Perspective ............................................................................................7 Product Functions ..............................................................................................7 User Characteristics ...........................................................................................7 General Constraints ...........................................................................................7 Assumptions and Dependencies .........................................................................8

2. General Description .................................................................................................7

3. Specific Requirements..............................................................................................9 3.1 External Interface Requirements ........................................................................9 3.1.1 User Interfaces .............................................................................................9 3.2 Functional Requirements ...................................................................................9 3.5 Non-Functional Requirements ..........................................................................10 3.5.1 Performance ............................................................................................... 10 3.7 Design Constraints ........................................................................................... 11 4. Analysis Models .....................................................................................................12 4.1 Activity Diagram ............................................................................................... 13 4.2 Use Case Diagrams .......................................................................................... 18 4.3 Sequence Diagram...24 4.4 Database Design...27

Paperless Hospital Service

1. Introduction
The Paperless Hospital management system can be proven best for upcoming future requirements. The main key point is to reduce the consumption of the paper and hence moving a step forward in saving our environment and making the process digital. In this system, we can keep track of the Patient for a longer period without losing the data. This can increase the searching of the data after a longer time too. In addition, we are converting all the hard documents to the digital documents such as the forms. In addition, if the hospital is spread all over the world then it may be easy to merge the details and can be accessed from all over the world in few seconds. In addition, if any new patients are coming then we can keep their past health records and hence we can easily identify or analysis the health history of that patient. This can increase the availability of the hospital service for a longer time. In addition, a patient can take advice from any particular doctor by the means of inquiry modules present in the system. Objective of this project is to leverage paperless hospital service where patient need not do any paper work while being 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.1. Purpose
The main purpose of Paperless Hospital Management system is to remove the usage of the paper from the hospital and make the processing of the Patient information faster and secured. Paperless Hospital Management System will developed mainly for providing an interaction with patient and generates an report based on It efficient and convenient manner . A fully automatic Hospital Management System reduce the use of paper and provide facility to doctor as well as admin staff and for patient.

1.2. Scope
The system will work for MIS (Management Information System) as well as DSS (Decision Support System) in the hospital management system. It will provide management for thousands of patients detail based on computer system. System will provide greater communication directly by network so there are no time wasting for all process that is generally done based on cost of time, Money all that process t are fully implemented in the system as logically and virtually.

Paperless Hospital Service

Describe the application of the software being specified. As a portion of this, it should: Paperless hospital management provide great facility of healthcare domain and all that facility that are given by any healthcare center as well as extra facility like blood bank, online medicine approval, appointment booking, doctor list, rooms availability, routine checkup mailing facility, suggestion facility etc. Simply the main focus behind this system is that all the work of hospital as well as communication between doctor and patient are done based on network so the overall speed of the work are going fast and the patient get fast tips on his/her health. Second main goal of this system is that provide eco-friendly system means that provide facility of all kind of process are done in system be based on paper that is now based on computer system. In addition, for that provide user-friendly interface to the patient as well as the entire user that are work in hospital so that he/she can interested to work with the system and the goal of system is satisfy. Our System Will Do:Can manage the personal record of the patients and doctors. Can manage the availability of the doctors. Can manage the health history and generate the proper report. Can provide online health advice to the visitors. Can provide the conference between multiple doctors. Can able to provide the information of the patients. Can allow the patient to pay the bill online. Can provide a user particular health account in which he/she can able to observe his/her health history. Patient can interact with the doctor using the web cam. Patient can able to his/her health report any time just connecting to the internet.

1.3. Definition, Acronyms and Abbreviations:Paperless hospital service is management that connect the entire hospital team with one common interface. Its main objective is to remove the use of paper in the organization so that the work becomes easy and effective. Patient: patient is the person who will take the service and treatment from the hospital and able to interact with the doctors and inquires about his health history. Admin Clerk: Admin clerk is the user of the system whose work is to assign the patient id number to the incoming patients and he is responsible to assign the department admin to the patient and maintain the records in the database.
5

Paperless Hospital Service

Department Admin: Department admin is the user whose task is to assign department and proper doctor and nurse to the incoming patient and maintain the records regarding this task. Doctor/Nurse: Doctor and nurse are the user of the system who will provide the service and treatment to the incoming patient and maintain the records regarding this in the database. Insurance Provider: Insurance provider is an external actor who will just ensure that whether the patient is insured or not, and it will take the help of the database to identify this.
AD: - Activity Diagram UCD: - Use Case Diagram SRS: - Software Requirement Specification.

1.4. Reference: 1) An integrated approach to software engineering, Third edition by Pankaj jalote

Paperless Hospital Service

2. OVERALL DESCRIPTION 2.1. Product perspectives:Existing System The existing system for the hospital service uses the hard files in order to maintain the records of the patients and all the activity carried out throughout the day. Hence, it becomes very cumbersome job to manage all this things because this requires the constant safety for the files and save them with the damage and all other problems. In present system all the appointments of the patient are entered in the appointment register, hence it also become hard to search the particular records from the file fastly, and so this decrease the efficiency of system.

2.2. Product Function:The data represented in hospital management System application will perform the following major function: Patient Details: - It includes inpatient and outpatient details. Lab reports:- it includes the details about the lab test conducted Billing Details:- it include the details regarding bill(include lab charge, doctor charge, nurse charge, room charge) Doctor allocation detail. Patient wise Doctor Allocation. This software will help to calculate the bill much quicker and simpler way. This enables the organization to keep the information in efficient and systematic way.

2.3. User Characteristics:This software is developed such that total appearance of the product to make it more user friendly. The operator will provided with login and password. General users with basic computer skills can use this software. Patient can easily get information from the system.

2.4. General Constraints: Any update regarding the patients information from the hospital are to be
record to have updated and correct values. 7

Paperless Hospital Service

One should have the computer knowledge to operate the system. 2.5. Assumption and Dependencies:All the data entered will be correct and up to date. This software package is develop using java as front end, which is supported by sun micro system, MS SQL server 2005 as the back end, which is supported by Microsoft windows Xp.

Paperless Hospital Service

3. SPECIFIC REQUIREMENTS
It describes all the details that the software developer need to know for designing and developing the system. This is typically the largest and most important part of the document.

3.1. External Interface Requirements:3.1.1. User Interface:User interface is designed in a user-friendly manner and the user, in another end he has to give the health detail, for that he will interface with keyboard and mouse.

3.2. Functional Requirements: Patient will go to hospital and are 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 about health history. In addition, 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. 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: o Create Patient Record o Modify Patient Record o View Patient Record o Delete a Patient Record o Bill to Insurance Providers o Bill to Patient

Paperless Hospital Service

3.3 Non Functional Requirement
Performance Requirements:
The capability of the computer depends on the performance of the software. The software can take any number of input provided the database size is large enough. This would depend on the available memory space. Database must be maintained to store all patient profiles

Storage

Security Password must be of six characters and must have at least one numeric character. Availability 24 X 7 availability.

3.4. Design Constraints:This will help the doctors or users to view the records of the patients immediately whenever necessary. They can also calculate the bill of the particular patients. This software also has the ability to add, update and delete the record whenever needed. This project will help to smoother the process of the hospital activates. In addition, it will help in maintaining the information about the health history of the patient.

10

Paperless Hospital Service

4. Analysis Models
4.1 Activity Diagram

11

Paperless Hospital Service

Activity Diagram for User: Admitting Clerk

12

Paperless Hospital Service

Activity Diagram for User: Department Admin

13

Paperless Hospital Service

Activity Diagram for User: Doctor/Nurse

14

Paperless Hospital Service

Activity Diagram for User: Billing Department

15

Paperless Hospital Service

Activity Diagram for User: Insurance Provider

16

Paperless Hospital Service

4.2 Use cases Use Case for User: Patient

17

Paperless Hospital Service

Use Case for User: Admitting Clerk

18

Paperless Hospital Service

Use Case for User: Department Admin

19

Paperless Hospital Service

Use Case for User: Doctor/Nurse

20

Paperless Hospital Service

Use Case for User: Billing Department

21

Paperless Hospital Service

Use Case for User: Insurance Provider

22

Paperless Hospital Service

4.3 Sequence Diagram
Sequence Diagram for Insurance provider: get patient information use case

23

Paperless Hospital Service

Sequence Diagram for Insurance provider: get insurance information use case

24

Paperless Hospital Service

Sequence Diagram for Insurance provider: get total Bill amount use case

25

Paperless Hospital Service

4.4 Database Design
1. Description A database is a collection of information and is systematically stored in tables in the form of rows and columns. The table in the database has unique name that identifies its contents. The database in turn is further described in detail giving all the fields used with the data types, constraints available, primary key and foreign key. Database design is used to manage large bodies of information. In this database, we describe all the four tables available in the software, which are used to store all the records. 2. Data types and its description: Fields in database table have a data type. Some of the data types used in database table are explained below. a) Integer:One optional sign character (+ or -) followed by at least one digit (0-9). Leading and trailing blanks are ignored. No other character is allowed. b) Varchar:It is used to store alphanumeric characters. In this data, type we can set the maximum number of characters up to 8000 ranges by default SQL server will set the size to 50 characters large. Date/Time:Date/Time data type is used for representing data or time.

26

Paperless Hospital Service

Department_Table Fields dept_id dept_name Doctore_Table Fields Doct_id Doct_name Dept_id Disease_Table Fields Disease_id Disease_name Patient_Table Fields Patient_id Patient_name Patient_dob Patient_age Patient_cont_no Patient_city Patient_gender Doct_id Dept_id Disease_id Room_Table Fields Room_id room_type Room_status Data Type Int Varchar(15) Varchar(10) Constraints Primary Key Not Null Not Null 27 Data Type Int Varchar(25) Date Int Varchar(11) Varchar(20) Varchar(6) Int Int Int Constraints Primary Key Not Null Allow Null Allow Null Allow Null Allow Null Not Null Foreign Key Foreign Key Foreign Key Data Type Int Varchar(50) Constraints Primary Key Not Null Data Type Int Varchar(25) Int Constraints Primary Key Not Null Foreign Key Data Type Int varchar(25) Constraints Primary Key Not Null

Paperless Hospital Service

Bill_Table Fields Bill_no Patient_id Doct_charge Nurse_charge Medicine_charge Room_charge No_of_days Insurance_id Lab_charge Tot_bill Insurance_Table Fields Insurance_id Insurance_type Inpatient_Table Fields Patient_id Room_id Date_of_adm Date_of_dis Lab_id Lab_Table Fields Lab_id Patient_id Weight Doct_id Date Lab_charge Data Type Int Int Int Int Date/Time Int Constraints Primary Key Foreign Key Foreign Key Foreign Key Allow Null Allow Null Data Type Int Int Date/Time Date/Time Int Constraints Foreign Key Foreign Key Not Null Not Null Foreign Key Data Type Int Varchar(25) Constraints Primary Key Not Null Data Type Varchar(10) Int Int Int Int Int Int Int Int Int Constraints Primary Key Foreign Key Allow Null Allow Null Allow Null Allow Null Allow Null Foreign Key Foreign Allow Null

28