Produced by Araxis Merge on 2/27/2019 2:32:40 PM Eastern Standard Time. See www.araxis.com for information about Merge. This report uses XHTML and CSS2, and is best viewed with a modern standards-compliant browser. For optimum results when printing this report, use landscape orientation and enable printing of background images and colours in your browser.
# | Location | File | Last Modified |
---|---|---|---|
1 | MCCF_EDI_TAS_P2_PRCA_4_5_332.zip\MCCF_EDI_TAS_P2_PRCA_4_5_332\PRCA_4_5_332_IB_2_0_633.zip | prca_4_5_332_ig.docx | Wed Jan 9 19:00:38 2019 UTC |
2 | MCCF_EDI_TAS_P2_PRCA_4_5_332.zip\MCCF_EDI_TAS_P2_PRCA_4_5_332\PRCA_4_5_332_IB_2_0_633.zip | prca_4_5_332_ig.docx | Tue Feb 26 14:52:15 2019 UTC |
Description | Between Files 1 and 2 |
|
---|---|---|
Text Blocks | Lines | |
Unchanged | 3 | 1070 |
Changed | 2 | 6 |
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 | Medical Ca re Collect ion Fund ( MCCF) Elec tronic Dat a Intercha nge (EDI) Transactio n Applicat ions Suite (TAS) ePa yments Bui ld 7 & 8 | |
2 | Accounts R eceivable PRCA*4.5*3 32 | |
3 | Integrated Billing I B*2.0*633 | |
4 | Version 1. 0 | |
5 | Deployment , Installa tion, Back -Out, and Rollback G uide | |
6 | ||
7 | ||
8 | December 2 018 | |
9 | Department of Vetera ns Affairs | |
10 | Office of Informatio n and Tech nology (OI &T) | |
11 | ||
12 | ||
13 | Revision H istory | |
14 | Date | |
15 | Version | |
16 | Descriptio n | |
17 | Author | |
18 | December 2 018 | |
19 | 1.0 | |
20 | Initial Ve rsion | |
21 | Fred Altma n | |
22 | ||
23 | Artifact R ationale | |
24 | 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 thos e activiti es. Its pu rpose is t o provide clients, s takeholder s, and sup port perso nnel with a smooth t ransition to the new product o r software , and shou ld be stru ctured app ropriately , to refle ct particu lars of th ese proced ures at a single or at multipl e location s. | |
25 | 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. | |
26 | ||
27 | ||
28 | ||
29 | ||
30 | Table of C ontents | |
31 | 1Introduct ion1 | |
32 | 1.1Purpose 1 | |
33 | 1.2Depende ncies1 | |
34 | 1.3Constra ints1 | |
35 | 2Roles and Responsib ilities1 | |
36 | 3Deploymen t2 | |
37 | 3.1Timelin e2 | |
38 | 3.2Site Re adiness As sessment3 | |
39 | 3.2.1Deplo yment Topo logy (Targ eted Archi tecture)3 | |
40 | 3.2.2Site Informatio n (Locatio ns, Deploy ment Recip ients)3 | |
41 | 3.2.3Site Preparatio n3 | |
42 | 3.3Resourc es3 | |
43 | 3.3.1Facil ity Specif ics3 | |
44 | 3.3.2Hardw are3 | |
45 | 3.3.3Softw are4 | |
46 | 3.3.4Commu nications5 | |
47 | 3.3.4.1Dep loyment/In stallation /Back-Out Checklist5 | |
48 | 4Installat ion5 | |
49 | 4.1Pre-ins tallation and System Requireme nts5 | |
50 | 4.2Platfor m Installa tion and P reparation 5 | |
51 | 4.3Downloa d and Extr act Files6 | |
52 | 4.4Databas e Creation 6 | |
53 | 4.5Install ation Scri pts6 | |
54 | 4.6Cron Sc ripts6 | |
55 | 4.7Access Requiremen ts and Ski lls Needed for the I nstallatio n6 | |
56 | 4.8Install ation Proc edure7 | |
57 | 4.9Install ation Veri fication P rocedure7 | |
58 | 4.10System Configura tion7 | |
59 | 4.11Databa se Tuning7 | |
60 | 5Back-Out Procedure7 | |
61 | 5.1Back-Ou t Strategy 7 | |
62 | 5.1.1Mirro r Testing or Site Pr oduction T esting7 | |
63 | 5.1.2After National Release bu t During t he Designa ted Suppor t Period7 | |
64 | 5.1.3After National Release an d Warranty Period7 | |
65 | 5.2Back-Ou t Consider ations8 | |
66 | 5.2.1Load Testing8 | |
67 | 5.2.2User Acceptance Testing8 | |
68 | 5.3Back-Ou t Criteria 13 | |
69 | 5.4Back-Ou t Risks13 | |
70 | 5.5Authori ty for Bac k-Out13 | |
71 | 5.6Back-Ou t Procedur e13 | |
72 | 5.7Back-ou t Verifica tion Proce dure14 | |
73 | 6Rollback Procedure1 4 | |
74 | 6.1Rollbac k Consider ations14 | |
75 | 6.2Rollbac k Criteria 14 | |
76 | 6.3Rollbac k Risks14 | |
77 | 6.4Authori ty for Rol lback14 | |
78 | 6.5Rollbac k Procedur e14 | |
79 | 6.6Rollbac k Verifica tion Proce dure14 | |
80 | ||
81 | ||
82 | ||
83 | ||
84 | Table of T ables | |
85 | Table 1: D eployment, Installat ion, Back- out, and R ollback Ro les and Re sponsibili ties1 | |
86 | Table 2: S ite Prepar ation3 | |
87 | Table 3: F acility-Sp ecific Fea tures3 | |
88 | Table 4: H ardware Sp ecificatio ns3 | |
89 | Table 5: S oftware Sp ecificatio ns4 | |
90 | Table 6: D eployment/ Installati on/Back-Ou t Checklis t5 | |
91 | ||
92 | ||
93 | ||
94 | Introducti on | |
95 | This docum ent descri bes how to deploy an d install the multi- build (whi ch include s patches PRCA*4.5*3 32 and IB* 2.0*633) a s well as how to bac k-out the product an d rollback to a prev ious versi on or data set. | |
96 | Purpose | |
97 | The purpos e of this plan is to provide a single, c ommon docu ment that describes how, when, where, an d to whom the multi- build PRCA IB EPAYME NTS BUNDLE 4.0 (whic h includes patches P RCA*4.5*33 2 and IB*2 .0*633) wi ll be depl oyed and i nstalled, as well as how the p atches are to be bac ked out an d rolled b ack, if ne cessary. T he plan al so identif ies resour ces, commu nications plan, and rollout sc hedule. Sp ecific ins tructions for instal lation, ba ck-out, an d rollback are inclu ded in thi s document . | |
98 | Dependenci es | |
99 | The follow ing patche s must be installed before PRC A*4.5*332 and IB*2.0 *633: | |
100 | PRCA*4.5*3 26 | |
101 | PRCA*4.5*3 15 | |
102 | PRCA*4.5*3 19 | |
103 | IB*2.0*516 | |
104 | IB*2.0*609 | |
105 | Constraint s | |
106 | This patch is intend ed for a f ully patch ed VistA s ystem. | |
107 | Roles and Responsibi lities | |
108 | Table 1: D eployment, Installat ion, Back- out, and R ollback Ro les and Re sponsibili ties | |
109 | ID | |
110 | Team | |
111 | Phase / Ro le | |
112 | Tasks | |
113 | Project Ph ase (See S chedule) | |
114 | 1 | |
115 | VA OI&T, V A OI&T Hea lth Produc t Support& PMO (Leid os) | |
116 | Deployment | |
117 | Plan and s chedule de ployment ( including orchestrat ion with v endors) | |
118 | Planning | |
119 | 2 | |
120 | Local VAMC and CPAC processes | |
121 | ||
122 | ||
123 | Deployment | |
124 | Determine and docume nt the rol es and res ponsibilit ies of tho se involve d in the d eployment. | |
125 | Planning | |
126 | 3 | |
127 | Field Test ing (Initi al Operati ng Capabil ity - IOC) , Health P roduct Sup port Testi ng & VIP R elease Age nt Approva l | |
128 | Deployment | |
129 | Test for o perational readiness | |
130 | Testing | |
131 | 4 | |
132 | Health Pro duct Suppo rt and Fie ld Operati ons | |
133 | Deployment | |
134 | Execute de ployment | |
135 | Deployment | |
136 | 5 | |
137 | Individual Veterans Administra tion Medic al Centers (VAMCs) | |
138 | Installati on | |
139 | Plan and s chedule in stallation | |
140 | Deployment | |
141 | 6 | |
142 | VIP Relea se Agent | |
143 | Installati on | |
144 | Ensure aut hority to operate an d that cer tificate a uthority s ecurity do cumentatio n is in pl ace | |
145 | Deployment | |
146 | 7 | |
147 | N/A for th is patch a s we are u sing only the existi ng VistA s ystem | |
148 | Installati on | |
149 | Validate t hrough fac ility POC to ensure that IT eq uipment ha s been acc epted usin g asset in ventory pr ocesses | |
150 | N/A | |
151 | 8 | |
152 | VA’s eBusi ness team | |
153 | Installati ons | |
154 | Coordinate training | |
155 | Deployment | |
156 | 9 | |
157 | VIP releas e Agent, H ealth Prod uct Suppor t & the de velopment team | |
158 | Back-out | |
159 | 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) | |
160 | Deployment | |
161 | 10 | |
162 | No changes to curren t process – we are u sing the e xisting Vi stA system | |
163 | Post Deplo yment | |
164 | Hardware, Software a nd System Support | |
165 | Warranty | |
166 | Deployment | |
167 | The deploy ment is pl anned as a national rollout. | |
168 | This secti on provide s the sche dule and m ilestones for the de ployment. | |
169 | Timeline | |
170 | 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 . | |
171 | Site Readi ness Asses sment | |
172 | This secti on discuss es the loc ations tha t will rec eive the d eployment of multi-b uild build PRCA IB E PAYMENTS B UNDLE 4.0 (which in cludes PRC A*4.5*332 and IB*2.0 *633). | |
173 | Deployment Topology (Targeted Architectu re) | |
174 | This multi -build bui ld PRCA IB EPAYMENTS BUNDLE 4. 0 (which i ncludes PR CA*4.5*332 and IB*2. 0*633) is to be nati onally rel eased to a ll VAMCs. | |
175 | ||
176 | Site Infor mation (Lo cations, D eployment Recipients ) | |
177 | The test s ites for I OC testing are: TBD | |
178 | ||
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 VAM Cs are exp ected to i nstall thi s patch by the compl iance date . | |
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 Accoun ts Receiva ble packag e within V istA | |
233 | N/A | |
234 | 4.5 | |
235 | N/A | |
236 | N/A | |
237 | N/A | |
238 | PRCA*4.5*3 19 | |
239 | N/A | |
240 | Nationally released version | |
241 | N/A | |
242 | N/A | |
243 | N/A | |
244 | PRCA*4.5*3 26 | |
245 | N/A | |
246 | Nationally released version | |
247 | N/A | |
248 | N/A | |
249 | N/A | |
250 | Fully patc hed Integr ated Billi ng package within Vi stA | |
251 | N/A | |
252 | 2.0 | |
253 | N/A | |
254 | N/A | |
255 | N/A | |
256 | IB*2.0*516 | |
257 | N/A | |
258 | Nationally released version | |
259 | N/A | |
260 | N/A | |
261 | N/A | |
262 | IB*2.0*609 | |
263 | N/A | |
264 | Nationally released version | |
265 | N/A | |
266 | N/A | |
267 | N/A | |
268 | 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. | |
269 | Communicat ions | |
270 | 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 Payments e Business t eam, the d evelopers, and produ ct support personnel . | |
271 | Deployment /Installat ion/Back-O ut Checkli st | |
272 | The Releas e Manageme nt team wi ll deploy the multi- build PRCA IB EPAYME NTS BUNDLE 4.0, whic h is track ed in the NPM 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 t he patch w as install ed in the VistA prod uction at each site, and by wh om. A repo rt can als o be run t o identify which sit es have no t installe d the patc h in their VistA pro duction sy stem as of that mome nt in time . | |
273 | ||
274 | Therefore, this info rmation do es not nee d to be ma nually tra cked in th e chart be low. | |
275 | ||
276 | ||
277 | Table 6: D eployment/ Installati on/Back-Ou t Checklis t | |
278 | Activity | |
279 | Day | |
280 | Time | |
281 | Individual who compl eted task | |
282 | Deploy | |
283 | N/A | |
284 | N/A | |
285 | N/A | |
286 | Install | |
287 | N/A | |
288 | N/A | |
289 | N/A | |
290 | ||
291 | Installati on | |
292 | Pre-instal lation and System Re quirements | |
293 | PRCA*4.5*3 32 and IB* 2.0*633 pa tches to t he existin g VistA Ac counts Rec eivable 4. 5 packages , are inst allable on a fully p atched M(U MPS) VistA system an d operate on the top of the Vi stA enviro nment prov ided by th e VistA in frastructu re package s. The lat ter provid es utiliti es which c ommunicate with the underlying operating system an d hardware , thereby providing Integrated Billing a nd Account s Receivab le indepen dence from variation s in hardw are and op erating sy stem. | |
294 | Platform I nstallatio n and Prep aration | |
295 | Refer to P RCA*4.5*33 2 and IB*2 .0*633 doc umentation on the Na tional Pat ch Module (NPM) on F orum for t he detaile d installa tion instr uctions. T hese instr uctions wo uld includ e any pre- installati on steps i f applicab le. | |
296 | Download a nd Extract Files | |
297 | Refer to t he PRCA*4. 5*332 and IB*2.0*633 documenta tion on th e NPM to f ind the lo cation of related do cumentatio n that can be downlo aded. PRCA *4.5*332 a nd IB*2.0* 633will be distribut ed via hos t file PRC A_IB_EPAYM ENTS_BUNDL E_4_0.KID. | |
298 | ||
299 | Sites can retrieve V istA softw are from d ownload. DNS . URL .
|
|
300 | ||
301 | Sites may retrieve s oftware di rectly usi ng Secure File Trans fer Protoc ol (SFTP) from the A NONYMOUS.S OFTWARE di rectory at the follo wing OI Fi eld Office s: | |
302 | ||
303 | Hin esDNS.URL | |
304 | Salt Lake City DNS . URL | |
305 | ||
306 | The PRCA_I B_EPAYMENT S_BUNDLE_4 _0.KID hos t file is located in the anony mous.softw are direct ory. Use t he America n Standard Code for Informatio n Intercha nge (ASCII ) Mode whe n download ing the fi le. | |
307 | ||
308 | Database C reation | |
309 | Multi-buil d build PR CA IB EPAY MENTS BUND LE 4.0 mod ifies the VistA data base. All changes ca n be found on the NP M document ation for these patc hes. | |
310 | ||
311 | Installati on Scripts | |
312 | No install ation scri pts are ne eded for m ulti-build build PRC A IB EPAYM ENTS BUNDL E 4.0 ins tallation. | |
313 | ||
314 | Cron Scrip ts | |
315 | No Cron sc ripts are needed for multi-bui ld build P RCA IB EPA YMENTS BUN DLE 4.0 i nstallatio n. | |
316 | Access Req uirements and Skills Needed fo r the Inst allation | |
317 | The follow ing staff will need access to the host f ile PRCA_I B_EPAYMENT S_BUNDLE_4 _0.KID con taining th e PRCA*4.5 *332 and I B*2.0*633 patches. T he softwar e is to be installed by the si te’s or re gion’s des ignated: V A OI&T IT OPERATIONS SERVICE, Enterprise Service L ines, Vist A Applicat ions Divis ion. | |
318 | Installati on Procedu re | |
319 | Refer to P RCA*4.5*33 2 and IB*2 .0*633 doc umentation on the NP M for the detailed i nstallatio n instruct ions. | |
320 | Installati on Verific ation Proc edure | |
321 | Refer to P RCA*4.5*33 2 and IB*2 .8*633 doc umentation on the NP M for the detailed i nstallatio n instruct ions. Thes e instruct ions would include a ny post in stallation steps if applicable . | |
322 | System Co nfiguratio n | |
323 | No system configurat ion change s are requ ired for t his patch. | |
324 | Database Tuning | |
325 | No reconfi guration o f the Vist A database , memory a llocations or other resources is necessa ry. | |
326 | Back-Out P rocedure | |
327 | Back-Out p ertains to a return to the las t known go od operati onal state of the so ftware and appropria te platfor m settings . | |
328 | Back-Out S trategy | |
329 | A decision to back o ut could b e made dur ing Site M irror Test ing, durin g Site Pro duction Te sting, or after Nati onal Relea se to the field (VAM Cs). The b est strate gy decisio n is depen dent on th e stage du ring which the decis ion is mad e. | |
330 | Mirror Tes ting or Si te Product ion Testin g | |
331 | If a decis ion to bac k out is m ade during Mirror Te sting or S ite Produc tion Testi ng, a new version of the patch can be us ed to rest ore the bu ild compon ents to th eir pre-pa tch condit ion. | |
332 | After Nati onal Relea se but Dur ing the De signated S upport Per iod | |
333 | If a decis ion to bac k out is m ade after national r elease and within th e designat ed support period, a new patch will be e ntered int o the NPM in Forum a nd will go through a ll the nec essary mil estone rev iews, etc. as a patc h for a pa tch. This patch coul d be defin ed as an e mergency p atch, and it could b e used to address sp ecific iss ues pertai ning to th e original patch or it could b e used to restore th e build co mponents t o their or iginal pre -patch con dition. | |
334 | After Nati onal Relea se and War ranty Peri od | |
335 | After the support pe riod, the VistA Main tenance Pr ogram will produce t he new pat ch, either to correc t the defe ctive comp onents or restore th e build co mponents t o their or iginal pre -patch con dition. | |
336 | Back-Out C onsiderati ons | |
337 | Changes im plemented with multi -build PRC A IB EPAYM ENTS BUNDL E 4.0 can be backed out in the ir entiret y or on an enhanceme nt-by-enha ncement ba sis. Eithe r could be accomplis hed via a new versio n of multi -build PRC A IB EPAYM ENTS BUNDL E 4.0 if b efore nati onal relea se or a ne w multi-bu ild if aft er nationa l release. | |
338 | Load Testi ng | |
339 | N/A. The b ack-out pr ocess woul d be execu ted at nor mal, rathe r than rai sed job pr iority, an d is expec ted to hav e no signi ficant eff ect on tot al system performanc e. Subsequ ent to the reversion , the perf ormance de mands on t he system would be u nchanged. | |
340 | ||
341 | User Accep tance Test ing | |
342 | 1. A new report EEO Bs marked for Auto-P ost Report (EMA) [R CDPE MARKE D AUTO-POS T REPORT] was added to the EDI LOCKBOX REPORTS Me nu [RCDPE EDI LOCKBO X REPORTS MENU]. | |
343 | a) All ows the us er to iden tify the u sers that marked an EEOB for a uto-postin g for a sp ecific da te range a nd other f ilter crit eria. | |
344 | 2. A new report Pe nding EFT Override R eport (PEO ) [RCDPE EFT OVERRI DE REPORT] was added to the ED I LOCKBOX REPORTS M enu [RCDPE EDI LOCKB OX REPORTS MENU]. | |
345 | a) Sho ws a listi ng of unpo sted medic al EFTs th at are old er than th e limit se t in the N UMBER OF D AYS (AGE) OF UNPOSTE D MEDICAL EFTS TO PR EVENT POST ING parame ter in a l ist manger . | |
346 | 3. A new option Du plicate ER A Worklist (DUP) [R CDPE DUPLI CATE ERA W ORKLIST] w as added t o the EDI LOCKBOX Me nu [RCDPE EDI LOCKBO X MENU]. | |
347 | a) All ows the us er to see all the in coming ERA messages that were determined to be dup licates. | |
348 | b) For each dupl icate in t he list, t he user ca n view the detail, delete the duplicate or file t he duplica te as a ne w ERA. If the user files the duplicate as new ERA , 'DUP' is appended to the end of the tr ace number to indica te that th e ERA was created fr om a dupli cate. | |
349 | 4. A new report Au to Paramet er History Report [R CDPE AUTO PARAM HIST REPORT] w as added t o the Site Parameter Edit menu of the Su pervisor's AR Menu. | |
350 | a) Dis plays a hi story of c hanges to auto-activ ity site p arameters. | |
351 | 5. The u ser initia ls column on the Lis t or Recei pts Report [RCDP LIS T OF RECEI PTS REPORT ] was expa nded to sh ow the fir st four le tters of t he user's last name followed b y a comma followed b y the firs t letter o f the user 's first n ame. Note : if the r eceipt was processed by the Ni ghtly job, the user' s initials will rema in 'ar'. | |
352 | 6) A cha nge was ma de to the EFT/ERA Tr ending Rep ort (ETR) [RCDPE EF T-ERA TREN DING REPOR T] to show the 'TOTA L DIFFEREN CE BETWEEN ERAs (PAI D) - EFTs (COLLECTED ): ' as th e last lin e of the f irst page instead of the first line of t he second page when the report is run in 'GRAND TO TALS ONLY' mode. | |
353 | 7. The f ollowing c hanges wer e made to the Active Bills wit h EEOB Rep ort (AB) [ RCDPE ACTI VE WITH EE OB REPORT] . | |
354 | a) The filter que stion 'RUN REPORT FO R (A)LL EE OBs or (Z) ERO PAYMEN T EEOBs on ly: ALL//' was chang ed to 'RUN REPORT FO R (P)AYMEN T EEOBs or (Z)ERO PA YMENT EEOB s or (A)LL : ALL//' | |
355 | b) The report now includes EEOBs with a posting status of 'NOT POST ED' or rem oved. Pre viously, t hese were omitted fr om the rep ort. | |
356 | ||
357 | 8. The fo llowing ch anges were made to t he 'Manual Match' | |
358 | [RCDPE EFT ERA M ANUAL MATC H] action on the ERA WORKLIST | |
359 | [RCDPE EDI LOCKB OX WORKLIS T]. | |
360 | a) The name of th e action w as changed to 'ERA M anual Matc h'. | |
361 | b) Afte r entering filtering criteria, a new lis t manager form is | |
362 | disp layed to s how all th e EFTs tha t partiall y match th e ERA in | |
363 | weig hted order such that the most likely EFT matches a re | |
364 | disp layed at t he top and the least likely ma tches are displayed at | |
365 | the bottom. E FTs that o nly match the ERA by the payer TIN are | |
366 | not displayed in the lis t. | |
367 | ||
368 | 9. A new parameter 'NUMBER OF DAYS (AGE ) OF UNPOS TED MEDICA L TRICARE TO | |
369 | PREVEN T POSTING: ' was adde d to the E DI Lockbox Parameter s | |
370 | [RCDPE EDI LOCKB OX PARAMET ERS]. | |
371 | a) The default of the new p arameter i s 30. The range is 14-60 | |
372 | b) Any time the v alue of th is paramet er is chan ged, the c hange is | |
373 | refl ected in t he EDI Loc kbox Param eters Audi t Report | |
374 | [RCD PE PARAMET ER AUDIT R EPORT]. | |
375 | c) If t he user tr ies to sel ect an ERA associate d with a T ricare | |
376 | Paye r in the E RA WORKLIS T [RCDPE E DI LOCKBOX WORKLIST] , that | |
377 | cont ains EFTs older than the new s ite parame ter, a loc k-out | |
378 | erro r message is display ed. | |
379 | d) The user may o verride th e Tricare lock-out u sing the U nposted EF T | |
380 | Over ride [RCDP E UNPOSTED EFT OVERR IDE] menu option. | |
381 | ||
382 | 10. The 'M ismatched Procedure Code' erro r message that is di splayed in the | |
383 | Third Party Join t Inquiry [IBJ THIRD PARTY JOI NT INQUIRY ] on the E P | |
384 | screen when a cl aim was bi lled elect ronically has been c hanged to | |
385 | 'Claim was not b illed elec troinicall y'. | |
386 | ||
387 | 11. The Ex tended Che ck/Trace/C redit Card Search (E X) | |
388 | [RCDP EXTENDED C HECK/CC SE ARCH] was modified i n the foll owing mann er: | |
389 | a) The filter pro mpt 'Check , Credit C ar or Trac e #' was c hanged to | |
390 | 'Che ck, Credit Card, Tra ce # or Al l' with a default of all. | |
391 | b) If ' All' is ch osen for t he filter above, the target st ring will be | |
392 | sear ched as a Check, Cre dit Card a nd Trace # . If all i s not chos en, | |
393 | the target str ing is onl y checked for select ed search type. | |
394 | c) a mi nimum of t hree chara cters is r equired to perform t he search. | |
395 | d) The search is case insen sitive suc h that a s earch for trace numb er | |
396 | cont aining 'zz z' will al so show re sults wher e the trac e # contai ns | |
397 | 'ZZZ '. | |
398 | e) If t he user do es NOT sel ect 'All' as a searc h filter a nd the tar get | |
399 | stri ng is not found, the user is t hen asked if they wa nt to perf orm | |
400 | a ne w search f or the sam e target b ut a diffe rent searc h type. | |
401 | ||
402 | 12. When the user s plits/edit s a claim on an ERA line and p uts all th e | |
403 | payme nt dollars into susp ense, the associated EEOB is n o longer | |
404 | remov ed from th e ERA Line . An EEOB is only re moved from an ERA li ne | |
405 | when all of the payment d ollars hav e been dis tributed t o other | |
406 | claim s. | |
407 | ||
408 | 13. The R eceipt Pro cessing [R CDP RECEIP T PROCESSI NG] option has been | |
409 | modif ied in the following manner: | |
410 | a) When the user s elects the Customize [RCDP DEP OSIT PROFI LE CUSTOMI Z] | |
411 | actio n, prompt 'Do you wa nt to show check, an d credit c ard inform ation?' | |
412 | has b een modifi ed to 'Do you want t o show tra ce #, chec k, and cre dit | |
413 | card informatio n?'. | |
414 | b) If th e type of payment of the recei pt is 'EDI LOCKBOX', then the trace | |
415 | # dis plays in l ieu of the check and /or credit card info rmation | |
416 | ||
417 | 14. The N ightly AR Process ha s been mod ified in t he followi ng manner: | |
418 | a) A new site para meter 'ENA BLE AUTO-A UDIT FOR T RICARE ELE CTRONIC BI LLS | |
419 | (Y/N) : No//' ha s been add ed to the EDI Lockbo x Paramete rs [RCDPE EDI | |
420 | LOCK BOX PARAME TERS] afte r the auto -audit par ameter for Pharmacy. | |
421 | b) Any t ime the va lue of thi s paramete r is chang ed, the ch ange is | |
422 | refl ected in t he EDI Loc kbox Param eters Audi t Report | |
423 | [RCD PE PARAMET ER AUDIT R EPORT]. | |
424 | c) If au to-auditin g of Trica re claims is turned on all new bills for | |
425 | claim s with pay ers flagge d as Trica re will be audited. | |
426 | ||
427 | 15. The E DI Lockbox (ePayment s) Reports Menu [RCD PE EDI LOC KBOX REPOR TS MENU] | |
428 | has b een re-org anized wit h the foll owing new sub-menus: | |
429 | a) A new sub-menu 'Workload Reports' [ RCDPE EDI LOCKBOX RE PORTS WORK LOAD | |
430 | MENU] was added to allow access to all of the workload reports as follows: | |
431 | 1. EF T Daily Ac tivity Rep ort [RCDPE EDI LOCKB OX ACT REP ORT] | |
432 | 2. EF T Unmatche d Aging Re port [RCDP E EFT AGIN G REPORT] | |
433 | 3. ER A Unmatche d Aging Re port [RCDP E ERA AGIN G REPORT] | |
434 | 4. Pe nding EFT Override R eport [RCD PE EFT OVE RRIDE REPO RT] | |
435 | 5. Un applied EF T Deposits Report [U NAPPLIED E FT DEP REP ORT] | |
436 | b) A new sub-menu 'Adjustmen t Code Rep orts' [RCD PE EDI LOC KBOX REPOR TS ADJ COD E | |
437 | MENU] was added to allow access to all of the workload reports as follows: | |
438 | 1. 83 5 CARC Dat a Report [ RCDPE CARC CODE PAYE R REPORT] | |
439 | 2. Pr ovider Lev el Adjustm ents Repor t [RCDPE P ROVIDER LV L ADJ REPO RT] | |
440 | 3. CA RC/RARC Qu ick Search [RCDPE CA RC/RARC QU ICK SEARCH ] | |
441 | 4. CA RC/RARC Ta ble Data R eport [RCD PE CARC/RA RC TABLE R EPORT] | |
442 | c) A new sub menu 'Additiona l Research Reports' | |
443 | [RCDP E EDI LOCK BOX REPORT S RESEARCH MENU] was added to allow acce ss to all | |
444 | of th e research reports a s follows: | |
445 | 1. EF T/ERA TREN DING Repor t [RCDPE E FT-ERA TRE NDING REPO RT ] | |
446 | 2. Ac tive Bills With EEOB Report [R CDPE ACTIV E WITH EEO B REPOR] | |
447 | d) A new sub menu 'Audit Rep orts' [RCD PE EDI LOC KBOX REPOR TS AUDIT M ENU] was | |
448 | added to allow access to all of the audit rep orts as fo llows: | |
449 | 1. Au to-Decreas e Adjustme nt report [RCDPE AUT O-DECREASE REPORT] | |
450 | 2. Au to-Post Re port [RCDP E AUTO-POS T REPORT] | |
451 | 3. Au to-Posted Receipt Re port [RCDP E AUTO-POS T RECEIPT REPORT] | |
452 | 4. Au to Paramet er History Report [R CDPE AUTO PARAM HIST REPORT] | |
453 | 5. EF T Transact ion Audit Report [RC DPE EFT TR ANSACTION AUD REP] | |
454 | 6. ER A Status C hange Audi t Report [ RCDPE ERA STATUS CHN G AUD REP] | |
455 | 7. Du plicate EF T Deposits Audit Rep ort [RCDPE EFT AUDIT REPORT] | |
456 | 8. EE OB Move/Co py/Remove Audit Repo rt [RCDPE EEOB MOVE/ COPY/RMOVE RPT] | |
457 | 9. EE OBs Marked for Auto- Post Audit Report [R CDPE MARKE D AUTO-POS T REPORT] | |
458 | 10. E RAs Posted with Pape r EOB Audi t Report [ RCDPE ERA W/PAPER EO B REPORT] | |
459 | 11. P ayer Imple mentation Report [RC DPE PAYER EXCLUSION NAME TIN] | |
460 | 12. [ Remove ERA from Acti ve Worklis t Audit Re port RCDPE REMOVED E RA AUDIT] | |
461 | ||
462 | 16. The R CDPEAR sec urity key was remove d from the Administr ative Cost Adjustmen t | |
463 | [PRCA F ADJ ADMI N] menu op tion. | |
464 | ||
465 | 17. The V iewing/Pri nting of E RA informa tion has b een modifi ed to allo w the user | |
466 | to vi ew it in a list mana ger so tha t specific informati on can sea rched for | |
467 | easil y. The fo llowing ar eas were c hanged: | |
468 | a) The V iew/Print ERA [RCDPE VIEW/PRIN T ERA] men u option. | |
469 | b) The V iew/Print ERA action [RCDPE ER A LIST VIE W ERA] on the ERA Wo rklist | |
470 | [RCDP E EDI LOCK BOX WORKLI ST]. | |
471 | c) The V iew/Print ERA action [RCDPE AP AR VIEW/PR INT ERA] f rom the Au to-Post | |
472 | Await ing Resolu tion (APAR ) Worklist [RCDPE AP AR]. | |
473 | Workl ist []. | |
474 | 18. The R efresh Lin e action w as added t o Auto-Pos t Awaiting Resolutio n (APAR) RCDPE APAR . The ref resh line action all ows the us er to refr esh Split/ Edit a Lin e actions that haven 't been au to-posted yet. | |
475 | Back-Out C riteria | |
476 | The projec t is cance led or the requested changes i mplemented by multi- build buil d PRCA IB EPAYMENTS BUNDLE 4.0 are no lo nger desir ed by VA O I&T and th e ePayment s eBusines s team, or the patch produces catastroph ic problem s. | |
477 | Back-Out R isks | |
478 | Since the ePayments software i s tightly integrated with exte rnal syste ms, any at tempt at a back-out should inc lude close consultat ion with t he externa l trading partners s uch as the Financial Services Center (FS C), the He alth Care Clearing H ouse (HCCH ), the VA 3rd Party Lockbox ba nk, and th e Financia l Manageme nt System (FMS) to d etermine r isk. | |
479 | Authority for Back-O ut | |
480 | 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), the Health Care Clea ring House (HCCH), V A 3rd Part y Lockbox bank, and the FMS to determine the appro priate cou rse of act ion. ePay ments is t ightly int egrated wi th these e xternal pa rtners and a back-ou t of the p atch shoul d not be a standalon e decision . | |
481 | Back-Out P rocedure | |
482 | 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 rollb ack 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. | |
483 | ||
484 | 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. Please c ontact the EPMO deve lopment te am for ass istance si nce this i nstalled p atch conta ins compon ents in ad dition to routines. | |
485 | ||
486 | ||
487 | The Multi- build buil d PRCA IB EPAYMENTS BUNDLE 4.0 contains the follow ing build components . | |
488 | Data Dicti onary Chan ges | |
489 | Options | |
490 | Routines | |
491 | Templates | |
492 | Protocols | |
493 | Modificati ons to the following files: | |
494 | AR SITE PA RAMETER Fi le [#342] | |
495 | AR EDI LOC KBOX MESSA GES File [ #344.5] | |
496 | RCDPE PARA METER File [#344.61] and Sub-f ile [#344. 611] | |
497 | ||
498 | ||
499 | 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. | |
500 | ||
501 | Please con tact the E PMO team f or assista nce since this insta lled patch contains components in additi on to rout ines. | |
502 | Back-out V erificatio n Procedur e | |
503 | Successful back-out is confirm ed by veri fication t hat the ba ck-out pat ch was suc cessfully implemente d. This in cludes suc cessful in stallation and testi ng that th e back-out it acted as expecte d, as defi ned togeth er with th e team the site cont acted in s ection 5.5 . | |
504 | Rollback P rocedure | |
505 | Rollback p ertains to data. PRC A*4.5*332 and IB*2.0 *633 do im pact the d ata in the Integrate d Billing and Accoun ts Receiva ble packag es. Theref ore, to ro ll back th e patches one will n eed to ins tall new p atches to roll back the databa se changes and resto re the sys tem back t o its prio r state. I n the case where a r ollback is needed, r efer to th e Back-Out procedure s detailed elsewhere within th is documen t. | |
506 | Rollback C onsiderati ons | |
507 | Not applic able. | |
508 | Rollback C riteria | |
509 | Not applic able. | |
510 | Rollback R isks | |
511 | Not applic able. | |
512 | Authority for Rollba ck | |
513 | Not applic able. | |
514 | Rollback P rocedure | |
515 | Not applic able. | |
516 | Rollback V erificatio n Procedur e | |
517 | Not applic able. | |
518 | Template R evision Hi story | |
519 | Date | |
520 | Version | |
521 | Descriptio n | |
522 | Author | |
523 | March 2016 | |
524 | 2.2 | |
525 | 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. | |
526 | VIP Team | |
527 | February 2 016 | |
528 | 2.1 | |
529 | 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 | |
530 | OI&T Docum entation S tandards C ommittee | |
531 | December 2 015 | |
532 | 2.0 | |
533 | 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. | |
534 | OI&T Docum entation S tandards C ommittee | |
535 | February 2 015 | |
536 | 1.0 | |
537 | Initial Dr aft | |
538 | Lifecycle and Releas e Manageme nt |
Araxis Merge (but not the data content of this report) is Copyright © 1993-2016 Araxis Ltd (www.araxis.com). All rights reserved.