65908736 healthcare project brd v02

8/12/2019 65908736 Healthcare Project BRD v02

1/38

Business Requirements Document(BRD)

for

Healthcare Portal

Version 2.0 [draft]

Prepared !

Pro"ect #ponsor$ Mr. Sadiq

Document %umer$ D&002/HC001/BRDVersion$ 0.2

'ast pdated$ th%o*emer 20+0,reation Date$ ++th-ctoer 20+0


2/38

Business Requirements Document (v02) HealthCare

ale of ,ontents

/B' -1 ,-%%# .............................................................................................................. ...2

+.%R-D,-% ................................................................................................................. ........3

DOCUMENTPURPOSE ........................................................................................................................................4

INTENDEDAUDIENCE ........................................................................................................................................4PROJECTBACKGROUND .....................................................................................................................................4

PURPOSEOFTHEBUSINESSREQUIREMENTS ..........................................................................................................5

BUSINESSGOALS/OBJECTIVESTOBEACHIEVED ....................................................................................................6

BENEFITS/RATIONALE .......................................................................................................................................6

STAKEHOLDERS ................................................................................................................................................6

DEPENDENCIESONEXISTINGSYSTEMS ..................................................................................................................7

REFERENCES ....................................................................................................................................................7

ASSUMPTIONS ..................................................................................................................................................7

R4R5%# #,-P .............................................................................................................6

TARGETEDLANGUAGESOFTHECURRENTSYSTEM ............................................................................................!INFORMATIONARCHITECTURE"MEDICALTOURISMPORTAL# ....................................................................... ...... ...!

INFORMATIONARCHITECTURE"PORTALFORINDIA# .............................................................................................$

INFORMATIONARCHITECTURE"ADMININTRANETAREA# ....................................................................................4

1%,-%/' R4R5%# ............................................................................................. ....+3

USERPROFILESSPECIFICATION"APPLICABLETOTOURISTPORTALANDPORTALFORINDIA# .....................................4

SMS FUNCTIONALITY ....................................................................................................................................7PMR FUNCTIONALITY ....................................................................................................................................7

MAP FUNCTIONALITY/ GOOGLEMAP API INTEGRATION .................................................................................7

VIRTUALOFFICE/ CLINICMANAGEMENTAPPLICATION ..........................................................................................%

ADVERTISEMENT / BRANDING/ ROTATINGBANNERMANAGEMENT ...........................................................................$!

JOBSFUNCTIONALITY .......................................................................................................................................$!

SEARCH/ ADVANCESEARCH ............................................................................................................................$!COMMUNICATION/ &ORKFLO&S .....................................................................................................................$!

BUILDINGCONSUMERDATABASE .......................................................................................................................$MANAGEDATABASEFORPHARMACISTS/DRUGSTORES/ DIAGNOSTICSCENTERS ANDLOCATETHEMINGOOGLEMAP.. .$

COMMUNITYSERVICES/ CORPORATESOCIALRESPONSIBILITY ................................................................................$

CONNECT"CONSUMER' SERVICEPROVIDER"DOCTOR' DRUGSTORE' DIAGNOSTICCENTER# .......................................$

INTERACTIVEFORMS .......................................................................................................................................$

SERVICEREQUEST ..........................................................................................................................................$

