.

SoftwareRequirements

Specification
for

DayHealthManager
Version1.1

Preparedby4yourhealth

SeniorProject2015

2/10/2015

TableofContents
TableofContents
RevisionHistory
Introduction
Purpose
DocumentConventions
IntendedAudienceandReadingSuggestion
ProjectScope
References
OverallDescription
ProductPerspective
ProductFeatures
UserClassesandCharacteristics
OperatingEnvironment
DesignandImplementationConstraints
UserDocumentation
AssumptionsandDependencies
SystemFeatures
ExternalInterfaceRequirements
UserInterfaces
HardwareInterfaces
SoftwareInterfaces
CommunicationsInterfaces
OtherNonfunctionalRequirements
PerformanceRequirements
SafetyRequirements
SecurityRequirements
SoftwareQualityAttributes
OtherRequirements

RevisionHistory
Name Date ReasonForChanges Version
ZacharyNielsen 2/10/15 Initialcreation 1.0.0
ZacharyNielsen 3/07/15 Customerrequest 1.1.0
DanielHudy 4/28/15 RevisionafterSessionAppchanges 1.2.0


1. Introduction
1.1. Purpose

TheTrilliumHealthDayHealthManagerisasystemprimarilyusedtoassistDayHealth
staffinthetrackingandcareofpatientsintheirDayHealthprogrambymultiplemeans.An
importantassistiveactivitythesystemprovidesistodigitizewhatarecurrentlyphysicalartifacts
suchaspatientassessments,careplans,andpatientsignin/outs.Asanimprovementtothe
currentphysicalworkflow,thesystemwillautomatetrackingofindividualsthroughtheprogram.
Inaddition,thesystemwillassistthestaffinclericaldutiessuchasbilling,reportgeneration,
overseeingcompliancewithpatientscareplans,andprovidingtoolstoassistinthecaseofan
audit.
Thesystemwillaccomplishthesegoalsthroughtheimplementationofadesktop
interface,database,andmobileapplication.TheClinicianPortalwillassisttheDayHealthstaff
inthecreationandretrievaloftheirelectronicmedicalrecords,billing,andreportgeneration.
Thedatabasewillpersistentlytrackthestatusoftheindividualsenrolledintheirprogram,and
themobileapplicationwillassistpatientswithsigninginandout.

1.2. DocumentConventions

Thisdocumenthasbeenbrokenintothreepartsundermostsectionstocoverthethree
fundamentalpartsoftheapplication,thedatabase,theClinicianPortal,andthesession
application.ThisdocumentismodeledaftertheSRStemplatefromtheSoftwareRequirements
andArchitectureclass[A:1].Throughoutthedocumentwereferencedifferentappendices,these
referenceswillbenotedwiththefollowingconvention:[AppendixLetter:ItemNumber].For
examplethenotationforreferencingitemoneinappendixA(TheSRSTemplate)wouldbe
[A:1].

1.3. IntendedAudienceandReadingSuggestion

Theintendedaudienceofthisdocumentisallmajorstakeholderswhichincludethe
developmentteam,theprojectowner,theprojectcustomer,theseniorprojectadvisor
(ProfessorHawker),andanyoneevaluatingtheproject.Itisrecommendedthatyoucheckout
ourteamswebsiteandthedocumentshostedthereforbetterbackgroundontheproject,
process,andtheteam.

1.4. ProjectScope

ThescopeforthisprojectincludeseverythingTrilliumneedstoreplacetheircurrent
systemwithoursysteminadditiontoacoupleofextrafeatures.Thescopeprimarilyconsistsof
threeparts,thedatabase,theclinicianportal,andthesessionapplication.Thethreeofthose
partseachhaveadistinctscope.

ThedatabasemustbeabletotrackallofthedatathatTrilliumislookingtostore.Ahuge
partofthisinvolvesscanningandstoringdocumentsonaperpatientbasis.Eachdocument
mayhavedifferentpiecesofdatathatneedtobetrackedinthedatabase.Thedatabasewillbe
inchargeofkeepingtrackofwhatpiecesofdataeachdocumentisassociatedwithaswellas
storingeachinstanceofthatdatathathasbeeninput.Thedatabasewillalsostoresessiondata
fromeachofTrilliumspatientsessions.Thisincludeseverythingfromdepartureandarrival
times,sessionnotes,andindividualsessionnotes.Morespecificsondatatobestoredcanbe
foundintheproductfeaturessection.

