Produced by Araxis Merge on 9/11/2018 8:57:42 AM Central 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 MCCF EDI TAS_Sept2018.zip\Remaining Doc.zip | TAS eBill VDD IB_2_608.docx | Fri Jun 29 19:27:34 2018 UTC |
2 | OSCIF MCCF EDI TAS_Sept2018.zip\Remaining Doc.zip | TAS eBill VDD IB_2_608.docx | Mon Sep 10 18:52:08 2018 UTC |
Description | Between Files 1 and 2 |
|
---|---|---|
Text Blocks | Lines | |
Unchanged | 37 | 572 |
Changed | 34 | 84 |
Inserted | 0 | 0 |
Removed | 3 | 3 |
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 | Version De scription Document | ||||
2 | Medical Ca re Collect ion Fund ( MCCF) EDI | ||||
3 | Transactio n Applicat ion Suite (TAS) eBil ling Build 5/6 | ||||
4 | IB*2.0*608 | ||||
5 | |||||
6 | June 2018 | ||||
7 | Document V ersion 1.0 | ||||
8 | Department of Vetera ns Affairs | ||||
9 | Document R evision Hi story | ||||
10 | Date | ||||
11 | Document V ersion | ||||
12 | Descriptio n | ||||
13 | VDD Author / Team Ro le | ||||
14 | VA Group o r Contract Company | ||||
15 | June 2018 | ||||
16 | 1.0 | ||||
17 | Initial Do cument | ||||
18 | PII | ||||
19 | Halfaker & Leidos | ||||
20 | |||||
21 | Deliverabl e (Product ) Version History | ||||
22 | Date | ||||
23 | Release / Revision | ||||
24 | Descriptio n | ||||
25 | Project Na me | ||||
26 | VA Departm ent | ||||
27 | June 2018 | ||||
28 | IB*2.0*608 T31 | ||||
29 | Initial Bu ild releas e for IOC testing. | ||||
30 | MCCF EDI T AS EBILLIN G BUILD 5/ 6 | ||||
31 | Product De velopment | ||||
32 | |||||
33 | 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 V DD reinfor ces strong risk mana gement pra ctices and helps pro tect VA fr om loss of the produ ct (IT ass et), which is especi ally impor tant with a regular rotation o f personne l and cont ractors. | ||||
34 | |||||
35 | The VDD is a mandate d document that will be verifi ed prior t o Release. | ||||
36 | |||||
37 | 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. The VDD is its elf a Conf iguration Item maint ained unde r change c ontrol in the TRM-ap proved con figuration managemen t system, which is p art of the VA Federa ted Config uration Ma nagement D ata Base ( CMDB). | ||||
38 | |||||
39 | Project Ma nagers and Configura tion Manag ers use th e VDD temp late as a tool for m anaging Co nfiguratio n Items an d baseline s associat ed with th e deployab le product . It is th e responsi bility of the Projec t Manager to ensure the proces ses are fo llowed wit hin the pr oduct buil d process (ProPath, Product Bu ild: BLD-1 Develop P roduct Com ponent). T he expecta tion is th at the VDD is contro lled as a source fil e having o ne VDD per Product t hat has ma ny version s managed within the SCM repos itory foll owing base line proce sses. The IT Configu ration Man agers (or IT Archite ct/Develop ment Lead) ensure th at creatio n and modi fication o f the Prod uct’s VDD is integra ted with a ny paralle l activiti es being p erformed o n the prod uct. The C onfigurati on Manager creates/u pdates the VDD each time the d eliverable (file set ) leaves t he develop ment envir onment, su ch as for testing or deploymen t. The VDD is the re presentati on and res ult of fol lowing the Software Configurat ion Manage ment Proce dures. The Product P rocedures along with work inst ructions a re to be c reated and maintaine d by the I T Configur ation Mana gers (or b y the IT A rchitect/D evelopment Lead). Fo r product procedure informatio n, refer t o the Soft ware Confi guration M anagement Procedures Template (ProPath, Project Pl anning: PR P 3.7). Th e Project Manager is responsib le for ens uring the Configurat ion Manage r maintain s versions of the VD D and deli verables ( files) in the TRM-ap proved con figuration managemen t system. | ||||
40 | Table of C ontents | ||||
41 | General Co nfiguratio n Manageme nt (CM) In formation1 | ||||
42 | Configurat ion Manage ment (CM) Tools1 | ||||
43 | Configurat ion Manage ment of Do cuments1 | ||||
44 | Rational C hange and Configurat ion Manage ment (CCM) Documents 1 | ||||
45 | Configurat ion Manage ment Devel opment Fil es (Ex. So urce, JSP, Configura tion, and Build File s)4 | ||||
46 | Rational C hange and Configurat ion Manage ment (CCM) Repositor y (Formerl y RTC)4 | ||||
47 | Baseline a nd Compone nt4 | ||||
48 | Build Info rmation4 | ||||
49 | CCM/RTC Bu ild Defini tion5 | ||||
50 | Build Labe l or Numbe r5 | ||||
51 | Build and Packaging5 | ||||
52 | Build Logs 5 | ||||
53 | Build Syst em/Process Informati on5 | ||||
54 | Change Tra cking6 | ||||
55 | Rational C hange and Configurat ion Manage ment (CCM) Repositor y (Formerl y RTC)6 | ||||
56 | Release (D eployment) Informati on7 | ||||
57 | |||||
58 | |||||
59 | |||||
60 | |||||
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 | Integrated Billing | ||||
69 | PII | ||||
70 | IB*2.0*608 T31 | ||||
71 | Leidos & H alfaker | ||||
72 | |||||
73 | Configurat ion Manage ment (CM) Tools | ||||
74 | CM Tools | ||||
75 | CM Tool Lo cation | ||||
76 | Tool | ||||
77 | Onsite/ | ||||
78 | Offsite | ||||
79 | CM Tool Ac cess | ||||
80 | Point of C ontact | ||||
81 | Access Inf ormation ( Forms or o ther acces s requirem ents) | ||||
82 | FORUM | ||||
83 | Albany | ||||
84 | VA Network | ||||
85 | VA OI&T | ||||
86 | |||||
87 | Rational 6 .0.5 | ||||
88 | Hines Data Center | ||||
89 | |||||
90 | VA Network | ||||
91 | VA Rationa l Tools Te am | ||||
92 | |||||
93 | http://URL | ||||
94 | Rally | ||||
95 | |||||
96 | Outside VA Network | ||||
97 | Halfaker | ||||
98 | https://UR L | ||||
99 | |||||
100 | Configurat ion Manage ment of Do cuments | ||||
101 | Rational C hange and Configurat ion Manage ment (CCM) Documents | ||||
102 | The CCM/RT C location for the d ocuments a nd CCM/RTC explanati on for the informati on. | ||||
103 | CCM/RTC In formation | ||||
104 | Explanatio n | ||||
105 | CCM URL | ||||
106 | The primar y change a nd configu ration man agement fo r this pat ch release is being addressed in Rally, outside th e VA firew all. | ||||
107 | https://UR L | ||||
108 | |||||
109 | VA Rationa l: | ||||
110 | https://UR L | ||||
111 | |||||
112 | |||||
113 | CCM Projec t Area | ||||
114 | Rally: eBi lling | ||||
115 | Rational: MCCF EDI T AS | ||||
116 | CCM Team A rea | ||||
117 | Rally: eBi lling | ||||
118 | Rational: eBilling | ||||
119 | CCM Stream | ||||
120 | eBilling_d ocument_st ream | ||||
121 | Baseline I D | ||||
122 | (151: ebil ling_doc_0 6292018) | ||||
123 | Components | ||||
124 | Rational: MCCF_EDI_T AS eBillin g_document s | ||||
125 | Rally: Doc uments are tied to t he respect ive user s tories in Rally. | ||||
126 | Directory Path | ||||
127 | Rational: ( Note: Cu t link and paste int o web brow ser) | ||||
128 | https://UR L | ||||
129 | |||||
130 | Rally: htt ps://URL | ||||
131 | |||||
132 | Documents Included | ||||
133 | In the Bas eline | ||||
134 | |||||
135 | Documents loaded to Rational | ||||
136 | |||||
137 | Document | ||||
138 | Rational L ink | ||||
139 | Work Item ID | ||||
140 | Patch Desc ription | ||||
141 | |||||
142 | |||||
143 | |||||
144 | |||||
145 | |||||
146 | Defect Log | ||||
147 | url | ||||
148 | url | ||||
149 | |||||
150 | |||||
151 | Test Execu tion Log | ||||
152 | |||||
153 | ur: | ||||
154 | IOC Test E xecution L og | ||||
155 | N/A | ||||
156 | |||||
157 | |||||
158 | SQA Checkl ist | ||||
159 | |||||
160 | url | ||||
161 | Traceabili ty Matrix( RTM) | ||||
162 | |||||
163 | url | ||||
164 | url | ||||
165 | |||||
166 | Version De scription Document | ||||
167 | url | ||||
168 | url: | ||||
169 | Deploy Ins tall Back- Out Rollba ck Guide | ||||
170 | url | ||||
171 | |||||
172 | url | ||||
173 | Technical Manual | ||||
174 | url | ||||
175 | url: | ||||
176 | User Manua l | ||||
177 | url | ||||
178 | url | ||||
179 | |||||
180 | |||||
181 | |||||
182 | |||||
183 | |||||
184 | Configurat ion Manage ment Devel opment Fil es (Ex. So urce, JSP, Configura tion, and Build File s) | ||||
185 | Rational C hange and Configurat ion Manage ment (CCM) Repositor y (Formerl y RTC) | ||||
186 | The CCM/RT C location for the d evelopment files (so urce) and CCM/RTC ex planation for the in formation. | ||||
187 | CCM/RTC In formation | ||||
188 | Explanatio n | ||||
189 | CCM URL | ||||
190 | Since this is a Vist A Patch, t he source files were submitted to Forum – forum.me d.va.gov | ||||
191 | Source cod e was not stored in Rational f or this re lease | ||||
192 | CCM Projec t Area | ||||
193 | Forum Name space: Int egrated Bi lling – IB namespace | ||||
194 | Rational: MCCF EDI T AS | ||||
195 | |||||
196 | CCM Team A rea | ||||
197 | Rational: eBilling | ||||
198 | Stream | ||||
199 | N/A – Vist a Source c ode not st ored in Ra tional | ||||
200 | |||||
201 | Baseline a nd Compone nt | ||||
202 | Where a se t of artif acts are i dentified as baselin ed, groupe d and mana ged. | ||||
203 | Name | ||||
204 | Descriptio n | ||||
205 | Rally – VA MCCF / eB illing / | ||||
206 | User stori es, accept ance crite ria, test scripts, e xecution l og of test scripts, defects, S DD, and ac ceptance o f SDDs. | ||||
207 | Forum | ||||
208 | KIDs build and patch descripti on | ||||
209 | Component/ Baseline: MCCF_EDI_T AS eBillin g_document s / (151: ebilling_d oc_0629201 8) | ||||
210 | Location f or Rationa l VIP docu ments | ||||
211 | |||||
212 | Build Info rmation | ||||
213 | General bu ild inform ation that results f rom the bu ild proces s. | ||||
214 | Name | ||||
215 | Descriptio n | ||||
216 | Build Outp ut | ||||
217 | IB*2.0*698 T31 | ||||
218 | Build Outp ut Directo ry | ||||
219 | Upon natio nal releas e: downloa d.vista.me d.va.gov | ||||
220 | Target Dep loyment Lo cation | ||||
221 | National r elease to all VistA sites | ||||
222 | |||||
223 | CCM/RTC Bu ild Defini tion | ||||
224 | The name o f the buil d definiti on, which controls w hat is bui lt and how it is bui lt. | ||||
225 | Name | ||||
226 | Descriptio n | ||||
227 | N/A | ||||
228 | RTC build definition s are not used to bu ild Vista patches | ||||
229 | |||||
230 | |||||
231 | Build Labe l or Numbe r | ||||
232 | The identi fier for t he derived object or package t hat was pr oduced for deploymen t and/or i nstall. | ||||
233 | Name | ||||
234 | Descriptio n | ||||
235 | IB*2.0*608 T31 | ||||
236 | MCCF EDI T AS EBILLIN G BUILD 5/ 6 | ||||
237 | |||||
238 | Build and Packaging | ||||
239 | Build Logs | ||||
240 | The KIDS b uild for I B*2.0*608 is maintai ned in the National Patch Modu le (NPM) w ithin foru m behind t he VA Fire wall. | ||||
241 | |||||
242 | |||||
243 | Build Syst em/Process Informati on | ||||
244 | Forum trac ks all KID S builds t hat are na tionally r eleased, c ompleted/n ot release d, and tho se under d evelopment . It conta ins the co de (routin es, menu o ptions, Li stMan temp lates, pro tocols, et c.), that were creat ed or modi fied as pa rt of the patch. It is the tru e source f ile for al l national ly release d code. It also help s identify those rou tines that are being updated b y more tha n one patc h to help teams iden tify who n eeds to co ordinate w ith whom f or overlap s. | ||||
245 | |||||
246 | Change Tra cking | ||||
247 | Change Tra cking Tool | ||||
248 | Change Tra cking Tool Location | ||||
249 | Tool | ||||
250 | Onsite/ | ||||
251 | Offsite | ||||
252 | Change Tra cking Tool Access / POC | ||||
253 | Access Inf ormation ( Forms or o ther acces s requirem ents) | ||||
254 | CA Rally | ||||
255 | https://UR L | ||||
256 | Offsite | ||||
257 | PII | ||||
258 | Contact:PI I | ||||
259 | |||||
260 | Rational C hange and Configurat ion Manage ment (CCM) Repositor y (Formerl y RTC) | ||||
261 | Location | ||||
262 | Terms | ||||
263 | CCM URL | ||||
264 | https://UR L | ||||
265 | CCM Projec t Area | ||||
266 | MCCF_EDI_T AS (CM) | ||||
267 | CCM Team A rea | ||||
268 | eBilling | ||||
269 | |||||
270 | Work Item ID | ||||
271 | Summary | ||||
272 | URL | ||||
273 | |||||
274 | RCB - Matc h COB Data to Payer Sequence | ||||
275 | URL | ||||
276 | |||||
277 | Non-MCCF U nbilled Am ounts Repo rt | ||||
278 | URL | ||||
279 | |||||
280 | Claims Tra cking Indi cator of R ecord Code d | ||||
281 | URL | ||||
282 | |||||
283 | Remove Fat al Error - Rendering Provider CMS 1500 | ||||
284 | URL | ||||
285 | |||||
286 | Non-MCCF P ay-to Prov ider RALLY ID US2599 > | ||||
287 | URL | ||||
288 | |||||
289 | Add T for Transmitte d to RCB S creen (Ral ly ID: US1 908) | ||||
290 | URL | ||||
291 | |||||
292 | Transmitti ng SNF Cla ims with A ppropriate Revenue C odes | ||||
293 | URL | ||||
294 | |||||
295 | Remove Abi lity to De fine Insur ance Compa ny as non- EDI (Rally ID: US190 9) | ||||
296 | |||||
297 | URL | ||||
298 | |||||
299 | CMN Oxygen and EPN N utrition ( Rally ID: US3) | ||||
300 | |||||
301 | Release (D eployment) Informati on | ||||
302 | Release Id entificati on | ||||
303 | Release Pa ckage POC Name | ||||
304 | Release Pa ckage POC Email | ||||
305 | IB*2.0*608 | ||||
306 | PII | ||||
307 | PII | ||||
308 | |||||
309 | Release Pa ckage (Com ponent) Id entified | ||||
310 | Release Pa ckage Desc ription | ||||
311 | Release Pa ckage Deli very Metho d | ||||
312 | Release Pa ckage Loca tion Ident ified | ||||
313 | IB*2.0*608 | ||||
314 | KIDs build | ||||
315 | PackMan me ssage | ||||
316 | Forum | ||||
317 | ib_2_0_p60 8_edi_ug.p df | ||||
318 | User guide | ||||
319 | .pdf downl oad | ||||
320 | URL | ||||
321 | |||||
322 | ib_2_0_p60 8_ig.pdf | ||||
323 | Deployment , Backout and Rollba ck Plan | ||||
324 | .pdf downl oad | ||||
325 | URL | ||||
326 | ib_2_0_p60 8_tm.pdf | ||||
327 | Technical/ Security M anual | ||||
328 | pdf downlo ad | ||||
329 | URL |
Araxis Merge (but not the data content of this report) is Copyright © 1993-2016 Araxis Ltd (www.araxis.com). All rights reserved.