Produced by Araxis Merge on 8/5/2017 9:36:44 AM 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 | BPS_1.0_21_Build_8.zip | bps_1_p21_ig.docx | Fri Apr 28 17:39:42 2017 UTC |
| 2 | BPS_1.0_21_Build_8.zip | bps_1_p21_ig.docx | Sat Aug 5 13:19:59 2017 UTC |
| Description | Between Files 1 and 2 |
|
|---|---|---|
| Text Blocks | Lines | |
| Unchanged | 1 | 738 |
| 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 | Medical Ca re Collect ion Fund ( MCCF) Elec tronic Dat a Intercha nge (EDI) Transactio n Applicat ions Suite (TAS) ePh armacy Bui ld 1 | |
| 2 | E Claims M anagement Engine BPS *1.0*21 | |
| 3 | Deployment , Installa tion, Back -Out, and Rollback G uide | |
| 4 | Version 1. 0 | |
| 5 | ||
| 6 | ||
| 7 | April 2017 | |
| 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 | April 2017 | |
| 18 | 1.0 | |
| 19 | Initial Ve rsion | |
| 20 | Christine Bullis, Ma rk Dawson | |
| 21 | ||
| 22 | Artifact R ationale | |
| 23 | 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. | |
| 24 | 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. | |
| 25 | ||
| 26 | ||
| 27 | ||
| 28 | ||
| 29 | Table of C ontents | |
| 30 | 1Introduct ion1 | |
| 31 | 1.1Purpose 1 | |
| 32 | 1.2Depende ncies1 | |
| 33 | 1.3Constra ints1 | |
| 34 | 2Roles and Responsib ilities1 | |
| 35 | 3Deploymen t2 | |
| 36 | 3.1Timelin e2 | |
| 37 | 3.2Site Re adiness As sessment2 | |
| 38 | 3.2.1Deplo yment Topo logy (Targ eted Archi tecture)2 | |
| 39 | 3.2.2Site Informatio n (Locatio ns, Deploy ment Recip ients)2 | |
| 40 | 3.2.3Site Preparatio n3 | |
| 41 | 3.3Resourc es3 | |
| 42 | 3.3.1Facil ity Specif ics3 | |
| 43 | 3.3.2Hardw are3 | |
| 44 | 3.3.3Softw are3 | |
| 45 | 3.3.4Commu nications4 | |
| 46 | 3.3.4.1Dep loyment/In stallation /Back-Out Checklist4 | |
| 47 | 4Installat ion4 | |
| 48 | 4.1Pre-ins tallation and System Requireme nts4 | |
| 49 | 4.2Platfor m Installa tion and P reparation 5 | |
| 50 | 4.3Downloa d and Extr act Files5 | |
| 51 | 4.4Databas e Creation 5 | |
| 52 | 4.5Install ation Scri pts5 | |
| 53 | 4.6Cron Sc ripts5 | |
| 54 | 4.7Access Requiremen ts and Ski lls Needed for the I nstallatio n5 | |
| 55 | 4.8Install ation Proc edure5 | |
| 56 | 4.9Install ation Veri fication P rocedure5 | |
| 57 | 4.10System Configura tion5 | |
| 58 | 4.11Databa se Tuning5 | |
| 59 | 5Back-Out Procedure6 | |
| 60 | 5.1Back-Ou t Strategy 6 | |
| 61 | 5.1.1Mirro r Testing or Site Pr oduction T esting6 | |
| 62 | 5.1.2After National Release bu t During t he Designa ted Suppor t Period6 | |
| 63 | 5.1.3After National Release an d Warranty Period6 | |
| 64 | 5.2Back-Ou t Consider ations6 | |
| 65 | 5.2.1Load Testing6 | |
| 66 | 5.2.2User Acceptance Testing6 | |
| 67 | 5.3Back-Ou t Criteria 8 | |
| 68 | 5.4Back-Ou t Risks8 | |
| 69 | 5.5Authori ty for Bac k-Out8 | |
| 70 | 5.6Back-Ou t Procedur e8 | |
| 71 | 5.7Back-ou t Verifica tion Proce dure9 | |
| 72 | 6Rollback Procedure9 | |
| 73 | 6.1Rollbac k Consider ations9 | |
| 74 | 6.2Rollbac k Criteria 9 | |
| 75 | 6.3Rollbac k Risks9 | |
| 76 | 6.4Authori ty for Rol lback9 | |
| 77 | 6.5Rollbac k Procedur e9 | |
| 78 | 6.6Rollbac k Verifica tion Proce dure9 | |
| 79 | ||
| 80 | Table of T ables | |
| 81 | Table 1: D eployment, Installat ion, Back- out, and R ollback Ro les and Re sponsibili ties1 | |
| 82 | Table 2: S ite Prepar ation3 | |
| 83 | Table 3: F acility-Sp ecific Fea tures3 | |
| 84 | Table 4: H ardware Sp ecificatio ns3 | |
| 85 | Table 5: S oftware Sp ecificatio ns4 | |
| 86 | Table 6: D eployment/ Installati on/Back-Ou t Checklis t4 | |
| 87 | ||
| 88 | ||
| 89 | ||
| 90 | Introducti on | |
| 91 | This docum ent descri bes how to deploy an d install the BPS*1. 0*21 and h ow to back -out the p roduct and rollback to a previ ous versio n or data set. | |
| 92 | Purpose | |
| 93 | 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 BPS*1. 0*21 will be deploye d and inst alled, as well as ho w it is to be backed out and r olled back , if neces sary. The plan ident ifies reso urces, com munication s plan, an d rollout schedule. Specific i nstruction s for inst allation, back-out, and rollba ck are inc luded in t his docume nt. | |
| 94 | Dependenci es | |
| 95 | BPS*1.0*20 must be i nstalled b efore BPS* 1.0*21. | |
| 96 | Constraint s | |
| 97 | This patch is intend ed for a f ully patch ed VistA s ystem. | |
| 98 | Roles and Responsibi lities | |
| 99 | Table 1: D eployment, Installat ion, Back- out, and R ollback Ro les and Re sponsibili ties | |
| 100 | ID | |
| 101 | Team | |
| 102 | Phase / Ro le | |
| 103 | Tasks | |
| 104 | Project Ph ase (See S chedule) | |
| 105 | 1 | |
| 106 | VA OI&T, V A OI&T Hea lth Produc t Support & PMO (Lei dos) | |
| 107 | Deployment | |
| 108 | Plan and s chedule de ployment ( including orchestrat ion with v endors) | |
| 109 | Planning | |
| 110 | 2 | |
| 111 | Local VAMC and CPAC processes | |
| 112 | ||
| 113 | ||
| 114 | Deployment | |
| 115 | Determine and docume nt the rol es and res ponsibilit ies of tho se involve d in the d eployment. | |
| 116 | Planning | |
| 117 | 3 | |
| 118 | Field Test ing (Initi al Operati ng Capabil ity - IOC) , Health P roduct Sup port Testi ng & VIP R elease Age nt Approva l | |
| 119 | Deployment | |
| 120 | Test for o perational readiness | |
| 121 | Testing | |
| 122 | 4 | |
| 123 | Health pro duct Suppo rt and Fie ld Operati ons | |
| 124 | Deployment | |
| 125 | Execute de ployment | |
| 126 | Deployment | |
| 127 | 5 | |
| 128 | Individual Veterans Administra tion Medic al Centers (VAMCs) | |
| 129 | Installati on | |
| 130 | Plan and s chedule in stallation | |
| 131 | Deployment | |
| 132 | 6 | |
| 133 | VIP Relea se Agent | |
| 134 | Installati on | |
| 135 | Ensure aut hority to operate an d that cer tificate a uthority s ecurity do cumentatio n is in pl ace | |
| 136 | Deployment | |
| 137 | 7 | |
| 138 | N/A for th is patch a s we are u sing only the existi ng VistA s ystem | |
| 139 | Installati on | |
| 140 | Validate t hrough fac ility POC to ensure that IT eq uipment ha s been acc epted usin g asset in ventory pr ocesses | |
| 141 | ||
| 142 | 8 | |
| 143 | VA’s eBusi ness team | |
| 144 | Installati ons | |
| 145 | Coordinate training | |
| 146 | Deployment | |
| 147 | 9 | |
| 148 | VIP releas e Agent, H ealth Prod uct Suppor t & the de velopment team | |
| 149 | Back-out | |
| 150 | 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) | |
| 151 | Deployment | |
| 152 | 10 | |
| 153 | No changes to curren t process – we are u sing the e xisting Vi stA system | |
| 154 | Post Deplo yment | |
| 155 | Hardware, Software a nd System Support | |
| 156 | Warranty | |
| 157 | Deployment | |
| 158 | The deploy ment is pl anned as a national rollout. | |
| 159 | This secti on provide s the sche dule and m ilestones for the de ployment. | |
| 160 | Timeline | |
| 161 | The durati on of depl oyment and installat ion is 30 days, as d epicted in the maste r deployme nt schedul e. | |
| 162 | Site Readi ness Asses sment | |
| 163 | This secti on discuss es the loc ations tha t will rec eive the B PS*1.0*21 deployment . | |
| 164 | Deployment Topology (Targeted Architectu re) | |
| 165 | This patch BPS*1.0*2 1 is to be nationall y released to all VA MCs. | |
| 166 | Site Infor mation (Lo cations, D eployment Recipients ) | |
| 167 | The test s ites for I OC testing are: TBD | |
| 168 | These site s will not be define d here unt il the sit es have ea ch signed a Memorand um of Unde rstanding (MOU) and testing is complete as sometim es a site has to sto p testing prior to t he end of IOC. | |
| 169 | ||
| 170 | Upon natio nal releas e all VAMC s are expe cted to in stall this patch pri or to or o n the comp liance dat e. | |
| 171 | Site Prepa ration | |
| 172 | The follow ing table describes preparatio n required by the si te prior t o deployme nt. | |
| 173 | Table 2: S ite Prepar ation | |
| 174 | Site/Other | |
| 175 | Problem/Ch ange Neede d | |
| 176 | Features t o Adapt/Mo dify to Ne w Product | |
| 177 | Actions/St eps | |
| 178 | Owner | |
| 179 | N/A | |
| 180 | N/A | |
| 181 | N/A | |
| 182 | N/A | |
| 183 | N/A | |
| 184 | Resources | |
| 185 | Facility S pecifics | |
| 186 | The follow ing table lists faci lity-speci fic featur es require d for depl oyment. | |
| 187 | Table 3: F acility-Sp ecific Fea tures | |
| 188 | Site | |
| 189 | Space/Room | |
| 190 | Features N eeded | |
| 191 | Other | |
| 192 | N/A | |
| 193 | N/A | |
| 194 | N/A | |
| 195 | N/A | |
| 196 | Hardware | |
| 197 | The follow ing table describes hardware s pecificati ons requir ed at each site prio r to deplo yment. | |
| 198 | Table 4: H ardware Sp ecificatio ns | |
| 199 | Required H ardware | |
| 200 | Model | |
| 201 | Version | |
| 202 | Configurat ion | |
| 203 | Manufactur er | |
| 204 | Other | |
| 205 | Existing V istA syste m | |
| 206 | N/A | |
| 207 | N/A | |
| 208 | N/A | |
| 209 | N/A | |
| 210 | N/A | |
| 211 | 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. | |
| 212 | Software | |
| 213 | The follow ing table describes software s pecificati ons requir ed at each site prio r to deplo yment. | |
| 214 | Table 5: S oftware Sp ecificatio ns | |
| 215 | Required S oftware | |
| 216 | Make | |
| 217 | Version | |
| 218 | Configurat ion | |
| 219 | Manufactur er | |
| 220 | Other | |
| 221 | Fully patc hed E Clai ms Managem ent Engine package w ithin Vist A | |
| 222 | N/A | |
| 223 | 1.0 | |
| 224 | N/A | |
| 225 | N/A | |
| 226 | N/A | |
| 227 | BPS*1.0*20 | |
| 228 | N/A | |
| 229 | Nationally released version | |
| 230 | N/A | |
| 231 | N/A | |
| 232 | N/A | |
| 233 | 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. | |
| 234 | Communicat ions | |
| 235 | 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 Pharmacy e Business t eam, the d evelopers, and produ ct support personnel . | |
| 236 | Deployment /Installat ion/Back-O ut Checkli st | |
| 237 | The Releas e Manageme nt team wi ll deploy the patch BPS*1.0*21 , which is tracked n ationally for all VA MCs in the NPM in Fo rum. Forum automatic ally track s the patc hes as the y are inst alled in t he differe nt VAMC pr oduction s ystems. On e can run a report i n Forum to identify when and b y whom the patch was installed in the Vi stA produc tion at ea ch site. A report ca n also be run to ide ntify whic h sites ha ve not cur rently ins talled the patch in their Vist A producti on system. | |
| 238 | ||
| 239 | Therefore, this info rmation do es not nee d to be ma nually tra cked in th e chart be low. | |
| 240 | Table 6: D eployment/ Installati on/Back-Ou t Checklis t | |
| 241 | Activity | |
| 242 | Day | |
| 243 | Time | |
| 244 | Individual who compl eted task | |
| 245 | Deploy | |
| 246 | N/A | |
| 247 | N/A | |
| 248 | N/A | |
| 249 | Install | |
| 250 | N/A | |
| 251 | N/A | |
| 252 | N/A | |
| 253 | ||
| 254 | Installati on | |
| 255 | Pre-instal lation and System Re quirements | |
| 256 | BPS*1.0*21 , a patch to the exi sting Vist A E Claims Managemen t Engine ( ECME) 1.0 package, i s installa ble on a f ully patch ed M(UMPS) VistA sys tem and op erates on the top of the VistA environme nt provide d by the V istA infra structure packages. The latter provides utilities which comm unicate wi th the und erlying op erating sy stem and h ardware, t hereby pro viding ECM E independ ence from variations in hardwa re and ope rating sys tem. | |
| 257 | Platform I nstallatio n and Prep aration | |
| 258 | Refer to t he BPS*1.0 *21 docume ntation on the Natio nal Patch Module (NP M) in Foru m for the detailed i nstallatio n instruct ions. Thes e instruct ions would include a ny pre-ins tallation steps if a pplicable. | |
| 259 | Download a nd Extract Files | |
| 260 | Refer to t he BPS*1.0 *21 docume ntation on the NPM t o find rel ated docum entation t hat can be downloade d. BPS*1.0 *21 will b e transmit ted via a PackMan me ssage and can be pul led from t he NPM. It is not a host file, and there fore does not need t o be downl oaded sepa rately. | |
| 261 | Database C reation | |
| 262 | BPS*1.0*21 modifies the VistA database. All change s can be f ound on th e NPM docu mentation for this p atch. | |
| 263 | Installati on Scripts | |
| 264 | No install ation scri pts are ne eded for B PS*1.0*21 installati on. | |
| 265 | Cron Scrip ts | |
| 266 | No Cron sc ripts are needed for BPS*1.0*2 1 installa tion. | |
| 267 | Access Req uirements and Skills Needed fo r the Inst allation | |
| 268 | The follow ing staff will need access to the PackMa n message containing the BPS*1 .0*21 patc h or to Fo rum’s NPM for downlo ading the nationally released BPS*1.0*21 patch. Th e software is to be installed by each si te’s or re gion’s des ignated VA OI&T IT O PERATIONS SERVICE, E nterprise Service Li nes, Vista Applicati ons Divisi on. | |
| 269 | Installati on Procedu re | |
| 270 | Refer to t he BPS*1.0 *21 docume ntation on the NPM f or detaile d installa tion instr uctions. | |
| 271 | Installati on Verific ation Proc edure | |
| 272 | Refer to t he BPS*1.0 *21 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. | |
| 273 | System Con figuration | |
| 274 | No system configurat ion change s are requ ired for t his patch. | |
| 275 | Database T uning | |
| 276 | No reconfi guration o f the Vist A database , memory a llocations or other resources is necessa ry. | |
| 277 | Back-Out P rocedure | |
| 278 | 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 . | |
| 279 | Back-Out S trategy | |
| 280 | A decision to back o ut could b e made dur ing site M irror Test ing, Site Production Testing, or after N ational Re lease to t he field ( VAMCs). Th e best str ategy deci sion is de pendent on the stage of testin g during w hich the d ecision is made. | |
| 281 | Mirror Tes ting or Si te Product ion Testin g | |
| 282 | 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. | |
| 283 | After Nati onal Relea se but Dur ing the De signated S upport Per iod | |
| 284 | 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 Nati onal Patch Module in Forum and will go t hrough all the neces sary miles tone revie ws, etc. a s a patch for a patc h. This pa tch could be defined as an eme rgency pat ch, and it could be used to ad dress spec ific issue s pertaini ng to the original p atch or be used to r estore the build com ponents to their ori ginal pre- patch cond ition. | |
| 285 | After Nati onal Relea se and War ranty Peri od | |
| 286 | 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 restore t he build c omponents to their o riginal pr e-patch co ndition. | |
| 287 | Back-Out C onsiderati ons | |
| 288 | Changes im plemented with BPS*1 .0*21 can be backed out in the ir entiret y on an en hancement- by-enhance ment basis . Either c ould be ac complished via a new version o f BPS*1.0* 21 if befo re nationa l release or a new p atch if af ter nation al release . | |
| 289 | Load Testi ng | |
| 290 | 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. | |
| 291 | User Accep tance Test ing | |
| 292 | Concerning the Defau lt item nu mber to 1. 1 when onl y one reje ct is list ed on the ECME User Screen use r story, t he followi ng accepta nce criter ia should be anticip ated: | |
| 293 | When only one reject is listed on the EC ME User Sc reen, the item numbe r value of 1.1 is de faulted at the Selec t Item pro mpt for al l ECME Use r Screen a ctions lis ted in the user stor y. | |
| 294 | ||
| 295 | Concerning the Defau lt item nu mber 1 whe n only one patient i s listed o n the ECME User Scre en user st ory, the f ollowing a cceptance criteria s hould be a nticipated : | |
| 296 | When only one patien t is liste d on the E CME User S creen, the item numb er value o f 1 is def aulted at the Select Item prom pt for all ECME User Screen ac tions list ed in the user story . | |
| 297 | ||
| 298 | Concerning the NCPDP Field Def inition – Provider N ame user s tory, the following acceptance criteria should be anticipate d: | |
| 299 | Confirm th at the BPS NCPDP FIE LD DEFS fi le include s the Prov ider First Name and Provider L ast Name f ields. | |
| 300 | ||
| 301 | Concerning the NCPDP Field Def inition – Product ID user stor y, the fol lowing acc eptance cr iteria sho uld be ant icipated: | |
| 302 | Confirm th at the BPS NCPDP FIE LD DEFS fi le include s the Orig inal Manuf acturer Pr oduct ID a nd the Ori ginal Manu facturer P roduct ID Qualifier fields. | |
| 303 | ||
| 304 | Concerning the NCPDP Field Def inition – Edits user story, th e followin g acceptan ce criteri a should b e anticipa ted: | |
| 305 | Confirm th at the BPS NCPDP FIE LD DEFS fi le reflect s the NCPD P name for the field s listed i n the user story. | |
| 306 | ||
| 307 | Concerning the NCPDP ECL Updat es user st ory, the f ollowing a cceptance criteria s hould be a nticipated : | |
| 308 | VistA ECME input fie lds accept the corre ct ECL val ues. | |
| 309 | VistA ECME stores pe rmanently ePharmacy claim data . | |
| 310 | All ECME s creens dis play the E CL values published after E7 O ctober 201 5. | |
| 311 | All ECME r eports pri nt the cor rect ECL v alues tran smitted on the ePhar macy claim s, as appl icable. | |
| 312 | VistA ECME sends ePh armacy cla im data us ing the NC PDP ECL va lues publi shed on/af ter Januar y 2016. | |
| 313 | VistA ECME receives an acknowl edgement t hat the cl aim has be en process ed without any rejec ts related to the up dated ECL updates. | |
| 314 | VistA ECME continues to displa y all reje cts to the user. | |
| 315 | The new re ject codes are displ ayed on th e ECME Use r Screen c orrectly. | |
| 316 | Descriptio ns for the new and/o r updated reject cod es display on the EC ME User Sc reen corre ctly. | |
| 317 | ||
| 318 | Concerning the Preve nt OPECC E ntering Su bmission C larificati on user st ory, when the OPECC performs t he Resubmi t w/Edits action, re strict the ability t o edit the Submissio n Clarific ation Code if any of the below criteria exist. | |
| 319 | If a presc ription ha s an unres olved Reje ct code 79 (Refill T oo Soon) o r Reject c ode 88 DUR (Drug Uti lization R eview). | |
| 320 | If a presc ription ha s a resolv ed Reject code 79 (R efill Too Soon) or R eject code 88 DUR (D rug Utiliz ation Revi ew) for th e most rec ent transa ction. | |
| 321 | If a presc ription ha s a pendin g reject o n the phar macist’s w orklist (N ote: Rejec t Resoluti on Require d rejects and Transf er Rejects are set u p locally and may va ry on the worklist). | |
| 322 | ||
| 323 | The follow ing accept ance crite ria should be antici pated: | |
| 324 | If prescri ption fall s into one of the th ree criter ia, then t he system should dis play the m essage and not allow OPECC to update the Submissio n Clarific ation Code using the RED Resub mit w/Edit s action. | |
| 325 | Assure tha t the OPEC C can edit the Submi ssion Clar ification Code using the RED R esubmit w/ Edits acti on for pre scriptions when the prescripti on does no t meet the criteria. | |
| 326 | Assure tha t the Phar macists ca n update t he Submiss ion Clarif ication Co de at all times (the Pharmacis ts’ abilit y to enter /edit the codes shou ld not be changed). | |
| 327 | Assure the OPECC can not edit t he Submiss ion Clarif ication Co de when us ing the RE D Resubmit w/Edits a ction and there are multiple r eject code s, one of which fits this crit eria and o ne does no t fit the criteria. | |
| 328 | The OPECC should be able to ed it other e xisting fi elds withi n the RED Resubmit e /Edits act ions if th e prescrip tion falls into the three crit eria. | |
| 329 | Assure the OPECC can edit the Submission Clarifica tion Code when using the RED R esubmit w/ Edits acti on and the re are mul tiple reje ct codes, none of wh ich meet t he criteri a. | |
| 330 | ||
| 331 | Concerning the Chang e ECME scr een for co mments on prior tran saction us er story, the follow ing accept ance crite ria should be antici pated: | |
| 332 | When a cla im is resu bmitted, t he main sc reen of th e ECME Use r Screen w ill automa tically di splay a me ssage of “ Prior comm ents suppr essed-use CMT action for all c omments” i nstead of displaying the comme nt for the previous transactio n. | |
| 333 | The main p age of the ECME User Screen wi ll display the most current co mment for the most r ecent tran saction. | |
| 334 | All commen ts will co ntinue to be availab le on othe r screens (no change ). | |
| 335 | If no comm ents have been enter ed (prior or current ) the mess age “Prior comments suppressed -use CMT a ction for all commen ts” does n ot display . | |
| 336 | ||
| 337 | Back-Out C riteria | |
| 338 | It may be decided to back out this patch if the pr oject is c anceled, t he request ed changes implement ed by BPS* 1.0*21 are no longer desired b y VA OI&T and the eP harmacy eB usiness te am, or the patch pro duces cata strophic p roblems. | |
| 339 | Back-Out R isks | |
| 340 | Since the ePharmacy 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) and the Health Ca re Clearin g House (H CCH) to de termine ri sk. | |
| 341 | Authority for Back-O ut | |
| 342 | The order would come from: rel ease coord inator (pr oduct supp ort), port folio dire ctor, and health pro duct suppo rt. The or der should be done i n consulta tion with the develo pment team and exter nal tradin g partners such as F SC and the HCCH to d etermine t he appropr iate cours e of actio n. ePharma cy is tigh tly integr ated with these exte rnal partn ers and a decision t o back-out should no t be made without th eir consul tation. | |
| 343 | Back-Out P rocedure | |
| 344 | Backing ou t enhancem ents to a VistA appl ication is often com plex. Norm ally, defe cts are re paired via 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. If not , the site should co ntact the Enterprise Program M anagement Office (EP MO) team d irectly fo r specific solutions to their unique pro blems. | |
| 345 | ||
| 346 | The BPS*1. 0*21 patch contains the follow ing build components : | |
| 347 | Routines | |
| 348 | File entri es in the files BPS NCPDP FIEL D DEFS (#9 002313.91) , BPS NCPD P REJECT C ODES (#900 2313.93), and BPS CL ARIFICATIO N CODES (# 9002313.25 ) | |
| 349 | Data Dicti onary Chan ges | |
| 350 | ||
| 351 | While the VistA KIDS installat ion proced ure allows the insta ller to ba ck up the modified r outines us ing the ‘B ackup a Tr ansport Gl obal’ acti on, the ba ck-out pro cedure for global, d ata dictio nary and o ther VistA component s is more complex an d requires issuance of a follo w-up patch to ensure all compo nents are properly r emoved and /or restor ed. All so ftware com ponents (r outines an d other it ems) must be restore d to their previous state at t he same ti me and in conjunctio n with the restorati on of the data. | |
| 352 | ||
| 353 | Please con tact the E PMO team f or assista nce since this insta lled patch contains components in additi on to rout ines. | |
| 354 | Back-out V erificatio n Procedur e | |
| 355 | Successful back-out is confirm ed by veri fication t hat the ba ck-out pat ch was suc cessfully installed. | |
| 356 | Rollback P rocedure | |
| 357 | 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. The se data ch anges are covered in the Back- out proced ures detai led elsewh ere in thi s document . | |
| 358 | Rollback C onsiderati ons | |
| 359 | Not applic able. | |
| 360 | Rollback C riteria | |
| 361 | Not applic able. | |
| 362 | Rollback R isks | |
| 363 | Not applic able. | |
| 364 | Authority for Rollba ck | |
| 365 | Not applic able. | |
| 366 | Rollback P rocedure | |
| 367 | Not applic able. | |
| 368 | Rollback V erificatio n Procedur e | |
| 369 | Not applic able. |
Araxis Merge (but not the data content of this report) is Copyright © 1993-2016 Araxis Ltd (www.araxis.com). All rights reserved.