Virtual Medical Home: System Requirements Specification (SRS)

Virtual medical home Version 1.
0
Software Requirements Specification 28-12-2010
kryptonite
VIRTUAL MEDICAL
HOME
System Requirements Specification (SRS)
Version 1.0
Team name: kryptonite
Team Guide: MR.A.SRINIVASAN
Members:
1. Hemavarthini.g
2. S.Sivagami
3. S.abinaya
4. R.Ramya
College Name: MISRIMAL NAVAJEE MUNOTH JAIN ENGINEERING COLLEGE

Department: COMPUTER SCIENCE AND ENGINEERING
State: TAMILNADU
1
Kryptonite/M.N.M jain engineering college
Virtual medical home Version 1.0
kryptonite
Revision History
Date Version Description Author

28-12-2010 1.0 Synopsis kryptonite
29-12-2010 2.0 Synopsis kryptonite
2
kryptonite
Table of Contents
Sl.no Description Page No.
1 Introduction 5
1.1 5
Purpose
1.2 5
Scope
1.3 Definition, Acronyms, and 6

Abbreviations
1.4 6
References
1.5 7
Technologies to be used
1.6 7
Overview
2 Overall Description 8
2.1 Product Perspective 8
2.2 Software Interface 9
2.3 Hardware Interface 9
2.4 Product Function 9
2.5 User Characteristics 9
2.6 Constraints 10
2.7 10
Architecture Design
2.8 11
Use Case Model
Description
3
kryptonite
2.9 14
Class Diagram
** 15
Sequence Diagram s
2.10 18
Database Design
2.10.1 19
ER Diagram
2.11 Assumptions and 20

Dependencies
3 Specific Requirements 20
3.1 Use Case Reports 20

3.2 Supplementary 23
Requirements
4
kryptonite
Software Requirements Specification

1.0 Introduction:
The section introduces the system requirements specification (SRS) for virtual
medical home.
Virtual medical home is designed to meet the requirements of the patients that are
to be done through online services. Main objective is to provide contact with the doctors
at remote areas and to throw light on the factor that limited hours of services and to
maintain these records.
1.1 Purpose:
Purpose Develop an online comprehensive virtual medical home to engage
patients, doctors and hospitals to be more quick, proactive and responsive to fight with
diseases and Unawareness about health. It provides the transparency between
patients and doctors with secure access to information at several levels. It will also
provide awareness among rural people as they miss experienced and matured doctors.
They feel the experience of Appointments with higher degree doctors.
1.2 Scope:
The Scope of the virtual medical home includes:
Create different system users and manage their details.
Doctors and Kiosk Managers will be added as a user of the system only after manual
verification from administrator.
Patients can make online appointment, look their previous health
Records, doctor’s prescriptions, lab reports and medical expenses,
Doctor’s can give appointments, e-prescriptions, and view patients
History.
Web-cam based interaction between patient and doctor.
Kiosk Manager can see/adjust appointments, perform day open &
Close activities and calculate his commission.
In case of any medical error (wrong medication or lab report) patient

Can register a complaint. Patient’s grievance and feedback goes to
Admin he can forward it to any doctor to answer.
Facilitates appropriate communication between all stakeholders -

Discussion forum/chat/mail/polls
Site has details online help manual for patients. Local language
5
kryptonite
Support is also provided.
Admin to take backup of all kind of data, view log and generate
System reports.
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.
• 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
• 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.
6
kryptonite
1.4 References:
 Building web app with uml-jim by conallen and grady booch.
 Core Java: All Volumes by Cay S. Horstmann, Gary Cornell.
 SOA: Service-Oriented Architecture Best Practices by Dirk Krafzig and Karl Banke.
 OOAD: object oriented analyses and design by grady booch.
1.5 Technologies to be used:

