Paperless Hospital Service: Software Requirement Specification

Paperless Hospital Service
Software Requirement Specification
Team Guide Sankar.K

Asst. Professor
Team Members
Abdul Jabbar. S Naveen. D 51309104301 51309104308
Department of Computer Science and Engineering Sri Balaji Chockalingam Engineering College, Arni 632 317, Tamil Nadu.
FANTASTIC 11
2011
Table Of Contents
Description 1.0 Introduction
1.1 Purpose 1.2 Scope 1.3 Definition, Acronyms, and Abbreviations 1.4 References 1.5 Technologies to be used 1.6 Overview 1 1 3 5 5 5
Page No
2.0 Overall Description

2.1 Product Perspective 2.2 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 Sequence Diagram 2.10 Database Design 2.10.1 ER Diagram 2.10.2 Schema 2.11 Assumptions and Dependencies 15 16 17 6 7 7 8 9 9 9 10 11 12
3.0 Specific Requirements

3.1 Use Case Reports 3.2 Supplementary Requirements 17 20
2011
FANTASTIC 11
Software Requirements Specification

1.0 Introduction 1.1 Purpose
Paperless Hospital Service is a Web application Which Provides fully Systemized services to hospital. Through this service the different users can communicate with each other as in the form of system. So patients need not do any paper work while getting admitted to hospital. This web application is more effective health care service for hospital especially to leverage the paper work.
1.2 Scope
There are Six basic Users 1. 2. 3. 4. 5. 6. Patient/Relative. Admitting Clerk. Department Admin. Doctor/Nurse. Billing Department. Healthcare Insurance Providers (External Actor).
All Users have own profiles in PHS.
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.
FANTASTIC 11
2011
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. 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
FANTASTIC 11
2011
1.3 Definitions, Acronyms and Abbreviations

PHS
Paperless Hospital Service: Its a Web application that provides fully systemized medical services for users.
Admin
Administrator: He has the authority to add/delete users, grant permission to doctors and patients.
ICU
Intensive Care Unit: It is one of the specialized departments in the hospital which provides Intensive Care Medicine.
ENT
Ear, Nose, Throat: It is the Branch of Medicine and Surgery that Specializes in the diagnosis and treatment of Ear, Nose, Throat and head & neck disorder.
HTML
Hyper Text Markup Language: It is used to create static web pages.
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.
JSP
Java Server Pages: It is used to create dynamic web content.
J2EE
Java 2 Enterprise Edition: A programming platform, belonging to the java platform, which is used for developing and running distributed java.
FANTASTIC 11
2011
WASCE
WebSphere Application Server Community Edition: It is an application server that runs and supports the J2EE and the web service applications.
WSAD
WebSphere Studio Application Developer: It is a designer toolkit which is designed to develop more complex projects by providing a complete dynamic web service.
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: It is 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.
FANTASTIC 11
2011
1.4 References:
IBM Red Books. IBM TGMC Sample Synopsis. IBM WWW.ibm.in/developerworks Java www.sun.com Wikipedia www.wikipedia.com
1.5 Technologies to be used:

DB2: Relational Database Management System (IBM Database) RAD: Rational Application Developer. WASCE: Web sphere Application Server Community Edition. Rational Software Modeler.
1.6 Overview:
Existing System: Discussion forum Patients should fill forum during admitted Drawbacks:
No healthcare insurance providers High cost
Proposed System:
Patient need not to do any paper work while getting admitted to hospital Patient ID will be sent via sms to patients mobile number.
Advantages:
Provides 24x7 service Eliminates hard to read handwriting Eliminates transcription errors Avoids duplicate ordering Accurate billing
FANTASTIC 11
2011
2.0 Overall Description

2.1 Product Perspective
WAS JSP/J2EE APPLICATION IBM LOTUS FORMS APPLICATION
JAXP & SAX PURE XML IS USED
JAVA APPLICATION
WEB SERVICE
JAXP & SAX
DB2 IBM
FANTASTIC 11
2011
2.2 Software Interface

Client on Internet Web Browser, Operating System (any) Client on Intranet Web Browser, Operating System (any) Web Server WASCE, Operating System (any) Data Base Server DB2, Operating System (any) Development End RAD (J2EE, Java, JavaBean, Servlets, HTML, XML, AJAX), DB2, OS (Window), Web Sphere (web Server)
2.3 Hardware Interface Minimum Requirements: Client Side Processor

Internet Explorer6
RAM
Disk Space
100 MB
Intel Pentium iii or 128 MB AMD -800 MHZ
FANTASTIC 11
2011
Server Side Processor