Theclinicianportalistheprimaryuserinterfaceforoursystem.Thiswillbeaweb
applicationaccessiblefromanycompatiblewebbrowser.Theclinicianportalhas3majorparts:
patients,sessions,andstatistics/billing.Thepatientssectionwillbewheretheusercanadd,
modify,orcheckanypatientdatastoredinthesystem.Thisincludesbasicfunctionalitysuchas
addinganewpatient,addinganewscanneddocumenttoapatient,orcheckingonapatients
basicinfo.Thesessionsectioniswhereausercangotoadd,modify,orcheckonanysession
data.Thisincludesfunctionalitysuchasschedulinganewsession,modifyingasessionleader,
orcheckingwhichclassesarescheduledonaspecificday.Thethirdbasicpartis
statistics/billing.Thestatistics/billingsectionwillbewheretheusercanfindtoolsthatareableto
runtrackingassociatedwithpatientdataandbilling.Thismayinvolveatoolthatcangetthe
patientsthatarebillablefortheweekorsimilartools.

Thesessionapplicationisusedbysessionleaderstostandardizeattendancetracking
andsessionnotekeeping.Thesessionapplicationwillprimarilybeusedtokeeptrackof
patientssigningintosessions.Thesessionapplicationwillinterfacewithafingerprintscanner
thattheuserwillneedtousetosignintoasession.ThisgivesTrilliumauniqueandprecise
timestampforeachindividualthatwillallowthemtodeterminehowlongapatienthasbeenat
eachsession.

1.5. References

Title CorrespondingFile/Address

TeamWebsite http://www.se.rit.edu/~foryourhealth/
2. OverallDescription
2.1. ProductPerspective

2.1.1. Database
CurrentlyTrilliumhealthuseslargelypaperformsandsharepointtomanagetheir
patientscare.Thishasbeenalessthananidealsolution,butnogoodmedicalsoftware
systemsexistforgroupsettings.Thedatabasesrolewillbetohostrelevantdocumentsand
relatepatientandclinicalinformationinameaningfulway.
2.1.2. Application
Aclinicianportalisrequiredtopresentandorganizethecontentsofthedatabase.This
istheuserfacingaspectofthesystemandwillbeimplementedwithspecialconsiderationgiven
tousability.Asuccessfulimplementationofthisuserinterfacewillaboveallprovidefaster
accessto,andbetterpresentationof,theclinicsdata.
2.1.3. SessionApp
AnotherapplicationisnecessarytoallowpatientstoeasilycheckintoDayHealthand
intospecificsessions.Thiswillallowthepatientstoverifytheirattendanceusingtheir
fingerprints.

2.2. ProductFeatures

