You are on page 1of 38

Business (BRD)

for

Requirements

Document

Healthcare Portal
Version 2.0 [draft]

Prepared !

Pro"ect #ponsor$ Mr. Sadiq Document %um er$ D&002/HC001/BRD Version$ 0.2 'ast (pdated$ )th %o*em er 20+0 ,reation Date$ ++th -cto er 20+0

Business Requirements Document (v02)

HealthCare

.a le of ,ontents
./B'0 -1 ,-%.0%.#.................................................................................................................2 +.2%.R-D(,.2-%.........................................................................................................................3 DOCUMENT PURPOSE........................................................................................................................................4 INTENDED AUDIENCE........................................................................................................................................4 PROJECT BACKGROUND.....................................................................................................................................4 PURPOSE OF THE BUSINESS REQUIREMENTS..........................................................................................................5 BUSINESS GOALS/OBJECTIVES TO BE ACHIEVED....................................................................................................6 BENEFITS/RATIONALE.......................................................................................................................................6 STAKEHOLDERS................................................................................................................................................6 DEPENDENCIES ON EXISTING SYSTEMS..................................................................................................................7 REFERENCES....................................................................................................................................................7 ASSUMPTIONS..................................................................................................................................................7 R04(2R050%.# #,-P0.............................................................................................................6 TARGETED LANGUAGES OF THE CURRENT SYSTEM............................................................................................ INFORMATION ARCHITECTURE "MEDICAL TOURISM PORTAL#................................................................................ INFORMATION ARCHITECTURE "PORTAL FOR INDIA#............................................................................................. INFORMATION ARCHITECTURE "ADMIN INTRANET AREA# .................................................................................... ! ! $ 4

1(%,.2-%/' R04(2R050%.#.................................................................................................+3 USER PROFILES SPECIFICATION "APPLICABLE TO TOURIST PORTAL AND PORTAL FOR INDIA#..................................... 4 SMS FUNCTIONALITY.................................................................................................................................... 7 PMR FUNCTIONALITY.................................................................................................................................... 7 MAP FUNCTIONALITY / GOOGLE MAP API INTEGRATION................................................................................. 7 VIRTUAL OFFICE / CLINIC MANAGEMENT APPLICATION.......................................................................................... % ADVERTISEMENT / BRANDING / ROTATING BANNER MANAGEMENT...........................................................................$! JOBS FUNCTIONALITY.......................................................................................................................................$! SEARCH / ADVANCE SEARCH............................................................................................................................$! COMMUNICATION / &ORK FLO&S.....................................................................................................................$! BUILDING CONSUMER DATABASE.......................................................................................................................$ MANAGE DATABASE FOR PHARMACISTS/DRUG STORES/ DIAGNOSTICS CENTERS AND LOCATE THEM IN GOOGLE MAP...$ COMMUNITY SERVICES / CORPORATE SOCIAL RESPONSIBILITY................................................................................$ CONNECT "CONSUMER' SERVICE PROVIDER "DOCTOR' DRUG STORE' DIAGNOSTIC CENTER#.......................................$ INTERACTIVE FORMS.......................................................................................................................................$ SERVICE REQUEST..........................................................................................................................................$ CONTACT US .................................................................................................................................................$( FEEDBACK.....................................................................................................................................................$( (. . .PUBLISH BASIC SERVICES "HEALTH TOURIST PORTAL#...............................................................................$4 D/./ R04(2R050%.# (50D2,/' .-(R2#. P-R./')..........................................................27 DATA ARCHITECTURE / METADATA..................................................................................................................$5 Entity Relationship Diagram................................................................................................................27 DATA VOLUMES............................................................................................................................................$% DATA RETENTION AND ARCHIVING...................................................................................................................$% PRIVACY IMPLICATIONS...................................................................................................................................$% DATA DEFINITION REPORTS.............................................................................................................................$) Entity Definition Report........................................................................................................................29 D/./ R04(2R050%.# (P-R./' 1-R 2%D2/).........................................................................80 DATA ARCHITECTURE / METADATA "FOR PORTAL IN INDIA#................................................................................(!

Last revised:

Page 2 of !

Business Requirements Document (v02)

HealthCare

#0,(R2.9 R04(2R050%.#......................................................................................................80 AUTHENTICATION...........................................................................................................................................(! AVAILABILITY REQUIREMENTS.........................................................................................................................( USABILITY REQUIREMENTS..............................................................................................................................($ SYSTEM HELP REQUIREMENTS.........................................................................................................................($ PERFORMANCE REQUIREMENTS ........................................................................................................................(( SCALABILITY REQUIREMENTS...........................................................................................................................(( User Scalability....................................................................................................................................33 Application Scalability..........................................................................................................................33 2%.0R1/,0 R04(2R050%.#...................................................................................................88 USER INTERFACE REQUIREMENTS......................................................................................................................(( SYSTEM INTERFACE REQUIREMENTS..................................................................................................................(4 PR-:0,. P'/% /%D D0'2V0R9 #,H0D('0..........................................................................87 7. PROJECT SCHEDULE..................................................................................................................................(5 7.$ PROJECT SCHEDULE..................................................................................................................................(5 ,-55(%2,/.2-% P'/%............................................................................................................8) %. PROPOSED COMMUNICATION PLANS............................................................................................................(6 PROJECT TEAM .............................................................................................................................................(6 ESCALATION POINTS.......................................................................................................................................(6 R0V2#2-% '-;............................................................................................................................86 /PP0%D2,0#..............................................................................................................................86 /PPR-V/'..................................................................................................................................8<

Last revised:

Page

of !

Business Requirements Document (v02)

HealthCare

+. 2ntroduction
Document Purpose

The purpose of this document is to describe business requirements of Hea thcare porta comp ete !" accurate ! and unambi#uous ! in Techno o#!$independent manner. % attempts ha&e been made in usin# most ! business termino o#! and business an#ua#e 'hi e describin# the requirements in this document. (er! minima and common ! understood Technica termino o#! is used. (se case / Desi=ner approach is used in mode in# the business requirements in this document.

2ntended /udience
The main intended audience for this document are the business o'ners of the proposed s!stem. This document shou d be readab e b! business o'ners of the proposed s!stem. The! must be ab e to &erif! that their business requirements ha&e been documented here comp ete !" accurate ! and unambi#uous !. Data %rchitects" %pp ication %rchitects and Technica %rchitects 'ou d a so find the information in this document usefu 'hen the! need to desi#n a so ution that 'i address these business requirements. Since the requirements are documented here in Techno o#!$independent manner" the end$ users of the s!stem shou d be ab e to comprehend the requirements fair ! easi ! from this document.

Pro"ect Bac>=round
Medica tourism industr! in )ndia is #ro'in# rapid ! and this industr! is estimated at Rs. 1"*+0 cores ,Source- )ndian ./press. Tue 0ct 0+ 2010 http-//'''.indiane/press.com/ne's/$$C12$ 'indfa $a'aits$medica $tourism$$/3*2*+044 5or )ndian doctors" 'estern shores cou d be #reener. But for an increasin# number of forei#n patients" )ndian hospita s are fast becomin# their first choice. 0&er 1.+ a6h medica tourists tra&e ed to )ndia in 2002 a one" brin#in# in earnin#s of 7800 mi ion. Since then" the number of such tra&e ers has been increasin# b! at east 2+9 e&er! !ear. % C))$Mc:inse! report pro;ects that earnin#s throu#h medica tourism 'ou d #o up to 72 bi ion b! 2012. ,SourceTimes of )ndia. %pr <" 200= http-//timesofindia.indiatimes.com/india/Medica $tourism$boomin#$in$ )ndia/artic esho'/2*2<2+2.cms4 >eop e rush to )ndia for treatment because it is 8+ to <09 esser than the treatment cost in ?S%. )t is not ;ust cost" )ndia has #ot specia ist around the 'or d and 'or d eminent Doctors/Hospita s 'here there to pro&ide a ser&ices to the patient. .n# ish spea6in# is another ad&anta#e 'here patients can address/communicate 'ithout an! difficu ties.

