Produced by Araxis Merge on 10/12/2017 2:13:19 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 | OSCIF_CPRS_v31_P2_PXRM2_47 (t8)_October_2017.zip | PXRM 47 Test Evaluation Summary.docx | Mon Aug 21 12:21:54 2017 UTC |
| 2 | OSCIF_CPRS_v31_P2_PXRM2_47 (t8)_October_2017.zip | PXRM 47 Test Evaluation Summary.docx | Thu Oct 12 01:17:31 2017 UTC |
| Description | Between Files 1 and 2 |
|
|---|---|---|
| Text Blocks | Lines | |
| Unchanged | 10 | 832 |
| Changed | 9 | 18 |
| 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 | Test Evalu ation Summ ary | |
| 2 | CPRS PXRM* 2.0*47 | |
| 3 | ||
| 4 | ||
| 5 | Department of Vetera ns Affairs | |
| 6 | July 2016 | |
| 7 | Version 2. 3 | |
| 8 | ||
| 9 | ||
| 10 | ||
| 11 | ||
| 12 | ||
| 13 | ||
| 14 | ||
| 15 | ||
| 16 | ||
| 17 | ||
| 18 | ||
| 19 | ||
| 20 | Revision H istory | |
| 21 | ||
| 22 | Date | |
| 23 | Version | |
| 24 | Descriptio n | |
| 25 | Author | |
| 26 | 8/21/2017 | |
| 27 | 2.3 | |
| 28 | Added T8 t o TES log | |
| 29 | PII | |
| 30 | 5/25/2017 | |
| 31 | 2.2 | |
| 32 | Added T7 t o TES log | |
| 33 | PII | |
| 34 | 5/24/2017 | |
| 35 | 2.1 | |
| 36 | Table adde d for Test Log | |
| 37 | PII | |
| 38 | 9/15/2016 | |
| 39 | 2.0 | |
| 40 | Evaluation Updates | |
| 41 | PII | |
| 42 | 7/11/2016 | |
| 43 | 1.0 | |
| 44 | PXRM*2.0*4 7 Patch Te st Evaluat ion | |
| 45 | PII | |
| 46 | ||
| 47 | ||
| 48 | ||
| 49 | ||
| 50 | Artifact R ationale | |
| 51 | The test e valuation document i s the prim ary output of the te st and eva luation pr ocess, an integral p art of the systems e ngineering process, which iden tifies lev els of per formance a nd assists the devel oper in co rrecting d eficiencie s. | |
| 52 | The PMAS D irective c ites the S ervice Del ivery and Engineerin g (SDE) or ganization as having primary r esponsibil ities for system tes ting and c ertificati on. | |
| 53 | ||
| 54 | Table of C ontents | |
| 55 | 1.Test Eva luation In troduction 4 | |
| 56 | 1.1.Test E valuation Scope4 | |
| 57 | 1.2.Test A rchitectur e4 | |
| 58 | 1.3.Test E nvironment / Configur ation4 | |
| 59 | 1.4.Instal lation Pro cess4 | |
| 60 | 2.Test Dat a4 | |
| 61 | 3.Issues4 | |
| 62 | 4.Test Exe cution Log 5 | |
| 63 | 5.Test Def ect Log5 | |
| 64 | 6.Test Res ults Summa ry6 | |
| 65 | 7.Suggeste d Actions6 | |
| 66 | 8.Priorty Level Defi nitions7 | |
| 67 | 9.Document Approval Signatures 8 | |
| 68 | Appendix A - Test Ex ecution Lo g9 | |
| 69 | Appendix B – Defect Log10 | |
| 70 | ||
| 71 | Test Evalu ation Intr oduction | |
| 72 | The purpos e of this Test Evalu ation Summ ary is to document t he testing efforts o f internal SQA for t he PXRM*2. 0*47 patch . After p assing all test scri pts, the p atch will then be se nt out to test sites around th e country for furthe r evaluati on. | |
| 73 | Test Evalu ation Scop e | |
| 74 | The scope of testing was inter nal SQA,ex ternal sit e test acc ount and e xternat te st site pr oduction a ccounts, f or the por pose of ev aluating f ixes to th e Clinical Reminders functiona lity of CP RS v31. | |
| 75 | Test Archi tecture | |
| 76 | The test a rchitectur e of each in-house t est accoun ts are set -up with t he CPRS v3 0 build. For CPRS v 30 functui onality, p lease refe r to the C PRS v30 Ma ster Test Plan. | |
| 77 | ||
| 78 | Test Envir onment/ Co nfiguratio n | |
| 79 | The test a ccounts ar e test env ironments that dupli cate the l ive system s operatin g in India nopolis, O rlando and Phoneix w ith the ex ception of the use o f mock pat ients for testing pu rposes. | |
| 80 | ||
| 81 | Installati on Process | |
| 82 | Installati on of the PXRM*2.0*4 7 CPRS v31 patch too k about 20 seconds t o install. No issue s were see n during t he install ation proc ess. | |
| 83 | ||
| 84 | Test Data | |
| 85 | See Test E xecution L og below. | |
| 86 | ||
| 87 | Issues | |
| 88 | All known issues are logged an d located in Appendi x B. All i ssues incl uding Leve ls 1-4 hav e been cor rected. | |
| 89 | Test Execu tion Log | |
| 90 | The Test E xecution L og records the execu tion of te st scripts and docum ents the t est result s for each test scri pt. The te st analyst is respon sible for completing the Test Execution Log. Each version of the Test Execution Log is lis ted in App endix A, a nd has at least one correspond ing Defect Log Liste d in Appen dix B. | |
| 91 | PXRM*2.0*4 7 | |
| 92 | ||
| 93 | ||
| 94 | Test Defec t Log | |
| 95 | The Test D efect Log table only contains defects li sted by th e PXRM*2*4 7 test scr ipts. List ed in Appe ndix B is the full t esting log conducted by test s ites, SQA and other developers .. The tab le specifi es behavio r or resul t that occ urred, cur rent statu s, resolut ion and th e IEEE def ined Sever ity Level. Use the IEEE defin itions for Severity Levels. | |
| 96 | No defects were seen during th e testing of T7 of t his patch. | |
| 97 | Table 1: T est Defect Log | |
| 98 | Defect ID | |
| 99 | Test Case ID | |
| 100 | Descriptio n | |
| 101 | Date | |
| 102 | Reported | |
| 103 | Severity | |
| 104 | ||
| 105 | Current S tatus | |
| 106 | Resolution | |
| 107 | Date | |
| 108 | Resolved | |
| 109 | 2-1 | |
| 110 | 9e | |
| 111 | Hard error occurring when doin g a taxono my code se arch if a term like “diabetes” was input instead o f an actua l code | |
| 112 | 3/2/16 | |
| 113 | 2 | |
| 114 | Resolved | |
| 115 | Corrected search | |
| 116 | 6/15/16 | |
| 117 | 2-2 | |
| 118 | 4 | |
| 119 | Time was n ot being d isplayed w hen the re minder fre quency was in hours | |
| 120 | 6/10/16 | |
| 121 | 2 | |
| 122 | Resolved | |
| 123 | Missing li ne of code in ACHK^P XRMLOG. Th e line was put back and the ro utine was added to t he build | |
| 124 | 6/15/16 | |
| 125 | 3-1 | |
| 126 | 3a | |
| 127 | New recurs ion checke r was intr oduced in T2 and thi s error wa s occurrin g during t he recursi on check t hat is mad e as part of reminde r evaluati on | |
| 128 | 7/22/16 | |
| 129 | 2 | |
| 130 | Resolved | |
| 131 | The recurs ion check was modifi ed | |
| 132 | 8/15/16 | |
| 133 | 5-1 | |
| 134 | N/A | |
| 135 | CPRS31 tes t site rep orted the following error: | |
| 136 | <UNDEFINED >FERROR+7^ PXRMOUTU * TEXT | |
| 137 | 1/9/17 | |
| 138 | 3 | |
| 139 | Resolved | |
| 140 | Corrected Typo | |
| 141 | 1/26/17 | |
| 142 | 6-1 | |
| 143 | N/A | |
| 144 | SQA review noted th at XU*8.0* 657 was st ill listed in the bu ild descri ption | |
| 145 | 5/3/17 | |
| 146 | 2 | |
| 147 | Resolved | |
| 148 | No functio nal change s made, co rrected li sted patch es and cre ated new b uild to ex clude XU*8 .0*657 in the build descriptio n | |
| 149 | 5/11/17 | |
| 150 | 7-1 | |
| 151 | N/A | |
| 152 | After inst alling the T7 build in Product ion, Puget Sound sta rted getti ng the fol lowing err ors: | |
| 153 | ||
| 154 | <><UNDEFIN ED>REMIND+ 29^VPSPTCR ^TMP("PXR HM" 06:46: 33 ROU:PU GR1PA03 1 | |
| 155 | <><UNDEFIN ED>REMIND+ 21^ORQQPX ^TMP("PXRH M" 06:46:2 2 ROU:PUG R1PA01 259 | |
| 156 | 7/27/2017 | |
| 157 | 1 | |
| 158 | Resolved | |
| 159 | VPS and OR errors we re due to improperly written c ode in tho se package s. solutio n was a on e line cha nge in Cli nical Remi nders | |
| 160 | 7/28/2017 | |
| 161 | ||
| 162 | ||
| 163 | Test Resul ts Summary | |
| 164 | Testing wa s conducte d on each build of P XRM*2*47. Reported e rrors were logged an d duplicat ed by CPRS developme nt teams. These defe cts were r esearched and correc ted. A fin al build C R_ICD-10_F OLLOWUP.KI D was prod uced and i nstalled a t the thre e test sit es, produc ing no fur ther error s. | |
| 165 | ||
| 166 | Suggested Actions | |
| 167 | N/A | |
| 168 | Priorty Le vel Defini tions | |
| 169 | Priority 1 - Resolve Immediate ly | |
| 170 | Further de velopment and/or tes ting canno t occur un til the de fect has b een repair ed. The sy stem canno t be used until the repair has been affe cted. | |
| 171 | Priority 2 - Give Hi gh Attenti on | |
| 172 | The defect must be r esolved as soon as p ossible be cause it i s impairin g developm ent and/or testing a ctivities. System us e will be severely a ffected un til the de fect is fi xed. | |
| 173 | Priority 3 - Normal Queue | |
| 174 | The defect should be resolved in the nor mal course of develo pment acti vities. It can wait until a ne w build or version i s created. | |
| 175 | Priority 4 - Low Pri ority | |
| 176 | The defect is an irr itant that should be repaired, but can b e repaired after mor e serious defects ha ve been fi xed. | |
| 177 | Document A pproval Si gnatures | |
| 178 | ||
| 179 | Signed: __ __________ __________ __________ __________ __________ __________ _________ | |
| 180 | PII , IT Program Manager, CPRS, EPMO , EPMDDate | |
| 181 | ||
| 182 | ||
| 183 | Signed: __ __________ __________ __________ __________ __________ __________ _________ | |
| 184 | PII , IT Project Manager C PRS EP1, E PMO, EPMDD ate | |
| 185 | ||
| 186 | ||
| 187 | Signed: __ __________ __________ __________ __________ __________ __________ _________ | |
| 188 | P II , VHA Clin ical Remin ders Devel operDate | |
| 189 | ||
| 190 | ||
| 191 | Appendix A - Test Ex ecution Lo g | |
| 192 | Appendix B – Defect Log | |
| 193 | T2 – T3 Ch anges: The se are the changes m ade to the T2 versio n to creat e the T3 v ersion. | |
| 194 | ||
| 195 | 17 Feb 201 6 – PKR Co rrected a misspelled word in t he comment s of WASIN P^PXRMPDEM . | |
| 196 | Routine: P XRMPDEM - IEEE defin ed Severit y Level 3 | |
| 197 | ||
| 198 | 17 Feb 201 6 – PKR Ti cket I5761 038FY15 re ported a p roblem wit h reminder reports n ot giving the same n umber of p atients as a FileMan query. It was deter mined the probable c ause of th is is the check for a valid ap pointment status whe n the serv ice catego ry is hist orical. Th e current behavior i s to ignor e the visi t if the a ssociated appointmen t status i s null whi ch is the case for m ost histor ical visit s. The cod e was chan ged to not make the appointmen t status c heck if th e service category i s “E”. | |
| 199 | Routines: PXRMLOCF, PXRMLOCL - IEEE defi ned Severi ty Level 2 | |
| 200 | ||
| 201 | 25 Feb 201 6 – PKR In Reminder Exchange, when insta lling a ta xonomy it was always showing a s differen t even if it had jus t been pac ked. The w as because the check sum calcul ation is s upposed to ignore th e EDIT HIS TORY/CHANG E LOG. In taxonomie s when EDI T HISTORY was rename d to CHANG E LOG the code was n ot modifie d to look for CHANGE LOG so ta xonomy che cksum calc ulations w ere includ ing the CH ANGE LOG. This was corrected. | |
| 202 | Routine: P XRMEXCS - IEEE defin ed Severit y Level 2 | |
| 203 | ||
| 204 | 02 Mar 201 6 – PKR Pu get Sound (Doreen Ra ins) repor ted a hard error occ urring whe n doing a taxonomy c ode search if a term like “dia betes” was input ins tead of an actual co de. This w as correct ed. | |
| 205 | Routine: P XRMLEX - I EEE define d Severity Level 2 | |
| 206 | ||
| 207 | 14 Mar 201 6 – PKR Ac cording to Alan this ticket sh ould be ad ded to the list of t ickets res olved by 4 7: R768824 3FY16 - IE EE defined Severity Level 2 | |
| 208 | ||
| 209 | 05 May 201 6 – PKR Up dated the value sets with the April 01, 2016 relea se. The ch anges are summarized in the fo llowing ta ble: | |
| 210 | ||
| 211 | File | |
| 212 | May 01, 20 15 | |
| 213 | April 01, 2016 | |
| 214 | After Purg e | |
| 215 | NLM Value Set Coding Systems | |
| 216 | 17 | |
| 217 | 17 | |
| 218 | ||
| 219 | NLM Value Sets | |
| 220 | 977 | |
| 221 | 1527 | |
| 222 | 1006 | |
| 223 | NLM Qualit y Measure Groups | |
| 224 | 242 | |
| 225 | 335 | |
| 226 | 260 | |
| 227 | ||
| 228 | - IEEE def ined Sever ity Level 2 | |
| 229 | ||
| 230 | 09 May 201 6 – PKR Ad ded in che ck in ERRH DLR^PXRMER RH for a F RAMESTACK error, if this is th e case it quits and does not t ry to send the MailM an message . | |
| 231 | Routine: P XRMERRH - IEEE defin ed Severit y Level 2 | |
| 232 | ||
| 233 | 11 May 201 6 – PKR Th e computed finding V A-REMINDER DEFINITIO N was leav ing some p arts of ^T MP, this w as fixed b y newing P XRMDEBG in the routi ne RDEF^PX RMCDEF. | |
| 234 | Routine: P XRMCDEF - IEEE defin ed Severit y Level 2 | |
| 235 | ||
| 236 | 13 May 201 6 – PKR Th e recursio n test for VA-REMIND ER DEFINIT ION was to o simple a nd in some cases inc orrectly f lagged rec ursion whi ch prevent ed the rem inder from being eva luated. A new algori thm was de signed in implemente d in PXRMR CUR, it co rrects the problem. The variab le PXRMDEF S is not n eeded with the new a lgorithm s o it was r emoved fro m all rout ines that had it. Th e reminder integrity check alr eady inclu ded a chec k for recu rsion but testing re vealed it could miss recursion when it o ccurred th rough a te rm. The im proved rec ursion che ck was add ed to the integrity check. | |
| 237 | Routines: PXRM, PXRM ICHK, PXRM RCUR | |
| 238 | Routines w here only change was deletion of PXRMPDE FS: PXRMDE V, PXRMETX R, PXRMTER M, PXRMXEV L, PXRMXSE 1 - IEEE d efined Sev erity Leve l 2 | |
| 239 | ||
| 240 | 18 May 201 6 – PKR Al an did a t est instal l and foun d that fil e #811.3 w as not del eted. The call to DE LETAX^PXRM P47I had n ot been pu t in the p ost-init, it was add ed to the post-init. | |
| 241 | Routine: P OST^PXRMP4 7I. - IEEE defined S everity Le vel 2 | |
| 242 | ||
| 243 | 10 Jun 201 6 – PKR Wh ile going through th e test scr ipts Jeff Fahner fou nd that ti me was not being dis played whe n the remi nder frequ ency was i n hours. T his was tr aced to a missing li ne of code in ACHK^P XRMLOG: | |
| 244 | S ^TMP("P XRHM",$J,P XRMITEM,PX RMRNAM,"FR EQ")=FREQ | |
| 245 | The line w as put bac k and the routine wa s added to the build . | |
| 246 | Routine: P XRMLOG - I EEE define d Severity Level 2 | |
| 247 | ||
| 248 | T3 – T4 Ch anges: The se are the changes m ade to the T3 versio n to creat e the T4 v ersion. | |
| 249 | ||
| 250 | 22 Jul 201 6 – PKR Pu get Sound reported t he followi ng error d uring remi nder evalu ation: | |
| 251 | I '$D(^PX D(811.9,DE FIEN,20,"E ","PXRMD(8 11.4,",RDC FIEN)) Q 0 | |
| 252 | ^ | |
| 253 | <SUBSCRIP T>DEFCHK+2 ^PXRMRCUR ^PXD(811.9 ,"") | |
| 254 | A new recu rsion chec ker was in troduced i n T2 and t his error was occurr ing during the recur sion check that is m ade as par t of remin der evalua tion. The error was occurring because th e Computed Finding P arameter f or VA-REMI NDER DEFIN ITION was a set to a non-exist ent remind er. The re cursion ch eck was mo dified to handle thi s case and the case when the C omputed Fi nding Para meter is n ull. | |
| 255 | Routine: D EFCHK^PXRM RCUR - IEE E defined Severity L evel 2 | |
| 256 | ||
| 257 | 22 Jul 201 6 – PKR Te sting of t he above c hange reve aled that the defini tion integ rity check was not c atching th e case whe n the Comp uted Findi ng Paramet er for VA- REMINDER D EFINITION is set to a non-exis tent remin der, this was correc ted and a check to m ake sure t he Usage i s not List was added . | |
| 258 | Routine: P XRMICHK - IEEE defin ed Severit y Level 2 | |
| 259 | ||
| 260 | 26 Jul 201 6 – PKR Fo r recursio n occurrin g through a term, th e recursio n checker was modifi ed to retu rn | |
| 261 | 1^811.9;IE N;FINDING^ 811.5;IEN, TERM FINDI NG. The in tegrity ch ecker uses this info rmation to display t he definit ion findin g, term na me, and te rm finding . When rec ursion is occurring in the def inition th e recursio n checker returns 1^ 811.9;IEN; FINDING. T he integri ty checker uses this to displa y the find ing causin g the recu rsion. | |
| 262 | Routines: PXRMICHK, PXRMRCUR - IEEE defi ned Severi ty Level 2 | |
| 263 | ||
| 264 | 26 Jul 201 6 – PKR Re minder def inition ed iting was changed so that the integrity check is a lways run unless the user opts to exit o ut. Previo usly the i ntegrity c heck was r un only if a change was made t o the defi nition. | |
| 265 | Routine: P XRMREDT - IEEE defin ed Severit y Level 2 | |
| 266 | ||
| 267 | 26 Jul 201 6 – PKR Ch ecks were added to t he nationa l computed finding V A-REMINDER DEFINITIO N to make sure the r eminder to evaluate is defined , that it exists, an d it is ac tive. If i t does not meet thes e criteria a fatal e rror is th rown. | |
| 268 | Routine: P XRMCDEF - IEEE defin ed Severit y Level 2 | |
| 269 | ||
| 270 | 26 Jul 201 6 – PKR Ch ecking for missing o r inactive reminder definition being pas sed to VA- REMINDER D EFINITION was added. Missing m eans that it is null or the sp ecified re minder def inition do es not exi st. If eit her of the se is true it will c ause a fat al evaluat ion error. | |
| 271 | Routine: P XRMCDEF - IEEE defin ed Severit y Level 2 | |
| 272 | ||
| 273 | 28 Jul 201 6 – PKR In PXRMOUTU checks are made for fatal erro rs and err or text is produced for the Cl inical Mai ntenance o utput. The checks fo r taxonomy expansion errors we re removed . Display of text fo r errors a ssociated with CF.VA -REMINDER definition was added . | |
| 274 | Routine: FERROR^PXR MOUTU - IE EE defined Severity Level 2 | |
| 275 | ||
| 276 | 01 Aug 201 6 – PKR Th e recursio n check in EVAL^PXRM was modif ied to set the error text that is displa yed in the Clinical Maintenanc e Output. It has to be done th ere becaus e if there is recurs ion no fur ther evalu ation can be done or it will g enerate st ack errors . | |
| 277 | Routine: E VAL^PXRM - IEEE defi ned Severi ty Level 2 | |
| 278 | ||
| 279 | 01 Aug 201 6 – PKR TE RMCHK^PXRM RCUR was n ot checkin g for a no n-existent definitio n before c alling DEF CHK^PXRMRC UR. The ch eck was ad ded. | |
| 280 | Routine: T ERMCHK^PXR MRCUR - IE EE defined Severity Level 2 | |
| 281 | ||
| 282 | 09 Aug 201 6 – PKR In response to the ROF received from PII did the f ollowing: | |
| 283 | File #802. 2 | |
| 284 | The OIDVD index was corrupted with bad d ates, it w as rebuilt and this corrected the proble m. | |
| 285 | ||
| 286 | The input transform for the Co de field i n the Code s multiple was chang ed to have a minimum length of 1 instead of 3. Thi s is becau se there a re codes l ike F for female or M for male . | |
| 287 | ||
| 288 | The algori thm for ge nerating S hort ID wa s failing for birth date and p rincipal b ecause the names are entirely lowercase. The algor ithm was c hanged to first chan ge names t o title ca se which g uarantees there will be at lea st on uppe rcase lett er to use for the Sh ort ID. Th e Short ID for these two entri es was rep aired by h and. | |
| 289 | ||
| 290 | File #802. 3 | |
| 291 | The field Version Nu mber which stores th e eMeasure Version N umber is f ailing the input tra nsform for many of t he entries . The fiel d is defin ed to be a n integer between 1 and 9999 w hich match es this de finition: | |
| 292 | eMeasure V ersion Num ber: A pos itive inte ger value used to in dicate the version o f the eMea sure. | |
| 293 | Found in t he documen t GUIDE FO R READING ELIGIBLE P ROFESSIONA L (EP) AND ELIGIBLE HOSPITAL ( EH) | |
| 294 | EMEASURES VERSION 5 (March 201 4) | |
| 295 | However in the SVS X ML files many of th e eMeasure Version N umbers are not integ ers but ha ve a forma t like 6.2 .000. It a ppears tha t this cha nge was ma de startin g with the May 01, 2 015 releas e. | |
| 296 | ||
| 297 | The Develo per field was create d with a m aximum len gth of 128 , two entr ies IEN=38 and 99 ha ve lengths that exce ed 128; 14 5 and 141 respective ly. The ma ximum leng th was cha nged to 24 5 and that took care of the pr oblem. - I EEE define d Severity Level 2 | |
| 298 | ||
| 299 | 10 Aug 201 6 – PKR Co ntinue wit h the ROF fixes. Som e of the V alue Set V ersion Dat e in Value Sets mult iple were -1700000, this was a problem w e saw with the 31505 01 release so those dates were set to 31 50501. | |
| 300 | See above for a desc ription of the issue with Vers ion, to so lve this p roblem the Version f ield was c hanged fro m integer to free te xt. - IEEE defined S everity Le vel 2 | |
| 301 | ||
| 302 | 11 Aug 201 6 – PKR Co ntinue wit h ROF fixe s. Correct ed misspel ling” “cha ngle” to “ change”. | |
| 303 | Routine: P XRMTAXL - IEEE defin ed Severit y Level 3 | |
| 304 | ||
| 305 | ||
| 306 | T4 – T5 Ch anges: The se are the changes m ade to the T4 versio n to creat e the T5 v ersion. | |
| 307 | ||
| 308 | 19 Sep 201 6 – PKR In the rare case when a definiti on was del eted an at tempt was made to ru n the inte grity chec k which ca used an un defined er ror, for e xample: | |
| 309 | ||
| 310 | S ZNODE=^P XD(811.9,I EN,100) | |
| 311 | ^ | |
| 312 | <UNDEFINED >DEF+7^PXR MICHK ^PXD (811.9,114 ,100) | |
| 313 | ||
| 314 | This was f ound worki ng with Te resa. It w as correct ed so that if a defi nition is deleted th e integrit y check is not run. - IEEE def ined Sever ity Level 3 | |
| 315 | ||
| 316 | 21 Sep 201 6 – PKR Ad ded the va riable DIR to the ne wed list i n GETLIST^ PXRMLEXL. | |
| 317 | Routine: P XRMLEXL - IEEE defin ed Severit y Level 3 | |
| 318 | ||
| 319 | 24 Oct 201 6 – PKR Bo b Ruff fou nd that fo r CF.VA-RE MINDER DEF INTION if the Comput ed Finding Parameter was not d efined it was genera ting the e rror: | |
| 320 | <UNDEFINE D>DEFCHK+9 ^PXRMRCUR ^PXD(811.9 ,98,20,3,1 5) | |
| 321 | The fix wa s simply p utting $G around all the sets of CFPARAM . | |
| 322 | Routine: P XRMRCUR - IEEE defin ed Severit y Level 2 | |
| 323 | ||
| 324 | 25 Oct 201 6 – PKR Bo b Ruff had an exampl e where th e step-by- step funct ion findin g evaluati on did not agree wit h the regu lar FF eva luation. T his was tr aced to th e handling of the nu ll charact er (ASCII 0). In th e step-by- step displ ay ASCII 0 was liste d as NULL but this c ausing con fusion wit h the actu al charact er string “NULL”. Th e represen tation of ASCII 0 wa s changed to {NULL} and for ea ch step in the logic calculati on {NULL} is changed to ASCII 0. The doc umentation needs upd ated. | |
| 325 | Routine: P XRMFF - IE EE defined Severity Level 2 | |
| 326 | ||
| 327 | 25 Oct 201 6 – PKR Wh ile testin g the abov e we found several v ariables b eing left in the sym bol table after remi nder evalu ation. The se variabl es are: DU E, DUEDATE , FREQ, PC LOGIC, RES DATE, and RESLOGIC. The variab les are al l initiali zed in EVA L^PXRM, ne wing of th e variable s was adde d just bef ore they a re initial ized. | |
| 328 | Routine: P XRM - IEEE defined S everity Le vel 2 | |
| 329 | ||
| 330 | 28 Oct 201 6 – PKR Oc casionally when tryi ng to inst all a Remi nder Excha nge entry the follow ing messag e appears: “Index mi ssing, can not contin ue!” This occurs wh en a corru pted compo nent throw s off the line count and the i nternal in dex for th e Exchange entry is not at the correct l ine. It th e past fin ding the c orrupted c omponent h as been a matter of trial and error. To make it ea sier to fi nd corrupt ed compone nts a new check has been added that will attempt t o locate a nd display the corru pted compo nent. It w ill be run automatic ally when the intern al index i s not at t he correct location. The docum entation n eeds updat ed. Ticket #I1127916 9FY17. | |
| 331 | Routines: PXRMEXCC, PXRMEXCO - IEEE defi ned Severi ty Level 3 | |
| 332 | ||
| 333 | 04 Nov 201 6 – PKR Th e Function Finding V alue funct ion could only handl e CSUBs wi th three s ubscripts. This was causing a problem a t sites ne eding to u se CSUBs w ith more t han three subscripts , CA ticke t I1137010 4FY17. It has been g eneralized so it can now retur n values f or CSUBs w ith any nu mber of su bscripts. | |
| 334 | Routine: P XRMFF0 - I EEE define d Severity Level 2 | |
| 335 | ||
| 336 | ||
| 337 | T5 – T6 Ch anges: The se are the changes m ade to the T5 versio n to creat e the T6 v ersion. | |
| 338 | ||
| 339 | 09 Jan 201 7 – PKR A CPRS31 te st site re ported the following error: | |
| 340 | <UNDEFINED >FERROR+7^ PXRMOUTU * TEXT | |
| 341 | Last Globa l Ref: ^TM P("PXRM494 64266,2341 7",17143,4 94,"FERROR ","ERROR T RAP") | |
| 342 | . D ADDTX TA(2,PXRMR M,.NTXT,TE XT) | |
| 343 | There is a typo, TEX T should h ave been p assed by r eference. | |
| 344 | Routine: P XRMOUTU - IEEE defin ed Severit y Level 3 | |
| 345 | ||
| 346 | 13 Jan 201 7 – PKR On 01/06/201 7 the VSAC released updated el ectronic c linical qu ality meas ure value set for 20 17 reporti ng. The Vi sta Value Set files were updat ed to this release. The number of entrie s before a nd after t he update are listed in the fo llowing ta ble: | |
| 347 | ||
| 348 | ||
| 349 | Before | |
| 350 | After | |
| 351 | NLM VALUE SET CODING SYSTEMS | |
| 352 | 17 | |
| 353 | 17 | |
| 354 | NLM VALUE SETS | |
| 355 | 1006 | |
| 356 | 1006 | |
| 357 | NLM QUALIT Y MEASURE GROUPS | |
| 358 | 260 | |
| 359 | 260 | |
| 360 | ||
| 361 | - IEEE def ined Sever ity Level 2 | |
| 362 | ||
| 363 | 13 Jan 201 7 – PKR A CPRSV31 t est site r eported th e followin g error: | |
| 364 | $ZE= <UNDE FINED>RDEF +17^PXRMCD EF *PXRMPI D | |
| 365 | Last Globa l Ref: ^PX D(811.9,91 4,0) | |
| 366 | . S ^TMP(P XRMPID,$J, PXRMITEM," FERROR","C F.VA-REMIN DER DEFINI TION")="Th e reminder definitio n is inact ive" | |
| 367 | ||
| 368 | Analysis o f the erro r determin ed the cau se to be d ialog bran ching logi c using CF .VA-REMIND ER definit ion throug h term eva luation an d the remi nder to be evaluated is inacti ve. Becaus e it was i nactive an attempt w as made to record th e error in ^TMP but the variab le PXRMPID was not d efined cau sing the h ard error. PXRMPID i s defined at the sta rt of remi nder evalu ation but was not de fined for term evalu ation done outside o f reminder evaluatio n. The sol ution is t o modify t he standal one term e valuator: IEVALTER^P XRMATERM, to make su re PXRMPID is define d: | |
| 369 | I '$D(PXR MPID) D | |
| 370 | . N PXRMITE M S PXRMIT EM=TERMARR ("IEN") | |
| 371 | . S PXRMPID ="PXRM"_PX RMITEM_$H | |
| 372 | The routin es that ca ll IEVALTE R^PXRMTERM were modi fied to in cluded PXR MPID in th e argument list of t he call. | |
| 373 | Routine: P XRMDLLB, P XRMDRUG, P XRMRUL1, P XRMTERM - IEEE defin ed Severit y Level 1 | |
| 374 | ||
| 375 | 24 Jan 201 7 – PKR An thony’s te sting show ed the abo ve changes did not f ix the pro blem. He g ave me a g ood test c ase which I put in B LTEST^PXRM TEST and a nalysis us ing it lea d to the c onclusion that in di alogs TERM ^PXRMDLLB is the top -level for term eval uation so it is the place wher e PXRMITEM and PXRMP ID should be defined . That cha nge was ma de and it eliminated the PXRMI TEM undefi ned error. The quest ion is sho uld we bac k-out PXRM PID being passed as a paramete r to IEVAL TER^PXRMTE RM; yes it was remov ed. | |
| 376 | Routine: P XRMDLLB - IEEE defin ed Severit y Level 1 | |
| 377 | ||
| 378 | 24 Jan 201 7 – AGP Re minder Dia logs and R eminder Or der Checks will now display an error mes sage to th e end user when an e rror is fo und in the Reminder Evaluation . Also, a MailMan me ssage will be sent t o the Clin ical Remin ders mail group. | |
| 379 | Routines: PXRMDLL, P XRMORCH - IEEE defin ed Severit y Level 2 | |
| 380 | ||
| 381 | T6 – T7 Ch anges: The se are the changes m ade to the T6 versio n to creat e the T7 v ersion. | |
| 382 | ||
| 383 | 2 May 2017 - When SQ A did revi ew they no ticed that XU*8.0*65 7 was stil l listed i n the buil d descript ion and ta king it ou t requires a new bui ld. Since there were n’t any fu nctional c hanges we did not as k test sit es to inst all it. We will have them inst all T7 for productio n testing. These are the host files: | |
| 384 | ||
| 385 | CR_ICD-10_ FOLLOWUP_T 6.KID;1 | |
| 386 | 61853 25-JAN-201 7 08:22:49 .85 | |
| 387 | CR_ICD-10_ FOLLOWUP_T 7.KID;1 | |
| 388 | 61853 11-MAY-201 7 08:23:39 .09 | |
| 389 | ||
| 390 | ||
| 391 | T7 – T8 Ch anges: The se are the changes m ade to the T6 versio n to creat e the T7 v ersion. | |
| 392 | The VPS an d OR error s were due to improp erly writt en code in those pac kages. The solution was a one line chang e in Clini cal Remind ers. Puget Sound has installed the chang e and veri fied that it elimina tes the er rors. | |
| 393 | Template R evision Hi story | |
| 394 | Date | |
| 395 | Version | |
| 396 | Descriptio n | |
| 397 | Author | |
| 398 | June 2015 | |
| 399 | 1.6 | |
| 400 | Migrated t o latest A rtifact Te mplate, ed ited to co nform with latest Se ction 508 guidelines , and reme diated wit h Common L ook Office tool | |
| 401 | Process Ma nagement | |
| 402 | May 2015 | |
| 403 | 1.5 | |
| 404 | Reviewed a nd modifie d during t he PMAS Pr ocess Impr ovement Lo ckdown | |
| 405 | Process Ma nagement | |
| 406 | October 20 14 | |
| 407 | 1.4 | |
| 408 | Edited to conform wi th current Section 5 08 guideli nes and re mediated w ith Common Look Offi ce tool | |
| 409 | Process Ma nagement | |
| 410 | June 2014 | |
| 411 | 1.3 | |
| 412 | Removed si gnature re quirements for ESE R epresentat ive | |
| 413 | Process Ma nagement | |
| 414 | March 2013 | |
| 415 | 1.2 | |
| 416 | Formatted to current ProPath d ocumentati on standar ds and edi ted to con form with latest Alt ernative T ext (Secti on 508) gu idelines | |
| 417 | Process Ma nagement | |
| 418 | March 2013 | |
| 419 | 1.1 | |
| 420 | Updates fr om ETS | |
| 421 | ETS | |
| 422 | January 20 13 | |
| 423 | 1.0 | |
| 424 | Initial Ve rsion | |
| 425 | PMAS Busin ess Office |
Araxis Merge (but not the data content of this report) is Copyright © 1993-2016 Araxis Ltd (www.araxis.com). All rights reserved.