66. EPMO Open Source Coordination Office Redaction File Detail Report

Produced by Araxis Merge on 11/8/2016 5:25:12 PM Eastern Standard Time. See www.araxis.com for information about Merge. This report uses XHTML and CSS2, and is best viewed with a modern standards-compliant browser. For optimum results when printing this report, use landscape orientation and enable printing of background images and colours in your browser.

66.1 Files compared

#	Location	File	Last Modified
1	rxrefill-v2.0.0 P2.zip	Rx+Refill+(RXR)+Requirements+Specification+Document+(RSD)+-+Addendum.docx	Fri Nov 4 21:49:40 2016 UTC
2	rxrefill-v2.0.0 P2.zip	Rx+Refill+(RXR)+Requirements+Specification+Document+(RSD)+-+Addendum.docx	Mon Nov 7 00:01:05 2016 UTC

66.2 Comparison summary

Description	Between Files 1 and 2
Description	Text Blocks	Lines
Unchanged	11	1910
Changed	10	20
Inserted	0	0
Removed	0	0

66.3 Comparison options

Whitespace
Character case	Differences in character case are significant
Line endings	Differences in line endings (`CR` and `LF` characters) are ignored
CR/LF characters	Not shown in the comparison detail

66.4 Active regular expressions

No regular expressions were active.

