1. EPMO Open Source Coordination Office Redaction File Detail Report

Produced by Araxis Merge on 8/29/2018 12:18:41 PM Central Daylight 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.

1.1 Files compared

#	Location	File	Last Modified
1	OSCIF_VBECS_Sust.zip	VistA Blood Establishment Computer Software (VBECS) 2.3.0 Admin User Guide.docx	Tue Aug 28 20:12:03 2018 UTC
2	OSCIF_VBECS_Sust.zip	VistA Blood Establishment Computer Software (VBECS) 2.3.0 Admin User Guide.docx	Wed Aug 29 14:43:42 2018 UTC

1.2 Comparison summary

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

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

1.4 Active regular expressions

No regular expressions were active.

1.5 Comparison detail

	1
	2
	3
	4
	5	VistA Bloo d Establis hment Comp uter Softw are (VBECS ) Version 2.3.0
	6
	7
	8	Administra tor User G uide
	9
	10	June 2018
	11
	12
	13
	14
	15
	16
	17
	18
	19	Department of Vetera ns Affairs
	20	Enterprise Project M anagement Office
	21	This page intentiona lly left b lank.
	22	Revision H istory
	23
	24	Date
	25	Revision
	26	Descriptio n
	27	Author
	28	6/19/18
	29	1.0
	30	Initial Ve rsion. (Ta sks 341068 , 508540, 618005, 62 8047, 7043 63)
	31	BBM team
	32
	33	This page intentiona lly left b lank.
	34
	35	Table of C ontents
	36	Revision H istory3
	37	Introducti onvii
	38	VBECS Vers ion Number svii
	39	Related Ma nuals and Reference Materialsi x
	40	How this A dministrat or User Gu ide is Org anized11
	41	Terms11
	42	Figures11
	43	Screen Sho ts11
	44	Customer S upport13
	45	VBECS Main tenance Op erations15
	46	Prerequisi tes15
	47	Outcome16
	48	Limitation s and Rest rictions16
	49	Additional Informati on16
	50	Log into V BECS Admin istrator16
	51	VBECS Admi nistrator Operations 21
	52	Edit Syste m Interfac es21
	53	Assumption s21
	54	Limitation s and Rest rictions21
	55	Additional Informati on21
	56	Edit Syste m Interfac e Paramete rs21
	57	Edit Divis ions30
	58	Assumption s30
	59	Limitation s and Rest rictions30
	60	Additional Informati on30
	61	Add and Ma intain Div isions30
	62	Edit Users 34
	63	Assumption s34
	64	Limitation s and Rest rictions34
	65	Additional Informati on34
	66	Edit VBECS Users34
	67	Index39
	68
	69	This page intentiona lly left b lank.
	70	Introducti on
	71	VBECS is a Blood Ban k applicat ion that f acilitates ongoing c ompliance with Food and Drug A dministrat ion (FDA) standards for medica l devices and enhanc es the VA’ s ability to produce high-qual ity blood products a nd service s to veter ans. The s ystem foll ows blood bank stand ards, stan dards of n ational ac crediting agencies, FDA regula tions, and VA polici es.
	72	The main p urpose of the VistA Blood Esta blishment Computer S oftware (V BECS) is t o automate the daily processin g of blood inventory and patie nt transfu sions in a hospital transfusio n service.
	73	Unauthori zed access or misuse of this s ystem and/ or its dat a is a fed eral crime . Use of a ll data, p rinted or electronic , must be in accorda nce with V A policy o n security and priva cy.
	74
	75	Do not ch ange the s ystem! The U.S. Food and Drug Administra tion class ifies this software as a medic al device. Unauthori zed modifi cations wi ll render this devic e an adult erated med ical devic e under Se ction 501 of the Med ical Devic e Amendmen ts to the Federal Fo od, Drug, and Cosmet ic Act. Ac quiring an d implemen ting this software t hrough the Freedom o f Informat ion Act re quire the implemente r to assum e total re sponsibili ty for the software and become a registe red manufa cturer of a medical device, su bject to F DA regulat ions. Addi ng to or u pdating VB ECS softwa re without permissio n is prohi bited.
	76	VBECS Vers ion Number s
	77	In previou s VBECS pa tch releas es, the us er documen tation ref erred to t he VBECS v ersion in a 4-digit format (e. g., 2.1.0. 2 – where 2.1.0 repr esents the patch ver sion and t he last di git (2) is the patch build num ber).
	78	The VBECS version (F igure 1) i s now repr esented wi th only th e first th ree digits (e.g., 2. 1.0) and a ppears tha t way in a ll user do cumentatio n to simpl ify readab ility
	79	The revisi on letter tracks dat abase-only updates ( e.g., bloo d product table upda tes, canne d comments updates). The revis ion letter is normal ly a singl e alpha ch aracter (e .g., C), b ut can be two charac ters (e.g. , AA, AB, AC) in the unlikely event that more than 25 databa se updates are made before a c ode change is implem ented. The revision letter sta rts at A w ith each n ew code ch ange and i s incremen ted to B w hen the fi rst databa se-only up date is ma de. The re vision let ter is the n updated by one cha racter in the alphab et for eve ry success ive databa se-only up date until a new cod e change i s implemen ted, at wh ich time t he revisio n letter r everts bac k to A. Th e version submitted for system testing i s revision A, but th e version customers receive ca n be revis ion A, B o r a higher revision letter.
	80
	81
	82	Figure 1: Example of VBECS Adm inistrator About Scr een
	83
	84	DR 4992
	85
	86	The VBECS Administra tor and VB ECS applic ations, wh en started , will ver ify that t he applica tion code (binary bu ild number ) matches the SQL Se rver code (database build numb er) in ord er to ensu re that ap plication servers an d SQL serv ers are pa tched and remain in sync with each other . In the r are event that they fall out o f sync, th e applicat ions will present th e followin g error me ssage (Fig ure 2) and close unt il both th e code and the datab ase are in sync.
	87	Figure 2: Example of System Er ror
	88
	89
	90	Related Ma nuals and Reference Materials
	91	HL7 V2.3.1 Implement ation Guid e
	92	CPRS-VBECS Interface (OR3.02 12) Releas e Notes Ap ril 2009
	93	PIMS V. 5. 3 Technica l Manual
	94	Duplicate Record Mer ge: Patien t Merge Te chnical Ma nual Versi on 7.3 Apr il 1998 Re vised Dece mber 2010
	95	Kernel Sys tems Manua l Version 8.0, Chapt er 1: Sign -On Securi ty/User In terface, p p. 13–20
	96	Manage Ope n Sessions and Files in Window s 2008 R2
	97	Health Pro duct Suppo rt Release of Produc ts and Pat ches Guide V2.3 Upda ted: Febru ary 2014
	98	VistA Bloo d Establis hment Comp uter Softw are (VBECS ) 2.3.0 Us er Guide
	99	VistA Bloo d Establis hment Comp uter Softw are (VBECS ) 2.3.0 Te chnical Ma nual-Secur ity Guide
	100	VistA Bloo d Establis hment Comp uter Softw are (VBECS ) 2.2.0 Au tomated In strument a nd Instrum ent Manage r for <ins trument> S etup Guide
	101	VistALink Version 1. 5 Develope r-System M anager Man ual, Chapt er 6: Secu rity Manag ement, pp. 34–35
	102	Windows Se rver 2008R 2 Security Guide, Mi crosoft Co rporation
	103	This page intentiona lly left b lank.
	104
	105	How this A dministrat or User Gu ide is Org anized
	106	Outlined t ext is use d througho ut this gu ide to hig hlight war nings, lim itations, and cautio ns:
	107	Warnings, limitatio ns, cautio ns
	108	Terms
	109	For consis tency and space cons iderations , the pron ouns “he,” “him,” an d “his” ar e used as pronouns o f indeterm inate gend er equally applicabl e to males and femal es.
	110	In many in stances, a user may scan a bar code or en ter data m anually (b y typing). The term “enter” is used thro ughout thi s guide to mean “ent er manuall y.”
	111	Figures
	112	If you ref er to figu res from t he VBECS A dministrat or User Gu ide in you r local po licy and p rocedure d ocuments, you may wi sh to use their titl es only, w ithout fig ure or tab le numbers : as the a dministrat or user gu ide is upd ated, thos e numbers may change .
	113	Screen Sho ts
	114	Because VB ECS is a m edical dev ice, scree n shots mu st be capt ured at va rious poin ts through out the ad ministrato r user gui de to meet FDA requi rements fo r objectiv e evidence and docum entation.
	115	This page intentiona lly left b lank.
	116	Customer S upport DR 4514
	117	Contact yo ur Local I nformation Resource Management (IRM) or Laboratory Automated Data Proc essing App lication C oordinator (ADPAC) i f you enco unter Vist A or CPRS connection problems and for tr aining sup port befor e contacti ng the VA Service De sk (SD).
	118
	119	Please e nsure loca l VistA Su pport cont act inform ation is a vailable a t all time s. Nationa l Support will engag e Enterpri se Operati ons (EO) p ersonnel a s needed.
	120
	121	Problems w ith connec tivity to VistA and CPRS may r equire per sonnel fro m EO with VBECS serv er adminis trator acc ess and Vi stA IT sup port acces s.
	122
	123	If you exp erience an FDA repor table adve rse event (patient d eath or se rious inju ry) that V BECS may h ave caused or contri buted to, contact th e Enterpri se Service Desk dire ctly to en ter a tick et for Blo od Bank so ftware sup port. Task 605697
	124
	125	If the pro blem remai ns unresol ved after local Vist A triage, contact th e national Informati on Technol ogy (IT) s upport ser vice or re quest a re gion ticke t to be re assigned t o:
	126
	127	Enterprise VA Servic e Desk Con tact
	128	See Custom er Support section o f the VBEC S n.n.n Re lease Note s (where n .n.n is th e version of the rel ease notes associate d with thi s release) .
	129	Task 5810 23
	130	Enterprise VA Servic e Desk Alt ernate Con tacts
	131	See Custom er Support section o f the VBEC S n.n.n Re lease Note s (where n .n.n is th e version of the rel ease notes associate d with thi s release) . Task 581 023
	132	This page intentiona lly left b lank.
	133
	134	VBECS Main tenance Op erations
	135
	136	These main tenance op erations a re perform ed, using the VBECS Administra tor softwa re.
	137
	138	Do not ch ange the s ystem! The U.S. Food and Drug Administra tion class ifies this software as a medic al device. Unauthori zed modifi cations wi ll render this devic e an adult erated med ical devic e under Se ction 501 of the Med ical Devic e Amendmen ts to the Federal Fo od, Drug, and Cosmet ic Act. Ac quiring an d implemen ting this software t hrough the Freedom o f Informat ion Act re quire the implemente r to assum e total re sponsibili ty for the software and become a registe red manufa cturer of a medical device, su bject to F DA regulat ions. Addi ng to or u pdating VB ECS softwa re without permissio n is prohi bited.
	139
	140	VistA dat a is treat ed as a ma ster recor d for Divi sions. Vis tA data an d Active D irectory a re treated as a mast er record for Users. If a disc repancy is found bet ween VBECS data and VistA or A ctive Dire ctory, suc h records will be di splayed as invalid a nd will re quire user intervent ion to cor rect.
	141
	142	VBECS dat a is cross reference d with Vis tA data, s o it is ve ry importa nt to make sure that the VBECS Administr ator is co nnected to the corre ct VistA a ccount (se e Figure 1 2: Example of Edit S ystem Inte rfaces – V istALink). This is w hy before connecting to VistA, the user is present ed with a VistA acco unt confir mation mes sage that contains a ll VistA a ccount inf ormation ( Figure 6 o r Figure 7 ). If the VistA acco unt is inc orrect, th e user mus t cancel t he connect ion and sp ecify the correct Vi stA accoun t in VistA Link Exter nal Interf ace settin gs. (See F igure 16 f or instruc tions on o btaining a valid Vis tA Broker IP/Port.)
	143	Prerequisi tes
	144	VistALink is install ed and run ning on th e associat ed VistA s ystem.
	145	The VistA Outbound l ogical lin ks have be en set up and starte d.
	146	The VBECS VistALink and VBECS HL7 window s services are insta lled and r unning on the applic ation serv er.
	147	The user i s defined in VistA, has a DUZ and connec tivity to VistA can be establi shed.
	148	The user h as a valid Windows a ccount and is define d as a mem ber of the VBECS Adm inistrator Active Di rectory (A D) domain group.
	149	The VBECS database i s operatio nal and up -to-date.
	150	If using a n Automate d Instrume nt interfa ce in VBEC S, the sup porting Mi ddleware s ystem with applicabl e drivers should be set up and running.
	151	Outcome
	152	The VBECS Internal a nd Externa l interfac es (Figure 9) have b een set up and start ed.
	153	VBECS user s and divi sions are defined an d users ar e able to access/use VBECS per its divis ional acce ss.
	154	Changes to verified data are c aptured fo r inclusio n in the A udit Trail Report.
	155	Limitation s and Rest rictions
	156	Only one i nstance of the VBECS Administr ator can r un at a ti me.
	157	Edit Syste m Interfac es and Edi t Division s options cannot run when VBEC S is opera tional. VB ECS cannot run when a dialog i n these op tions is o perational .
	158	Additional Informati on
	159	Refer to t he complet ed Appendi x B from t he Configu ration Wor ksheet in VBECS Appl ication In terfacing Support So ftware Ins tallation and User C onfigurati on Guide f or require d informat ion when p erforming maintenanc e operatio ns.
	160	Log into V BECS Admin istrator
	161
	162	User Actio n
	163	VBECS Admi nistrator
	164	Open a Rem ote Deskto p Connecti on.
	165	Displays t he Remote Desktop Co nnection s creen.
	166
	167
	168	Enter or s elect the name of th e VBECS Ap plication Server on the Remote Desktop C onnection (Figure 3) screen an d click Co nnect.
	169	Displays W indows Sec urity wind ow for cre dentials.
	170	Select app ropriate P IV, enter PIN, and c lick OK to enter the Remote De sktop Conn ection (Fi gure 4 and Figure 5) .
	171	Remote Des ktop Conne ction esta blishes co nnection t o target s erver. Ta rget serve r displays Warning s creen.
	172	Click OK o n the Secu rity Warni ng screen.
	173	If another message i s displaye d (about t he last ti me the use r logged i n), click OK.
	174	Displays V BECS serve r desktop with VBECS Admin Pro d and VBEC S Admin Te st icons.
	175	Double-cli ck the VBE CS Admin P rod icon.
	176	Opens VBEC S Administ rator.
	177
	178
	179	Select app ropriate P IV, enter PIN if req uested to connect to VistA (Fi gure 4, Fi gure 5 and Figure 6) when VBEC S Administ rator star ts up or a t the invo cation of any option that uses VistALink when Vist ALink is n ot connect ed.
	180	VistA acco unt confir mation mes sage is di splayed.
	181	Verify tha t correct VistA acco unt is dis played.
	182	If the Vis tA account is correc t, enter t he VistA A ccess and Verify Cod es if requ ested (Fig ure 6) and click Con nect.
	183	If the Vis tA account is incorr ect, click Cancel. S pecify the correct V istA accou nt in Vist ALink Exte rnal Inter face setti ngs (Figur e 12). Cli ck OK to r estart app lication. Go to step 5.
	184	Displays t he main VB ECS Admini strator sc reen.
	185
	186
	187
	188	NOTES
	189
	190	BR_102.06 The user m ay skip lo gging into VistALink or contin ue and log on as nee ded.
	191	BR_103.02
	192	Figure 3: Remote Des ktop Conne ction Opti ons
	193
	194	Figure 4: IAM – PIV Certificat e
	195
	196	Figure 5: ActivClien t Login
	197
	198
	199	Figure 6: Example of VistA Log on with PI V
	200
	201	Figure 7: Example of VistA Log on with Ac cess/Verif y Codes
	202
	203
	204	Figure 8: Example of VBECS Adm inistrator
	205
	206
	207	VBECS Admi nistrator Operations
	208	Edit Syste m Interfac es MUC_01
	209	The VBECS Administra tor will s et up the parameters required for connec tion to Vi stA (VistA Link and H L7 interfa ces) and D ata Innova tions Midd leware (Au tomated In strument i nterface) enabling V BECS to se nd or rece ive data f rom multip le systems where app licable.
	210
	211	Interfaces are divid ed in two groups (Fi gure 9):
	212	Internal i nterfaces (marked wi th label) are VBECS services that liste n for inco ming messa ges from e xternal in terfaces.
	213	External i nterfaces (marked wi th label) are all o ther inter faces that VBECS com municates with.
	214	Assumption s
	215	None
	216	Limitation s and Rest rictions
	217	It is reco mmended to restart t he VBECS H L7 Service and the V BECS VistA Link Servi ce on the applicatio n server i f its prop erties are changed. VBECS Admi nistrator will also try to aut omatically restart s ervices in certain s cenarios a nd will no tify the u ser if the attempt f ails (usua lly due to insuffici ent user p rivileges) . If you r eceive the service r estart fai lure messa ge, file a support t icket. See the Custo mer Suppor t section of VBECS 2 .3.0 Relea se Notes.
	218	Additional Informati on
	219	None
	220	Edit Syste m Interfac e Paramete rs
	221	User Actio n
	222	VBECS Admi nistrator
	223	Select Edi t System I nterfaces option (Fi gure 9).
	224	System dis plays the available interfaces for confi guration a nd their c onnection status:
	225
	226	MBR_4.11 I nternal VB ECS Servic es:
	227	VBECS Vist ALink Serv ice (See F igure 10)
	228	VBECS HL7 Service (S ee Figure 11)
	229
	230	MBR_4.11 E xternal In terfaces:
	231	VistALink (See Figur e 12)
	232	CPRS HL7 O ERR (See F igure 13)
	233	BCE COTS ( See Figure 14)
	234	Automated Instrument (See Figu re 15)
	235
	236	NOTES
	237
	238	MBR_4.20 A ll enabled interface s that hav e Connecti on Options are teste d for conn ectivity a nd the int erface sta tus is dis played to the user.
	239	Select an interface for config uration.
	240	MBR_4.12 S ystem allo ws the fol lowing att ributes to be config ured or ex ecuted whe re applica ble:
	241	MBR_4.08 E mail alert s: must be a valid e -mail addr ess
	242	MBR_1.01 L ocal/Exter nal Connec tion
	243	TCP/IP add ress or se rver name
	244	TCP/IP Por t Number: integer de fined in r ange 1024- 65535
	245	External F acility: 1 through 2 0-characte r identifi er for the remote si de of the CPRS HL7 O ERR and BC E COTS int erfaces.
	246	Ack Timeou t: is the number of seconds to wait for an acknowl edgement f rom the re ceiving se rver and c an be defi ned with a value fro m 1 throug h 999 seco nds.
	247	Re-transmi t Attempts : is the n umber of r etransmit attempts f or failed messages a nd can be defined wi th a value from 1 th rough 99.
	248	MBR_4.19 A ctivate/De activate i nterface s witch: whe n Off, com munication ends and no updates are queue d.
	249	Apply the changes to the inter face param eters.
	250	System sav es the cha nged param eters.
	251
	252	NOTES
	253
	254	If changes are made to the VBE CS VistALi nk Service or the VB ECS HL7 Se rvice conn ection par ameters, t hese servi ces will b e restarte d automati cally.
	255
	256	BR_2.18 Us er may can cel change s or leave screen or applicati on without applying changes. V BECS warns user that it will n ot save th e data.
	257
	258	MBR_1.14 A ll changes to previo usly verif ied data, captured f or an audi t trail re port, incl ude:
	259	Category o r transact ion
	260	Data:
	261	Name of te ch enterin g data
	262	Division
	263	Date/time originally saved
	264	Newly ente red data:
	265	Name of te ch enterin g data
	266	Division
	267	Date/time the new va lue is sav ed
	268	Repeat Ste ps 2 and 3 to config ure additi onal inter faces as a pplicable.
	269
	270	Figure 9: Example of Edit Syst em Interfa ces
	271
	272	Figure 10: Example o f Edit Sys tem Interf aces – VBE CS VistALi nk Service
	273
	274
	275	Figure 11: Example o f Edit Sys tem Interf aces – VBE CS HL7 Ser vice
	276
	277
	278	Figure 12: Example o f Edit Sys tem Interf aces – Vis tALink
	279
	280
	281	Figure 13: Example o f Edit Sys tem Interf aces – CPR S HL7 OERR
	282
	283	Figure 14: Example o f Edit Sys tem Interf aces – BCE COTS
	284
	285
	286	Figure 15: Example o f Edit Sys tem Interf aces – Aut omated Ins trument
	287
	288
	289	Figure 16: Example o f Collecti ng VistA B roker Valu es from a CPRS Short cut
	290
	291
	292	Edit Divis ions MUC_0 2
	293	The VBECS Administra tor config ures VBECS as a sing le divisio n or as mu ltidivisio nal. One o r more div isions may be define d in VBECS as local facilities (marked w ith label ) or may b e mapped ( marked wit h label) to a defin ed VBECS d ivision (s ee Figure 17). Mappe d division s (also kn own as CBO C) specify order del ivery mapp ing: if bl ood is iss ued to a m apped divi sion, all activities in VBECS associated with that order wil l be relat ed to the mapped-to defined di vision.
	294	Defined or Mapped di visions ma y be undef ined in VB ECS. All u ndefined d ivisions a re marked with MBR_2 .32 label ; this mea ns that th ey exist o nly in a V istA accou nt and are available for futur e defining or mappin g in VBECS .
	295	Assumption s
	296	The VistAL ink extern al interfa ce (see Fi gure 12) i s configur ed and val id.
	297	VistA Logo n has been executed successful ly.
	298	Limitation s and Rest rictions
	299	VBECS orde rs can onl y be mappe d to divis ions defin ed in VBEC S.
	300	BR_9.09 Wh en the div ision chan ges from f ull-servic e to trans fusion-onl y or from transfusio n-only to full-servi ce, blood units and orders mus t be in a final stat e and eXM must be di sabled.
	301	Divisions defined in VBECS mus t have at least one Level 6 (A dministrat or/Supervi sor) user assigned i n order to have acce ss to the Supervisor menu opti ons in VBE CS.
	302	When orde rs mapping is change d, VBECS H L7 Service should be restarted in order to accept these chan ges. If us er does no t have the necessary permissio ns to do t his, they will need to file a ticket wit h customer support.
	303	Additional Informati on
	304	Changes i n the mapp ing orders do not af fect deliv ered order s. Orders delivered to a VBECS division must be co mpleted, r ejected, o r canceled in that d ivision. R esubmit or ders after mapping i s complete d to send an order t o another VBECS divi sion.
	305	Add and Ma intain Div isionsTech Doc Task 1 103
	306	User Actio n
	307	VBECS Admi nistrator
	308	Select Edi t Division s (Figure 17).
	309	System dis plays each available VistA div ision with its statu s in VBECS .
	310
	311	NOTES
	312
	313	System che cks to see whether a connectio n to VistA Link is es tablished. When ther e is not a connectio n to VistA Link, the option is not availa ble.
	314
	315	MBR_2.33 I f a previo usly defin ed or mapp ed VBECS d ivision is not found in VistA, the corre sponding r ecord will be marked as Invali d. If inva lid record s are foun d, the lis t will be pre-filter ed to inva lid record s only.
	316
	317	If user ch ooses to c lear an in valid divi sion which was previ ously defi ned, it wi ll be clea red togeth er with al l user div isional ro les assign ed to that division and all or der mappin g to that division ( mapped div isions).
	318
	319	MBR_2.34 T he Divisio n Name in VBECS is s ilently sy nced with the Divisi on Name in VistA if a discrepa ncy is det ected.
	320	Select a d ivision fr om the pre sented lis t view to configure it in VBEC S (Figure 18).
	321	For an und efined div ision, the system al lows the u ser to def ine or map the divis ion (map i ts orders) to the ot her define d division .
	322
	323	For a mapp ed divisio n, the sys tem allows the user to un-map the divisi on (remove order map ping) from the other defined d ivision. A fter un-ma pping the division, the user w ill get th e undefine d status.
	324
	325	For a defi ned divisi on, the sy stem allow s the user to undefi ne the div ision in V BECS as we ll as conf iguring th e followin g paramete rs:
	326	Full Servi ce Divisio n switch: when on, d ivision is Full Serv ice; when off, divis ion is Tra nsfusion o nly (when a division is transf usion-only , VBECS di sables ele ctronic cr ossmatch).
	327	MBR_2.19As sociated F DA Registe red Facili ty
	328	Orders Map ping (CBOC )
	329	Accession Area
	330	Lock Timeo ut: lock i nactivity timeout in VBECS (ra nge 5-15)
	331	Map Orders from othe r VistA di visions no t currentl y defined in VBECS
	332	MBR_2.08 L abel Print ing (optio nal)
	333	TCP/IP add ress or se rver name
	334	MBR_2.08TC P/IP Port Number: in teger defi ned in ran ge 1024-65 535. Must match the port numbe r defined in the pri nter softw are.
	335	MBR_2.31 R eport Prin ter: Requi red select ion from a ll report printers i nstalled o n the VBEC S server. VBECS will warn the user if th e defined division d oes not ha ve the cor rect repor t printer selected.
	336	Time Zone
	337	Observing DST
	338
	339	NOTES
	340
	341	MBR_2.07 W hen undefi ning a div ision, VBE CS will wa rn the use r if the d ivision ha s any user division roles assi gned, and requires u ser confir mation bef ore contin uing. Afte r positive confirmat ion, the s ystem must remove al l assigned user role s as a par t of the U n-Defining command.
	342
	343	MBR_2.35 V BECS will warn the u ser if the defined d ivision do es not hav e a Level 6 user.
	344
	345	MBR_2.32 U ndefined V istA divis ions are a vailable f or definin g a new VB ECS divisi on or orde r mapping. One defin ed VBECS d ivision ma y have man y VistA di visions ma pped to it , but a Vi stA divisi on may be associated with only one defin ed VBECS d ivision (i .e., one-t o-many rel ation). An already m apped Vist A division cannot be used for defining a new VBECS division.
	346	Apply the changes to the divis ion parame ters.
	347	System sav es the cha nged param eters.
	348
	349	NOTES
	350
	351	BR_2.18 Us er may can cel change s or leave the scree n or appli cation wit hout apply ing change s. VBECS w arns the u ser that i t will not save the data.
	352
	353	MBR_2.09 , MBR_1.14 All change s to previ ously veri fied data, captured for an aud it trail r eport, inc lude:
	354	Category o r transact ion
	355	Data:
	356	Name of te ch enterin g data
	357	Division
	358	Date/time originally saved
	359	Newly ente red data:
	360	Name of te ch enterin g data
	361	Division
	362	Date/time the new va lue is sav ed
	363	MBR_3.21 R epeat Step s 2 and 3 for each d ivision, a s applicab le.
	364
	365	Figure 17: Example o f Select V istA Divis ion
	366
	367
	368	Figure 18: Example o f Edit Div ision
	369
	370
	371
	372
	373
	374
	375
	376	Edit Users MUC_03
	377	The VBECS Administra tor config ures VBECS users. On e or more users may be defined in VBECS (marked wi th label) or may be undefined (marked w ith label ) (see Fig ure 19). D efined use rs can use VBECS per the user’ s division al access settings. Users may have diffe rent secur ity levels for each assigned d ivision; u sers may b e restrict ed to use the divisi on as well .
	378	Undefined users exis t only in VistA acco unt and Ac tive Direc tory group and are a vailable f or future defining i n VBECS.
	379	Assumption s
	380	The VistAL ink extern al interfa ce (see Fi gure 12) i s configur ed and val id.
	381	VistA Logo n has been executed successful ly.
	382	Users to b e configur ed have be en defined as VistA Blood Bank users in VistA acco unt and as signed to the correc t Active D irectory g roup (see Figure 1). Contact a local sys tem admini strator to add or re move VBECS users fro m your VBE CS Active Directory groups.
	383	Limitation s and Rest rictions
	384	VBECS Admi nistrator caches dat a collecte d from the Active Di rectory at startup. In order t o refresh it, the ap plication must be re started.
	385	Each VBEC S user mus t have a u nique Wind ows login ID. If a W indows log in ID beco mes inacti ve and is eligible f or re-use in Active Directory, do not re -use it fo r VBECS: i t may resu lt in corr upted data in VBECS.
	386	It is not recommende d to chang e a user’s Windows l ogin ID. I f it does change, th e current user recor d will be invalidate d in VBECS Administr ator. (DR3 470)
	387	Additional Informati on
	388	MBR_3.15 E ach define d VBECS us er must ha ve a uniqu e DUZ.
	389	BR_19.04Th e VBECS Us er ID stor ed in VBEC S is the u ser’s NT L ogon ID.
	390	A VBECS Ad ministrato r/Supervis or can fur ther confi gure VBECS users in VBECS but an initial role must be define d for each VBECS use r in VBECS Administr ator. The option sho uld be use d primaril y to defin e and unde fine the u ser in VBE CS.
	391	A user’s r ole may be changed w hile they are logged into VBEC S; the cha nge takes effect the next time the user logs into VBECS.
	392	Edit VBECS Users
	393	User Actio n
	394	VBECS Admi nistrator
	395	Select Edi t Users (F igure 19).
	396	System dis plays each available VistA Blo od Bank us er (who ar e also def ined in th e appropri ate Active Directory group) wi th its sta tus in VBE CS. System displays user name and DUZ as it is def ined in Vi stA.
	397	The list i s searchab le by:
	398	VistA user name and DUZ
	399	User’s NT Logon ID
	400	Active Dir ectory use r name
	401
	402	NOTES
	403
	404	System che cks whethe r a connec tion to Vi stALink is establish ed. When t here is no a connect ion to Vis tALink, th e option i s not avai lable.
	405
	406	MBR_3.10If a previou sly define d VBECS us er is not found in V istA or Ac tive Direc tory Group , the corr esponding record wil l be marke d as Inval id. If inv alid recor ds are fou nd, the li st will be pre-filte red to inv alid recor ds only.
	407
	408	If user ch ooses to c lear an in valid user which was previousl y defined, it will b e cleared together w ith all di visional r oles.
	409
	410	MBR_3.10If a user’s name and e -mail from Active Di rectory do es not mat ch what is in VBECS, VBECS dat a will be automatica lly update d to match the Activ e Director y record.
	411
	412	The user n ame and e- mail in VB ECS are si lently syn ced with t he user’s data from Active Dir ectory if a discrepa ncy is det ected.
	413	Select a u ser for co nfiguratio n (Figure 20).
	414	For an und efined use r record, the system allows th e user to define the user in V BECS.
	415
	416	For a defi ned user, the system allows th e user to undefine t he user in VBECS as well as co nfigure th e followin g paramete rs:
	417	Mapped Win dows User: allows th e user to map the cu rrent user record to a differe nt Windows Account f rom the Ac tive Direc tory group . There is a one-to- one corres pondence b etween Win dows users and VistA users. A VistA DUZ may only b e associat ed with on e NT Logon ID and vi ce versa.
	418	Initials: A unique u ser initia l is requi red which may be 2-5 character s (alphanu meric) in length.
	419	Divisional Access: m atches div isional ac cess in Vi stA for ea ch user. A llows the user to as sign divis ional acce ss for all defined d ivisions i n VBECS.
	420
	421	NOTES
	422
	423	An invalid record mi ght hold a DUZ; clea r invalid record to re-use rel eased DUZ for defini ng a new V BECS user.
	424
	425	Invalid re cord might hold NT L ogon ID, c lear the i nvalid rec ord to re- use releas ed NT Logo n ID for d efining a new VBECS user or ma pping exis ting defin ed user to this NT L ogon ID.
	426
	427	MBR_3.24A user may n ot remove the last l evel 6 (Ad ministrato r/ Supervi sor) user from a def ined divis ion. An er ror messag e will app ear when t he last le vel 6 is b eing updat ed to a le vel 5 or l ower.
	428	Apply the changes to the user parameters .
	429	System sav es the cha nges param eters.
	430
	431	NOTES
	432
	433	BR_2.18 Us er may can cel change s or leave screen or applicati on without applying changes. V BECS warns the user that it wi ll not sav e the data .
	434
	435	BR_2.13 VB ECS associ ates the t echnologis t ID, date , time, an d division with each process f or retriev al by divi sion.
	436
	437	MBR_1.14 A ll changes to previo usly verif ied data, captured f or an audi t trail re port, incl ude:
	438	Category o r transact ion
	439	Data:
	440	Name of te ch enterin g data
	441	Division
	442	Date/time originally saved
	443	Newly ente red data:
	444	Name of te ch enterin g data
	445	Division
	446	Date/time the new va lue is sav ed
	447	MBR_3.21 R epeat Step s 2 and 3 for each u ser, as ap plicable.
	448
	449
	450	Figure 19: Example o f Select V istA User
	451
	452
	453	Figure 20: Example o f Edit Use r
	454
	455	This page intentiona lly left b lank.
	456	Index
	457
	458	C
	459	Customer S upport13
	460	H
	461	How This T echnical M anual-Secu rity Guide Is Organi zed11
	462	I
	463	Introducti onvii
	464	M
	465	Maintenanc e Operatio ns15
	466	R
	467	Related Ma nuals and Reference Materialsi x
	468	S
	469	Screen Sho ts11
	470	V
	471	VA Service Desk13
	472
	473
	474	This is th e last pag e of the V istA Blood Establish ment Compu ter Softwa re (VBECS) 2.3.0 Adm inistrator User Guid e.
	475
	476
	477
	478