19. EPMO Open Source Coordination Office Redaction File Detail Report

Produced by Araxis Merge on 9/19/2018 12:35:17 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.

19.1 Files compared

#	Location	File	Last Modified
1	ePharmacy_Bundle 12.zip	TAS ePhm SDD US586 v1.00.docx	Wed Sep 12 15:17:00 2018 UTC
2	ePharmacy_Bundle 12.zip	TAS ePhm SDD US586 v1.00.docx	Tue Sep 18 17:36:34 2018 UTC

19.2 Comparison summary

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

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

19.4 Active regular expressions

No regular expressions were active.

19.5 Comparison detail

	1	MCCF EDI T AS US586
	2	System Des ign Docume nt
	3
	4
	5
	6
	7
	8	Department of Vetera ns Affairs
	9	January 20 18
	10	Version 1. 00
	11	User Story Number:
	12	User Story Name:
	13	Product Ba cklog ID:
	14	Priority:
	15	Initial Si zing Estim ate: 5
	16	Rational I D:
	17	Rally ID: US586
	18	Epic Taxon omy: Updat e
	19
	20	Design – S ummary
	21
	22
	23	List of Co mponents:
	24	File:
	25	Routine:
	26
	27
	28	Design – D etail
	29
	30
	31
	32	Subroutine Name
	33
	34	Enhancemen t Category
	35	New
	36	Modify
	37
	38
	39	Related Me nu Options or ListMa n Actions
	40	Optional – include i f helpful, otherwise delete th is row.
	41	Routines W hich Call This Subro utine
	42	Optional – include i f helpful, otherwise delete th is row.
	43	Calls to O ther Packa ges
	44	Optional – include i f there ar e any call s to other packages, otherwise delete th is row.
	45	New Integr ation Cont rol Regist rations (I CRs)
	46	Optional – include i f any new ICRs, othe rwise dele te this ro w.
	47	Current Lo gic
	48
	49
	50
	51	Modified L ogic (Chan ges are hi ghlighted)
	52
	53
	54
	55
	56
	57
	58
	59	Integratio n Control Registrati on #
	60
	61	Name
	62
	63	Enhancemen t Category
	64	New Modify Expand
	65	Custodial Package
	66
	67	Subscribin g Package( s)
	68
	69	Usage
	70	Controlled Subscript ion
	71	Type
	72	Routine
	73	Routine
	74
	75	Component
	76
	77	Input Vari ables
	78	Name:
	79	Descriptio n:
	80	Output Var iables
	81	Name:
	82	Descriptio n:
	83
	84
	85
	86	For descri bing how t o add a fi le to the build:
	87
	88	File Name
	89
	90	Send Full or Partial DD
	91
	92	Update the Data Dict ionary
	93
	94	Send Secur ity Codes
	95
	96	Screen to Determine DD Update
	97
	98	Data Comes with File
	99
	100	Site’s Dat a
	101
	102	Resolve Po inters
	103
	104	May User O verride Da ta Update
	105
	106	Data List
	107
	108	Screen to Select Dat a
	109
	110
	111
	112
	113	For adding /modifying a field o n a DD:
	114
	115	Field Attr ibutes
	116	Values
	117	FIELD NAME
	118
	119	FIELD NUMB ER
	120
	121	NODE;PIECE
	122
	123	FIELD TYPE
	124
	125	FIELD LENG TH
	126
	127	INPUT TRAN SFORM
	128
	129	HELP PROMP T
	130
	131	DESCRIPTIO N
	132
	133	TECHNICAL DESCRIPTIO N
	134
	135
	136
	137	For adding /modifying an ACTION protocol:
	138
	139	Field Attr ibutes
	140	Values
	141	NAME
	142
	143	ITEM TEXT
	144
	145	DESCRIPTIO N
	146
	147	TYPE
	148
	149	PACKAGE
	150
	151	ENTRY ACTI ON
	152
	153
	154
	155	For adding /modifying a MENU pr otocol:
	156
	157	Field Attr ibutes
	158	Values
	159	NAME
	160
	161	ITEM TEXT
	162
	163	DESCRIPTIO N
	164
	165	TYPE
	166
	167	PACKAGE
	168
	169	COLUMN WID TH
	170
	171	MNEMONIC W IDTH
	172
	173	MENU PROMP T
	174
	175	ITEM
	176	MNEMONIC
	177	SEQUENCE
	178
	179
	180
	181
	182
	183
	184
	185
	186
	187
	188
	189	Back Out/R ollback Pr ocedure
	190	A descript ion of how the above changes c ould be ba cked out o f a system after bei ng loaded, and how a ny data ch anges can be rolled back to th e previous state.
	191	Sample lan guage:
	192
	193	This story does not include ad ding or ch anging dat a fields i n any Vist A files, s o no rollb ack of dat a would be necessary if this e nhancement needed to be backed out.
	194
	195	To back ou t this enh ancement, the routin es ^abcd s hould be b acked up p rior to in stalling t his patch. Reverting to the pr evious ver sions of t hese routi nes would back out t his enhanc ement. Alt ernatively , the prev ious versi ons of the se routine s could be distribut ed via an emergency patch.
	196
	197
	198
	199