Last revised:

Page " of !

Business Requirements Document (v02)

HealthCare

)ndia is one of the most fa&orab e tourist destinations in the 'or d. Medica treatment combines 'ith tourism 'ou d #i&e an added ad&anta#e to the customer. There are treatments i6e denta and cosmetic sur#er! 'hich are cate#ori@ed as non$ ife threat are most ! not co&ered under the hea th insurance. These treatments are char#es e/orbitant price in ?S%. % person can #et 'or d c ass treatment in )ndia and 'ou d i6e to ta6e ad&anta#e of )ndiaAs ancient tradition and e/p ore &arious p aces and sti sa&e hu#e sum. B%BCC hea thcare is an internet 'eb porta to pro&ide not$hea th ris6 medica tourism ser&ices to the peop e of ?S% and bui d a database of Hospita s" C inics" Doctors and 5aci ities pro&ided b! each Hospita /C inic in )ndia. The porta 'ou d potentia ! # o' and come to fu b o'n ser&ices in due course of timeD ho'e&er to start 'ith it is tar#eted to pro&ide medica tourism ser&ices i6e Denta and Cosmeto o#!. To'ards bui din# of database" can start 'ith ma;or metropo itan cities i6e H!derabad" Ben#a uru" De hi" Mumbai" :o 6ata" Chandi#arh" Chennai" >une" %hmedabad" 2oa and consider to be phase$1 of the pro;ect.

Purpose of the Business Requirements


This section describes the purpose of the Business Requirements.

Business requirements for ma;or enhancements to an e/istin# app ication. Business requirements for ne' app ication de&e opment. Business requirements for rep acement app ication de&e opment. Business requirements for a request for proposa s ,R5>4.

Last revised:

Page # of !

Business Requirements Document (v02)

HealthCare

Business ;oals?- "ecti*es to e achie*ed


The ob;ecti&e of this porta is to attract peop e from ?S% to &isit )ndia as a medica tourist. % so a database of Doctors" Hospita s" C inics and faci ities 'ou d he p common peop e to search and #et ri#ht treatment. >eop e 'ou d ha&e an opportunit! to chec6 &arious a ternates a&ai ab e to them and compare price of one 'ith the other. 2enerate 100E number of eads and con&ert into +0 number of business opportunit! in a month Bui d database of 10"000 number of hospita sD 2+"000 number of c inicsD 2+0"000 number of Doctors in a phased manner ,cit! 'ise4 Tar#eted cities in )ndia Compare ser&ices of one 'ith other in a simi ar cate#or! 5eature &arious tourist and &isitin# p aces in )ndia 5eature hote s and p aces of accommodation Sho'casin# ?S office address and a person attendin# queries Channe i@in# contacts and si#nin# Mo?s 'ith &arious corporate hospita s Beta re ease tar#et date % pane of doctors in the compan! board 'ou d #i&e an added ad&anta#e

Benefits?Rationale
This section describes the ma;or benefits to be achie&ed 'ith the imp ementation of the Business Requirements.

#ta>eholders
>ro;ect sponsors Hospita s/C inics in )ndia Doctors in )ndia Medica tourists ,Customer4 >atients in )ndia 1eb$site &isitors >harmaceutica Companies Dia#nostic Centers >atients in #enera Fob see6ers .mp o!ers

Last revised:

Page $ of !

Business Requirements Document (v02)

HealthCare

Dependencies on e@istin= s!stems


This section describes the dependencies bet'een the %pp ication for 'hich these Business Requirements are 'ritten and the other e/istin# app ications/s!stems. Got app icab e