2.3. Install
2.3.1.1. Awayfortrilliumtoinstallthedatabase
2.3.1.2. Awayfortrilliumtoinstalltheserverapp
2.3.1.3. Awayfortrilliumtoinstallthefrontendapplication
2.3.2. Database
2.3.2.1. Storespreviousstatesofalltableswithallchangesmadetothem
2.3.2.2. Canstorepatientssigninginfortheday
2.3.2.3. Canstorepatientssigningoutfortheday
2.3.2.4. Canstorepatientssigninginforsessions
2.3.2.5. Canstorepatientssigningoutforsessions
2.3.2.6. Canstorenewdocumentsinthedatabase
2.3.2.7. Storestructureofnewdocumentscreated
2.3.2.8. Canstorepatientcareplans
2.3.2.9. Cantrackreviewsofcareplans
2.3.2.10. Cantrackapprovalofcareplans
2.3.2.11. Canstorecareplanupdatesandchanges
2.3.2.12. Canstoretracks
2.3.2.13. Canstoreclasses
2.3.2.14. Canlinkpatientstoclasses
2.3.2.15. Canstoreschedules
2.3.2.16. Canstoresessions
2.3.2.17. Canstorealldataassociatedwithsessions
2.3.2.18. Canstoregroupnotesforsessions
2.3.2.19. Canstoreindividualnotesforsession
2.3.2.20. Canlinkuserstotracks
2.3.2.21. CancalculateAssessmenttimeline
2.3.2.22. Cancalculatewhoisbillablebasedondates
2.3.2.23. Cankeeptrackofwhatclaimshasbeensentfor
2.3.2.24. Cankeeptrackofclaimsthathavebeenacceptedordenied
2.3.2.25. Willhavestoredproceduresforcalculationswithinthedatabase
2.3.3. ClinicianPortal
2.3.3.1. Willhaveawaytoconfigureexternaldatarequests
2.3.3.2. Willhaveawaytogetexternaldatathroughconfiguredconnectionsandscripts
2.3.3.3. TheusershallhaveaccesstoaStartScreen
2.3.3.4. TheusershallbeabletoaviewaMetricspage,withthefollowingdisplayed...
2.3.3.4.1. NumberofPatientsenrolled
2.3.3.4.2. Percentageofserviceencountersbilled
2.3.3.4.3. TotalDollarsbilled
2.3.3.4.4. AveragepercentageattendanceforADHP
2.3.3.4.5. NetRevenue
2.3.3.4.6. Receivablesforthepast90days
2.3.3.4.7. HIVHealthaggregated
2.3.3.5. TheusershallhaveaccesstoaPatientpage,withthefollowingdisplayed...
2.3.3.5.1. ViewingofthePatient'scareplans
2.3.3.5.2.
LinkstootherpatientDocuments
2.3.3.5.3.
Sessionattendance
2.3.3.5.4. Billinginformation
2.3.3.6. ThePortalwilldisplayalistofsessions
2.3.3.7. Theusershallbeabletoselectaparticularsessiontoseemoredetails
2.3.3.8. TheusershallbeabletoseeSessioninformation
2.3.3.8.1. Facilitatorinformation
2.3.3.8.2. Timeandscheduling
2.3.3.8.3. Attendance
2.3.3.8.4. GroupandIndividualnotes
2.3.3.9. Supportforenteringandviewingpatientassessments
2.3.3.9.1. Nursing,Nutrition,HealthLiteracy,CareManagement,BehavioralHealth,etc.
2.3.3.9.2. Theusershallbeabletocreatenewassessmenttypes
2.3.3.10. TheusershallbeabletoconducttheCareplanprocess
2.3.3.10.1. PerformCareplanReview
2.3.3.10.2. ApproveaCareplan
2.3.3.10.3. ViewCareplanhistory
2.3.3.10.4. MakeupdatesorchangestoaCareplan
2.3.3.11. ThePortalshallsupportauditingofDocumentsandotherdatawiththe
following...
2.3.3.12. Trackingadditionofnewdocumentsordata
2.3.3.13. AllowingandTrackingchangestoexistingdocumentsordata
2.3.3.14. AllowingandTrackingdeletionsofexistingdocumentsordata
2.3.3.15. Reportswhichshowauditinghistory,peruserorperpatient.
2.3.3.16. Exportofauditinghistories
2.3.3.17. Clearlydemonstratethelinkbetweenpatientgoalsandsessions.
2.3.3.18. Eithercatalogdocumentlocations,ordisplaythedocumentsintheapplication.
2.3.3.19. Addfingerprintstothedatabaseforeachuser
2.3.4. SessionApp
2.3.4.1. Maintainalocalcopyofpatientfingerprintsforoffsitepurposes
2.3.4.2. Fingerprintscannersigninandsignoutforthedayandindividualsessions
2.3.4.3. Hasabackupwaytosigninandoutincaseoffingerprintscannererror
2.3.4.4. Abilityforfacilitatortooverridesigninoroutincaseoffingerprintorbackuperror
2.3.4.5. Overviewofattendanceforparticulardayorsession
2.3.4.6. Abilityforfacilitatortocreateanewsession

2.4. UserClassesandCharacteristics

