Produced by Araxis Merge on 1/29/2018 2:44:56 PM Eastern Standard Time. See www.araxis.com for information about Merge. This report uses XHTML and CSS2, and is best viewed with a modern standards-compliant browser. For optimum results when printing this report, use landscape orientation and enable printing of background images and colours in your browser.
# | Location | File | Last Modified |
---|---|---|---|
1 | OneVA_Pharmacy_CAS_RxSU2_Build-1_Sprint-2_CIF_Package.zip\OneVA_Pharmacy_CAS_RxSU2_Build-1_Sprint-2_CIF_Package\OneVA_Pharmacy_CAS_RxSU2__Build-1_Sprint-2_Documentation | 2001AK_CAS_RxSU2_Version_Description_Document_20171219.docx | Tue Dec 19 05:04:03 2017 UTC |
2 | OneVA_Pharmacy_CAS_RxSU2_Build-1_Sprint-2_CIF_Package.zip\OneVA_Pharmacy_CAS_RxSU2_Build-1_Sprint-2_CIF_Package\OneVA_Pharmacy_CAS_RxSU2__Build-1_Sprint-2_Documentation | 2001AK_CAS_RxSU2_Version_Description_Document_20171219.docx | Mon Jan 29 19:18:33 2018 UTC |
Description | Between Files 1 and 2 |
|
---|---|---|
Text Blocks | Lines | |
Unchanged | 6 | 488 |
Changed | 5 | 10 |
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 | U.S. Depar tment of V eterans Af fairs | |
2 | ||
3 | OneVA Phar macy | |
4 | Clinical A ncillary S ervices (C AS) | |
5 | Pharmacy S afety Upda tes Phase II (RxSU2) | |
6 | Version De scription Document | |
7 | ||
8 | Contract N o: VA118-1 6-D-1009 | |
9 | Task Order : VA11817F 10090006 | |
10 | CLIN: 2001 AK | |
11 | ||
12 | December 2 017 | |
13 | Version 1. 0 | |
14 | Document R evision Hi story | |
15 | Date | |
16 | Document V ersion | |
17 | Descriptio n | |
18 | VDD Author / Team Ro le | |
19 | VA Group o r Contract Company | |
20 | 12/19/2017 | |
21 | 1.0 | |
22 | Initial Ve rsion | |
23 | Joseph A. McGovern | |
24 | AbleVets | |
25 | Deliverabl e (Product ) Version History | |
26 | Date | |
27 | Release / Revision | |
28 | Descriptio n | |
29 | Project Na me | |
30 | VA Departm ent | |
31 | 12/19/2017 | |
32 | 1.0 | |
33 | CAS RxSU2 Build-1 Sp rint-2 | |
34 | CAS RxSU2 | |
35 | OI&T EPMO IT | |
36 | ||
37 | VA require s the Vers ion Descri ption Docu ment (VDD) to identi fy, mainta in, enhanc e, and rec reate the product (I T asset) t hroughout its lifecy cle. The VDD reinfo rces stron g risk man agement pr actices an d helps pr otect VA f rom loss o f the prod uct (IT as set), whic h is espec ially impo rtant with a regular rotation of personn el and con tractors. | |
38 | ||
39 | The VDD is the autho ritative i nventory a nd roadmap of all Co nfiguratio n Items th at make up the deplo yable prod uct/system . Configur ation Item s include source cod e files, b uilds/pack aging, too ls, baseli nes, locat ions, and associated product f iles. Th e VDD is i tself a Co nfiguratio n Item mai ntained un der change control i n the TRM- approved c onfigurati on managem ent system , which is part of t he VA Fede rated Conf iguration Management Data Base (CMDB). | |
40 | ||
41 | Project Ma nagers and Configura tion Manag ers use th e VDD temp late as a tool for m anaging Co nfiguratio n Items as sociated w ith the de ployable p roduct. Pr oject Mana gers distr ibute the VDD templa te to IT C onfigurati on Manager s (or IT A rchitect/D evelopment Lead) at the beginn ing of the product b uild proce ss in comp liance wit h Veteran Focused In tegration Process (V IP ). The Configura tion Manag er creates /updates t he VDD eac h time the deliverab le (file s et) leaves the devel opment env ironment, such as fo r testing or deploym ent. For product pr ocedures, refer to t he Softwar e Configur ation Mana gement Pro cedures Te mplate (Pr oPath, Pro ject Plann ing: PRP 3 .7). The Project Ma nager is r esponsible for ensur ing the Co nfiguratio n Manager completes the VDD an d places t he VDD wit h the deli verables ( files) in the TRM-ap proved con figuration managemen t system. | |
42 | Table of C ontents | |
43 | General Co nfiguratio n Manageme nt (CM) In formation1 | |
44 | Configurat ion Manage ment (CM) Tools1 | |
45 | Configurat ion Manage ment of Do cuments1 | |
46 | Rational C hange and Configurat ion Manage ment (CCM) Documents 1 | |
47 | Configurat ion Manage ment Devel opment Fil es (Ex. So urce, JSP, Configura tion, and Build File s)2 | |
48 | Rational C hange and Configurat ion Manage ment (CCM) Repositor y2 | |
49 | Component( s)2 | |
50 | Baseline2 | |
51 | Build Info rmation3 | |
52 | CCM/RTC Bu ild Defini tion3 | |
53 | Build Labe l or Numbe r3 | |
54 | Build and Packaging3 | |
55 | Build Logs 3 | |
56 | Build Syst em/Process Informati on3 | |
57 | Change Tra cking3 | |
58 | Rational C hange and Configurat ion Manage ment (CCM) Repositor y4 | |
59 | Release (D eployment) Informati on4 | |
60 | Additional Supportin g Document ation4 | |
61 | ||
62 | ||
63 | General Co nfiguratio n Manageme nt (CM) In formation | |
64 | Deliverabl e (Product ) Name | |
65 | Configurat ion Manage r | |
66 | VDD Packag e Name | |
67 | Project / Delivery T eam | |
68 | Clinical A ncillary S ervices (C AS) | |
69 | Joseph A. McGovern | |
70 | Sprint-2 | |
71 | CAS RxSU2 Team | |
72 | Configurat ion Manage ment (CM) Tools | |
73 | CM Tools | |
74 | CM Tool Lo cation | |
75 | Tool | |
76 | Onsite/ | |
77 | Offsite | |
78 | CM Tool Ac cess | |
79 | Point of C ontact | |
80 | Access Inf ormation ( Forms or o ther acces s requirem ents) | |
81 | IBM Ration al Require ments Comp oser, v6.0 .1 | |
82 | VA Rationa l Jazz Ser ver | |
83 | Onsite | |
84 | Joseph A. McGovern | |
85 | RTSUB Rati onal Tools Team | |
86 | IBM Ration al Team Co ncert, v6. 0.1 | |
87 | VA Rationa l Jazz Ser ver | |
88 | Onsite | |
89 | Joseph A. McGovern | |
90 | RTSUB Rati onal Tools Team | |
91 | IBM Ration al Quality Manager, v6.0.1 | |
92 | VA Rationa l Jazz Ser ver | |
93 | Onsite | |
94 | Joseph A. McGovern | |
95 | RTSUB Rati onal Tools Team | |
96 | Configurat ion Manage ment of Do cuments | |
97 | Rational C hange and Configurat ion Manage ment (CCM) Documents | |
98 | The CCM/RT C location for the d ocuments a nd CCM/RTC explanati on for the informati on. | |
99 | CCM/RTC In formation | |
100 | Explanatio n | |
101 | CCM URL | |
102 | https:// DNS . URL /web/proje cts/PBM%20 (CM)#actio n=com.ibm. team.scm.b rowseEleme nt&workspa ceItemId=_ WrGV0M0PEe avJeNSIzjK KQ&compone ntItemId=_ W5_tcc0PEe avJeNSIzjK KQ&itemTyp e=com.ibm. team.scm.F older&item Id=_JHc0cN 9MEeeQDchW ytgP8w | |
103 | CCM Projec t Area | |
104 | PBM (CM) R xSU2_Proje ct | |
105 | CCM Team A rea | |
106 | PBM(CM) Rx SU2 Projec t | |
107 | CCM Stream | |
108 | PBM_CAS_Do cumentatio n_Stream | |
109 | Baseline I D | |
110 | CAS RxSU2_ Build_1_Sp rint_2 | |
111 | ||
112 | Components | |
113 | PBM_Docume ntation | |
114 | Directory Path | |
115 | https:// DNS . URL /web/proje cts/PBM%20 (CM)#actio n=com.ibm. team.scm.b rowseEleme nt&workspa ceItemId=_ WrGV0M0PEe avJeNSIzjK KQ&compone ntItemId=_ W5_tcc0PEe avJeNSIzjK KQ&itemTyp e=com.ibm. team.scm.F older&item Id=_JHc0cN 9MEeeQDchW ytgP8w | |
116 | Documents Included | |
117 | In the Bas eline | |
118 | CAS RxSU2 Configurat ion Manage ment Plan 1.0, Septe mber 2017 | |
119 | CAS RxSU2 Business R equirement Document (BRD) -PWS Attachmen ts B., Jan uary 2015 | |
120 | CAS RxSU2 Requiremen ts Specifi cation Doc ument (RSD ) Version 1.0, Septe mber 2017 | |
121 | CAS RxSU2 Requiremen ts Traceab ility Matr ix (RTM) V ersion 1.0 , Septembe r 2017 | |
122 | Veteran-Fo cused Inte gration Pr ocess Guid e, 2.0, Ma y 2017 | |
123 | Configurat ion Manage ment Devel opment Fil es (Ex. So urce, JSP, Configura tion, and Build File s) | |
124 | Rational C hange and Configurat ion Manage ment (CCM) Repositor y | |
125 | The CCM/RT C location for the d ocuments a nd CCM/RTC explanati on for the informati on. | |
126 | CCM/RTC In formation | |
127 | Explanatio n | |
128 | CCM URL | |
129 | https:// DNS . URL /ccm/web/p rojects/PB M%20(CM)#a ction=com. ibm.team.s cm.browseS tream&id=_ bsI4kFwvEe eKmr_L82eL AQ | |
130 | CCM Projec t Area | |
131 | PBM(CM) Rx SU2 Projec t | |
132 | CCM Team A rea | |
133 | PBM(CM) Rx SU2 Projec t | |
134 | Stream | |
135 | PBM_CAS_Rx SU2_Produc tion_Strea m | |
136 | Baseline I D | |
137 | CAS RxSU2_ Build_1_Sp rint_2 | |
138 | ||
139 | Component( s) | |
140 | Where a se t of artif acts are g rouped and managed. | |
141 | Name | |
142 | Descriptio n | |
143 | CAS RxSU2 | |
144 | PBM Source Code Comp onent: PBM _CAS_RxSU2 _src | |
145 | ||
146 | Baseline | |
147 | The baseli ne name, s uch as a l abel or ta g. | |
148 | Name | |
149 | Descriptio n | |
150 | CAS_RxSU2_ Build_1 Sp rint_2 | |
151 | Baseline f or CAS RxS U2 Build-1 Sprint-2 | |
152 | ||
153 | Build Info rmation | |
154 | General bu ild inform ation that results f rom the bu ild proces s. | |
155 | Name | |
156 | Descriptio n | |
157 | Build Outp ut | |
158 | \PBM_CAS_R xSU2_Produ ction_Stre am\PBM_CAS _RxSU2_src \Release\B uild-1\Spr int-2\Vist A\ GMRA_4_ 58.KID, P SJ_5_353.K ID, PSN_4_ 541.KID, P SO_7_507.K ID, PSS_1 _218.KID | |
159 | Build Outp ut Directo ry | |
160 | \PBM_CAS_R xSU2_Produ ction_Stre am\PBM_CAS _RxSU2_src \Release\B uild-1\Spr int-2\Vist A\.. | |
161 | Target Dep loyment Lo cation | |
162 | CAS Develo pment and Test Envir onments: C HYSHR, DAY TSHR | |
163 | CCM/RTC Bu ild Defini tion | |
164 | The name o f the buil d definiti on, which controls w hat is bui lt and how it is bui lt. | |
165 | Name | |
166 | Descriptio n | |
167 | GMRA_4_58 | |
168 | PSJ_5_353 | |
169 | PSN_4_541 | |
170 | PSO_7_507 | |
171 | PSS_1_218 | |
172 | \PBM_CAS_R xSU2_Produ ction_Stre am\PBM_CAS _src\Relea se\Build-1 \Sprint-2\ VistA\... | |
173 | Build Labe l or Numbe r | |
174 | The identi fier for t he derived object or package t hat was pr oduced for deploymen t and/or i nstall. | |
175 | Name | |
176 | Descriptio n | |
177 | CAS RxSU2_ Build_1_Sp rint_2 | |
178 | CAS RxSU2 Build-1 Sp rint-2 | |
179 | Build and Packaging | |
180 | Build Logs | |
181 | \PBM_CAS_R xSU2_Produ ction_Stre am\PBM_CAS _src\Relea se\ Build- 1\Sprint-2 \VistA\.. | |
182 | Build Syst em/Process Informati on | |
183 | PBM_CAS_Rx SU2_Produc tion_Strea m\PBM_CAS_ src\Releas e\ Build-1 \Sprint-2\ VistA\.. | |
184 | Change Tra cking | |
185 | Change Tra cking Tool | |
186 | Change Tra cking Tool Location | |
187 | Tool | |
188 | Onsite/ | |
189 | Offsite | |
190 | Change Tra cking Tool Access / POC | |
191 | Access Inf ormation ( Forms or o ther acces s requirem ents) | |
192 | IBM Ration al Team Co ncert, v6. 0. | |
193 | VA Rationa l Jazz Ser ver | |
194 | Onsite | |
195 | Joseph A. McGovern | |
196 | RTSUB Rati onal Tools Team | |
197 | Rational C hange and Configurat ion Manage ment (CCM) Repositor y | |
198 | ||
199 | Location | |
200 | Terms | |
201 | CCM URL | |
202 | https:// DNS . URL /ccm/web/p rojects/PB M%20(CM)#a ction=com. ibm.team.s cm.browseS tream&id=_ bsI4kFwvEe eKmr_L82eL AQ | |
203 | CCM Projec t Area | |
204 | PBM(CM) Rx SU2 Projec t | |
205 | CCM Team A rea | |
206 | PBM(CM) Rx SU2 Projec t | |
207 | ||
208 | Work Item ID | |
209 | Sprint-2 S tory / Def ect Summar y | |
210 | 592204 | |
211 | 1.1.1.01 | As a phar macist, I need the s pecial han dling prop erty "K" a dded to th e list of codes and their desc riptions, so that Vi stA can ac count for this code when used by AudioCa re. | |
212 | 592205 | |
213 | 1.3.1.01 | As a prov ider writi ng an outp atient pre scription, I want du plicate th erapy aler ts suppres sed when I write the prescript ion within (a) the l ast 25% of the medic ation's ca lculated d ays supply , (b) wher e I was th e prescrib er on the profile pr escription , and (c) when the d ispense dr ug is the same as th e previous prescript ion, so th at I do no t get aler t fatigue. | |
214 | 592207 | |
215 | 1.4.1.01 | As a phar macist usi ng the (to -be) 'Send Mail Mess age when D epartment of Veteran s Affairs (VA) Drug Class fiel d is empty ' function ality, I n eed the sy stem to su ppress the email fun ctionality if the re actant typ e does not contain " Drug". | |
216 | 592210 | |
217 | 1.5.1.01 | As a phar macist fin ishing med ication or ders, I ne ed the abi lity to vi ew more in formation about the provider a nd the med ication on the order , so that I can conf irm the pr escriber p rivileges for a medi cation. | |
218 | 592208 | |
219 | 1.6.1.01 | As a phar macist, I need the f ield indic ating whet her a medi cation is active/ina ctive disp layed in t he lookup list, so t hat I may select the active me dication, initially. | |
220 | 592214 | |
221 | 1.7.1.01 | As a phar macist, I need to vi ew additio nal inform ation abou t the atte nding prov ider's tre atment spe cialty on the patien t medicati on 'Patien t Informat ion' and ' Order Entr y' screen( s) so that I know mo re about t he acuity of the pat ient's tre atment. | |
222 | ||
223 | Release (D eployment) Informati on | |
224 | Release Id entificati on | |
225 | Release Pa ckage POC Name | |
226 | Release Pa ckage POC Email | |
227 | CAS RxSU2 | |
228 | J. McGove rn – CAS R xSU2 Team | |
229 | PII | |
230 | ||
231 | Release Pa ckage (Com ponent) Id entified | |
232 | Release Pa ckage Desc ription | |
233 | Release Pa ckage Deli very Metho d | |
234 | Release Pa ckage Loca tion Ident ified | |
235 | GMRA_4_58 | |
236 | PSJ_5_353 | |
237 | PSN_4_541 | |
238 | PSO_7_507 | |
239 | PSS_1_218 | |
240 | CAS RxSU2 Build-1 Sp rint-2 | |
241 | RTC Source Code Repo sitory | |
242 | PBM_CAS_Rx SU2_Produc tion_Strea m | |
243 | Additional Supportin g Document ation | |
244 | Document N ame | |
245 | Revision | |
246 | Date | |
247 | N/A | |
248 | N/A | |
249 | N/A |
Araxis Merge (but not the data content of this report) is Copyright © 1993-2016 Araxis Ltd (www.araxis.com). All rights reserved.