Produced by Araxis Merge on 3/30/2017 2:34:51 PM Eastern Daylight Time. See www.araxis.com for information about Merge. This report uses XHTML and CSS2, and is best viewed with a modern standards-compliant browser. For optimum results when printing this report, use landscape orientation and enable printing of background images and colours in your browser.
| # | Location | File | Last Modified |
|---|---|---|---|
| 1 | VA DBA Approval of Data Dictionary Changes.zip | PCL-5 MHAS RSD.docx | Thu Mar 30 13:30:52 2017 UTC |
| 2 | VA DBA Approval of Data Dictionary Changes.zip | PCL-5 MHAS RSD.docx | Thu Mar 30 17:06:43 2017 UTC |
| Description | Between Files 1 and 2 |
|
|---|---|---|
| Text Blocks | Lines | |
| Unchanged | 7 | 1400 |
| Changed | 6 | 12 |
| 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 | Posttrauma tic Stress Disorder Checklist 5 (PCL-5) and Mental Health As sistant St abilizatio n (MHAS) | |
| 2 | Database R edesign | |
| 3 | Increment 2 and 3 | |
| 4 | System Des ign Docume nt | |
| 5 | ||
| 6 | ||
| 7 | ||
| 8 | ||
| 9 | ||
| 10 | May 2016 | |
| 11 | Version 1. 5 | |
| 12 | ||
| 13 | Department of Vetera ns Affairs | |
| 14 | ||
| 15 | ||
| 16 | Revision H istory | |
| 17 | Date | |
| 18 | Version | |
| 19 | Descriptio n | |
| 20 | Author | |
| 21 | 11/29/16 | |
| 22 | 1.5 | |
| 23 | Technical Edit | |
| 24 | Aaron Lind strom PM, , C. Berni er, Tech W riter | |
| 25 | 3/16/2016 | |
| 26 | 1.5 | |
| 27 | Added mino r changes to wording for AERB requested informatio n | |
| 28 | Shawn Suit ers PD IT PM, TM 3, Leo Manmoh an Singh | |
| 29 | 3/15/2016 | |
| 30 | 1.4 | |
| 31 | Added requ ested info rmation fr om AERB | |
| 32 | Shawn Suit ers PD IT PM, TM 3, Leo Manmoh an Singh | |
| 33 | 2/18/2016 | |
| 34 | 1.3 | |
| 35 | Tech Write r review | |
| 36 | Shawn Suit ers PD IT PM, TM 3, C. Bernier , Tech Wri ter | |
| 37 | 2/1/2016 | |
| 38 | 1.2 | |
| 39 | Edits to S DD | |
| 40 | Shawn Suit ers PD IT PM, TM 3 | |
| 41 | 1/27/2016 | |
| 42 | 1.1 | |
| 43 | Draft upda tes | |
| 44 | Leo Manmoh an Singh | |
| 45 | 8/9/2015 | |
| 46 | 1 | |
| 47 | Initial Dr aft | |
| 48 | Shawn Suit ers PD IT PM, TM 3 | |
| 49 | ||
| 50 | ||
| 51 | ||
| 52 | ||
| 53 | ||
| 54 | Artifact R ationale | |
| 55 | The System Design Do cument (SD D) is a du al-use doc ument that provides the concep tual desig n as well as the as- built desi gn. This d ocument wi ll be upda ted as the product i s built, t o reflect the as-bui lt product . | |
| 56 | ||
| 57 | ||
| 58 | ||
| 59 | Activity | |
| 60 | New Capabi lity (1) | |
| 61 | Feature En hancement (2) | |
| 62 | Field Depl oyment (A) | |
| 63 | Yes | |
| 64 | Yes | |
| 65 | Cloud/Web Deployment (B) | |
| 66 | Yes | |
| 67 | Yes | |
| 68 | Mobile App lication ( C) | |
| 69 | Yes | |
| 70 | Yes | |
| 71 | ||
| 72 | Table of C ontents | |
| 73 | 1.Introduc tion1 | |
| 74 | 1.1.Scope1 | |
| 75 | 1.2.User P rofiles1 | |
| 76 | 2.Backgrou nd2 | |
| 77 | 2.1.Overvi ew of the System2 | |
| 78 | 2.2.Overvi ew of the Business P rocess2 | |
| 79 | 2.3.Overvi ew of the Significan t Requirem ents2 | |
| 80 | 3.Conceptu al Design3 | |
| 81 | 3.1.Concep tual Appli cation Des ign3 | |
| 82 | 3.1.1.Appl ication Co ntext3 | |
| 83 | 3.1.2.High -Level App lication D esign4 | |
| 84 | 3.1.3.Appl ication Lo cations4 | |
| 85 | 3.2.Concep tual Data Design4 | |
| 86 | 3.2.1.Proj ect Concep tual Data Model4 | |
| 87 | 3.2.2.Data base Infor mation5 | |
| 88 | 3.2.3.User Interface Data Mapp ing5 | |
| 89 | 3.3.Concep tual Infra structure Design5 | |
| 90 | 3.3.1.Syst em Critica lity and H igh Availa bility5 | |
| 91 | 3.3.2.Spec ial Techno logy5 | |
| 92 | 3.3.3.Tech nology Loc ations6 | |
| 93 | 3.3.4.Conc eptual Inf rastructur e Diagram6 | |
| 94 | 4.System A rchitectur e7 | |
| 95 | 4.1.Hardwa re Archite cture7 | |
| 96 | 4.2.Softwa re Archite cture7 | |
| 97 | 4.3.Networ k Architec ture7 | |
| 98 | 4.4.Servic e Oriented Architect ure / ESS7 | |
| 99 | 4.5.Enterp rise Archi tecture7 | |
| 100 | 5.Data Des ign8 | |
| 101 | 5.1.DBMS F iles10 | |
| 102 | 5.2.Non-DB MS Files11 | |
| 103 | 5.3.Data V iew11 | |
| 104 | 6.Detailed Design12 | |
| 105 | 6.1.Hardwa re Detaile d Design12 | |
| 106 | 6.2.Softwa re Detaile d Design12 | |
| 107 | 6.2.1.Conc eptual Des ign12 | |
| 108 | 6.2.1.1. P roduct Per spective12 | |
| 109 | 6.2.1.1.1. User Inter faces12 | |
| 110 | 6.2.1.1.2. Hardware I nterfaces1 2 | |
| 111 | 6.2.1.1.3. Software I nterfaces1 2 | |
| 112 | 6.2.1.1.4. Communicat ions Inter faces12 | |
| 113 | 6.2.1.1.5. Memory Con straints12 | |
| 114 | 6.2.1.1.6. Special Op erations12 | |
| 115 | 6.2.1.2.Pr oduct Feat ures12 | |
| 116 | 6.2.1.3.De pendencies and Const raints13 | |
| 117 | 6.2.1.4.Us er Charact eristics13 | |
| 118 | 6.2.2.Spec ific Requi rements13 | |
| 119 | 6.2.2.1Dat abase Repo sitory13 | |
| 120 | 6.2.2.2Sys tem Featur es13 | |
| 121 | 6.2.2.3Des ign Elemen t Tables13 | |
| 122 | 6.2.2.3.1R outines (E ntry Point s)13 | |
| 123 | 6.2.2.3.2T emplates15 | |
| 124 | 6.2.2.3.3B ulletins15 | |
| 125 | 6.2.2.3.4D ata Entrie s Affected by the De sign15 | |
| 126 | 6.2.2.3.5U nique Reco rd(s)15 | |
| 127 | 6.2.2.3.6F ile or Glo bal Size C hanges15 | |
| 128 | 6.2.2.3.7M ail Groups 15 | |
| 129 | 6.2.2.3.8S ecurity Ke ys15 | |
| 130 | 6.2.2.3.9O ptions15 | |
| 131 | 6.2.2.3.10 Protocols1 5 | |
| 132 | 6.2.2.3.11 Remote Pro cedure Cal l (RPC)16 | |
| 133 | 6.2.2.3.12 Constants Defined in Interface 16 | |
| 134 | 6.2.2.3.13 Variables Defined in Interface 16 | |
| 135 | 6.2.2.3.14 Types Defi ned in Int erface16 | |
| 136 | 6.2.2.3.15 GUI16 | |
| 137 | 6.2.2.3.16 GUI Classe s16 | |
| 138 | 6.2.2.3.17 Current Fo rm16 | |
| 139 | 6.2.2.3.18 Modified F orm16 | |
| 140 | 6.2.2.3.19 Components on Form16 | |
| 141 | 6.2.2.3.20 Methods16 | |
| 142 | 6.2.2.3.21 Special Re ferences16 | |
| 143 | 6.2.2.3.22 Class Even ts16 | |
| 144 | 6.2.2.3.23 Class Meth ods16 | |
| 145 | 6.2.2.3.24 Class Prop erties16 | |
| 146 | 6.2.2.3.25 Uses Claus e16 | |
| 147 | 6.2.2.3.26 Forms16 | |
| 148 | 6.2.2.3.27 Functions1 7 | |
| 149 | 6.2.2.3.28 Dialog17 | |
| 150 | 6.2.2.3.29 Help Frame 17 | |
| 151 | 6.2.2.3.30 HL7 Applic ation Para meter17 | |
| 152 | 6.2.2.3.31 HL7 Logica l Link17 | |
| 153 | 6.2.2.3.32 COTS Inter face17 | |
| 154 | 6.3.Networ k Detailed Design17 | |
| 155 | 6.4.Securi ty and Pri vacy18 | |
| 156 | 6.4.1Secur ity18 | |
| 157 | 6.4.2Priva cy18 | |
| 158 | 6.5.Servic e Oriented Architect ure / ESS Detailed D esign18 | |
| 159 | 6.5.1.Serv ice Descri ption for <Consumed Service Na me>18 | |
| 160 | 6.5.2.Serv ice Design for <Prov ided Servi ce Name>18 | |
| 161 | 6.5.2.1Int roduction1 8 | |
| 162 | 6.5.2.1.1P urpose and Scope of Service18 | |
| 163 | 6.5.2.1.2L inks to Ot her Docume nts18 | |
| 164 | 6.5.2.2Ser vice Detai ls18 | |
| 165 | 6.5.2.2.1S ervice Ide ntificatio n18 | |
| 166 | 6.5.2.2.2S ervice Ver sions19 | |
| 167 | 6.5.2.2.3S ummary of Design and Platform Details19 | |
| 168 | 6.5.2.2.3. 1SOA Patte rn(s) Impl emented19 | |
| 169 | 6.5.2.2.3. 2COTS Plat form vendo r names an d versions for hosti ng platfor m19 | |
| 170 | 6.5.2.3Dep endencies1 9 | |
| 171 | 6.5.2.4Ser vice Desig n Details1 9 | |
| 172 | 6.5.2.4.1I nterface T echnical S pecs19 | |
| 173 | 6.5.2.4.1. 1Service I nvocation Type19 | |
| 174 | 6.5.2.4.1. 2Service I nterface T ype19 | |
| 175 | 6.5.2.4.1. 3Service N ame19 | |
| 176 | 6.5.2.4.1. 4Interface 19 | |
| 177 | 6.5.2.4.1. 5End Point s19 | |
| 178 | 6.5.2.4.1. 6Operation s or Metho ds19 | |
| 179 | 6.5.2.4.1. 7Message S chemas19 | |
| 180 | 6.5.2.4.2I nformation Model19 | |
| 181 | 6.5.2.4.2. 1Class Dia gram and D escription of Entiti es Involve d19 | |
| 182 | 6.5.2.4.2. 2Mappings from ELDM to Standar ds Based S chemas19 | |
| 183 | 6.5.2.4.3B ehavior Mo del (AKA U se Case Re alization) 20 | |
| 184 | 6.5.2.4.3. 1Use Cases (Use Case Model)20 | |
| 185 | 6.5.2.4.3. 2Interacti on Diagram s20 | |
| 186 | 6.5.2.5Gap Analysis2 0 | |
| 187 | 6.5.2.5.1V ariances f rom Enterp rise Targe t Architec ture20 | |
| 188 | 6.5.2.5.2V ariances f rom SLDs20 | |
| 189 | 6.5.2.5.3V ariances f rom Standa rds and Po licies20 | |
| 190 | 6.5.2.5.4J ustificati on for Exc eptions an d Mitigati on20 | |
| 191 | 7.External System In terface De sign21 | |
| 192 | 7.1.Interf ace Archit ecture21 | |
| 193 | 7.2.Interf ace Detail ed Design2 1 | |
| 194 | 8.Human-Ma chine Inte rface22 | |
| 195 | 8.1.Interf ace Design Rules22 | |
| 196 | 8.2.Inputs 22 | |
| 197 | 8.3.Output s22 | |
| 198 | 8.4.Naviga tion Hiera rchy22 | |
| 199 | 9.Attachme nt A – App roval Sign atures23 | |
| 200 | A.Addition al Informa tion24 | |
| 201 | A.1.Identi fication o f Technolo gy and Sta ndards24 | |
| 202 | A.2.Constr aining Pol icies, Dir ectives an d Procedur es24 | |
| 203 | A.3.Requir ements Tra ceability Matrix24 | |
| 204 | A.4.Packag ing and In stallation 24 | |
| 205 | A.5.Design Metrics25 | |
| 206 | A.6.Requir ed Technic al Documen ts25 | |
| 207 | A.7.Acrony m List and Glossary2 5 | |
| 208 | ||
| 209 | Introducti on | |
| 210 | This patch redesigns the datab ase for in the Menta l Health A ssistant v 3 (MHA3) c orrecting several is sues that have halte d the prog ression an d hindered the abili ties of Ph ysicians u sing the M HA3. The r edesign ad dresses th ese issues and produ ces a data base that will allow for futur e instrume nt creatio n / implem entation. Furthermor e, the cur rent imple mentation of the dat abase will be change d to lever age the ca pabilities of FileMa n. | |
| 211 | ||
| 212 | Scope | |
| 213 | The scope of this do cument is limited to the Post Traumatic Stress Dis order Chec klist (PCL -5) MHAS developmen t project. This will include V eterans Af fairs cont ractor dev elopment m odificatio ns to the existing M HA3 databa se. Modifi cations wi ll be made to the da tabase tha t include capabiliti es for Fil eMan, Inst rument sco ring, Nati onal Clini cal Remind ers and He alth Summa ry, additi on of Syst ematized N omenclatur e of Medic ine (SNOME D) codes, correction of Window s Secure D esktop, an d address requiremen ts in the Business R equirement s Document (BRD) and Requireme nts Specif ication Do cument (RS D). These changes wi ll be addr essed in t wo six (6) month inc rements of developme nt. | |
| 214 | ||
| 215 | User Profi les | |
| 216 | Users resp onsible fo r entering data via the instru ments (que stionnaire s) will in clude Ment al Health profession als, clini cians, and veterans who can ac cess the i nstruments for self- reporting. | |
| 217 | The techni cal backgr ound and d egree of s ophisticat ion of the individua l users wi ll vary. T he Mental Health Cli nician nee ds the abi lity to ac cess the i nstruments and admin ister them when aski ng the pat ient the q uestions i n a clinic al setting . The vete ran that d esires to self-repor t may have physical, visual, c ognitive, and learni ng impairm ents. | |
| 218 | ||
| 219 | Background | |
| 220 | Overview o f the Syst em | |
| 221 | The MHA3 p rovides a mechanism to adminis ter and sc ore standa rdized que stionnaire s and psyc hological tests. It provides a mechanism for both patients a nd clinici ans to ent er respons es to thes e instrume nts and al so provide s automate d scoring of the ins trument. M HA3 runs i n conjunct ion with C PRS (Compu terized Pa tient Reco rd System) . A user o f CPRS can branch to MHA3 as n eeded via the CPRS T ools menu. MHA3 inst rument res ults may b e used by Clinical R eminders a s a partic ipant in r eminder lo gic or as a part of a Reminder Dialog. H ealth Summ ary also a llows the display of MHA3 inst rument res ults. | |
| 222 | ||
| 223 | Overview o f the Busi ness Proce ss | |
| 224 | MHA3 is al ready runn ing as par t of Veter ans Health Informati on Systems and Techn ology Arch itecture ( VistA); th ere is no change in the busine ss process . The Ment al Health V. 5.01 pa ckage is d esigned to provide a means of rapidly ga thering, s toring, an d reportin g clinical informati on for pat ients rece iving ment al health treatment and /or as sistance w ith vocati onal issue s. The cli nical info rmation st ored in th e VistA da tabase is readily ac cessible t o clinical staff thr oughout th e various Mental Hea lth Treatm ent Servic e areas an d other cl inics in t he Medical Center. I t can also be sent t o enterpri se storage facilitie s such as the Austin Informati on Technol ogy Center (AITC). | |
| 225 | For additi onal detai ls referen ce section 3.1.2, 3. 2.1 and Se ction 6. | |
| 226 | Overview o f the Sign ificant Re quirements | |
| 227 | The signif icant requ irements f or Increme nt two and three are combined for one re lease of P atch YS*5. 01*123.The Business Requiremen ts Documen t (BRD) is located a t: | |
| 228 | http:// DNS /anotebk.a sp?proj=18 38 | |
| 229 | The Requir ements Spe cification Document (RSD) for PCL-5 and stabilizat ion of the MHA3 is l ocated at: | |
| 230 | Rational D ashboard/S ource Cont rol/Stream s/MHLTH_MH AS_PCL5/ M HLTH_MHAS_ PCL5_Docum entation | |
| 231 | The patch YS*5.01*12 3 for incr ement two (2) will a ddress the following requireme nts: | |
| 232 | Section 1. 1.1.5 Data base | |
| 233 | Section 1. 1.1.7 Syst ematized N omenclatur e of Medic ine (SNOME D) codes | |
| 234 | ||
| 235 | The patch YS*5.01*12 3 for incr ement thre e (3) will address t he followi ng require ments: | |
| 236 | Section 1. 1.1.6 Nati onal Clini cal Remind ers and He alth Summa ry | |
| 237 | Section 1. 1.1.8 Wind ows Secure Desktop | |
| 238 | Conceptual Design | |
| 239 | This secti on will de scribe MHA 3 as curre ntly desig ned. The d esign is n ot affecte d by the r elease of an updated file entr y. | |
| 240 | Conceptual Applicati on Design | |
| 241 | MHA3 is a Windows cl ient appli cation wri tten in De lphi. It c ommunicate s with Vis tA via the Remote Pr ocedure Ca ll Broker (RPC Broke r). The ex isting arc hitecture of the sys tem will n ot change. This patc h updates the file e ntries for the PCL-5 instrumen t. It also adds some filtering logic to protect Cl inical Rem inders and Health Su mmary from displayin g inaccura te instrum ent scores . | |
| 242 | Applicatio n Context | |
| 243 | Mental Hea lth Assist ant is a p ackage wit hin VistA and does n ot interfa ce to exte rnal syste ms. There is a clien t user int erface whi ch is laun ched from CPRS. Like CPRS, the client ap plication communicat es with Vi stA via th e RPC Brok er. | |
| 244 | Figure 1: Mental Hea lth Assist ant | |
| 245 | ||
| 246 | ||
| 247 | Table 1 (G rouping): Applicatio n Context Descriptio n | |
| 248 | Object | |
| 249 | ID | |
| 250 | Name | |
| 251 | Descriptio n | |
| 252 | Interface Name | |
| 253 | Interface System | |
| 254 | CPRS Clien t | |
| 255 | CPRS Clien t | |
| 256 | CPRS Windo ws executa ble client applicati on. | |
| 257 | RPC Broker | |
| 258 | VistA | |
| 259 | MHA Client | |
| 260 | MHA Client | |
| 261 | Mental Hea lth Assist ant execut able clien t applicat ion – laun ched from CPRS. | |
| 262 | RPC Broker | |
| 263 | VistA | |
| 264 | High-Level Applicati on Design | |
| 265 | This is a simple Vis tA patch w ith no maj or compone nts to be built or m odified. T he design of the Men tal Health Assistant , as it cu rrently ex ists is no t being ch anged. The as-is des ign is sho wn in Figu re 2. | |
| 266 | Figure 2: Applicatio n Design | |
| 267 | ||
| 268 | Applicatio n Location s | |
| 269 | The applic ation runs as a Vist A package in locatio ns where V istA is in stalled. | |
| 270 | Table 2: A pplication Locations | |
| 271 | Applicatio n Componen t | |
| 272 | Descriptio n | |
| 273 | Location a t Which Co mponent is Run | |
| 274 | Type | |
| 275 | VistA | |
| 276 | VistA pack age – a su bset of th e Mental H ealth pack age. | |
| 277 | All VistA instances. | |
| 278 | N/A | |
| 279 | Table 3: A pplication Users | |
| 280 | Applicatio n Componen t | |
| 281 | Location | |
| 282 | User | |
| 283 | VistA | |
| 284 | All VAMCs and Clinic with Vist A access | |
| 285 | Mental Hea lth Clinic ian | |
| 286 | Conceptual Data Desi gn | |
| 287 | Project Co nceptual D ata Model | |
| 288 | The databa se for Men tal Health Assistant , as it cu rrently ex ists, is n ot being c hanged. Th e database consists of a set o f Fileman files. The as-is des ign is sho wn in Figu re 3. Ther e are two main sets of tables in the dat abase. One set is us ed to desc ribe the c ontent, la yout, and behavior o f mental h ealth inst ruments. T he other s et is used to store answers fr om or on b ehalf of t he patient . Below is the curre nt data mo del. No mo dification s to the d ata model are being changed. | |
| 289 | Figure 3: Project Co nceptual D ata Model | |
| 290 | ||
| 291 | ||
| 292 | Database I nformation | |
| 293 | Database s tructure i s being ch anged from a non-Fil eman frien dly archit ecture to Fileman fr iendly str ucture. Th e informat ion is exp lained in section 5 Database D esign. | |
| 294 | User Inter face Data Mapping | |
| 295 | Mental Hea lth Assist ant is an applicatio n that all ows the us er to sele ct and ins trument, a dminister an instrum ent, and r eview the responses and scores from prev iously ent ered instr uments. Th ere are no user inte rface comp onents in this patch . | |
| 296 | ||
| 297 | Conceptual Infrastru cture Desi gn | |
| 298 | There are no changes to the Vi stA infras tructure i n this pat ch. Delphi / MUMPS u ses a clie nt / serve r design c urrently u tilized in the VA De lphi/ MUMP S applicat ions. | |
| 299 | System Cri ticality a nd High Av ailability | |
| 300 | This patch has very low impact to the op eration of VistA. Th e disaster relief pl ans for Vi stA are no t affected by this p atch. | |
| 301 | Special Te chnology | |
| 302 | N/A. No sp ecial tech nology is involved i n the patc h. | |
| 303 | Technology Locations | |
| 304 | N/A. This is a simpl e VistA pa tch – ther e are no s pecial tec hnology co mponents. | |
| 305 | Conceptual Infrastru cture Diag ram | |
| 306 | N/A. There are no ex ternal int erfaces or special e nvironment s involved . | |
| 307 | System Arc hitecture | |
| 308 | Hardware A rchitectur e | |
| 309 | There are no hardwar e modifica tions with this Ment al Health Assistant release; h owever, pr evious pac kages have been run on the sta ndard hard ware platf orms used by the Dep artment of Veterans Affairs He alth Care System fac ilities. T hese syste ms consist of standa rd or upgr aded Alpha AXP clust ers or sta ndard inte l hardware Windows o perating s ystem and run either Cache-VMS , Cache-NT , Cache- O penVMS, or Cache- Wi ndows Serv er 2008 or higher. | |
| 310 | Software A rchitectur e | |
| 311 | There is n o change i n software architect ure. | |
| 312 | Network Ar chitecture | |
| 313 | No communi cation wit hin the sy stem, such as local area netwo rks (LANs) and buses are being added, re moved, or modified. MHA3 uses local Netw ork config urations t o communic ate betwee n the MHA3 applicati on and Vis tA. For in formation on Network Architect ure please reference the VDL. | |
| 314 | Service Or iented Arc hitecture / ESS | |
| 315 | This patch updates t he file en tries and target sou rce mappin g that rep resent the MHA3. The re are no new servic es provide d or consu med. | |
| 316 | Enterprise Architect ure | |
| 317 | VA Technic al Referen ce Model ( TRM)/ Stan dards are used in th e developm ent, opera tions, and sustainme nt of Vist A is shown in Table 5. All TRM applicati ons are ap proved by the One-VA TRM VA Te chnology L icense Tea m. | |
| 318 | TRM Link h ttp:// DNS /TRMHomePa ge.asp | |
| 319 | Table 5: T RM Tools U sed | |
| 320 | Applicatio n | |
| 321 | TRM Compli ant | |
| 322 | Environmen t | |
| 323 | License | |
| 324 | MUMPS | |
| 325 | (Massachus etts Gener al Hospita l Utility Multi-Prog ramming Sy stem) | |
| 326 | Yes | |
| 327 | All | |
| 328 | ISO/IEC 11 756:1999 | |
| 329 | Caché | |
| 330 | Yes | |
| 331 | All | |
| 332 | Commercial / v2014 | |
| 333 | VA M Progr amming Sta ndard | |
| 334 | Yes | |
| 335 | All | |
| 336 | VA Standar d Document . http:// DN S
|
|
| 337 | dWinlock | |
| 338 | Yes | |
| 339 | All | |
| 340 | Commercial / v3.3 | |
| 341 | RAD Studio version D elphi XE6 | |
| 342 | Yes | |
| 343 | All | |
| 344 | Commercial / version Delphi XE 6 | |
| 345 | ||
| 346 | Data Desig n | |
| 347 | This patch changes t he data de sign of a few files from what appears to be more S QL/relatio nal design to a more Fileman/V istA frien dly design . This is done by mo ving some of the sub ordinate d ata of “MH TESTS AND SURVEYS,” scattered in many f iles, into subfiles. Similar c hanges are being mad e to “MH A DMINISTRAT IONS” and to “MH BAT TERY” file s. The mos t current up-to-date list of f iles being changed i s located at: | |
| 348 | Rational D ashboard/S ource Cont rol/Stream s/MHLTH_MH AS_PCL5/MH LTH_MHAS_P CL5_Docume ntation/YS _501_123/P CL-5 MHAS File Redes ign Docume nts | |
| 349 | The diagra m below, “ MH Files.p df” lists the “as-is ” state of data stru cture. And the diagr am in “MH Files-Rede sign.pdf” lists the “to-be” ar chitecture . | |
| 350 | ||
| 351 | Figure 2 - MH Files - As-Is Da ta Structu re | |
| 352 | ||
| 353 | Figure 3 M H Files – To-Be Data Structure | |
| 354 | ||
| 355 | ||
| 356 | NOTE: None of the ex isting fil es are phy sically re moved from the datab ase. These will be l eft in pla ce for his torical pu rposes as well as fo r validati ng new dat a in the n ew structu re after p atch insta ll to ensu re complet e and accu rate data conversion . After th e system h as been op erational for a year or more, the old fi les may be removed i n a separa te patch o nce it is determined that ther e is no fu rther need to valida te any con verted dat a at any s ite. | |
| 357 | Separately the patch also intr oduces “SN OMED CODE” field in files list ed below. This field is databa se only an d does not have a GU I componen t for this patch. | |
| 358 | ||
| 359 | ||
| 360 | DBMS Files | |
| 361 | This patch adds new subfiles t o the MH T ESTS AND S URVEYS (#6 01.71), th e MH ADMIN ISTRATIONS (#601.84) and the M H BATTERY (#601.99) files. | |
| 362 | Table 6: N ew Sub-fil es in this patch. | |
| 363 | File Name | |
| 364 | Original f ile name c hanged to Sub File | |
| 365 | MH ADMINIS TRATIONS ( #601.84) | |
| 366 | ANSWERS | |
| 367 | ||
| 368 | RESULTS | |
| 369 | MH BATERY (#601.99) | |
| 370 | INSTRUMENT | |
| 371 | ||
| 372 | USER | |
| 373 | MH TESTS A ND SURVEYS (#601.61) | |
| 374 | INSTRUMENT CONTENT | |
| 375 | ||
| 376 | INSTRUMENT RULES | |
| 377 | ||
| 378 | INSTRUMENT SCALE GRO UPS | |
| 379 | ||
| 380 | INSTRUMENT SECTIONS | |
| 381 | ||
| 382 | REPORT TEM PLATE | |
| 383 | ||
| 384 | SKIPPED QU ESTIONS | |
| 385 | ||
| 386 | This patch also adds new “SNOM ED CODE” f ields to t he MH TEST S AND SURV EYS file ( #601.71) a nd in MH A DMINISTRAT IONS (601. 84) file u nder the s ubfile “An swers” and subfile “ Results” a s shown in Table 6b. This addi tion of SN OMED CODE file is co mpletely u nrelated t o the desi gn change listed abo ve. | |
| 387 | Table 6b: New Fields in this p atch | |
| 388 | File -> Fi eld Name | |
| 389 | Field | |
| 390 | Number | |
| 391 | Type | |
| 392 | Size | |
| 393 | MH TESTS A ND SURVEYS (#601.71) -> SNOMED CODE | |
| 394 | #97 | |
| 395 | Free Text | |
| 396 | 80 bytes | |
| 397 | ADMINISTRA TIONS (601 .84) -> An swers (mul tiple) -> SNOMED COD E | |
| 398 | #14 (multi ple) -> #3 | |
| 399 | Free Text | |
| 400 | 80 bytes | |
| 401 | ADMINISTRA TIONS (601 .84) -> Re sults (mul tiple) -> SNOMED COD E | |
| 402 | #15 (multi ple) -> #6 | |
| 403 | Free Text | |
| 404 | 80 bytes | |
| 405 | ||
| 406 | These new “SNOMED CO DE” fields will be u sed only o n the data base and t here is no correspon ding GUI c omponent. The fields will be p opulated b y function ality in s eparate fu ture relea ses outsid e of the s cope of th is patch. | |
| 407 | ||
| 408 | Non-DBMS F iles | |
| 409 | N/A. There are no fi les outsid e of the V istA FileM an databas e. | |
| 410 | ||
| 411 | Data View | |
| 412 | The data f iles chang es listed in previou s sections are all a ccessed us ing RPCs a nd the RPC interface s are unch anged. As a result, there are no changes in this p atch that alter the data view. | |
| 413 | Detailed D esign | |
| 414 | Hardware D etailed De sign | |
| 415 | MHA3 is a Client-Ser ver applic ation deli vered on a networked , Intel-pr ocessor-ba sed comput er. The c omputer ha s the VA-s tandard hu man interf ace device s: a keybo ard and a mouse. Bec ause MHA3 is designe d to be ab le to be u sed by the visually impaired, the system also incl udes a set of speake rs or head phones. | |
| 416 | Software D etailed De sign | |
| 417 | Conceptual Design | |
| 418 | There is n o change i n the GUI design of Mental Hea lth Assist ant for in crements 2 and 3 dep icted in t his docume nt. | |
| 419 | 6.2.1.1. P roduct Per spective | |
| 420 | 6.2.1.1.1. User Inter faces | |
| 421 | The MHA3 G UI will co mply with the genera l requirem ents for a ll VistA® applicatio ns as spec ified in t he VistA G raphical U ser Interf ace Standa rds and Co nventions document, Section 4, Look and Feel. | |
| 422 | 6.2.1.1.2. Hardware I nterfaces | |
| 423 | N/A. There are no ha rdware com ponents fo r this pat ch. | |
| 424 | 6.2.1.1.3. Software I nterfaces | |
| 425 | MHA3 requi res the fo llowing so ftware on the VistA servers: | |
| 426 | FileMan v2 2.2 | |
| 427 | MailMan v8 .0 | |
| 428 | Kernel v8. 0 | |
| 429 | MHA3 can c onnect wit h the foll owing soft ware: | |
| 430 | CPRS (curr ent Versio n) | |
| 431 | 6.2.1.1.4. Communicat ions Inter faces | |
| 432 | There are no special communica tion inter faces requ ired for t his functi onality. | |
| 433 | 6.2.1.1.5. Memory Con straints | |
| 434 | There are no memory constraint s. | |
| 435 | 6.2.1.1.6. Special Op erations | |
| 436 | There are no special operation s required to implem ent Instru ments. | |
| 437 | 6.2.1.2.Pr oduct Feat ures | |
| 438 | The softwa re feature s enabled by this pa tch are: | |
| 439 | The MHA3 i nstruments that were scored by Aux_DLL w ill no lon ger scored be scored by the Au x_DLL and will inste ad be scor ed in Vist A database using new routines introduced in this p atch. | |
| 440 | GUI design will not be changed because i t is writt en intelli gently to first look in the DL L for scor ing and if DLL doesn ’t do the scoring fo r an instr ument it a utomatical ly goes to the VistA database for scorin g. As a re sult, the removal of MHA3 inst ruments fr om Aux_DLL will auto matically cause the GUI to uti lize the s coring alg orithms on the VistA database. | |
| 441 | SNOMED cod es added i n this pat ch do not have a GUI component and will not cause any GUI ch anges. | |
| 442 | 6.2.1.3.De pendencies and Const raints | |
| 443 | YS*5.01*10 5 has been nationall y deployed for sever al years. There are no additio nal depend encies or constraint s. | |
| 444 | 6.2.1.4.Us er Charact eristics | |
| 445 | MHA3 is us ed by ment al health clinicians . Patients may optio nally be a sked to us e the ques tionnaire portion of MHA3. Thi s patch wi ll make th e PCL-5 in strument a vailable t o both cli nicians an d patients . The admi nistration of the PC L-5 instru ment is th e same as the existi ng mental health ins truments. | |
| 446 | Specific Requiremen ts | |
| 447 | 6.2.2.1Dat abase Repo sitory | |
| 448 | N/A. There is no cha nge in the database repository . | |
| 449 | 6.2.2.2Sys tem Featur es | |
| 450 | This patch is the se cond incre ment of th e features described in the RS D and RTM found at: | |
| 451 | http:/ DNS v/warboard /anotebk.a sp?proj=18 38 | |
| 452 | Design Ele ment Table s | |
| 453 | 6.2.2.3.1R outines (E ntry Point s) | |
| 454 | This patch does not change exi sting rout ines but a dds new en try points and new l ogic to so me of them . It also modifies e xisting RP Cs and red irects the calls fro m those RP Cs to new entry poin ts. The up to date l isting of routines a nd RPCs is at: | |
| 455 | http:// DNS /projects/ PCL5MHAS/D ocuments/P CL-5%20MHA S%20File%2 0Redesign% 20Document s/MHA%20RP Cs.xlsx | |
| 456 | Figure 4 M HA related RPCs and Routines | |
| 457 | ||
| 458 | ||
| 459 | ||
| 460 | ||
| 461 | 6.2.2.3.2T emplates | |
| 462 | N/A. No te mplates ar e involved . | |
| 463 | 6.2.2.3.3B ulletins | |
| 464 | N/A. No bu lletins ar e involved . | |
| 465 | 6.2.2.3.4D ata Entrie s Affected by the De sign | |
| 466 | N/A. No Da ta Entries are affec ted. | |
| 467 | 6.2.2.3.5U nique Reco rd(s) | |
| 468 | N/A. No Un ique recor ds are inv olved. | |
| 469 | 6.2.2.3.6F ile or Glo bal Size C hanges | |
| 470 | The change in file s ize with t his patch is depende nt on the site. Exis ting files are uncha nged and n ew subfile s size at startup wi ll approxi mately mat ch the siz e of curre nt data fi le they’re replacing . | |
| 471 | 6.2.2.3.7M ail Groups | |
| 472 | N/A. No ma il groups are involv ed. | |
| 473 | 6.2.2.3.8S ecurity Ke ys | |
| 474 | These secu rity keys have been in place a nd will no t change w ith this d evelopment . Sites wi ll allocat e the foll owing secu rity keys to appropr iate site personnel: | |
| 475 | Name Descript ion | |
| 476 | YSCL AUTHO RIZED - Th e presence of this k ey designa tes an aut horized Cl ozapine Pr ovider. | |
| 477 | ||
| 478 | YSD - Allo ws verific ation of I CD diagnos es. This is a clini cal privil ege. The chief of p sychiatry will deter mine who m ay have th is key. | |
| 479 | ||
| 480 | YSP - Prov ides acces s to psych ological t est option s. The Ch ief of Psy chology Se rvice will determine who may h ave this k ey. | |
| 481 | ||
| 482 | YSQ - Allo ws verific ation of D SM-III dia gnoses. T he Chiefs of Clinica l Services will dete rmine who may have t his key. | |
| 483 | ||
| 484 | YSZ - Allo ws Mental Health tec hnicians/a ides to qu eue tests/ interviews after com pletion. | |
| 485 | ||
| 486 | 6.2.2.3.9O ptions | |
| 487 | N/A. No op tions are involved. | |
| 488 | 6.2.2.3.10 Protocols | |
| 489 | N/A. No pr otocols ar e involved . | |
| 490 | 6.2.2.3.11 Remote Pro cedure Cal l (RPC) | |
| 491 | There are updates to existing RPCs inter nal functi onality bu t no chang es for any external users of t he RPCs. F or a compl ete list o f RPCs ple ase see se ction on R outines. | |
| 492 | 6.2.2.3.12 Constants Defined in Interface | |
| 493 | N/A. No in terfaces a re involve d. | |
| 494 | 6.2.2.3.13 Variables Defined in Interface | |
| 495 | N/A. No in terfaces a re involve d. | |
| 496 | 6.2.2.3.14 Types Defi ned in Int erface | |
| 497 | N/A. No in terfaces a re involve d. | |
| 498 | 6.2.2.3.15 GUI | |
| 499 | N/A. The G UI is not modified. | |
| 500 | 6.2.2.3.16 GUI Classe s | |
| 501 | N/A. The G UI is not modified. | |
| 502 | 6.2.2.3.17 Current Fo rm | |
| 503 | N/A. No fo rms are mo dified. | |
| 504 | 6.2.2.3.18 Modified F orm | |
| 505 | N/A. No fo rms are mo dified. | |
| 506 | 6.2.2.3.19 Components on Form | |
| 507 | N/A. No fo rms are mo dified. | |
| 508 | 6.2.2.3.20 Methods | |
| 509 | N/A. No me thods are involved. | |
| 510 | 6.2.2.3.21 Special Re ferences | |
| 511 | N/A. There are no sp ecial refe rences. | |
| 512 | 6.2.2.3.22 Class Even ts | |
| 513 | N/A. There are no cl ass events . | |
| 514 | 6.2.2.3.23 Class Meth ods | |
| 515 | N/A. There are no cl ass method s. | |
| 516 | 6.2.2.3.24 Class Prop erties | |
| 517 | N/A. There are no cl ass proper ties. | |
| 518 | 6.2.2.3.25 Uses Claus e | |
| 519 | N/A. No us es clause is involve d. | |
| 520 | 6.2.2.3.26 Forms | |
| 521 | N/A. No fo rms are mo dified. | |
| 522 | 6.2.2.3.27 Functions | |
| 523 | N/A. No fu nctions ar e added/mo dified. | |
| 524 | 6.2.2.3.28 Dialog | |
| 525 | N/A. There are no ch anges to t he DIALOG file. | |
| 526 | 6.2.2.3.29 Help Frame | |
| 527 | N/A. There are no ch anges to H elp Frames . | |
| 528 | 6.2.2.3.30 HL7 Applic ation Para meter | |
| 529 | N/A. HL7 i s not used . | |
| 530 | 6.2.2.3.31 HL7 Logica l Link | |
| 531 | N/A. HL7 i s not used . | |
| 532 | 6.2.2.3.32 COTS Inter face | |
| 533 | N/A. No CO TS product s are invo lved. | |
| 534 | Network De tailed Des ign | |
| 535 | There is n o change i n network functional ity. MHA3 is a Clien t-Server a pplication delivered on the VA network. Each VA re gion / fac ility is r esponsible for their network s chema. Bel ow is a si mple desig n of a net work and d oes not sp ecifically point out any VA ne twork. | |
| 536 | ||
| 537 | ||
| 538 | Security a nd Privacy | |
| 539 | 6.4.1Secur ity | |
| 540 | MHA3 allow s a staff member to select one or more I nstruments to admini ster, put the comput er into a kiosk mode , and turn the compu ter over t o the vete ran to res pond to th e instrume nt. In thi s mode, th e only thi ng that ca n be done by the vet eran is re spond to t he instrum ent. All o ther funct ions of th e computer are inacc essible ap art from t he entry o f the staf f member’s credentia ls to unlo ck the kio sk mode. W hen the ve teran has completed the self-a dministrat ion of the instrumen t, access to the sys tem will b e prevente d until a staff memb er supplie s the appr opriate cr edentials. | |
| 541 | No changes will be n eeded to t he securit y and priv acy requir ements alr eady appro ved for Vi stA and th e GUIs. | |
| 542 | MHA3 funct ionality w ill adhere to all VA and VHA s ecurity re quirements . | |
| 543 | 6.4.2Priva cy | |
| 544 | MHA3 softw are applic ation did not releas e any new security k eys. The Y SP securit y key is s till requi red to con trol acces s to the r esults of “non-exemp t” instrum ents. Whil e anyone m ay adminis ter a “non -exempt” i nstrument, only psyc hologists with the Y SP securit y key may view the r esults. Ho lders of t he YSP sec urity key are determ ined by th e Chief of Psycholog y or a sen ior psycho logist at a facility that does not have a Chief of Psycholog y. The Chi ef of Psyc hology or senior psy chologist also deter mines whic h tests ar e “exempt” (i.e., th e results can be see n by anyon e), and wh ich are “n on-exempt” (i.e., re quire the YSP key to see the r esults). | |
| 545 | Service Or iented Arc hitecture / ESS Deta iled Desig n | |
| 546 | N/A. This patch does not affec t the cons umption or provision of any se rvices. | |
| 547 | Service De scription for <Consu med Servic e Name> | |
| 548 | N/A. | |
| 549 | Service De sign for < Provided S ervice Nam e> | |
| 550 | 6.5.2.1Int roduction | |
| 551 | 6.5.2.1.1P urpose and Scope of Service | |
| 552 | N/A. | |
| 553 | 6.5.2.1.2L inks to Ot her Docume nts | |
| 554 | N/A. | |
| 555 | 6.5.2.2Ser vice Detai ls | |
| 556 | 6.5.2.2.1S ervice Ide ntificatio n | |
| 557 | N/A. | |
| 558 | 6.5.2.2.2S ervice Ver sions | |
| 559 | N/A. | |
| 560 | 6.5.2.2.3S ummary of Design and Platform Details | |
| 561 | 6.5.2.2.3. 1SOA Patte rn(s) Impl emented | |
| 562 | N/A. | |
| 563 | 6.5.2.2.3. 2COTS Plat form vendo r names an d versions for hosti ng platfor m | |
| 564 | N/A. | |
| 565 | Dependenci es | |
| 566 | N/A. | |
| 567 | Service De sign Detai ls | |
| 568 | N/A. | |
| 569 | 6.5.2.4.1I nterface T echnical S pecs | |
| 570 | N/A. | |
| 571 | 6.5.2.4.1. 1Service I nvocation Type | |
| 572 | N/A. | |
| 573 | 6.5.2.4.1. 2Service I nterface T ype | |
| 574 | N/A. | |
| 575 | 6.5.2.4.1. 3Service N ame | |
| 576 | N/A. | |
| 577 | 6.5.2.4.1. 4Interface | |
| 578 | N/A. | |
| 579 | 6.5.2.4.1. 5End Point s | |
| 580 | N/A. | |
| 581 | 6.5.2.4.1. 6Operation s or Metho ds | |
| 582 | N/A. | |
| 583 | 6.5.2.4.1. 7Message S chemas | |
| 584 | N/A. | |
| 585 | 6.5.2.4.2I nformation Model | |
| 586 | N/A. | |
| 587 | 6.5.2.4.2. 1Class Dia gram and D escription of Entiti es Involve d | |
| 588 | N/A. | |
| 589 | 6.5.2.4.2. 2Mappings from ELDM to Standar ds Based S chemas | |
| 590 | N/A. | |
| 591 | 6.5.2.4.3B ehavior Mo del (AKA U se Case Re alization) | |
| 592 | N/A. | |
| 593 | 6.5.2.4.3. 1Use Cases (Use Case Model) | |
| 594 | N/A. | |
| 595 | 6.5.2.4.3. 2Interacti on Diagram s | |
| 596 | N/A. | |
| 597 | 6.5.2.5Gap Analysis | |
| 598 | N/A. | |
| 599 | 6.5.2.5.1V ariances f rom Enterp rise Targe t Architec ture | |
| 600 | N/A. | |
| 601 | 6.5.2.5.2V ariances f rom SLDs | |
| 602 | N/A. | |
| 603 | 6.5.2.5.3V ariances f rom Standa rds and Po licies | |
| 604 | N/A. | |
| 605 | 6.5.2.5.4J ustificati on for Exc eptions an d Mitigati on | |
| 606 | N/A. | |
| 607 | External S ystem Inte rface Desi gn | |
| 608 | N/A. There are no ex ternal int erfaces as part of t his patch. | |
| 609 | Interface Architectu re | |
| 610 | N/A. | |
| 611 | Interface Detailed D esign | |
| 612 | N/A. | |
| 613 | Human-Mach ine Interf ace | |
| 614 | N/A. The u ser interf ace is not changed b y this pat ch. | |
| 615 | Interface Design Rul es | |
| 616 | N/A. | |
| 617 | Inputs | |
| 618 | N/A. | |
| 619 | Outputs | |
| 620 | N/A. | |
| 621 | Navigation Hierarchy | |
| 622 | N/A. | |
| 623 | Attachment A – Appro val Signat ures | |
| 624 | This secti on is used to docume nt the app roval of t he System Design Doc ument. The review sh ould be co nducted fa ce to face where sig natures ca n be obtai ned ‘live’ during th e review. If unable to conduct a face-to -face meet ing then i t should b e held via LiveMeeti ng and con currence c aptured du ring the m eeting. Th e Scribe s hould add /es/name b y each pos ition cite d. Example provided below. | |
| 625 | The Busine ss Sponsor and Proje ct Manager are requi red to sig n. | |
| 626 | ||
| 627 | __________ __________ __________ __________ __________ __________ __________ _______ | |
| 628 | Signed:Dat e: | |
| 629 | Kathleen L ysell, Psy .D. Nation al Mental Health Dir ector for Informatic s | |
| 630 | ||
| 631 | __________ __________ __________ __________ __________ __________ __________ ________ | |
| 632 | Signed:Dat e: | |
| 633 | Shawn Suit ers, OIT P D, PM, Tm 3, Project Manager | |
| 634 | ||
| 635 | __________ __________ __________ __________ __________ __________ __________ _______ | |
| 636 | Signed:Dat e: | |
| 637 | James Gold smith, HP PM, PCL-5 MHAS | |
| 638 | ||
| 639 | Additional Informati on | |
| 640 | Identifica tion of Te chnology a nd Standar ds | |
| 641 | The system which app lies to th e SDD is M ental Heal th Assista nt v3. Sof tware used is Massac husetts Ge neral Hosp ital Utili ty Multi-P rogramming System (M UMPS) whic h is TRM c ompliant. American N ational St andards In stitute [A NSI], Inte rnational Organizati on for Sta ndardizati on [ISO], Institute of Electri cal and El ectronics Engineers [IEEE] wil l be compl ied with d uring the software c oding of P CL-5 MHAS. | |
| 642 | Constraini ng Policie s, Directi ves and Pr ocedures | |
| 643 | None ident ified at t his time. | |
| 644 | Requiremen ts Traceab ility Matr ix | |
| 645 | The RTM is located a t: http:// DNS /warboard/ anotebk.as p?proj=183 8 | |
| 646 | Packaging and Instal lation | |
| 647 | This patch is distri buted via a Packman message an d may be i nstalled w ith users on the sys tem althou gh it is r ecommended that it b e installe d during n on-peak ho urs to min imize pote ntial disr uption to users. Thi s patch sh ould take less than one hour t o install. | |
| 648 | This patch will upda te the MHA 3 Database : | |
| 649 | Choose the PackMan m essage con taining th is patch. | |
| 650 | Choose the INSTALL/C HECK MESSA GE PackMan option. | |
| 651 | From the K ernel Inst allation a nd Distrib ution Syst em Menu, s elect the Installati on Menu. F rom this m enu, you m ay elect t o use the following options. W hen prompt ed for the INSTALL N AME enter YS*5.01*12 3. | |
| 652 | Backup a T ransport G lobal - Th is option will creat e a backup message o f any rout ines expor ted with t his patch. It will n ot backup any other changes su ch as DDs or templat es. | |
| 653 | Compare Tr ansport Gl obal to Cu rrent Syst em - This option wil l allow yo u to view all change s that wil l be made when this patch is i nstalled. It compare s all comp onents of this patch (routines , DDs, tem plates, et c.). | |
| 654 | Verify Che cksums in Transport Global - T his option will allo w you to e nsure the integrity of the rou tines that are in th e transpor t global. | |
| 655 | From the I nstallatio n Menu, se lect the I nstall Pac kage(s) op tion and c hoose the patch to i nstall. | |
| 656 | When promp ted ‘Want KIDS to Re build Menu Trees Upo n Completi on of Inst all? NO//’ enter NO. | |
| 657 | When promp ted ‘Want KIDS to IN HIBIT LOGO Ns during the instal l? NO//’ e nter NO. | |
| 658 | When promp ted 'Want to DISABLE Scheduled Options, Menu Optio ns, and Pr otocols? N O//’ enter NO. | |
| 659 | If prompte d ‘Delay I nstall (Mi nutes): (0 – 60): 0/ /’ respond 0. | |
| 660 | Design Met rics | |
| 661 | Compliance with Vete rans Affai rs Standar ds and Con ventions ( SAC) and o ther VA de sign conve ntions wil l be maint ained. | |
| 662 | Required T echnical D ocuments | |
| 663 | The follow ing docume nts must b e submitte d for revi ew to supp ort proper approval: | |
| 664 | Conformanc e Validati on Stateme nt (CVS) - Section 5 08- 508 is not appli cable to t his patch. | |
| 665 | YS*5.01*12 3 Patch De scription | |
| 666 | YS*5.01*12 3 Version Descriptio n Document (VDD) | |
| 667 | Acronym Li st and Glo ssary | |
| 668 | ||
| 669 | Term | |
| 670 | Meaning | |
| 671 | CPRS | |
| 672 | Computeriz ed Patient Record Sy stem | |
| 673 | DSM-5 | |
| 674 | Diagnostic and Stati stical Man ual of Men tal Disord ers – 5th Edition | |
| 675 | MHA | |
| 676 | Mental Hea lth Assist ant | |
| 677 | MUMPS | |
| 678 | Massachuse tts Genera l Hospital Utility M ulti-Progr amming Sys tem | |
| 679 | PCL-5 | |
| 680 | Posttrauma tic Stress Disorder Checklist- 5 | |
| 681 | PSPO | |
| 682 | Patient Sa fety Progr am Office | |
| 683 | PTSD | |
| 684 | Posttrauma tic Stress Disorder | |
| 685 | RPC Broker | |
| 686 | Remote Pro cedure Cal l Broker | |
| 687 | RSD | |
| 688 | Requiremen ts Specifi cation Doc ument | |
| 689 | RTM | |
| 690 | Requiremen ts Traceab ility Matr ix | |
| 691 | SAC | |
| 692 | Standards And Conven tions | |
| 693 | SDD | |
| 694 | System des ign Docume nt | |
| 695 | SSO | |
| 696 | Single Sig n-On | |
| 697 | SQA | |
| 698 | Software Q uality Ass urance | |
| 699 | TRM | |
| 700 | Technical Reference Model | |
| 701 | VA | |
| 702 | Veterans A dministrat ion | |
| 703 | VDD | |
| 704 | Version De scription Document | |
| 705 | VistA | |
| 706 | Veterans H ealth Info rmation Sy stems and Technology Architect ure |
Araxis Merge (but not the data content of this report) is Copyright © 1993-2016 Araxis Ltd (www.araxis.com). All rights reserved.