MIT MANDSAUR

VIRTUAL MEDICAL HOME

Software Requirements Specification

TEAM NAME

BOMBINOO

TEAM MEMBERS

1. ROSHNI MITTAL
2. SANGEETA SEWANI
3. UMA SHANKAR

PROJECT GUIDE

Mr.Prabhat Singh

1
 Index & Tables

1) Introduction:........................................................................................4

1.1) Purpose: .....................................................................................4

1.2) Scope ..........................................................................................4-5

1.3) Abbreviations:...............................................................................5-6

1.4) References:....................................................................................6

1.5) Technologies:..................................................................................6

1.6) Overview...........................................................................................6

2) Overall Description:....................................................................................7

2.01) Product Perspective:..........................................................................7-8

2.02)Software Interface:..................................................................................9

2
 2.03) Hardware Interface: ...............................................................................9-10

2.04) Communication Interface:.........................................................................10

2.05) Product Function:.....................................................................................10

2.06) User Characteristics:.................................................................................11

2.07) Constraints: ..............................................................................................11

2.08) Use-Case Model Survey:............................................................................12-14

2.09) Database design: ......................................................................................15-16

3) Specific Requirements: .......................................................................................17

3.1) Use Case Reports:..........................................................................................17-44

3.2) Supplementary Requirements:……………….…………………………………..45

3
1.)Introduction :

1.1) Purpose :

A Virtual Medical home is a web-page of integrated application selected by the consumer to better
manage all aspects his/her health and healthcare.
The major objective of this program is to provide the necessary required online services to all
irrespective of their location.

1.2) Scope :

1. Managing profiles of users and register them.

2. Patients to make online appointment.
3. Managing patient’s health record, lab reports.
4. Doctors to give appointment and view patients history.
5. Webcam based interaction between patient and doctor.
6. Track all the payment details of the patient and medical expenses
7. Adjustment of the appointments and daily activities by

4
 kiosk manager.
8. Charge complaints against wrong medication and lab reports.
9. Patients grievances and feedback goes to the admin and this can
be forwarded to any doctor for their answer.
10. Activities like chat, mail and discussion forum for appropriate
Communication.
11. View all the details of all the interactions made by the
Customers.
12. To have the backup for all kind of data and generate reports on
The admin.
13. Activities like updations, creations done in the system by the
System users.

1.3 Abbreviations :

HTML: Hypertext Markup Language is a markup language used to design static web pages.

EJB: Enterprise Java Beans.

J2EE: Java 2 Enterprise Edition is a programming platform— part of the Java Platform for developing and running distributed
multitier architecture Java applications, based largely on modular software components running on an application server.

DB2: DB2 Database is the database management system that delivers a flexible and cost effective database platform to build
robust on demand business applications.

5
Apache Tomcat: Apache Tomcad is an open source software implementation of java servlets and java server pages
technologies.

TCP/IP: Transmission Control Protocol/Internet Protocol, the suite of communicationprotocols used to connect hosts on the
Internet. TCP/IP uses several protocols, thetwo main ones being TCP and IP.

1.4) References:

IEEE SRS Format

Problem Definition (Provided by IBM)
CT Arrington. Enterprise Java with UML. OMG Press.

1.5) Technologies:

J2EE: Application Architecture

DB2: Database
Apache Tomcat

1.6) Overview: SRS will include two sections:

Overall Description will describe major components of the system, interconnection and external interfaces.
Specific Requirements will describe the functions of actors, their role in the system and constraints.

6
2) Overall Description :

Describe the general factors that effect the product and its requirements.

2.01) Product perspective

1. The web pages (XHTML/JSP) are present to provide the user interface on customer client
side . Communication between customer and server is provided through HTTP/HTTPS protocols.

2.The Client Software is to provide the user interface on system user client side and for this TCP/IP protocols are used.

3.On the server side web server is for EJB and database server is for storing the information.

7
Application Database
Server Server

8
2.02) Software Interface:

Client on Internet: Web Browser, Operating System (any)

Web Server: Apache Tomcat, Operating System (any)
Data Base Server: DB2, Operating System (any)
Development End: WSAD (J2EE, Java, Java Bean, Servlets, HTML),
DB2, OS (Windows), Web Server.

2.03)Hardware Interface:

Client Side :

Processor RAM Disk Space

Internet explorer Pentium II at 64 MB 1 GB

6.0 500 MHz

9
Server Side :

Processors RAM Disk Space

Pentium III at 1
DB2 V8.1 GHz 512 MB
Intel Celeron M
ApacheTomcat Processor 1.6GHz 512 MB 2GB

