Produced by Araxis Merge on 4/6/2018 1:16:17 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 | SPP_YS_501_134_135.zip | SPP_SDD_YS_501_135.docx | Thu Apr 5 21:13:13 2018 UTC |
2 | SPP_YS_501_134_135.zip | SPP_SDD_YS_501_135.docx | Thu Apr 5 22:40:08 2018 UTC |
Description | Between Files 1 and 2 |
|
---|---|---|
Text Blocks | Lines | |
Unchanged | 5 | 1192 |
Changed | 4 | 8 |
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 | Department of Vetera ns Affairs | |
2 | Mental Hea lth – Suic ide Preven tion | |
3 | Suicide Pr evention P ackage | |
4 | ||
5 | ||
6 | ||
7 | March 20, 2018 | |
8 | Version 1. 0 | |
9 | ||
10 | System Des ign Docume nt | |
11 | Submitted as CLIN 00 03AC | |
12 | Contract V A118-16-D- 1007, Task Order VA1 1817F10070 006 | |
13 | ||
14 | Submitted by: | |
15 | Booz Allen Hamilton Inc. | |
16 | 141 W. Fro nt Street, Suite 200 | |
17 | Red Bank, NJ 07701 | |
18 | Phone: 732 -936-3500 | |
19 | Fax: 732-9 36-3535 | |
20 | ||
21 | ||
22 | ||
23 | ||
24 | Revision H istory | |
25 | Date | |
26 | Version | |
27 | Descriptio n | |
28 | Author | |
29 | 3/20/2018 | |
30 | 1.0 | |
31 | Initial Dr aft – Patc h YS*5.01* 135 | |
32 | Booz Allen | |
33 | ||
34 | Artifact R ationale | |
35 | 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 . | |
36 | ||
37 | ||
38 | Table of C ontents | |
39 | 1.Introduc tion1 | |
40 | 1.1.Scope1 | |
41 | 1.2.User P rofiles1 | |
42 | 2.Backgrou nd2 | |
43 | 2.1.Overvi ew of the System2 | |
44 | 2.2.Overvi ew of the Business P rocess2 | |
45 | 2.3.Overvi ew of the Significan t Requirem ents2 | |
46 | 3.Conceptu al Design3 | |
47 | 3.1.Concep tual Appli cation Des ign3 | |
48 | 3.1.1.Appl ication Co ntext3 | |
49 | 3.1.2.High -Level App lication D esign3 | |
50 | 3.1.3.Appl ication Lo cations4 | |
51 | 3.2.Concep tual Data Design4 | |
52 | 3.2.1.Proj ect Concep tual Data Model4 | |
53 | 3.2.2.Data base Infor mation5 | |
54 | 3.2.3.User Interface Data Mapp ing5 | |
55 | 3.3.Concep tual Infra structure Design5 | |
56 | 3.3.1.Syst em Critica lity and H igh Availa bility5 | |
57 | 3.3.2.Spec ial Techno logy5 | |
58 | 3.3.3.Tech nology Loc ations5 | |
59 | 3.3.4.Conc eptual Inf rastructur e Diagram6 | |
60 | 4.System A rchitectur e7 | |
61 | 4.1.Hardwa re Archite cture7 | |
62 | 4.2.Softwa re Archite cture7 | |
63 | 4.3.Networ k Architec ture7 | |
64 | 4.4.Servic e Oriented Architect ure / ESS7 | |
65 | 4.5.Enterp rise Archi tecture7 | |
66 | 5.Data Des ign9 | |
67 | 5.1.DBMS F iles9 | |
68 | 5.2.Non-DB MS Files9 | |
69 | 5.3.Data V iew9 | |
70 | 6.Detailed Design10 | |
71 | 6.1.Hardwa re Detaile d Design10 | |
72 | 6.2.Softwa re Detaile d Design10 | |
73 | 6.2.1.Conc eptual Des ign10 | |
74 | 6.2.1.1. P roduct Per spective10 | |
75 | 6.2.1.1.1. User Inter faces10 | |
76 | 6.2.1.1.2. Hardware I nterfaces1 0 | |
77 | 6.2.1.1.3. Software I nterfaces1 0 | |
78 | 6.2.1.1.4. Communicat ions Inter faces10 | |
79 | 6.2.1.1.5. Memory Con straints10 | |
80 | 6.2.1.1.6. Special Op erations10 | |
81 | 6.2.1.2.Pr oduct Feat ures10 | |
82 | 6.2.1.3.De pendencies and Const raints11 | |
83 | 6.2.1.4.Us er Charact eristics11 | |
84 | 6.2.2.Spec ific Requi rements11 | |
85 | 6.2.2.1Dat abase Repo sitory11 | |
86 | 6.2.2.2Sys tem Featur es11 | |
87 | 6.2.2.3Des ign Elemen t Tables11 | |
88 | 6.2.2.3.1R outines (E ntry Point s)11 | |
89 | 6.2.2.3.2T emplates11 | |
90 | 6.2.2.3.3B ulletins11 | |
91 | 6.2.2.3.4D ata Entrie s Affected by the De sign11 | |
92 | 6.2.2.3.5U nique Reco rd(s)11 | |
93 | 6.2.2.3.6F ile or Glo bal Size C hanges11 | |
94 | 6.2.2.3.7M ail Groups 11 | |
95 | 6.2.2.3.8S ecurity Ke ys12 | |
96 | 6.2.2.3.9O ptions12 | |
97 | 6.2.2.3.10 Protocols1 2 | |
98 | 6.2.2.3.11 Remote Pro cedure Cal l (RPC)12 | |
99 | 6.2.2.3.12 Constants Defined in Interface 12 | |
100 | 6.2.2.3.13 Variables Defined in Interface 12 | |
101 | 6.2.2.3.14 Types Defi ned in Int erface12 | |
102 | 6.2.2.3.15 GUI - Over view12 | |
103 | 6.2.2.3.16 GUI Classe s12 | |
104 | 6.2.2.3.17 Current Fo rm12 | |
105 | 6.2.2.3.18 Modified F orm12 | |
106 | 6.2.2.3.19 Components on Form12 | |
107 | 6.2.2.3.20 Methods12 | |
108 | 6.2.2.3.21 Special Re ferences12 | |
109 | 6.2.2.3.22 Class Even ts12 | |
110 | 6.2.2.3.23 Class Meth ods13 | |
111 | 6.2.2.3.24 Class Prop erties13 | |
112 | 6.2.2.3.25 Uses Claus e13 | |
113 | 6.2.2.3.26 Forms13 | |
114 | 6.2.2.3.27 Functions1 3 | |
115 | 6.2.2.3.28 Dialog13 | |
116 | 6.2.2.3.29 Help Frame 13 | |
117 | 6.2.2.3.30 HL7 Applic ation Para meter13 | |
118 | 6.2.2.3.31 HL7 Logica l Link13 | |
119 | 6.2.2.3.32 COTS Inter face13 | |
120 | 6.3.Networ k Detailed Design13 | |
121 | 6.4.Securi ty and Pri vacy14 | |
122 | 6.4.1Secur ity14 | |
123 | 6.4.2Priva cy14 | |
124 | 6.5.Servic e Oriented Architect ure / ESS Detailed D esign15 | |
125 | 6.5.1.Serv ice Descri ption for <Consumed Service Na me>15 | |
126 | 6.5.2.Serv ice Design for <Prov ided Servi ce Name>15 | |
127 | 6.5.2.1Int roduction1 5 | |
128 | 6.5.2.1.1P urpose and Scope of Service15 | |
129 | 6.5.2.1.2L inks to Ot her Docume nts15 | |
130 | 6.5.2.2Ser vice Detai ls15 | |
131 | 6.5.2.2.1S ervice Ide ntificatio n15 | |
132 | 6.5.2.2.2S ervice Ver sions15 | |
133 | 6.5.2.2.3S ummary of Design and Platform Details15 | |
134 | 6.5.2.2.3. 1SOA Patte rn(s) Impl emented15 | |
135 | 6.5.2.2.3. 2COTS Plat form vendo r names an d versions for hosti ng platfor m15 | |
136 | 6.5.2.3Dep endencies1 5 | |
137 | 6.5.2.4Ser vice Desig n Details1 5 | |
138 | 6.5.2.4.1I nterface T echnical S pecs15 | |
139 | 6.5.2.4.1. 1Service I nvocation Type15 | |
140 | 6.5.2.4.1. 2Service I nterface T ype16 | |
141 | 6.5.2.4.1. 3Service N ame16 | |
142 | 6.5.2.4.1. 4Interface 16 | |
143 | 6.5.2.4.1. 5End Point s16 | |
144 | 6.5.2.4.1. 6Operation s or Metho ds16 | |
145 | 6.5.2.4.1. 7Message S chemas16 | |
146 | 6.5.2.4.2I nformation Model16 | |
147 | 6.5.2.4.2. 1Class Dia gram and D escription of Entiti es Involve d16 | |
148 | 6.5.2.4.2. 2Mappings from ELDM to Standar ds Based S chemas16 | |
149 | 6.5.2.4.3B ehavior Mo del (AKA U se Case Re alization) 16 | |
150 | 6.5.2.4.3. 1Use Cases (Use Case Model)16 | |
151 | 6.5.2.4.3. 2Interacti on Diagram s16 | |
152 | 6.5.2.5Gap Analysis1 6 | |
153 | 6.5.2.5.1V ariances f rom Enterp rise Targe t Architec ture16 | |
154 | 6.5.2.5.2V ariances f rom SLDs16 | |
155 | 6.5.2.5.3V ariances f rom Standa rds and Po licies16 | |
156 | 6.5.2.5.4J ustificati on for Exc eptions an d Mitigati on16 | |
157 | 7.External System In terface De sign17 | |
158 | 7.1.Interf ace Archit ecture17 | |
159 | 7.2.Interf ace Detail ed Design1 7 | |
160 | 8.Human-Ma chine Inte rface18 | |
161 | 8.1.Interf ace Design Rules18 | |
162 | 8.2.Inputs 18 | |
163 | 8.3.Output s18 | |
164 | 8.4.Naviga tion Hiera rchy18 | |
165 | 9.Attachme nt A – App roval Sign atures19 | |
166 | A.Addition al Informa tion20 | |
167 | A.1.Identi fication o f Technolo gy and Sta ndards20 | |
168 | A.2.Constr aining Pol icies, Dir ectives an d Procedur es20 | |
169 | A.3.Requir ements Tra ceability Matrix20 | |
170 | A.4.Packag ing and In stallation 20 | |
171 | A.5.Design Metrics21 | |
172 | A.6.Requir ed Technic al Documen ts21 | |
173 | A.7.Acrony m List and Glossary2 1 | |
174 | ||
175 | Introducti on | |
176 | This docum ent descri bes some o f the chan ges implem ented to t he MHA sys tem by the Suicide P revention Project. It current ly consist s of three different efforts: new instru ments, a d ashboard, and migrat ing to the intranet. | |
177 | ||
178 | Scope | |
179 | This docum ent descri bes change s made by patch YS*5 .01*135. | |
180 | ||
181 | The projec t scope ca n be found in the Su icide_Prev ention_Req uirements. xlsx in ht tps:// URL /ccm/web/p rojects/MH LTH%20(CM) #action=co m.ibm.team .scm.brows eElement&w orkspaceIt emId=_qnwD oOTkEees-s Am-9T4WA&c omponentIt emId=_qEOE gvr4EeePfN SGcJfSjQ&i temType=co m.ibm.team .scm.Folde r&itemId=_ TPF09_r6Ee e0AMheAjwA gw | |
182 | ||
183 | User Profi les | |
184 | Users of t his applic ation will include M ental Heal th profess ionals and clinician s. | |
185 | The techni cal backgr ound and d egree of s ophisticat ion of the individua l users wi ll vary. | |
186 | ||
187 | Background | |
188 | Overview o f the Syst em | |
189 | The MHA pr ovides a m echanism t o administ er and sco re standar dized ques tionnaires and psych ological t ests. 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. MHA runs i n conjunct ion with C PRS (Compu terized Pa tient Reco rd System) . A user of CPRS ca n branch t o MHA as n eeded via the CPRS T ools menu. MHA 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. Health Sum mary also allows the display o f MHA inst rument res ults. | |
190 | ||
191 | MHA Dashbo ard suppor ts this sy stem by gi ving views of cohort s of veter ans and th eir status . The dat a displaye d varies b y the sele cted workf low of the individua l user. | |
192 | ||
193 | Overview o f the Busi ness Proce ss | |
194 | MHA is alr eady runni ng as part of Vetera ns Health Informatio n Systems and Techno logy Archi tecture (V istA). SP P will add more inst ruments to MHA. It will also add a dash board appl ication to review th e status o f several veterans a t a glance . | |
195 | For additi onal detai ls referen ce section 3.1.2, 3. 2.1 and Se ction 6. | |
196 | ||
197 | Overview o f the Sign ificant Re quirements | |
198 | The signif icant requ irements f or the das hboard can be found in the Sui cide_Preve ntion_Requ irements.x slx docume nt; which combines t he Busines s Requirem ents Docum ent and a traceabili ty matrix, and is lo cated at: | |
199 | https:// URL v/ccm/web/ projects/M HLTH%20(CM )#action=c om.ibm.tea m.scm.brow seElement& workspaceI temId=_qnw DoOTkEees- sAm-9T4WA& componentI temId=_qEO Egvr4EeePf NSGcJfSjQ& itemType=c om.ibm.tea m.scm.Fold er&itemId= _TPF09_r6E ee0AMheAjw Agw | |
200 | Patch YS*5 .01*135 ad ds a routi ne to assi st with th e developm ent of the upcoming dashboard applicatio n. | |
201 | Conceptual Design | |
202 | This secti on will de scribe MHA as curren tly design ed. The de sign is no t affected by the re lease of a n updated file entry . | |
203 | Conceptual Applicati on Design | |
204 | MHA is a W indows cli ent applic ation writ ten in Del phi. It co mmunicates with Vist A via the Remote Pro cedure Cal l Broker ( RPC Broker ). The exi sting arch itecture o f the syst em will no t change f or this pa tch. This patch adds a test RP C for the upcoming d ashboard a pplication . | |
205 | Applicatio n Context | |
206 | 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. | |
207 | Figure 1: Mental Hea lth Assist ant | |
208 | ||
209 | ||
210 | Table 1 (G rouping): Applicatio n Context Descriptio n | |
211 | Object | |
212 | ID | |
213 | Name | |
214 | Descriptio n | |
215 | Interface Name | |
216 | Interface System | |
217 | CPRS Clien t | |
218 | CPRS Clien t | |
219 | CPRS Windo ws executa ble client applicati on. | |
220 | RPC Broker | |
221 | VistA | |
222 | MHA Client | |
223 | MHA Client | |
224 | Mental Hea lth Assist ant execut able clien t applicat ion – laun ched from CPRS. | |
225 | RPC Broker | |
226 | VistA | |
227 | High-Level Applicati on Design | |
228 | 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 cur rently exi sts, is no t being ch anged. The as-is des ign is sho wn in Figu re 2. | |
229 | Figure 2: Applicatio n Design | |
230 | ||
231 | Applicatio n Location s | |
232 | The applic ation runs as a Vist A package in locatio ns where V istA is in stalled. | |
233 | Table 2: A pplication Locations | |
234 | Applicatio n Componen t | |
235 | Descriptio n | |
236 | Location a t Which Co mponent is Run | |
237 | Type | |
238 | VistA | |
239 | VistA pack age – a su bset of th e Mental H ealth pack age. | |
240 | All VistA instances. | |
241 | N/A | |
242 | Table 3: A pplication Users | |
243 | Applicatio n Componen t | |
244 | Location | |
245 | User | |
246 | VistA | |
247 | All VAMCs and Clinic with Vist A access | |
248 | Mental Hea lth Clinic ian | |
249 | Conceptual Data Desi gn | |
250 | Project Co nceptual D ata Model | |
251 | 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. | |
252 | Figure 2: Project Co nceptual D ata Model | |
253 | ||
254 | ||
255 | Database I nformation | |
256 | N/A. No ch anges are being made . | |
257 | User Inter face Data Mapping | |
258 | 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 . | |
259 | ||
260 | Conceptual Infrastru cture Desi gn | |
261 | 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. | |
262 | System Cri ticality a nd High Av ailability | |
263 | 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. | |
264 | Special Te chnology | |
265 | N/A. No sp ecial tech nology is involved i n the patc h. | |
266 | Technology Locations | |
267 | N/A. This is a simpl e VistA pa tch – ther e are no s pecial tec hnology co mponents. | |
268 | Conceptual Infrastru cture Diag ram | |
269 | N/A. There are no ex ternal int erfaces or special e nvironment s involved . | |
270 | System Arc hitecture | |
271 | Hardware A rchitectur e | |
272 | 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. | |
273 | Software A rchitectur e | |
274 | There is n o change i n software architect ure. | |
275 | Network Ar chitecture | |
276 | No communi cation wit hin the sy stem, such as local area netwo rks (LANs) and buses are being added, re moved, or modified. MHA uses l ocal Netwo rk configu rations to communica te between the MHA a pplication and VistA . For info rmation on Network A rchitectur e please r eference t he VDL. | |
277 | Service Or iented Arc hitecture / ESS | |
278 | This patch updates t he file en tries and target sou rce mappin g that rep resent the MHA. Ther e are no n ew service s provided or consum ed. | |
279 | Enterprise Architect ure | |
280 | 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. | |
281 | TRM Link h ttps://www .va.gov/tr m/ | |
282 | Table 5: T RM Tools U sed | |
283 | Applicatio n | |
284 | TRM Compli ant | |
285 | Environmen t | |
286 | License | |
287 | MUMPS | |
288 | (Massachus etts Gener al Hospita l Utility Multi-Prog ramming Sy stem) | |
289 | Yes | |
290 | All | |
291 | ISO/IEC 11 756:1999 | |
292 | Caché | |
293 | Yes | |
294 | All | |
295 | Commercial / v2014 | |
296 | VA M Progr amming Sta ndard | |
297 | Yes | |
298 | All | |
299 | VA Standar d Document . http:// URL /VAStandar dPage.asp? tid=7404 | |
300 | dWinlock | |
301 | Yes | |
302 | All | |
303 | Commercial / v3.3 | |
304 | TMS VCL Co mponent Pa ck | |
305 | Yes | |
306 | All | |
307 | Commercial Site Lice nse v8.8.5 .1 | |
308 | RAD Studio version D elphi XE8 | |
309 | Yes | |
310 | All | |
311 | Commercial / version Delphi XE 8 | |
312 | ||
313 | Data Desig n | |
314 | This patch does not change the current d ata design . | |
315 | ||
316 | DBMS Files | |
317 | N/A. This patch does not add n ew files o r columns. . | |
318 | ||
319 | Non-DBMS F iles | |
320 | N/A. There are no fi les outsid e of the V istA FileM an databas e. | |
321 | ||
322 | Data View | |
323 | 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. | |
324 | Detailed D esign | |
325 | Hardware D etailed De sign | |
326 | MHA is a C lient-Serv er applica tion deliv ered on a networked, Intel-pro cessor-bas ed compute r. The co mputer has the VA-st andard hum an interfa ce devices : a keyboa rd and a m ouse. Beca use MHA is designed to be able to be use d by the v isually im paired, th e system a lso includ es a set o f speakers or headph ones. | |
327 | Software D etailed De sign | |
328 | Conceptual Design | |
329 | There is n o change i n the GUI design of Mental Hea lth Assist ant for th is patch. | |
330 | 6.2.1.1. P roduct Per spective | |
331 | 6.2.1.1.1. User Inter faces | |
332 | The MHA GU I will com ply with t he general requireme nts for al l VistA® a pplication s as speci fied in th e VistA Gr aphical Us er Interfa ce Standar ds and Con ventions d ocument, S ection 4, Look and F eel. | |
333 | 6.2.1.1.2. Hardware I nterfaces | |
334 | N/A. There are no ha rdware com ponents fo r this pat ch. | |
335 | 6.2.1.1.3. Software I nterfaces | |
336 | MHA requir es the fol lowing sof tware on t he VistA s ervers: | |
337 | FileMan v2 2.2 | |
338 | MailMan v8 .0 | |
339 | Kernel v8. 0 | |
340 | MHA can co nnect with the follo wing softw are: | |
341 | CPRS (curr ent Versio n) | |
342 | 6.2.1.1.4. Communicat ions Inter faces | |
343 | There are no special communica tion inter faces requ ired for t his functi onality. | |
344 | 6.2.1.1.5. Memory Con straints | |
345 | There are no memory constraint s. | |
346 | 6.2.1.1.6. Special Op erations | |
347 | There are no special operation s required to implem ent Instru ments. | |
348 | 6.2.1.2.Pr oduct Feat ures | |
349 | N/A There are no pro duct featu re changes for this patch. | |
350 | 6.2.1.3.De pendencies and Const raints | |
351 | There are no additio nal depend encies or constraint s. | |
352 | 6.2.1.4.Us er Charact eristics | |
353 | MHA is use d by menta l health c linicians. Patients may option ally be as ked to use the quest ionnaire p ortion of MHA. | |
354 | Specific Requiremen ts | |
355 | 6.2.2.1Dat abase Repo sitory | |
356 | N/A. There is no cha nge in the database repository . | |
357 | 6.2.2.2Sys tem Featur es | |
358 | N/A This patch does not chang e any syst em feature s. | |
359 | Design Ele ment Table s | |
360 | 6.2.2.3.1R outines (E ntry Point s) | |
361 | This patch does not change exi sting rout ines but c ontains a new routin e and entr y points f or the MHA Dashboard . | |
362 | Figure 3 M HA related RPCs and Routines | |
363 | ||
364 | ||
365 | ||
366 | 6.2.2.3.2T emplates | |
367 | N/A. No te mplates ar e involved . | |
368 | 6.2.2.3.3B ulletins | |
369 | N/A. No bu lletins ar e involved . | |
370 | 6.2.2.3.4D ata Entrie s Affected by the De sign | |
371 | N/A. No da ta entries are affec ted. | |
372 | 6.2.2.3.5U nique Reco rd(s) | |
373 | N/A. No un ique recor ds are inv olved. | |
374 | 6.2.2.3.6F ile or Glo bal Size C hanges | |
375 | 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 sub fil es size at startup w ill approx imately ma tch the si ze of curr ent data f ile they’r e replacin g. | |
376 | 6.2.2.3.7M ail Groups | |
377 | N/A. No ma il groups are involv ed. | |
378 | 6.2.2.3.8S ecurity Ke ys | |
379 | These secu rity keys have been in place a nd will no t change w ith this d evelopment . | |
380 | Name Descript ion | |
381 | ||
382 | 6.2.2.3.9O ptions | |
383 | N/A. No op tions are involved. | |
384 | 6.2.2.3.10 Protocols | |
385 | N/A. No pr otocols ar e involved . | |
386 | 6.2.2.3.11 Remote Pro cedure Cal l (RPC) | |
387 | There are no changes for any e xternal us ers of the RPCs. For a complet e list of RPCs pleas e see the section on Routines. | |
388 | 6.2.2.3.12 Constants Defined in Interface | |
389 | N/A. No in terfaces a re involve d. | |
390 | 6.2.2.3.13 Variables Defined in Interface | |
391 | N/A. No in terfaces a re involve d. | |
392 | 6.2.2.3.14 Types Defi ned in Int erface | |
393 | N/A. No in terfaces a re involve d. | |
394 | 6.2.2.3.15 GUI - Over view | |
395 | N/A. The G UI is not modified. | |
396 | 6.2.2.3.16 GUI Classe s | |
397 | N/A. The G UI is not modified. | |
398 | 6.2.2.3.17 Current Fo rm | |
399 | N/A. No fo rms are mo dified. | |
400 | 6.2.2.3.18 Modified F orm | |
401 | N/A. No fo rms are mo dified. | |
402 | 6.2.2.3.19 Components on Form | |
403 | N/A. No fo rms are mo dified. | |
404 | 6.2.2.3.20 Methods | |
405 | N/A. No me thods are involved. | |
406 | 6.2.2.3.21 Special Re ferences | |
407 | N/A. There are no sp ecial refe rences. | |
408 | 6.2.2.3.22 Class Even ts | |
409 | N/A. There are no cl ass events . | |
410 | 6.2.2.3.23 Class Meth ods | |
411 | N/A. There are no cl ass method s. | |
412 | 6.2.2.3.24 Class Prop erties | |
413 | N/A. There are no cl ass proper ties. | |
414 | 6.2.2.3.25 Uses Claus e | |
415 | N/A. No us es clause is involve d. | |
416 | 6.2.2.3.26 Forms | |
417 | N/A. No fo rms are mo dified. | |
418 | 6.2.2.3.27 Functions | |
419 | N/A. No fu nctions ar e added/mo dified. | |
420 | 6.2.2.3.28 Dialog | |
421 | N/A. There are no ch anges to t he DIALOG file. | |
422 | 6.2.2.3.29 Help Frame | |
423 | N/A. There are no ch anges to H elp Frames . | |
424 | 6.2.2.3.30 HL7 Applic ation Para meter | |
425 | N/A. HL7 i s not used . | |
426 | 6.2.2.3.31 HL7 Logica l Link | |
427 | N/A. HL7 i s not used . | |
428 | 6.2.2.3.32 COTS Inter face | |
429 | N/A. No CO TS product s are invo lved. | |
430 | Network De tailed Des ign | |
431 | There is n o current change in network fu nctionalit y. MHA is a Client-S erver appl ication de livered on the VA ne twork. Eac h VA regio n / facili ty is resp onsible fo r their ow n network schema. Be low contai ns the net work inter actions fo r the proj ect. Futu re planned , but not finalized, changes c an be foun d in Figur e 5 below. | |
432 | Figure 5 | |
433 | ||
434 | Security a nd Privacy | |
435 | 6.4.1Secur ity | |
436 | MHA allows a staff m ember to s elect one or more In struments to adminis ter, put t he compute r into a k iosk mode, and turn the comput er over to the veter an to resp ond to the instrumen t. In this mode, the only thin g that can be done b y the vete ran is res pond to th e instrume nt. All ot her functi ons of the computer are inacce ssible apa rt from th e entry of the staff member’s credential s to unloc k the kios k mode. Wh en the vet eran has c ompleted t he self-ad ministrati on of the instrument , access t o the syst em will be prevented until a s taff membe r supplies the appro priate cre dentials. | |
437 | 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. | |
438 | MHA functi onality wi ll adhere to all VA and VHA se curity req uirements. | |
439 | 6.4.2Priva cy | |
440 | MHA softwa re applica tion did n ot release any new s ecurity ke ys. The YS P security key is st ill requir ed to cont rol access to the re sults of “ non-exempt ” instrume nts. While anyone ma y administ er a “non- exempt” in strument, only psych ologists w ith the YS P security key may v iew the re sults. Hol ders of th e YSP secu rity key a re determi ned by the Chief of Psychology or a seni or psychol ogist at a facility that does not have a Chief of Psychology . The Chie f of Psych ology or s enior psyc hologist a lso determ ines which tests are “exempt” (i.e., the results c an be seen by anyone ), and whi ch are “no n-exempt” (i.e., req uire the Y SP key to see the re sults). | |
441 | Service Or iented Arc hitecture / ESS Deta iled Desig n | |
442 | N/A. This patch does not affec t the cons umption or provision of any se rvices. | |
443 | Service De scription for <Consu med Servic e Name> | |
444 | N/A. | |
445 | Service De sign for < Provided S ervice Nam e> | |
446 | 6.5.2.1Int roduction | |
447 | 6.5.2.1.1P urpose and Scope of Service | |
448 | N/A. | |
449 | 6.5.2.1.2L inks to Ot her Docume nts | |
450 | N/A. | |
451 | 6.5.2.2Ser vice Detai ls | |
452 | 6.5.2.2.1S ervice Ide ntificatio n | |
453 | N/A. | |
454 | 6.5.2.2.2S ervice Ver sions | |
455 | N/A. | |
456 | 6.5.2.2.3S ummary of Design and Platform Details | |
457 | 6.5.2.2.3. 1SOA Patte rn(s) Impl emented | |
458 | N/A. | |
459 | 6.5.2.2.3. 2COTS Plat form vendo r names an d versions for hosti ng platfor m | |
460 | N/A. | |
461 | Dependenci es | |
462 | N/A. | |
463 | Service De sign Detai ls | |
464 | N/A. | |
465 | 6.5.2.4.1I nterface T echnical S pecs | |
466 | N/A. | |
467 | 6.5.2.4.1. 1Service I nvocation Type | |
468 | N/A. | |
469 | 6.5.2.4.1. 2Service I nterface T ype | |
470 | N/A. | |
471 | 6.5.2.4.1. 3Service N ame | |
472 | N/A. | |
473 | 6.5.2.4.1. 4Interface | |
474 | N/A. | |
475 | 6.5.2.4.1. 5End Point s | |
476 | N/A. | |
477 | 6.5.2.4.1. 6Operation s or Metho ds | |
478 | N/A. | |
479 | 6.5.2.4.1. 7Message S chemas | |
480 | N/A. | |
481 | 6.5.2.4.2I nformation Model | |
482 | N/A. | |
483 | 6.5.2.4.2. 1Class Dia gram and D escription of Entiti es Involve d | |
484 | N/A. | |
485 | 6.5.2.4.2. 2Mappings from ELDM to Standar ds Based S chemas | |
486 | N/A. | |
487 | 6.5.2.4.3B ehavior Mo del (AKA U se Case Re alization) | |
488 | N/A. | |
489 | 6.5.2.4.3. 1Use Cases (Use Case Model) | |
490 | N/A. | |
491 | 6.5.2.4.3. 2Interacti on Diagram s | |
492 | N/A. | |
493 | 6.5.2.5Gap Analysis | |
494 | N/A. | |
495 | 6.5.2.5.1V ariances f rom Enterp rise Targe t Architec ture | |
496 | N/A. | |
497 | 6.5.2.5.2V ariances f rom SLDs | |
498 | N/A. | |
499 | 6.5.2.5.3V ariances f rom Standa rds and Po licies | |
500 | N/A. | |
501 | 6.5.2.5.4J ustificati on for Exc eptions an d Mitigati on | |
502 | N/A. | |
503 | External S ystem Inte rface Desi gn | |
504 | N/A. There are no ex ternal int erfaces as part of t his patch. | |
505 | Interface Architectu re | |
506 | N/A. | |
507 | Interface Detailed D esign | |
508 | N/A. | |
509 | Human-Mach ine Interf ace | |
510 | N/A. The u ser interf ace is not changed b y this pat ch. | |
511 | Interface Design Rul es | |
512 | N/A. | |
513 | Inputs | |
514 | N/A. | |
515 | Outputs | |
516 | N/A. | |
517 | Navigation Hierarchy | |
518 | N/A. | |
519 | Attachment A – Appro val Signat ures | |
520 | 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. | |
521 | The Busine ss Sponsor and Proje ct Manager are requi red to sig n. | |
522 | ||
523 | __________ __________ __________ __________ __________ __________ __________ _______ | |
524 | Signed:Dat e: | |
525 | ||
526 | __________ __________ __________ __________ __________ __________ __________ ________ | |
527 | Signed:Dat e: | |
528 | ||
529 | __________ __________ __________ __________ __________ __________ __________ ______ | |
530 | Signed:Dat e: | |
531 | ||
532 | Additional Informati on | |
533 | Identifica tion of Te chnology a nd Standar ds | |
534 | 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. | |
535 | Constraini ng Policie s, Directi ves and Pr ocedures | |
536 | None ident ified at t his time. | |
537 | Requiremen ts Traceab ility Matr ix | |
538 | The RTM ca n be found within th e SPP_Prev ention_Req uirements. xlsx locat ed at: https:// URL /ccm/web/p rojects/MH LTH%20(CM) #action=co m.ibm.team .scm.brows eElement&w orkspaceIt emId=_qnwD oOTkEees-s Am-9T4WA&c omponentIt emId=_qEOE gvr4EeePfN SGcJfSjQ&i temType=co m.ibm.team .scm.Folde r&itemId=_ TPF09_r6Ee e0AMheAjwA gw | |
539 | ||
540 | Packaging and Instal lation | |
541 | 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. | |
542 | This patch will upda te the MHA Database: | |
543 | Choose the PackMan m essage con taining th is patch. | |
544 | Choose the INSTALL/C HECK MESSA GE PackMan option. | |
545 | 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*13 5. | |
546 | 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. | |
547 | 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.). | |
548 | 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. | |
549 | From the I nstallatio n Menu, se lect the I nstall Pac kage(s) op tion and c hoose the patch to i nstall. | |
550 | When promp ted ‘Want KIDS to Re build Menu Trees Upo n Completi on of Inst all? NO//’ enter NO. | |
551 | When promp ted ‘Want KIDS to IN HIBIT LOGO Ns during the instal l? NO//’ e nter NO. | |
552 | When promp ted 'Want to DISABLE Scheduled Options, Menu Optio ns, and Pr otocols? N O//’ enter NO. | |
553 | If prompte d ‘Delay I nstall (Mi nutes): (0 – 60): 0/ /’ respond 0. | |
554 | Design Met rics | |
555 | 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. | |
556 | Required T echnical D ocuments | |
557 | The follow ing docume nts must b e submitte d for revi ew to supp ort proper approval: | |
558 | Conformanc e Validati on Stateme nt (CVS) - Section 5 08- 508 is not appli cable to t his patch. | |
559 | YS*5.01*13 5 Patch De scription | |
560 | YS*5.01*13 5 Version Descriptio n Document (VDD) | |
561 | Acronym Li st and Glo ssary | |
562 | ||
563 | Term | |
564 | Meaning | |
565 | CPRS | |
566 | Computeriz ed Patient Record Sy stem | |
567 | DSM-5 | |
568 | Diagnostic and Stati stical Man ual of Men tal Disord ers – 5th Edition | |
569 | MHA | |
570 | Mental Hea lth Assist ant | |
571 | MUMPS | |
572 | Massachuse tts Genera l Hospital Utility M ulti-Progr amming Sys tem | |
573 | PSPO | |
574 | Patient Sa fety Progr am Office | |
575 | PTSD | |
576 | Posttrauma tic Stress Disorder | |
577 | RPC Broker | |
578 | Remote Pro cedure Cal l Broker | |
579 | RSD | |
580 | Requiremen ts Specifi cation Doc ument | |
581 | RTM | |
582 | Requiremen ts Traceab ility Matr ix | |
583 | SAC | |
584 | Standards And Conven tions | |
585 | SDD | |
586 | System Des ign Docume nt | |
587 | SSO | |
588 | Single Sig n-On | |
589 | SPP | |
590 | Suicide Pr evention P roject | |
591 | SQA | |
592 | Software Q uality Ass urance | |
593 | TRM | |
594 | Technical Reference Model | |
595 | VA | |
596 | Veterans A dministrat ion | |
597 | VDD | |
598 | Version De scription Document | |
599 | VistA | |
600 | 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.