References
>ro;ect Charter (er.02

/ssumptions
This section describes ma;or assumptions that 'ere made prior to or durin# the Business Requirements #atherin# and documentation.

Requirements #cope
%his section sho&s &hat 'usiness functionalit( is in sco)e and out of sco)e for *m)lementation+ *n ,se case a))roach- the out of sco)e ,se cases are indicated in a se)arate 'oundar( 'o.+ *n /racle Designer a))roach the out of sco)e 0unctions are sho&n in gre( coloured 'o.es+ 1. Pu lic facin= Ae sites (Health tourist portal and 2ndian portal) should ha*e Aorld class desi=n templates. 5unctiona ! there are t'o separate pub ic facin# 'ebsites. 0ne is to promote hea th tourists and the other is for )n 2. Content of the 'ebsite 'ou d chan#e dependin# upon the tar#eted audience and mana#ed throu#h countr! )> ,i.e. different oo6 and fee for ?S% and )ndian &isitors4. (irtua ! it is t'o different 'ebsites. 8. % the contents are to be mana#ed throu#h a pass'ord protected admin intranet ,to pub ish formatted te/t" ima#es" &ideos <. %dmin intranet 'i ha&e &arious user e&e to access/not to ha&e access to certain data +. >ub ish basic ser&ices H identified in the 1st phase ,non ife ris6 medica tourists4 3. >ub ish anci ar! ser&ices ,(isitin# p aces" hote s etc.4 I. Customer can compare ser&ices and pricin# on the porta =. Customer can submit an enquir! form 'hich is considered to be a business ead *. % the communication 'ith the customer shou d be mana#ed throu#h the admin intranet 10. ./tensi&e search faci it! ,simp e and ad&anced search4

Last revised:

Page 1 of !

Business Requirements Document (v02)

HealthCare

11. )nte#ration 'ith 2oo# e Map %>) ,Shou d be the first of its 6ind information4 5aci it! to update b! the indi&idua &isitor i6e updatin# address/ ocation in the 2oo# e map. 12. Fobs section ,>ost ;obs" Search ;obs re ated to hea thcare ser&ices4 18. Brandin# and ad&ertisin# b! &arious ser&ice pro&iders ,Jistin# of hospita s/c inics" Jistin# of doctors" >harmaceutica companies" Ge' product re eases" re ated ser&ices i6e %mbu ance" Supp iers etc.4 1<. (irtua office for Doctors H 0n ine appointment" s!nc ca endar in smart phones ,This ma! attract some Doctors to be part of this initiati&e4. 1+. C inic mana#ement soft'are H SaaS soft'are to mana#e sma c inic/independent doctors 13. Bui din# consumers database 'hich 'ou d he p in the future to mar6et 1I. Ge's feeds 1=. .mai inte#ration 1*. SMS inte#ration 20. Communit! ser&ices/Corporate Socia Responsibi it! ,)f the customer is poor and cou d not ocate a doctor" 'e 'i he p them ocatin# ri#ht doctor4 21. >MR ,>ersona Medica Record4 22. Mana#e data bases of >harmacists/Dru# stores and ocate them in 2oo# e Map 28. Connect ,Consumer" Ser&ice pro&iders ,Doctors" Dru# stores" Dia#nostic centers etc..4

+. Be site. The 'ebsite contains a home pa#e describin# the purpose and na&i#ationa in6s to other sections. .ach na&i#ation in6 ta6es the 'eb site &isitor to a separate pa#e. Some pa#es i6e ,%bout us" Ser&ices" Contact us" 1h! 'e4 and na&i#ations in6s described in the respecti&e )%. T!pica 1ebsite f o' H Tourist porta -

Last revised:

Page ! of !

Business Requirements Document (v02)

HealthCare

%bout us

Jo#in

Ser&ices

Ho' 'i it Benefit m e K

Contact

Jatest Ge's

Testim onia s

Contact Sa es

Last revised:

Page 2 of !

Business Requirements Document (v02)

HealthCare

.ar=eted 'an=ua=es of the current s!stem


The pub ic facin# 'ebsite of the Hea th tourist porta contents to be a&ai ab e in the fo o'in# an#ua#esi. ii. .n# ish Spanish

.n# ish is the defau t an#ua#e 'hen 'ebsite is open. There 'ou d be an option 'here user can chan#e the an#ua#e. % options" menus" tit es" abe s and on$screen messa#es are to be chan#ed to LSpanishM 'hen the user se ect an#ua#e option. )t shou d be an eas! to use admin interface to create/update an#ua#e equi&a ents for a re e&ant sections. .n# ish is the primar! an#ua#e for the )ndian porta .

2nformation /rchitecture (5edical .ourism Portal)

Last revised:

Page 30 of !

Business Requirements Document (v02)

HealthCare

1ebsite Ja!out ,Medica tourist porta 4

Jo#o

&*+,-.* /01*/.-.2*
Banner section to e/p ain the 1ebsite / ser&ices features

Ji&e Chat section

(isitin# > aces in )ndia

Compare ser&ices section

Ser&ice cate#ories section

C ient testimonia s

Jatest Ge's

Cop!ri#ht NNNNN

>ri&ac! O Disc aimers O Terms of use

Last revised:

Page 33 of !

Business Requirements Document (v02)

HealthCare

2nformation /rchitecture (Portal for 2ndia)

Last revised:

Page 32 of !

Business Requirements Document (v02)


1ebsite Ja!out ,>orta for )ndia4

HealthCare

Jo#o

1ebsite name/tit e

Space for %d. banner

Ji&e Chat section

Hospitals

,linics

Dia=nostics

Doctors

:o s #u mi. Space for ne' products re eased

Search Here
./. 2enera >h!sician in H!derabad" %bids

S'itch to %d&ance Search

Space for disp a!in# comparisons

Cop!ri#ht NNNNN

>ri&ac! O Disc aimers O Terms of use

Last revised:

Page 3 of !

Business Requirements Document (v02)

HealthCare

2nformation /rchitecture (/dmin 2ntranet /rea)