2.04) Communication Interface:

1. Client on Internet will be using TCP\IP protocol.

2. Apache Tomcat

2.05) Product Function:

1.Provide the user with online medical help.
2.Maintain a proper link between doctor and patient.
3.Manage all the appointments.
4.Establish effective interaction between the doctor and the patient.
5.Maintain logs of different users.
6. Maintains all the details (Personal, Official) of the patient.

7. If we want to update your personal details or new informations then it will supports to users
10
2.06) User Characteristics:

Every user should be comfortable of working with computer and netbrowsing. He must have basic knowledge of
English too.

2.07) Constraints:

1.GUI is only in English.

2.Anonymous user can get information upto an appropriate limit & for more details the user have to login.
3.This system is working for single server.

11
2.08) Use-Case Model Survey:

12
1] Administrator: Responsible for managing system users, viewing logs and managing all types of managers

Ø  Manage System Users: The Administrator will create different roles. The system users will be created and will be
assigned with the different roles. More than one task and permissions can be granted or revoked from the system
users.
Ø V
 iew Logs: Responsible for checking the logs of different system user for auditing and maintaining the integrity of
the system.
Ø Manage All Managers: All managers are supervised by the administrator
Ø View All Details: View the user details and all other sorts of details even which comes under the other managers.
Ø Manage complaints/feedback:-Responsible for managing feedback from patient .patient’s grievance and
feedback goes to admin and he can forward it to any doctor to answer

2] Kiosk manager:-Responsible for managing patient daily appointment ,adjust appointment ,perform daily and close
activities ,manages modes of payment and services catalogs.

Ø Manage patient :-records details of new patient ,update and view its details.
Ø Manage appointment :-records the daily appointment of each doctor and inform the records of daily appointment of
each doctor through emails.
Ø View all details:-view the patient details,payment details and daily services details.
Ø Manage groups:-categorize the patient belonging to different doctor according to some criteria.
Ø Inform medical expenses:-manage the medical expenses of each patient and calculate the total expenses of each
Doctor and its commission.
Ø Manage complaints:-Responsible for managing complaints against Doctor for wrong medication or lab report

13
3] Doctor:-Responsible for viewing patient’history ,giving e-prescription,appointment according to the availability of time.

Ø Manage appointment:-responsible for managing daily appointment according to the availability of time via manager
through mails.
Ø Give e-prescription:-give e-prescription to each patient through mail.
Ø Manage patient history:-Responsible for managing the patient previous health records and lab reports.

4]Patient:-Responsible for making its online appointment ,look on their previous health records,doctor’s prescription,lab
records and prescription.

Ø View health records:-view the previous health,lab reports and prescription.

Ø View its own details:-patient can view its own details,medical expenses details,details about services provided and
can view the details of Doctor’s available related to the website.
Ø Webcam interaction:patient can interact directly to the doctor through the webcam.
Ø Complaint : patient can register complaint against wrong medication.
Ø Make online appointment : patient can get appointment from the manager.
Ø View the medical expenses: patient can view his total medical expenses.

14
2.09)Database Design:-

15
16
3) Specifications:

3.01)Use Case Reports:

i)Administrator:-Responsible for managing system users,viewing logs and managing standard groups of the system.

Ø Manage System Users: The Administrator will create different roles. The system users will be created and will be
assigned with the different roles. More than one task and permissions can be granted or revoked from the system
users.
Ø V
 iew Logs: Responsible for checking the logs of different system user for auditing and maintaining the integrity of
the system.
Ø Manage All Managers: All managers are supervised by the administrator.
Ø View All Details: View the user details and all other sorts of details even which comes under the other managers.
Ø Manage complaints/feedback:-Responsible for managing feedback from patient .patient’s grievance and
feedback goes to admin and he can forward it to any doctor to answer.

17
Name of use case: view system user
Description: View the list of system users in a role and view the details of
roles, tasks and permissions assigned to a system user.
Preconditions:
GAdministrator is already logged in.
GSystem users have already been created and assigned some roles, tasks and permissions.
Normal flow of events:
The system user or a role will be selected.
Ø Query will be submitted.
Ø Relevant output will be displayed (If system user is selected then roles, tasks and
permissions assigned to one will be displayed and if role is selected then list of system
Ø users assigned to that role will be displayed).
Ø Alternate flow of events: None.
18
Name of use case: Create System Users
Description: To create system users (Giving them a login name, password
and assign roles, tasks and permissions to them).
Preconditions: Administrator is already logged in.
Normal flow of events:
GNew Login name, password, details, roles, tasks and permissions will be entered.
GSave the details.
Alternate flow of events:
GA message appears for duplicate login name.
GThe administrator has to fill the details again.
Post condition: A login id is generated with its details.
19
20
Name of use case: Update details of Users
Description: To update the details of system users (assigning or revoking roles, tasks and
permissions).
Preconditions:
GAdministrator is already logged in.
GSystem Users have already been created.
Normal flow of events:
GSelect the user name.
GAssign or Revoke the roles, tasks and permissions.