ITPersonnel:
TechnicalSkill:Hasfullunderstandingofthesystem,andworkingknowledgeofSQL
FrequencyofUse:Low
EducationLevel:Atleastformaltrainingorsomecollege
Privileges:Administratorprivilegeshasaccesstoallpartsofthesystemandcan
directlyaccessthedatabase
ExperiencewithSystem:High
ProductFunctions:Rundatabasequeries,addnewforms

Clinician
TechnicalSkill:Lowtomedium
FrequencyofUse:Multipletimesperday
EducationLevel:Nonspecific
Privileges:Readaccesstoalldocuments,writeaccessonlyuponcreationorspecial
cases.
ExperiencewithSystem:Medium
ProductFunctions:Viewandinterpretdataanddocuments,createandaddnew
documents.

Patient
TechnicalSkill:Low
FrequencyofUse:Multipletimesperday
EducationLevel:NotSpecified
 Privileges:Session/Dailyattendancethroughfingerprintscanner
ExperiencewithSystem:Low
ProductFunctions:Checkintosessionordaythroughfingerprintscanner.

Facilitator
TechnicalSkill:Lowtomedium
FrequencyofUse:Multipletimesperday
EducationLevel:Nonspecific
Privileges:Readaccesstosessionattendance
ExperiencewithSystem:Medium
ProductFunctions:Confirmsessionattendancetakenthroughfingerprintscanner.

2.5. OperatingEnvironment

2.5.1. Database
ThedatabasewillexistonaMicrosoftWindowsServerThatrunsMSSQL2008.This
serverwillonlyserverequestsfrominsidetrillium.
2.5.2. Application
Themainuserapplicationwillbebuiltasawebbasedsystem.Userswillaccessit
throughabrowserandloginwindow.ThespringMVCmodelwillbeusedasabase.
2.5.3. SessionApp
ThesessionapplicationwillbehostedonlaptopswithWindowsOS.
.

2.6. DesignandImplementationConstraints

2.6.1. Database
Databaseneedstobeavailabletointernalsourcesforqueries.Thecustomerwouldlike
thedatabasetobeabletobeeasilymodifiedinthefutureforotherteamstoupgradethe
systemordoworkonit.
2.6.2. Application
Featuresneedtobesupportableinawebapplication,securityfeaturesandsecurity
designmustaddressthisrelianceontheweb.Additionally,boththedesignandthe
implementationneedstobeusablebyallclinicians.
2.6.3. SessionApp

2.7. UserDocumentation

2.7.1. Database
 UserdocumentationwillconsistoftheDatabaseSchemaandhowtoguideforrunning
databasesetupscript.
2.7.2. Application
Theapplicationshallhavetutorialdocumentation,forthepurposeofeducatingnew
usersaswellasactingasareference.Clearproceduresandproperprotocolmustbeexplained
indetail,asoftenthesetasksmustrespectbothlegalandbusinessconcerns.These
proceduresshallbepresentedinstepbystepinstructionswhichareaccompaniedbyboth
screenshotsandinapplicationtooltips.Thegoalhereistoproduceaninterfacewhichcan
selfteachitsownpracticetoanyfirsttimeusers.
2.7.3. SessionApp
Userdocumentationwillbelimitedonthesessionapplicationasthisisintendedtobean
internalattendanceverification/recordingandnotetakingapplication.Navigationwillbeclearly
markedandtooltipswillbeusedtoguidenewfacilitators.

2.8. AssumptionsandDependencies

2.8.1. Database
UseofMSSQLdependsuponaMicrosoftWindowsoperatingsystem.
2.8.2. Application
DependentonTrilliumsLocalAreaNetwork.Willalsodependuponthefunctioningof
theSpringmodel,uponwhichtheClinicianPortalisbeingbuilt(thecustomeralreadyhas
experienceworkingwithSpring).Assumeusersarecapableofusinginternetbrowsers.
AssumethatDayHealthcontinuestotrackpatientsandsessionsinmuchthesamewaythey
donow.
2.8.3. SessionApp
FingerprintscannerisbeingbuiltusingcustomizationstothePersonIDsoftwareoffered
by360Biometrics.WeareworkingthroughtheirrepresentativePinkyThakkartoensurethat
oursoftwareanddatabaseintegratessmoothlywithPersonID.Weareassumingthatby
workingcloselywiththeirdevelopmentteamwewillbeabletolowerthechanceofhavinglarge
integrationissues.