1unctional Requirements
(ser Profiles #pecification (/pplica le to .ourist portal and Portal for 2ndia)
This section describes a the %ctors and their profi es 'ithin the conte/t of the Business Requirements ein= documented. /n /ctor is a personC or=aniDation or an e@ternal s!stem/sub$s!stem/pro#ram that has interactions 'ith the %pp ication. %ctors" b! definition" are e/terna to the s!stem 'ith 'hich the! are ha&in# interactions. %ctors ha&e #oa s that are achie&ed b! use cases. T!pica !" %ctors ha&e beha&iour and are represented b! the ro es the! p a! in the use cases. %n %ctor stimu ates the s!stem b! pro&idin# input and/or recei&in# somethin# of measurab e &a ue from the s!stem.

Last revised:

Page 3" of !

Business Requirements Document (v02)

HealthCare

Super %dmin ?serSuper %dmin user has contro o&er the comp ete s!stem and can mana#e to create other users" #roups" pri&i e#es and required master data. The functiona it! of the comp ete app ication is modu ari@ed and access to each modu e is set b! the app icationAs access contro matri/. T!pica user access contro matri/Roles &&E 5ana=e ;roups 5ana=e (sers 5ana=e parameters /dmin %dd P P Business P P P P

.dit P P

De P P

(ie' P P

Super admin can inacti&ate certain 2roups/?sers/5eatures for some reason before de etin# permanent !. The user ha&in# admin pri&i e#e can acti&ate or inacti&ate a record. % data &ie' ist can ha&e the option to see %cti&e and )nacti&e records. %ccesses to indi&idua acti&it! are fi/ed as per the user c assification and ro e. Super %dmin ?ser

U,*3 N01* P0,,4536 OK C0/7*2

2roup and ?ser Mana#ement

Mana#e Business >arameters

Content Mana#ement

C ient re ationship mana#ement

Communication Mana#ement

Last revised:

Page 3# of !

Business Requirements Document (v02)

HealthCare

%dministrator%dministrator is another user 'ho inherits some contro s from the super admin to perform certain acti&ities. 2enera ! admin user has a the ri#hts of L%dd/.dit or De ete a record. There can be mu tip e admin users.

Content De&e operContent de&e oper is another user 'ho #enera ! create ne' contents/edit the content but does not ha&e ri#ht to de ete permission. Content created or edited 'ou d not be pub ished unti it is has be re&ie'ed or appro&ed b! the >ub isher.

Content >ub isherContent pub isher 'i re&ie'" appro&e or disappro&e an! content to be pub ished in the pub ic area.

1ebsite (isitor%n! 'ebsite &isitor 'i ha&e access to a the pub ic contents pub ished in the 'ebsite. 1ebsite &isitor can search and consume a ser&ices 'hich are set as free ser&ices.

Re#istered ?serRe#istered users 'i ha&e pri&i e#es to access certain pri&ate data and communicate 'ith the ser&ice pro&iders.

CustomerCustomer is a user 'ho 'ou d ha&e access to paid ser&ices.

Last revised:

Page 3$ of !

Business Requirements Document (v02)

HealthCare

#5# 1unctionalit!
a. %b e to confi#ure at east 8 ser&ice pro&iders %>) for sendin# SMS. b. %b e to send bu 6 SMS b! the 'ebsite admin/users to the &arious sta6e ho ders. c. %b e to confi#ure in the %dmin internet to send SMS for &arious acti&ities ,./amp e a ne' ead is recei&ed" confirmation to customer that his enquir! is recorded etc..4 d. Re#istered users / customers can send SMS after o#in e. %b e to a ocate number of SMSs a customer can a&ai free and subscribe for more SMSs ,most ! app icab e for &irtua office and re easin# ne' products4

P5R 1unctionalit!
a. b. c. d. e. f. #. %b e to update demo#raphics / persona records %b e to update demo#raphics of the fami ! members %b e to update Doctors information %b e to up oad prescriptions ,as attachments4 %b e to update prescriptions as te/t %b e to setup medication %b e to setup a erts ,.mai and SMS4 'ith re#ard to re#u ar chec6ups" medicine and doses h. %b e to share medica records 'ith the doctor for a particu ar period 'ith permissions ,(ie' on ! / (ie' and Do'n oad4

5/P 1unctionalit! ? ;oo=le 5/P /P2 inte=ration 0. %b e to ocate Doctors" Hospita s" C inics" Dru# Stores" Dia#nostic Jabs on a
M%>. b. Disp a! different icons for each cate#or! of information. c. )cons are updated throu#h %dmin intranet for each cate#or! of information. d. %b e to disp a! more information throu#h a ca $out 'hen user point on a particu ar icon. e. %b e to &ie' more information in a separate pa#e 'hen user opted to 6no' more about se ected information. f. ?ser can ab e to submit feedbac6s to the site o'ner for an! se ected information. #. ?ser can ab e to report an! errors to the site o'ner for an! se ected information. h. The feedbac6s / errors reported b! the users are emai ed/sms to the respecti&e site admin/user. -. The feedbac6 / reported errors are stored in the admin intranet. ;. The user is reported bac6 'hen the corrections are done or feedbac6 are ac6no' ed#ed. 8. (isitors can add a ocation ,Doctor/Hospita /C inic/Medica store/Dia#nostics4 if the! fee so b! fi in# a sma form. The Jatitude and Jon#itude shou d be pic6ed up automatica !. . The information submitted are stored separate ! for the admin to re&ie' and appro&e or disappro&e.

Last revised:

Page 31 of !

Business Requirements Document (v02)

HealthCare

1. % messa#e emai /sms sent to the user 'ho submitted 'hen the admin
appro&e / disappro&e. )f the admin disappro&e the reason shou d be fi ed and intimated.

Virtual office ? ,linic mana=ement application 0. %pp ication is based on SaaS ,Soft'are as a ser&ice4 mode +. %b e to pro&ide a separate area for each customer ,Doctor/c inic4 and
accessed throu#h a user name and pass'ord c. .ach customer can si#n$up to a&ai this faci it! d. Customer can opt$out this ser&ice b! sendin# an emai /ca in# to a site admin / support request. e. %dmin can acti&ate / inacti&ate this ser&ice for a customer f. 5o o'in# are the faci ities inc uded in the (irtua officea. Customer ,Doctor/C inic4 update their p ace of a&ai abi it!" timin#s for a particu ar period ,Da!" Time" Got a&ai ab e time etc..4 +. (isitors ,>atients4 can &ie' the ca endar or schedu e an appointment c. Customer to &ie' the ca endar and ist of appointments d. Customer can accept / re;ect one or a appointments for a da! or period e. )nformation #oes to the patients 'hen Doctor/C inic accepted or re;ected an appointment b! emai / sms f. Record/update patient &isits #. %b e to #enerate a bi for the ser&ices h. %b e to 'rite a prescription for the patient i. %b e to #enerate a medica certificate for the patient ;. %b e to recommend/order a dia#nostics #. SaaS %rchitecture 1. 5u ! Shared DB >er Tenant

Last revised:

Page 3! of !

Business Requirements Document (v02)

HealthCare

The proposed app ication shou d be dep o!ed on SaaS p atform. The app ication shou d ta6e care of the fo o'in# 'hi e desi#nin# the app ication. >erformance Securit! Re iabi it! Customi@ation )nte#ration Sca abi it! Mu ti tenanc!

There are t'o a!ers. DB a!er and %pp ication Ja!er. 0r#ani@ation )D is the 6e! for a database tab es ,Master and transaction4. Data is accessed from the app ication b! pro&idin# 0r#ani@ation )D. .&er! user is associated 'ith an or#ani@ation id. %n or#ani@ation can ha&e man! users. ?ser )D is unique throu#hout the database. There are t'o databasesD one to store a data re ated to user" contains ,username" pass'ord" or#ani@ation id4 for authentication and the other is database contains data re ated to app ication.

Last revised:

Page 32 of !

Business Requirements Document (v02)

HealthCare

2?)D is used for or#ani@ation id. Mu tip e or#ani@ation data can reside in a sin# e database or mu tip e of databases.

/d*ertisement ? randin= ? rotatin= anner mana=ement


a. %b e to define the ad p acements in &arious pa#es b. %b e to define price for ad p acements ,ad si@e / duration / price4 7. %b e to update/up oad ad content for a ocation 'ith priorit!" number of impressions" time period etc.. d. %b e to mana#e the ad banners and content throu#h admin area

:o s functionalit!
a. %b e to search ;ob openin#s b! enter search te/t" e/perience/ ocation. b. %b e to respond/send resume for a ;ob direct ! after o#in 7. %b e to pub ish ist of recent ;obs b! function and ocation 6. %b e to pub ish top 10 emp o!ers 'ith their o#os. Disp a! ist of current ;ob openin#s. e. %b e to re#ister and up oad resume b! the ;ob see6ers f. %b e to o#in and update resume b! the ;ob see6ers #. .mp o!ers to re#ister and update ;ob openin#s h. .mp o!er o#in and search resumes i. Do'n oad matchin# resumes for a particu ar post 9. .mai to ;ob see6er 'hen a ne' matchin# ;ob is updated b! the emp o!er 6. .mai to emp o!er 'hen a ne' matchin# resume is updated b! a ;ob see6er. . B oc6 resumes to be &ie'ed b! certain companies ,b! enterin# 6e! 'ords of the companies4 b! the ;ob see6er for mana#in# pri&ac!

#earch ? /d*ance search


a. Basic search shou d 'or6 i6e 2oo# e search 'ith su##estions b. ?ser can shift to ad&ance search and search throu#h se ectin# fi ters and criteria

,ommunication ? Bor> floAs


a. The &isitors to the 'ebsite shou d ab e to communicate 'ith the site admin / ser&ice pro&iders b! fi in# pre$defined forms. +. % confirmation messa#e shou d be sent to the person 'ho submitted b! emai as a cop! for hi/her record. c. %part from sa&in# data in a database tab e 'hich can be accessed throu#h admin intranetD a information shou d be sent to respecti&e site user / ser&ice pro&ider dependin# on the 6ind of ser&ice request. d. 1or6$f o's are defined in the admin intranet ,i.e. mai to 'hom" access to 'hom4

Last revised:

Page 20 of !

Business Requirements Document (v02) Buildin= consumer data ase

HealthCare

a. Consumers are the users 'ho search/see6 &arious ser&ices and submits request for ser&ices in &arious forms. Re#istered / non re#istered users. b. % the information are to be compi ed and cate#ori@ed for future ser&ices i6e ,'hen ne' product / ser&ices are re eased.4 7. %b e to attract consumer to re#ister to #et &a ue added ser&ices.

5ana=e data ase for Pharmacists?Dru= stores? Dia=nostics centers and locate them in ;oo=le 5ap
a. %b e to search and ocate a dru# store / dia#nostic ser&ices +. %b e to compare prices for different tests bet'een the dia#nostic centers in a particu ar oca it!.

,ommunit! ser*ices ? ,orporate social responsi ilit!


a. >eop e re#ister as ser&ice pro&ider / &o unteer to e/tend their ser&ices. +. >eop e request to for ser&ices ,./amp e- Joo6in# for he p to ocate a doctor for a particu ar disease" Joo6in# for he p. c. %b e to connect bet'een the ser&ice pro&iders 'ith ser&ice see6ers

,onnect (,onsumerC #er*ice pro*ider (DoctorC Dru= storeC Dia=nostic center)


a. %b e to create a p atform to connect bet'een the consumer and ser&ice pro&ider and brin# them into to a common p atform. b. The information shou d be f ashed to nearest Dia#nostics center 'hen Doctor prescribes tests. c. Consumer / >atient can compare price for different tests

2nteracti*e 1orms #er*ice Request


(se ,ase %ame Description /ctors Business Rules Submittin# on ine form Submittin# on ine form in the 'ebsite >rospecti&e medica tourist ,Customer4

. 5orm can be submitted on ! after the user


comp ete fi in# a the required data. 2. ?ser can s'itch to detai ed form / pro&ide more information if he/she 'i in# to pro&ide at that moment b! e/pandin#

Last revised:

Page 23 of !

Business Requirements Document (v02)

HealthCare

Basic 1loA 1. 0n screen than6 !ou messa#e. $. .mai confirmation to the customerAs emai address as a cop! of the information submitted. (. .mai notification to the business head/concerned e/ecuti&e. 4. Sa&e data in the database for reportin#

section of the form. /lternate 1loAs 1. The ser&ice request form can be submitted ,after censorin#4 direct ! to the affi iate hospita s ,Ser&ice pro&iders4 to submit their quotes. 2. The business head/concerned e/ecuti&e 'i re&ie' and submit the form to Ser&ice pro&iders.

Last revised:

Page 22 of !

Business Requirements Document (v02)

HealthCare

,ontact us
(se ,ase %ame Description /ctors Submittin# contact us form Submittin# on ine form in the 'ebsite >rospecti&e medica tourist ,Customer4 1ebsite &isitors >rospecti&e ser&ice pro&iders ,1anted to ist in the porta 4 1. 5orm can be submitted on ! after the user comp ete fi in# a the required data. /lternate 1loAs

Business Rules Basic 1loA 1. 0n screen than6 !ou messa#e. $. .mai confirmation to the emai address pro&ided as a cop! of the information submitted. 8. .mai notification to the business head/concerned e/ecuti&e. 4. Sa&e data in the database for reportin#

1eed ac>
(se ,ase %ame Description /ctors Business Rules Basic 1loA 1. 0n screen than6 !ou messa#e. 2. .mai confirmation to the emai address pro&ided as a cop! of the information submitted. 8. .mai notification to the business head/concerned e/ecuti&e. <. Sa&e data in the database for reportin# Submittin# feedbac6 on ine Submittin# an on ine form in the 'ebsite 1ebsite &isitors 2. 5orm can be submitted on ! after the user comp ete fi in# a the required data. /lternate 1loAs

Last revised:

Page 2 of !

Business Requirements Document (v02) 8.+.+. Pu lish Basic #er*ices (Health .ourist Portal)

HealthCare

The content is mana#ed in the admin section and pub ished in the home pa#e and ser&ices section. ?ser can e/p ore to 6no' more information ,i.e. Jist of ser&ice pro&iders" their faci ities" pricin# etc4 on se ectin# a particu ar ser&ice. % so" user can compare price bet'een ser&ice pro&iders for a se ected ser&ice cate#or!.

Last revised:

Page 2" of !

Business Requirements Document (v02)

HealthCare

Data Requirements (5edical tourist portal)


The content and data required for the porta is co ected from &arious sources and updated throu#h the admin contro pane b! the authori@ed users. The content/data pub ished on ! after it has been &erified and appro&ed b! the pub isher. 2nitiall! all the rele*ant data updated ! the portal administrator and pro=ressi*el! an e@tranet s!stem can e de*eloped Ahich Aould ena le the ser*ice pro*ider to update data throu=h secure lo=in. 1. Core ser&ices H )nformation about &arious hospita s / c inics" their ser&ices" faci ities" pricin# etc. 2. %nci ar! ser&ices a. )nformation about &arious tourist p aces b. )nformation about hote s c. )nformation about tra&e s (. 0ther ser&ices H Re ated ne's and updates

Data /rchitecture ? 5etadata


1. )nformation about a Hospita /C inic i. Game and address ii. Contact te ephones a. 2enera b. .mer#enc! c. .ach specia i@ation iii. .mai s i&. Jocation and direction &. >hotos &i. Specia ities / Ser&ice cata o#ue &ii. %chie&ements &iii. Testimonia s i/. 5aci ities a. >harmac! b. Canteen c. Dia#nostics /. )nfrastructure 0. Ma;or equipments b. Ma6e 7. >hotos /i. 0Ts a. T!pe b. Specia about theatre c. >hotos /ii. Doctors a. Game and contacts b. Specia i@ation c. ./perience d. %chie&ements

Last revised:

Page 2# of !

Business Requirements Document (v02)


e. Testimonia s

HealthCare

2.

)nformation about a (isitin#/Historica p ace i. Game ii. Short description iii. %ddress/Jocation i&. )mportance &. >hoto#raphs

8. )nformation about a Hote s i. Game ii. Short description iii. %ddress/Jocation i&. Tariff &. >hoto#raphs <. )nformation about a Tra&e i. Game ii. Short description iii. %ddress/Jocation i&. Tariffs +. Ge's 5eeds i. ii. iii. i&. &. &i. &ii. )nte#rate 'ith re ated ne's feeds Create an interface to up oad ne's Ge's tit e Date Source Te/t ima#es

6. Corporate contents ,CMS4


i. %bout us a. Te/t b. >hotos ii. Ser&ices a. Ser&ice cate#or! b. Ser&ice description c. >hotos iii. 1h! 'e a. Te/t b. >hotos I. 5%Qs ,CMS4 i. Question ii. %ns'er =. Ser&ice 'ise price comparison i. Ser&ice cate#or! ii. Ser&ice description iii. >rice in ?S7 i&. 0ther char#es if an! ?S7

Last revised:

Page 2$ of !

Business Requirements Document (v02)


0ntit! Relationship Dia=ram

HealthCare

Last revised:

Page 21 of !

Business Requirements Document (v02)

HealthCare

Data Volumes
Health .ourist Portal$ )nitia 10 2B inc udin# ima#es and annua #ro'th cou d #o up to 109 Portal for 2ndia$ )nitia 20 2B inc udin# ima#es and annua #ro'th cou d #o up to 209

Data Retention and /rchi*in=


This section describes the Data retention ,time frames for on ine Data retention before archi&in#4 and a so the archi&in# requirements.

Pri*ac! 2mplications
This section describes the sensiti&it! e&e s of each c ass of data. The fo o'in# criteria are used in determinin# the sensiti&it! e&e of each conceptua c ass/entit! in ine 'ith the 2o&ernment Core >o ic! Manua 4.

Non-sensitive information that &ould not reasona'l( 'e e.)ected to cause in4ur( (harm) if released to the )u'lic5 Protected A: information that- if com)romised- could reasona'l( 'e e.)ected to cause in4ur( (harm)- e+g+ loss of )rivac(5 Protected B: information that- if com)romised- could reasona'l( 'e e.)ected to cause serious in4ur( (harm)- e+g+ the conduct of a court )roceeding &ould 'e adversel( affected5 Protected C: information that- if com)romised- could reasona'l( 'e e.)ected to cause e.tremel( grave in4ur( (harm)- e+g+ loss of life+

Last revised:

Page 2! of !

Business Requirements Document (v02)

HealthCare

Data Definition Reports


0ntit! Definition Report
This section is app icab e on ! to 0rac e Desi#ner approach. This section describes Data %rchitecture / definition ,.ntit! Re ationship mode 4 in narrati&e te/t form.
0ntit! %ame 0ntit! Description

2nitial Data Volume (appro@.) /nnual Data =roAth rate (in appro@. F) /ttri utes (fields) of the 0ntit!

Game Description Game Description Game Description Game Description Game Description Game Description -

Last revised:

Page 22 of !

Business Requirements Document (v02)

HealthCare

Data Requirements (Portal for 2ndia)


The content and data required for the porta is co ected from &arious sources and updated throu#h the admin contro pane b! the authori@ed users. The content/data pub ished on ! after it has been &erified and appro&ed b! the pub isher. 2nitiall! all the rele*ant data updated ! the portal administrator and pro=ressi*el! an e@tranet s!stem can e de*eloped Ahich Aould ena le the ser*ice pro*ider to update data throu=h secure lo=in.

. Core ser&ices H )nformation about &arious Hospita s" C inics" Doctors" Dia#nostic" 5aci ities
pro&ided b! them and pricin# etc.

$. %nci ar! ser&ices


Fobs Ge' product re eases %d&ertisement 0ther ser&ices H Re ated ne's and updates

(.

Data /rchitecture ? 5etadata (for Portal in 2ndia)

#ecurit! Requirements
/uthentication
This section describes the %uthentication requirements part of the Business Requirements. %uthentication is the process of &erif!in# the #enuineness of c aims that a person/#roup ma6es to estab ish identit!/e i#ibi it! for access to ser&ices. The fo o'in# criteria is used in determinin# transaction t!pes of each use case/functionLevel 0 : Anonymous transaction 6 triggers transactions that do not require or allo& a )erson to 'e identified- or transactions &hich require )rotection of a )erson7s identit(+ 0or e.am)le- access to online information a'out government )rograms or services or )rotecting a )erson7s identit(+ Com'ining the transaction data &ith other data must not allo& identification of a )articular individual+ Level 1 : Pseudonymous transaction 6 triggers transactions that do not require a )erson to 'e identified 'ut do require a means for further contact to deliver a )roduct or service+ 0or e.am)le- a note from some)erson899999+com can not 'e readil( translated into an individual:s name- 'ut it ma( 'e sufficient to request information- to )rovide some services- or on;going follo& u)+ Level 2 : Identified transaction 6 triggers transactions that require that a )erson 'e s)ecificall( identified+ %he nature of the transaction ma( require confirmation of a )erson7s identit( (e+g+- name- address- 'irth date- etc+) and<or data lin=ing the )erson to a transaction (e+g+- invoice num'er- )ersonal health num'er- etc+)+ Level 3 : Verified transaction 6 triggers transactions that require: the )erson to 'e s)ecificall( identified5 verification of the integrit( of the data e.changed and the e.change itself5 and- the creation of sufficient evidence to indicate that the )erson agreed to 'e 'ound

Last revised:

Page 0 of !

Business Requirements Document (v02)

HealthCare

'( the transaction+ 0or e.am)le- a note signed &ith a digital certificate- audit trails and securit( logs ma( )rovide sufficient evidence that a s)ecific )erson intended to conduct a transaction+

/*aila ilit! Requirements


The s!stem is a&ai ab e o&er the net. The hea thcare porta is tar#eted to ?S% and >orta for )ndia is tar#eted 'ho e of )ndia. The s!stem 'ou d re$direct to the user based on )> address. )f an!bod! tr!in# to access the Hea thcare porta from )ndia" the s!stem 'i re$direct to >orta for )ndia and &ice$&ersa. The s!stem uptime shou d be **.009. The simi ar bac6 to bac6 #uarantee needs to be obtained from the hostin# compan!. )n case of an! brea6do'n" appropriate messa#e need to be f ashed. 0n$ ine chat to be ad;usted 'ith ?S and )ndia time. Response to user quer! 'ithin 2< hours.

Last revised:

Page 3 of !

Business Requirements Document (v02)

HealthCare

(se ,ase ? Business 1unction %ame

/*aila ilit! Requirements & Re=ular Aor> hours & 23@6 & /n! other (please descri e)

(sa ilit! Requirements


This section describes the s!stem usabi it! requirements. % usabi it! requirement specifies ho' eas! the s!stem must be to use. ?sabi it! is a non$functiona requirement" because in its essence it doesnRt specif! parts of the s!stem functiona it!" but specifies on ! ho' that functiona it! is to be percei&ed b! the user" for instance ho' eas! it must be to earn and operate the s!stem.

#!stem Help Requirements


This section describes 'hat 6ind of S!stem He p features are needed to be bui t into the s!stem.

(se ,ase ? Business 1unction %ame

Help Requirements & 1ield le*el (online) & #creen le*el (online) & Help Printin= -ptions & -perations 5anual (-ffline) & /n! other

Last revised:

Page 2 of !

Business Requirements Document (v02) Performance Requirements


+.+.1. Stress Requirements

HealthCare

Hea th tourist porta s must be ab e to support minimum of 200 user accessin# records simu taneous !. >orta for )ndia must support minimum of +000 users accessin# simu taneous !. +.+.2. Response$Time Requirements The ma/imum a o'ab e 'ait time from the moment the user submits a request unti the s!stem comes bac6 'ith a response shou d not #o be!ond = seconds 'ith the data &o ume 800"000E records

#cala ilit! Requirements


The s!stem shou d be sca ab e to accommodate add ne' ser&ices" enhance e/istin# ser&ices.

(ser #cala ilit!

/pplication #cala ilit!

2nterface Requirements
This section describes ?ser and S!stem )nterface requirements for the proposed s!stem.

(ser 2nterface Requirements


BroAser compati ilit! The 'ebsite shou d support a ma;or bro'sers of the current &ersion and one &ersion do'n. 1. 2. 8. <. ). 5ire 5o/ Mo@i a ,Mac4 Chrome

Last revised:

Page

of !

Business Requirements Document (v02)

HealthCare

Data displa! The content presented in the porta 'ou d be desi#ned professiona ! i6e an! 'or d c ass 'ebsite. The data can be presented in Jist &ie'/5orm &ie' to the sta6eho ders in their respecti&e area. Drop&doAn list Data consistenc! is maintained throu#h se ectin# choices from drop do'n ist. The app ication shou d enab e each customer to add their ne' choices. The master drop do'n ist is mana#ed throu#h the %dmin area. 1hen a customer re#ister" set of master data ,pre$requisites4 are a&ai ab e for them. This 'ou d he p them to start usin# the app ication instant !. % so" each re#istered customer can mana#e their o'n master data ,add/edit/de ete4. #a*in= report as PD1 file. 5aci itates to sa&e a report in >D5 format Be 2.0 features 1ebsite / %pp ication to be bui t on 1eb 2.0 features. >a#e re$ oadin# / refresh to be a&oided comp ete !.

#!stem 2nterface Requirements

Last revised:

Page " of !

Business Requirements Document (v02)

HealthCare

Project Plan and Delivery Schedule


7.1 Project Schedule
#' 1 .as> Definition S!stem Desi#n Detai ed Desi#n De&e opment )nte#ration Testin# Dep o!ment ?%T Bu# fi/in# 2o Ji&e #tart 1inish Duration

6.2

Pro"ect #chedule

Phase Requirement Definition >rotot!pin# /1ire framin# / >orta a!outs

5ilestone BRD Si#noff Ja!out desi#n si#n$off and 1ireframe Si#noff

Deli*era le Business Requirement Document >DS" htm and CSSs >rotot!pe for the proposed app ication

S!stem Desi#n

Comp etion of Desi#n Document

Desi#n document containin# f o's" &a idations" inputs and outputs. Database desi#n Beta &ersion ,Tested fu !4

De&e opment" )nte#ration and Testin# Dep o!ment and 2o Ji&e

Beta Re ease of the site for ?%T 5ina Si#noff

Source Code for the app ication hosted on i&e en&ironment. Source code documentation and ?ser #uide. 5i/ bu#s

Support

C osin#

Last revised:

Page # of !

Business Requirements Document (v02)

HealthCare

Communication Plan
8.1 Proposed Communication Plans
Dai ! ca 1ee6 ! re&ie' meetin# 'ou d be he d on a preschedu ed da! ,NNNNNN4 and time. Re#u ar communication 'ou d be done throu#h emai s" phone and 1ebMeetin# 'ith emai 'ou d be the most frequent communication medium ./tranet porta ,Basecamp4 created for the pro;ect 'ou d be the p atform throu#h 'hich the pro;ect re ated documents" minutes of the meetin# are shared. The tas6s assi#ned for the team members are presented and trac6ed throu#h the porta 1ee6 ! status report shou d be shared 'ith C ient throu#h emai and a so posted to the e/tranet porta b! end of the 'ee6.

Project Team
#' %ame Role -r=aniDation ,ontact %o 0&mail address

0scalation Points
#' %ame Desi=nation -r=aniDation ,ontact %o 0&mail address

Last revised:

Page $ of !

Business Requirements Document (v02)

HealthCare

Re*ision 'o=
ate 2+th 0ct 2010 23th 0ct 2010 Version 01$Draft 02$Draft Jist of 5unctiona it! inc uded for )ndian >orta 1. Communit! /Corporate Socia Responsibi it! 2. >HR ,>ersona Hea th Record4. 8. Mana#e data bases of >harmacists/Dru# stores and ocate them in 2oo# e Map 1. Scope is e/p ained and e/panded 2. SaaS architecture dia#ram is depicted 8. Connect functiona it! is inc uded C!an"e #eference #evie$ed %y

3th Go& 2010

02$Draft

/ppendices

.nter content here.

Last revised:

Page 1 of !

Business Requirements Document (v02)

HealthCare

/ppro*al
This document has been appro&ed as the officia Business Requirements Document for the Hea thCare pro;ect. 5o o'in# appro&a of this document" chan#es 'i be #o&erned b! the pro;ectAs chan#e mana#ement process" inc udin# impact ana !sis" appropriate re&ie's and appro&a s" under the #enera contro of the Master >ro;ect > an and accordin# to >ro;ect Support 0ffice po ic!. Pre&ared %y
%uthorRs Game STit eT S0r#ani@ationT

'i"nature

ate

A&&roved %y
SC ient %cceptorAs GameT STit eT S0r#ani@ationT

'i"nature

ate

Last revised:

Page ! of !