UML: unified markup language
J2EE: (Servlet, JSP, JAXP, Java Beans) Application architecture.
Ajax: Asynchronous Java Script and XML.
XML: Extension Markup Language.
Web 2.0: RSS Feed 2.0.
E-FORMS: electronic form (visual basic)
SOA: service oriented architecture
1.6 Overview:
1.6.1 Specific Requirements:
This section will describe the functions of actors, their roles in the system and the
constraints faced by the system.
The virtual medical home (VMH) system will be a global Web-based place bringing together
private individuals, patients and doctors. It will take advantage of the Internet and World
Wide Web to radically improve the way of health care centers and hospitals.
The patient objectives for the VMH are to:
• Provide them with a user login and password.
• Enable them to easily search for, find, and get the advice they want.
• Enable them to search that they could not ordinarily find or afford.
• Enable them to help to get appointment they wish to get from preferred specialist.
7
kryptonite
• Provide them to maintain a private profile for them (e.g.: their problems, diseases
etc).
• More security for patients profile information.
The doctor objectives for the VMH are to:
• Provide them with a user login and password.
• Provide them with a huge customer base of potential.
• Enable them to easily target and personalize their patient problems.
• Enable them to give online medical prescription.
• Enable them to maintain their profile.
• Provide online appointments for patients.
The VMH objectives for the users are to:

• Minimize the cost and time.
• Minimize travel expansive.
• Doctors can attend patient at any time and vice versa.
1.6.2Overall Description:
This section will describe major components of the system, interconnections, and
external interfaces.
Overall description describes the general factors about project and its requirements.
And also describes the major components of the system, Interconnection and
external interfaces. Specific requirements will describe the functions of actors,
their role in the System and constraints.
2.0 Overall Description:

2.1 Product Perspective:
• The web pages (xhtml/jsp) are present to provide the end user interface
on Client side.
• Communication between users and server is provided through Http/https
protocols.
• On the server side web server is for jsp, servlet and database server, db2
is for storing the information. J2EE will be used to provide interface to
administrator and sub administrator
8
kryptonite
2.2 Software Interface:

Front End Client: internet server and operating system (any).
Web Server: Common
Data Base Server: DB2
Back End: DB2 and J2EE.
2.3 Hardware Interface:

Client Side: internet explorer 7
Server Side: Optional
2.4 Product Function:

Track Account Level Data: In this module, receivables from customer
Are maintained.
Authenticate Doctors and Kiosk Managers: The administrator will manually check
the details of each doctor and kiosk manager
And authenticate him/her.
Service Level Agreements: It contains the agreements of providing the
Services to patients, doctors and kiosk managers.
User Contact Information: It maintains all the details (Personal,
Official, Contact, and Company) of different users.
Transactions Records: Maintenance of transactions related to
The services provided to patients, kiosk managers.
Maintaining Logs: Activities of the various users can be tracked through
The logs, which are maintained by the system.
2.5 User Characteristics:

 Every user should be comfortable of working with computer and net browsing as the
server is user friendly.
 Although we have provided the support of using local languages yet it is preferred
that user should use English language.
9
kryptonite
2.6 Constraints:
 For full working of Virtual Medical Home requires internet connection.
 Login and password is used for identification of the various users that are
 Patient, doctor and kiosk manager.
 This system is working for single server.
 For backing up the data, the administrator will have to manually do it.
2.7 Architecture Design:
1
0
kryptonite
2.8 Use Case Diagram:
1
1
kryptonite
1
2
kryptonite
1
3
kryptonite
2.9 Class Diagram:
1
4
kryptonite
2.10 Sequence Diagrams:
1
5
kryptonite
1
6
kryptonite
1
7
kryptonite
2.10.1 Database Design:
2.10.2 ER Diagram:
1
8
kryptonite
1
9
kryptonite
2.11 Assumptions and Dependencies:

 The details related to the patient, doctor, kiosk manager and
Transaction provided manually.
 Administrator is created in the system already.
 Roles and tasks are predefined.
3. Specific Requirements:
3.1 Use Case Reports:
Administrator: Responsible for managing all the three types of users,
viewing
Logs and managing standard groups of the system.
 Manage System Users: The Administrator will provide the system
Users, Doctors and Kiosk Managers, authentication to use the site.
 View Logs: Responsible for checking the logs of different system
User for auditing and maintaining the integrity of the system.
 System Reports: The Administrator is responsible to generate
System reports for the future references.
 View All Details: View the users’ details, chatting details, complaint
Details, daily service transaction details.
 Back Up data: The Administrator is responsible to back up all the