3. SystemFeatures
UseCases

PrimaryActors ID Name
Clinician DHM_UC_1 Aclinicianlogsin
Clinician DHM_UC_2 Aclinicianlogsout
Clinician DHM_UC_3 Aclinicianaddsanewpatient
Clinician DHM_UC_4 Aclinicianaddsapatientscareplan
Clinician DHM_UC_5 Aclinicianupdatesapatientscareplan
Clinician DHM_UC_6 Aclinicianviewsapatientscareplan
Clinician DHM_UC_7 Aclinicianviewsapatientssessionattendance
Clinician DHM_UC_8 Aclinicianviewsapatientsmedicalassessments
Clinician DHM_UC_9 Aclinicianaddsadocumenttemplatetothesystem
Clinician DHM_UC_10 Aclinicianeditsanexistingdocumenttemplate
Clinician DHM_UC_11 Aclinicianviewsadocumenttemplateinthesystem
Clinician DHM_US_12 Acliniciandeletesadocumenttemplatefromthesystem
Clinician DHM_UC_13 Aclinicianaddsaclasstothesystem
Clinician DHM_UC_14 Aclinicianeditsaclassinthesystem
Clinician DHM_UC_15 Aclinicianviewsaclassinthesystem
Clinician DHM_UC_16 Acliniciandeletesaclassfromthesystem
Clinician DHM_UC_17 Acliniciancreatesaninstanceofadocument
Clinician DHM_UC_18 Aclinicianeditsaninstanceofadocument
Clinician DHM_UC_19 Aclinicianviewsaninstanceofadocument
Clinician DHM_UC_20 Acliniciandeletesaninstanceofadocument
Clinician DHM_UC_21 Aclinicianviewstheaudithistoryofadocument
Clinician DHM_UC_22 Aclinicianprintsadocumentinstance
Clinician DHM_UC_23 AclinicianassignsclassestoapatientbasedonCCP
Clinician DHM_UC_24 Aclinicianviewsoverallprogramstatistics
Clinician DHM_UC_25 AcliniciannavigatestheClinicianPortal
Patient DHM_UC_26 Apatientsignsinfortheday
Patient DHM_UC_27 Apatientsignsoutfortheday
Clinician DHM_UC_28 Aclinicianoverridesthepatientssignoutfortheday
Patient DHM_UC_29 Apatientsignsinforasession
Patient DHM_UC_30 Apatientsignsoutofasession
Facilitator DHM_UC_31 Afacilitatoroverridesthepatientsigninforthesession
 Facilitator DHM_UC_32 Afacilitatoroverridesthepatientsignoutforthesession
Facilitator DHM_UC_33 Afacilitatorcreatesanewsession
Facilitator DHM_UC_34 Afacilitatorendsasession
IT DHM_UC_36 AnITpersonrunsaqueryonthedatabase
IT DHM_UC_37 AnITpersoneditsanexternaldatasourceconfig
IT DHM_UC_38 AnITpersonconfiguresanewdatapiece
Clinician DHM_UC_39 Aclinicianrunsabillingreport
Clinician DHM_UC_40 Aclinicianmarksabillingassent
Clinician DHM_UC_41 Aclinicianupdatesabillingstatus
See external Use Cases document for actual use cases with their
detailed descriptions.

4. ExternalInterfaceRequirements
4.1. UserInterfaces

4.1.1. ClinicianPortal
Asawebbasedapplication,willbetheprimarychannelthroughwhichusersaccessor
modifyanyinformationinthedatabase.Shallrelyoncommonwebapplicationstandards,
specificallyAJAXandrequireuserstoaccessthroughabrowser.Theinterfacemustbeeasyto
learnandnavigatequickly.

4.2. HardwareInterfaces

4.2.1. SessionApplication
Thesessionapplicationrequiresanexternalfingerprintscannersupportedbythe
customversionofPersonID.

4.3. SoftwareInterfaces

4.3.1. ClinicianPortaltoDatabase
4.3.2. SessionApplicationtoDatabase
4.3.3. PersonIDtoDatabase