66.5 Comparison detail

	1	Rx Refill (RXR) Requ irements S pecificati on Documen t (RSD) - Addendum
	2	Veterans H ealth Admi nistration (VHA)
	3	Mobile App lications Requiremen ts Addendu m
	4	Rx Refill (RXR) Requ irements S pecificati on Documen t - Addend um
	5	Increment/ Release #: v2
	6	Version in formation is require d for fina l SQA test ing
	7	Name of Mo bile Appli cation:
	8	Rx Refill
	9	Name of JI RA Project :
	10	RX Refill - Prescrip tion Refil l
	11	Descriptio n of Mobil e Applicat ion:
	12	Date
	13	RSD/ARD MA
	14	Addendum V ersion
	15	Author
	16	Descriptio n of Docum ent Change
	17	Associated BRD
	18	Version
	19	Associated Concept/
	20	Scope Vers ion
	21	Other Asso c.
	22	Other Asso c.
	23	04/06/2016
	24	v6.0
	25	M. Lucas
	26	Updated do cument dur ing Sprint 6
	27
	28
	29
	30
	31	02/16/2016
	32	v5.0
	33	M. Lucas
	34	Updated d ocument du ring Sprin t 5
	35
	36
	37
	38
	39	11/24/2015
	40	v4.0
	41	J. Millard
	42	Incorpora ted Change Order
	43
	44
	45
	46
	47	06/08/201 5
	48	v3.0
	49	L. Kirby
	50	Added addi tional Fun ctional Re quirements
	51
	52
	53
	54
	55	06/02/201 5
	56	v2.0
	57	L. Kirby
	58	Revised Ap plication Workflow
	59
	60
	61
	62
	63	02/18/201 5
	64	v1.0
	65	L. Kirby/ M.Lucas
	66	Initial
	67
	68
	69
	70
	71	Applicatio n Owner/An alyst/PM C ontact Inf ormation
	72	Applicatio n Owner/An alyst Name /Point of Contact (P OC)
	73	Eric Spah n
	74	VA E-Mail Address
	75	PII
	76	Phone Numb er
	77	PII
	78	Developer Organizati on/Company
	79	Hewlett-P ackard Ent erprise Se rvices
	80	Contract S tart Date
	81	09/24/201 4
	82	Contract E nd Date
	83	07/10/2017
	84	Web and Mo bile Solut ions PM or POC
	85	Constance Murphy
	86	VA E-Mail Address
	87	PII
	88	Phone Numb er
	89	PII
	90	VA Product Developme nt PM or P OC
	91	N/A
	92	VA E-Mail Address
	93	N/A
	94	Phone Numb er
	95	N/A
	96	Mobile App lication I nformation
	97	Intended A udience (U ser) for M obile Appl ication: I ntended Au dience (Us er) for Mo bile Appli cation: _ x_Veteran __Caregiv er __Prov ider __Pu blic
	98	Scope of I ntegration
	99	Currently the Depart ment of Ve terans Aff airs (VA) sends the majority o f outpatie nt Rx’s to Veteran p atients vi a mail. In order t o track th e delivery of mailed prescript ion medica tions, VA patients m ust (1) ca ll their l ocal Veter ans Admini stration M edical Cen ter (VAMC) directly and wait f or a repre sentative to look up their ord er and con nect them to the car rier respo nsible for deliverin g the ship ment or (2 ) Veteran patients c an track t he deliver y of their VA prescr iptions on line throu gh My Heal theVet at DNS from the Prescripti on Refill, Prescript ion Histor y, and/or the main P rescriptio n Track De livery. Pa tients can also use the My Hea ltheVet ap plications to manage their pre scriptions . To improve upon this process t he project will enha nce the Pr escription Refill mo bile appli cation to allow Vete rans to tr ack their prescripti on shipmen ts and ret rieve expe cted deliv ery date(s ) and time (s) via a mobile dev ice. The Rx Ref ill mobile applicati on shall b e modified to includ e links to the presc ription ma il provide r United S tates Post al Service (USPS) an d/or contr acted mail carrier s hipment de tails ther eby permit ting the u ser with a n ability to track t he status online. The conten t displaye d on the R x Refill m obile appl ication sh all use as much of t he informa tion in My HealtheVe t (MHV) as possible and make u se of exis ting MHV s ervices, w here appro priate. In additio n, the Con tractor sh all includ e the name and pictu re of the prescripti on medicat ion(s) wit hin the RX Refill mo bile appli cation if available. The applic ation will also leve rage Medic ation Imag e Library (MIL) data from the VA Corpora te Data Wa rehouse (C DW) within the appli cation.
	100	The scope of these e nhancement s is to pr ovide Vete rans with more relia ble and be tter defin ed informa tion relat ed to thei r prescrip tions and the tracki ng of thei r delivery by utiliz ing the Rx Refill mo bile appli cation.
	101	Applicatio n Expected Workflow
	102
	103	Laws and R egulation
	104	Section 50 8 of the R ehabilitat ion Act (2 9 U.S.C. § 794d), as amended b y the Work force Inve stment Act of 1998 ( P.L. 105-2 20), Augus t 7, 1998.
	105	Legal, Cop yright, an d Other No tices
	106	Section 50 8 of the R ehabilitat ion Act (2 9 U.S.C. § 794d), as amended b y the Work force Inve stment Act of 1998 ( P.L. 105-2 20), Augus t 7, 1998.
	107	Business N eeds
	108	Ref. ID
	109	Need
	110	Business V alue
	111	1.
	112	Adhere to the Enterp rise Level requireme nts within the Enter prise Mana gement (ER M) Reposit ory.
	113	To meet en terprise a nd applica tion speci fic nonfun ctional re quirements for VA ap proval.
	114	2.
	115	Utilize na tionally s tandardize d terminol ogy.
	116	Utilize na tionally s tandardize d terminol ogy.
	117	3.
	118	Ability to refill VA Refillabl e Medicati ons from a mobile ap plication.
	119	So that us ers can re fill their VA Medica tions inde pendent of access to a persona l computer .
	120	4.
	121	Ability to track pre scription delivery i nformation from a mo bile appli cation.
	122	So that us ers can tr ack prescr iptions de livery ind ependent o f access t o a person al compute r.
	123	5.
	124	Ability to access Pr escription History f rom a mobi le applica tion.
	125	So that us ers can vi ew their P rescriptio n History Informatio n independ ent of acc ess to a p ersonal co mputer.
	126	6.
	127	Ability to view Medi cation Ima ge from a mobile app lications.
	128	So that us ers can vi ew images of their p rescriptio n independ ent of acc ess to a p ersonal co mputer.
	129	7.
	130	Setup of a developme nt and tes t environm ent.
	131	So that th e developm ent and te st teams m ay begin d eveloping and testin g the appl ication.
	132	System Fea tures
	133	Feature N ame
	134	Inputs
	135	Outputs
	136	Refillable VA Medica tions
	137	Retrieves refill inf ormation f rom MHV.
	138	Displays p atient ref illable VA medicatio ns.
	139	Track Deli very
	140	Gets track ing inform ation from MHV patie nt prescri ptions.
	141	Displays t racking in formation and links to externa l carrier shipping s ite.
	142	Prescripti on History
	143	Retrieves prescripti on history for patie nts from M HV.
	144	Displays h istorical prescripti on informa tion.
	145	RxRefill a nd Trackin g Service
	146	Takes inpu t from Mob ile applic ation.
	147	Returns re fill and t racking da ta.
	148	Medication Image Lib rary Servi ce
	149	Takes inpu t from the Medical I mage Libra ry.
	150	Returns im age for pr escription .
	151	References
	152	Reference Descriptio n
	153	Link or At tachment
	154	Business R equirement s Document - BRD
	155
	156
	157
	158	Program Le vel Requir ement Chan ges
	159	Required C hanges to Mobile App lications Program-Le vel RSD
	160	JIRA Chang e Request Issue Numb er
	161	Link or At tachment o f Change P ages
	162	RXR-001
	163	N/A
	164	The requir ements add ed are doc umented in an epic i n JIRA:
	165	https:// DNS /browse/RX R-1206
	166	RXR-002
	167	N/A
	168	The requir ements add ed are doc umented in an epic i n JIRA: ht tps:// DNS /browse/RX R-1235
	169	Requiremen ts
	170	Functional Requireme nts
	171	Epic
	172	JIRA Story ID
	173	User Story
	174	Change Ord er - TRM a nd library updates
	175	RXR-1189
	176	As an RXR developer, I would l ike to upg rade Jasmi ne from ve rsion 2.1 to version 2.3, so t hat the en vironment is running on the mo st up to d ate TRM ap proved ver sion.
	177	Change Ord er - TRM a nd library updates
	178	RXR-1191
	179	As an RXR developer, I would l ike to upg rade the R XR Resourc e service to align J ersey libr aries with those run ning in th e Health A dapter, so that the libraries running be have as ex pected wit hout libra ry collisi ons.
	180	Change Ord er - TRM a nd library updates
	181	RXR-1193
	182	As an RXR developer I would li ke to upgr ade the MI L Resource service t o align Je rsey libra ries with those runn ing in the Health Ad apter, so that the l ibraries r unning beh ave as exp ected with out librar y collisio ns.
	183	Change Ord er - TRM a nd library updates
	184	RXR-1188
	185	As an RXR developer, I would l ike to upg rade Handl ebars from version 1 .0.12 to v ersion 2.0 .0, so tha t the envi ronment is running o n the most up to dat e TRM appr oved versi on.
	186	Change Ord er - TRM a nd library updates
	187	RXR-1190
	188	As an RxR developer, I would l ike to upg rade SASS, so that t he environ ment is ru nning on t he most up to date T RM approve d version.
	189	Disclaimer
	190	RXR-554
	191	As a RxR t eam member , I want t o create a mechanism for resiz ing MIL im ages, so t hat the im ages can b e used on a mobile p latform.
	192	Error Desc riptions
	193	RXR-1009
	194	As an RxR business o wner, I ne ed to prov ide user f riendly er ror descri ptions, so that Vete rans have meaningful error des criptions to allow t hem to res olve any p otential e rrors.
	195	Error Desc riptions
	196	RXR-1013
	197	As an RxR developer, I need to incorpora te the use r friendly error des cription t hat were p rovided by the busin ess wwner into the e xception h andling of each webs ervice end point, so that use r friendly error mes sages can be provide d to a cal ling appli cation.
	198	Error Desc riptions
	199	RXR-974
	200	As a RxR d eveloper, I want to implement oAuth secu rity for a ll non-pub lic webser vice endpo ints, so t hat endpoi nts are pr otected.
	201	Logout
	202	RXR-1130
	203	As a RXR d eveloper, I would li ke to upda te/verify that the l ogin funct ionality i s consiste nt with ot her MAP2 a pps and to integrate it with R OA, so tha t a common workflow for login is achie ved.
	204	Logout
	205	RXR-1131
	206	As a Veter an, I want the appli cation to integrate with the V AMF author ization me chanism fo r logout s o that the user can see they a re logged out of the applicati on.
	207	Medication Image Lib rary Servi ce
	208	RXR-563
	209	As a RxRef ill develo per, I wan t to creat e the proj ect struct ure and sh ell along with build scripts f or the VAM F MIL Serv ice so tha t a web se rvice proj ect can be initiated to provid e medicati on images from the M IL for VAM F applicat ions.
	210	Medication Image Lib rary Servi ce
	211	RXR-564
	212	As a RxRef ill develo per, I wan t to creat e a medica tion image metadata endpoint w ithin the VAMF MIL S ervice so that medic ation imag e metadata from the CDW MIL da tabase can be provid e to VAMF applicatio ns.
	213	Medication Image Lib rary Servi ce
	214	RXR-565
	215	As a RxRef ill develo per, I wan t to creat e a MIL im age endpoi nt within the VAMF M IL Service so that m edication image from the CDW M IL databas e can be p rovide to VAMF appli cations.
	216	Medication Image Lib rary Servi ce
	217	RXR-566
	218	As a RxRef ill develo per, I wan t to creat e a MIL im ages endpo int withi n the VAMF MIL Servi ce so that a list o f medicati on images from the C DW MIL dat abase can be provide to VAMF a pplication s.
	219	Medication Image Lib rary Servi ce
	220	RXR-567
	221	As a RxRef ill develo per, I wan t to creat e a MIL im age proper ties endpo int with t he VAMF MI L Service so that pr operties a bout a med ication im age from t he CDW MIL database can be pro vide to VA MF applica tions.
	222	Medication List on M yHealtheVe t
	223	RXR-568
	224	As a Veter an using t he RxRefil l applicat ion, I nee d access t o the My C omplete Me dication L ist via a link to MH V, so that I can vie w all my m edications .
	225	Medication List on M yHealtheVe t
	226	RXR-569
	227	As a Veter an using t he RxRefil l applicat ion, I nee d access t o my Blue Button Dow nload via a link to MHV, so th at I acces s my Blue Button dat a.
	228	Medication List on M yHealtheVe t
	229
	230	As a Veter an using t he RxRefil l applicat ion, I nee d access t o my Healt h Summary (VA CCD) v ia a link to MHV, so that I ca n view all my CCD da ta.
	231	Medication Image
	232	RXR-553
	233	As a Veter an, I want to see me dication d etail on a prescript ion select ed from th e prescrip tion histo ry screen, so that I can easil y view det ailed info rmation on a presc ription.
	234	Prescripti on History
	235	RXR-551
	236	As a Veter an, I want to see my VA prescr iptions, s o that I c an view de tailed inf ormation o n a prescr iption.
	237	Prescripti on History
	238	RXR-552
	239	As a Veter an, I want to sort m y VA presc riptions o n the pres cription h istory scr een, so th at I can v iew detail ed informa tion on a prescripti on.
	240	Prescripti on History
	241	RXR-550
	242	As a Veter an, I want to track my prescri ption, so that I can determine where it is.
	243	Refillable VA Medica tion
	244	RXR-696
	245	As a proje ct team, w e must ens ure that f ollowing 1 5 minutes of inactiv ity by the current u ser our ap plication time-outs so that ou r applicat ion effici ently used the limit ed resourc es that ma ybe availa ble to the user.
	246	Refillable VA Medica tion
	247	RXR-697
	248	As a Veter an, I want to see my active/re fillable V A prescrip tions, so that I can view deta iled infor mation on a prescrip tion and r efill it w hen approp riate.
	249	Refillable VA Medica tion
	250	RXR-698
	251	As a Veter an, I want to sort m y active/r efillable VA prescri ptions, so that I ca n view det ailed info rmation on a prescri ption and refill it when appro priate.
	252	Refillable VA Medica tion
	253	RXR-699
	254	As a Veter an, I want to see me dication d etail on m y active/r efillable VA prescri ptions, so that I ca n easily v iew detail ed informa tion on a prescripti on.
	255	Refillable VA Medica tion
	256	RXR-1016
	257	As a Veter an, I want to see an image d isclaimer before vie wing the s elected me dication f or trackab le medic ation, so that I am aware the image is for ident ification purposes only.
	258	Refillable VA Medica tion
	259	RXR-1017
	260	As a RxR d eveloper, I want to create a refillabl e prescrip tion endpo int within the VAMF RxRefill S ervice, so that on ly refilla ble prescr iptions ca n be provi ded to the RxRefill applicat ion.
	261	Refillable VA Medica tion
	262	RXR-1018
	263	As a Veter an, I want to see on ly refilla ble prescr iptions in the Refil lable VA M edications screen, s o that I c an quickly review an d refill m y refillab le medicat ions.
	264	Right of A ccess
	265	RXR-1107
	266	As a Vete ran, I wan t to appro ve the rel ease of my health in formation, so that I may be gr anted acce ss to my i nformation via the R XR mobile applicatio n.
	267	RxRefill a nd Trackin g Service
	268	RXR-562
	269	As a RxRef ill develo per, I wan t to creat e a medica tion refil l request endpoint w ithin the VAMF RxRef ill Servic e so that details on prescript ions that have bee n successf ully refil led by the VAMF RxRe fill app.
	270	RxRefill a nd Trackin g Service
	271	RXR-556
	272	As a RxRef ill develo per, I wan t to creat e the proj ect struct ure and sh ell along with build scripts f or the VAM F RxRefill Service s o that a w eb service project c an be in itiated to provide R xRefill an d Tracking informati on for the RxRefill applicatio n.
	273	RxRefill a nd Trackin g Service
	274	RXR-557
	275	As a RxRef ill develo per, I wan t to creat e an activ e prescrip tions endp oint withi n the VAMF RxRefill Service so that acti ve prescri ptions fro m the Ente rprise Tra cking and Refill ser vice can b e provided to the Rx Refill App lication.
	276	RxRefill a nd Trackin g Service
	277	RXR-558
	278	As a RxRef ill develo per, I wan t to creat e a histor ical presc riptions e ndpoint wi thin the V AMF RxRefi ll Service so that h istorical prescripti ons from t he Enter prise Trac king and R efill serv ice can b e provided to the Rx Refill App lication.
	279	RxRefill a nd Trackin g Service
	280	RXR-559
	281	As a RxRef ill develo per, I wan t to creat e a presc ription re fill endpo int within the VAMF RxRefill S ervice so that a pre scription refill req uest can b e submitte d to the E nterprise Tracking a nd Refill service vi a the RxRe fill Appli cation.
	282	RxRefill a nd Trackin g Service
	283	RXR-560
	284	As a RxRef ill develo per, I wan t to creat e a tracka ble prescr iptions en dpoint wit hin the VA MF RxRefil l Service so that tr ackable pr escription s from the Enterpris e Tracking and Refil l service can be pro vided to t he RxRefil l App.
	285	RxRefill a nd Trackin g Service
	286	RXR-561
	287	As a RxRef ill develo per, I wan t to creat e a tracka ble prescr iption det ail endpoi nt within the VAMF R xRefill Se rvice so t hat detail ed trackin g informat ion on a p rescriptio n from the Enterpris e Tracking and Refil l service can be pro vided to t he RxRefil l App.
	288	RxRefill a nd Trackin g Service
	289	RXR-700
	290	As a Veter an, I want to reques t a refill on my act ive/refill able VA pr escription s, so that I can ref ill my VA medication s.
	291	RxRefill a nd Trackin g Service
	292	RXR-973
	293	As a RxR d eveloper, I want to develop a mechanism to lookup a Veteran’ s mhvCorre lationId, so that I can implem ent busine ss logic w ithin the RXR Sessio n endpoint .
	294	RxRefill a nd Trackin g Service
	295	RXR-555
	296	As a RxR t eam member , I want t o provide a disclaim er for the Veteran, so that th e applicat ion inform s the user to take m edication as prescri bed.
	297	Track Deli very
	298	RXR-545
	299	As a Veter an, I want the abili ty to see a list of my VA pres criptions that have been shipp ed so I ca n determin e when I w ill recei ve my VA m edication by mail.
	300	Track Deli very
	301	RXR-546
	302	As a Veter an, I want to sort m y trackabl e prescrip tions, so that I can ultimatel y view det ailed info rmation on tracking and shipme nt.
	303	Track Deli very
	304	RXR-547
	305	As a Veter an, I want the optio n to see a n importan t informat ion screen when I se lect track ing delive ry details so that I can be in formed on tracking d etail in formation.
	306	Track Deli very
	307	RXR-548
	308	As a Veter an, I want to see de tail track ing inform ation for my trackab le prescri ptions, so that I tr ack and de termine wh ere my med ication is .
	309	Track Deli very
	310	RXR-549
	311	As a Veter an, I want to see an image of my medicat ion for tr ackable pr escription s, so that I can com pare what was shippe d to what I received
	312	Track Deli very
	313	RXR-1014
	314	As a Veter an, I want to see us er friendl y error me ssages whe n an error occurs, s o that I u nderstand how to cor rect the e rror or be provided with a mec hanism for assistanc e.
	315	Track Deli very
	316	RXR-1015
	317	As a Veter an, I want to see “I mage not a vailable” when an im age for me dication i s selected and is no t availabl e for trac kable medi cation, so that I se e an image is not av ailable in clear, re adable lan guage.
	318	Track Deli very
	319	RXR-539
	320	As a Rx Re fill team member, I want to cr eate the f ooter area of the si ngle page applicatio n so that the RXR ap plication displays g eneral inf ormation a bout the a pplication and the u ser.
	321	Web Applic ation Temp late
	322	RXR-538
	323	As a Rx Re fill team member, I want to cr eate the s ingle page applicati on templat e so that the RXR ap plication has a defi ned struct ure.
	324	Web Applic ation Temp late
	325	RXR-570
	326	As a Veter an using t he RxRefil l applicat ion, I nee d access t o my Healt h Summary (VA CCD) v ia a link to MHV, so that I ca n view all my CCD da ta.
	327	Web Applic ation Temp late
	328	RXR-690
	329	As a Rx Re fill team member, I want to cr eate the H ome/Landin g page for the RXR a pplication so that t he user ha s quick ac cess to th e major el ements pro vided by t he applica tion.
	330	Web Applic ation Temp late
	331	RXR-691
	332	As a Rx Re fill team member, I want to cr eate a qui ck access navigation element i n the bann er of the RXR applic ation so t hat the us er has qui ck access to the maj or element s provided by the ap plication.
	333	Web Applic ation Temp late
	334	RXR-692
	335	As a Rx Re fill team member, I want to cr eate a Hel p page so that the u ser is pro vided with help info rmation re lating to the applic ation by t he applica tion.
	336	Web Appli cation Tem plate
	337	RXR-693
	338	As a Rx Re fill team member, I want to cr eate an Ab out page s o that the user is p rovided wi th about i nformation relating to the app lication b y the appl ication.
	339	Web Appli cation Tem plate
	340	RXR-694
	341	As a Rx Re fill team member, I want to in tegrate wi th the VAM F authoriz ation mech anism for login so t hat the us er can be authentica ted prior to enterin g the appl ication.
	342	Change Ord er: Upgrad e for Auth Services 4 .4.0
	343	RXR-1236
	344	As an RXR (MT) Devel oper, I ne ed to inco rporate th e oAuth Li b Spring M VC Control ler into m y applicat ion so tha t the Fron t End can query MT f or oAuth c lient deta ils and ca n request MT to brok er calls f or obtaini ng oauth t okens give n the oAut h code.
	345	Change Ord er: Upgrad e for Auth Services 4 .4.0
	346	RXR-1237
	347	As a UI De veloper, I want to u tilize the Auth Func tions wrap per to ini tialize th e applicat ion, so th at user ca n see if t hey are au thenticate d properly .
	348	Change Ord er: Upgrad e for Auth Services 4 .4.0
	349	RXR-1238
	350	As a SQA T ester, I n eed to reg ression te st the use of Token validation services with Autho rization S ervices 4. 4 to ensur e that the service p rotection continues to work
	351	Change Ord er: Upgrad e for Auth Services 4 .4.0
	352	RXR-1239
	353	As a SQA T ester, I n eed to ens ure that t he Inactiv ity timeou t function ality cont inues to f unction as before wi th Authori zation Ser vices 4.4, so that I can verif y the upgr ade did no t impact t imeout.
	354	Change Or der: Upgra de for Aut hServices 4.4.0
	355	RXR-1240
	356	As a SQA T ester, I n eed to ens ure that t he Logout functions continue t o perform as before with Autho rization S ervices 4. 4, so that I can ver ify that I can logou t of the s ystem.
	357
	358	Applicatio n-Specific Non-Funct ional Requ irements ( NFRs)
	359	These NFRs are liste d in the B RD and usu ally assig ned to BN 1: Adhere to the Ent erprise Le vel requir ements wit hin the En terprise M anagement (ERM) Repo sitory, an d BN 2: Ut ilize nati onally sta ndardized terminolog y.
	360	Enterprise -Wide Non- Functional Requireme nts (NFRs)
	361	As a proje ct team, w e must ens ure that w e are suff iciently d escribing all elemen ts, otherw ise we wil l not be S ection 508 compliant .
	362	JIRA Story ID
	363	EWNFR JIRA ID
	364	User Story /Guidance
	365	RXR-138
	366	EWNFR-529
	367	As a proje ct team, w e must fol low the SN OMED stand ard for cl inical ter ms so that the clini cal data a nd termino logy used within our applicati on conform s to natio nal standa rds.
	368	RXR-140
	369	EWNFR-530
	370	As a proje ct team, w e must fol low the LO INC standa rd for lab oratory te rms so tha t the clin ical data and termin ology used within ou r applicat ion confor ms to nati onal stand ards.
	371	RXR-142
	372	EWNFR-531
	373	As a proje ct team, w e must fol low the RX Norm stan dard for p harmacy te rms so tha t the clin ical data and termin ology used within ou r applicat ion confor ms to nati onal stand ards.
	374	RXR-144
	375	EWNFR-532
	376	As a proje ct team, w e must ide ntify othe r clinical data elem ents that are eligib le for sub mission to the Data and Termin ology comp liance gro up so that the docum entation w e submit f or the com pliance re view is co mplete and accurate.
	377	RXR-146
	378	EWNFR-533
	379	Guidance: it is reco mmended th at the pro ject team documents other clin ical data elements t hat are el igible for submissio n. This is so the in formation can quickl y and effi ciently be provided to the Dat a and Term inology St andards co mpliance g roup.
	380	RXR-147
	381	EWNFR-539
	382	Guidance: it is reco mmended th at the pro ject team document h ow all cli nical data is captur ed within the applic ation. Thi s is so th e informat ion can qu ickly and efficientl y be provi ded to the Data and Terminolog y Standard s complian ce group.
	383	RXR-148
	384	EWNFR-540
	385	Guidance: it is reco mmended th at the pro ject team document h ow all cli nical data is stored within th e applicat ion. This is so the informatio n can quic kly and ef ficiently be provide d to the D ata and Te rminology Standards compliance group.
	386	RXR-92
	387	EWNFR-312
	388	As a proje ct team, w e must inc lude an En d User Lic ense Agree ment (EULA ) that sta tes that t he Veteran owns all the data t hat has be en pulled from a VA database a nd stored on their d evice othe rwise our applicatio n risks no n-approval from the Privacy an d Security complianc e group.
	389	RXR-95
	390	EWNFR-313
	391	As a proje ct team, w e must inc lude an En d User Lic ense Agree ment (EULA ) that sta tes that t he Veteran is only g iven tempo rary acces s to the d ata in a V A database through t heir devic e otherwis e our risk s non-appr oval from the Privac y and Secu rity compl iance grou p.
	392	RXR-97
	393	EWNFR-314
	394	As a proje ct team, w e must ens ure that a ll data en tered by t he Veteran into our applicatio n (but not transmitt ed to the VA) is sec urely stor ed on the user’s dev ice.
	395	RXR-99
	396	EWNFR-315
	397	Guidance: all data e ntered by the Vetera n into the applicati on (and tr ansmitted to the VA) is covere d by a Pri vacy Act o r records otherwise our applic ation risk s non-appr oval from the Privac y and Secu rity compl iance grou p.
	398	RXR-105
	399	EWNFR-316
	400	As a proje ct team, w e must inc lude an En d User Lic ense Agree ment (EULA ) that sta tes that t he VA will receive t he data en tered by t he Veteran on the de vice our a pplication risks non -approval from the P rivacy and Security compliance group.
	401	RXR-100
	402	EWNFR-318
	403	As a proje ct team, w e must ens ure that V A data pul led from a VA databa se and dis played to a VA Provi der is not stored on the devic e otherwis e our appl ication ri sks non-ap proval fro m the Priv acy and Se curity com pliance gr oup.
	404	RXR-103
	405	EWNFR-321
	406	As a proje ct team, w e must ens ure that u ser accoun t informat ion (PID) is not tra nsferred t o our appl ication ot herwise ou r applicat ion risks non-approv al from th e Privacy and Securi ty complia nce group.
	407	RXR-82
	408	EWNFR-698
	409	Guidance: all applic ations and services should be written in complianc e with OWA SP guideli nes which VA Securit y referenc es for bes t practice s in web a pplication security.
	410	RXR-83
	411	EWNFR-699
	412	As a proje ct team, w e must ens ure that o ur applica tion passe s a Fortif y scan (Co de Review) where the re are no Critical o r High iss ues report ed so that our appli cation suc cessfully completes the Enterp rise Secur ity compli ance proce ss.
	413	RXR-85
	414	EWNFR-711
	415	As a proje ct team, w e must ens ure that a ll Moderat e and Low issues rem aining in our applic ation at i nitial rel ease for b oth the Fo rtify and WASA/MASA scans must be captur ed in a Pl an of Acti on and Mil estones (P OA&M) repo rt so that we show t hat there is a plan for future remediati on of rema ining issu es.
	416	RXR-87
	417	EWNFR-712
	418	As a proje ct team, w e must ens ure that o ur applica tion passe s a WASA/M ASA scan w here there are no Cr itical or High issue s reported so that o ur applica tion succe ssfully co mpletes th e Enterpri se Securit y complian ce process .
	419	RXR-89
	420	EWNFR-720
	421	Guidance: all applic ations mus t obtain s ignoff of the SSP Ad dendum and load the signed SSP Addendum into the R isk Vision .
	422	RXR-150
	423	EWNFR-20
	424	Guidance: usability testing mu st occur i n a dedica ted test e nvironment that is s eparate fr om both th e developm ent and pr oduction e nvironment s.
	425	RXR-153
	426	EWNFR-25
	427	As a proje ct team, w e must use mixed cas e text wit hin the ap plication so that ou r applicat ion will e nhance the user’s ex perience w ith our ap plication.
	428	RXR-157
	429	EWNFR-26
	430	As a proje ct team, w e must use simple an d consiste nt button labels so that our a pplication will enha nce the us er’s exper ience with our appli cation.
	431	RXR-163
	432	EWNFR-27
	433	As a proje ct team, w e must lef t align pa ge/section titles to anchor ti tles in co nsistent l ocations o n all wind ows/screen s so that our applic ation will enhance t he user’s experience with our applicatio n.
	434	RXR-166
	435	EWNFR-28
	436	As a proje ct team, w e must lef t align th e labels f or fields so that ou r applicat ion will e nhance the user’s ex perience w ith our ap plication.
	437	RXR-168
	438	EWNFR-29
	439	As a proje ct team, w e must avo id using a cronyms/ab breviation s so that our applic ation will enhance t he user’s experience with our applicatio n.
	440	RXR-171
	441	EWNFR-30
	442	As a proje ct team, w e must pro vide “Help ” informat ion and/or a tooltip when we u se acronym s/abbrevia tions due to screen space limi tations so that our applicatio n will enh ance the u ser’s expe rience wit h our appl ication.
	443	RXR-173
	444	EWNFR-31
	445	As a proje ct team, w e must use the color s red and green only for statu s driven c ontent wit h our appl ication so that our applicatio n will enh ance the u ser’s expe rience wit h our appl ication.
	446	RXR-176
	447	EWNFR-32
	448	As a proje ct team, w e must pro vide visua l separati on between the navig ation spac e and the main-conte nt area so that our applicatio n will enh ance the u ser’s expe rience wit h our appl ication.
	449	RXR-179
	450	EWNFR-33
	451	As a proje ct team, w e must hav e field le vel valida tion and n otificatio ns for mis sing and i nvalid inf ormation o n the same page so t hat our ap plication will enhan ce the use r’s experi ence with our applic ation.
	452	RXR-182
	453	EWNFR-34
	454	As a proje ct team, w e must hav e a consis tent style for text hyperlinks within ou r applicat ion so tha t our appl ication wi ll enhance the user’ s experien ce with ou r applicat ion.
	455	RXR-185
	456	EWNFR-41
	457	Guidance: to enhance the user’ s experien ce with th e applicat ion, defin e and adhe re to a mo del for th e design e lements wi thin the a pplication .
	458	RXR-186
	459	EWNFR-43
	460	As a proje ct team, w e must mak e sure tha t text is sized to b e readable so that o ur applica tion will enhance th e user’s e xperience with our a pplication .
	461	RXR-188
	462	EWNFR-44
	463	As a proje ct team, w e must use consisten t location s when pla cing navig ation elem ents so th at our app lication w ill enhanc e the user ’s experie nce with o ur applica tion.
	464	RXR-190
	465	EWNFR-45
	466	As a proje ct team, w e must pla ce critica l informat ion in the top porti on of the screen so that our a pplication will enha nce the us er’s exper ience with our appli cation.
	467	RXR-192
	468	EWNFR-46
	469	To enhance the user’ s experien ce with th e applicat ion, creat e and use a consiste nt screen flow model within ou r applicat ion so tha t our appl ication wi ll.
	470	RXR-193
	471	EWNFR-47
	472	As a proje ct team, w e must use consisten t screen e lements wi thin our a pplication so that o ur applica tion will enhance th e user’s e xperience with our a pplication .
	473	RXR-195
	474	EWNFR-48
	475	Guidance: enhance th e user’s e xperience with our a pplication by using consistent screen te rms within the appli cation.
	476	RXR-196
	477	EWNFR-53
	478	As a proje ct team, w e must dis play field labels cl ose to the ir corresp onding ent ry element s on the s creen so t hat our ap plication will enhan ce the use r’s experi ence with our applic ation.
	479	RXR-198
	480	EWNFR-63
	481	As a proje ct team, w e must def ine a logi cal tab or der throug h fields o n a screen when the default ta b order is not suffi cient for our applic ation so t hat our ap plication will enhan ce the use r’s experi ence with our applic ation.
	482	RXR-200
	483	EWNFR-64
	484	As a proje ct team, w e must mak e sure tha t the erro r messages within th e applicat ion are in user-cent ric langua ge so that our appli cation wil l enhance the user’s experienc e with our applicati on.
	485	RXR-202
	486	EWNFR-65
	487	As a proje ct team, w e must mak e sure tha t the erro r messages within th e applicat ion contai n specific instructi on on the meaning of error so that our a pplication will enha nce the us er’s exper ience with our appli cation.
	488	RXR-204
	489	EWNFR-67
	490	As a proje ct team, w e must mak e sure tha t the erro r messages within th e applicat ion are co nsistently used and displayed so that ou r applicat ion will e nhance the user’s ex perience w ith our ap plication.
	491	RXR-208
	492	EWNFR-68
	493	As a proje ct team, w e must pro vide conte xt specifi c Help so that our a pplication will enha nce the us er’s exper ience with our appli cation.
	494	RXR-211
	495	EWNFR-70
	496	As a proje ct team, w e must pro vide an in dicator fo r non-visi ble text t hat prompt s the user to scroll so that o ur applica tion will enhance th e user’s e xperience with our a pplication .
	497	RXR-213
	498	EWNFR-365
	499	As a proje ct team, w e must ens ure color usage with in our app lication r eflects pu rpose of o ur applica tion so th at our app lication w ill enhanc e the user ’s experie nce with o ur applica tion.
	500	RXR-216
	501	EWNFR-366
	502	As a proje ct team, w e must pro vide Info button so that our a pplication will enha nce the us er’s exper ience with our appli cation.
	503	RXR-206
	504	EWNFR-66
	505	As a proje ct team, w e must mak e sure tha t the erro r messages within th e applicat ion contai n specific instructi on on how to recover from an e rror so th at our app lication w ill enhanc e the user ’s experie nce with o ur applica tion.
	506	RXR-219
	507	EWNFR-156
	508	As a proje ct team, w e must adh ere to the standard navigation of the de vice so th at consist ency exist s and user s do not h ave an add itional co gnitive lo ad to dete rmine diff erent navi gation met hods.
	509	RXR-221
	510	EWNFR-157
	511	As a proje ct team, w e must adh ere to the standard navigation practices of the pl atform’s o perating s ystem so t hat consis tency exis ts and use rs do not have an ad ditional c ognitive l oad to det ermine dif ferent nav igation me thods.
	512	RXR-223
	513	EWNFR-158
	514	As a proje ct team, w e must adh ere to the standard navigation practices of the de vice’s web -browser s o that con sistency e xists and users do n ot have an additiona l cognitiv e load to determine different navigation methods.
	515	RXR-225
	516	EWNFR-159
	517	As a proje ct team, w e must adh ere to the standard navigation practices implement ed by the VA so that consisten cy exists and users do not hav e an addit ional cogn itive load to determ ine differ ent naviga tion metho ds.
	518	RXR-227
	519	EWNFR-161
	520	As a proje ct team, w e must pre sent the c ontent of the applic ation cons istently t hroughout the applic ation so t hat consis tency exis ts and use rs are abl e to easil y find inf ormation.
	521	RXR-229
	522	EWNFR-163
	523	As a proje ct team, w e must use consisten t screen m ovement th roughout t he applica tion so th at consist ency exist s and user s do not h ave an add itional co gnitive lo ad to dete rmine how to perform functions .
	524	RXR-231
	525	EWNFR-164
	526	As a proje ct team, w e must pro vide immed iate feedb ack (.25) following user input activitie s so that the user i s aware th e applicat ion has re cognized t he user’s input.
	527	RXR-233
	528	EWNFR-165
	529	As a proje ct team, w e must pro vide a pro cessing in dicator fo r all task s, regardl ess of the ir duratio n, so that the user is aware t he applica tion is pr ocessing i nformation .
	530	RXR-235
	531	EWNFR-166
	532	As a proje ct team, w e must pro vide a rem aining pro cessing ti me indicat or for tas ks that wi ll take lo nger than 10 seconds so that t he user is aware the applicati on is proc essing inf ormation.
	533	RXR-237
	534	EWNFR-168
	535	As a proje ct team, w e must mak e sure tha t our appl ication pr operly rec ognizes an y standard physical gestures o f the devi ce so that confusion can be av oided by k eeping wel l tested, well estab lished ges ture stand ards.
	536	RXR-239
	537	EWNFR-169
	538	As a proje ct team, w e must mak e sure tha t we creat e our icon s based on the stand ards of th e device s o that the re is cons istency in the appli cation and we can av oid confus ion.
	539	RXR-242
	540	EWNFR-170
	541	As a proje ct team, w e must mak e sure tha t the scre ens of our applicati on adapt t o the orie ntation (p ortrait/la ndscape) o f the devi ce so that the appli cation wil l be consi stent with the user’ s expectat ions.
	542	RXR-244
	543	EWNFR-175
	544	As a proje ct team, w e must use clear ind icators th at instruc ts the use r how to m ove forwar d (when an activity requires a series of steps to complete) on our scr eens when the screen s are a st ep in an a ctivity so that cons istency ex ists and u sers do no t have an additional cognitive load to d etermine t he appropr iate activ ity workfl ow.
	545	RXR-246
	546	EWNFR-176
	547	As a proje ct team, w e must giv e the user a choice to complet e the task or abando n the task presented on a moda l screen i s used so that a cle ar choice for exit a nd control over acti ons for th e user.
	548	RXR-248
	549	EWNFR-177
	550	As a proje ct team, w e must mak e sure tha t when a l ist of opt ions is be ing displa yed to the user, all of the ch oices can be read wi thout scro lling (ver tical/hori zontal) so that the user’s mem ory load i s minimize d.
	551	RXR-250
	552	EWNFR-178
	553	As a proje ct team, w e must mak e sure tha t the titl e of any m odal scree n represen ts the tas k being pe rformed on the scree n so that the purpos e of the s creen is s imply unde rstood.
	554	RXR-252
	555	EWNFR-179
	556	As a proje ct team, w e must use the link name to in dicate the destinati on of the link so th at the pur pose of th e link is simply und erstood.
	557	RXR-255
	558	EWNFR-180
	559	As a proje ct team, w e must use short nam es for men us items t hat will n ot be trun cated when displayed on the us er’s devic e so that the purpos e of the m enu items are eviden t and user ’s memory load is mi nimized.
	560	RXR-257
	561	EWNFR-181
	562	As a proje ct team, w e must mak e sure the entire na me of our applicatio n is visib le when th e applicat ion icon t hat is dis played on the user’s device so that the full name of the app lication i s evident.
	563	RXR-259
	564	EWNFR-183
	565	As a proje ct team, w e must not allow for the conte nt of the screens wi thin the a pplication to take u p 80% of m ore of any screen wi thin the a pplication so that t he focus o f the scre en serves the applic ations pur pose.
	566	RXR-263
	567	EWNFR-186
	568	As a proje ct team, w e must use tappable elements t hat are 44 x44 points or larger so that t he user ca n easily s elect the element wi th their f ingertip a nd avoid a n incorrec t element selection by the use r.
	569	RXR-265
	570	EWNFR-188
	571	Selectable buttons t hat are ve rtically p laced one on top of the other with no wh ite space between th em. This p lacement i ncreases t he possibi lity of se lecting th e incorrec t button. If used, t here needs to be spa ce between verticall y stacked controls t o avoid mi s-selectio n by the u ser.
	572	RXR-268
	573	EWNFR-230
	574	As a proje ct team, w e must use the VA Ad ministrati on logo pr ovided in VA Mobile Style Guid e, otherwi se our app lication r isks non-a pproval fr om the VA Branding c ompliance group.
	575	VA Mobile Branding R equirement s and Reso urces ( DNS content/va -mobile-br anding-req uirements- resources) Source: VA Mobile St yle Guidel ines.
	576	RXR-271
	577	EWNFR-231
	578	As a proje ct team, w e must ref erence the latest av ailable VA Branding Graphics S tyle guide when inco rporating the VA Mob ile logo i nto our ap plication otherwis e our appl ication ri sks non-ap proval fro m the VA B randing co mpliance g roup.
	579	RXR-277
	580	EWNFR-232
	581	As a proje ct team, w e must use the VA He alth logo (If applic ation is s ponsored b y VHA) pro vided on t he VA Mobi le Brandin g website otherwise our applic ation risk s non-appr oval from the VA Bra nding comp liance gro up.
	582	RXR-279
	583	EWNFR-235
	584	As a proje ct team, w e must ref erence the latest av ailable VA Branding Graphics S tyle guide when inco rporating the VA Hea lth logo i nto our ap plication otherwise our applic ation risk s non-appr oval from the VA Bra nding comp liance gro up.
	585	RXR-282
	586	EWNFR-238
	587	As a proje ct team, w e must use the VA Mo bile logo on all ele ctronic me dia associ ated with our applic ation othe rwise our applicatio n risks no n-approval from the VA Brandin g complian ce group.
	588	RXR-288
	589	EWNFR-239
	590	As a proje ct team, w e must use the fonts listed wi thin the V A Branding Style Gui de for app lication c hiclets, s plash scre ens and co ntent othe rwise our applicatio n risks no n-approval from the VA Brandin g complian ce group.
	591	RXR-292
	592	EWNFR-240
	593	As a proje ct team, w e must use the appro priate adm inistratio n color pa lette desc ribed in t he latest VA Brandin g Style Gu ide otherw ise our ap plication risks non- approval f rom the VA Branding compliance group.
	594	RXR-298
	595	EWNFR-241
	596	As a proje ct team, w e must cre ate the ch icklet for our appli cation usi ng the app ropriate r equirement s (based o n administ ration) li sted in th e latest V A Branding Style Gui de otherwi se our app lication r isks non-a pproval fr om the VA Branding c ompliance group.
	597	RXR-308
	598	EWNFR-242
	599	As a proje ct team, w e must cre ate the sp lash scree n for our applicatio n using th e requirem ents liste d in the l atest VA B randing St yle Guide otherwise our applic ation risk s non-appr oval from the VA Bra nding comp liance gro up.
	600	RXR-316
	601	EWNFR-243
	602	As a proje ct team, w e must nam e our appl ication in a manner that descr ibes the f unctionali ty of the applicatio n otherwis e our appl ication ri sks non-ap proval fro m the VA B randing co mpliance g roup.
	603	RXR-321
	604	EWNFR-675
	605	As a proje ct team, w e must VA brand all web pages within the applicati on using t he respons ive templa te documen ted in the latest VA Branding Style Guid e otherwis e our appl ication ri sks non-ap proval fro m the VA B randing co mpliance g roup.
	606	RXR-323
	607	EWNFR-676
	608	As a proje ct team, w e must VA brand all mobile pag es within the applic ation usin g the resp onsive tem plate docu mented in the latest VA Brandi ng Style G uide other wise our a pplication risks non -approval from the V A Branding complianc e group.
	609	RXR-325
	610	EWNFR-677
	611	As a proje ct team, w e must ens ure our gr aphics use the appro priate dpi for mobil e devices to ensure that graph ics are co nsistently of a good resolutio n and are not blurry or pixela ted otherw ise our ap plication risks non- approval f rom the VA Branding compliance group.
	612	RXR-327
	613	EWNFR-678
	614	As a proje ct team, w e must ens ure our im ages use t he appropr iate dpi f or mobile devices to ensure th at graphic s are cons istently o f a good r esolution and are no t blurry o r pixelate d otherwis e our appl ication ri sks non-ap proval fro m the VA B randing co mpliance g roup.
	615	RXR-331
	616	EWNFR-374
	617	As a proje ct team, w e must pre vent incor rect data entry so t hat we can stop the user from entering i ncorrect d ata into o ur applica tion, and also preve nt incorre ct action selection so that th e user can more easi ly interac t with our applicati on and avo id errors.
	618	RXR-333
	619	EWNFR-375
	620	As a proje ct team, w e must (if applicabl e) only pr ovide writ e access t o EHR data when nece ssary so t hat we can prevent t he user fr om enterin g incorrec t data int o our appl ication.
	621	RXR-335
	622	EWNFR-377
	623	Guidance: the import ant inform ation need ed to comp lete safet y critical actions i s displaye d to the u ser in a m anner that helps the user noti ce it. For instance, by its po sition on a screen o r font cha racteristi cs (e.g. c olor, bold or underl ine etc.)
	624	RXR-336
	625	EWNFR-378
	626	Guidance: the contex t for safe ty critica l values m ust be com municated to reduce the likeli hood it is missed or misinterp reted.
	627	RXR-337
	628	EWNFR-379
	629	Guidance: the user i nterface a rticulates requireme nts that c apture wha t informat ion users need to be able to e nter so th at informa tion is sh ared, reco rded, and utilized b y the syst em.
	630	RXR-338
	631	EWNFR-382
	632	Guidance: the user i nterface a rticulates requireme nts that c apture wha t informat ion users need to be able to r etrieve so that info rmation is shared, r ecorded, a nd utilize d by the s ystem.
	633	RXR-339
	634	EWNFR-383
	635	Guidance: a confirma tion reque st is pres ented to t he user wh en a safet y critical action th at can't b e undone i s taken.
	636	RXR-340
	637	EWNFR-385
	638	Guidance: programmin g calls th at fail wh en trying to support a user ac tion cause a message to be sen t to the u ser and th e text pre sented des cribes the error.
	639	RXR-341
	640	EWNFR-386
	641	As a proje ct team, w e must (wh en possibl e) ensure that user actions ar e undoable so that o ur applica tion will allow our users to c orrect err ors and ea sily retur n to their tasks.
	642	RXR-343
	643	EWNFR-388
	644	As a proje ct team, w e must inc lude “why it happene d” informa tion in er ror feedba ck so that our appli cation wil l allow ou r users to correct e rrors and easily ret urn to the ir tasks.
	645	RXR-345
	646	EWNFR-390
	647	As a proje ct team, w e must pro vide a way for our u sers to im mediately obtain hel p from som eone with specific m edical or psychiatri c knowledg e so that our users can mitiga te the eff ects of gu idance tha t is not s ufficient for the us er’s curre nt needs.
	648	RXR-347
	649	EWNFR-391
	650	Guidance: there is a way for t he user to get help with safet y critical tasks.
	651	RXR-348
	652	EWNFR-394
	653	As a proje ct team, w e must pro vide a mec hanism to report sof tware issu es so that we can mo nitor syst em usage a fter deplo yment.
	654	RXR-350
	655	EWNFR-395
	656	Guidance: software p rogramming calls for data, res ources, an d services , are tran sactional, traceable and with clear indi cations of success a nd failure .
	657	RXR-351
	658	EWNFR-396
	659	Guidance: there is a mechanism in place that captu res use er rors, allo ws the use r to volun tarily rep ort advers e events a nd (if app licable) a llows for network me ssaging to be monito red.
	660	RXR-352
	661	EWNFR-397
	662	Guidance: all screen s/pages ar e uniquely identifie d within t he applica tion.
	663	RXR-353
	664	EWNFR-399
	665	Guidance: Patient Sa fety Repre sentatives are given the infor mation the y need (e. g. documen tation on the purpos e and desi gn of the applicatio n, the res ults from an indepen dent clini cal review , and the results fr om the Hum an Factors Engineeri ng office' s evaluati ons) to co nduct thei r reviews and respon ses to any of their requests f or change are docume nted.
	666	RXR-354
	667	EWNFR-347
	668	Guidance: documentat ion of a c onceptual model and use cases for patien t safety c ritical ta sks have b een create d and sent to Inform atics Pati ent Safety for revie w.
	669	RXR-355
	670	EWNFR-348
	671	Guidance: a list of patient sa fety criti cal data a nd tasks h as been do cumented a nd sent to Informati cs Patient Safety fo r review.
	672	RXR-356
	673	EWNFR-349
	674	Guidance: documentat ion of an independen t clinical expert re view is pr ovided to Informatic s Patient Safety.
	675	RXR-357
	676	EWNFR-350
	677	Guidance: the team e ngages Pat ient Safet y speciali st during our develo pment phas e.
	678	RXR-358
	679	EWNFR-351
	680	Guidance: pilot test ing is con ducted and documente d in the p ost deploy ment envir onment.
	681	RXR-359
	682	EWNFR-352
	683	Guidance: there is a mechanism in place that will allow the team to co llect post -deploy pa tient safe ty issues.
	684	RXR-360
	685	EWNFR-653
	686	Guidance: the user i nterface i mplements requiremen ts that ar ticulate u ser decisi on making needs base d on ident ifying rel evant user s, informa tion, task s, and tim ing - and relationsh ips betwee n them.
	687	RXR-361
	688	EWNFR-656
	689	Guidance: there is a mechanism in place that will help the u ser unders tand abnor mal system results b y explaini ng why it is abnorma l.
	690	RXR-363
	691	EWNFR-444
	692	As a proje ct team, w e must ens ure that w e are not using colo r and text formattin g as the o nly means of communi cating inf ormation o n the Andr oid/iOS pl atforms ot herwise we will not be Section 508 compl iant.
	693	RXR-365
	694	EWNFR-445
	695	As a proje ct team, w e must ens ure that w e are not using colo r and text formattin g as the o nly way to communica te selecti on on the Android/iO S platform s, otherwi se we will not be 50 8 complian t.
	696	RXR-367
	697	EWNFR-446
	698	As a proje ct team, w e must ens ure that a nything th at uses co lor to con vey a mean ing, can a lso do so without us ing color in the con tent, on t he Android /iOS platf orms, othe rwise we w ill not be Section 5 08 complia nt
	699	RXR-369
	700	EWNFR-447
	701	As a proje ct team, w e must ens ure that a nything th at uses co lor to con vey a mean ing, can a lso do so without us ing color on-screen on the And roid/iOS p latforms, otherwise we will no t be Secti on 508 com pliant.
	702	RXR-371
	703	EWNFR-448
	704	As a proje ct team, w e must ens ure that a nything th at uses co lor to con vey a mean ing withou t needing additional interacti on from th e user on the Androi d/iOS plat forms, oth erwise we will not b e Section 508 compli ant.
	705	RXR-373
	706	EWNFR-449
	707	As a proje ct team, w e must ens ure that w e provide a sufficie nt color c ontrast wh en using t ext and te xt images on the And roid/iOS P latform, o therwise w e will not be Sectio n 508 comp liant.
	708	RXR-375
	709	EWNFR-450
	710	As a proje ct team, w e must ens ure that w hen colors from the OS are not used, tha t we provi de a varie ty of colo r contrast selection , otherwis e we will not be Sec tion 508 c ompliant.
	711	RXR-377
	712	EWNFR-451
	713	As a proje ct team, w e must ens ure that w hen White on Black i s enabled on the iOS platform, that an a cceptable contrast i s provided within th e applicat ion color settings, otherwise we will no t be Secti on 508 Com pliant.
	714	RXR-379
	715	EWNFR-452
	716	As a proje ct team, w e must ens ure that t he additio n of on-sc reen compo nents are properly e xposed to assistive technology on the An droid/iOS platforms, otherwise , we will not be 508 compliant .
	717	RXR-381
	718	EWNFR-453
	719	As a proje ct team, w e must ens ure that t he removal of on-scr een compon ents are p roperly ex posed to a ssistive t echnology on the And roid/iOS M edia Platf orms.
	720	RXR-383
	721	EWNFR-455
	722	As a proje ct team, w e must ens ure that w e make ass istive tec hnologies aware of a ny content changes t o the Andr oid/iOS ap plications in real t ime, other wise we wi ll not be Section 50 8 complian t.
	723	RXR-385
	724	EWNFR-461
	725	As a proje ct team, w e must ens ure that s creen tran sitions se ttle withi n 5 second s on the A ndroid/iOS platform applicatio ns, otherw ise we wil l not be S ection 508 compliant .
	726	RXR-387
	727	EWNFR-462
	728	As a proje ct team, w e must ens ure that d ecorative animations settle wi thin 5 sec onds on th e Android/ iOS platfo rm applica tions, oth erwise we will not b e Section 508 compli ant.
	729	RXR-389
	730	EWNFR-464
	731	As a proje ct team, w e must ens ure that e rror messa ge have a platform s pecific al ert or the focus is moved to t he error m essage aft er submitt ing of an action, ot herwise we will not be Section 508 compl iant.
	732	RXR-392
	733	EWNFR-465
	734	As a proje ct team, w e must ens ure that w e provide a clear in dication o f errors o n the Andr oid/iOS ap plication platforms, otherwise we will n ot be Sect ion 508 co mpliant.
	735	RXR-394
	736	EWNFR-466
	737	As a proje ct team, w e must ens ure that w e provide a consiste nt strateg y to imple ment an er ror mechan ism on the Android/i OS platfor ms, otherw ise we wil l not be S ection 508 compliant .
	738	RXR-396
	739	EWNFR-467
	740	As a proje ct team, w e must ens ure that w e provide a consiste nt way to implement and alert mechanism on the And roid/iOS p latforms, otherwise we will no t be Secti on 508 com pliant.
	741	RXR-400
	742	EWNFR-469
	743	As a proje ct team, w e must ens ure that w e provide error prev ention for legal com mitments o n the Andr oid/iOS pl atforms, o therwise w e will not be Sectio n 508 comp liant.
	744	RXR-402
	745	EWNFR-471
	746	As a proje ct team, w e must pro vide sugge stions to the user w hen they r eceive err or message s whenever they are known when using the Android/i OS platfor ms, otherw ise we wil l not be S ection 508 compliant .
	747	RXR-404
	748	EWNFR-472
	749	As a proje ct team, w e must ens ure that w hen focus changes oc cur that t he context has not c hanged, ot herwise we will not be Section 508 compl iant.
	750	RXR-406
	751	EWNFR-473
	752	As a proje ct team, w e must ens ure that t he focus i s set logi cally when a module opens, oth erwise we will not b e Section 508 compli ant.
	753	RXR-409
	754	EWNFR-474
	755	As a proje ct team, w e must ens ure that t he focus i s set logi cally when pop alert s close, o therwise w e will not be Sectio n 508 comp liant.
	756	RXR-412
	757	EWNFR-475
	758	As a proje ct team, w e must ens ure that t he focus i s not forc ibly shift ed when in putting in formation, otherwise we will n ot be Sect ion 508 co mpliant.
	759	RXR-414
	760	EWNFR-476
	761	As a proje ct team, w e must ens ure that n avigation is visuall y indicate d, otherwi se we will not be Se ction 508 compliant.
	762	RXR-416
	763	EWNFR-477
	764	As a proje ct team, w e must mak e sure tha t when usi ng keyboar d focus, w e clearly indicate i nteraction , otherwis e we will not be Sec tion 508 c ompliant.
	765	RXR-418
	766	EWNFR-478
	767	As a proje ct team we must ensu re that we use inter active ele ments on a page in a logical f ocus order , otherwis e, we will not be Se ction 508 compliant.
	768	RXR-420
	769	EWNFR-479
	770	As a proje ct team, w e must ens ure that a ll element s can rece ive focus, otherwise we will n ot be Sect ion 508 co mpliant.
	771	RXR-422
	772	EWNFR-481
	773	As a proje ct team, w e must ens ure that w e are suff iciently d escribing all elemen ts, otherw ise we wil l not be S ection 508 compliant .
	774	RXR-424
	775	EWNFR-487
	776	As a proje ct team, w e must ens ure that i t is possi ble for al l enhancem ents to op erate simu ltaneously , even if they are n ot all bei ng used, o therwise w e will not be Sectio n 508 comp liant.
	777	RXR-426
	778	EWNFR-488
	779	As a proje ct team, w e must ens ure that t ime based sessions a re accessi ble, other wise we wi ll not be Section 50 8 complian t.
	780	RXR-428
	781	EWNFR-489
	782	As a proje ct team, w e must mak e sure tha t all cont rols suppo rt Accessi bility, ot herwise we will not be Section 508 compl iant.
	783	RXR-430
	784	EWNFR-490
	785	As a proje ct team, w e must mak e sure tha t non-deco rative con tent suppo rts access ibility, o therwise w e will not be Sectio n 508 comp liant.
	786	RXR-432
	787	EWNFR-491
	788	As a proje ct team we must ensu re that co ntrols are correctly identifie d as they are intend ed to be, and the “s tate” is c orrectly i dentified, otherwise we will n ot be Sect ion 508 co mpliant.
	789	RXR-434
	790	EWNFR-492
	791	As a proje ct team, w e must be sure that all applic ations do not interf ere with A ssistive T echnology, otherwise we will n ot be Sect ion 508 co mpliant.
	792	RXR-436
	793	EWNFR-493
	794	As a proje ct team, w e must mak e sure tha t hidden c ontent is not expose d to assis tive techn ologies, o therwise w e will not be Sectio n 508 comp liant.
	795	RXR-438
	796	EWNFR-494
	797	As a proje ct team, w e must mak e sure tha t decorati ve content is not ex posed to a ssistive t echnologie s, otherwi se we will not be Se ction 508 compliant.
	798	RXR-440
	799	EWNFR-495
	800	As a proje ct team, w e must mak e sure tha t duplicat e content is not exp osed to as sistive te chnologies , otherwis e we will not be Sec tion 508 c ompliant.
	801	RXR-442
	802	EWNFR-496
	803	As a proje ct team, w e must mak e sure tha t artifact elements are not ex posed to a ssistive t echnologie s, otherwi se we will not be Se ction 508 compliant.
	804	RXR-444
	805	EWNFR-497
	806	As a proje ct team, w e cannot o nly rely o n sensory characteri stics when providing instructi ons, other wise we wi ll not be Section 50 8 complian t.
	807	RXR-446
	808	EWNFR-498
	809	As a proje ct team, w e must ens ure that s hape and l ocation ar e not the only ways informatio n is commu nicated, o therwise w e will not be Sectio n 508 comp liant.
	810	RXR-448
	811	EWNFR-499
	812	As a proje ct team, w e must ens ure that s hape and l ocation ar e not the only ways hierarchy is communi cated, oth erwise we will not b e Section 508 compli ant.
	813	RXR-500
	814	EWNFR-500
	815	As a proje ct team, w e must use consisten t labels f or control s, otherwi se we will not be Se ction 508 compliant.
	816	RXR-452
	817	EWNFR-501
	818	As a proje ct team, w e must use consisten t labels f or images, otherwise we will n ot be Sect ion 508 co mpliant.
	819	RXR-454
	820	EWNFR-502
	821	As a proje ct team, w e must use consisten t labels f or common elements, otherwise we will no t be Secti on 508 com pliant.
	822	RXR-456
	823	EWNFR-503
	824	As a proje ct team, w e must be sure to pr ovide the ability fo r the user to contro l the font size, oth erwise we will not b e Section 508 compli ant.
	825	RXR-458
	826	EWNFR-504
	827	As a proje ct team, w e must be sure that content th at gives t he user an alternati ve to non- accessible content, also provi de an equi valent fun ctionality , otherwis e we will not be Sec tion 508 c ompliant.
	828	RXR-460
	829	EWNFR-505
	830	As a proje ct team, w e must ens ure access to altern ative inpu t methods, otherwise we will n ot be Sect ion 508 co mpliant
	831	RXR-462
	832	EWNFR-506
	833	As a proje ct team, w e must be sure that element te xt has the same mean ing when o ut of cont ext, other wise we wi ll not be Section 50 8 complian t.
	834	RXR-464
	835	EWNFR-507
	836	As a proje ct team, w e must be sure that element te xt has the same mean ing within context, otherwise we will no t be Secti on 508 com pliant.
	837	RXR-466
	838	EWNFR-508
	839	As a proje ct team, w e must be sure that we are abl e to move focus away from focu sable comp onents, ot herwise we will not be Section 508 compl iant.
	840	RXR-468
	841	EWNFR-509
	842	As a proje ct team, w e must be sure that we do not overlap ac tive eleme nts in tou ch focus a reas, othe rwise we w ill not be Section 5 08 complia nt.
	843	RXR-470
	844	EWNFR-510
	845	As a proje ct team, w e must ens ure that a ll actions on a touc h screen a re trigger ed on remo val and no t with the initial t ouch, othe rwise we w ill not be Section 5 08 complia nt.
	846	RXR-473
	847	EWNFR-511
	848	As a proje ct team, w e must pro vide inact ive space around ele ments on t he touch s creen, oth erwise we will not b e Section 508 compli ant.
	849	RXR-475
	850	EWNFR-512
	851	As a proje ct team, w e must be sure to pr ovide suff icient siz e for the element on the touch screen, o therwise w e will not be Sectio n 508 comp liant.
	852	RXR-477
	853	EWNFR-513
	854	As a proje ct team, w e must mak e sure tha t while us ing logica l navigati on scrolli ng occurs as needed, otherwise we will n ot be Sect ion 508 co mpliant.
	855	RXR-479
	856	EWNFR-514
	857	As a proje ct team, w e must mak e sure tha t all of t he control s that hav e accessib le input m ethods for the contr ols, have a specific set of be haviors an d are adeq uately sup ported, ot herwise we will not be Section 508 compl iant.
	858	RXR-481
	859	EWNFR-515
	860	As a proje ct team, w e must ens ure that a ll interac tions with a control is what t he user ex pects it t o be, othe rwise we w ill not be Section 5 08 complia nt.
	861	RXR-483
	862	EWNFR-516
	863	As a proje ct team, w e must avo id duplica ting infor mation in alternativ es, otherw ise we wil l not be S ection 508 compliant .
	864	RXR-485
	865	EWNFR-517
	866	As a proje ct team, w e must ens ure that w hen using non-decora tive image s, informa tive alter native tex t is provi ded to the user, oth erwise we will not b e 508 comp liant.
	867	RXR-487
	868	EWNFR-518
	869	As a proje ct team, w e must use actual te xt when te chnology a llows inst ead of ima ges of the text, oth erwise we will not b e Section 508 compli ant.
	870	RXR-489
	871	EWNFR-519
	872	As a proje ct team, w e must pro vide the e quivalent text for a ll non-tex t elements including sound and images, o therwise w e will not be Sectio n 508 comp liant.
	873	RXR-491
	874	EWNFR-520
	875	As a proje ct team, w e must be sure that the readin g order of the appli cation con tent is lo gical, oth erwise we will not b e Section 508 compli ant.
	876	RXR-493
	877	EWNFR-521
	878	As a proje ct team, w e must be sure that where a sc reen title is provid ed, a clea r title is presented on all sc reens, oth erwise we will not b e Section 508 compli ant.
	879	RXR-501
	880	EWNFR-700
	881	Guidance: developmen t team mus t scan the ir applica tions duri ng both th e developm ent and th e A&A proc esses (for example: during com ponent tes ting).
	882	RXR-496
	883	EWNFR-701
	884	Guidance: developmen t teams mu st obtain automatic static ana lysis tool s from the VA SwA Pr ogram Offi ce.
	885	RXR-497
	886	EWNFR-702
	887	Guidance: if Applica ble, devel opment tea m must per form the V &V Secure Code Revie w Process.
	888	RXR-498
	889	EWNFR-703
	890	Guidance: (if applic able) deve lopment te ams must p erform the IV&V High Risk and High Prior ity applic ation Revi ew process .
	891	RXR-499
	892	EWNFR-704
	893	Guidance: developmen t teams sh ould revie w the OWAS P Top Ten list.
	894	RXR-500
	895	EWNFR-705
	896	Guidance: developmen t teams sh ould revie w the CWE/ SANS Top 2 5 Most Dan gerous Sof tware Erro rs.
	897	RXR-107
	898	EWNFR-660
	899	Guidance: the Mobile Applicati on is free of all Le vel-1 (Cri tical) and Level 2 ( High) defe cts prior to submitt ing to V&V .
	900	RXR-109
	901	EWNFR-663
	902	As a proje ct team, w e must be sure to pr ovide a bu siness own er waiver if our Mob ile Applic ation is n ot free of all criti cal and hi gh defects , otherwis e we will not meet t he criteri a for entr ance into V&V.
	903	RXR-110
	904	EWNFR-665
	905	Guidance: test scrip ts and tes t results are docume nted accor ding to Pr oPath guid ance.
	906	RXR-111
	907	EWNFR-669
	908	Guidance: to meet th e requirem ents for V &V test in take, the functional requireme nts, busin ess rule l ogic and c ompliance requiremen ts have be en tested.
	909	RXR-113
	910	EWNFR-694
	911	As a proje ct team, w e must ens ure that f ollowing 1 5 minutes of inactiv ity by the current u ser our ap plication time-outs so that ou r applicat ion effici ently used the limit ed resourc es that ma ybe availa ble to the user.
	912	RXR-118
	913	EWNFR-695
	914	As a proje ct team, w e must inc lude an Ab out tab or button wi thin our a pplication so that t he user ca n quickly locate imp ortant inf ormation a bout our a pplication . Contents should in clude; Ap plication Name, Vers ion Number , Develope d By U.S. Department of Vetera ns Affairs , National Release D ate, App D escription .
	915	RXR-126
	916	EWNFR-707
	917	As a proje ct team, w e must inc lude the v ersion num ber of the applicati on on the About tab so that th e use will know whic h version of the app lication t hey are us ing.
	918	RXR-130
	919	EWNFR-708
	920	As a proje ct team, w e must inc lude a Hel p tab or b utton with in our app lication s o that the user can quickly lo cate impor tant infor mation to assist the m in using our appli cation. Th e Help tab /button sh ould conta in: Brows ers, User Manual, Vi deos and F requently Asked Ques tions, Tol l Free Hel p Desk, an d General Feedback t o VA.
	921	RXR-134
	922	EWNFR-710
	923	As a proje ct team, w e must ens ure that o ur applica tion gives the user the abilit y to choos e (from wi thin the a pplication ) to retur n to the L aunchpad o nce the ap plication is exited so that a common exi t procedur e is used for all mo bile appli cations.
	924	RXR-509
	925	EWNFR-155
	926	As a proje ct team, w e must use terminolo gy consist ently thro ughout the applicati on so that we do not use two d ifferent t erms that have the s ame meanin g and we c an avoid c onfusion.
	927	RXR-511
	928	EWNFR-160
	929	As a proje ct team, w e must use a consist ent screen layout th roughout t he applica tion so th at consist ency exist s and user s are able to easily find info rmation.
	930	RXR-513
	931	EWNFR-167
	932	As a proje ct team, w e must cre ate a spla sh screen that conve ys that ou r applicat ion is VA sanctioned so that t he user kn ows that t his is an authorized VA applic ation.
	933	RXR-516
	934	EWNFR-171
	935	As a proje ct team,we must comp ose the ap plication messages i n simple, plain lang uage so th at it is e asily unde rstood by the target user. Thi s NFR is a pplicable to both Pa tient Safe ty and Use r Interfac e. Message s include the follow ing:
	936	• Error
	937	• Warning
	938	• Informat ional
	939	• Alerts
	940	RXR-518
	941	EWNFR-172
	942	As a proje ct team, w e must des cribe erro rs using p lain, simp le languag e so that it is easi ly underst ood by the target us er.
	943	RXR-520
	944	EWNFR-173
	945	As a proje ct team, w e must com pose error recovery instructio ns using p lain, simp le languag e so that it is easi ly underst ood by the target us er.
	946	RXR-522
	947	EWNFR-174
	948	As a proje ct team, w e must inc lude error recovery instructio ns in all of the err or message s of the a pplication so that i t is easil y understo od by the target use r.
	949	RXR-524
	950	EWNFR-182
	951	As a proje ct team, w e must use a text he ight that can easily read by t he user so that the text is ea sily read and does n ot require manipulat ion techni ques by th e user to make the t ext readab le.
	952	RXR-507
	953	EWNFR-389
	954	As a proje ct team, w e must inc lude “how to correct error” in formation in error f eedback so that our applicatio n will all ow our use rs to corr ect errors and easil y return t o their ta sks. This NFR is app licable to Patient S afety and Usability.
	955	RXR-505
	956	EWNFR-387
	957	As a proje ct team, w e must inc lude “what happened” informati on in erro r feedback so that o ur applica tion will allow our users to c orrect err ors and ea sily retur n to their tasks. Th is NFR is applicable to Patien t Safety a nd Usabili ty.
	958	RXR-503
	959	EWNFR-384
	960	As a proje ct team, w e must use the langu age of the user when we create the user interface for our ap plication and as muc h as possi ble we mus t ensure t he applica tion acts and reacts as the us er expects so that w e can redu ce the occ urrences o f user err or.
	961
	962
	963
	964
	965