Data at a particular time every day.
Kiosk Manager: Responsible to see/adjust appointments, perform day open &

Close activities and calculate his commission.
2
0
kryptonite
 Login: Kiosk Manager can login to the site only if it receives an

Authentication mail from the administrator.
 Appointments: Kiosk Manager can arrange appointments between a
Patient and a doctor.
 View own details: Kiosk Manager can view his details and can also
Update his profile but not its centre name and location.
 Calculate Commission: Kiosk Manager can calculate his
commission at the end of his day activities.
Doctor: Responsible to give appointments, e-prescriptions and can also

view his
Patient’s history.
 Login: A Doctor can login to the site only if it receives an
Authentication mail from the administrator.
 Appointments: The Doctor can approve or give the appointments to
His/her patient.
 Prescriptions: The Doctor can provide the patients with
e-prescriptions.
 Fees: The Doctor can calculate his fees for the prescriptions he/she
Provided it to patients.
 Patients’ History: The Doctor can view his/hers patients’ history
that he attended.
 View own details: The Doctor can view his details and can also
2
1
kryptonite
Update his profile but not its field, company name and location.
Patients: Patients can make online appointment; look their previous

health
Records, doctor’s prescriptions, lab reports and medical expenses.
 Login: Patients can easily register to the site and after verification
They can easily login.
 Appointments: Patients can ask for appointments from their
Respective doctor.
 Prescription: Patients can keep the records of the prescriptions
they’d been given by their respective doctors.
 Health Records: Patients can watch their previous health records in
their profile.
 Lab Reports: Patients can watch their previous lab reports provided
to them from their respective doctors.
 Medical Expense: They can keep a record of all the medical
2
2
kryptonite
expense and watch them in their profile.
3.2 Supplementary Requirements

 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.
 Reduce the cost of a sales transaction - To the extent that one can automate the
sales process through this system, one can start to reduce the cost of those sales
transaction. This is particularly true of mundane sales transactions where the customer
knows what they want.
 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.
 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.
2
3

Virtual Medical Home: System Requirements Specification (SRS)

Uploaded by

Copyright:

Available Formats

You might also like

Virtual Medical Home: System Requirements Specification (SRS)

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Virtual Medical Home: System Requirements Specification (SRS)

Uploaded by

Copyright:

Available Formats

Virtual medical home Version 1.

College Name: MISRIMAL NAVAJEE MUNOTH JAIN ENGINEERING COLLEGE

Date Version Description Author

Sl.no Description Page No.

1.3 Definition, Acronyms, and 6

2.11 Assumptions and 20

3.1 Use Case Reports 20

Software Requirements Specification

In case of any medical error (wrong medication or lab report) patient

Facilitates appropriate communication between all stakeholders -

Support is also provided.

1.3 Definitions, Acronyms, and Abbreviations:

• 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

• WASCE (Web Sphere Application Server Community Edition): It is an application

• WSAD (Web Sphere Studio Application Developer): It is a designer toolkit which is

• HTTP (Hyper Text Transfer Protocol): It is a transaction oriented client/ server

• XML (Extensible Markup Language): It is a markup language that was designed to

1.5 Technologies to be used:

J2EE: (Servlet, JSP, JAXP, Java Beans) Application architecture.

Ajax: Asynchronous Java Script and XML.

XML: Extension Markup Language.

Web 2.0: RSS Feed 2.0.

E-FORMS: electronic form (visual basic)

SOA: service oriented architecture

The VMH objectives for the users are to:

2.0 Overall Description:

2.2 Software Interface:

2.3 Hardware Interface:

Server Side: Optional

2.4 Product Function:

2.5 User Characteristics:

2.7 Architecture Design:

2.8 Use Case Diagram:

2.9 Class Diagram:

2.10 Sequence Diagrams:

2.10.1 Database Design:

2.11 Assumptions and Dependencies:

 Roles and tasks are predefined.

Kiosk Manager: Responsible to see/adjust appointments, perform day open &

 Login: Kiosk Manager can login to the site only if it receives an

Doctor: Responsible to give appointments, e-prescriptions and can also

Patients: Patients can make online appointment; look their previous

expense and watch them in their profile.

3.2 Supplementary Requirements

You might also like