4.4. CommunicationsInterfaces

4.4.1. ThedatabasewillcommunicateviaanencryptedremoteconnectionusingSSL.

5. OtherNonfunctionalRequirements
5.1. PerformanceRequirements

5.1.1. Database
5.1.1.1. Thedatabaseshallbeavailable99%ofthetimeduringbusinesshours
5.1.1.2. Thedatabaseshallbeavailable95%ofthetimeduringnonbusinesshours
5.1.1.3. NoDatabasequeryshalltakemorethan5secondswithonlyonedatabase
connectionactive
5.1.1.4. Onaverageadatabasequeryshalltakelessthan.5secondswithonlyone
databaseconnectionactive
5.1.1.5. Nodatabasequeryshalltakemorethan10secondswhilelessthan25database
connectionsareactive
5.1.1.6. Onaverageadatabasequeryshalltakelessthan2secondswhilelessthan25
databaseconnectionsareactive
5.1.2. Application
5.1.2.1. Nopageshalltakemorethan2secondstoaccesswithonlyoneuseronline
5.1.2.2. Onaveragenopageshalltakemorethan.5secondstoaccesswithonlyone
useronline
5.1.2.3. Nopageshallevertakemorethan5secondstoaccess
5.1.2.4. Onaveragenopageshalltakemorethan2secondstoaccess
5.1.2.5. Theclinicianportalshallbeaccessibleviaaninternetconnection99.9%ofthe
timeduringbusinesshours
5.1.3. SessionApp
5.1.3.1. Fingerprintscanningshallrecognizeregisteredusers95%ofthetime
5.1.3.2. Fingerprintscanningshallreturnresultswithin1second
5.1.3.3. TheSessionappwillbeoperational99.99%ofthetimeregardlessofaninternet
connection

5.2. SafetyRequirements

5.2.1. Database
5.2.1.1. Datafromthedatabasewillneverbetransmittedtounauthenticatedsources
5.2.2. Application
5.2.2.1. Theclinicianapplicationwillneverdisclosepatientinformationtousersthatare
notauthorizedtoseeit.
5.2.3. SessionApp
5.2.3.1. ThesessionappwillneverdisclosePatientinformationtousersthatarenot
authorizedtoseeit.

5.3. SecurityRequirements

5.3.1. Database
5.3.1.1. Thedatabasemustbeencryptedatrest
5.3.1.2. Allrequestanddatatransferbetweentheserverinthedatabasemustbedone
overanSSLconnection
5.3.1.3. Thedatabasemustonlybeaccessiblebydevicesonthesamenetwork
5.3.2. Application
5.3.2.1. AllcommunicationbetweentheserverandClinicianApplicationwillbedoneover
SSL.
5.3.3. SessionApp
5.3.3.1. Allpatientinformationstoredlocallyonthecomputerrunningthesessionapp
mustbeencrypted
5.3.3.2. AllcommunicationbetweentheserverandSessionappwillbedoneoverSSL

5.4. SoftwareQualityAttributes

5.4.1. Database
5.4.1.1. Databaseisnormalized
5.4.1.2. AJgivesapprovalofdatabaseschema
5.4.2. Application
5.4.2.1. Clinicianapplicationisratedat
orabovebyatleast85%ofcliniciansfor
aesthetics
5.4.2.2. Clinicianapplicationisratedat
orabovebyatleast80%ofcliniciansforeaseof
use
5.4.2.3. Clinicianapplicationisratedat
orabovebyatleast90%ofcliniciansforeaseof
learning
5.4.3. SessionApp
5.4.3.1. Sessionappisratedat orabovebyatleast85%offacilitatorsforaesthetics
5.4.3.2. Sessionappisratedat orabovebyatleast80%offacilitatorsforeaseofuse
5.4.3.3. Sessionappisratedat orabovebyatleast90%offacilitatorsforeaseof
learning

AppendixA:Glossary
1. ThetermClinicianPortalorCPreferstothewebbaseduserinterfacethatmostclinic
workerswillusetointeractwiththedatabase.ThismaybereferredtoastheDesktop
Applicationinolderdocumentation.