Produced by Araxis Merge on 3/20/2019 1:04:43 PM Eastern 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.
# | Location | File | Last Modified |
---|---|---|---|
1 | eInsurance_IB_2.0_602.zip | IB_2_0_P602_IG (Track Changes).docx | Wed Feb 27 18:49:30 2019 UTC |
2 | eInsurance_IB_2.0_602.zip | IB_2_0_P602_IG (Track Changes).docx | Wed Mar 20 13:03:03 2019 UTC |
Description | Between Files 1 and 2 |
|
---|---|---|
Text Blocks | Lines | |
Unchanged | 1 | 766 |
Changed | 0 | 0 |
Inserted | 0 | 0 |
Removed | 0 | 0 |
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 |
No regular expressions were active.
1 | Deployment , Installa tion, Back -Out, and Rollback G uide | |
2 | Medical C are Collec tion Fund (MCCF) Ele ctronic Da ta Interch ange (EDI) Transacti on Applica tions Suit e (TAS) Ph ase 1 | |
3 | eInsurance IB*2.0*60 2 | |
4 | ||
5 | ||
6 | March 2019 | |
7 | Document V ersion 1.2 | |
8 | Department of Vetera ns Affairs | |
9 | Office of Informatio n and Tech nology (OI &T) | |
10 | ||
11 | ||
12 | Revision H istory | |
13 | Date | |
14 | Version | |
15 | Descriptio n | |
16 | Author | |
17 | 1/31/2019 | |
18 | 1.2 | |
19 | Updating f or Tech Wr iter Revie w | |
20 | Melanie Wi ndsor | |
21 | 12/12/2019 | |
22 | 1.1 | |
23 | IOC – Entr y (updated again) | |
24 | Tim Zimmer and Darle ne White | |
25 | 04/06/2018 | |
26 | 1.0 | |
27 | IOC – Entr y (was she lved for I OC testing at a late r date) | |
28 | Daniel Mor an | |
29 | March 2018 | |
30 | 0.1 | |
31 | Initial Ve rsion - Dr aft | |
32 | Daniel Mor an | |
33 | ||
34 | Artifact R ationale | |
35 | This docum ent descri bes the De ployment, Installati on, Back-o ut, and Ro llback Pla n for new products g oing into the VA Ent erprise. T he plan in cludes inf ormation a bout syste m support, issue tra cking, esc alation pr ocesses, a nd roles a nd respons ibilities involved i n all of t hese activ ities. Its purpose i s to provi de clients , stakehol ders, and support pe rsonnel a smooth tra nsition to the new p roduct or software. This docum ent should be struct ured to re flect the applicatio n of these procedure s to eithe r a single site or t o multiple sites. | |
36 | Per the Ve teran-focu sed Integr ated Proce ss (VIP) G uide, the Deployment , Installa tion, Back -out, and Rollback P lan is req uired to b e complete d prior to Critical Decision P oint #2 (C D #2), wit h the expe ctation th at it will be update d througho ut the lif ecycle of the projec t for each build, as needed. | |
37 | ||
38 | ||
39 | ||
40 | ||
41 | Table of C ontents | |
42 | 1Introduct ion1 | |
43 | 1.1Purpose 1 | |
44 | 1.2Depende ncies1 | |
45 | 1.3Constra ints1 | |
46 | 2Roles and Responsib ilities1 | |
47 | 3Deploymen t2 | |
48 | 3.1Timelin e2 | |
49 | 3.2Site Re adiness As sessment2 | |
50 | 3.2.1Deplo yment Topo logy (Targ eted Archi tecture)2 | |
51 | 3.2.2Site Informatio n (Locatio ns, Deploy ment Recip ients)3 | |
52 | 3.2.3Site Preparatio n3 | |
53 | 3.3Resourc es3 | |
54 | 3.3.1Facil ity Specif ics3 | |
55 | 3.3.2Hardw are3 | |
56 | 3.3.3Softw are3 | |
57 | 3.3.4Commu nications4 | |
58 | 3.3.4.1Dep loyment/In stallation /Back-Out Checklist4 | |
59 | 4Installat ion4 | |
60 | 4.1Pre-ins tallation and System Requireme nts4 | |
61 | 4.2Platfor m Installa tion and P reparation 5 | |
62 | 4.3Downloa d and Extr act Files5 | |
63 | 4.4Databas e Creation 5 | |
64 | 4.5Install ation Scri pts5 | |
65 | 4.6Cron Sc ripts5 | |
66 | 4.7Access Requiremen ts and Ski lls Needed for the I nstallatio n5 | |
67 | 4.8Install ation Proc edure5 | |
68 | 4.9Install ation Veri fication P rocedure5 | |
69 | 4.10System Configura tion5 | |
70 | 4.11Databa se Tuning6 | |
71 | 5Back-Out Procedure6 | |
72 | 5.1Back-Ou t Strategy 6 | |
73 | 5.2Back-Ou t Consider ations6 | |
74 | 5.2.1Load Testing6 | |
75 | 5.2.2User Acceptance Testing6 | |
76 | 5.3Back-Ou t Criteria 7 | |
77 | 5.4Back-Ou t Risks7 | |
78 | 5.5Authori ty for Bac k-Out7 | |
79 | 5.6Back-Ou t Procedur e8 | |
80 | 5.7Back-ou t Verifica tion Proce dure8 | |
81 | 6Rollback Procedure8 | |
82 | 6.1Rollbac k Consider ations8 | |
83 | 6.2Rollbac k Criteria 8 | |
84 | 6.3Rollbac k Risks9 | |
85 | 6.4Authori ty for Rol lback9 | |
86 | 6.5Rollbac k Procedur e9 | |
87 | 6.6Rollbac k Verifica tion Proce dure9 | |
88 | ||
89 | Table of T ables | |
90 | Table 1: D eployment, Installat ion, Back- out, and R ollback Ro les and Re sponsibili ties1 | |
91 | Table 2: S ite Prepar ation3 | |
92 | Table 3: F acility-Sp ecific Fea tures3 | |
93 | Table 4: H ardware Sp ecificatio ns3 | |
94 | Table 5: S oftware Sp ecificatio ns4 | |
95 | Table 6: D eployment/ Installati on/Back-Ou t Checklis t4 | |
96 | ||
97 | ||
98 | ||
99 | Introducti on | |
100 | This docum ent descri bes how to deploy an d install the IB*2.0 *602 patch and how t o back-out the produ ct and rol lback to a previous version or data set. | |
101 | Purpose | |
102 | The purpos e of this plan is to provide a single, c ommon docu ment that describes how, when, where, an d to whom IB*2.0*602 will be d eployed an d installe d, as well as how th e patches are to be backed out and rolle d back, if necessary . The plan also iden tifies res ources, co mmunicatio ns plan, a nd rollout schedule. Specific instructio ns for ins tallation, back-out, and rollb ack are in cluded in this docum ent. | |
103 | Dependenci es | |
104 | The follow ing patche s must be installed before IB* 2.0*602: | |
105 | IB*2*621 | |
106 | ||
107 | Constraint s | |
108 | This patch is intend ed for a f ully patch ed VistA s ystem. | |
109 | Roles and Responsibi lities | |
110 | Table 1: D eployment, Installat ion, Back- out, and R ollback Ro les and Re sponsibili ties | |
111 | ID | |
112 | Team | |
113 | Phase / Ro le | |
114 | Tasks | |
115 | Project Ph ase (See S chedule) | |
116 | 1 | |
117 | VA OI&T, V A OI&T Hea lth Produc t Support & PMO (Lei dos) | |
118 | Deployment | |
119 | Plan and s chedule de ployment ( including orchestrat ion with v endors) | |
120 | Planning | |
121 | 2 | |
122 | Local VAMC and CPAC processes | |
123 | ||
124 | ||
125 | Deployment | |
126 | Determine and docume nt the rol es and res ponsibilit ies of tho se involve d in the d eployment. | |
127 | Planning | |
128 | 3 | |
129 | Field Test ing (Initi al Operati ng Capabil ity (IOC)) , Health P roduct Sup port Testi ng & VIP R elease Age nt Approva l | |
130 | Deployment | |
131 | Test for o perational readiness | |
132 | Testing | |
133 | 4 | |
134 | Health Pro duct Suppo rt and Fie ld Operati ons | |
135 | Deployment | |
136 | Execute de ployment | |
137 | Deployment | |
138 | 5 | |
139 | Individual Veterans Affairs Me dical Cent ers (VAMCs ) | |
140 | Installati on | |
141 | Plan and s chedule in stallation | |
142 | Deployment | |
143 | 6 | |
144 | VIP Relea se Agent | |
145 | Installati on | |
146 | Ensure aut hority to operate an d that cer tificate a uthority s ecurity do cumentatio n is in pl ace | |
147 | Deployment | |
148 | 7 | |
149 | N/A for th is patch a s we are u sing only the existi ng VistA s ystem | |
150 | Installati on | |
151 | Validate t hrough fac ility POC to ensure that IT eq uipment ha s been acc epted usin g asset in ventory pr ocesses | |
152 | N/A | |
153 | 8 | |
154 | VA’s eBusi ness team | |
155 | Installati on | |
156 | Coordinate training | |
157 | Deployment | |
158 | 9 | |
159 | VIP releas e Agent, H ealth Prod uct Suppor t & the de velopment team | |
160 | Back-out | |
161 | Confirm av ailability of back-o ut instruc tions and back-out s trategy (w hat are th e criteria that trig ger a back -out) | |
162 | Deployment | |
163 | 10 | |
164 | No changes to curren t process – we are u sing the e xisting Vi stA system | |
165 | Post Deplo yment | |
166 | Hardware, Software a nd System Support | |
167 | Warranty | |
168 | Deployment | |
169 | The deploy ment is pl anned as a national rollout. | |
170 | This secti on provide s the sche dule and m ilestones for the de ployment. | |
171 | Timeline | |
172 | The deploy ment and i nstallatio n is sched uled to ru n for 30 d ays, as de picted in the master deploymen t schedule . | |
173 | Site Readi ness Asses sment | |
174 | This secti on discuss es the loc ations tha t will rec eive the I B*2.0*602 deployment . | |
175 | Deployment Topology (Targeted Architectu re) | |
176 | This patch IB*2.0*60 2 is to be nationall y released to all VA MCs. | |
177 | Site Infor mation (Lo cations, D eployment Recipients ) | |
178 | The test s ites for I OC testing are: TBD | |
179 | These site s will not be define d here unt il the sit es have si gned the M emorandum of Underst anding (MO Us) and te sting has completed as sometim es a site has to sto p testing prior to t he end of IOC. | |
180 | ||
181 | Upon natio nal releas e all VAMC s are expe cted to in stall this patch wit hin the co mpliance d ates. | |
182 | Site Prepa ration | |
183 | The follow ing table describes preparatio n required by the si te prior t o deployme nt. | |
184 | Table 2: S ite Prepar ation | |
185 | Site/Other | |
186 | Problem/Ch ange Neede d | |
187 | Features t o Adapt/Mo dify to Ne w Product | |
188 | Actions/St eps | |
189 | Owner | |
190 | N/A | |
191 | N/A | |
192 | N/A | |
193 | N/A | |
194 | N/A | |
195 | Resources | |
196 | Facility S pecifics | |
197 | The follow ing table lists faci lity-speci fic featur es require d for depl oyment. | |
198 | Table 3: F acility-Sp ecific Fea tures | |
199 | Site | |
200 | Space/Room | |
201 | Features N eeded | |
202 | Other | |
203 | N/A | |
204 | N/A | |
205 | N/A | |
206 | N/A | |
207 | Hardware | |
208 | The follow ing table describes hardware s pecificati ons requir ed at each site prio r to deplo yment. | |
209 | Table 4: H ardware Sp ecificatio ns | |
210 | Required H ardware | |
211 | Model | |
212 | Version | |
213 | Configurat ion | |
214 | Manufactur er | |
215 | Other | |
216 | Existing V istA syste m | |
217 | N/A | |
218 | N/A | |
219 | N/A | |
220 | N/A | |
221 | N/A | |
222 | Please see the Roles and Respo nsibilitie s table in Section 2 for detai ls about w ho is resp onsible fo r preparin g the site to meet t hese hardw are specif ications. | |
223 | Software | |
224 | The follow ing table describes software s pecificati ons requir ed at each site prio r to deplo yment. | |
225 | Table 5: S oftware Sp ecificatio ns | |
226 | Required S oftware | |
227 | Make | |
228 | Version | |
229 | Configurat ion | |
230 | Manufactur er | |
231 | Other | |
232 | Fully patc hed Integr ated Billi ng package within Vi stA | |
233 | N/A | |
234 | 2.0 | |
235 | N/A | |
236 | N/A | |
237 | N/A | |
238 | IB*2*621 | |
239 | N/A | |
240 | Nationally released version | |
241 | N/A | |
242 | N/A | |
243 | N/A | |
244 | Please see the Roles and Respo nsibilitie s table in Section 2 above for details a bout who i s responsi ble for pr eparing th e site to meet these software specificat ions. | |
245 | Communicat ions | |
246 | The sites that are p articipati ng in fiel d testing (IOC) will use the “ Patch Trac king” mess age in Out look to co mmunicate with the e Business e Insurance sub-team, the develo pers, and product su pport pers onnel. | |
247 | Deployment /Installat ion/Back-O ut Checkli st | |
248 | The Releas e Manageme nt team wi ll deploy the patch IB*2.0*602 , which is tracked i n the Nati onal Patch Module (N PM) in For um, nation ally to al l VAMCs. F orum autom atically t racks the patches as they are installed in the dif ferent VAM C producti on systems . One can run a repo rt in Foru m to ident ify when a nd by whom the patch was insta lled in th e VistA pr oduction a t each sit e. A repor t can also be run to identify which site s have not currently installed the patch in their VistA prod uction sys tems. Ther efore, thi s informat ion does n ot need to be manual ly tracked in the ch art below. | |
249 | Table 6: D eployment/ Installati on/Back-Ou t Checklis t | |
250 | Activity | |
251 | Day | |
252 | Time | |
253 | Individual who compl eted task | |
254 | Deploy | |
255 | N/A | |
256 | N/A | |
257 | N/A | |
258 | Install | |
259 | N/A | |
260 | N/A | |
261 | N/A | |
262 | Back-Out | |
263 | N/A | |
264 | N/A | |
265 | N/A | |
266 | ||
267 | Installati on | |
268 | Pre-instal lation and System Re quirements | |
269 | IB*2.0*602 , a patch to the exi sting Vist A Integrat ed Billing 2.0 packa ge, is ins tallable o n a fully patched M( UMPS) Vist A system a nd operate s on top o f the Vist A environm ent provid ed by the VistA infr astructure packages. The latte r provides utilities which com municate w ith the un derlying o perating s ystem and hardware, providing Integrated Billing i ndependenc e from var iations in hardware and operat ing system . | |
270 | Platform I nstallatio n and Prep aration | |
271 | Refer to t he IB*2.0* 602 docume ntation on the Natio nal Patch Module (NP M) on Foru m for the detailed i nstallatio n instruct ions. Thes e instruct ions will include an y pre inst allation s teps if ap plicable. | |
272 | Download a nd Extract Files | |
273 | Refer to t he IB*2.0* 602 docume ntation on the NPM t o find the location of related documenta tion that can be dow nloaded. I B*2.0*602 will be tr ansmitted via a Pack Man messag e and can be pulled from the N PM. It is not a hos t file, an d therefor e does not need to b e download ed separat ely. | |
274 | Database C reation | |
275 | IB*2.0*602 does NOT modify the VistA dat abase. | |
276 | Installati on Scripts | |
277 | No install ation scri pts are ne eded for I B*2.0*602 installati on. | |
278 | Cron Scrip ts | |
279 | No Cron sc ripts are needed for IB*2.0*60 2 installa tion. | |
280 | Access Req uirements and Skills Needed fo r the Inst allation | |
281 | The follow ing staff need acces s to the P ackMan mes sage conta ining the IB*2.0*602 patch or Forum’s NP M in order to downlo ad the nat ionally re leased IB* 2.0*602 pa tch. The s oftware is to be ins talled by the sites or regions designate d: VA OI&T IT OPERAT IONS SERVI CE, Enterp rise Servi ce Lines, and/or Vis tA Applica tions Divi sion. | |
282 | Installati on Procedu re | |
283 | Refer to t he IB*2.0* 602 docume ntation on the NPM f or the det ailed inst allation i nstruction s. | |
284 | Installati on Verific ation Proc edure | |
285 | Refer to t he IB*2.0* 602 docume ntation on the NPM f or detaile d installa tion instr uctions. T hese instr uctions in clude any post insta llation st eps if app licable. | |
286 | System Con figuration | |
287 | No system configurat ion change s are requ ired for t his patch. | |
288 | Database T uning | |
289 | No reconfi guration o f the Vist A database , memory a llocations or other resources is necessa ry. | |
290 | Back-Out P rocedure | |
291 | Back-Out p ertains to a return to the las t known va lid instan ce of oper ational so ftware and platform settings. | |
292 | Back-Out S trategy | |
293 | Although i t is unlik ely, due t o care in collecting , elaborat ing, and d esigning a pproved us er stories , followed by multip le testing stages (D eveloper U nit Testin g, Compone nt Integra tion Testi ng, SQA Te sting, and User Acce ptance Tes ting), a b ack-out de cision due to major issues wit h this pat ch could o ccur durin g site Mir ror Testin g, Site Pr oduction T esting or after Nati onal Relea se to the field (VAM Cs). The best strat egy is dep endent on the stage during whi ch the dec ision is m ade. | |
294 | ||
295 | If during Mirror tes ting or Si te Product ion Testin g, a new v ersion of a defect c orrecting test patch is produc ed, retest ed and suc cessfully passes dev elopment t eam testin g, it woul d be resub mitted to the site f or testing . If the p atch produ ced catast rophic pro blems, a n ew version of the pa tch can be used to r estore the build com ponents to their pre -patch con dition. | |
296 | ||
297 | If the def ect(s) wer e not disc overed unt il after n ational re lease but during the designate d support period, a new patch will be en tered into the Natio nal Patch Module on Forum and go through all the n ecessary m ilestone r eviews etc ., as a pa tch for a patch. It is up to V A OI&T and product s upport whe ther this new patch would be d efined as an emergen cy patch o r not. Thi s new patc h could be used to a ddress spe cific issu es pertain ing to the original patch or c ould be us ed to rest ore the bu ild compon ents to th eir origin al pre-pat ch conditi on. | |
298 | ||
299 | After the support pe riod, the VistA Main tenance Pr ogram woul d produce the new pa tch, eithe r to corre ct the def ective com ponents or to back-o ut the pat ch. | |
300 | Back-Out C onsiderati ons | |
301 | It is nece ssary to d etermine i f a wholes ale back-o ut of the patch IB*2 .0*602 is needed or if a bette r course o f action i s to corre ct through a new ver sion of th e patch (i f prior to national release) o r through a subseque nt patch a imed at sp ecific are as modifie d or affec ted by the original patch (aft er nationa l release) . A whole sale back- out of the patch wil l still re quire a ne w version (if prior to nationa l release) or a subs equent pat ch (after national r elease). If the bac k-out is p ost-releas e of this patch IB*2 .0*602, th is patch s hould be a ssigned st atus of “E ntered in Error” in Forum’s NP M. | |
302 | Load Testi ng | |
303 | N/A. The b ack-out pr ocess if n ecessary i s executed at normal , rather t han raised job prior ity, and i s expected to have n o signific ant effect on total system per formance. Subsequent to the re version, t he perform ance deman ds on the system wou ld be unch anged. | |
304 | User Accep tance Test ing | |
305 | Added the ability fo r a VistA user to ex pire all s ubscriber policies a ttached to an insura nce group plan witho ut the nee d to move them to an other plan . The user can also choose to inactivate the plan after the expiration process h as complet ed. A bull etin detai ling the c hanges is sent to bo th the use r initiati ng the pro cess and t he “IB NEW INSURANCE ” mail gro up. A new option was added, “E xpire Grou p Plan” [I BCN EXPIRE GROUP SUB SCRIBERS] with synon ym [XPIR] to the PAT IENT INSUR ANCE MENU [IBCN INSU RANCE MGMT MENU]. | |
306 | ||
307 | Adjusted t he VistA T hird Party Joint Inq uiry optio n (TPJI) t o correctl y display the date o f death (D oD) inform ation in t he header so it is n o longer t runcated w hen the pa tient name is long. | |
308 | ||
309 | Enhanced t hese Excel formatted reports t o include the same i dentifying header in formation (other tha n “Page:” and page n umber) as their repo rt formatt ed counter parts: | |
310 | ||
311 | “eIV Payer Link Repo rt” [IBCNE IIV PAYER LINK REPO RT] | |
312 | “eIV Respo nse Report ” [IBCNE I IV RESPONS E REPORT] | |
313 | “Insurance Buffer Ac tivity” [I BCN OUTPUT INS BUFF ACTIVITY] | |
314 | “Insurance Buffer Em ployee” [I BCN OUTPUT INS BUFF EMPLOYEE] | |
315 | “Verificat ion of No Coverage R eport” [IB CN NO COVE RAGE VERIF IED] | |
316 | “User Edit Report” [ IBCN USER EDIT RPT] | |
317 | “Generate Insurance Company Li stings” [I BCN ID DUP INSURANCE ENTRIES] | |
318 | “List New Not Verifi ed Policie s” [IBCN L IST NEW NO T VER] | |
319 | ||
320 | Adjusted t he VistA s oftware th at purges eIV relate d inquirie s and resp onses to c orrectly c alculate t he earlies t possible purge dat e to displ ay to the user. The IIV TRANSM ISSION QUE UE (#365.1 ) file (TQ ) records linked to IIV Respon se File (# 365) recor ds whose “ Do Not Pur ge” field (#365, .11 ) is set t o “1” (Yes ) will no longer be considered . Additio nally, whe n examinin g IIV Resp onse File (#365) rec ords for p urging, Vi stA was mo dified to remove res ponses tha t have a T Q pointer that point s to a non -existent TQ record. | |
321 | ||
322 | Adjusted t he VistA s oftware fo r the Fee Patient In quiry [FBA A PATIENT INQUIRY] o ption, Pre register a Patient [ DGPRE PRE- REGISTER O PTION] opt ion and Re gister a P atient [DG REGISTER PATIENT] o ption to v erify the proper fie ld size fo r the Medi care (WNR) Subscribe r ID and d escribe th ose requir ements for the user via help t ext. | |
323 | ||
324 | Back-Out C riteria | |
325 | The projec t is cance led or the requested changes i mplemented by IB*2.0 *602 are n o longer d esired by VA OI&T an d the eBus iness eIns urance sub -team, or the patch produces c atastrophi c problems . | |
326 | Back-Out R isks | |
327 | Since the eInsurance software is tightly integrate d with ext ernal syst ems, any a ttempt at a back-out should in clude clos e consulta tion with the extern al trading partners such as th e Financia l Services Center (F SC) and th e Health C are Cleari ng House ( HCCH) to d etermine r isk. | |
328 | Authority for Back-O ut | |
329 | Any back-o ut decisio n should b e a joint decision o f the Busi ness Owner (or their represent ative) and the Progr am Manager with inpu t from the Health Pr oduct Supp ort (HPS) Applicatio n Coordina tor, devel opers (bot h project and Tier 3 HPS), and if approp riate, ext ernal trad ing partne rs such as the VA Fi nancial Se rvice Cent er (FSC) o r Health C are Cleari nghouse. | |
330 | ||
331 | eInsurance is tightl y integrat ed with th ese extern al partner s and a ba ck-out of the patch should not be a stan dalone dec ision. | |
332 | Back-Out P rocedure | |
333 | The back-o ut plan fo r VistA ap plications is comple x and not a “one siz e fits all ” solution . The gene ral strate gy for a V istA back- out is to repair the code with a follow- up patch. The develo pment team recommend s that sit es log a t icket if i t is a nat ionally re leased pat ch. | |
334 | ||
335 | Back-Out P rocedure p rior to Na tional Rel ease. If i t is prior to nation al release , the site will be a lready wor king direc tly with t he develop ment team daily and should con tact that team. The developmen t team mem bers will have been identified in the In itial Oper ating Capa bility (IO C) Memoran dum of Und erstanding (MOU). A s discusse d in secti on 5.2, it is likely that deve lopment te am can qui ckly addre ss via a n ew softwar e version. If the si te is unsu re who to contact th ey may log a ticket of contact Health Pr oduct Supp ort - Mana gement Sys tems Team. | |
336 | ||
337 | The IB*2.0 *602 patch contains the follow ing build components . | |
338 | Enhancemen ts | |
339 | Routines | |
340 | Options | |
341 | ||
342 | While the VistA inst allation p rocedure o f the KIDS build all ows the in staller to back up t he modifie d routines using the ‘Backup a Transport Global’ a ction, due to the co mplexity o f this pat ch, it is not recomm ended for back-out, and a rest ore from a backup of the Trans port Globa l should n ot be atte mpted. In the event that a si te decides to back o ut this pa tch, the s ite should contact t he Nationa l Service Desk (NSD) to submit a help de sk ticket. The devel opment tea m will nee d to issue a follow- on patch i n order to comprehen sively bac k-out this patch and /or to cle an up corr upted data /remove da ta diction ary change s, if need ed and res tore the s ystem to a functioni ng state. | |
343 | ||
344 | Please con tact the E PMO team f or assista nce since this insta lled patch contains components in additi on to rout ines. | |
345 | Back-out V erificatio n Procedur e | |
346 | Successful back-out is confirm ed by veri fication t hat the ba ck-out pat ch was suc cessfully installed. | |
347 | Rollback P rocedure | |
348 | Rollback p ertains to data. The only data changes i n this pat ch are spe cific to t he operati onal softw are and pl atform set tings and they are c overed in the Back-o ut procedu res detail ed elsewhe re in this document. | |
349 | Rollback C onsiderati ons | |
350 | Not applic able. | |
351 | Rollback C riteria | |
352 | Not applic able. | |
353 | Rollback R isks | |
354 | Not applic able. | |
355 | Authority for Rollba ck | |
356 | Not applic able. | |
357 | Rollback P rocedure | |
358 | Not applic able. | |
359 | Rollback V erificatio n Procedur e | |
360 | Not applic able. | |
361 | ||
362 | Template R evision Hi story | |
363 | Date | |
364 | Version | |
365 | Descriptio n | |
366 | Author | |
367 | March 2016 | |
368 | 2.2 | |
369 | Changed th e title fr om Install ation, Bac k-Out, and Rollback Guide to D eployment and Instal lation Gui de, with t he underst anding tha t Back-Out and Rollb ack belong with Inst allation. | |
370 | VIP Team | |
371 | February 2 016 | |
372 | 2.1 | |
373 | Changed ti tle from I nstallatio n, Back-Ou t, and Rol lback Plan to Instal lation, Ba ck-Out, an d Rollback Guide as recommende d by OI&T Documentat ion Standa rds Commit tee | |
374 | OI&T Docum entation S tandards C ommittee | |
375 | December 2 015 | |
376 | 2.0 | |
377 | The OI&T D ocumentati on Standar ds Committ ee merged the existi ng “Instal lation, Ba ck-Out, Ro llback Pla n” templat e with the content r equirement s in the O I&T End-us er Documen tation Sta ndards for a more co mprehensiv e Installa tion Plan. | |
378 | OI&T Docum entation S tandards C ommittee | |
379 | February 2 015 | |
380 | 1.0 | |
381 | Initial Dr aft | |
382 | Lifecycle and Releas e Manageme nt | |
383 |
Araxis Merge (but not the data content of this report) is Copyright © 1993-2016 Araxis Ltd (www.araxis.com). All rights reserved.