21
Name of the Use Case : View logs
Description : To view the activities and logs of system users.
PreCondition :
1.Administrator is already logged in.
2.System user is already logged in.
Normal flow of events :
1.Select user name.
2.Select date.
PostCondition : None

22
Name of the Use Case : View system reports.
Description : Medical details and its expenses are displayed.
PreCondition : Administrator should be already logged in medical information must be present.
Normal flow of events :
1.Select the service.
2.The catalogue of services is shown.

23
Name of the Use Case : Manage Complaints.
Description : To manage complaints of patients for wrong medical
prescription.
PreCondition : Administrator is already logged in.
Normal flow of events :
1.Check the complaints made by the patients.
2.Inform doctor for the wrong medical prescription.
3.Take new prescription from the doctor.
4.Update prescription.
5.Inform patient via mail.
PostCondition : Updated prescription is sent to the patient via mail.

24
ii)Kiosk manager:-Responsible for managing patient daily appointment ,adjust appointment ,perform daily and close activities
,manages modes of payment and services catalogs.
Ø Manage patient :-records details of new patient ,update and view its details.
Ø Manage appointment :-records the daily appointment of each doctor and inform the records of daily appointment of
each doctor through emails.
Ø View all details:-view the patient details,payment details and daily services details.
Ø Manage groups:-categorize the patient belonging to different doctor according to some criteria.
Ø Inform medical expenses:-manage the medical expenses of each patient and calculate the total expenses of each
Doctor and its commission.
Ø Manage complaints:-Responsible for managing complaints against Doctor for wrong medication or lab report

Name of the Use Case : Manage daily open and close activities.
Description : Manager manages the daily open and close activities ,
see and adjust appointments and calculate the commission.
PreCondition : Manager is already logged in.
Normal flow of events : Look for the daily activities.
Alternate flow of events:-
Ø A message appears for unfilled fields.
Ø The kiosk manager has to fill the details again.
Post condition:-None.

25
26
Name of the Use case : Manager-Management of appointments.
Description : Management of appointments.
PreCondition : Manager is already logged in.
Normal flow of events :
1.Look for new patients registered.
2.Check for the availability of doctors.
3.Give appointments to patients and take expenses.
4.Expenses paid.
5.Inform doctor via mail.
6.Appointment confirmed.

Alternate flow of events : A message appears if appointment not available then look for the new date.
Post Condition : Appointment confirmed.

27
28
Name of use case: Manage mode of payment.

Description: Manage the mode of payment, take patients

medical expenses and calculate his commission.

Precondition: Manager is already logged in.

Normal flow of events:

G Look for the patient and their expenses.

G Payment done.

Alternate flow of events:

G A message appear if payment not done.

G Wait for payment.

Post condition: Manager calculates his commission.

29
iii)Doctor:-Responsible for viewing patient’ history ,giving e-prescription, appointment according to the availability of time.

Ø Manage appointment:-responsible for managing daily appointment according to the availability of time via manager
through mails.
Ø Give e-prescription:-give e-prescription to each patient through mail.
Ø Manage patient history:-Responsible for managing the patient previous health records and lab reports.

30
 Name of the Use Case : Doctor –Manage appointments of patients
Description : Manage daily appointments according to the availability of time.
PreCondition : Doctor is already logged in.
Normal flow of events :
1.Check for the availability of time.
2.Time available.
3.Give appointment via manager to the patient.
Alternate flow of events : If time is not available then check for tha availability of time.
PostCondition : Patient’s appointments are confirmed.

31
Name of use case: View patient history

Description: View the patient previous history and health records

Precondition: Doctor is already logged in

Normal flow of events:

 1.Check mails

2.Inbox contain mails of appointment of that patient

3.View patient health records

Alternate flow of events: If inbox does not contain any mails of

appointment of that patient then exit

Post condition: Patient’s previous health records are viewed by doctor

32
Name of use case :-Status of doctor
Description :give information about status of doctor ,check the availability of doctor.
Precondition: Doctor should be already logged in.

Normal flow of events:

Ø Check for the availability of Doctor.
Ø Status is available.
Ø View patient.
Alternate flow of events:-
Ø A message appears if doctor status is busy then ask from manager..

33
Name of use case:-e-prescription
Description :-doctor prescribe medical information &medicine through e-mail that is e –prescription.
Precondition:-Doctor should be already logged in.

Normal flow of events:-

Ø View patient’s previous health records.
Ø Interaction done.
Ø Prescribe medicine through mails.
Alternate flow of events:-
Ø A message appears if the interaction between doctor and patient is not done.

34
.

Name of use case:- Webcam Interaction

Description:-interaction between patient and doctor is done through webcam .
Precondition:-patient and doctor should already be logged in.

Normal flow of events:-

Ø Check the availability of appointment from manager.
Ø Check the status of doctor.
35
 Ø doctor status is available.
Ø Interact through web cam.
Alternate flow of events:-
Ø A message appears if doctor status is busy in that case ask new date from manager according to the availability of Doctor.

36
iv)Patient:-Responsible for making its online appointment ,look on their previous health records, doctor’s prescription, lab records
and prescription.
Ø View health records:-view the previous health, lab reports and prescription.
Ø View its own details:-patient can view its own details, medical expenses details, details about services provided and
can view the details of Doctor’s available related to the website.

GName of the use case: Registration of Patient

Description: To get benefit of the website and to know more

Information of this website patient have to register

Precondition: No precondition

Normal flow of events: If new register then login

Alternate flow of events: If already registered then login

Post condition: A login id is generated with its details

37
Name of the Use Case : View Health Records of the Patient
Description : Patient can view their health records.
Precondition : Patient is already logged in.
Normal flow of events :
1.Visit home.
2.View your previous health records.
Post Condition : Patient’s health records are viewed.

38
Name of the Use Case : Patient’s medical expenses.
Description :View the Medical Expenses related to each disease
Precondition : Patient is already logged in.
Normal flow of events :
1.Visit home.
2.Contact manager for fee.
3.Check the fees charged.
4. Pay the total expenses.
Post Condition : Medical expenses related to each doctor is calculated.

39
Name of the Use Case : Make Online Appointments.
Description : Patient make Online appointment to make interaction with doctor.
PreCondition : Patient is already logged in.
Normal flow of events :
1.Ask for the appointment from manager.
2.Appointment available then give appointment.
3.Appointment confirmed.
40
Alternate flow of events :
1.A message appears if appointment is not available.
2.Ask for a new date & select date.
Post Condition : Patient’s appointment is confirmed.

41
Name of use case: Patient’s mod of payment.

Description: A way of paying medical expenses.

Preconditions: Patient is already logged in.

Normal flow of events:

G Pay your medical expenses.

G Enter your credit no and its details.

G Enter your 4 no digit code.

G Enter the amount.

G A message appears if medical expenses are paid.

Alternate flow of events: If the 4 no digit code is not valid then enter
your credit no again and whole process will
be repeated.

42
43
Name of the Use Case :- Registration of complaint.
Description : Registration of complaint against doctor for wrong medical prescription
PreCondition : Patient is already logged in.
Normal flow of events :
1.Register a complaint.
2.Make complaint against doctor.
3.Specify the doctor and complaint.
4.Inform patient about registration of complaint.
PostCondition : Complaint is registered against the specified doctor.

44
3.2) Supplementary Requirements:

1) Have hours of operation that are 24 x 7 - Because system can be an automated process, so it can stay open for 24 hours a
day. If the base is now the entire world,staying open 24 hours a day becomes critical. System is required to be available 24X7 so
UPS support must be on server site for at least 8 hours in case of power failure. System will remain inaccessible to users at 2:00 to
4:00 am for backup and maintenance purpose.
2)Make the existing Web site more dynamic in nature - Many early Web implementations consisted of static HTML pages. This
becomes very difficult to manage if the number of pages gets too large. An effective system should be largely dynamic taking
advantage of technology that automates this process rather than relying on manual processes. Application should serve dynamic
user based customized web pages to its clients from server.
3)Tie the existing Web site into existing enterprise systems – Any existing Web site that relies on the manual duplication of
data from another system is one that can be improved. Most of the business data in the world today exists in enterprise servers that
can be connected to the Web servers to make this process far more effective.
4)Provide good performance and the ability to scale the server – The WebApplication Server should provide good performance
and the ability to manage performance with techniques, such as support for caching, clustering, and load
balancing.
5)Providing session management capability - Web application developers should not spend valuable time worrying about how to
maintain sessions within the application. The Web Application Server should provide these services.

45