CONTACTUS .................................................................................................................................................$(

FEEDBACK .....................................................................................................................................................$(

(...PUBLISHBASICSERVICES"HEALTHTOURISTPORTAL# ...............................................................................$4

D// R4R5%# (5D,/' -R# P-R/') ...................................................... ....27

DATAARCHITECTURE/ METADATA ..................................................................................................................$5Entity Relationship Diagram ................................................................................................................27

DATAVOLUMES ............................................................................................................................................$%

DATARETENTIONANDARCHIVING ...................................................................................................................$%

PRIVACYIMPLICATIONS ...................................................................................................................................$%

DATADEFINITIONREPORTS .............................................................................................................................$)

Entity Definition Report ........................................................................................................................29

D// R4R5%# (P-R/' 1-R %D/) .........................................................................80

DATAARCHITECTURE/ METADATA"FORPORTALININDIA# ......................................................... ...... ...... ...... .....(!

Last revised: Page 2 of !


3/38


#,R9 R4R5%# ......................................................................................................80

AUTHENTICATION ...........................................................................................................................................(!

AVAILABILITYREQUIREMENTS .........................................................................................................................(

USABILITYREQUIREMENTS ..............................................................................................................................($

SYSTEMHELPREQUIREMENTS .........................................................................................................................($

PERFORMANCEREQUIREMENTS ........................................................................................................................((

SCALABILITYREQUIREMENTS ...........................................................................................................................((User Scalability ............................................................................................................................. ...... .33

Application Scalability ..........................................................................................................................33

%R1/, R4R5%# ....................................................................................... ............88

USERINTERFACEREQUIREMENTS ......................................................................................................................((

SYSTEMINTERFACEREQUIREMENTS ..................................................................................................................(4

PR-:, P'/% /%D D'VR9 #,HD' ..........................................................................87

7. PROJECTSCHEDULE ..................................................................................................................................(57.$ PROJECTSCHEDULE ..................................................................................................................................(5

,-55%,/-% P'/% .......................................................................................................... ..8

%. PROPOSEDCOMMUNICATIONPLANS ............................................................................................................(6PROJECTTEAM .............................................................................................................................................(6

ESCALATIONPOINTS .......................................................................................................................................(6

RV#-% '-; ............................................................................................................................86

/PP%D,# .................................................................................................................... ..........86

/PPR-V/' ..................................................................................................................................8une" %hmedabad"oa 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 eistin# appication.

Business requirements for ne' appication de&eopment.

Business requirements for repacement appication de&eopment.

Business requirements for a request for proposas ,R5>4.

Last revised: Page # of !


6/38


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

The ob;ecti&e of this porta is to attract peope from ?S% to &isit )ndia as a medica tourist.

%so a database of Doctors" Hospitas" Cinics and faciities 'oud hep common peope tosearch and #et ri#ht treatment. >eope 'oud ha&e an opportunit! to chec6 &ariousaternates a&aiabe to them and compare price of one 'ith the other.

enerate 100E number of eads and con&ert into +0 number of businessopportunit! in a month Buid database of 10"000 number of hospitas 2+"000 number of cinics 2+0"000number of Doctors in a phased manner ,cit! 'ise4 Tar#eted cities in )ndia Compare ser&ices of one 'ith other in a simiar cate#or! 5eature &arious tourist and &isitin# paces in )ndia 5eature hotes and paces of accommodation

Sho'casin# ?S office address and a person attendin# queries Channei@in# contacts and si#nin# Mo?s 'ith &arious corporate hospitas Beta reease tar#et date % pane of doctors in the compan! board 'oud #i&e an added ad&anta#e

Benefits?Rationale

This section describes the ma;or benefits to be achie&ed 'ith the impementation of theBusiness Requirements.

#ta>eholders

>ro;ect sponsors Hospitas/Cinics in )ndia Doctors in )ndia

Medica tourists ,Customer4

>atients in )ndia

eb$site &isitors >harmaceutica Companies Dia#nostic Centers >atients in #enera Fob see6ers mpo!ers

Last revised: Page $ of !


7/38


Dependencies on e@istin= s!stems

This section describes the dependencies bet'een the %ppication for 'hich these BusinessRequirements are 'ritten and the other eistin# appications/s!stems.

Got appicabe

References

>ro;ect Charter (er.02

/ssumptions

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

Requirements #cope

%his section sho&s &hat 'usiness functionalit is in scoe and out of scoe for *mlementation+*n ,se case aroach- the out of scoe ,se cases are indicated in a searate 'oundar 'o.+ *n/racle Designer aroach the out of scoe unctions are sho&n in gre coloured 'o.es+

1. Pulic facin= Aesites (Health tourist portal and ndian portal) should ha*e Aorldclass desi=n templates.

5unctiona! there are t'o separate pubic facin# 'ebsites. ne is to promote heathtourists and the other is for )n

2. Content of the 'ebsite 'oud chan#e dependin# upon the tar#eted audience andmana#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 ,topubish formatted tet" ima#es" &ideos


8/38


11. )nte#ration 'ith oo#e Map %>) ,Shoud be the first of its 6ind information4 5aciit! toupdate b! the indi&idua &isitor i6e updatin# address/ocation in the oo#e map.

12. Fobs section ,>ost ;obs" Search ;obs reated to heathcare ser&ices418. Brandin# and ad&ertisin# b! &arious ser&ice pro&iders ,Jistin# of hospitas/cinics" Jistin#

of doctors" >harmaceutica companies" Ge' product reeases" reated ser&ices i6e%mbuance" Suppiers etc.4

1MR ,>ersona Medica Record422. Mana#e data bases of >harmacists/Dru# stores and ocate them in oo#e Map28. Connect ,Consumer" Ser&ice pro&iders ,Doctors" Dru# stores" Dia#nostic centers etc..4

+. esite.

The 'ebsite contains a home pa#e describin# the purpose and na&i#ationa in6s to othersections. 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" h! 'e4 and na&i#ations in6s described in the respecti&e)%.

T!pica ebsite fo' Tourist porta-

Last revised: Page ! of !


9/38


Jo#in

Ser&ices

Contact

%bout us

Ho' 'i it

Benefit me K

Jatest Ge's

Testimonias

Last revised: Page of !


10/38


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

The pubic facin# 'ebsite of the Heath tourist porta contents to be a&aiabe in thefoo'in# an#ua#es-

i. n#ishii. Spanish

n#ish is the defaut an#ua#e 'hen 'ebsite is open. There 'oud be an option 'hereuser can chan#e the an#ua#e.

% options" menus" tites" abes and on$screen messa#es are to be chan#ed toLSpanish 'hen the user seect an#ua#e option.

)t shoud be an eas! to use admin interface to create/update an#ua#e equi&aents for aree&ant sections.

n#ish is the primar! an#ua#e for the )ndian porta.

nformation /rchitecture (5edical ourism Portal)



11/38


ebsite Ja!out ,Medica tourist porta4


Jo#o

Banner section to epain the ebsite / ser&ices features

&*+,-* 01*/-2* Ji&e Chat sectio

+ 2 8

(isitin# >aces in

)ndia

Compare ser&ices section

Ser&ice cate#ories sectionCient testimonias

Jatest Ge's

Cop!ri#ht NNNNN >ri&ac! O Discaimers O Terms of


12/38


nformation /rchitecture (Portal for ndia)



13/38


ebsite Ja!out ,>orta for )ndia4


Jo#o ebsite name/titeJi&e Chasection

Cop!ri#ht NNNNN >ri&ac! O Discaimers O Terms of

Search Here #umi

. enera >h!sician in H!derabad" %bids S'itch to %d&ance Search

Space for %d. banner

Space for ne'products reeased

Hospitals ,linics DoctorsDia=nostics :os

Space for dispa!in# comparisons


14/38


nformation /rchitecture (/dmin ntranet /rea)

1unctional Requirements

ser Profiles #pecification (/pplicale to ourist portal and Portal forndia)

This section describes a the %ctors and their profies 'ithin the contet of the BusinessRequirements ein= documented. /n /ctor is a personC or=aniation or an e@ternals!stem/sub$s!stem/pro#ram that has interactions 'ith the %ppication. %ctors" b! definition"are eterna to the s!stem 'ith 'hich the! are ha&in# interactions. %ctors ha&e #oas that areachie&ed b! use cases. T!pica!" %ctors ha&e beha&iour and are represented b! the roesthe! pa! in the use cases. %n %ctor stimuates the s!stem b! pro&idin# input and/or recei&in#somethin# of measurabe &aue from the s!stem.

Last revised: Page 3" of !


15/38


Super %dmin ?ser-

Super %dmin user has contro o&er the compete s!stem and can mana#e to create otherusers" #roups" pri&ie#es and required master data.

The functionait! of the compete appication is moduari@ed and access to each modueis set b! the appicationAs access contro matri.

T!pica user access contro matri-

Roles &&E /dmin

%dd dit De (ie'

5ana=e ;roups P P P P

5ana=e sers P P P P5ana=e Businessparameters P P P P

Super admin can inacti&ate certain roups/?sers/5eatures for some reason beforedeetin# permanent!. The user ha&in# admin pri&ie#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 fied as per the user cassification and roe.

Last revised: Page 3# of !

Super %dmin?ser

U,*3 N01*

P0,,3

OK C0*2

roup and ?serMana#ement

Mana#e Business>arameters

ContentMana#ement

Cient reationshipmana#ement

CommunicationMana#ement


16/38


%dministrator-

%dministrator is another user 'ho inherits some contros from the super admin to perform certainacti&ities. enera! admin user has a the ri#hts of L%dd/dit or Deete a record. There can bemutipe admin users.

Content De&eoper-

Content de&eoper is another user 'ho #enera! create ne' contents/edit the content but doesnot ha&e ri#ht to deete permission. Content created or edited 'oud not be pubished unti it ishas be re&ie'ed or appro&ed b! the >ubisher.

Content >ubisher-

Content pubisher 'i re&ie'" appro&e or disappro&e an! content to be pubished in the pubicarea.

ebsite (isitor-

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

Re#istered ?ser-

Re#istered users 'i ha&e pri&ie#es to access certain pri&ate data and communicate 'ith theser&ice pro&iders.

Customer-

Customer is a user 'ho 'oud ha&e access to paid ser&ices.

Last revised: Page 3$ of !


17/38


#5# 1unctionalit!

a. %be to confi#ure at east 8 ser&ice pro&iders %>) for sendin# SMS.b. %be to send bu6 SMS b! the 'ebsite admin/users to the &arious sta6e

hoders.c. %be to confi#ure in the %dmin internet to send SMS for &arious acti&ities

,ampe a ne' ead is recei&ed" confirmation to customer that his enquir! isrecorded etc..4

d. Re#istered users / customers can send SMS after o#ine. %be to aocate number of SMSs a customer can a&ai free and subscribe for

more SMSs ,most! appicabe for &irtua office and reeasin# ne' products4

P5R 1unctionalit!

a. %be to update demo#raphics / persona recordsb. %be to update demo#raphics of the fami! members

c. %be to update Doctors informationd. %be to upoad prescriptions ,as attachments4e. %be to update prescriptions as tetf. %be to setup medication#. %be to setup aerts ,mai and SMS4 'ith re#ard to re#uar chec6ups"

medicine and dosesh. %be to share medica records 'ith the doctor for a particuar period 'ith

permissions ,(ie' on! / (ie' and Do'noad4

5/P 1unctionalit! ? ;oo=le 5/P /P inte=ration

0. %be to ocate Doctors" Hospitas" Cinics" Dru# Stores" Dia#nostic Jabs on aM%>.b. Dispa! different icons for each cate#or! of information.c. )cons are updated throu#h %dmin intranet for each cate#or! of information.d. %be to dispa! more information throu#h a ca$out 'hen user point on a

particuar icon.e. %be to &ie' more information in a separate pa#e 'hen user opted to 6no'

more about seected information.f. ?ser can abe to submit feedbac6s to the site o'ner for an! seected

information.#. ?ser can abe to report an! errors to the site o'ner for an! seected

information.h. The feedbac6s / errors reported b! the users are emaied/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/Cinic/Medica store/Dia#nostics4if the! fee so b! fiin# a sma form. The Jatitude and Jon#itude shoud bepic6ed up automatica!.

. The information submitted are stored separate! for the admin to re&ie' andappro&e or disappro&e.



18/38


1. % messa#e emai/sms sent to the user 'ho submitted 'hen the adminappro&e / disappro&e. )f the admin disappro&e the reason shoud be fied andintimated.

Virtual office ? ,linic mana=ement application

0. %ppication is based on SaaS ,Soft'are as a ser&ice4 mode

+. %be to pro&ide a separate area for each customer ,Doctor/cinic4 andaccessed throu#h a user name and pass'ord

c. ach customer can si#n$up to a&ai this faciit!d. Customer can opt$out this ser&ice b! sendin# an emai/cain# to a site admin

/ support request.e. %dmin can acti&ate / inacti&ate this ser&ice for a customerf. 5oo'in# are the faciities incuded in the (irtua office-

a. Customer ,Doctor/Cinic4 update their pace of a&aiabiit!" timin#s fora particuar period ,Da!" Time" Got a&aiabe time etc..4

+. (isitors ,>atients4 can &ie' the caendar or schedue an appointment

c. Customer to &ie' the caendar and ist of appointmentsd. Customer can accept / re;ect one or a appointments for a da! or

periode. )nformation #oes to the patients 'hen Doctor/Cinic accepted or

re;ected an appointment b! emai / smsf. Record/update patient &isits#. %be to #enerate a bi for the ser&icesh. %be to 'rite a prescription for the patienti. %be to #enerate a medica certificate for the patient

;. %be to recommend/order a dia#nostics

#. SaaS %rchitecture

1. 5u! Shared DB >er Tenant

Last revised: Page 3! of !


19/38


The proposed appication shoud be depo!ed on SaaS patform. The appication shoud ta6e care

of the foo'in# 'hie desi#nin# the appication.

>erformance

Securit!

Reiabiit!

Customi@ation

)nte#ration

Scaabiit!

Muti tenanc!

There are t'o a!ers. DB a!er and %ppication Ja!er. r#ani@ation )D is the 6e! for a database

tabes ,Master and transaction4. Data is accessed from the appication b! pro&idin# r#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 databases one to store a data reated to user" contains ,username" pass'ord"

or#ani@ation id4 for authentication and the other is database contains data reated to appication.



20/38


?)D is used for or#ani@ation id. Mutipe or#ani@ation data can reside in a sin#e database or

mutipe of databases.

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

a. %be to define the ad pacements in &arious pa#esb. %be to define price for ad pacements ,ad si@e / duration / price4

. %be to update/upoad ad content for a ocation 'ith priorit!" number ofimpressions" time period etc..

d. %be to mana#e the ad banners and content throu#h admin area

:os functionalit!

a. %be to search ;ob openin#s b! enter search tet" eperience/ocation.b. %be to respond/send resume for a ;ob direct! after o#in

. %be to pubish ist of recent ;obs b! function and ocation. %be to pubish top 10 empo!ers 'ith their o#os. Dispa! ist of current ;obopenin#s.

e. %be to re#ister and upoad resume b! the ;ob see6ersf. %be to o#in and update resume b! the ;ob see6ers#. mpo!ers to re#ister and update ;ob openin#sh. mpo!er o#in and search resumesi. Do'n oad matchin# resumes for a particuar post

9. mai to ;ob see6er 'hen a ne' matchin# ;ob is updated b! the empo!er6. mai to empo!er 'hen a ne' matchin# resume is updated b! a ;ob see6er.. Boc6 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 shoud 'or6 i6e oo#e search 'ith su##estionsb. ?ser can shift to ad&ance search and search throu#h seectin# fiters and

criteria

,ommunication ? or> floAs

a. The &isitors to the 'ebsite shoud abe to communicate 'ith the site admin /ser&ice pro&iders b! fiin# pre$defined forms.

+. % confirmation messa#e shoud 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 tabe 'hich can be accessed throu#hadmin intranet a information shoud be sent to respecti&e site user / ser&icepro&ider dependin# on the 6ind of ser&ice request.

d. or6$fo's are defined in the admin intranet ,i.e. mai to 'hom" access to'hom4



21/38


Buildin= consumer dataase

a. Consumers are the users 'ho search/see6 &arious ser&ices and submitsrequest for ser&ices in &arious forms. Re#istered / non re#istered users.

b. % the information are to be compied and cate#ori@ed for future ser&ices i6e,'hen ne' product / ser&ices are reeased.4

. %be to attract consumer to re#ister to #et &aue added ser&ices.

5ana=e dataase for Pharmacists?Dru= stores? Dia=nostics centers andlocate them in ;oo=le 5ap

a. %be to search and ocate a dru# store / dia#nostic ser&ices

+. %be to compare prices for different tests bet'een the dia#nostic centers in aparticuar ocait!.

,ommunit! ser*ices ? ,orporate social responsiilit!

a. >eope re#ister as ser&ice pro&ider / &ounteer to etend their ser&ices.

+. >eope request to for ser&ices ,ampe- Joo6in# for hep to ocate a doctorfor a particuar disease" Joo6in# for hep.

c. %be to connect bet'een the ser&ice pro&iders 'ith ser&ice see6ers

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

a. %be to create a patform to connect bet'een the consumer and ser&ice

pro&ider and brin# them into to a common patform.b. The information shoud be fashed to nearest Dia#nostics center 'hen Doctor

prescribes tests.c. Consumer / >atient can compare price for different tests

nteracti*e 1orms

#er*ice Request

se ,ase %ame Submittin# onine formDescription Submittin# onine form in the 'ebsite

/ctors >rospecti&e medica tourist ,Customer4

Business Rules . 5orm can be submitted on! after the usercompete fiin# a the required data.

2. ?ser can s'itch to detaied form / pro&idemore information if he/she 'iin# topro&ide at that moment b! epandin#



22/38


section of the form.Basic 1loA /lternate 1loAs

1. n screen than6 !ou messa#e.

$. mai confirmation to the customerAsemai address as a cop! of theinformation submitted.

(. mai notification to the businesshead/concerned eecuti&e.

4. Sa&e data in the database forreportin#

1. The ser&ice request form can besubmitted ,after censorin#4 direct! to theaffiiate hospitas ,Ser&ice pro&iders4 tosubmit their quotes.

2. The business head/concerned eecuti&e'i re&ie' and submit the form to Ser&icepro&iders.



23/38


,ontact us

se ,ase %ame Submittin# contact us formDescription Submittin# onine form in the 'ebsite

/ctors >rospecti&e medica tourist ,Customer4ebsite &isitors>rospecti&e ser&ice pro&iders ,anted to ist inthe porta4

Business Rules 1. 5orm can be submitted on! after the usercompete fiin# a the required data.

Basic 1loA /lternate 1loAs


$. mai confirmation to the emaiaddress pro&ided as a cop! of theinformation submitted.

8. mai notification to the businesshead/concerned eecuti&e.

4. Sa&e data in the database forreportin#

1eedac>

se ,ase %ame Submittin# feedbac6 onineDescription Submittin# an onine form in the 'ebsite

/ctors ebsite &isitors

Business Rules 2. 5orm can be submitted on! after the usercompete fiin# a the required data.

Basic 1loA /lternate 1loAs


2. mai confirmation to the emaiaddress pro&ided as a cop! of theinformation submitted.

8. mai notification to the businesshead/concerned eecuti&e.


24/38


8.+.+. Pulish Basic #er*ices (Health ourist Portal)

The content is mana#ed in the admin section and pubished in the home pa#e andser&ices section.

?ser can epore to 6no' more information ,i.e. Jist of ser&ice pro&iders" their faciities"

pricin# etc4 on seectin# a particuar ser&ice.

%so" user can compare price bet'een ser&ice pro&iders for a seected ser&ice cate#or!.

Last revised: Page 2" of !


25/38


26/38


e. Testimonias

2. )nformation about a (isitin#/Historica pacei. Gameii. Short description

iii. %ddress/Jocationi&. )mportance&. >hoto#raphs

8. )nformation about a Hotesi. Gameii. Short descriptioniii. %ddress/Jocationi&. Tariff &. >hoto#raphs

hotos

I. 5%Qs ,CMS4i. Questionii. %ns'er

=. Ser&ice 'ise price comparisoni. Ser&ice cate#or!ii. Ser&ice descriptioniii. >rice in ?S7i&. ther char#es if an! ?S7

Last revised: Page 2$ of !


27/38


ntit! Relationship Dia=ram



28/38


Data Volumes

Health ourist Portal$

)nitia 10 B incudin# ima#es and annua #ro'th coud #o up to 109

Portal for ndia$

)nitia 20 B incudin# ima#es and annua #ro'th coud #o up to 209

Data Retention and /rchi*in=

This section describes the Data retention ,time frames for onine Data retention before

archi&in#4 and aso the archi&in# requirements.

Pri*ac! mplications

This section describes the sensiti&it! e&es of each cass of data. The foo'in# criteria areused in determinin# the sensiti&it! e&e of each conceptua cass/entit! in ine 'ith theo&ernment Core >oic! Manua4.

Non-sensitiveinformation that &ould not reasona'l 'e e.ected to cause in4ur (harm)if released to the u'lic5

Protected A: information that- if comromised- could reasona'l 'e e.ected to cause

in4ur (harm)- e+g+ loss of rivac5

Protected B: information that- if comromised- could reasona'l 'e e.ected to causeserious in4ur (harm)- e+g+ the conduct of a court roceeding &ould 'e adversel affected5

Protected C: information that- if comromised- could reasona'l 'e e.ected to causee.tremel grave in4ur (harm)- e+g+ loss of life+

Last revised: Page 2! of !


29/38


Data Definition Reports

ntit! Definition Report

This section is appicabe on! to race Desi#ner approach. This section describes Data%rchitecture / definition ,ntit! Reationship mode4 in narrati&e tet form.

ntit! %ame

ntit! Description

nitial Data Volume (appro@.)

/nnual Data =roAth rate (in appro@. F)

/ttriutes (fields) of the ntit! Game -

Description -Game -

Description -Game -

Description -Game -

Description -

Game -

Description -Game -

Description -



30/38


Data Requirements (Portal for ndia)

The content and data required for the porta is coected from &arious sources and updated

throu#h the admin contro pane b! the authori@ed users. The content/data pubished on! after ithas been &erified and appro&ed b! the pubisher.

nitiall! all the rele*ant data updated ! the portal administrator and pro=ressi*el! ane@tranet s!stem can e de*eloped Ahich Aould enale the ser*ice pro*ider to update datathrou=h secure lo=in.

. Core ser&ices )nformation about &arious Hospitas" Cinics" Doctors" Dia#nostic" 5aciitiespro&ided b! them and pricin# etc.

$. %nciar! ser&icesFobsGe' product reeases

%d&ertisement

(. ther ser&ices Reated ne's and updates

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

#ecurit! Requirements

/uthentication

This section describes the %uthentication requirements part of the Business Requirements.%uthentication is the process of &erif!in# the #enuineness of caims that a person/#roupma6es to estabish identit!/ei#ibiit! for access to ser&ices. The foo'in# criteria is used indeterminin# transaction t!pes of each use case/function-

Level 0 : Anonymous transaction6 triggers transactions that do not require or allo& aerson to 'e identified- or transactions &hich require rotection of a erson7s identit+ ore.amle- access to online information a'out government rograms or services or rotectinga erson7s identit+ Com'ining the transaction data &ith other data must not allo&identification of a articular individual+

Level 1 : Pseudonymous transaction6 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+ ore.amle- a note from someerson899999+com can not 'e readil translated into anindividuals name- 'ut it ma 'e sufficient to request information- to rovide some services- oron;going follo& u+

Level 2 : Identified transaction 6 triggers transactions that require that a erson 'esecificall identified+ %he nature of the transaction ma require confirmation of a erson7sidentit (e+g+- name- address- 'irth date- etc+) and


31/38


' the transaction+ or e.amle- a note signed &ith a digital certificate- audit trails andsecurit logs ma rovide sufficient evidence that a secific erson intended to conduct atransaction+

/*ailailit! Requirements

The s!stem is a&aiabe o&er the net. The heathcare porta is tar#eted to ?S% and >orta for)ndia is tar#eted 'hoe of )ndia. The s!stem 'oud re$direct to the user based on )> address.)f an!bod! tr!in# to access the Heathcare porta from )ndia" the s!stem 'i re$direct to >ortafor )ndia and &ice$&ersa.

The s!stem uptime shoud be **.009. The simiar bac6 to bac6 #uarantee needs to beobtained from the hostin# compan!.

)n case of an! brea6do'n" appropriate messa#e need to be fashed.

n$ine chat to be ad;usted 'ith ?S and )ndia time.

Response to user quer! 'ithin 2< hours.



32/38


se ,ase ? Business1unction %ame

/*ailailit! Requirements& Re=ular Aor> hours& 23@6& /n! other (please descrie)

sailit! Requirements

This section describes the s!stem usabiit! requirements. % usabiit! requirement specifiesho' eas! the s!stem must be to use. ?sabiit! is a non$functiona requirement" because in itsessence it doesnt specif! parts of the s!stem functionait!" but specifies on! ho' thatfunctionait! is to be percei&ed b! the user" for instance ho' eas! it must be to earn andoperate the s!stem.

#!stem Help Requirements

This section describes 'hat 6ind of S!stem Hep features are needed to be buit into the

s!stem.

se ,ase ? Business1unction %ame

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



33/38


Performance Requirements

+.+.1. Stress Requirements

Heath tourist portas must be abe to support minimum of 200 user accessin# recordssimutaneous!.

>orta for )ndia must support minimum of +000 users accessin# simutaneous!.

+.+.2. Response$Time Requirements

The maimum ao'abe 'ait time from the moment the user submits a request unti thes!stem comes bac6 'ith a response shoud not #o be!ond = seconds 'ith the data&oume 800"000E records

#calailit! Requirements

The s!stem shoud be scaabe to accommodate add ne' ser&ices" enhance eistin#ser&ices.

ser #calailit!

/pplication #calailit!

nterface Requirements

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

ser nterface Requirements

BroAser compatiilit!

The 'ebsite shoud support a ma;or bro'sers of the current &ersion and one &ersion

do'n.

1. )

2. 5ire 5o

8. Mo@ia ,Mac4


34/38


Data displa!

The content presented in the porta 'oud be desi#ned professiona! i6e an! 'ord cass

'ebsite. The data can be presented in Jist &ie'/5orm &ie' to the sta6ehoders in their

respecti&e area.

Drop&doAn list

Data consistenc! is maintained throu#h seectin# choices from drop do'n ist. Theappication shoud enabe each customer to add their ne' choices.

The master drop do'n ist is mana#ed throu#h the %dmin area. hen a customerre#ister" set of master data ,pre$requisites4 are a&aiabe for them. This 'oud hep themto start usin# the appication instant!. %so" each re#istered customer can mana#e theiro'n master data ,add/edit/deete4.

#a*in= report as PD1 file.

5aciitates to sa&e a report in >D5 format

e 2.0 features

ebsite / %ppication to be buit on eb 2.0 features. >a#e re$oadin# / refresh to bea&oided compete!.

#!stem nterface Requirements

Last revised: Page " of !


35/38


Project Plan and Delivery Schedule

7.1 Project Schedule

#' as> #tart 1inish Duration

1 DefinitionS!stem Desi#nDetaied Desi#nDe&eopment)nte#ration Testin#Depo!ment?%TBu# fiin#

o Ji&e

6.2 Pro"ect #chedule

Phase 5ilestone Deli*erale

Requirement Definition BRD Si#noff Business RequirementDocument

>rotot!pin# /ire framin# />orta a!outs

Ja!out desi#n si#n$off andireframe Si#noff

>DS" htm and CSSs

>rotot!pe for the proposedappication

S!stem Desi#n Competion of Desi#nDocument

Desi#n document containin#fo's" &aidations" inputs andoutputs.Database desi#n

De&eopment" )nte#ration andTestin#

Beta Reease of the site for?%T

Beta &ersion ,Tested fu!4

Depo!ment and o Ji&e 5ina Si#noff Source Code for theappication hosted on i&een&ironment. Source codedocumentation and ?ser#uide.

Support Cosin# 5i bu#s

Last revised: Page # of !


36/38


Communication Plan

8.1 Proposed Communication Plans

Dai! ca ee6! re&ie' meetin# 'oud be hed on a preschedued da! ,NNNNNN4 and time.

Re#uar communication 'oud be done throu#h emais" phone and ebMeetin# 'ithemai 'oud be the most frequent communication medium

tranet porta ,Basecamp4 created for the pro;ect 'oud be the patform throu#h 'hichthe pro;ect reated documents" minutes of the meetin# are shared. The tas6s assi#ned forthe team members are presented and trac6ed throu#h the porta

ee6! status report shoud be shared 'ith Cient throu#h emai and aso posted to theetranet porta b! end of the 'ee6.

Project Team

#' %ame Role -r=aniation ,ontact %o &mail address

scalation Points

#' %ame Desi=nation -r=aniation ,ontact %o &mail address

Last revised: Page $ of !


37/38


Re*ision 'o=

ate Version C!an"e #eference #evie$ed %y

2+thct 2010 01$Draft

23thct 2010 02$Draft Jist of 5unctionait! incuded for )ndian >orta1. Communit! /Corporate Socia Responsibiit!2. >HR ,>ersona Heath Record4.8. Mana#e data bases of >harmacists/Dru#stores and ocate them in oo#e Map

3thGo& 2010 02$Draft 1. Scope is epained and epanded

2. SaaS architecture dia#ram is depicted

8. Connect functionait! is incuded

/ppendices

nter content here.



38/38


/ppro*al

This document has been appro&ed as the officia Business Requirements Document forthe HeathCare pro;ect.

5oo'in# appro&a of this document" chan#es 'i be #o&erned b! the pro;ectAs chan#e

mana#ement process" incudin# impact ana!sis" appropriate re&ie's and appro&as"under the #enera contro of the Master >ro;ect >an and accordin# to >ro;ect Supportffice poic!.

Pre&ared %y 'i"nature ate

%uthors Game

Titer#ani@ation

A&&roved %y 'i"nature ate

Cient %cceptorAs Game

Titer#ani@ation

65908736 healthcare project brd v02

Documents