RAD DB2
RAM
Disk Space
3.5 GB 500 MB (Excluding Data Size)
Intel Pentium iii or 1 GB AMD -800 MHZ 256 MB
Recommended Requirements: Client Side Processor RAM Disk Space

100 MB
Internet Explorer-6 All Intel or AMD - 256 MB 1 GHZ
Server Side Processor

RAD DB2
RAM
Disk Space
3.5 GB 500 MB (Excluding Data Size)
All Intel or AMD - 2 GB 2 GHZ 512 MB
2.4 Product Function

PHS System Exposed Various Operations through Web Sphere application 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
FANTASTIC 11
2011
2.5 User Characteristics

Patients accept id number through SMS Admin and Doctor can interact with patient through this id number and update records to Database DB2 with the help of PHS Environment.
2.6 Constraints
GUI is only in English Login and password is used for the identification of users Only registered patients and doctors will be authorized to use the services This system is working for Single server.
2.7 Architecture Design
APPLICATION LAYER
BUSSINESS LAYER
DATABASE LAYER
Login UI
Login UI
Login
Registration UI
Registration UI Doctor/ Patient
Search UI
Search UI
Appointment
Appointment
Appointment
Report UI
Report UI
Report
FANTASTIC 11
2011
2.8 Use Case Model Description
<<extends>> Take Appointment Authenticate Maintain Sy stem DataBase
Search Doctor Interact With Doctor Generate Records
Patient
Admin
Register
Login
Logout
Search
Chat
Doctor
Giv e Prescription Receiv e Mail
View Appointmemt
Patient:
Patient can admitted in hospital as register and search for doctor appointment and then chat
Admin:
Admin can login to system and create new patient record and maintain system database
FANTASTIC 11
2011
10
Doctor:
Doctor login to system and view appointments then give prescription to the patient.
2.9 Class Diagram
Admin Ad_id Ad_name Age Gender D_O_B Address 1 Address 2 Phone Mobile_no_1 Mobile_no_2 Admitting patient() Create records() Take Backup() Send SMS() Approve appointments()
Doctor Doct_id Doct_name Age D_O_B D_O_J Gender Photo Specialization Address 1 Address 2 Phone_no_1 Phone_no_2 Mobile_no_1 Mobile_no_2 Prescribe patients() Surgery() Update Patient Records() Department Dept_id Dept_name Conduct various test() Update records()
Patient Pat_id Pat_Type Pat_name Age D_O_B Gender Photo Address 1 Address 2 Phone_no Mobile_no_1 Mobile_no_2 Father's name Address PhoneNo MobileNo1 MobileNo2 Disease CreditCard_no DebitCard_no Get admitted() Interact w ith doctor() View health records()
Bill_details Bill_no Amount
FANTASTIC 11
2011
11
Sequence Diagram
Sequence Diagram for Patient Admit
Patient/Relative
Admitting Clerk 1:Giveinfo()
Department Admin
Doctor
Billing Department
Insurance Provider
PHS DataBase
2:CreateNewHealthRec ord() 3:SendPatient_id as SMS() 4:AssignPatientRecords() 5:AssignPatient to Department()
6:InteractWithDoctor()
7:GiveTreatment()
8:UpdatePatientRecords()
9:VerifyPatientInsurancePolicy() 10:ChargeCost()
11:CheckPolicyCoverage() 12:Pay by Cash or Credit/Debit Cards()
FANTASTIC 11
2011
12
Sequence Diagram For Appointment:
Patient
Admin
Interface
Doctor
PHS DataBase
1:SearchDoctor()
2:Forward() 3:Search()
4:ForwardResult()
5:SendAppointmentDate/time() 6:ApproveAppointment()
7:InteractWithDoctor()
8:GiveTreatment() 9:UpdatePatientRecords()
10:Send to DataBase()
FANTASTIC 11
2011
13
Sequence Diagram for Prescription
Doctor
Interface 1:Prompt to Select Patient()
Patient
PHS DataBase
2:EnterDetails() 3:Forward() 4:Search()
6:DisplayResult()
5:ForwardResult()
7:SelectPatient()
8:ViewHealthRecords()
9:EnterPrescription() 10:Forward()
FANTASTIC 11
2011
14
2.10 Database Design 2.10.1 E-R Diagram
Med Condition Allerg ies Name Pat_ID Age Record_I D Te st
Ph_no PATIEN T Addres s
Gend er Addr ess
HA S Immunizati on
HEALTHRE CO RD
Insuran ce
Ph_no Fathers name Mobile_ no Mobile_n o Departm ent Dept_I D App_I D Appoint ment Ti me Specializat ion
Prescript ions
Updat es
Nam e Na me Doct_I D Age DO CT OR
Manag es
Gende r Adde rss
Date
Designati on Conta ct Appro ves
Ad_ ID Na me Age Gend er Conta ct ADM IN Add ress
Bill_Det ails Amou nt Bill_N o
FANTASTIC 11
2011
15
2.10.2 Schema
FANTASTIC 11
2011
16
2.11 Assumption and Dependencies
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 Specification Requirement 3.1 Use Case Reports
Send SMS Search
Create New Record
Interact With Doctor
Patient
Register Admin
Update Record
View Health Record
Approv e Appointment
Patients Use case Report: USE CASE

