930. EPMO Open Source Coordination Office Redaction File Detail Report

Produced by Araxis Merge on 2/17/2017 4:31:02 PM Central 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.

930.1 Files compared

#	Location	File	Last Modified
1	VSA P2.5 v3.0.12.zip	VSA Phase2 RSD v5.7.docx	Fri Feb 10 16:05:38 2017 UTC
2	VSA P2.5 v3.0.12.zip	VSA Phase2 RSD v5.7.docx	Thu Feb 16 17:43:59 2017 UTC

930.2 Comparison summary

Description	Between Files 1 and 2
Description	Text Blocks	Lines
Unchanged	2	4480
Changed	1	2
Inserted	0	0
Removed	0	0

930.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

930.4 Active regular expressions

No regular expressions were active.

930.5 Comparison detail

	1	VistA Serv ices Assem bler Phase 2 (VSA-P2 )
	2	Requiremen ts Specifi cation Doc ument
	3
	4	Department of Vetera ns Affairs
	5	Office of Informatio n and Tech nology (OI &T)
	6	Product De velopment (PD)
	7	Documentat ion Versio n 5.7
	8	March 2016
	9
	10
	11	Revision H istory
	12	Note: The revision h istory cyc le begins once chang es or enha ncements a re request ed after t he Require ments Spec ification Document h as been ba selined.
	13	Date
	14	Version
	15	Descriptio n
	16	Author
	17	3/08/2016
	18	5.7
	19	Address VA VSA feedb ack
	20	Apex – M. Waterloo
	21	2/17/2016
	22	5.7
	23	Extensive fixes to m inimize ex changes be tween APEX and VA. T rack Chang es were Ac cepted.
	24	APEX chang ed staff f rom Carol Jones to S . Greenacr e and info rmation wa s not comm unicated t o new staf f.
	25	VA and Eng ility
	26	01/21/2016
	27	5.7
	28	Technical Edit. Recr eated the list of ta bles and f igures TOC . Section A6, added content to a table.
	29	Updated Ta ble 3 with the missi ng Require ment numbe rs and Exp ected Deli very Dates .
	30	Added S-Cu re charts to section 4.
	31	C. Perkins ,
	32	S. Greenac re
	33	01/19/2016
	34	5.6
	35	Update to address VA comments.
	36	Updated to current P roPath Tem plate.
	37	S. Greenac re
	38	11/30/2015
	39	5.5
	40	Tech Edits
	41	Accepted a ll Track C hanges and removed c omments.
	42	Re-formatt ed entire document f or 508 com pliance.
	43	Added alt txt to all tables an d figures for 508 co mpliance.
	44	Updated al l hyperlin ks per the 508 compl iance guid elines.
	45	C. Perkins
	46	11/23/2015
	47	5.4
	48	Tech Edits
	49	Updated th e Delivery Column
	50	Added cont ract verbi age to Int roduction, Purpose a nd Scope
	51	C. Jones
	52	J. Yaple
	53	11/19/2015
	54	5.3
	55	Tech Edits
	56	Replaced V SA VistA.j s with VSA
	57	Replaced S OA with SO AP
	58	C. Jones
	59	11/06/2015
	60	5.2
	61	Tech Edits
	62	Replaced V SA VistA w ith VSA Vi stA.js
	63	Replaced S OAP with S OA
	64	Updated fo oter
	65	Added just ification to deleted requireme nts
	66	Deleted a number of requiremen ts with ju stificatio n that tex t related to a speci fic techni cal implem entation t hat is no longer cur rent.
	67	Updated se veral requ irements t o reflect scope.
	68	Replaced “ VSA Wizard ” with Vis tA.js Wiza rd functio nality.
	69	Noted that Figures 2 , 3 and 4 are no lon ger curren t.
	70	Corrected previous s ubstitutio n of SOAP with SOA. This updat e will be validated with Gover nment.
	71	Updated de livery col umn values and 2.6.1 5 requirem ents appor tionment.
	72	C. Jones
	73	J. Yaple
	74	07/28/2015
	75	5.1
	76	Tech Edits
	77	Added note below Fig ure 8.
	78	Corrected footer for matting in Section 8 .
	79	Renamed do cument to follow lat est VSA na ming conve ntions.
	80	E. Laurel
	81	T. Blom
	82	07/24/2015
	83	5.0
	84	Tech Edits
	85	Baselined document b ased on la test updat es and fee dback from the VSA d evelopment team.
	86	Modified s tyles and formatting throughou t.
	87	Added “Dra ft” waterm ark on all pages. Th is should be removed prior to final docu ment appro val and si gnoff.
	88	Updated do cument for latest do cumentatio n standard s.
	89	Reviewed, added, and updated h yperlinks throughout .
	90	Reviewed W ord docume nt for Sec tion 508 c onformance .
	91	Reviewed a nd edited content fo r grammar, punctuati on, and sp elling.
	92	T. Blom
	93	E. Laurel
	94	07/16/2015
	95	4.0
	96	Removed la nguage on the use of technolog y specific to Java, JavaScript , etc., an d other ed its provid ed.
	97	J. Garcia
	98	V. Rodrigu ez
	99	E. Laurel
	100	10/20/2014
	101	3.0
	102	Tech Edits
	103	Final base line docum ent for si gnatures i n PDF.
	104	Extensive rewrite an d reformat of entire document as per K. Cox review .
	105	VSA Develo pment Team
	106	10/03/2014
	107	2.0
	108	Tech Edits
	109	Baselined document t o Version 2.0.
	110	Reviewed u pdated sec tions in d ocument, s ince last baseline.
	111	Reviewed d ocument fo r formatti ng and sty le updates .
	112	Updated al l document reference s, table o f contents , table of figures, etc.
	113	Added Offi ce of Gene ral Counse l software disclaime r statemen t to Secti on 5.
	114	Made minor grammar, punctuatio n, and spe lling upda tes as nee ded.
	115	Checked do cument for Section 5 08 conform ance.
	116	Removed “D raft” and watermark from the d ocument fo r final PD F and digi tal signat ures.
	117	T. Blom
	118	E. Laurel
	119	10/01/2014
	120	1.7
	121	Added spec for “Fede rated” cal ls item 2. 6.4d.
	122	Added requ irement fo r Federate d calls, s ee PS2.9.8 .
	123	E. Laurel
	124	J. Garcia
	125	09/22/2014
	126	1.6
	127	Updated Bu siness Nee ds table i n Section 2.6.15 wit h the most up to dat e “status” .
	128	Added secu rity requi rements fo r PII and PHI as SS2 .13.7 in S ection 2.1 3.
	129	E. Laurel
	130	J. Garcia
	131	V. Rodrigu ez
	132	L. Janko
	133	09/18/2014
	134	1.5
	135	Added numb ering (e.g ., 2.2a, e tc.) to no n-function al specs n ot contain ing tables ; this wil l better l ink requir ements to RRC identi fiers.
	136	E. Laurel
	137	09/10/2014
	138	1.4
	139	Added cont ent to Sec tion 2.13, “Security Specifica tions.”
	140	J. Garcia
	141	E. Laurel
	142	08/26/2014
	143	1.3
	144	Revised sc ope in Sec tion 1.2.
	145	Added RRC requiremen t identifi er numbers in Sectio n 2.6; cor responds w ith new en tries of r equirement s in RRC f or VSA-P2.
	146	Added Goal s/Objectiv es table f rom BRD in Section 1 .2.1.
	147	Removed al l comments .
	148	E. Laurel
	149	08/14/2014
	150	1.2
	151	Tech Edits
	152	Updated Fi gure 2, Fi gure 3, an d Figure 4 ; based on new foote r added to VSA Wizar d screens.
	153	Updated Fi gure 7 and Figure 8.
	154	Changed We bLogic Rel ease “12.1 .2” to “12 .x” in Tab le 17.
	155	Added Regi stered tra demark ® t o referenc es in Tabl e 17 and T able 18.
	156	T. Blom
	157	M. Ogi
	158	08/07/2014
	159	1.1
	160	Tech Edits
	161	Updated ca ption for Figure 7.
	162	Updated Fi gure 7 and added Fig ure 8 base d on feedb ack from J . Garcia.
	163	Updated ac ronyms in Table 18.
	164	Removed th e moved co ntent from “Status” column, to “OWNR” co lumn and t hen delete d the “Sta tus” colum n. Also, c hanged ref erences fr om “POC” t o “Phase 2 ” througho ut the tab le.
	165	T. Blom
	166	J. Garcia
	167	08/04/2014
	168	1.0
	169	Tech Edits
	170	Reviewed d ocument fo r formatti ng and sty le updates .
	171	Updated al l document reference s, table o f contents , table of figures, etc.
	172	Made minor grammar, punctuatio n, and spe lling upda tes as nee ded.
	173	Checked do cument for Section 5 08 conform ance.
	174	Baselined document t o Version 1.0.
	175	T. Blom
	176	E. Laurel
	177	07/31/2014
	178	0.5
	179	Revised mu ltiple sec tions; Mul tiDivision al, Perfor mance, Sco pe Integra tion, Reli ability, U sability, GUI, Commu nications, User Inte rface sect ions
	180	J. Garcia
	181	E. Laurel
	182	07/17/2014
	183	0.4
	184	Revised mu ltiple sec tions; add ed comment s
	185	Accepted i nserts and deleted c omments
	186	G. Smullen
	187	J. Garcia
	188	M. Ogi
	189	E. Laurel
	190	06/23/2014
	191	0.3
	192	Revised Fe deration o f Web Serv ices; adde d content for Pre an d Post Act ion action s
	193	E. Laurel
	194	05/28/2014
	195	0.2
	196	Revised to modify sc ope and ad ded functi onality fo r Represen tational S tate Trans fer (RESTf ul) servic es
	197	E. Laurel
	198	04/08/2014
	199	0.1
	200	Initial VS A 1.0.0 Ph ase 2 docu ment: Base d on origi nal Protot ype; Proof -of-Concep t document .
	201	Revised co ntent to r eflect req uirements for Increm ent 1 (RES Tful Servi ces).
	202	E. Laurel
	203
	204	Table of C ontents
	205	1.Introduc tion1
	206	1.1.Purpos e2
	207	1.2.Scope3
	208	1.3.Refere nces6
	209	2.Overall Descriptio n7
	210	2.1.Access ibility Sp ecificatio ns7
	211	2.2.Busine ss Rules S pecificati on7
	212	2.3.Design Constrain ts Specifi cation7
	213	2.4.Disast er Recover y Specific ation8
	214	2.5.Docume ntation Sp ecificatio ns8
	215	2.6.Functi onal Speci fications8
	216	2.6.1.VSA Wizard Fun ctionality —User Inte rface8
	217	2.6.2.VSA Wizard Fun ctionality —Functions 23
	218	2.6.3.VSA Runtime En vironment Components 25
	219	2.6.4.Fede ration27
	220	2.6.5.Pre/ Post Logic Processin g29
	221	2.6.6.Exce ption and Error Hand ling31
	222	2.6.7.Arch itectural Principles 32
	223	2.6.8.Supp orting geo graphicall y distribu ted VA Sys tem Topolo gy33
	224	2.6.9.Non- Functional Requireme nts36
	225	2.6.10.Cap acity, Loa d, and Per formance38
	226	2.6.11.Sec urity39
	227	2.6.12.Use r Identity Propagati on40
	228	2.6.13.Ava ilability - COOP/Dis aster Reco very42
	229	2.6.14.Doc umentation 43
	230	2.6.15.App ortioning of Require ments44
	231	2.7.Graphi cal User I nterface ( GUI) Speci fications4 4
	232	2.8.Multi- divisional Specifica tions48
	233	2.9.Perfor mance Spec ifications 48
	234	2.10.Quali ty Attribu tes Specif ication49
	235	2.11.Relia bility Spe cification s49
	236	2.12.Scope Integrati on49
	237	2.13.Secur ity Specif ications49
	238	2.14.Syste m Features 49
	239	2.15.Usabi lity Speci fications4 9
	240	3.Purchase d Componen ts49
	241	4.Estimati on49
	242	5.Approval Signature s53
	243	Appendix A : Non-Func tional Req uirements5 4
	244	System Per formance R eporting R equirement s54
	245	Operationa l Environm ent Requir ements54
	246	Documentat ion Requir ements55
	247	Implementa tion Requi rements55
	248	Data Prote ction/Back -up/Archiv e Requirem ents56
	249	Levels for Disaster Recovery56
	250	Data Quali ty/Assuran ce Require ments56
	251	User Acces s/Security Requireme nts56
	252	Usability/ User Inter face Requi rements57
	253	Conceptual Integrity 57
	254	Availabili ty57
	255	Interopera bility57
	256	Manageabil ity58
	257	Performanc e58
	258	Reliabilit y58
	259	Security59
	260	Supportabi lity59
	261	Usability6 0
	262	Documentat ion60
	263	Appendix B : Acronym List and G lossary60
	264	Acronyms60
	265	Definition s63
	266
	267	List of Ta bles
	268	Table 1: V SA Primary and Failo ver Sites4
	269	Table 2: V SA Project Scope: Go als and Ob jectives5
	270	Table 3: V SA Wizard Functional ity-User I nterface R equirement s8
	271	Table 4: V SA Wizard Functional ity-Functi ons24
	272	Table 5: V SA Runtime Environme nt25
	273	Table 6: V SA Federat ion Requir ements27
	274	Table 7: V SA Pre/Pos t Logic Pr ocessing R equirement s30
	275	Table 8: V SA Excepti on and Err or Handlin g Requirem ents31
	276	Table 9: V SA Archite ctural Pri nciples Re quirements 32
	277	Table 10: VSA System Topology Requiremen ts33
	278	Table 11: VSA Non-Fu nctional R equirement s36
	279	Table 12: VSA Capaci ty-Load an d Performa nce Requir ements38
	280	Table 13: VSA Securi ty Require ments39
	281	Table 14: VSA User I dentity Pr opagation Requiremen ts40
	282	Table 15: VSA Availa bility-Con tinuity of Operation s (COOP)/D isaster Re covery (DR ) Requirem ents42
	283	Table 16: VSA Docume ntation Re quirements 43
	284	Table 17: Levels for Disaster Recovery56
	285	Table 18: Acronyms60
	286	Table 19: Definition s63
	287
	288	List of Fi gures
	289	Figure 1: VSA “Pre/P ost” Logic Model30
	290	Figure 2: VSA RPC Wi zard-Selec t RPC45
	291	Figure 3: VSA RPC Wi zard-Edit Definition 46
	292	Figure 4: VSA API Br owser-Show RESTified RPCs46
	293	Figure 5: VSA API Br owser-Sele ct A RESTi fied RPC47
	294	Figure 6: VSA API Br owser-Test ing The Re st Call47
	295	Figure 7: VSA API Br owser-REST Call Resu lts48
	296	Figure 8: Cumulative Probabili ty (“S-cur ve”) Chart —Project D uration51
	297	Figure 9. Cumulative Probabili ty (“S-cur ve”) Chart —Project E ffort52
	298
	299
	300	Introducti on
	301	This Requi rements Sp ecificatio ns Documen t (RSD) is developed for the V istA Servi ces Assemb ler Phase 2 (VSA-P2) project s upported b y the Offi ce of Info rmation an d Technolo gy (OI&T)/ Product De velopment (PD) divis ion. The m ajority of Departmen t of Veter ans Affair s (VA) hea lthcare co mputing in volves Vet erans Heal th Informa tion Syste m and Tech nology Arc hitecture (VistA) an d applicat ions integ rated with VistA. Th e increasi ng need to integrate VA comput ing system s across b usiness do mains and with exter nal system s, such a Department of Defens e (DoD), h as taken p recedence in bridgin g the tech nical gap between le gacy VistA and dispa rate techn ologies of Commercia l-Off-The- Shelf (COT S) product s. In addi tion, the VA healthc are Servic e Oriented Architect ure (SOA) currently faces chal lenges in:
	302	Exposing e xisting an d new Vist A business functiona lity and d ata secure ly and eff iciently.
	303	Exposing V istA funct ionality b y hiding t he distrib uted locat ion of all the exist ing VistA systems.
	304	Providing services f or use by other syst ems and te chnologies .
	305	Decoupling consuming systems f rom the im plementati on details of VistA.
	306	OI&T/PD ha s defined VSA as a n ew design approach f or providi ng SOA-com pliant int egration b etween Vis tA applica tions and external s ystems.
	307	VSA facili tates a so lution tha t provides the abili ty to:
	308	Expose Vis tA functio nality as SOA-compli ant Web se rvices dir ectly.
	309	Federate ( route) Vis tA functio nality req uests to o ne or more VistA sys tems.
	310	Integrate legacy sys tem VistA to externa l systems and applic ations.
	311	With VistA as an SOA service p rovider, t hese servi ces use Vi stA applic ation busi ness logic directly; thus, eli minating r edundancy and levera ging exist ing, teste d VistA ap plication functional ity. The V SA solutio n will pro vide:
	312	Utilities to automat e the crea tion of Vi stA SOA se rvices pla tform.
	313	VistA SOA Services P latform (r untime) en vironment necessary to host SO A services and execu te the cor responding VistA fun ctionality to one or more Vist A systems.
	314	VSA addres ses SOA ob jectives a nd provide s the abil ity for Vi stA applic ations and services to become:
	315	Economical ly extensi ble
	316	Maintainab le
	317	Individual ly replace able
	318	Fully comp liant
	319	The VSA de sign patte rn has bee n identifi ed as the preferred architectu ral design for SOA-b ased syste ms going f orward. Th e intent i s to addre ss the fun ctional re quirements of connec tivity des igns (e.g. , Medical Domain Web Services [MDWS], Vi stA Integr ation Adap tor [VIA], Clinical Data Servi ces [CDS], etc.) for the integ ration of VistA with external systems/ap plications . As such, VSA will need to sa tisfy the consumer n eeds curre ntly suppl ied by tho se approac hes, as we ll as sign ificantly enhance th e followin g:
	320	VistA secu rity
	321	System per formance
	322	Sustainabi lity
	323	The VSA so lution has adopted a phased, i terative a pproach to requireme nts defini tion, deve lopment, a nd impleme ntation of new capab ilities. T his approa ch allows VA to:
	324	Finalize a discrete set of req uirements.
	325	Implement VSA softwa re capabil ities.
	326	Roll out u tilities a nd softwar e function alities.
	327	This docum ent contai ns a list and descri ption of r equirement s that dep ict the fu nctionalit y within t he iterati on of plan ning, anal ysis, desi gn, and so ftware dev elopment f or the VSA Phase 2 p roject. Th e requirem ents in th is documen t can be u sed to con struct, co nfigure, a nd test th e software to suppor t the VSA solution.
	328	Purpose
	329	The purpos e of this RSD is to:
	330	Define the requireme nts for de veloping t he VSA sol ution, whi ch include s:
	331	Framework functional requireme nts
	332	Technical requiremen ts
	333	Security r equirement s
	334	System req uirements
	335	Provide tr aceability between t he VSA pro duct featu res and bu siness nee ds with gu idance fro m the Busi ness Requi rements Do cument (BR D).
	336	Function a s the VSA master req uirements specificat ion, provi ding a bas eline to s upport tes ting of th e proposed toolset, which incl udes the V SA Wizard functional ity and it s associat ed runtime environme nt used fo r service execution.
	337	It is impo rtant to n ote that t hese speci fications will be re vised as n eeded for subsequent iteration s of this document, and will b e publishe d as part of the Pro ject Manag ement Acco untability System (P MAS) plann ing phase for the ne xt increme nts of the VSA proje ct.
	338	The functi onal syste m shall co ver the co mprehensiv e, scope f or VSA. It is antici pated that as part o f each pro ject incre ment, a de tailed req uirements analysis w ill be per formed. Th is analysi s will inc lude a det ailed elab oration of the requi rements as they pert ain to the respectiv e scope of each incr ement. Upd ated versi ons of the RSD will be publish ed to addr ess the de fined scop e for each respectiv e incremen t and to i nclude det ailed use cases. The se detaile d use case s will be developed incrementa lly under each requi rements an alysis pha se of the project.
	339	To gain an explicit understand ing of req uirements needed to support VS A, this do cument is intended f or use by the follow ing:
	340	VHA busine ss represe ntatives
	341	Program an d project management
	342	Architects
	343	Developmen t
	344	Software Q uality Ass urance (SQ A) analyst s
	345	Other proj ect stakeh olders
	346	Scope
	347	The scope for VSA Ph ase 2 is t o:
	348	Transition the Platf orm protot ype to a d eployable initial op erating ca pability ( IOC) pilot package s tatus; rol lout the I OC package to up to 11 pilot s ites; and provide en hancements , source c ode, insta llation pr ocedures, documentat ion and tr aining. In order to transition the Platf orm protot ype to a d eployable IOC pilot package, t he Contrac tor shall further ex tend the p rototype t o meet VA Enterprise -grade req uirements, 508 compl iance, pat ient safet y mandates , as well as undergo extensive performan ce and use r acceptan ce testing given the clinical nature of the soluti on involvi ng direct patient ca re and saf ety.
	349	Create a s oftware de velopment tool, Vist A Services Assembler Wizard, t o simplify the creat ion of Vis tA SOA ser vices. The type of s ervices th at the Wiz ard genera tes and th e types of services that the r untime env ironment c an host an d run are Representa tional Sta te Transfe r (REST) a nd Simple Object Acc ess Protoc ol (SOAP) service.
	350	Create, mo del (in ru ntime), de velop, and deploy a VistA SOA Services P latform fo r IOC nati onal deplo yment to h ost and ex ecute Vist A SOA serv ices using Governmen t provided test and developmen t infrastr ucture(s). The platf orm includ es a Feder ating Plat form and c orrespondi ng service execution component s that all ows aggreg ation of f unctionali ty in mult iple VistA instances . The plat form compo nents and service ex ecution pr ovide a si mple view that expos es functio nality in multiple V istA syste ms as indi vidual Vis tA SOA ser vices.
	351	Identify a nd produce multiple sample Vis tA SOA bus iness serv ices as “r eference i mplementat ions.” In the near t erm, VSA w ill use vi rtual inte gration en vironments provided by the Ent erprise De velopment Environmen t (EDE) te ams. Howev er, to inc lude devel opment and testing e nvironment s for buil ding, inte grating, a nd testing VSA compo nents, VSA -P2 will progress t o environm ents in th e followin g location s:
	352	IOC Sites:
	353	Boise, ID
	354	Hudson Val ley, NY
	355	Memphis, T N
	356	Hampton Ro ads, VA
	357	South Texa s (San Ant onio), TX
	358	For Federa tion:
	359	Table 1: V SA Primary and Failo ver Sites
	360	Primary Si tes
	361	Failover S ites
	362	Austin Inf ormation T echnology Center (AI TC)
	363	Philadelph ia Informa tion Techn ology Cent er (PITC)
	364
	365	As VSA imp lements co nnectivity and softw are distri bution mod els that a re not cur rently mai nstream in the VA, t he second area of sc ope involv es:
	366	Documentat ion of pol icy, proce ss, and te chnical us er guidanc e regardin g the opti mal defini tion of VS A services .
	367	Distributi on of such services to the var ious syste ms and tec hnical env ironments necessary for the fu nction of VSA servic es. For ex ample:
	368	Enterprise Messaging Infrastru cture (eMI )
	369	VSA Run-Ti me
	370	HyperText Transfer P rotocol (H TTP) to Vi stA MUMPS Binding/ I ntegration with pati ent lookup service
	371	Identity a nd Access Management (IAM)
	372	The VSA pr oject team will coll aborate wi th busines s represen tatives an d software developme nt initiat ives to id entify sam ple VistA SOA busine ss service s as a “re ference im plementati on” to cri tically te st and to demonstrat e the func tionality of VSA uti lities. Ho wever it i s not the scope or i ntent of t he VSA eff ort to ide ntify and produce a collection of “servi ces” for s ubsequent organizati onal use. This activ ity would be perform ed by soft ware devel opment ini tiative te ams that u se VSA uti lities to produce Vi stA-based services.
	373	The busine ss benefit s of a ful l-featured VSA inclu de, but ar e not limi ted to, th e followin g:
	374	Provides c omplete co mpliance a nd integra tion with VA Enterpr ise Design Patterns for SOA ar chitecture and infra structure.
	375	Produces V istA SOA s ervices th at are aut horitative and non-d uplicated.
	376	Enhances s ystem main tainabilit y, sustain ability, a nd applica tion repla ce ability .
	377	Produces t echnically standardi zed and hi ghly maint ainable SO A services .
	378	Cost effec tive, low organizati onal impac t, with mi nimal staf f orientat ion and tr aining.
	379	Enables ra pid assemb ly of exis ting VistA functiona lity as SO A-complian t services by non-pr ogrammers.
	380	Facilitate s rapid Vi stA SOA se rvice deve lopment th rough an i ncremental approach.
	381	Allows for increment al deploym ent and co nsumption of VistA S OA service s.
	382	Addresses SOA object ives with enhanced s ecurity an d system p erformance (once IAM Security Assertion Mark-up La nguage (SA ML) token process is implement ed).
	383	Provides i mmediate v alue befor e full eMI infrastru cture is i n place.
	384	Alleviates “vendor d ependence” concerns while expo nentially expanding VistA exte nsibility and “open source” pr oduct deve lopment op portunitie s.
	385	Significan tly expand s VistA ex tensibilit y and syst em integra tion oppor tunities.
	386	Table 2: V SA Project Scope: Go als and Ob jectives
	387	Goal/Objec tive
	388	Desired Ou tcome
	389	Measuremen t
	390	Impact
	391	Provide ut ilities fo r automati ng the cre ation of V istA SOA s ervices an d supporti ng their u se.
	392	VistA SOA Services P latform ut ilities th at support automated VistA SOA service c reation an d executio n.
	393	VistA SOA services a re consuma ble by ext ernal syst ems/applic ations.
	394	NOTE: Web services w ill be man aged by th e Enterpri se Messagi ng Infrast ructure (e MI), which will serv e as a Web servicer registry a nd reposit ory.
	395	VistA can be easily integrated with exte rnal syste ms/applica tions thro ugh SOA-co mpliant ar chitecture .
	396	Enable the exposure of existin g VistA da ta and met hods as SO A-compatib le Web ser vices.
	397	Use of VSA utilities to create business services t hat provid e business value to VA mission and objec tives.
	398	Current VA developme nt and sys tem integr ation init iatives ar e consumer s of VistA SOA servi ces implem ented by V SA.
	399	Advanced s tate of SO A architec ture imple mentation in the VA and associ ated softw are functi onality an d sustaina bility ben efits.
	400	Abstract V istA syste m develope rs and int egrators f rom multip le technol ogy orient ation.
	401	Consuming systems / applicatio ns can be integrated without e xtensive k nowledge o f VistA te chnology.
	402	VA softwar e developm ent staff members ar e able to rapidly cr eate and d eploy Vist A SOA Serv ices with minimal re -training.
	403	Improved u se of exis ting staff skills, l everaging of previou sly implem ented Vist A applicat ion functi onality.
	404	Improve Vi stA develo pment “tim e to marke t” and ove rall syste m sustaina bility.
	405	Automated, standardi zed produc tion of Vi stA SOA se rvice comp onents.
	406	Developmen t time for VistA rel ated servi ces is not ably reduc ed support ing effici ent softwa re deliver y.
	407	Provides c ost effect ive method ology for the integr ation of V istA with external s ystems.
	408	References
	409	The conten t of this document i s based, i n part, on the PMAS Requiremen ts Specifi cation Doc ument (RSD ) template . Addition al documen ts referen ced in the creation of this re quirements specifica tion inclu de:
	410	ProPath Sh arePoint s ite
	411	Project Ma nagement A ccountabil ity System (PMAS) Pr ogram Mana gement Doc ument Repo sitory
	412	VistA Serv ices Assem bler Busin ess Requir ements Doc ument (BRD )
	413	Authentica tion, Auth orization, and Audit Design Pa ttern: Int ernal User Identity Authentica tion
	414	VA Enterpr ise Design Patterns:
	415	Documents Design Pat terns SOA
	416	VA Enterpr ise Shared Services (ESS) Fami ly of Serv ices/Initi ative Mana gement (Fo SIM)
	417	Enterprise Shared Se rvices (ES S) Service Oriented Architectu re (SOA) M ethodology / VA Fami ly of Serv ices Initi atives Man agement Fo sim
	418	VA Handboo k 6500
	419	VA Directi ve 6500
	420	FIPS PUB 1 99, Standa rds for Se curity Cat egorizatio n of Feder al Informa tion and i nformation Systems
	421	National I nstitute o f Standard s and Tech nology (NI ST) Specia l Publicat ion (SP):
	422	National I nstitute o f Standard s and Tech nology Spe cial Publi cation: 80 0-30 rev 1
	423	National I nstitute o f Standard s and Tech nology Spe cial Publi cation: 80 0-37
	424	National I nstitute o f Standard s and Tech nology Spe cial Publi cation: 80 0-53
	425	National I nstitute o f Standard s and Tech nology Spe cial Publi cation: 80 0-60 rev 1
	426	National I nstitute o f Standard s and Tech nology Spe cial Publi cation: 80 0-53 rev 4 (supersed es Revisio n 3)
	427	National I nstitute o f Standard s and Tech nology Spe cial Publi cation: 80 0-111
	428	Fast Healt hcare Inte roperabili ty Resourc es (FHIR) Specificat ion
	429	VA Acronym s
	430	Overall De scription
	431	The follow ing specif ications d elineate t he require ments nece ssary for the develo pment of t he VSA com ponents, d etailing t he overall specifica tions for the utilit ies and in frastructu re element s that sup port the a uto-genera tion and e xecution o f Web serv ices. Thes e componen ts cover a small ran ge of VSA business n eeds, func tional and non-funct ional requ irements, and will s erve as in put to sub sequent sy stem devel opment lif ecycle act ivities an d artifact s, such as architect ure defini tion, syst em design, and syste m test pla ns. VSA pr ovides an easy to us e and admi nister VSA Wizard fu nctionalit y with the goal to p rovide aut horized in formation and legacy services to VA cons umers requ esting acc ess to Vet eran data. Many of t he require ments are applicable to multip le section s of the R equirement s Specific ation docu ment (RSD) .
	432	The requir ements for the VSA p roject are entered a nd managed into the VA Rationa l Team Con cert (RTC) tool via Rational R equirement s Composer (RRC) and Rational Quality Ma nager (RQM ). They wi ll be used to create and maint ain full t raceabilit y between new/update d requirem ents and t he associa ted change requests from initi al discove ry to reso lution. Ar tifacts ca n be found at:
	433	Rational R equirement s Manageme nt - VSA ( RM)
	434	Rational Q uality Man ager - VSA (QM)
	435	Rational C hange and Configurat ion Manage ment - VSA (CM)
	436	The VA VSA Product D evelopment (PD) Shar ePoint sit e will be used as a repository and knowl edge manag ement tool for proje ct-related documents , such as the VSA Pr oject Char ter, Proje ct Managem ent Plan, VSA archit ectural an d technica l artifact s can be f ound on th e VA VSA P D Project SharePoint site.
	437	Accessibil ity Specif ications
	438	Refer to r equirement s 2.6.9.43 3 and 2.6. 9.434 in S ection 2.6 .9 for Sec tion 508 c ompliance.
	439	Business R ules Speci fication
	440	Business r ules are i mplemented by the re mote proce dure calls (RPCs) th emselves. VSA respon ds with er ror messag es to the requesting client ap plication. Implement ation of o rganizatio nal busine ss rule lo gic allows client an d provider applicati on develop ers to mak e requests to VSA wi thout requ iring know ledge of r ules that govern acc ess to RPC s, queryin g RPCs, an d aggregat ing and pa rsing RPC results. I t is impor tant to no te that co nsuming ap plications are respo nsible for their own adherence to all VA business rules.
	441	Design Con straints S pecificati on
	442	The VSA de sign is in formed and driven by architect ural desig n patterns and artif acts. Each section o f the arch itecture d ocument de rives conc eptual app lication, data, and infrastruc ture desig ns and an overview d escribing the full f unctionali ty of the utilities to be prov ided. Flow charts, sc reen shots , swim lan es, patter n sketches , and othe r graphic depictions are used to show ho w the VSA solution s upports th e overall design of the VSA Wi zard funct ionality a nd infrast ructure co mponents.
	443	Technical overview d ocuments a re found o n the VSA’ s Project SharePoint site.
	444	Disaster R ecovery Sp ecificatio n
	445	Refer to S ection 2.6 .13.
	446	Documentat ion Specif ications
	447	Refer to S ection 2.6 .14.
	448	Functional Specifica tions
	449	The VSA Wi zard funct ionality a nd its run time infra structure components allow ser vice devel opers to c hoose the VistA func tionality that are e xposed as a Web serv ice.
	450	Service de veloper us ing the VS A Wizard f unctionali ty:
	451	Selects th e RPC.
	452	Creates a service de finition f ile.
	453	Generates a service for a spec ific runti me.
	454	Developer tests the service on its speci fic runtim e.
	455	Original r equirement s are in n ormal text . Modified or new re quirements are in it alics. Jus tification s explain any change s to the r equirement s set.
	456	“Expected Delivery” indicates the planne d delivery Phase, In crement, a nd Sprint. Every eff ort will b e made to maintain t his, but a s Agile de velopment dictates, priorities may be sh ifted by t he custome r needs an d by any d ependencie s with dev elopment o r outside interfaces as needed . For the most accur ate repres entation o f the plan ned delive ry, please use VA JA ZZ and the Requireme nts Tracea bility Mat rix (RTM) in the VA SharePoint site.
	457	VSA Wizard Functiona lity—User Interface
	458	The VSA Wi zard funct ionality e nables ser vice devel opers to e ither iden tify or cr eate new V istA funct ionality a s a Web se rvice.
	459	Table 3: V SA Wizard Functional ity-User I nterface R equirement s
	460	Req. #
	461	Requiremen t
	462	Expected D elivery
	463	2.6.1.1
	464	The VSA Wi zard funct ionality s hall inclu de a secur e VA Intra net Web in terface us ed by VA M UMPS (M) d evelopers or system integrator s at desig n-time.
	465	(Original) The VSA W izard web applicatio n shall in clude a se cure VA In tranet web interface to be use d by VA MU MPS (M) de velopers o r system i ntegrators at design -time.
	466	Justificat ion for Re vision: Ad ded text f or clarity
	467	P2.2.2
	468	2.6.1.1.1
	469	The VSA Wi zard web a pplication shall inc lude a sec ure VA Int ranet web interface to be used by VA MUM PS (M) dev elopers or system in tegrators at design- time to co mply with the VistA Authentica tion “M4A” minimum a ttributes.
	470	Justificat ion for Re moval: Com bined and addressed by 2.6.1.3
	471	Removed
	472	2.6.1.1.2
	473	The VSA Wi zard web a pplication shall inc lude a sec ure VA Int ranet web interface to be used by VA MUM PS (M) dev elopers or system in tegrators at design- time to co mply with the VistA Authentica tion using SAML toke ns.
	474	Justificat ion for Re moval: Com bined and addressed by 2.6.1.1 .3
	475	Removed
	476	2.6.1.1.3
	477	The VSA wi zard funct ionality s hall inclu de a secur e VA Intra net web in terface to be used b y develope rs or syst em integra tors at de sign-time that compl ies with V A 6500 sec urity requ irements a nd uses VA ESS IAM a uthenticat ion/author ization.
	478	(Original) The VSA W izard web applicatio n shall in clude a se cure VA In tranet web interface to be use d by VA MU MPS (M) de velopers o r system i ntegrators at design -time to c omply with the VistA Authentic ation via Transport Layer Secu rity (TLS) connectio ns.
	479	Justificat ion for Re vision: Re worded for clarity
	480	P2.3
	481	2.6.1.1.4
	482	The VSA Wi zard funct ionality s hall inclu de a secur e VA Intra net Web in terface to be used b y VA MUMPS (M) devel opers or s ystem inte grators at design-ti me via eMI connectio ns.
	483	(Original) The VSA W izard web applicatio n shall in clude a se cure VA In tranet web interface to be use d by VA MU MPS (M) de velopers o r system i ntegrators at design -time to c omply with the VistA Authentic ation via Enterprise Service b us (ESB) c onnections .
	484	Justificat ion for Re vision: Re worded for clarity
	485	P2.2.2
	486	2.6.1.2
	487	VSA shall provide a Graphical User Inter face (GUI) .
	488	(Original) VSA shall provide V SA Wizard Graphical User Inter face (GUI) .
	489	Justificat ion for Re vision: Re worded for clarity
	490	P2.2.2
	491	2.6.1.3
	492	The VSA Wi zard servi ce assembl er shall i mplement u ser authen tication f or the use of the VS A Wizard. This is co nsistent w ith 2.6.1. 1.3
	493	P2.2.2
	494	2.6.1.4
	495	The VSA Wi zard funct ionality s hall enabl e service developers to identi fy/define existing V istA logic as the bu siness log ic for a W eb service .
	496	(Original) The VSA W izard main page shal l enable s ervice dev elopers to identify/ define exi sting Vist A logic as the busin ess logic for a web service.
	497	Justificat ion for Re vision: Re worded for clarity
	498	P2.2.2
	499	2.6.1.5
	500	The VSA Wi zard funct ionality s hall allow a user to search th rough a li st of exis ting Servi ce Descrip tors for e diting.
	501	(Original) The VSA W izard main page shal l allow a user to se arch throu gh the fil e system o f the Fede rating Pla tform to s elect an e xisting Se rvice Desc riptor fil e.
	502	Justificat ion for Re vision: Re worded for clarity
	503	P2.3
	504	2.6.1.6
	505	The VSA Wi zard main page shall provide t he user wi th the abi lity to:
	506	create a n ew Service Descripto r
	507	browse thr ough servi ce descrip tors to al low select ion
	508	enter the name of th e service descriptor manually
	509	select the correct s ervice des criptor an d click on it for ed iting
	510	(Original) The VSA W izard main page shal l provide the user w ith the ab ility to c reate a ne w Service Descriptor file.
	511	Justificat ion for Re vision: Re worded for clarity
	512	P2.2.2
	513	2.6.1.7
	514	The VSA Wi zard point and click interface shall all ow navigat ion throug h the file system to allow sel ection of the correc t file pat h.
	515	Justificat ion for Re moval: Add ressed by 2.6.1.6
	516	Removed
	517	2.6.1.8
	518	The VSA Wi zard point and click interface shall all ow manual entry of t he path to the file.
	519	Justificat ion for Re moval: Add ressed by 2.6.1.6
	520	Removed
	521	2.6.1.9
	522	The VSA Wi zard point and click interface shall all ow the use r to selec t the corr ect Extend ed Markup Language ( XML) file and click on the fil e to start editing.
	523	Justificat ion for Re moval: Add ressed by 2.6.1.6
	524	Removed
	525	2.6.1.10
	526	The system shall dis play a “Te xt Descrip tion Box” detailing Simple Obj ect Access Protocol (SOAP) Ser vice Infor mation fie lds from t he Service Descripto r. Include s:
	527	Service Na me
	528	Version
	529	Runtime Na mespace
	530	Service Na mespace
	531	P2.4
	532	2.6.1.11
	533	The system shall dis play a “Te xt Descrip tion Box” detailing Representa tional Sta te Transfe r (REST) S ervice Inf ormation f rom the Se rvice Desc riptor. In cludes:
	534	Service Na me
	535	Version
	536	Runtime Na mespace
	537	URL Path
	538	Life Cycle
	539	Produces
	540	Consumes
	541	P2.2.2
	542	2.6.1.12
	543	The system shall pro vide a Ser vice Descr iptor form to define the servi ce.
	544	P2.2.2
	545	2.6.1.13
	546	The system shall pro vide the u ser with t he ability to select a type of service ( SOAP or RE ST).
	547	Justificat ion for Re moval: Thi s requirem ent was co mbined wit h 2.6.1.14
	548	Removed
	549	2.6.1.14
	550	The system shall dis play servi ce types t o select f rom, at th e time of selecting a Service Descriptor the syste m should s how the co rrect serv ice type a ssociated with the s ervice (wh en in Edit mode):
	551	SOAP
	552	REST
	553	P2.5
	554	2.6.1.15
	555	The VSA Wi zard selec tion field shall pro vide the a bility to input the following SOAP infor mation:
	556	Web Servic e Name.
	557	Web Servic e Version
	558	Service Na mespace (p revent nam e collisio ns)
	559	Run-time N amespace ( prevent na me collisi ons)
	560
	561	(Original) The VSA W izard sele ction fiel d shall pr ovide the ability to input SOA P informat ion for a Service Na me.
	562	Justificat ion for Re vision: Re worded for clarity
	563	P2.5
	564	2.6.1.16
	565	The VSA Wi zard selec tion field shall pro vide the a bility to input SOAP informati on for the Version o f the web service.
	566	Justificat ion for Re moval: Thi s requirem ent was co mbined wit h 2.6.1.15
	567	Removed
	568	2.6.1.17
	569	The VSA Wi zard selec tion field shall pro vide the a bility to input SOAP informati on for the Runtime N amespace.
	570	Justificat ion for Re moval: Thi s requirem ent was co mbined wit h 2.6.1.15
	571	Removed
	572	2.6.1.18
	573	The system shall dis play SOAP- specific f ields on t he VSA Wiz ard Servic e Descript or form.
	574	P2.5
	575	2.6.1.19
	576	The VSA Wi zard selec tion field shall pro vide the a bility to input SOAP informati on for a S ervice Nam espace to allow mult iple appli cations to use the V SA Wizard without na ming colli sions.
	577	Justificat ion for Re moval: Thi s requirem ent was co mbined wit h 2.6.1.15
	578	Removed
	579	2.6.1.20
	580	The system shall dis play REST- specific f ields on t he VSA Wiz ard Servic e Descript or form.
	581	P2.3
	582	2.6.1.21
	583	The VSA Wi zard selec tion field shall pro vide the a bility to input REST informati on for a U niform Res ource Loca tor (URL) path to th e resource of the da ta.
	584	P2.2.2
	585	2.6.1.22
	586	The system shall pro vide the u ser with t he ability to select a REST li fe cycle e ntry from a drop-dow n list.
	587	P2.3
	588	2.6.1.23
	589	The system shall pro vide the u ser with t he ability to select a REST “P roduces” e ntry from a drop-dow n list.
	590	P2.3
	591	2.6.1.24
	592	The system shall pro vide the u ser with t he ability to select a REST “C onsumes” e ntry from a drop-dow n list.
	593	P2.3
	594	2.6.1.25
	595	The system shall pro vide the u ser with t he ability to search for an ex isting RPC based on an RPC Nam e.
	596	P2.2.2
	597	2.6.1.26
	598	The system shall pro vide the u ser with t he ability to input informatio n in the f ollowing f ield:
	599	RPC Name
	600	P2.2.2
	601	2.6.1.27
	602	The system shall pro vide a dro p-down lis t for the user to se lect from a list of RPCs retur ned from V istA.
	603	P2.2.2
	604	2.6.1.28
	605	The system shall pro vide the u ser with t he ability to view t he details of a sele cted RPC.
	606	P2.2.2
	607	2.6.1.29
	608	The system shall pro vide the u ser with t he ability to auto-g enerate an operation from a se lected RPC .
	609	P2.2.2
	610	2.6.1.30
	611	The system shall pro vide the u ser with t he ability to modify the auto- generated SOAP opera tion.
	612	P2.5
	613	2.6.1.31
	614	The system shall pro vide the u ser with t he ability to add on e or more SOAP-speci fic operat ions to on e RPC.
	615	P2.5
	616	2.6.1.32
	617	The system shall pro vide the u ser with t he ability to add on e SOAP ope ration to multiple R PCs (aka “ Service Co mposition” ).
	618	P2.5
	619	2.6.1.33
	620	The system shall pro vide the u ser with t he ability to input SOAP infor mation for an RPC Na me.
	621	P2.5
	622	2.6.1.34
	623	The system shall pro vide the u ser with t he ability to input SOAP infor mation for an Operat ion Name.
	624	P2.5
	625	2.6.1.35
	626	The system shall pro vide the u ser with t he ability to select a SOAP Re sponse Typ e from a d rop-down l ist correl ating a re turn type value of t he data re sponse fro m VistA th at can be represente d in any o f the foll owing form ats:
	627	String
	628	JavaScript Object No tation (JS ON)
	629	List
	630	Map
	631	P2.5
	632	2.6.1.36
	633	The system shall pro vide the u ser with t he ability to edit a SOAP-spec ific opera tion.
	634	P2.5
	635	2.6.1.37
	636	The system shall pro vide the u ser with t he ability to delete a SOAP-sp ecific ope ration, an d all its associated input par ameters.
	637	P2.5
	638	2.6.1.38
	639	The system shall dis play to th e user a w arning mes sage confi rming a de letion of a SOAP ope ration.
	640	P2.5
	641	2.6.1.39
	642	The system shall pro vide the u ser with t he ability to add on e to multi ple SOAP-s pecific pa rameters i f necessar y that def ine the in put parame ters for a n operatio n.
	643	P2.5
	644	2.6.1.40
	645	The system shall pro vide the u ser with t he ability to input SOAP infor mation for a Name of a paramet er.
	646	P2.5
	647	2.6.1.41
	648	The system shall pro vide the u ser with t he ability to input SOAP infor mation for a Type of parameter .
	649	P2.5
	650	2.6.1.42
	651	The system shall pro vide the u ser with t he ability to select a SOAP-sp ecific Par ameter Typ e from a d rop-down l ist that d efines the type of p arameter.
	652	P2.5
	653	2.6.1.43
	654	The system shall pro vide the u ser with t he ability to delete a SOAP-sp ecific inp ut paramet er.
	655	P2.5
	656	2.6.1.44
	657	The system shall dis play to th e user a w arning mes sage confi rming a de letion of a SOAP-spe cific inpu t paramete r.
	658	P2.5
	659	2.6.1.45
	660	The system shall pro vide the u ser with t he ability to edit a SOAP-spec ific input parameter .
	661	P2.5
	662	2.6.1.46
	663	The system shall pro vide the u ser with t he ability to expand or collap se the SOA P-specific input par ameters in formation for any op eration.
	664	P2.5
	665	2.6.1.47
	666	The system shall pro vide the u ser with t he ability to add on e to multi ple REST-s pecific op erations t hat corres pond to a VistA remo te procedu re to be i nvoked.
	667	P2.2.2
	668	2.6.1.48
	669	The system shall pro vide the a bility to display in put REST O peration i nformation for an RP C Name.
	670	P2.2.2
	671	2.6.1.49
	672	The system shall pro vide the a bility to display in put REST O peration i nformation for an Op eration Na me.
	673	P2.2.2
	674	2.6.1.50
	675	The system shall pro vide the a bility to display in put REST O peration i nformation for a Res ponse Type .
	676	P2.2.2
	677	2.6.1.51
	678	The system shall pro vide the a bility to display in put REST O peration i nformation for a HTT P Method.
	679	P2.3
	680	2.6.1.52
	681	The system shall pro vide the a bility to display in put REST O peration i nformation for a URL Path.
	682	P2.2.2
	683	2.6.1.53
	684	The system shall pro vide the a bility to display in put REST O peration i nformation for a Con sumes entr y.
	685	P2.3
	686	2.6.1.54
	687	The system shall pro vide the u ser with t he ability to displa y input RE ST Operati on informa tion for a Produces entry, e.g . JSON.
	688	P2.2.2
	689	2.6.1.55
	690	The system shall pro vide the a bility to enter the name of th e REST-spe cific RPC associated with this operation .
	691	P2.3
	692	2.6.1.56
	693	The system shall pro vide the a bility to enter a un ique Opera tion Name for this R EST-specif ic operati on.
	694	P2.3
	695	2.6.1.57
	696	The REST-s pecific Op eration Na me will co rrespond t o the defa ult name o f the gene rated Runt ime operat ion.
	697	P2.3
	698	2.6.1.58
	699	The system shall pro vide the u ser with t he ability to select a REST-sp ecific Res ponse Type from a dr op-down li st correla ting a ret urn type v alue of th e data res ponse from VistA tha t can be r epresented in any of the follo wing forma ts:
	700	String
	701	JavaScript Object No tation (JS ON)
	702
	703	(Original) The syste m shall pr ovide the user with the abilit y to selec t a REST-s pecific Re sponse Typ e from a d rop-down l ist correl ating a re turn type value of t he data re sponse fro m VistA th at can be represente d in any o f the foll owing form ats:
	704	String
	705	JavaScript Object No tation (JS ON)
	706	List
	707	Map
	708	Justificat ion for Re vision: St ring and J SON are mi nimum form ats for RE ST, theref ore, List and MAP ar e not need ed here.
	709	P2.3
	710	2.6.1.59
	711	The system shall pro vide the u ser with t he ability to select a REST-sp ecific HTT P Method f rom a drop -down list correlati ng a metho d definiti on value t hat can be represent ed as:
	712	GET
	713	POST
	714	PUT
	715	DELETE
	716	HEAD
	717	P2.3
	718	2.6.1.60
	719	The system shall pro vide the u ser with t he ability to enter the relati ve Uniform Resource Locator (U RL) path o f the REST ful operat ion.
	720	(Original) The system shall pro vide the u ser with t he ability to enter the relati ve Uniform Resource Locator (U RL) path o f the REST ful operat ion. This correspond s to the @ Path annot ation of t he generat ed Runtime operation .
	721	Justificat ion for Re vision: De leted text for clari ty
	722	P2.3
	723	2.6.1.61
	724	The system shall pro vide the u ser with t he ability to select a REST-sp ecific Con sumes entr y from a d rop-down l ist to spe cify the M ultimedia Internet M ail Extens ions (MIME ) media ty pe that ca n be consu med by the operation . Examples of media types are:
	725	“text/plai n”
	726	“test/html ”
	727	“applicati on/xml”
	728	“applicati on/h-www-f orm-urlenc oded”
	729	“applicati on/json”
	730
	731	(Original) The system shall pro vide the u ser with t he ability to select a REST-sp ecific Con sumes entr y from a d rop-down l ist to spe cify the M ultimedia Internet M ail Extens ions (MIME ) media ty pe that ca n be consu med by the operation . Examples of media types are:
	732	“text/plai n”
	733	“test/html ”
	734	“applicati on/xml”
	735	“applicati on/h-www-f orm-urlenc oded”
	736	applicatio n/json”
	737	This corre sponds to the @Consu mes annota tion of th e generate d Runtime operation.
	738
	739	Justificat ion for Re vision: De leted text for clari ty.
	740	P2.3
	741	2.6.1.62
	742	The system shall pro vide the u ser with t he ability to select a REST-sp ecific Pro duces entr y from a d rop-down l ist to spe cify the M IME media type of th e response that the operation can produc e and send back to t he client. Examples of media t ypes are:
	743	“text/plai n”
	744	“test/html ”
	745	“applicati on/xml”
	746	“applicati on/h-www-f orm-urlenc oded”
	747	“applicati on/json”
	748
	749	(Original) The syste m shall pr ovide the user with the abilit y to selec t a REST-s pecific Pr oduces ent ry from a drop-down list to sp ecify the MIME media type of t he respons e that the operation can produ ce and sen d back to the client . This cor responds t o the @Pro duces anno tation of the genera ted Runtim e operatio n. Example s of media types are :
	750	“text/plai n”
	751	“test/html ”
	752	“applicati on/xml”
	753	“applicati on/h-www-f orm-urlenc oded”
	754	“applicati on/json”
	755
	756	Justificat ion for Re vision: De leted text that is i mplementat ion specif ic
	757	P2.3
	758	2.6.1.63
	759	The system shall pro vide the u ser with t he ability to edit a REST-spec ific opera tion.
	760	P2.4
	761	2.6.1.64
	762	The system shall pro vide the u ser with t he ability to delete a REST-sp ecific ope ration, an d all its associated input par ameters.
	763	P2.4
	764	2.6.1.65
	765	The system shall dis play to th e user a w arning mes sage confi rming a de letion of a REST-spe cific oper ation.
	766	P2.2.2
	767	2.6.1.66
	768	The system shall pro vide the u ser with t he ability to add on e to multi ple REST-s pecific pa rameters i f necessar y that def ine the in put parame ters for a n operatio n.
	769	P2.4
	770	2.6.1.67
	771	The system shall pro vide the a bility to display in put REST-s pecific in formation for a Name of a REST parameter .
	772	P2.4
	773	2.6.1.68
	774	The system shall pro vide the a bility to display in put inform ation for a Name of a REST par ameter.
	775	P2.4
	776	2.6.1.69
	777	The system shall pro vide the a bility to display in put inform ation for a Type of a REST par ameter.
	778	P2.4
	779	2.6.1.70
	780	The system shall pro vide the a bility to display in put inform ation for a Param Ty pe of a RE ST paramet er.
	781	P2.4
	782	2.6.1.71
	783	The system shall pro vide the a bility to display in put inform ation for a Param Na me of a RE ST paramet er.
	784	P2.4
	785	2.6.1.72
	786	The system shall pro vide the a bility to display in put inform ation for a Default Name of a REST param eter.
	787	P2.4
	788	2.6.1.73
	789	The system shall req uire the u ser to ent er a uniqu e Name for the REST- specific i nput param eter.
	790	(Original) The system shall pro vide the u ser with t he ability to enter a unique N ame for th e REST-spe cific inpu t paramete r.
	791	Justificat ion for Re vision: Re worded for clarity
	792	P2.4
	793	2.6.1.74
	794	The unique parameter name corr esponds to the name of the RES T-specific input var iable used in the ge nerated Ru ntime oper ation.
	795	P2.4
	796	2.6.1.75
	797	The system shall pro vide the u ser with t he ability to select Type from a drop-do wn list th at defines the type of the RES T-specific input par ameter (e. g., string , ref, lis t, and map ).
	798	P2.2.2
	799	2.6.1.76
	800	The system shall pro vide the u ser with t he ability to select a REST-sp ecific Par am Type, w hich indic ates how t he paramet er will be sent to t he resourc e method. Possible v alues can include:
	801	PathParam
	802	QueryParam
	803	MatrixPara m
	804	FormParam
	805	HeaderPara m
	806	CookiePara m
	807	Context
	808	This corre sponds to the annota tion of th e paramete r in the r esource me thod signa ture.
	809	P2.4
	810	2.6.1.77
	811	The system shall pro vide the u ser with t he ability to enter the REST-s pecific na me of the parameter. This corr esponds to the argum ent to be used in th e followin g annotati on of the input para meter of t he generat ed Runtime operation :
	812	@PathParam
	813	@QueryPara m
	814	@MatrixPar am
	815	@FormParam
	816	@HeaderPar am
	817	@CookiePar am
	818	@Context
	819	Justificat ion for Re moval: Thi s is addre ssed by 2. 6.1.76
	820	Removed
	821	2.6.1.78
	822	The system shall pro vide the u ser with t he ability to specif y a defaul t value fo r this inp ut paramet er if one is not pas sed.
	823	P2.4
	824	2.6.1.79
	825	The defaul t value co rresponds to the @De faultValue annotatio n of the R EST-specif ic input p arameter o f the gene rated Runt ime operat ion.
	826	Justificat ion for Re moval: Thi s is addre ssed by 2. 6.1.78
	827	Removed
	828	2.6.1.80
	829	The system shall pro vide the u ser with t he ability to delete a REST in put parame ter.
	830	P2.4
	831	2.6.1.81
	832	The system shall dis play to th e user a w arning mes sage confi rming a de letion of a REST inp ut paramet er.
	833	P2.2.2
	834	2.6.1.82
	835	The system shall pro vide the u ser with t he ability to edit a REST-spec ific input parameter .
	836	P2.2.2
	837	2.6.1.83
	838	The system shall pro vide the u ser with t he ability to hide o r show the REST-spec ific input parameter s for any operation.
	839	P2.4
	840	2.6.1.84
	841	The system shall pro vide the u ser with t he ability to save a Service D escriptor.
	842
	843	(Original) The syste m shall pr ovide the user with the abilit y to save a Service Descriptor file in X ML format.
	844
	845	Justificat ion for Re vision: Re moved XML format - i mplementat ion specif ic
	846	P2.2.2
	847	2.6.1.85
	848	The system shall dis play the c ontents of a newly g enerated s ervice des criptor.
	849
	850	(Original) The syste m shall di splay the contents o f a newly generated service de scriptor f ile.
	851
	852	Justificat ion for Re vision: Re worded for clarity
	853	P2.2.2
	854	2.6.1.86
	855	The system shall not allow the user to g enerate a service fr om partial ly filled Service De scriptor f orm.
	856	P2.4
	857	2.6.1.87
	858	The system shall lab el fields in the Wiz ard that a re require d.
	859	P2.2.2
	860	2.6.1.88
	861	The system shall pro vide the u ser with t he ability to auto-g enerate a service de scriptor i nto a depl oyable run time packa ge.
	862	(Original) The syste m shall pr ovide the user with the abilit y to auto- generate a service d escriptor XML file i nto a depl oyable run time packa ge.
	863	Justificat ion for Re vision: Re moved XML format - i mplementat ion specif ic
	864	P2.4
	865	2.6.1.89
	866	The system shall pro vide the u ser with t he ability to deploy and publi sh the Web service r untime pac kage to th e non-Prod uction Fed erating Pl atform.
	867	P2.4
	868	2.6.1.90
	869	The system shall dis play the U RL of the service to be tested .
	870	P2.4
	871	2.6.1.91
	872	The system shall pro vide the u ser with t he ability to test a nd execute a deploye d Web serv ice.
	873	P2.2.2
	874	2.6.1.92
	875	The GUI sh all consis t of a str uctured po int-and-cl ick interf ace, and w ith free-t ext fields on a Serv ice Descri ptor form for the us er to ente r informat ion.
	876	P2.2.2
	877	2.6.1.93
	878	The system shall pro vide text fields use d to accep t alphanum eric entri es. Specif ic text fi elds will also accep t special characters .
	879	P2.2.2
	880	2.6.1.94
	881	The system shall pro vide drop- down selec tion menus used to p resent lon ger lists of respons es but per mit only a single re sponse (e. g., RPCs).
	882	P2.2.2
	883	2.6.1.95
	884	The system shall pro vide drop- down selec tion menus used when a short l ist of res ponses all ows only a single an swer (e.g. , a String , JSON, li st, or map response) .
	885	P2.2.2
	886	2.6.1.96
	887	The system shall pro vide butto ns used to search, d elete, ins ert, or hi de informa tion about an RPC op eration or parameter .
	888	P.2.3
	889	2.6.1.97
	890	In develop ment, VSA Wizard sha ll enforce VistA use r security to its co rrespondin g developm ent VistA instance, by meeting the requi rements of the VSA R un-Time as a consume r applicat ion (the W izard as t he consume r).
	891	(Original) VSA Wizar d shall en force Vist A user sec urity to i ts corresp onding dev elopment V istA insta nce, by me eting the requiremen ts of the VSA Run-Ti me as a co nsumer app lication ( the Wizard as the co nsumer).
	892	Justificat ion for Re vision: Re worded for clarity
	893	P2.2.2
	894	2.6.1.98
	895	In develop ment, the VSA Wizard shall all ow the use r to speci fy its Vis tA develop ment envir onment and to provid e the nece ssary cred entials th rough Acce ss and Ver ify codes to connect securely with VistA .
	896	(Original) If the VS A Wizard i s deployed in a cent ralized an d shared e nvironment , the VSA Wizard sha ll allow t he user to specify i ts VistA d evelopment environme nt and to provide th e necessar y credenti als throug h Access a nd Verify codes to c onnect sec urely with VistA.
	897	Justificat ion for Re vision: Re worded for clarity
	898	P2.2.2
	899	2.6.1.99
	900	The VSA Ph ase 2 soft ware shall allow the user (e.g ., develop er) to use a VA Intr anet Web b rowser to access the VSA Wizar d on the r untime env ironment.
	901	P2.2.2
	902	2.6.1.100
	903	The system shall pro vide the a bility for the user to modify existing o r create n ew Service Descripto r, which a re used to create VS A Web serv ices (runt ime packag es).
	904	P2.3
	905	2.6.1.101
	906	The system shall dis play Servi ce Descrip tor inform ation to a llow the u ser to sel ect it for edit.
	907	P2.2.2
	908	2.6.1.102
	909	The VSA Ph ase 2 soft ware shall create th e followin g display screens an d output r elative to the user:
	910	VSA Wizard main page (Service Descriptor front-end )
	911	VSA Wizard Service D escriptor forms for SOAP and R EST; Inclu des displa y of any V SA system messages.
	912	P2.3
	913	2.6.1.103
	914	The VSA Ph ase 2 soft ware shall create th e followin g display screens:
	915	Service De scriptor, which is u sed to def ine a Web service an d to gener ate the ru ntime pack age.
	916	(Original) The VSA P hase 2 sof tware shal l create t he followi ng display screens a nd output file:
	917	Service De scriptor X ML file, w hich is us ed to defi ne a web s ervice and to genera te the run time packa ge.
	918	Justificat ion for Re vision: Re moved XML format - i mplementat ion specif ic
	919	P2.3
	920	2.6.1.104
	921	The VSA Ph ase 2 soft ware shall create th e followin g display screens an d output f ile:
	922	A deployab le Web ser vice runti me package .
	923	P2.3
	924	2.6.1.105
	925	When the f orm is dis played, th e VSA Wiza rd functio nality sha ll enable a user to click or t ab to each field whe n entering data.
	926
	927	(Original) When the form is di splayed, t he VSA Wiz ard shall enable a u ser to cli ck or tab to each fi eld when e ntering da ta.
	928	Justificat ion for Re vision: Re worded for clarity
	929	P2.3
	930	2.6.1.106
	931	When a use r saves a form, the VSA Wizard functiona lity shall display a message a s the form is being saved.
	932	(Original) When a us er saves a form, the VSA Wizar d shall di splay a me ssage as t he form is being sav ed.
	933	Justificat ion for Re vision: Re worded for clarity
	934	P2.2.2
	935	2.6.1.107
	936	When a use r submits a form, th e VSA Wiza rd functio nality sha ll provide an indica tion that the form h as been sa ved by dis playing th e contents of the ne wly create d service descriptor
	937	(Original) When a us er submits a form, t he VSA Wiz ard shall provide an indicatio n that the form has been saved by displa ying the c ontents of the newly created s ervice des criptor in to an XML document.
	938	Justificat ion for Re vision: Re moved XML format - i mplementat ion specif ic
	939	P2.3
	940	2.6.1.108
	941	When a use r selects to create or deploy a Web serv ice runtim e package, the VSA W izard func tionality shall disp lay a mess age as the service i s being cr eated and deployed.
	942	P2.3
	943	2.6.1.109
	944	VSA runtim e platform shall pro vide an ad ministrato r user int erface for configuri ng URL end points, us er names a nd passwor ds in acco rdance wit h VA secur ity requir ements.
	945	(Original) The syste m shall pr ovide an a dministrat or user in terface fo r configur ing VSA on the runti me system to specify URL endpo ints, user names and passwords .
	946	Justificat ion for Re vision: Re worded for clarity
	947	P2.6
	948	2.6.1.110
	949	The system shall pro vide a con figuration file for configurin g the VSA applicatio n server o n the runt ime system to specif y URL endp oints, use r names an d password s.
	950	Justificat ion for Re moval: Add ressed in 2.6.1.109
	951	Removed
	952	2.6.1.111
	953	The VSA Wi zard funct ionality s hall allow the user to configu re and cho ose the Vi stA instan ce.
	954	(Original) The VSA W izard shal l allow th e user to configure and choose the neede d developm ent VistA instance.
	955	Justificat ion for Re vision: Re worded for clarity
	956	P2.2.2
	957	2.6.1.112
	958	The applic ation shal l conform to look an d feel sta ndards as establishe d by Secti on 508 of the Rehabi litation A ct (29 U.S .C. § 794d ).
	959	(Original) The appli cation sha ll conform to look a nd feel st andards as establish ed by the VA’s curre nt and fut ure health care syste ms’ core s pecificati ons for re -hosting.
	960	Justificat ion for Re vision: Re worded for clarity
	961	P2.2.2
	962	2.6.1.113
	963	A GUI appl ication sh all be dev eloped for the creat ion of ser vice descr iptors.
	964	P2.2.2
	965	2.6.1.114
	966	The VSA Wi zard funct ionality s hall allow the user to create deployable runtime p ackage
	967	(Original) The Wizar d GUI shal l allow th e user to create dep loyable ru ntime pack age from t he created service d escriptors .
	968	Justificat ion for Re vision: Re worded for clarity
	969	P2.3
	970	2.6.1.115
	971	The soluti on shall p rovide a p oint and c lick inter face with free text fields fro m the VSA Wizard fun ctionality .
	972	(Original) The solut ion shall provide a point and click inte rface with free text fields fr om the Wiz ard form.
	973	Justificat ion for Re vision: Re worded for clarity
	974	P2.2.2
	975	2.6.1.116
	976	During cre ation of a service d escriptor, part of t he GUI’s f unctionali ty shall i nterrogate the VistA for avail able RPCs and retrie ve all the details o f a given RPC to pre -populate the interf ace fields .
	977	(Original) During cr eation of a service descriptor , part of the GUI’s functional ity shall interrogat e the deve lopment Vi stA for av ailable RP Cs and ret rieve all the detail s of a giv en RPC to pre-popula te the int erface fie lds.
	978	Justificat ion for Re vision: Re worded for clarity
	979	P2.2.2
	980	2.6.1.117
	981	(NEW) The VSA soluti on shall p rovide a U I for docu mentation about the server-sid e APIs (in cluding ex posed Vist A SOA serv ices [SOAP or REST]) .
	982	P2.2.2
	983	VSA Wizard Functiona lity—Funct ions
	984	The VSA Wi zard funct ionality p rovides fo r the auto -generatio n of VistA -based ser vices.
	985	Table 4: V SA Wizard Functional ity-Functi ons
	986	Req. #
	987	Requiremen t
	988	Delivery
	989	2.6.2.117
	990	The VSA Wi zard servi ce descrip tor shall allow to L ocate and select for edit an e xisting Se rvice Desc riptor.
	991	P2.2.2
	992	2.6.2.118
	993	The VSA Wi zard shall Create a Service De scriptor.
	994	P2.2.2
	995	2.6.2.119
	996	The VSA Wi zard funct ionality s hall Searc h for RPCs to be cal led from V istA.
	997	P2.2.2
	998	2.6.2.120
	999	The VSA Wi zard funct ionality s hall Retri eve and ad d operatio ns and par ameter map pings.
	1000	P2.4
	1001	2.6.2.121
	1002	The VSA Wi zard shall Save and store serv ice descri ptor.
	1003	P2.2.2
	1004	2.6.2.122
	1005	The VSA Wi zard funct ionality s hall Creat e and depl oy runtime package ( on the dev elopment s ystem) tha t are nece ssary in d efining an d publishi ng an RPC as a Web s ervice.
	1006	P2.2.2
	1007	2.6.2.123
	1008	The VSA Wi zard shall provide a link to t est the de ployed Vis tA SOA ser vice.
	1009	(Original) The VSA W izard shal l provide a link to test the d eployed we b service.
	1010	Justificat ion for Re vision: Re worded for clarity
	1011	P2.5
	1012	2.6.2.124
	1013	The VSA Wi zard shall provide a method fo r reviewin g and veri fying the newly auto -generated VistA SOA service.
	1014	(Original) The VSA W izard shal l provide a workflow for revie wing and v erifying t he newly a uto-genera ted Web se rvice.
	1015	Justificat ion for Re vision: Re worded for clarity
	1016	P2.5
	1017	2.6.2.125
	1018	The system shall pro vide the a bility to store Serv ice Descri ptors and runtime pa ckages.
	1019	P2.2.2
	1020	2.6.2.126
	1021	The VSA Wi zard funct ionality s hall provi de RPC Ser vice for W izard—An i nternal VS A Web serv ice that t he VSA Wiz ard functi onality wi ll use to interrogat e VistA fo r availabl e RPCs and to retrie ve all the details o f a given RPC to aut omatically generate a Web serv ice operat ion that i nvokes tha t RPC.
	1022	P2.2.2
	1023	2.6.2.127
	1024	The VSA Wi zard shall provide S ervice Cod e Generato r—An inter nal VSA ut ility that parses th e service definition generates the neces sary runti me compone nts and ar tifacts th at will be compiled and combin ed with ot her librar ies into a deployabl e runtime package.
	1025	(Original) The VSA W izard shal l provide Service Co de Generat or—An inte rnal VSA u tility tha t parses t he service definitio n file in XML format and gener ates the n ecessary r untime com ponents an d artifact s that lat er will be compiled and combin ed with ot her librar ies into a deployabl e runtime package by the Servi ce Assembl er.
	1026	Justificat ion for Re vision: Re moved XML and reword ed for cla rity
	1027	P2.3
	1028	2.6.2.128
	1029	The VSA Wi zard funct ionality s ervice ass embler sha ll aggrega te all the runtime c omponents that defin e a servic e.
	1030	P2.3
	1031	2.6.2.129
	1032	The VSA Wi zard funct ionality s ervice ass embler sha ll combine runtime c omponents with other necessary dependenc ies.
	1033	P2.3
	1034	2.6.2.130
	1035	The VSA Wi zard funct ionality s ervice ass embler sha ll produce a deploya ble runtim e package.
	1036	P2.3
	1037	2.6.2.131
	1038	The VSA Wi zard funct ionality s hall provi de a servi ce deploye r for depl oying gene rated serv ice files to the dev elopment p latform.
	1039	P2.3
	1040	2.6.2.132
	1041	The VSA Wi zard funct ionality s hall utili ze a runti me environ ment for t esting fed erated ser vices.
	1042	P2.3
	1043	2.6.2.133
	1044	The VSA Wi zard runti me environ ment shall provide a repositor y for stor ing Servic e Descript or and run time packa ges.
	1045	P2.2.2
	1046	2.6.2.134
	1047	The servic e descript or shall c ontain ser vice defin itions det ailing the service, applicatio n package, operation , expected input par ameters, a nd data ty pes.
	1048	(Original) The servi ce descrip tor XML fi le shall c ontain ser vice defin itions det ailing the service, applicatio n package, operation , expected input par ameters, a nd data ty pes.
	1049	Justificat ion for Re vision: Re moved XML
	1050	P2.2.2
	1051	2.6.2.135
	1052	The Servic e Descript or generat ed by the Wizard sha ll be stor ed on the file syste m of the n on-Product ion runtim e environm ent.
	1053	P2.4
	1054	2.6.2.136
	1055	Create Web Service r untime pac kage: A co py of runt ime compon ent librar ies shall be package d in each deployable Web Servi ce artifac t.
	1056	P2.4
	1057	2.6.2.137
	1058	The VSA Wi zard shall validate a form whe n the user saves a s ervice des criptor to prevent r untime err ors. Manda tory field s shall ha ve a visua l indicato r.
	1059	(Original) The VSA W izard shal l validate an incomp lete form when the u ser saves a service descriptor .
	1060	Justificat ion for Re vision: Re worded for clarity
	1061	P2.2.2
	1062	2.6.2.138
	1063	The VSA Wi zard funct ionality s hall use s tandard an d secure c ommunicati on protoco ls (Hypert ext Transf er Protoco l Secure [ HTTPS]). U sing Gover nment-prov ided PKI c ertificate s.
	1064	(Original) The VSA W izard shal l provide communicat ion to dev elopment V istA insta nces and u se standar d and secu re communi cation pro tocols (Hy pertext Tr ansfer Pro tocol Secu re [HTTPS] ).
	1065	Justificat ion for Re vision: Re worded for clarity
	1066	P2.2.2
	1067	2.6.2.139
	1068	(NEW) The VSA soluti on shall i nclude a W eb-based W izard to e xpose Vist A as SOA s ervices (S OAP and RE ST).
	1069	P2.2.2
	1070	VSA Runtim e Environm ent Compon ents
	1071	Additional VSA funct ionality a s follows:
	1072	Table 5: V SA Runtime Environme nt
	1073	Req. #
	1074	Requiremen t
	1075	Delivery
	1076	2.6.3.300
	1077	The VSA ru ntime envi ronment sh all enable the Wizar d to inter act with o ne develop ment VistA system.
	1078	(Original) The VSA r untime env ironment s hall provi de for the hosting o f the VSA Wizard to enable the Wizard to interact with one d evelopment VistA sys tem.
	1079	Justificat ion for Re vision: Re worded for clarity
	1080	P2.2.2
	1081	2.6.3.301
	1082	The VSA ru ntime envi ronment sh all facili tate the V SA Wizard to store S ervice Des criptor an d runtime packages g enerated b y the VSA Wizard.
	1083	P2.2.2
	1084	2.6.3.302
	1085	The VSA ru ntime envi ronment lo gic shall perform th e routing (federatio n) of quer ies from p rovider an d consumer “service” requests to and fro m VistA.
	1086	P2.2.2
	1087	2.6.3.303
	1088	The VSA ru ntime envi ronment lo gic shall facilitate “run-time ” executio n of gener ated VistA -based Web services.
	1089	P2.2.2
	1090	2.6.3.304
	1091	The VSA Vi stA runtim e environm ent shall provide We b connecti vity to Vi stA as an HTTP to Vi stA MUMPS binding th at conveys ‘service requests’ to one or more VistA systems i n the stan dard and s ecured HTT PS protoco l. Using G overnment- provided P KI certifi cates.
	1092	(Original) The VSA ru ntime envi ronment sh all provid e web conn ectivity t o VistA as an HTTP t o VistA MU MPS bindin g that con veys ‘serv ice reques ts’ to one or more V istA syste ms in the standard a nd secured HTTPS pro tocol.
	1093	Justificat ion for Re vision: Ad ded text r equirement
	1094	P2.2.2
	1095	2.6.3.305
	1096	VSA shall provide a VistA “lis tener,” kn own as the VistA M R outine Cal ling Servi ce (VMRCS) .
	1097	Justificat ion for Re moval: Rem ove, combi ned and sa tisfied by 2.6.3.304 .
	1098	Removed
	1099	2.6.3.306
	1100	VSA shall provide We b based (H TTP) conne ctivity to the VistA functiona lity and d ata such a s RPCs, ro utines, or database access.
	1101	P2.2.2
	1102	2.6.3.307
	1103	The VSA Vi stA “liste ner” (VMRC S) shall b e responsi ble for tr ansferring requests to run M r outines to the VistA M Routine Calling A daptor (VM RCA) and t he legacy M environm ent.
	1104	Justificat ion for Re moval: Rem ove, this is covered by 304 th ru 306 whi ch will be moved to the SDD.
	1105	Removed
	1106	2.6.3.308
	1107	VSA shall provide a VistA M Ro utine Call ing Adapto r (VMRCA) that integ rates the VMRCS comp onent with the tradi tional M c omputing e nvironment and provi des for th e invocati on of M ro utines.
	1108	Justificat ion for Re moval: Rem ove, this is covered by 304 th ru 306 whi ch will be moved to the SDD.
	1109	Removed
	1110	2.6.3.309
	1111	A VSA gene rated serv ice shall contain on e or more operations .
	1112	P2.2.2
	1113	2.6.3.310
	1114	VSA genera ted servic es shall s upport the execution of a sing le RPC or routine AP I.
	1115	P2.2.2
	1116	2.6.3.311
	1117	A single V SA generat ed service shall sup port the s equential execution of multipl e “chained ” RPCs or APIs.
	1118	P2.2.2
	1119	2.6.3.312
	1120	VSA servic es that ex ecute mult iple “chai ned” RPCs or APIs ma y include “stateful” RPCs that rely on t he results of a prec eding RPC in the exe cution seq uence.
	1121	P2.2.2
	1122	2.6.3.313
	1123	VSA shall validate t he presenc e of requi red inform ation in ‘ service re quests’ in cluding us er identit y, input p arameters, federatio n routing, etc.
	1124	P2.2.2
	1125	2.6.3.314
	1126	VSA shall establish VistA back ground inf ormation f or a sessi on consist ent with A SD securit y patterns and organ izationall y establis hed ‘user identity p ropagation ’ guidelin es.
	1127	P2.2.2
	1128	2.6.3.315
	1129	The VSA We b connecti vity to Vi stA shall not allow connection s or accep t ‘service requests’ from any other appl ication or middlewar e, except VSA.
	1130	P2.4
	1131	2.6.3.317
	1132	VSA shall verify tha t all “ser vice reque sts” inclu de user id entity att ributes, t he “consum ing applic ation” ide ntity and routing in formation.
	1133	P2.4
	1134	2.6.3.442
	1135	VSA shall facilitate the loggi ng of ‘ser vice reque st’ transa ctions.
	1136	P2.2.2
	1137	2.6.3.443
	1138	VSA transa ction logg ing data s hall inclu de date/ti me of tran saction, ‘ consuming applicatio n’, servic e invoked and destin ation Vist A systems.
	1139	P2.2.2
	1140	2.6.3.444
	1141	(NEW) The VSA soluti on shall f acilitate sending an d receivin g of an in dustry sta ndard C32 Continuity of Care D ocument (C CD) transa ction betw een VA and external parties.
	1142	HITSP Summ ary Docume nts Using HL7 Contin uity of Ca re Documen t (CCD) Co mponent
	1143	P2.6
	1144	Federation
	1145	The VSA Ru ntime Envi ronment pr ovides for federated routing o f “service requests” to multip le VistA s ystems and the aggre gation of responses returned.
	1146	Table 6: V SA Federat ion Requir ements
	1147	Req. #
	1148	Requiremen t
	1149	Delivery
	1150	2.6.4.318
	1151	The VSA sh all provid e federate d aggregat ion of res ponses fro m provider and consu mer “servi ce” reques ts to Vete rans Healt h Informat ion System s and Tech nology Arc hitecture (VistA).
	1152	P2.2.2
	1153	2.6.4.319
	1154	The VSA Fe derating P latform sh all facili tate feder ated routi ng of quer ies across multiple VistA syst ems and ag gregation of returne d results.
	1155	P2.2.2
	1156	2.6.4.320
	1157	VSA feder ation func tionality shall faci litate rou ting of “s ervice req uests” to a single s pecified V istA syste m.
	1158	P2.2.2
	1159	2.6.4.321
	1160	VSA federa tion funct ionality s hall facil itate rout ing of “se rvice requ ests” to a specified list of V istA syste ms.
	1161	P2.2.2
	1162	2.6.4.322
	1163	VSA federa tion funct ionality s hall facil itate rout ing of “se rvice requ ests” to a ll VistA s ystems.
	1164	P2.2.2
	1165	2.6.4.323
	1166	VSA federa tion funct ionality s hall facil itate rout ing of “se rvice requ ests” to a ll VistA s ystems to which a sp ecified pa tient is k nown (“tre ating faci lities”).
	1167	P2.5
	1168	2.6.4.324
	1169	VSA federa tion funct ionality s hall facil itate rout ing of “se rvice requ ests” to a ll VistA s ystems to which a sp ecified Vi stA user i s known.
	1170	P2.5
	1171	2.6.4.325
	1172	VSA federa ted calls to multipl e VistA sy stems shal l be made asynchrono usly and i n parallel to optimi ze perform ance of re turned res ults.
	1173	P2.2.2
	1174	2.6.4.326
	1175	The result s of VSA f ederated c alls to mu ltiple Vis tA systems shall be aggregated into a si ngle respo nse for re turn to th e “consumi ng applica tion.”
	1176	P2.2.2
	1177	2.6.4.327
	1178	VSA shall use the MV I to deter mine the l ist of “tr eating fac ilities” f or the rou ting of ‘s ervice req uests’ to each VistA system th at has a s pecified p atient on record.
	1179	P2.5
	1180	2.6.4.328
	1181	VSA shall facilitate the retur n of aggre gated “ser vice reque st” respon ses from m ultiple Vi stA system s that are incomplet e due to t ime-out, n on-respons iveness, e tc. of one or more V istA syste ms.
	1182	P2.5
	1183	2.6.4.329
	1184	Aggregated “service request” r esponses f rom multip le VistA s ystems tha t are inco mplete due to time-o ut, non-re sponsivene ss, etc. o f one or m ore VistA systems sh all includ e an excep tion messa ge noting the incomp lete natur e of the r esponse.
	1185	P2.2.2
	1186	2.6.4.330
	1187	Exception messages i ncluded wi th aggrega ted “servi ce request ” response s from mul tiple Vist A systems that inclu de an inco mplete res ponse shal l include a list of VistA syst ems to whi ch the “se rvice requ est” was r outed but from which no respon se was rec eived.
	1188	P2.2.2
	1189	2.6.4.331
	1190	With the e xception o f federati on (e.g., MVI, etc.) , all busi ness logic that is t he basis f or VSA gen erated ser vices shal l be in th e VistA M environmen t in the f orm of RPC s or APIs.
	1191	P2.2.2
	1192	2.6.4.332
	1193	The core l ogic for V SA utiliti es shall b e packaged and distr ibuted sep arately fr om service -specific business l ogic (e.g. , RPCs).
	1194	P2.2.2
	1195	2.6.4.333
	1196	Stability of the cor e logic fo r VSA util ities shal l be maint ained by k eeping VSA core logi c generic and non-se rvice-spec ific.
	1197	P2.2.2
	1198	2.6.4.334
	1199	(NEW) The VSA soluti on shall p rovide a s ervices Fe deration c apability that provi des access to Enterp rise entit ies includ ing:
	1200	Instances of VistA,
	1201	Medication Image Lib rary (MIL) ,
	1202	Master Vet eran Index (MVI)
	1203	P2.6
	1204	2.6.4.335
	1205	(NEW) The VSA soluti on shall e nsure acce ss to Ente rprise ent ities is f ederated t hrough a d ynamic, da ta-driven, configura ble scopin g mechanis m that all ows system administr ators to c ontrol run time routi ng in prod uction. A specific e xample of this is th e integrat ion of a S OAP servic e.
	1206	P2.6
	1207	Pre/Post L ogic Proce ssing
	1208	VSA provid es the abi lity to ex tend the b ehavior of VSA-gener ated servi ces throug h the conf iguration of “pre” a nd “post” processing logic. Th e followin g describe s the proc ess flow:
	1209	“Consuming applicati on” obtain s a user i dentity SA ML token f rom IAM.
	1210	“Consuming applicati on” sends “service r equest” (i ncluding S AML token) to eMI.
	1211	eMI authen ticates th e “consumi ng applica tion,” aut horizes ex ecution of a specifi c service, validates the SAML token.
	1212	eMI routes ‘service request’ t o VSA.
	1213	VSA (optio nally) inv okes “Pre” logic in the eMI en vironment.
	1214	VSA uses V istA logic to establ ish VistA background represent ing the us er.
	1215	VSA (optio nally) inv okes “Pre” logic in the VistA M environm ent.
	1216	VSA invoke s VistA RP C.
	1217	VistA RPC returns re sult to VS A.
	1218	VSA (optio nally) inv okes “Post ” logic in the VistA M environ ment.
	1219	VSA (optio nally) inv okes “Post ” logic in the eMI e nvironment .
	1220	VSA return s the “ser vice respo nse” to th e eMI.
	1221	eMI return s “service response” to the “c onsuming a pplication ”.
	1222	Figure 1 d epicts the process f low:
	1223
	1224	Figure 1: VSA “Pre/P ost” Logic Model
	1225	Table 7: V SA Pre/Pos t Logic Pr ocessing R equirement s
	1226	Req. #
	1227	Requiremen t
	1228	Delivery
	1229	2.6.5.335
	1230	VSA shall facilitate the proce ssing of “ Pre” actio ns that pr ecede the execution of the ser vice busin ess logic (RPC or AP I).
	1231	P2.2.2
	1232	2.6.5.336
	1233	VSA shall facilitate the proce ssing of “ Post” acti ons that f ollow the execution of the ser vice busin ess logic (RPC or AP I).
	1234	P2.2.2
	1235	2.6.5.337
	1236	VSA shall facilitate “Pre” and “Post” ac tions that allow the execution of other SOA servic es.
	1237	P2.2.2
	1238	2.6.5.338
	1239	VSA shall facilitate “Pre” and “Post” ac tions that allow the execution of other VistA logi c.
	1240	P2.2.2
	1241	2.6.5.339
	1242	The core l ogic for V SA utiliti es shall n ot contain “Pre/Post ” logic el ements.
	1243	P2.2.2
	1244	2.6.5.340
	1245	The core l ogic for V SA utiliti es shall b e packaged and distr ibuted sep arately fr om “Pre/Po st” logic elements.
	1246	P2.2.2
	1247	2.6.5.341
	1248	VSA “Pre/P ost” proce ssing shal l allow th e executio n of servi ces and/or M logic c reated by other sour ces (e.g., “open sou rce”).
	1249	P2.2.2
	1250	2.6.5.342
	1251	VSA “Pre/P ost” actio n processi ng shall f acilitate the follow ing ‘to be ’ process flow:
	1252	“Consuming applicati on” obtain s a user i dentity SA ML token f rom IAM.
	1253	“Consuming applicati on” sends “service r equest” (i ncluding S AML token) to eMI.
	1254	eMI authen ticates th e “consumi ng applica tion,” aut horizes ex ecution of a specifi c service, validates the SAML token.
	1255	eMI routes ‘service request’ t o VSA.
	1256	VSA (optio nally) inv okes “Pre” logic in the eMI en vironment.
	1257	VSA uses V istA logic to establ ish VistA background represent ing the us er.
	1258	VSA (optio nally) inv okes “Pre” logic in the VistA M environm ent.
	1259	VSA invoke s VistA RP C.
	1260	VistA RPC returns re sult to VS A.
	1261	VSA (optio nally) inv okes “Post ” logic in the VistA M environ ment.
	1262	VSA (optio nally) inv okes “Post ” logic in the eMI e nvironment .
	1263	VSA return s the “ser vice respo nse” to th e eMI.
	1264	eMI return s “service response” to the “c onsuming a pplication .”
	1265	P2.6
	1266	Exception and Error Handling
	1267	VSA provid es standar dized exce ption and error hand ling.
	1268	Table 8: V SA Excepti on and Err or Handlin g Requirem ents
	1269	Req. #
	1270	Requiremen t
	1271	Delivery
	1272	2.6.6.343
	1273	If require d informat ion is not present i n a “servi ce request ”, VSA sha ll refuse the reques t and retu rn an erro r response as indica ted.
	1274	P2.2.2
	1275	2.6.6.344
	1276	VSA shall implement standardiz ed VSA err or codes b ased on ES S SOA Desi gn Guideli nes and st andards.
	1277	P2.4
	1278	2.6.6.345
	1279	VSA shall return sta ndard HTTP error cod es as rela ted to Rep resentatio nal State Transfer ( REST) serv ices.
	1280	P2.2.2
	1281	2.6.6.346
	1282	VSA shall return Vis tA error i nformation when exce ptions occ ur in that environme nt.
	1283	P2.2.2
	1284	Architectu ral Princi ples
	1285	VSA provid es utiliti es for the auto-gene ration of VistA-base d services and the i ntegration of extern al systems with Vist A.
	1286	Table 9: V SA Archite ctural Pri nciples Re quirements
	1287	Req. #
	1288	Requiremen t
	1289	Delivery
	1290	2.6.7.347
	1291	VSA shall be fully c ompliant w ith guidel ines and s tandards a s establis hed by VA Enterprise Architect ure and Ar chitecture , Strategy and Desig n (ASD).
	1292	P2.2.2
	1293	2.6.7.348
	1294	All compon ents and t echnologie s of the V SA product shall be compliant with the V A Enterpri se Archite cture Tech nical Refe rence Mode l (TRM).
	1295	P2.2.2
	1296	2.6.7.350
	1297	The VSA so lution sha ll comply with estab lished VA standards and conven tions for software d evelopment .
	1298	P2.2.2
	1299	2.6.7.351
	1300	VSA shall strictly i mplement r elevant ar chitectura l design p atterns as establish ed by ASD, including those rel ated to SO A security and “user identity propagatio n.”
	1301	P2.2.2
	1302	2.6.7.352
	1303	VSA shall provide ge neric util ities whic h support the creati on of Vist A based se rvices whi ch are con sumable by all ‘cons uming appl ications’ in the SOA services environmen t.
	1304	P2.2.2
	1305	2.6.7.353
	1306	VSA genera ted Web se rvices sha ll be cons umable fro m the Ente rprise Mes saging Inf rastructur e (eMI) in a technol ogy agnost ic manner.
	1307	P2.3
	1308	2.6.7.354
	1309	VSA shall support th e creation of author itative, n on-redunda nt VistA b ased servi ces.
	1310	P2.2.2
	1311	2.6.7.355
	1312	VSA utilit ies shall not contai n or repli cate busin ess logic that exist s in VistA applicati ons.
	1313	P2.2.2
	1314	2.6.7.356
	1315	All VSA ge nerated se rvices sha ll be defi ned/expose d on the E nterprise Messaging Infrastruc ture (eMI) .
	1316	P2.3
	1317	2.6.7.357
	1318	VSA servic es shall b e fully do cumented i n the eMI Service Re gistry.
	1319	P2.6
	1320	2.6.7.358
	1321	VSA shall implement technology that leve rages ‘ope n source’ compatibil ity.
	1322	P2.2.2
	1323	2.6.7.359
	1324	(NEW) The VSA soluti on shall b e SMART-co mpliant (S ubstitutab le Medical Applicati ons, Reusa ble Techno logies Pla tform), bo th as a co nsumer and a produce r of FHIR- based Web services ( Fast Healt hcare Inte roperabili ty Resourc es).
	1325	SMART Heal th IT Tech nology Pla tform
	1326	P2.5
	1327	2.6.7.360
	1328	(NEW) The VSA soluti on shall s upport use of struct ured FHIR data to co ordinate i nteraction s between mobile and connected devices.
	1329	P2.6
	1330	2.6.7.361
	1331	(NEW) The VSA soluti on shall s upport VA alignment with HL7 F HIR standa rd policie s.
	1332	P2.6
	1333	2.6.7.362
	1334	(NEW) The solution s hall be de signed to synchroniz e with oth er Enterpr ise servic e registri es, to inc lude six V ISN Regist ries and t he Enterpr ise Regist ry, to inc lude use o f the Ente rprise Mes saging Inf rastructur e (eMI).
	1335	P2.6
	1336	Supporting geographi cally dist ributed VA System To pology
	1337	The VSA Ru ntime Envi ronment (F ederating platforms connecting VistA sys tems with eMI/SOA) w ill suppor t geograph ically dis tributed V A system t opology. T his includ es infrast ructure th roughout C ontinental United St ates (CONU S), includ ing Enterp rise and R egional Da ta Process ing Center s.
	1338	Table 10: VSA System Topology Requiremen ts
	1339	Req. #
	1340	Requiremen t
	1341	Delivery
	1342	2.6.8.359
	1343	VSA shall facilitate deploymen t of the V SA Federat ing Platfo rm to acco mmodate th e geograph ically dis tributed V A system t opology (i nfrastruct ure/server s).
	1344	(Original) VSA shall implement system to pology (se rvers) tha t facilita te deploym ent of the VSA Feder ating Plat form.
	1345	Justificat ion for Re vision: Re worded for clarity
	1346	P2.2.2
	1347	2.6.8.359. 1
	1348	VSA shall implement system top ology (ser vers) that facilitat e deployme nt of the VSA Federa ting Platf orm (decen tralized a t the Remo te Data Pr ocessing C enters [RD PCs]).
	1349	P2.6
	1350	2.6.8.360
	1351	VSA shall rely on VA eMI to au thenticate the ‘cons uming appl ication’, consumptio n of speci fic servic es and val idated via the VA IA M SAML tok en--and sh all not au thenticate or valida te ‘consum ing applic ation’ con sumption o f services
	1352	(Original) VSA shall rely on t he ESB to have authe nticated t he ‘consum ing applic ation’, au thorized t he consump tion of sp ecific ser vices and validated the IAM SA ML token-- and shall not perfor m these ac tivities i ndependent ly or redu ndantly.
	1353	Justificat ion for Re vision: Re worded for clarity
	1354	P2.5
	1355	2.6.8.361
	1356	VSA shall be integra ted with t he Enterpr ise Messag ing Interf ace (eMI) consistent with ASD design pat terns.
	1357	P2.4
	1358	2.6.8.362
	1359	VSA shall rely on th e eMI excl usively to accept “s ervice req uests” fro m ‘externa l applicat ions’ and shall not accept “se rvice requ ests” dire ctly.
	1360	(Original) VSA shall not accep t “service requests” directly from exter nal applic ations—exc ept as com municated through th e ESB.
	1361	Justificat ion for Re vision: Re worded for clarity
	1362	P2.6
	1363	2.6.8.363
	1364	VSA shall coordinate with SDE to identif y specific ations for initial s erver impl ementation .
	1365	P2.4
	1366	2.6.8.364
	1367	VSA shall coordinate with SDE to determi ne optimal server sp ecificatio ns for the “to be” i mplementat ion based on impleme ntation an d testing of the ini tial imple mentation.
	1368	(Original) Informati on gathere d as a res ult of imp lementatio n and test ing of the “initial” implement ation shal l be used to determi ne optimal server sp ecificatio ns for the “to be” i mplementat ion.
	1369	Justificat ion for Re vision: Re worded for clarity
	1370	P2.6
	1371	2.6.8.365
	1372	VSA server s shall co mply with National I nstitute o f Standard s and Tech nology (NI ST) and Fe deral Desk top Core C onfigurati on (FDCC) guidelines regarding build-out s and secu rity setti ngs.
	1373	P2.2.2
	1374	2.6.8.366
	1375	Servers sh all use st andard pro tocols and ports for communica tion and n etwork set tings.
	1376	P2.2.2
	1377	2.6.8.367
	1378	VSA system s shall co mply with VA Directi ve 6102 re lative to VA Interne t and Intr anet stand ards for s ystems ope ration.
	1379	P2.2.2
	1380	2.6.8.368
	1381	VSA shall implement an “initia l implemen tation” th at facilit ates rapid early dep loyment to productio n in the g eographica lly distri buted VA s ystem topo logy (infr astructure /servers).
	1382	(Original) VSA shall implement an interi m topology that faci litates ra pid early deployment to produc tion.
	1383	Justificat ion for Re vision: Re worded for clarity
	1384	P2.3
	1385	2.6.8.369
	1386	The VSA “i nitial imp lementatio n” shall s upport sep arate envi ronments f or develop ment in th e geograph ically dis tributed V A system t opology (i nfrastruct ure/server s).
	1387	(Original) The VSA “ initial im plementati on” topolo gy shall p rovide sep arate envi ronments f or develop ment.
	1388	Justificat ion for Re vision: Re worded for clarity
	1389	P2.3
	1390	2.6.8.370
	1391	The VSA “i nitial imp lementatio n” shall s upport sep arate envi ronments f or integra tion testi ng in the geographic ally distr ibuted VA system top ology (inf rastructur e/servers) .
	1392	(Original) The VSA “ initial im plementati on” topolo gy shall p rovide sep arate envi ronments f or integra tion testi ng.
	1393	Justificat ion for Re vision: Re worded for clarity
	1394	P2.3
	1395	2.6.8.371
	1396	The VSA “i nitial imp lementatio n” shall s upport sep arate envi ronments f or user fu nctional a nd accepta nce testin g by SQA i n the geog raphically distribut ed VA syst em topolog y (infrast ructure/se rvers).
	1397	(Original) The VSA “ initial im plementati on” topolo gy shall p rovide sep arate envi ronments f or user fu nctional a nd accepta nce testin g.
	1398	Justificat ion for Re vision: Re worded for clarity
	1399	P2.3
	1400	2.6.8.372
	1401	The VSA “i nitial imp lementatio n” shall s upport sep arate envi ronments f or SQA tes ting in th e geograph ically dis tributed V A system t opology (i nfrastruct ure/server s).
	1402	Justificat ion for re moval: Add ressed by 2.6.8.371
	1403	Removed
	1404	2.6.8.373
	1405	The VSA “i nitial imp lementatio n” shall s upport sep arate envi ronments f or capacit y/load/per formance t esting by VA ETS in the geogra phically d istributed VA system topology (infrastru cture/serv ers).
	1406	(Original) The VSA “ initial im plementati on” topolo gy shall p rovide sep arate envi ronments f or capacit y/load/per formance t esting
	1407	Justificat ion for Re vision: Re worded for clarity
	1408	P2.2.2
	1409	2.6.8.374
	1410	The VSA “i nitial imp lementatio n” shall s upport sep arate envi ronments f or securit y testing by VA OIS in the geo graphicall y distribu ted VA sys tem topolo gy (infras tructure/s ervers).
	1411	(Original) The VSA “i nitial imp lementatio n” topolog y shall pr ovide sepa rate envir onments fo r security testing.
	1412	Justificat ion for Re vision: Re worded for clarity
	1413	P2.2.2
	1414	2.6.8.375
	1415	The VSA “i nitial imp lementatio n” shall s upport sep arate envi ronments f or pre-pro duction in the geogr aphically distribute d VA syste m topology (infrastr ucture/ser vers).
	1416
	1417	(Original) The VSA “ initial im plementati on” topolo gy shall p rovide sep arate envi ronments f or pre-pro duction.
	1418
	1419	Justificat ion for Re vision: Re worded for clarity
	1420	P2.3
	1421	2.6.8.376
	1422	The VSA “i nitial imp lementatio n” shall s upport sep arate envi ronments f or product ion in the geographi cally dist ributed VA system to pology (in frastructu re/servers ).
	1423	(Original) The VSA “ initial im plementati on” topolo gy shall p rovide sep arate envi ronments f or product ion.
	1424	Justificat ion for Re vision: Re worded for clarity
	1425	P2.3
	1426	2.6.8.377
	1427	The VSA “i nitial imp lementatio n” shall p rovide mul tiple inst ances of t he VSA Fed erating Pl atform to facilitate developme nt of fede rated ‘ser vice reque st’ routin g function ality in t he geograp hically di stributed VA system topology ( infrastruc ture/serve rs).
	1428	(Original) The VSA “ initial im plementati on” topolo gy shall p rovide mul tiple inst ances of t he VSA Fed erating Pl atform to facilitate developme nt of fede rated ‘ser vice reque st’ routin g function ality.
	1429	Justificat ion for Re vision: Re worded for clarity
	1430	P2.3
	1431	2.6.8.378
	1432	The VSA “i nitial imp lementatio n’ shall s upport net work commu nications with other SOA compo nents (e.g ., eMI, Vi stA system s, etc.).
	1433	(Original) The VSA “ initial im plementati on’ topolo gy shall f acilitate network co nnectivity with othe r SOA comp onents (e. g., ESB, V istA syste ms, etc.).
	1434	Justificat ion for Re vision: Re worded for clarity
	1435	P2.3
	1436	2.6.8.379
	1437	The VSA “i nitial imp lementatio n” topolog y shall pr ovide mult iple insta nces of th e VSA Fede rating Pla tform to s upport dev elopment o f federati on and fai l-over log ic in the geographic ally distr ibuted VA system top ology (inf rastructur e/servers) .
	1438	(Original) The VSA “ initial im plementati on” topolo gy shall p rovide mul tiple inst ances of t he VSA Fed erating Pl atform to support de velopment of federat ion and fa il-over lo gic.
	1439	Justificat ion for Re vision: Ad ded text r equirement for clari ty
	1440	P2.3
	1441	2.6.8.380
	1442	Testing re sults and “lessons l earned” fr om the VSA ‘initial implementa tion’ topo logy shall be used t o document recommend ed optimal specifica tions and topology f or the VSA ‘to be’ i mplementat ion.
	1443	Justificat ion for Re moval: Add ressed in 2.6.8.364
	1444	Removed
	1445	2.6.8.381
	1446	VSA shall support mu ltiple ins tances of the VSA Fe derating P latform to support “ to be” dep loyment of VSA syste ms to RDPC s or AITCs as indica ted by VA system spe cification for the ‘ to be’ imp lementatio n.
	1447	(Original) VSA shall implement multiple instances of the VSA Federatin g Platform to suppor t “to be” deployment of VSA sy stems to R DPCs or IT Cs as indi cated by d etermined system spe cification for the ‘ to be’ imp lementatio n.
	1448	Justificat ion for Re vision: Re worded for clarity
	1449	P2.2.2
	1450	2.6.8.382
	1451	VSA shall coordinate with SDE to determi ne optimal “to be” t opology fo r system s ecurity, r eliability and perfo rmance.
	1452	(Original) VSA shall implement “to be” t opology th at optimiz es system security, reliabilit y and perf ormance.
	1453	Justificat ion for Re vision: Re worded for clarity
	1454	P2.2.2
	1455	2.6.8.383
	1456	VSA shall coordinate with SDE to finaliz e “to be” implementa tion syste m specific ations for the “to b e” impleme ntation ba sed on “in itial impl ementation ” testing results an d “lessons learned.”
	1457	(Original) VSA shall finalize “to be” im plementati on system specificat ions based on VSA ‘i nitial imp lementatio n’ testing results a nd “lesson s learned. ”
	1458	Justificat ion for Re vision: Re worded for clarity
	1459	P2.2.2
	1460	2.6.8.384
	1461	VSA shall coordinate with SDE to determi ne final “ to be” imp lementatio n topology based on “initial i mplementat ion” testi ng results and “less ons learne d.”
	1462	(Original) VSA shall finalize “to be” im plementati on topolog y based on VSA ‘init ial implem entation’ testing re sults and “lessons l earned.”
	1463	Justificat ion for Re vision: Re worded for clarity
	1464	P2.2.2
	1465	2.6.8.385
	1466	VSA shall be designe d to facil itate “sca le up” or “scale out ” to accom modate exp anding usa ge, capaci ty and per formance n eeds.
	1467	(Original) VSA syste m and topo logy shall be design ed to faci litate “sc ale up” or “scale ou t” to acco mmodate ex panding us age, capac ity and pe rformance needs.
	1468	Justificat ion for Re vision: Re worded for clarity
	1469	P2.5
	1470	Non-Functi onal Requi rements
	1471	Table 11: VSA Non-Fu nctional R equirement s
	1472	Req. #
	1473	Requiremen t
	1474	Delivery
	1475	2.6.9.386
	1476	The contra ctor shall use VA-ap proved sou rce contro l utilitie s and tech niques for the stora ge and man agement of all VSA a rtifacts a nd deliver ables.
	1477	(Original) VSA shall use sourc e control utilities and techni ques for t he storage and manag ement of a ll VSA art ifacts and deliverab les.
	1478	Justificat ion for Re vision: Re worded for clarity
	1479	P2.2.2
	1480	2.6.9.387
	1481	VSA delive rables sha ll be desi gned in th e context of VA Ente rprise Sha red Servic es (ESS) F amily of S ervices/In itiative M anagement (FoSIM) so lution and service p lanning ac tivities t o ensure a rchitectur al models are consis tent.
	1482	(Original) VSA utili ties shall be design ed and mod eled using a web-bas ed, multi- tier archi tecture.
	1483	Justificat ion for Re vision: Re worded for clarity
	1484	P2.2.2
	1485	2.6.9.388
	1486	Architectu rally sign ificant el ements (de aling with scalabili ty, stabil ity, flexi bility, in teroperabi lity, etc. ) shall be designed in the Uni fied Model ing Langua ge (UML).
	1487	P2.2.2
	1488	2.6.9.389
	1489	Software e lements th at will ex ist outsid e of the l egacy Vist A environm ent shall be develop ed using V A Enterpri se Archite cture desi gn pattern s and meth ods.
	1490	(Original) Software elements t hat will e xist outsi de of the legacy Vis tA environ ment shall be develo ped using Object-Ori ented (OO) technolog ies.
	1491	Justificat ion for Re vision: Re worded for clarity
	1492	P2.2.2
	1493	2.6.9.390
	1494	An object- oriented a nalysis ap proach sha ll be used to map th e problem domain int o an exten sible obje ct model.
	1495	P2.2.2
	1496	2.6.9.391
	1497	A traceabi lity matri x shall be defined w hich maps relationsh ips betwee n BRD requ irements, RSD requir ements, SD D design e lements an d test scr ipts.
	1498	P2.2.2
	1499	2.6.9.392
	1500	User inter face chara cteristics shall be designed f or optimal usability .
	1501	Justificat ion for Re moval: Add ressed by 2.6.9.434
	1502	Removed
	1503	2.6.9.393
	1504	VSA docume ntation sh all includ e the foll owing VA O ffice of G eneral Cou nsel (OGC) disclaime r:
	1505	“This soft ware was d eveloped a t the Depa rtment of Veterans A ffairs (VA ) by emplo yees of th e Federal Government in the co urse of th eir offici al duties. Pursuant to title 1 7 Section 105 of the United St ates Code this softw are is not subject t o copyrigh t protecti on and is in the pub lic domain . VA assum es no resp onsibility whatsoeve r for its use by oth er parties , and make s no guara ntees, exp ressed or implied, a bout its q uality, re liability, or any ot her charac teristic. We would a ppreciate acknowledg ement if t he softwar e is used. This soft ware can b e redistri buted and/ or modifie d freely p rovided th at any der ivative wo rks bear s ome notice that they are deriv ed from it , and any modified v ersions be ar some no tice that they have been modif ied.”
	1506	P2.2.2
	1507	2.6.9.433
	1508	The Wizard functiona lity GUI i nterface s hall compl y with all Section 5 08 legal a nd organiz ational ex pectations .
	1509	P2.5
	1510	2.6.9.434
	1511	The contra ctor will provide ce rtificatio n to the S ection 508 Office th at contrac ted delive rables mee t Section 508 requir ements.
	1512	(Original) The VSA p roject tea m will pro vide certi fication t o the Sect ion 508 Of fice that the VSA pr oduct meet s all Sect ion 508 re quirements .
	1513	Justificat ion for Re vision: Re worded for clarity
	1514	P2.5
	1515	2.6.9.435
	1516	VSA shall comply wit h VA Web d evelopment standards .
	1517	P2.2.2
	1518	Capacity, Load, and Performanc e
	1519	Table 12: VSA Capaci ty-Load an d Performa nce Requir ements
	1520	Req. #
	1521	Requiremen t
	1522	Delivery
	1523	2.6.10.394
	1524	The VSA “r un time” f unctionali ty shall p rovide sub -second re sponse tim e consiste nt with En terprise-l evel capac ity and pe rformance for critic al busines s applicat ions.
	1525	P2.4
	1526	2.6.10.395
	1527	The VSA “d esign time ” function ality shal l provide response t ime consis tent with software d evelopment utility u ser expect ations.
	1528	(Original) The VSA “ design tim e” functio nality sha ll provide sub-secon d response time cons istent wit h software developme nt utility user expe ctations.
	1529	Justificat ion for Re vision: Re worded for clarity
	1530	P2.2.2
	1531	2.6.10.396
	1532	VSA capaci ty shall s upport tho usands of consumer i nitiated c onnections received via the ES B.
	1533	Justificat ion for Re moval: Add ressed by 3.6.10.398 .
	1534	Removed
	1535	2.6.10.397
	1536	VSA load s hall suppo rt million s of consu mer initia ted transa ctions (“s ervice req uests”) re ceived via the ESB f rom thousa nds of con current us ers.
	1537	Justificat ion for Re moval: Add ressed by 3.6.10.398
	1538	Removed
	1539	2.6.10.398
	1540	VSA shall support lo ads and pe ak utiliza tion perio ds similar to CPRS a nd Medical Domain We b Services (MDWS).
	1541	P2.5
	1542	2.6.10.399
	1543	VSA shall support mu ltiple con current co nnections and thousa nds of con current us ers.
	1544	Justificat ion for Re moval: Add ressed by 3.6.10.398 .
	1545	Removed
	1546	2.6.10.400
	1547	VSA shall accommodat e transact ion sizes commensura te to the limitation s of the e MI.
	1548	P2.6
	1549	2.6.10.401
	1550	Failure ra te of comp onent syst ems shall be less th an 10% in a rolling 12 month p eriod for VSA Federa ting Platf orms.
	1551	Justificat ion for Re moval: Add ressed by 2.6.10.402 .
	1552	Removed
	1553	2.6.10.402
	1554	VSA compon ents shall provide f ull operat ional capa city 99.99 % of the t ime, 24/7/ 365.
	1555	P2.4
	1556	2.6.10.403
	1557	VSA contra ctor shall support G overnment capacity, load and p erformance testing e ffort.
	1558	(Original) VSA shall execute c apacity, l oad and pe rformance testing.
	1559	Justificat ion for Re vision: Te xt change for greate r clarity of roles.
	1560	P2.6
	1561	2.6.10.404
	1562	VSA shall support in dependent capacity, load and p erformance testing.
	1563	P2.2.2
	1564	2.6.10.405
	1565	VSA capaci ty, load a nd perform ance testi ng shall e valuate th e full SOA stack (fr om the “co nsuming ap plication” to VistA and back).
	1566	Justificat ion for Re moval: Add ressed by 2.6.10.404 .
	1567	Removed
	1568	2.6.10.406
	1569	VSA capaci ty, load a nd perform ance testi ng shall m easure and evaluate the latenc y of each applicatio n componen t and netw ork segmen t the full VSA suppo rted SOA s tack.
	1570	Justificat ion for Re moval: Add ressed by 2.6.10.404 .
	1571	Removed
	1572	2.6.10.407
	1573	VSA capaci ty, load a nd perform ance testi ng environ ments shal l support evaluation of SOA st ack compon ent distri bution acr oss the ne twork (Wid e Area Net work [WAN] ).
	1574	Justificat ion for Re moval: Add ressed by 2.6.10.404 .
	1575	Removed
	1576	2.6.10.408
	1577	Testing pe rformed in the VSA i nterim top ology shal l be used to determi ne/modify/ validate t he optimal topology for the VS A “to be” implementa tion.
	1578	P2.4
	1579	2.6.10.409
	1580	VSA will u se standar d VA monit oring tool s or real- time monit oring and on-demand evaluation of system performan ce during normal ope ration or when techn ical issue s/problems occur tha t may requ ire a reme diation.
	1581	(Original) VSA shall provide a system ad ministrati on user in terface fo r real-tim e monitori ng and on- demand eva luation of system pe rformance during nor mal operat ion or whe n technica l issues/p roblems oc cur that m ay require a remedia tion.
	1582	Justificat ion for Re vision: Re worded for clarity a nd focus o n leveragi ng/reuse o f current monitoring approach.
	1583	P2.3
	1584	2.6.10.410
	1585	(NEW) The VSA soluti on shall a llow the n umber of e xternal ap plications accessing VistA to scale up b ased on Vi stA system licensing limitatio ns.
	1586	P2.6
	1587	Security
	1588	Table 13: VSA Securi ty Require ments
	1589	Req. #
	1590	Requiremen t
	1591	Delivery
	1592	2.6.11.409
	1593	The VSA so lution sha ll comply with VA 65 00 and rel ated secur ity progra m requirem ents.
	1594	(Original) The VSA s olution sh all comply with all organizati onally est ablished s ecurity, p rivacy, an d confiden tiality cr iteria rel ated to se nsitive da ta and bus iness proc esses.
	1595	Justificat ion for Re vision: Re worded for clarity
	1596	P2.2.2
	1597	2.6.11.410
	1598	No Persona lly Identi fiable Inf ormation ( PII) or Pe rsonal Hea lth Identi fiers (PHI ) shall be stored Vi stA SOA Se rvices Pla tform util ity compon ents.
	1599	(Original) No Person ally Ident ifiable In formation (PII) or P ersonal He alth Ident ifiers (PH I) shall b e stored V SA infrast ructure ut ility comp onents.
	1600	Justificat ion for Re vision: Re worded for clarity
	1601	P2.2.2
	1602	2.6.11.411
	1603	The intern al connect ivity and communicat ions of th e VSA plat forms shal l be encry pted and e xclusive t o VSA, eMI , and its specific V istA syste m(s) where ver VSA wi ll be inst alled.
	1604	(Original) Two-way S ecure Sock et Layer ( SSL) conne ctivity sh all be imp lemented b etween the VSA VistA “listener ” (VMRCS) and the VS A Federati ng Platfor m to provi de a priva te service that can only be co nsumed/con nected to by the VSA Federatin g Platform .
	1605	Justificat ion for Re vision: VM RCS portio n was remo ved, is im plementati on specifi c. Retain & re-word to preserv e the inte nt (privat e consumpt ion of VSA services) .
	1606	P2.2.2
	1607	2.6.11.412
	1608	Secure Soc ket Layer (SSL/TLS) authentica tion shall be implem ented betw een the VS A Federati ng Platfor m and the eMI to pro vide a tru sted conne ction that can only be used by the VSA F ederating Platform a nd the eMI .
	1609	P2.6
	1610	2.6.11.413
	1611	VSA networ k connecti vity from the eMI to VSA shall employ SS L/TLS to i mplement p ayload enc ryption an d authenti cation of both clien t and serv er systems .
	1612	P2.2.2
	1613	2.6.11.414
	1614	VSA networ k connecti vity from VSA VistA systems sh all employ SSL/TLS t o implemen t payload encryption and authe ntication of both VS A and Vist A systems.
	1615	P2.2.2
	1616	2.6.11.430
	1617	VSA shall support Go vernment s ecurity ev aluation/t esting of deliverabl es.
	1618	(Original) VSA shall engage in dependent security e valuation/ testing of VSA compo nents.
	1619	Justificat ion for Re vision: Re worded for clarity
	1620	P2.2.2
	1621	2.6.11.431
	1622	VSA shall engage ind ependent s ecurity ev aluation/t esting of the VSA su pported SO A stack.
	1623	Justificat ion for Re moval: Add ressed by 2.6.10.409
	1624	Removed
	1625	2.6.11.432
	1626	VSA shall provide a suitable s ecurity te sting envi ronment fo r independ ent evalua tion/testi ng of VSA components and the S OA stack.
	1627	Justificat ion for Re moval: Add ressed by 2.6.10.430
	1628	Removed
	1629	User Ident ity Propag ation
	1630	VSA provid es the abi lity to co mmunicate informatio n necessar y to ensur e user ide ntity prop agation ac ross archi tectural t iers.
	1631	Table 14: VSA User I dentity Pr opagation Requiremen ts
	1632	Req. #
	1633	Requiremen t
	1634	Delivery
	1635	2.6.12.415
	1636	The VSA so lution sha ll comply with VA 65 00 and rel ated secur ity progra m requirem ents to en sure that User ident ity Inform ation is p ropagated across all the layer s in the s olution us ing VA app roved solu tions such as the IA M STS SAML token or M4A.
	1637	(Original ) VSA shal l implemen t function ality that supports user ident ity propag ation acro ss all arc hitectural tiers of the SOA st ack--from the “consu ming appli cation” to the “serv ice provid er” (VistA ).
	1638	Justificat ion for Re vision: Up date provi ded by VA.
	1639	P2.3
	1640	2.6.12.416
	1641	The VSA sh all accomm odate the communicat ion of “co nsuming ap plication” user iden tity in th e form of the “inter im approac h” minimum four attr ibutes (M4 A).
	1642	P2.4
	1643	2.6.12.417
	1644	M4A elemen ts shall i nclude Sub ject Organ ization, S ubject Org anization ID, Unique User ID a nd Subject ID.
	1645	P2.4
	1646	2.6.12.418
	1647	For “inter im approac h” service requests, VSA shall accept an “Authoriz ation” HTT P header w ith the mi nimum four attribute s (M4A). F or example :
	1648	Authorizat ion: VistA id {“subje ct name“:“ One Xuuser ,”subject unique ID” :“728”,“or ganization name“:“Sa n Francisc o VAMC”,“o rganizatio n unique I D”:“662”}.
	1649	P2.4
	1650	2.6.12.419
	1651	For “servi ce request s” from “c onsuming a pplication s” that ha ve integra ted with I AM user au thenticati on, VSA sh all accept ‘service requests’ that inclu de the IAM SAML toke n.
	1652	P2.3
	1653	2.6.12.420
	1654	For SOAP s ervices, V SA shall a ccept the SAML token in WS-Sec urity SOAP header.
	1655	P2.4
	1656	2.6.12.421
	1657	For REST s ervices, V SA shall a ccept an “ Authorizat ion” HTTP header wit h a SAML t oken in ac cordance w ith RFC 26 17. For ex ample:
	1658	Authorizat ion: <trus t:TokenTyp e>http://d ocs.oasis- open.org/w ss/oasis-w ss-saml-to ken-profil e-1.1#SAML V2.0</trus t:TokenTyp e> -<trust :Requested SecurityTo ken>… …</t rust:Reque stedSecuri tyToken>
	1659
	1660	(Original) For REST services, VSA shall accept an “Authoriza tion” HTTP header wi th a SAML token. For example:
	1661	Authorizat ion: <trus t:TokenTyp e>http://d ocs.oasis- open.org/w ss/oasis-w ss-saml-to ken-profil e-1.1#SAML V2.0</trus t:TokenTyp e> -<trust :Requested SecurityTo ken>… …</t rust:Reque stedSecuri tyToken>
	1662
	1663	Justificat ion for Re vision: Ad ded text f or clarity
	1664	P2.4
	1665	2.6.12.422
	1666	The VSA sh all accomm odate the communicat ion of “co nsuming ap plication” user iden tity in th e form of the IAM ‘t o be’ solu tion SAML token.
	1667	P2.4
	1668	2.6.12.423
	1669	VSA shall not honor or process “service requests” that do no t contain user ident ity attrib utes in th e form of the IAM SA ML token o r M4A.
	1670	P2.4
	1671	2.6.12.424
	1672	An error r esponse sh all be ret urned to t he “consum ing applic ation” rel ative to “ service re quests” th at have be en rejecte d due to m issing or incomplete user iden tity attri butes.
	1673	P2.2.2
	1674	2.6.12.425
	1675	VSA functi onality sh all facili tate the p rocessing of either the SAML t oken or th e “interim approach” M4A attri butes (bot h variatio ns) to all ow organiz ational tr ansition t o the IAM “to be” so lution wit hout requi ring revis ion of VSA logic or custom con figuration relative to “consum ing applic ations.”
	1676	P2.4
	1677	2.6.12.426
	1678	VSA shall not manipu late (chan ge) the co nsuming ap plication’ s user ide ntity or a uthorizati on attribu tes.
	1679	P2.2.2
	1680	2.6.12.427
	1681	VSA shall not transp ort or app ly RPC “co ntext opti on” inform ation to d etermine u ser author ization to execute a n RPC.
	1682	P2.2.2
	1683	2.6.12.428
	1684	VSA shall provide Vi stA M envi ronment fu nctionalit y to execu te RPC log ic without the need for a “con text optio n.”
	1685	P2.2.2
	1686	2.6.12.429
	1687	When avail able in th e “service request,” VSA shall apply the IAM SAML token as t he single authoritat ive source of user i dentity in formation.
	1688	P2.3
	1689	Availabili ty - COOP/ Disaster R ecovery
	1690	Table 15: VSA Availa bility-Con tinuity of Operation s (COOP)/D isaster Re covery (DR ) Requirem ents
	1691	Req. #
	1692	Requiremen t
	1693	Delivery
	1694	2.6.13.436
	1695	VSA will c ontribute VSA update s to the V A continge ncy plan w hich descr ibes syste m availabi lity and C ontinuity of Operati ons/Disast er Recover y (COOP/DR ) elements including failover, failsoft, backup an d restore procedures , etc.
	1696
	1697	(Original) VSA shall document a continge ncy plan w hich descr ibes syste m availabi lity and C ontinuity of Operati ons/Disast er Recover y (COOP/DR ) elements including failover, failsoft, backup an d restore procedures , etc.
	1698
	1699	Justificat ion for Re vision: Cl arify role s of VSA a nd VA in c ontingency planning
	1700	P2.2.2
	1701	2.6.13.437
	1702	VSA shall provide 99 .99% uptim e by imple menting fa ilover acr oss multip le VSA Fed erating Pl atforms.
	1703	P2.5
	1704	2.6.13.438
	1705	The VSA pr oduction i mplementat ion shall provide En terprise-l evel COOP/ DR determi ned approp riate to s ystem supp ort for cr itical bus iness proc esses and data (e.g. , provisio n of healt hcare).
	1706	Justificat ion for Re moval: Add ressed by 2.6.13.436
	1707	Removed
	1708	2.6.13.439
	1709	VSA non-pr oduction e nvironment s shall im plement CO OP/DR as a ppropriate for softw are develo pment and testing en vironments .
	1710	P2.2.2
	1711	2.6.13.440
	1712	Failover f unctionali ty shall b e used to allow func tionality to be repa ired/repla ced/upgrad ed without adversely impacting the 99.99 % uptime o f the rema ining func tionality.
	1713
	1714	(Original) Failover functional ity shall be used to allow pro duction se rvers to b e repaired /replaced/ upgraded w ithout adv ersely imp acting the 99.99% up time of th e remainin g servers.
	1715
	1716	Justificat ion for Re vision: Cl arified to focus on delivered functional ity not se rvers (phy sical or v irtual inf rastructur e).
	1717	P2.5
	1718	2.6.13.441
	1719	Each VSA F ederating Platform s hall facil itate fail over to ot her VSA Fe derating p latforms s o that a f ailure may occur at one platfo rm and wor kload shal l be trans ferred to the other Federating Platforms that rema in operati onal.
	1720	P2.4
	1721	Documentat ion
	1722	Table 16: VSA Docume ntation Re quirements
	1723	Req. #
	1724	Requiremen t
	1725	Delivery
	1726	2.6.14.444
	1727	VSA shall provide re levant doc umentation for each software r elease.
	1728	P2.2.2
	1729	2.6.14.445
	1730	VSA shall provide re lease note s for each software release.
	1731	P2.2.2
	1732	2.6.14.446
	1733	VSA shall provide a user guide for each software r elease.
	1734	P2.2.2
	1735	2.6.14.447
	1736	VSA shall provide an installat ion guide for each s oftware re lease.
	1737	P2.2.2
	1738	2.6.14.448
	1739	VSA shall draft guid elines for the distr ibution of VSA utili ties and t he distrib ution of V SA-generat ed service s.
	1740
	1741	(Original) VSA shall produce s eparate gu ides for t he distrib ution of V SA utiliti es and the distribut ion of VSA -generated services.
	1742
	1743	Justificat ion for Re vision: Re worded for clarity
	1744	P2.2.2
	1745	2.6.14.449
	1746	VSA shall draft the process fo r distribu ting VSA u tilities a s a combin ed applica tion packa ge (both M and VSA r untime com ponents).
	1747
	1748	(Original) VSA shall define an d document the proce ss for dis tributing VSA utilit ies as a c ombined ap plication package (b oth M and VSA runtim e componen ts).
	1749
	1750	Justificat ion for Re vision: Re worded for clarity
	1751	P2.2.2
	1752	2.6.14.450
	1753	VSA shall draft the process fo r distribu ting VSA g enerated s ervices.
	1754
	1755	(Original) VSA shall define an d document the proce ss for dis tributing VSA genera ted servic es.
	1756
	1757	Justificat ion for Re vision: Re worded for clarity
	1758	P2.2.2
	1759	2.6.14.451
	1760	VSA shall draft reco mmended or ganization al policy regarding the implem entation o f VSA gene rated serv ices.
	1761	P2.2.2
	1762	2.6.14.452
	1763	VSA shall draft reco mmended or ganization al policy regarding the use of VSA utili ties.
	1764	P2.6
	1765	Apportioni ng of Requ irements
	1766	VSA requir ements are apportion ed accordi ng the des ignation i n the “Del ivery” col umn of the tables ap pearing in Sections 2.6.1 thro ugh 2.6.14 . All requ irements a re represe nted in an “x.y.z” n omenclatur e
	1767	x = Phase (As determ ined by PM AS)
	1768	y = Increm ent (A cyc le of spri nts with p lanned cap abilities lasting ei ther 3 or 6 months
	1769	Increment 1 & 2 are 6 month in crements a s determin d by PMAS
	1770	Increments 3-6 will be 3 month increment s as deter mined by V IP
	1771	z = Delive red sprint for requi rement ful fillment
	1772	Sprint val ue “z” wil l only be populated when deliv ery is pla nned. Incr ement valu es for fut ure work a re planned placehold ers. The d eterminati on of incr ement and sprint is made as pa rt of an A gile proce ss, and us er functio nality can be reprio ritized to best meet user need s, or work with depe ndencies i n the deve lopment cy cle.
	1773	Requiremen ts marked as removed are eithe r redundan t requirem ents (dupl icated in other requ irements, and met th ere), or t hey have b een determ ined thru the Agile process to be no lon ger releva nt to the work at ha nd. This l atter outc ome is a n atural par t of Agile learning, where dis covery thr u developm ent allows the capab ilities to expand to existing needs not yet discov ered.
	1774
	1775	Graphical User Inter face (GUI) Specifica tions
	1776	Refer to S ection 2.6 .1 for det ailed requ irements.
	1777	A service developer user inter acts with a Web appl ication in terface si milar to t he GUI sho wn in Figu re 2, Figu re 3, and Figure 4.
	1778
	1779	Figure 2: VSA RPC Wi zard-Selec t RPC
	1780
	1781	Figure 3: VSA RPC Wi zard-Edit Definition
	1782
	1783	Figure 4: VSA API Br owser-Show RESTified RPCs
	1784
	1785	Figure 5: VSA API Br owser-Sele ct a RESTi fied RPC
	1786
	1787	Figure 6: VSA API Br owser-Test ing the Re st Call
	1788
	1789	Figure 7: VSA API Br owser-REST Call Resu lts
	1790	Multi-divi sional Spe cification s
	1791	Not Applic able.
	1792	Performanc e Specific ations
	1793	Refer to S ection 2.6 .10 for de tailed req uirements.
	1794	VSA will e xecute per formance, capacity, and indepe ndent test ing of the VSA produ ct, and as part of S QA analysi s and test ing. Web s ervices ex posing Vis tA functio nality wil l be imple mented in various la yers (eMI/ eMI, secur ity valida tion, etc. ). Some of these Web services can access one or mo re VistA s ystems con currently. Performan ce will de pend on th e type of Web servic e (Federat ed for mul tiple Vist A systems and Non-Fe derated fo r a single VistA).
	1795	NOTE: Requ irements a re subject to change after tru e performa nce testin g is condu cted at th e Bay Pine s Test Lab .
	1796	Quality At tributes S pecificati on
	1797	Refer to S ection 2.6 .9.
	1798	Reliabilit y Specific ations
	1799	Refer to S ection 2.6 .13.
	1800	Scope Inte gration
	1801	Refer to s ection 2.6 , “Functio nal Specif ications.”
	1802	VSA is not an applic ation. VSA is a Vist A SOA Serv ices Platf orm that h ost servic es for exp osing Vist A function ality. App lications use VSA as a tool fo r generati ng service s and as a runtime p latform fo r hosting services. VSA integr ates with all VistA systems wi th MVI and eMI. Ther efore, sco pe integra tion for V SA is Vist A SOA Serv ices Platf orm integr ation.
	1803	Security S pecificati ons
	1804	Refer to S ection 2.6 .11.
	1805	System Fea tures
	1806	Refer to S ection 2.6 .3.
	1807	Usability Specificat ions
	1808	Refer to S ection 2.6 .3.
	1809	Purchased Components
	1810	Specificat ions for p urchased c omponents for the Vi stA Servic es Assembl er (VSA) p roduct wil l be deter mined as t he project team coll aborates w ith the sy stems/netw ork teams.
	1811	Estimation
	1812
	1813
	1814	Project So ftware Fun ctional Si ze and Siz e-Based Ef fort and D uration Es timate
	1815	Applicatio n
	1816	Item
	1817	A
	1818	B
	1819	C
	1820	D
	1821	E
	1822	Total
	1823	Counted Fu nction Poi nts
	1824	65
	1825	N/A
	1826	N/A
	1827	N/A
	1828	N/A
	1829	65
	1830	Estimated Scope Grow th
	1831	N/A
	1832	N/A
	1833	N/A
	1834	N/A
	1835	N/A
	1836	N/A
	1837	Estimated Size at Re lease
	1838	49-85
	1839	N/A
	1840	N/A
	1841	N/A
	1842	N/A
	1843	49-85
	1844
	1845	Size-Based Effort Es timates
	1846	Labor Hour s
	1847	Probabilit y
	1848	Low-Effort Estimate – With ind icated pro bability, project wi ll consume no more t han:
	1849	1030
	1850	50%
	1851	High-Effor t Estimate – With in dicated pr obability, project w ill consum e no more than:
	1852	1920
	1853	75%
	1854
	1855	Size-Based Duration Estimates
	1856	Work Days
	1857	Probabilit y
	1858	Low-Durati on Estimat e – With i ndicated p robability , project will consu me no more than:
	1859	68
	1860	50%
	1861	High-Durat ion Estima te -- With indicated probabili ty, projec t will con sume no mo re than:
	1862	115
	1863	75%
	1864	NOTE: Base d on the m inor chang es to the RSD, a new Function Point Anal ysis (FPA) project e stimation count is n ot warrant ed at this time.
	1865
	1866	Figure 8: Cumulative Probabili ty (“S-cur ve”) Chart —Project D uration
	1867
	1868	Figure 9: Cumulative Probabili ty (“S-cur ve”) Chart —Project E ffort
	1869
	1870	Approval S ignatures
	1871	REVIEW DAT E:
	1872	SCRIBE: El aine Laure l
	1873
	1874	Signed:
	1875
	1876	__________ __________ __________ __________ __________ __________ __________ ________
	1877	Steven Ost er, Integr ated Proje ct Team (I PT) ChairD ate
	1878
	1879
	1880	__________ __________ __________ __________ __________ __________ __________ ________
	1881	Mike Davis , Business Sponsor D ate
	1882
	1883
	1884	__________ __________ __________ __________ __________ __________ __________ ________
	1885	Russell Ho lt, IT Pro gram Manag erDate
	1886
	1887
	1888	__________ __________ __________ __________ __________ __________ __________ ________
	1889	Lori Warre n, Project ManagerDa te
	1890
	1891
	1892
	1893	Appendix A : Non-Func tional Req uirements
	1894	The follow ing non-fu nctional r equirement s should b e reviewed and asses sed while developing the requi rements fo r the proj ect.
	1895	Refer to S ection 2.6 .9 for det ailed requ irements.
	1896	System Per formance R eporting R equirement s
	1897	(Note: Ea ch system developed by the Dep artment of Veterans Affairs (V A) Office of Informa tion and T echnology (OI&T) mus t comply w ith the fo llowing ma ndatory re quirements .)
	1898	Include in strumentat ion to mea sure all p erformance metrics s pecified i n the Non- Functional Requireme nts sectio n of the R equirement s Traceabi lity Matri x (RTM). A t a minimu m, systems will have the abili ty to meas ure report ing requir ements for Responsiv eness, Cap acity, and Availabil ity as def ined in th e non-func tional req uirements section of the RTM.
	1899	Make the p erformance measureme nts availa ble to the Informati on Technol ogy (IT) P erformance Dashboard to enable display o f “actual” system me trics to c ustomers a nd IT staf f.
	1900	Operationa l Environm ent Requir ements
	1901	System res ponse time s and page load time s shall be consisten t with ___ CPRS____ s tandards ( for exampl e, My Heal theVet or HealtheVet ). (Commen t: There m ay be diff erent expe ctations f or an exte rnal displ ay vs. a q uery. Need to addres s these di fferent us es. Also i ndicate if this info rmation is unknown).
	1902	Maintenanc e, includi ng mainten ance of ex ternally d eveloped s oftware in corporated into the __VSA___ap plication( s), shall be schedul ed during off peak h ours or in conjuncti on with re levant mai ntenance s chedules. The busine ss owner s hould prov ide specif ic require ments for establishi ng system maintenanc e windows when plann ed service disruptio ns can occ ur in supp ort of per iodic main tenance.
	1903	Informatio n about re sponse tim e degradat ion result ing from u nscheduled system ou tages and other even ts that de grade syst em functio nality and /or perfor mance shal l be disse minated to the user community within 30 minutes of the occur rence. The notificat ion shall include th e informat ion descri bed in the current A utomated N otificatio n Reportin g (ANR) te mplate mai ntained by the VA Se rvice Desk . The spec ific busin ess impact must be n oted in or der for OI T to provi de accurat e data in the servic e impact n otice of t he ANR.
	1904	Provide a real-time monitoring solution to report agreed/ide ntified cr itical sys tem perfor mance para meters.
	1905	Critical b usiness pe rformance parameters shall be identified e.g., tra nsaction s peed, resp onse time for screen display/r efresh, da ta retriev al, etc. i n a manner that data capture c an occur t o support metric rep orting and support t he OI&T pe rformance dashboard display. I f no such performanc e metrics are requir ed or prov ided there will be n o program specific S ervice Lev el Agreeme nts (SLA) created, n or shall t here be an y active/r eal time m onitoring through OI &T Perform ance Dashb oard to pr ovide the business o wners any performanc e metrics.
	1906	Notificati on of sche duled main tenance pe riods that require t he service to be off line or th at may deg rade syste m performa nce shall be dissemi nated to t he busines s user com munity a m inimum of 48 hours p rior to th e schedule d event.
	1907	Documentat ion Requir ements
	1908	The traini ng curricu lum shall state the expected t raining ti me for pri mary users and secon dary users to become proficien t at using the _____ _______ ap plication( s).
	1909	All traini ng curricu la, user m anuals and other tra ining tool s shall be developed /updated b y ______ < <insert na me of Prog ram Office >> and del ivered to all levels of users __________ ______. If known, in sert how m uch time i n advance the traini ng tools w ill be del ivered and via what mechanism( s); for ex ample, 2-4 weeks in advance of the relea se of the enhancemen t through nationwide conferenc e calls an d PowerPoi nt present ations). T he curricu la shall i nclude all aspects o f the enha nced _____ ___ applic ation(s) a nd all cha nges to pr ocesses an d procedur es.
	1910	The traini ng curricu lum develo ped by the Program O ffice shal l state th e expected task comp letion tim e for prim ary and se condary us ers.
	1911	User manua ls and tra ining tool s shall be developed . If they already ex ist, updat es shall b e made, as necessary , to them and they s hall be de livered to all level s of users .
	1912	IT will pr ovide the level of d ocumentati on require d to suppo rt the sys tem and ma intain ope rations an d continui ty. Docume ntation sh all repres ent minima l programm atic and l ifecycle o perations support do cumentatio n artifact s as defin ed by VA s tandards i n ProPath and as req uired by t he VA Ente rprise Sys tem Engine ering Life cycle and Release Ma nagement o ffice for sustained operations , maintena nce, and s upport (ht tp:// URL /lifecycle /default.a spx) prior to approv al by any VA change control bo ard and re lease into productio n.
	1913	Implementa tion Requi rements
	1914	Technical Help Desk support fo r the appl ication sh all be pro vided for users to o btain assi stance wit h ________ ___.
	1915	The IT sol ution shal l be desig ned to com ply with t he applica ble approv ed Enterpr ise SLA.
	1916	The implem entation m ust be com plete by _ _________. (Enter da te - dd-mm -yyyy)
	1917	Data Prote ction/Back -up/Archiv e Requirem ents
	1918	Based upon the criti cality of the system , provide a back-up and data r ecovery pr ocess for when the s ystem is b rought off -line for maintenanc e or techn ical issue s/problems .
	1919	Data prote ction meas ures, such as back-u p interval s and redu ndancy sha ll be cons istent wit h systems categorize d as routi ne (30 day restorati on), missi on essenti al (72 hou r restorat ion), or m ission cri tical (12 hour resto ration).
	1920	Business o wners are required t o state th e mission criticalit y of the I T services required in order t o assist t he planner s and deve lopers in determinin g best str ategies fo r engineer ing an IT solution t o meet the ir busines s objectiv es/needs. The busine ss owner n eeds to st ate the cr iticality of the dat a and the impact to the busine ss during a service disruption so approp riate tech nologies c an be cons idered.
	1921	Levels for Disaster Recovery
	1922	Table 17: Levels for Disaster Recovery
	1923	Classifica tion
	1924	Recovery T ime Object ive
	1925	Recovery P oint
	1926	Objective Routine
	1927	30 day res toration
	1928	TBD
	1929	Mission Es sential
	1930	72 hour re storation
	1931	24 hours
	1932	Mission Cr itical
	1933	12 hour re storation
	1934	2 hours
	1935	Recovery T ime Object ive (RTO) – RTO defi nes the ma ximum amou nt of time that a sy stem resou rce can re main unava ilable bef ore there is an unac ceptable i mpact on o ther syste m resource s, support ed mission /business processes, and the M TD.
	1936	Maximum To lerable Do wntime (MT D) - The M TD represe nts the to tal amount of time t he system owner/auth orizing of ficial is willing to accept fo r a missio n/business process o utage or d isruption and includ es all imp act consid erations.
	1937	Recovery P oint Objec tive (RPO) - The RPO represent s the poin t in time, prior to a disrupti on or syst em outage, to which mission/bu siness pro cess data can be rec overed (gi ven the mo st recent backup cop y of the d ata) after an outage .
	1938	Data Quali ty/Assuran ce Require ments
	1939	A monitori ng process shall be provided t o ensure t hat data i s accurate and up-to -date and provides a ccurate al erts for m alfunction s while mi nimizing f alse alarm s.
	1940	User Acces s/Security Requireme nts
	1941	Ensure the proposed solution m eets all V eterans He alth Admin istration (VHA) Secu rity, Priv acy, and I dentity Ma nagement r equirement s includin g VA Handb ook 6500 ( see the En terprise R equirement s section of the RTM ).
	1942	Usability/ User Inter face Requi rements
	1943	Adhere to good User Interface/ User Cente red Design (UI/UCD) principles as outlin ed in the Usability Appendix o f the BRD.
	1944	Conceptual Integrity
	1945	Provide st andards ba sed messag ing and mi ddleware i nfrastruct ure needed to suppor t both Leg acy Vetera ns Health Informatio n Systems Technology Architect ure (VistA ) and futu re VistA 4 deploymen ts.
	1946	Availabili ty
	1947	Maintenanc e window, including maintenanc e of exter nally deve loped soft ware incor porated in to the Vis tA 4 appli cation(s), will be b y mutual a greement b etween OI& T and the VHA Point of Contact (POC) for the affec ted facili ty (ies). VHA will p rovide POC s for each facility.
	1948	VistA appl ication un availabili ty due to an unplann ed outage or planned outages t hat exceed the defin ed mainten ance windo w will not exceed 8. 76 hours p er year an d will not exceed 43 .8 minutes per month (99.9% av ailability ).
	1949	The applic ation shal l be avail able 24 ho urs a day, seven day s a week, with an up time of 99 .9%.
	1950	All system updates a nd schedul ed mainten ance shoul d occur be tween the hours of 1 800 and 06 00 (per lo cal time z one), when clinical usage woul d be light est.
	1951	Interopera bility
	1952	The system shall sup port all r ecognized health sys tem standa rds i.e., Health Lev el 7 (HL7) , Fast Hea lthcare In teroperabi lity Resou rces (FHIR ).
	1953	Systems mu st be hete rogeneous and agnost ic for ope rating sys tems and c ode bases.
	1954	Provide th e ability to securel y transfer large fil es (of 4-8 gigabyte) from an e xternal so urce to VA systems.
	1955	Provide ac cess to th e system o ver a remo te access solution.
	1956	Manageabil ity
	1957	Provide Se rvice Desk /Incident and Proble m Manageme nt trackin g related to mainten ance event s of patie nt care sy stems with priority over non-p atient car e systems.
	1958	Provide da ta related to mainte nance even ts, both r outine and exception al, includ ing key me tadata:
	1959	Predicted routine wo rk
	1960	Occurrence s where ma intenance is complet ed, includ ing restar t from dow n time
	1961	Identity o f the orga nization p erforming maintenanc e
	1962	User perfo rming main tenance (i f availabl e)
	1963	Identity o f the syst em
	1964	Date/time, physical location
	1965	Systems im pacted
	1966	Does it af fect patie nt care
	1967	Non-urgent or emerge nt
	1968	Provide au dit capabi lities for system ac cess and u sage with settings t hat are co nfigurable to suppor t internal and exter nal audits based on federal an d VHA mand ates.
	1969	The system must comp ly with VA Directive 6300 Reco rds and In formation Management and with VHA Record s Control Schedule ( RCS) 10-1, in genera l and spec ifically w ith Electr onic Final Version o f Health R ecord: Des troy/Delet e 75 years after las t episode of patient care, or longer (if specified ).
	1970	Performanc e
	1971	Provide an Infobutto n Query Re sponder on all platf orms with a response time of l ess than . 5 seconds.
	1972	The system shall rec ognize, re port, and retransmit data lost , with les s than 0-1 % chance o f incomple te patient records.
	1973	Provide pa tient data (for data within th e system) transactio ns (e.g., capture, s earch, req uest for d ata) withi n .5 secon ds.
	1974	Mouse or k ey-based U I controls , e.g., me nus, check boxes shal l provide instantane ous respon siveness ( <90ms).
	1975	Part-scree n refreshe s after us er action shall comp lete withi n a pro-ra ted interv al between 200 ms an d 1200 ms times a pe rcentage o f the scre en area be ing refres hed. For e xample, a component 10% of the screen ar ea would r efresh in (1200 – 20 0) * 0.10 + 200 = 30 0 ms.
	1976	Reliabilit y
	1977	Provide sy stem relia bility:
	1978	Threshold = 99.9%
	1979	Objective = 99.99% s ystem and applicatio n
	1980	Provide sy stem relia bility:
	1981	Level 1 se verity =<1 failure p er month
	1982	Level 2 se verity =<2 failures per month
	1983	Level 3 se verity =<3 failures per month
	1984	Security
	1985	Provide ma nagement o f electron ic attesta tion of in formation including the retent ion of the signature of attest ation (or certificat e of authe nticity) a ssociated with incom ing or out going info rmation.
	1986	Supportabi lity
	1987	Provide al erts (that extend be yond syste m messages to extern al systems like mobi le devices ) for malf unctions, while prev enting fal se alarms for local, regional, and natio nal evalua tions in r eal time.
	1988	Provide re ports on p erformance metrics a s specifie d in the V istA 4 Eff ectiveness and Value / Benefit s Framewor k on a bi- weekly bas is.
	1989	Provide na tional, re gional, an d local re ports on p erformance metrics a s specifie d in the V istA 4 Eff ectiveness and Value / Benefit s Framewor k.
	1990	Provide pe rformance metrics (f rom reques t for info rmation to receipt o f informat ion on the screen) m onitored b y the syst em and sys tem admini strators s o they kno w what the user expe rience is like witho ut users h aving to c all them a nd tell th em the sys tem is run ning very slow.
	1991	Provide th e ability for VHA an d IT staff to create standard and ad-hoc reports o f usage, b andwidth, response t ime, login time, and other var iables wit h a verifi cation pro cess for m easuring t he capabil ities of t he system.
	1992	Provide en d-user tra ining on h ow to gene rate the v arious sys tem perfor mance repo rts (e.g., in standa rd file fo rmats such as Comma Separated Values [CS V], Portab le Documen t Format [ PDF], or E xcel) depe nding on t he user's needs.
	1993	Provide th e ability to view sy stem stati stics (e.g ., informa tion on th e specific network e nvironment ) and iden tify areas that are having iss ues or are beyond ca pacity, in near-real -time (to be quantif ied at a l ater time) .
	1994	Technical Help Desk support fo r the appl ication vi a instant message, o n-line, ph one, and r emote desk top access support, shall be p rovided fo r users to obtain as sistance 2 4/7.
	1995	The IT sol ution shal l be desig ned to com ply with t he applica ble approv ed Enterpr ise SLAs.
	1996	Data prote ction meas ures, such as back-u p interval s and redu ndancy sha ll be cons istent wit h systems categorize d as missi on critica l (1hr res toration, 2hrs backu p recovery ). Impact of system failure mu st be moni tored on a near real time basi s.
	1997	Provide th e ability to set thr esholds an d notifica tion type (e.g., ema il or text alerts) w hen alerti ng the use r about re sponse tim e degradat ion and un scheduled outages.
	1998	Disaster R ecovery Pl ans (DRP) and Contin uity of Op erations P lan (COOP) will be u pdated and tested se mi-annuall y to addre ss the Vis tA 4 produ ct (see Na tional Sec urity and Homeland S ecurity Pr esidential Directive : National Continuit y Policy. NSPD-51/HS PD-20, May 9, 2007 h ttp://www. fas.org/ir p/offdocs/ nspd/nspd- 51.htm)
	1999	Usability
	2000	Provide vi ew ability /usability of VistA 4 applicat ions on mo bile devic es.
	2001	User promp ts and scr een help s hall be em bedded int o the syst em to guid e use of t he solutio n.
	2002	Documentat ion
	2003	The traini ng curricu lum shall be provide d in two h ours or mo re of trai ning time for primar y users an d secondar y users to become pr oficient a t using th e VistA 4 applicatio n(s).
	2004	All traini ng curricu la, user m anuals and other tra ining tool s shall be developed /updated b y the VE P rogram Off ice and de livered to all level s of users 4 weeks i n advance of the rel ease of th e enhancem ent throug h mediums that will best suppo rt the sha ring of in formation to all aff ected staf f.
	2005	Provide fo llow-up tr aining cla sses tailo red to VHA workflow 4 weeks af ter the us ers have b egun to us e the syst em
	2006
	2007	Appendix B : Acronym List and G lossary
	2008
	2009	This subse ction prov ides the d efinitions of all te rms, acron yms, and a bbreviatio ns require d to prope rly interp ret the Vi stA Servic es Assembl er (VSA) P hase 2.
	2010	Acronyms
	2011	In additio n to the a cronyms de fined belo w, refer t o the Offi ce of Info rmation an d Technolo gy (OI&T) Master glo ssary.
	2012	Table 18: Acronyms
	2013	Term
	2014	Descriptio n
	2015	AITC
	2016	Austin Inf ormation T echnology Center
	2017	API
	2018	Applicatio n Program Interface
	2019	BRD
	2020	Business R equirement s Document
	2021	CDS
	2022	Clinical D ata Servic es
	2023	CIO
	2024	Chief Info rmation Of fice
	2025	CONUS
	2026	Continenta l United S tates
	2027	COOP
	2028	Continuity of Operat ions
	2029	COTS
	2030	Commercial -Off-The-S helf
	2031	CSP
	2032	Caché Serv er Pages
	2033	CVS
	2034	Conformanc e Validati on Stateme nt
	2035	DFN
	2036	Data File Number
	2037	DoD
	2038	Department of Defens e
	2039	DR
	2040	Disaster R ecovery
	2041	EDE
	2042	Enterprise Developme nt Departm ent
	2043	eMI
	2044	Enterprise Messaging Infrastru cture
	2045	ESB
	2046	Enterprise Service B us
	2047	ESS
	2048	Enterprise Shared Se rvices
	2049	EWD
	2050	Enterprise Web Devel opment
	2051	FDCC
	2052	Federal De sktop Core Configura tion
	2053	GUI
	2054	Graphical User Inter face
	2055	HTTPS
	2056	Hypertext Transfer P rotocol Se cure
	2057	IAM
	2058	Identity a nd Access Management
	2059	iEHR
	2060	Integrated Electroni c Health R ecord
	2061	IHS
	2062	Indian Hea lth Servic e
	2063	IT
	2064	Informatio n Technolo gy
	2065	IV&V
	2066	Independen t Verifica tion and V alidation
	2067	JAX-WS
	2068	Java API f or XML Web Services
	2069	JSON
	2070	JavaScript Object No tation
	2071	M (MUMPS)
	2072	Massachuse tts Genera l Hospital Utility M ultiprogra mming Syst em (now kn own as “M” )
	2073	MDWS
	2074	Medical Do main Web S ervices
	2075	MPI
	2076	Master Pat ient Index
	2077	MVI
	2078	Master Vet eran Index
	2079	NIST
	2080	National I nstitute o f Standard s and Tech nology
	2081	OED
	2082	Office of Enterprise Developme nt
	2083	OI&T
	2084	Office of Informatio n and Tech nology
	2085	OSEHRA
	2086	Open Sourc e Electron ic Health Record Age nt
	2087	PD
	2088	Product De velopment
	2089	PHI
	2090	Personal H ealth Iden tifiers
	2091	PII
	2092	Personally Identifia ble Inform ation
	2093	POAM
	2094	Plan of Ac tion and M ilestones
	2095	POC
	2096	Proof of C oncept
	2097	RDC
	2098	Regional D ata Center
	2099	REST
	2100	Representa tional Sta te Transfe r
	2101	RPC
	2102	Remote Pro cedure Cal ls
	2103	RSD
	2104	Requiremen ts Specifi cation Doc ument
	2105	RTM
	2106	Requiremen ts Traceab ility Matr ix
	2107	SAML
	2108	Security A ssertion M ark-up Lan guage
	2109	SDD
	2110	Systems De sign Docum ent
	2111	SDLC
	2112	System Dev elopment L ife Cycle
	2113	SEDR
	2114	Systems En gineering and Design Review
	2115	SME
	2116	Subject Ma tter Exper t
	2117	SOA
	2118	Service Or iented Arc hitecture
	2119	SOAP
	2120	Simple Obj ect Access Protocol
	2121	SSL
	2122	Secure Soc ket Layer
	2123	TCP/IP
	2124	Transmissi on Control Protocol/ Internet P rotocol
	2125	TLS
	2126	Transport Layer Secu rity
	2127	TRM
	2128	Technical Reference Model
	2129	URI
	2130	Uniform Re source Ide ntifiers
	2131	URL
	2132	Uniform Re source Loc ator
	2133	VA
	2134	Department of Vetera ns Affairs
	2135	VAMC
	2136	VA Medical Center
	2137	VE
	2138	VistA Evol ution
	2139	VHA
	2140	Veterans H ealth Admi nistration
	2141	VistA
	2142	Veterans H ealth Info rmation Sy stem and T echnology Architectu re
	2143	VM
	2144	Virtual Ma chine
	2145	VSA
	2146	VistA Serv ices Assem bler
	2147	WAR
	2148	Web Applic ation ARch ive
	2149	WMB
	2150	WebSphere Message Br oker
	2151	WSDL
	2152	Web Servic es Descrip tion Langu age
	2153	WSRR
	2154	WebSphere Registry a nd Reposit ory
	2155	XML
	2156	Extended M arkup Lang uage
	2157	Definition s
	2158	Table 19: Definition s
	2159	Term
	2160	Definition
	2161	Caché
	2162	An “M”-bas ed product (by Inter Systems) t hat has be en selecte d as the n ext genera tion Veter ans Health Informati on Systems and Techn ology Arch itecture ( VistA) pla tform. Cac hé stores data in mu ltidimensi onal array s capable of carryin g hierarch ically str uctured da ta. These are the sa me “global ” data str uctures us ed by the MUMPS prog ramming la nguage, wh ich influe nced the d esign of C aché, and are simila r to those used by M ultiValue (aka PICK) systems. In most ap plications ; however, object an d/or SQL a ccess meth ods are us ed.
	2163	Caché Obje ctScript, Caché Basi c or T-SQL can be us ed to deve lop applic ation busi ness logic . External interface s include native obj ect bindin g for C++, Java, EJB , ActiveX, and NET. Caché supp orts JDBC and ODBC f or relatio nal access . XML and Web Servic es are als o supporte d.
	2164	Connectivi ty
	2165	Connectivi ty provide s connecti on to the Master Pat ient Index (MPI), St ructured Q uery Langu age (SQL), and XML.
	2166	Federating Services Platform
	2167	Serves as the regist ry and rep ository fo r storing Service De scriptor a nd runtime packages (Web servi ces). It f ederates r outing of queries fr om provide r and cons umer “serv ice” reque sts to and from Vete rans Healt h Informat ion System s and Tech nology Arc hitecture (VistA). I t also pro vides the security i nterface t hat contro ls single sign-on (S SO) access , so a use r’s authen tication t oken is tr usted acro ss multipl e VA Infor mation Tec hnology (I T) systems or organi zations.
	2168	GUI
	2169	The Graphi cal User I nterface a pplication that is d eveloped f or the cli ent workst ation.
	2170	JSON
	2171	JavaScript Object No tation is an open st andard for mat that u ses human- readable t ext to tra nsmit data objects c onsisting of attribu te–value p airs. It i s used pri marily to transmit d ata betwee n a server and Web a pplication , as an al ternative to XML.
	2172	M Hosting Platform
	2173	A runtime system sup porting AN SI standar d M such a s InterSys tems Caché or GT.M.
	2174	MPI
	2175	The Master Patient I ndex (MPI) is locate d at the A ustin Info rmation Te chnology C enter (AIT C). It is composed o f a unique list of p atients, e ach with a n assigned Integrati on Control Number (I CN), and a n associat ed list of VAMCs (Ve terans Aff airs Medic al Centers ) and othe r systems of interes t where ea ch patient has been seen. This enables t he sharing of patien t data bet ween opera tionally d iverse sys tems. Each patient r ecord (or index entr y) on the MPI contai ns multipl e demograp hic fields which are updated t o the Prim ary View o f the MPI.
	2176	MVI
	2177	The Master Veteran I ndex retur ns identit y data for person ma tching the criteria provided. Additional ly, MVI wi ll provide scores in dicating a degree of certainty for each person. MV I also wil l provide a threshol d, indicat ing which scores ind icate a va lid match. For the m atched rec ord, ICN a nd its ide ntifiers i n other co rrelated s ystems wil l be retur ned.
	2178	SOA
	2179	Service Or iented Arc hitecture is a flexi ble set of design pr inciples u sed during the phase s of syste ms develop ment and i ntegration . A deploy ed SOA-bas ed archite cture will provide a loosely-i ntegrated suite of s ervices th at can be used withi n multiple business domains.
	2180	SSL
	2181	A cryptogr aphic prot ocol desig ned to pro vide commu nication s ecurity ov er the Int ernet.
	2182	VistA Serv ices Assem bler Wizar d
	2183	A Web appl ication to ol which a uto genera tes VistA SOA Servic es.
	2184	VistA SOA Federating Services Platform
	2185	A server f or hosting Web servi ces, to wh ich VistA SOA Servic es are dep loyed.
	2186	VistA SOA Service
	2187	An SOA com pliant ser vice gener ated by th e VistA Se rvices Ass embler Wiz ard with f ederating capabiliti es. Implem ented in J AX-WS.
	2188	VistA Serv ices Assem bler SOA S ervice Des criptors
	2189	Meta data XML docume nt created by the Vi stA Servic es Assembl er Wizard used to au to generat e VistA SO A Services .
	2190	VistA SOA Service Re gistry Ent ry
	2191	Entry in t he WebSphe re Registr y and Repo sitory (WS RR) used t o govern a specific VistA SOA Service.
	2192	VistA SOA Service Pr oxy
	2193	Proxy on t he Enterpr ise Messag ing Infras tructure ( eMI) used to abstrac t the serv ice endpoi nt.
	2194	VistA
	2195	The Vetera ns Health Informatio n Systems and Techno logy Archi tecture (V istA) – A rich autom ated envir onment tha t supports day-to-da y operatio ns at loca l VA healt h care fac ilities. V istA is bu ilt on a c lient-serv er archite cture, whi ch ties to gether wor kstations and person al compute rs with gr aphical us er interfa ces at VA facilities , as well as softwar e develope d by local medical f acility st aff. VistA also incl udes the l inks that allow comm ercial off -the-shelf software and produc ts to be u sed with e xisting an d future t echnologie s.
	2196	WSDL
	2197	Web Servic e Descript ion Langua ge (WSDL) is a docum ent that p rovides a common lan guage to d escribe:
	2198	What the W eb service does.
	2199	What funct ionality i t can prov ide.
	2200	What data it can del iver.
	2201	A develope r can clic k the WSDL and gener ate the co de automat ically.
	2202	XML
	2203	XML is a m arkup lang uage that defines a set of rul es for enc oding docu ments in a format th at is both human-rea dable and machine-re adable.
	2204
	2205	Template R evision Hi story
	2206	Date
	2207	Version
	2208	Descriptio n
	2209	Author
	2210	September 2015
	2211	1.7
	2212	Updated He adings and spacing t o conform with lates t OIT Docu mentation Standards guidelines
	2213	Process Ma nagement
	2214	June 2015
	2215	1.6
	2216	Updated to conform w ith latest Section 5 08 guideli nes and re mediated w ith Common Look Offi ce tool
	2217	Process Ma nagement
	2218	May 2015
	2219	1.5
	2220	Revised by the PMAS Process Im provement Lockdown T eam
	2221	PMAS Proce ss Improve ment Lockd own Team
	2222	December 2 014
	2223	1.4
	2224	Updated to conform w ith latest Section 5 08 guideli nes and re mediated w ith Common Look Offi ce tool
	2225	Process Ma nagement
	2226	May 2014
	2227	1.3
	2228	Reordered cover page to enhanc e search c apabilitie s
	2229	Process Ma nagement
	2230	May 2013
	2231	1.2
	2232	Add Append ix for acr onyms and glossary
	2233	Process Ma nagement
	2234	March 2013
	2235	1.1
	2236	Formatted to current ProPath d ocumentati on standar ds and edi ted to con form with latest Alt ernative T ext (Secti on 508) gu idelines
	2237	Process Ma nagement
	2238	January 20 13
	2239	1.0
	2240	Initial Ve rsion
	2241	PMAS Busin ess Office