Register Interact With Doctor View Health Records Search Send SMS Create New Record Update Records Approve Appointment
DESCRIPTION
Patient Admitted to hospital The Patient Can Interact With doctor The Patient Can View his/her Health Records The patient search for particular doctor An Admin Send Patient_ID by Sending SMS An Admin Can Create New Record for new Patients An Admin Can Update the patient records if needed An Admin Approves Appointment to Doctor for Particular patient
FANTASTIC 11
2011
17
Doctors Use Case Report:

<<include>> Approv al From Admin
Register <<extends>>
Doctor
Login
Select a Patient
Interact With Patients
Prescribe Treatment
Approv e Appointment
Patient
<<extends>>
Create Health Record
Update Health Record
USE CASE
Login Register Prescribe Treatment Approval From Admin Select a Patient Interact With Patient Approve Appointment Create Health Record Update Health Record
DESCRIPTION
The Doctor has Login to System in order to begin his work The Doctor has Registered for Approval from Admin The Doctor Prescribe the Treatment For Patient The Doctor gets Approval From Admin The Doctor Select a Patient which is approved by Admin The Doctor Intract with Patient The Doctor Approves the Patient Appointments The Doctor Will Create Health Patient Record if needed The Doctor Update the Patients health Record after treatment
FANTASTIC 11
2011
18
Admin Use Case report:
<<extends>> Update Profile Send SMS View Prof ile
Generate Records
Admin
Login View Records
Take Backup
Authenticate Doctors Delete Records Maintain Records
USE CASE
Login Generate Records Send SMS View Profile Update Profile View Records Authenticate Doctors Maintain Records Take Backup Delete records
DESCRIPTION
An Admin Login to System in order to Start Work An Admin Generate New Patient Record An Admin Sends Patient_ID by SMS An Admin View the Doctor Profile An Admin Can Update the profile An Admin can view the Patient Records An Admin Can Authenticate for Doctors An Admin Maintains the patient records An Admin Take system database backup An Admin Delete Patient Records if needed
FANTASTIC 11
2011
19
3.2 Supplementary Requirements

INDEX
A
Abbreviations Acronyms Admin AJAX Architecture Design Assumptions 5 5 5 6 11 19
C
Class Diagram Client on Internet Client on Intranet Constraints 13 9 9 11
D
Database Design Database Server Development End Doctor DB2 Dependencies Definitions 7 9 9 5 5 19 5
E
E-R Diagram ENT Existing System 17 5 7
FANTASTIC 11
2011
20
H
HTML HTTP Hardware Interface 5 6 9
I
Introduction ICU 3 5
J
JSP J2EE 5 5
M
Minimum Requirements 9
O
Overview Overall Description 7 8
P
Patient Purpose PHS Proposed System Product Perspective Product Function 12 3 5 7 8 10
FANTASTIC 11
2011
21
R
References Recommended Requirements 7 10
S
Schema Scope Sequence Diagram Software Interface Software Requirement 18 3 14 9 19
T
Technologies to be used 7
U
UML Use Case Model Description Use Case Reports 6 12 19
W
WASCE Web 2.0 Web Server WSAD 6 6 9 6
X
XML 6
FANTASTIC 11
2011
22
THANKS
We Convey Our Special thanks to our department and College. We also Convey a Special thanks to our Guide and all these softwares and websites, they have been helping a lot in doing the project.
F ANTASTIC 11
FANTASTIC 11
2011
23

Paperless Hospital Service: Software Requirement Specification

Încărcat de

Informații document

Descriere originală:

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Paperless Hospital Service: Software Requirement Specification

Încărcat de

Drepturi de autor:

Formate disponibile

Paperless Hospital Service

Software Requirement Specification

Team Guide Sankar.K