Produced by Araxis Merge on 2/7/2017 12:14:12 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 | cpss.zip | PSE RSD Phase 2 Incr02 V2.5.docx | Wed Feb 1 21:07:14 2017 UTC |
2 | cpss.zip | PSE RSD Phase 2 Incr02 V2.5.docx | Fri Feb 3 17:47:39 2017 UTC |
Description | Between Files 1 and 2 |
|
---|---|---|
Text Blocks | Lines | |
Unchanged | 6 | 2770 |
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 | Patient St atement En hancement - Phase 2 | |
2 | Requiremen ts Specifi cation Doc ument | |
3 | ||
4 | December 2 016 | |
5 | Version 2. 5 | |
6 | Department of Vetera ns Affairs | |
7 | ||
8 | ||
9 | Revision H istory | |
10 | Note: The revision h istory cyc le begins once chang es or enha ncements a re request ed after t he Require ments Spec ification Document h as been ba selined. | |
11 | Date | |
12 | Version | |
13 | Descriptio n | |
14 | Author | |
15 | 12/15/2016 | |
16 | 2.5 | |
17 | Added Requ irement AC J007 to im plement th e correct missing tr ansaction amount cal culation; and ACJ015 to correc tly fix In complete t ransaction s for non- active bil ls. (CR# 4 32565) | |
18 | ||
19 | Added US00 9 and Requ irement AR 001 to upd ate the AR Adjustmen t menu opt ion bill c alculation . (CR# 414 650) | |
20 | ||
21 | Added US00 8 to inclu de a new s ort order version of the Auto- Correction Report (C R #430031) | |
22 | ||
23 | Added User Story US0 10 for Fil eMan spell ing correc tions. (CR #416592) | |
24 | ||
25 | Added User Story US0 10 to acco unt for da ta archivi ng require ments as d iscussed a t the requ irements e laboration meeting o n 10/29/20 15. | |
26 | ||
27 | Updated re quirement 3.1.2 to e xplicitly state that two CBS f iles are s ent to AIT C and that the file is sorted so that th e primary site data is listed first. | |
28 | ||
29 | Add detail ed sub-req uirements to AR repo rts requir ements 8.1 .1, 8.1.2, and 8.13 and update d AR Repor t mock ups in sectio n 2.6.10. | |
30 | ||
31 | Update req uirement 2 .1.2 to in clude DFN on the CBS account n umber (CR# 440415). | |
32 | Ray Mattes on | |
33 | 8/22/2016 | |
34 | 2.4 | |
35 | Added requ irements ( 3.1.14 & 3 .1.15) ) t o the Send CBS proce ss to not start job if Generat e CBS is r unning (CR # 313059). | |
36 | ||
37 | Updated re quirement 4.2.1 to s end paymen t allocati on based o n a balanc e owed (CR # 366324). | |
38 | Ray Mattes on | |
39 | 8/12/2106 | |
40 | 2.3 | |
41 | Removed BN 4.1 from scope per contract m odificatio n. | |
42 | ||
43 | Added requ irements ( BN 7) for Two Factor Authentic ation per contract m odificatio n. | |
44 | Ray Mattes on | |
45 | 8/5/2016 | |
46 | 2.2 | |
47 | Added Prin t Acknowle dgement Re quirements | |
48 | Added Epic (9.0.0) a nd User St ory & Requ irements 9 .1.X in Ta ble 2.9 fo r the enha ncements o f the Vist A AR Repor ts. | |
49 | ||
50 | Existing V ista Repor ts | |
51 | Added Epic (9.0.0) a nd User St ory & Requ irements 8 .1.X in Ta ble 2.9 fo r the enha ncements o f the Vist A AR Repor ts. | |
52 | ||
53 | Added requ irement 4. 2.1 for ni ghtly file to AITC/L OCKBOX. | |
54 | Updated Ta ble 2.8 to reflect t he new 16- day FPS fi le schedul e. | |
55 | Update Req uirement 1 .1.1 to re flect a 16 -day FPS f ile cycle. | |
56 | Added requ irements 1 .1.3 throu gh 1.1.7 t o the Load FPS Data User Story . | |
57 | Added requ irement 3. 1.11 throu gh 3.1.13 to the Sen d CBS User Story. | |
58 | Added User Story 5.4 .0 for 2 f actor auth entication . | |
59 | Added requ irements 6 .1.6 & 6.1 .7 to the Manage ICN User Stor y. | |
60 | Ray Mattes on/Diana C ollins | |
61 | 5/16/2016 | |
62 | 2.1 | |
63 | Updated to include 3 new Chang e Orders: | |
64 | -Second Vi stA patch to update statement run date ( 3.1.13) | |
65 | -Send a me ssage if t here was a problem w ith the ac knowledgem ent files (3.1.12) | |
66 | -Use a fla g to ident ify when a dditional statements are sent out (outsi de of the standard m onthly sta tement) (3 .1.11) | |
67 | Diana Coll ins | |
68 | 4/26/2016 | |
69 | 1.12 | |
70 | Inserted t ext for BN 2.1, 2.2, and 3.1 i n table 2. 7.1. | |
71 | Beth Easto n | |
72 | 03/21/2016 | |
73 | 1.11 | |
74 | Update to change acr onyms ‘CPS ’ to ‘CBS’ and ‘CPSS ’ to ‘CBSS ’. | |
75 | Erica Robe rtson | |
76 | 02/18/2016 | |
77 | 1.10 | |
78 | Updated Fi gure 2 and changed A ITC/Lockbo x descript ion in tab le 2-2. | |
79 | Beth Easto n | |
80 | 02/17/2016 | |
81 | 1.09 | |
82 | Updated Fi gure 2, ad ded email content te xt to 2.6. 1 through 2.6.4, cha nged distr ibution me thod to al location, removed Ap pendix 1 a nd changed reference to SDD. | |
83 | Beth Easto n | |
84 | 02/16/2016 | |
85 | 1.08 | |
86 | Updated Fi gures 5 an d 10, Sect ion 2.10, and AITC d escription s througho ut documen t. | |
87 | Beth Easto n | |
88 | 02/11/2016 | |
89 | 1.07 | |
90 | Updated to reflect V A reviewer ’s comment s. | |
91 | Erica Robe rtson/Beth Easton | |
92 | 01/21/2016 | |
93 | 1.06 | |
94 | Updated Fi gures and tables thr oughout RS D | |
95 | Section Up dates Incl ude: | |
96 | Section 1. 2 Scope nu mbers 1 an d 2. | |
97 | Section 2 Overall De scription, added new figure an d table. | |
98 | Section 2. 6 added fi gures and descriptio n | |
99 | Section 2. 7 added an d deleted tables | |
100 | Updated de scriptions in sectio ns 2-9, 2- 10, 2-12, 2-13, 2-14 , 2-15, 2- 16 | |
101 | Updated Se ction 3 Pu rchased Co mponents R emoved: gl obal payme nt section s and text | |
102 | Updated al l subsecti ons of sec tion 2 to reflect la test busin ess decisi ons | |
103 | Erica Robe rtson/ Bet h Easton | |
104 | 01/06/2015 | |
105 | 1.05 | |
106 | Updates in clude cove r page, ve rsion hist ory and da te. | |
107 | Section up dates incl ude: | |
108 | Section 1. 2 -1.3, 2. 4, 2.5 for matting an d added sp ecificatio ns | |
109 | Section 2. 0 descript ion update d | |
110 | Tables 2-1 , 2-3, 2-6 spelling and descri ptions upd ated | |
111 | Table 2-5 updated | |
112 | Section 2. 1 moved to Appendix A.2 | |
113 | Section 2. 3 added ve rbiage for explanati on | |
114 | Section 2. 4 updated and added enterprise requireme nt specifi cation | |
115 | Section 2. 5- updated verbiage and added new table for PSE do cumentatio n | |
116 | Figure 7- revised fi gure | |
117 | 2.6.1.1 ad ded detail and a tab le for cla rification | |
118 | Section 2. 6.1.3 spel ling | |
119 | Shawnee Bl air/Heathe r Chatwin/ Erica Robe rtson | |
120 | 12/17/2015 | |
121 | 1.04 | |
122 | Updates oc curred bet ween 11/1 through 12 /17, and i nclude cov er page ve rsion and date. | |
123 | Section up dates incl ude: | |
124 | Section 1, added sec tion 1.2.1 -Out of Sc ope requir ement. | |
125 | Section 2, updated f igure and table. | |
126 | Section 2. 2-updated business r ule questi ons with a nswers and status to date. | |
127 | Section 2. 6, updated section n ame and de scription of content s. | |
128 | Section 2. 6.1 – prov ided updat ed process diagrams for Manage CBS Data module. | |
129 | Section 2. 6.2, provi ded update d process diagrams f or Generat e CBS modu le. | |
130 | Section 2. 6.3, provi ded update d process diagrams f or Manage Batch modu le. | |
131 | The follow ing requir ements wer e amended: CBSS001, CBSS003, C BSS004, CB SS005, CBS S006, CBSS 010, CBSS0 11, CBSS01 4, CBSS015 , CBSS017, CBSS018, CBSS020, C BSS026 | |
132 | Added the following requiremen ts: CBSS00 6.1, CBSS0 10.1, CBSS 011.1, CBS S011.2, CB SS011.3, C BSS011.4, CBSS012.1, CBSS012.2 | |
133 | Revised US 006. | |
134 | Heather Ch atwin | |
135 | 10/29/2015 | |
136 | 1.03 | |
137 | Removed ou t of scope section a nd updated scope sec tion. Upda ted cover page and f ooters. | |
138 | Heather Ch atwin | |
139 | 10/18/2014 | |
140 | 1.02 | |
141 | The follow ing sectio ns were re vised for the final draft: | |
142 | Section 1. 2.1: this section wa s added to address i tems that are out of scope for Phase 2 d evelopment . | |
143 | Section 1. 3: added a dditional reference material t hat was an alyzed to create To- Be process es. | |
144 | Section 2: updated t he diagram and table descripti ons, | |
145 | Section 2. 2: removed business rules but kept the p lace holde r for the ten outsta nding ques tions. | |
146 | Section 2. 6: Introdu ced and ad ded workfl ows. | |
147 | Section 2. 7: Introdu ces functi onal speci fications and revise d requirem ents. | |
148 | Section 3: added ver biage rega rding the hardware a nd softwar e componen ts necessa ry for Pha se 2 devel opment. | |
149 | Heather Ch atwin | |
150 | 10/1/2014 | |
151 | 1.01 | |
152 | Updated do cument per internal team revie w and requ irement el aboration sessions. Updated co ver page a nd footers . | |
153 | Heather Ch atwin | |
154 | 9/16/2015 | |
155 | 1.0 | |
156 | Initial dr aft | |
157 | Heather Ch atwin | |
158 | Tony Nixon | |
159 | ||
160 | Artifact R ationale | |
161 | The Requir ements Spe cification Document (RSD) reco rds the re sults of t he specifi cation gat hering pro cesses car ried out d uring the Requiremen ts phase. The RSD is generally written b y the func tional ana lyst(s) an d should p rovide the bulk of t he informa tion used to create the test p lan and te st scripts . It shoul d be updat ed for eac h incremen t. | |
162 | The level of detail contained in this RS D should b e consiste nt with th e size and scope of the projec t. It is n ot necessa ry to fill out any s ections of this docu ment that do not app ly to the project. T he resourc es necessa ry to crea te and mai ntain this document during the life cycl e of a lar ge project should be acknowled ged and cl early refl ected in p roject sch edules. Do not dupli cate data that is al ready defi ned in ano ther docum ent or a s ection in this docum ent; note in the sec tion where the infor mation can be found. | |
163 | Table of C ontents | |
164 | 1.Introduc tion1 | |
165 | 1.1.Purpos e1 | |
166 | 1.2.Scope1 | |
167 | 1.2.1.Out of Scope3 | |
168 | 1.3.Refere nces3 | |
169 | 2.Overall Descriptio n3 | |
170 | 2.1.Access ibility Sp ecificatio ns8 | |
171 | 2.2.Busine ss Rules S pecificati on9 | |
172 | 2.2.1.CBS Person Tra its9 | |
173 | 2.2.2.CBS Veteran Ma iling Addr ess9 | |
174 | 2.2.3.CBSS Payment D istributio n10 | |
175 | 2.2.4.CBSS User Acce ss11 | |
176 | 2.3.Design Constrain ts Specifi cation11 | |
177 | 2.4.Disast er Recover y Specific ation12 | |
178 | 2.5.Docume ntation Sp ecificatio ns12 | |
179 | 2.6.Functi onal Speci fications1 3 | |
180 | 2.6.1.Load FPS Data1 3 | |
181 | 2.6.2.Gene rate CBS14 | |
182 | 2.6.3.Send CBS16 | |
183 | 2.6.4.Upda te Print A cknowledgm ent16 | |
184 | 2.6.5.Mana ge Bill Da ta17 | |
185 | 2.6.6.Mana ge Batch18 | |
186 | 2.6.7.Mana ge ICN21 | |
187 | 2.6.8.Gene rate FPS ( VistA AR)2 1 | |
188 | 2.6.9.Send Nightly B ill Inform ation22 | |
189 | 2.6.10.Enh ance VistA AR Report s22 | |
190 | 2.6.11.Enh ance Auto- Correction Processi ng Logic2 6 | |
191 | 2.6.12.Enh ance the I ncrease/De crease Adj ustment Me nu Option2 7 | |
192 | 2.6.13.Fun ctional Re quirements 28 | |
193 | 2.6.14.Non -Functiona l Requirem ents37 | |
194 | 2.6.15.Add itional PW S Requirem ents37 | |
195 | 2.7.Graphi cal User I nterface ( GUI) Speci fications3 8 | |
196 | 2.8.Multi- divisional Specifica tions38 | |
197 | 2.9.Perfor mance Spec ifications 38 | |
198 | 2.10.Quali ty Attribu tes Specif ication39 | |
199 | 2.11.Relia bility Spe cification s39 | |
200 | 2.12.Scope Integrati on39 | |
201 | 2.13.Secur ity Specif ications41 | |
202 | 2.14.Syste m Features 41 | |
203 | 2.15.Usabi lity Speci fications4 1 | |
204 | 3.Purchase d Componen ts41 | |
205 | 4.Approval Signature s43 | |
206 | A.1.CBSS U ser44 | |
207 | ||
208 | ||
209 | List of Ta bles | |
210 | Table 21: Actors and User Role s5 | |
211 | Table 22: CBSS Actor Descripti ons6 | |
212 | Table 23: CBSS Capab ilities an d Brief De scriptions 7 | |
213 | Table 24 U ser Access to Consol idated Pat ient State ment9 | |
214 | Table 25 P SE Documen tation Req uirements1 2 | |
215 | Table 26: Validation s for Bill Data File Load Proc ess18 | |
216 | Table 27: New Attrib utes Added to The FP S File21 | |
217 | Table 28: Modified S chedule fo r FPS File Generatio n by Patie nt Last Na me22 | |
218 | Table 29 C BS Functio nal Requir ements28 | |
219 | Table 210 Auto-Corre ction and Transactio n Discrepa ncy Fix Fu nctional R equirement s35 | |
220 | Table 211 Additional Requireme nts38 | |
221 | Table 31 C BSS VM Req uirements4 2 | |
222 | List of Fi gures | |
223 | Figure 21: CBSS New Processes and Intera ctions wit h Actors5 | |
224 | Figure 22: Consolida ted Billin g Statemen t Context Diagram8 | |
225 | Figure 23: Veteran A ddress - L ast Site V isited Rul es10 | |
226 | Figure 24: Two Facto r Authenti cation / A uthorizati on11 | |
227 | Figure 25: Generate, Process a nd Load FP S Data14 | |
228 | Figure 26: Generate CBS15 | |
229 | Figure 27: Update Pr int Acknow ledgement Status Scr een (No er rors)16 | |
230 | Figure 28: Update Pr int Acknow ledgment S tatus Scre en (File L evel Error )17 | |
231 | Figure 29: Update Pr int Acknow ledgement Status Scr een (Recor d Level Er rors)17 | |
232 | Figure 210 : Login Sc reen19 | |
233 | Figure 211 : View Bat ch Job Scr een19 | |
234 | Figure 212 : Configur e Batch Jo b screen20 | |
235 | Figure 213 : Sample F PS Batch J ob Status Screen20 | |
236 | Figure 214 : Run Conf irmation21 | |
237 | Figure 215 : CCPC Pat ient State ment Error s report – ran for o ne stateme nt date23 | |
238 | Figure 216 : CCPC Pat ient State ment Error s report – ran for a ll statem ent error dates24 | |
239 | Figure 217 : CBSS Tot als report – ran for a single summary to tal25 | |
240 | Figure 218 : CBSS - T otals repo rt – ran f or subtota ls by date , and gran d summary total25 | |
241 | Figure 219 : CBSS Mes sage Total s report – ran for a user sele cted date2 6 | |
242 | Figure 220 : Reprint Patient St atements m enu option 26 | |
243 | Figure 2-2 21: Auto-C orrection Batch Proc ess27 | |
244 | Figure 222 : CBSS Int erface41 | |
245 | ||
246 | Introducti on | |
247 | The remedi ation of t he Veteran s Health I nformation Systems T echnology Architectu re (VistA) Accounts Receivable (AR) proc ess is req uired to p rovide a c onsolidate d and easi ly readabl e patient statement from multi ple treatm ent facili ties durin g a monthl y cycle. E nhancement s to the A R system w ill increa se Veteran satisfact ion by mit igating co ncerns rai sed by Vet erans Serv ice Organi zations (V SO) and in dividual V eterans, w ho have pr ovided fee dback to t he Departm ent of Vet erans Affa irs (VA) r egarding p oor custom er service and poor business p ractices. Future dev elopment a ctivities are depend ent on Pha se 1 and P hase 2 enh ancements, as these enhancemen ts will de ploy best practices in financi al and bus iness proc esses, and align wit h the VA i nitiative to build V eterans Re cord Manag ement (VRM ) capabili ty to enab le conveni ent and se amless int eractions. | |
248 | The PSE pr oject incl udes 3 dev elopment p hases acro ss 5 incre ments. Pha se 1 will remediate existing p ayment cyc le deficie ncies and include an auto-corr ection job . Phase 1 will be co ded and in itial SQA testing wi ll be perf ormed in I ncrement 1 . Phase 1 final Soft ware Quali ty Assuran ce (SQA), User Funct ionality T esting (UF T), Initia l Operabil ity Capabi lity (IOC) , and depl oyment wil l be in In crement 3. | |
249 | Phase 2 in cludes the creation of the Con solidated Patient St atement. P hase 2 wil l be coded and initi al SQA tes ting will be perform ed in Incr ement 2. P hase 2 fin al SQA, UF T, IOC, an d deployme nt will be in Increm ent 3. | |
250 | Phase 3 in cludes mak ing the Co nsolidated Billing S tatement ( CBS) avail able on-li ne through the Healt heVet port al and rep orting cap abilities. Phase 3 w ill be cod ed and ini tial SQA t esting wil l be perfo rmed in In crement 4. Phase 3 f inal SQA, UFT, IOC, and deploy ment will be in Incr ement 5. | |
251 | Purpose | |
252 | The purpos e of this Requiremen ts Specifi cation Doc ument (RSD ) is to in troduce th e function al and tec hnical req uirements for Patien t Statemen t Enhancem ents (PSE) for Phase 2. The in tended aud ience for this docum ent are PS E Office o f Informat ion and Te chnology ( OI&T), the PSE Busin ess Requir ements Off ice, and o ther PSE s takeholder s. | |
253 | Scope | |
254 | This RSD f ocuses on the busine ss rules a nd require ments for Phase 2 de velopment. Items con sidered in scope for Phase 2 a re listed below: | |
255 | Enhance th e Auto-Cor rection Ba tch proces s to inclu de fixes f or the Mis sing amoun t discrepa ncies. The enhanceme nt detects the discr epancy and determine s the appr opriate do llar amoun t to use f or the Aut o-Correcti on logic w hen fixing missing a mount disc repancies. | |
256 | Enhance th e Auto-Co rrection B atch proce ss to incl ude fixes for Incomp lete trans actions fo r non-acti ve bills. | |
257 | Update the Decrease/ Increase A djustment menu optio n so that bill calcu lations do not creat e account out of bal ance discr epancies, This is do ne by corr ectly incl uding only incomplet e transact ions that should be considered for bill balance ca lculations . | |
258 | Create a c onsolidate d patient stamement across all VA Medica l Center ( VAMC) faci lities. Th e Consolid ated Billi ng Stateme nt System (CBSS) wil l create a Consolida ted Billin g Statemen t (CBS), a data file for each Veteran th at has vis ited one o r more of the 150 VA MC sites. CBSS will receive pa tient stat ement data from the 150 VAMC s ites and c ombine all of a Vete ran’s mont hly activi ty, includ ing VAMCs visited, c harges rel ated to ea ch visit, payments m ade toward debt and balance am ounts (pre vious bala nce, curre nt balance , and tota l amount d ue), and p ayment due date into a single monthly st atement. R eceiving s tatement d ata from t he VAMCs w ill be acc omplished through a scheduled batch proc ess. Once the CBS da ta file is created, it is sent to Austin Informati on Technol ogy Center (AITC) fo r formatti ng and sen t to the p rint vendo r for prin ting and m ailing. Wh en the AIT C has sent the print vendor th e statemen t print fi les, AITC/ CCPC will send print acknowled gement to CBSS for p rocessing of updates of the CB S status. | |
259 | Existing V istA AR re ports will be analyz ed and mod ified as n eeded to w ork with t he CBS pro cesses. | |
260 | Each VAMC will provi de CBSS wi th the old est bill b alance and amount fo r each Vet eran on a nightly ba sis. This informatio n will be used to de termine pa yment dist ribution. VistA AR w ill mainta in the abi lity for V istA AR us ers to pos t Veteran payments a t a site w here the c harge was incurred. Health Res ource Cent er (HRC) p ersonnel w ill contin ue to be a ble to pos t payments using pay .gov. CBSS will prov ide AITC/L ockbox the payment a llocation for Lockbo x payments . | |
261 | As-Is and To-Be anal ysis of pa yment proc essing (th e followin g interfac es will no t be enhan ced during the PSE p roject, bu t remain i n-scope fo r integrat ion and re gression t esting; to ensure th at current processes are not i mpacted ne gatively a nd continu e to work with the d evelopment of CBSS): | |
262 | Customer R elations M anagement (CRM) As-I s payment processing will rema in intact and not en hanced dur ing Phase 2 developm ent (see P erformance Work Stat ement (PWS ) requirem ent 5.12 i n section 2.7.4) | |
263 | Pay.gov As -Is paymen t processi ng will re main intac t and not enhanced d uring Phas e 2 develo pment. (Se e PWS 5.13 in sectio n 2.7.4) | |
264 | Treasury O ffset Prog ram (TOP) As-Is paym ent proces sing will remain int act and no t enhanced during Ph ase 2 deve lopment (s ee PWS 5.1 4 in secti on 2.7.4) | |
265 | Debt Manag ement Syst em (DMS) A s-Is payme nt will re main intac t and not enhanced d uring Phas e 2 develo pment (see PWS 5.15 in section 2.7.4) | |
266 | Consolidat ed Co-Paym ent Proces sing Cente r (CCPC) P rint Vendo r As-Is pr ocessing w ill remain intact an d not enha nced durin g Phase 2 developmen t (see PWS 5.16 in s ection 2.7 .4) | |
267 | Lockbox Ba nk of Amer ica As-Is payment pr ocessing ( on-line an d by mail) will rema in intact and not be enhanced during Pha se 2 devel opment (se e PWS 5.17 in sectio n 2.7.4) | |
268 | The Financ ial Manage ment Syste m (FMS) As -Is proces ses will n ot be enha nced durin g Phase 2 developmen t | |
269 | To-Be proc esses are introduced in sectio n 2.6 (see sections 2.6.1 thro ugh 2.6.9) | |
270 | Analysis o f the stat ement data transferr ed to AITC /CCPC. To- be Consoli dated Pati ent Statem ent file l ayout and additional technical requireme nts are av ailable in the Phase 2 System Design Doc ument (SDD ). | |
271 | Analysis a nd data ma pping of t he data tr ansferred to the CBS S. | |
272 | Out of Sc ope | |
273 | The follow ing PWS re quirements were dete rmined to be out of scope. | |
274 | PWS Refere nce | |
275 | Requiremen t Test | |
276 | Priority | |
277 | PWS 5.5.1 BN 3.1 | |
278 | The system shall ass ign a Vete rans Healt h Administ ration (VH A)-wide, u nique pati ent identi fier for e ach custom er. | |
279 | ||
280 | High | |
281 | PWS 5.5.1 BN 3.2 | |
282 | The system shall ass ess a sing le, monthl y administ rative cha rge for a Veteran’s delinquent account o n the cons olidated p atient sta tement. (C ontact Chi ef Busines s Office ( CBO) Reven ue regardi ng the pol icy) | |
283 | High | |
284 | PWS 5.5.1 | |
285 | BN 3.4 | |
286 | The system shall pro vide funct ionality t o ensure t hat paymen ts made by Veterans at a site are applie d to the a ppropriate charges r egardless of the VA facility a t which th e charge o riginated. This cove rs all pay ments and repayment plans made by Vetera ns in pers on at a VA facility. | |
287 | High | |
288 | PWS 5.5.1 BN 4.1 | |
289 | The system shall int erface wit h VistA AR to pass V HA-wide, u nique, ide ntifier to the Conso lidated Co -payment P rocessing Center (CC PC). | |
290 | High | |
291 | References | |
292 | The follow ing docume nts were u sed refere nce materi al for cre ating this RSD and T o-Be proce ss diagram s: | |
293 | Patient St atement En hancements (PSE) Pro ject Work Scope (PWS ), section 5.5 | |
294 | Agent Cash ier Manual , last upd ated May 2 015 | |
295 | AR User Ma nual, last updated M arch 1995 | |
296 | Lockbox Tr aining Gui de, revise d Septembe r 2007 | |
297 | CCPC LBX s ystem data flows | |
298 | Clerks AR Menu Part 1, last up dated May 2015 | |
299 | Clerks AR Menu Part 2, last up dated Nove mber 1994 | |
300 | MPI_PD Tec hnical Man ual, last updated Se ptember 20 15 | |
301 | MPI_PD Use r Manual, last updat ed Septemb er 2015 | |
302 | VA-Financi al Policy Volume XII Chapter01 A | |
303 | Overall De scription | |
304 | The VHA CB O is reque sting the developmen t of CBSS to capture , store, a nd to proc ess Facili ty Patient Statement (FPS) dat a received from all sites into a monthly CBS. The diagram be low provid es a high level over view of CB SS capabil ities, int erfacing s ystems, an d affected user grou ps. The bo x in the c enter of t he diagram illustrat es the CBS S, the blu e circles in the CBS S box are the high l evel capab ilities of this new system und er develop ment durin g PSE Phas e 2 (Load FPS data, Generate C BS, Manage Bill, Man age Batch, and Manag e ICN proc esses are the high-l evel capab ilities of CBSS). Th e actors t o the righ t and to t he left of the CBSS box illust rate the u ser groups and syste ms that ar e affected by the de velopment of the new system; t he actors to the lef t of the C BSS box wi ll provide CBS data to CBSS. T he actors to the rig ht of the CBSS box w ill receiv e CBS data and manag e schedule d job proc esses. | |
305 | The abilit y to View the CBS wi ll be deli vered thro ugh enhanc ements to the HRC/CC PC applica tion by th e HRC team . It is r epresented in the RS D for inte gration te sting. AI TC will be making ch anges to t he AITC/CC PC applica tion, in s upport of the CBS, t o provide the abilit y to send FPS files to CBSS. A ITC will a lso be mak ing change s to AITC/ Lockbox in order to receive a file of bi ll informa tion conta ining paym ent alloca tion for p atients th at visit m ultiple si tes. | |
306 | ||
307 | Figure 21: CBSS New Processes and Intera ctions wit h Actors | |
308 | The follow ing table provides a list of u ser roles that corre spond to e ach actor. | |
309 | Table 21: Actors and User Role s | |
310 | Actors | |
311 | User Roles | |
312 | AITC/Lockb ox | |
313 | System | |
314 | VAMC/ Vist A AR Users | |
315 | Agent cash iers Locat ed at the VAMC & Cas h Manageme nt (Consol idated Pat ient Accou nt Center (CPAC) | |
316 | ||
317 | Facility r evenue tec hnicians | |
318 | ||
319 | HRC | |
320 | ||
321 | Veteran Se rvice Tech nician – 1 st party a ccounts re ceivable | |
322 | (CPAC) | |
323 | ||
324 | Financial Services C enter (FSC ) Exceptio n Handling | |
325 | CRM Users | |
326 | Facility r evenue tec hnicians | |
327 | ||
328 | HRC | |
329 | Master Vet eran Index (MVI) | |
330 | System | |
331 | AITC/ CCPC | |
332 | System | |
333 | The follow ing table provides a brief des cription o f the acto rs that pl ay a role in the CBS S Processe s identifi ed in Figu re 1. | |
334 | Table 22: CBSS Actor Descripti ons | |
335 | Actors | |
336 | Descriptio n | |
337 | ||
338 | As-Is or T o-Be | |
339 | Lockbox | |
340 | First Part y Lockbox (LBX) supp orts the c entralized collectio n of check s and cred it card pa yments (ma il and on- line payme nts) at a lockbox ba nk (i.e., Bank of Am erica) and automates the steps necessary to apply those fund s to a pat ient’s acc ount that resides at the VAMCs . The lock box bank t ransmits t he payment transacti ons electr onically t o AITC/Loc kbox and t hese trans actions ar e distribu ted to the appropria te VAMC fo r automati c posting to the pat ient’s acc ount and s ubsequent reporting into the V A’s accoun ting syste m. | |
341 | If for som e reason a Lockbox p ayment can not be pro cessed as received, payment in formation is sent to the Excep tions Hand ling team to researc h and coor dinate res olution an d manual p ayment pos ting with VAMCs. | |
342 | As-Is | |
343 | VAMC/ Vist A AR Users | |
344 | There are 150 VA Med ical Cente rs located across th e U.S. The se facilit ies use th e VistA Ac counts Rec eivable (A R) applica tion to ma nage Veter an debt an d payment transactio ns. VistA AR is the authoritat ive data s ource for all Vetera n account informatio n. | |
345 | As-Is | |
346 | CRM Users | |
347 | The new CB S will be passed fro m AITC/CCP C to the H RC CCPC ap plication, which wil l render a PDF for v iewing in CRM. | |
348 | To-Be | |
349 | Master Vet eran Index (MVI) | |
350 | CBSS will register a n interest with MVI all new DF N/Site com binations. MVI will send CBSS a notifica tion when an ICN has been upda ted for an y DFN/ICN for which CBSS has a registere d interest . CBSS wil l retrieve the updat e from MVI through a HL7 inter face engin e (i.e., M IRTH) and update the Veteran r ecord with new ICN. | |
351 | To-Be | |
352 | AITC/Lockb ox | |
353 | AITC/Lockb ox receive s first pa rty lockbo x payments , and will receive p ayment all ocation fr om CBSS. A ITC/Lockbo x will the n distribu te payment s to the V AMCs. Lock box paymen ts that ca nnot be pr ocessed ar e sent to the Except ions Handl ing team f or researc h and effo rts to res olve error s are coor dinated wi th the VAM Cs. | |
354 | To-Be | |
355 | AITC/CCPC | |
356 | CBSS sends AITC/CCPC CBS data files. AIT C/CCPC con firms data was recei ved, forma ts data an d sends da ta to the print vend or for mai ling, and to HRC/CCP C for PDF generation and displ ay in CRM. AITC/CCPC sends pri nt acknowl edgement f iles to CB SS and VAM C (VistA). | |
357 | To-Be | |
358 | ||
359 | The follow ing table provides a brief des cription o f the CBSS processes identifie d in Figur e 1. | |
360 | Table 23: CBSS Capab ilities an d Brief De scriptions | |
361 | CBSS Capab ility | |
362 | Descriptio n | |
363 | As-Is or T o-Be | |
364 | Load FPS D ata | |
365 | This modul e provides the abili ty to rece ive and lo ad FPS dat a into CBS S. | |
366 | To-Be | |
367 | Generate C BS | |
368 | This modul e provides the abili ty to gene rate conso lidated pa tient stat ements. Du ring this process, C BSS will e xecute bus iness rule s to aggre gate trans actions an d calculat e totals t o format a CBS for e ach unique patient/u nique acco unt number . | |
369 | To-Be | |
370 | Send CBS | |
371 | This modul e provides the abili ty to crea te CBS dat a files an d send to AITC/CCPC. | |
372 | To-Be | |
373 | Manage Bil l | |
374 | This modul e provides the abili ty to rece ive and lo ad oldest bill infor mation fro m each VAM C and send the payme nt allocat ion to AIT C/Lockbox. | |
375 | To-Be | |
376 | Manage Bat ch | |
377 | This modul e provides the abili ty to view batch job s, configu re the sch eduling of a batch j ob, view j ob status, manually run a job, and view the status of a comp leted job. | |
378 | To-Be | |
379 | Manage ICN | |
380 | This modul e provides the abili ty to regi ster an in terest in ICN change s with MVI and recei ve updates of Vetera n identity from MVI. | |
381 | To-Be | |
382 | The follow ing diagra m depicts the contex t of inter actions of the syste ms, enviro nments, an d actors i nvolved in the CBS p rocesses. | |
383 | ||
384 | Figure 22: Consolida ted Billin g Statemen t Context Diagram | |
385 | Accessibil ity Specif ications | |
386 | The PSE pr oject will adhere to all Secti on 508 req uirements, which inc lude compl iance with the appli cable requ irements i n the VHA Section 50 8 checklis ts (1194.2 1, 1194.22 , 1194.24, 1194.31, and 1194.4 1) located at 508 Re sources Li nk or as o therwise s pecified. Establishe d checkpoi nts will e nsure that accessibi lity is in corporated from the earliest p ossible de sign or ac quisition phase and successful ly impleme nted throu ghout the project. | |
387 | The CBSS w ill includ e a new us er role fo r managing batch pro cesses and manually re-generat ing CBS da ta files. Section A. 11 CBSS Us er of this document defines th e role and responsib ilities of this new user. | |
388 | The table below defi nes the di fferent le vels of ac cess to vi ew the con solidated patient st atement (a s a form, or VistA A R data), a nd user ac cess to CB SS. | |
389 | Table 24 U ser Access to Consol idated Pat ient State ment | |
390 | Users | |
391 | Transactio ns or PDF Version | |
392 | Applicatio n | |
393 | Consolidat ed Stateme nt | |
394 | Transactio ns | |
395 | Agent cash iers Locat ed at the VAMC & Cas h Manageme nt (CPAC) | |
396 | Only users that can post payme nts | |
397 | Transactio ns | |
398 | VistA | |
399 | No | |
400 | Facility r evenue tec hnicians ( Located at a site) | |
401 | ||
402 | CRM | |
403 | Yes | |
404 | Health Res ource Cent er (HRC) | |
405 | ||
406 | CRM | |
407 | Yes | |
408 | Veteran Se rvice Tech nician – 1 st party a ccounts re ceivable | |
409 | (CPAC) | |
410 | Transactio ns | |
411 | VistA | |
412 | No | |
413 | FSC Except ion Handli ng | |
414 | Transactio ns | |
415 | VistA | |
416 | No | |
417 | ||
418 | Business R ules Speci fication | |
419 | This secti on identif ies the bu siness rul es for the PSE proje ct. | |
420 | CBS Person Traits | |
421 | CBSS shall use Perso n Traits f rom the FP S file wit h the most recent si te visited . Each VAM C will sen d CBSS the most rece nt Date Bi ll Prepare d (subject to change per VistA Maintenan ce Team re view) in t he FPS dat a. CBSS wi ll use thi s date to determine, across si tes, which one repre sents the most recen t Veteran activity. | |
422 | CBS Vetera n Mailing Address | |
423 | CBSS shall use the V eteran Mai ling Addre ss from th e FPS file with an A R Flag or the last s ite visite d on the C BS. CBSS w ill use th e most rec ent Date B ill Prepar ed (subjec t to chang e per Vist A Maintena nce Team r eview) fro m the FPS data to de termine th e site wit h the most recent Ve teran acti vity. CBSS will use the follow ing logic to determi ne the add ress. | |
424 | ||
425 | Figure 23: Veteran A ddress - L ast Site V isited Rul es | |
426 | CBSS Pay ment Distr ibution | |
427 | The CBSS s hall deter mine payme nt distrib ution acco rding to t he oldest debt. Each VAMC will calculate and send CBSS a nig htly updat e of the I CN, Site, DFN, oldes t debt bal ance and d ate. CBSS will then send AITC/ Lockbox th e payment allocation for each Veteran wh o has visi ted multip le sites, the oldest debt date will be u sed to det ermine the payment a llocation. The run f requency m ay be adju sted based on result s of perfo rmance tes ting. | |
428 | Multiple s ites will be based o n the Vete ran having billing i nformation from more than one site in th e nightly payment fi les. | |
429 | CBSS User Access | |
430 | The CBSS s hall requi re two fac tor login access usi ng the Per sonal Iden tity Verif ication (P IV). CBSS will inter face with the Identi ty and Acc ess servic es to auth enticate a nd authori ze access to the sys tem. | |
431 | ||
432 | Figure 24: Two Facto r Authenti cation / A uthorizati on | |
433 | Design Con straints S pecificati on | |
434 | PSE will a dhere to a ll technic al standar ds publish ed in VA H andbook 61 02, as wel l as all s ecurity st andards de scribed un der the Se curity Spe cification s section of this do cument. | |
435 | Proposed d esign of t he consoli dated pati ent statem ent will c omply with VistA, VH A Security , Privacy, Identity Management , business rules, an d function al and non -functiona l requirem ents addre ssed in th is documen t. | |
436 | The number of statem ents to be mailed du ring a mon th must no t exceed 1 10,000 a d ay, as it would impa ct HRCs ab ility to m anage call volume. | |
437 | Disaster R ecovery Sp ecificatio n | |
438 | The PSE de velopment team shall utilize t he existin g Disaster Recovery Plan for t he VistA A R applicat ion as the re are no changes to this plan for the P SE project . | |
439 | The PSE de velopment team shall document the Disast er Recover y Plan inc luding a r ollback st rategy pri or to depl oyment (se e enterpri se require ment below ). | |
440 | ENTR949 | |
441 | Applicatio ns shall d ocument a rollback s trategy pr ior to dep loyment. | |
442 | The PSE Di saster Rec overy Plan shall ide ntify the activities that are necessary to execute temporary informati on system processing capabilit ies, repai r damage t o the orig inal syste m, and res tore opera tional cap abilities at the ori ginal or n ew facilit y. Recover y strategi es will in clude the sequence o f activiti es as well as detail ed procedu res for th e technica l recovery of operat ions until the syste m can be r econstitut ed. | |
443 | In complia nce with t he require ments esta blished, t he system is classif ied as “es sential su pport” as defined in the AITC Disaster R ecovery Se rvices (Pe r AITC DR procedures this incl udes onsit e tape bac kup/restor e and Back up Server’ s for PSE- CBSS Produ ction Serv ers). PSE Team will work with AITC/Servi ce Deliver y and Engi neering (S DE) on the Applicati on Conting ency Plan maintained by CDCO, for specif ics on the Disaster Recovery ( DR), and h igh availa bility pro cedures. | |
444 | Documentat ion Specif ications | |
445 | PSE projec t document ation will comply wi th existin g PMAS pol icies and ProPath te mplates. P SE project documenta tion deliv erables ar e listed i n the PSE PWS. The P SE project requires updates to VistA doc uments and CBSS docu ments iden tified in the table below. | |
446 | Table 25 P SE Documen tation Req uirements | |
447 | Document | |
448 | Descriptio n | |
449 | VistA AR U ser Manual | |
450 | The VistA AR User Ma nual will be updated to reflec t enhancem ents made to the app lication. | |
451 | VistA AR T echnical M anual | |
452 | The VistA AR Technic al Manual will be up dated to r eflect enh ancements made to th e applicat ion. | |
453 | VistA AR S ecurity Gu ide | |
454 | The VistA AR Securit y Guide wi ll be upda ted to ref lect enhan cements ma de to the applicatio n. | |
455 | VistA AR I nstallatio n Guide | |
456 | The instal lation gui de will be updated t o include all requir ements ass ociated wi th initial installat ion/implem entation. | |
457 | VistA AR D eployment Plan | |
458 | A new Depl oyment Pla n will be created fo r VistA AR . | |
459 | VistA AR S ecurity Gu ide | |
460 | The Securi ty Guide w ill be upd ated to in clude all security r elated cha nges to Vi stA AR. | |
461 | VistA AR R elease Not es | |
462 | A new Rele ase Notes will be cr eated for VistA AR. | |
463 | CBSS User Manual | |
464 | A new User Manual wi ll be crea ted for CB SS. | |
465 | CBSS Secur ity Guide | |
466 | A new Secu rity Guide will be c reated for CBSS. | |
467 | CBSS Insta llation Gu ide | |
468 | A new inst allation g uide will be created for CBSS and includ e all tech nical and physical r equirement s for host ing, housi ng, operat ing and ma intaining the system hardware and softwa re, and al l requirem ents assoc iated with initial i nstallatio n/implemen tation. | |
469 | CBSS Deplo yment Plan | |
470 | A new Depl oyment Pla n will be created fo r CBSS. | |
471 | CBSS Secur ity Guide | |
472 | A new Secu rity Guide will be c reated for CBSS. | |
473 | CBSS Relea se Notes | |
474 | A new Rele ase Notes will be cr eated for CBSS. | |
475 | CBSS Produ ction Oper ations Man ual (POM) | |
476 | A new POM will be cr eated for CBSS. | |
477 | Functional Specifica tions | |
478 | This secti on introdu ces the ne w CBSS sys tem proces ses and Vi stA AR enh ancements to be impl emented du ring Phase 2 of the PSE projec t to suppo rt the fun ctionality to produc e a consol idated mon thly patie nt billing statement . | |
479 | Load FPS Data | |
480 | This CBSS process wi ll be a sc heduled ba tch job th at when tr iggered wi ll load th e FPS data from AITC /CCPC. Pri or to load ing the fi le, CBSS w ill perfor m basic va lidation t o ensure t he data is not corru pt or the file is no t empty. I t is assum ed that du plicate pa tient tran saction da ta is not received p er site. I f data val idation is successfu l, CBSS wi ll save th e data. If validatio n fails, a n error me ssage will be genera ted. A CBS S user wil l work wit h AITC to correct an d retransm it the fil e. Upon co mpletion o f the job an email n otificatio n will be sent to th e PII email dis tribution group alon g with a s uccess or failure sp ecific sub ject. The email will contain a list of a ll files p rocessed a nd their s tatus. The email sub ject and c ontent wil l be defin ed during developmen t. | |
481 | The follow ing figure illustrat es the pro cess by wh ich FPS da ta is sent from all 150 VAMC l ocations 1 5 – 20 tim es a month , accordin g to last name, to A ITC/CCPC f or process ing and va lidation t hen on to CBSS for l oading. | |
482 | ||
483 | Figure 25: Generate, Process a nd Load FP S Data | |
484 | Generate CBS | |
485 | This modul e provides the abili ty to gene rate conso lidated pa tient stat ements. Th e figure b elow illus trates the CBSS proc ess of cre ating the CBS. The p rocess beg ins when t he Generat e CBS batc h job is e xecuted. I t includes the busin ess logic to aggrega te and cal culate pat ient state ment trans actions in to a conso lidated mo nthly pati ent statem ent and st ored in th e database . The diag ram below depicts th e detailed process o f selectin g each new patient, consolidat ing that p atient’s d ata, stori ng it in t he databas e, and the n repeatin g the proc ess until no more ne w patients exist tha t need a c onsolidate d patient statement. | |
486 | CBSS will display a successful notice wh en the job is comple te. CBSS w ill displa y an error notificat ion if it is unab le to gene rate a CBS . Upon com pletion of the job a n email no tification will be s ent to the PII email dis tribution group alon g with a s uccess or failure sp ecific sub ject. The email will contain a count of statements processed and their status. T he email s ubject and content w ill be def ined durin g developm ent. | |
487 | ||
488 | Figure 26: Generate CBS | |
489 | ||
490 | Send CBS | |
491 | This modul e provides the abili ty to crea te CBS dat a files an d send the m to AITC/ CCPC. The process be gins when the Genera te CBS bat ch job is executed. Each CBS c reated in the Genera te CBS bat ch job wil l be selec ted and in serted int o a file l ocated on the FTP se rver for p ick up by AITC/CCPC. File size will be o ptimized d uring test ing. Once all availa ble CBS da ta has bee n written to a file, the job w ill save t he files t o the FTP server. | |
492 | Upon compl etion of t he job an email noti fication w ill be sen t to the DN S
|
|
493 | If an erro r occurs d uring the Send CBS p rocess, no files wil l be saved to the FT P server. CBSS will display an error not ification in the sta tus. | |
494 | When the S end CBS pr ocess is r an, CBSS w ill perfor m a check to see if the “Gener ate CBS" i s actively running. If the Gen erate CBS process is running, the Send C BS batch j ob will no t be start ed. CBSS w ill attemp t a re-sta rt every 1 5 minutes and will s top retryi ng after 2 hours. I f it stops due to th e 2 hour r etry timeo ut, CBSS w ill send a n email no tification to the di stribution group to notify tha t the job did not ru n and need s to be ma nually sta rted. | |
495 | Update Pri nt Acknowl edgment | |
496 | AITC/CCPC will send CBSS and V istA AR pr int acknow ledgements (received from the billing st atement pr int vendor ). CBSS wi ll load th e print ac knowledgem ent files received f rom AITC/C CPC and up date the C BS status to complet e for each statement in the re ceived fil e. | |
497 | The follow ing screen mockup pr ovides a v isual of w hat the CB SS Update Print Ackn owledgemen t status s creens may look like and are n ot intende d to repre sent the f inal appro ved screen layouts. | |
498 | ||
499 | ||
500 | Figure 27: Update Pr int Acknow ledgement Status Scr een (No er rors) | |
501 | ||
502 | ||
503 | Figure 28: Update Pr int Acknow ledgment S tatus Scre en (File L evel Error ) | |
504 | ||
505 | ||
506 | Figure 29: Update Pr int Acknow ledgement Status Scr een (Recor d Level Er rors) | |
507 | Manage Bi ll Data | |
508 | This modul e provides the abili ty to rece ive and lo ad oldest bill infor mation fro m each VAM C and send payment a llocations to AITC/L ockbox. | |
509 | Load Bill Data | |
510 | Each VAMC will send a nightly file of bi ll informa tion to CB SS. The fi le will co ntain the ICN, oldes t bill dat e, and old est bill a mount for each Veter an. CBSS w ill receiv e and load the data for each I CN. If an error occu rs during the proces s, CBSS wi ll display an error notificati on. Upon c ompletion of the job an email notificati on will be sent to t he DN S
|
|
511 | Validation s of the B ill Data f ile are id entified i n the Tabl e 26 below . If the file itsel f is corru pt or any validation fails in the Header record t hen the en tire file will be re jected and no data r ecords wil l be proce ssed. If a validatio n check in the detai l record f ails, only that spec ific recor d will be rejected. | |
512 | Table 26: Validation s for Bill Data File Load Proc ess | |
513 | Message He ader or De tail Recor d | |
514 | Field Name | |
515 | Validation s | |
516 | Header | |
517 | RECORD-TYP E | |
518 | Must be th e value “P U” | |
519 | Header | |
520 | TOT-NUM | |
521 | Not Null | |
522 | Max Length 10 | |
523 | Header | |
524 | FACILITY-N UM | |
525 | Not Null | |
526 | Max Length 5 | |
527 | Header | |
528 | PROCESS-DA TE | |
529 | Not Null | |
530 | Must be in MMDDYYYY format | |
531 | Detail | |
532 | RECORD-TYP E | |
533 | Must be th e value “P D” | |
534 | Detail | |
535 | ICN | |
536 | Not NullMa x Length 1 8 | |
537 | Detail | |
538 | ACCT-NUM | |
539 | Not NullMa x Length 1 9 | |
540 | Detail | |
541 | SUB-TOTAL | |
542 | Not Null | |
543 | Detail | |
544 | DATE-OLDES T-BILL | |
545 | Not NullMu st be in M MDDYYYY fo rmat | |
546 | Distribute Payment | |
547 | CBSS will send AITC/ Lockbox a nightly fi le of paym ent alloca tion for a ll Veteran s who have a balance greater t han zero. CBSS will use the ol dest bill date and a mount to g enerate th e payment allocation . If an er ror occurs during th e process, CBSS will display a n error no tification . Upon com pletion of the job a n email no tification will be s ent to the DN S
|
|
548 | Manage Ba tch | |
549 | This modul e provides the abili ty to view batch job s, configu re a batch job, view batch job status, m anually ru n a batch job, and v iew the st atus of a completed batch job. | |
550 | View Batch Jobs | |
551 | This proce ss assumes the CBSS user has s uccessfull y logged i nto the sy stem. Upon entering the system , CBSS dis plays the landing pa ge, which displays a list of a vailable b atch jobs and each b atch job s cheduled t ime, actua l run star t date/tim e, actual run end ru n date/tim e, and job status. | |
552 | The follow ing screen mockup pr ovides a v isual of w hat the CB SS Login s creen and View Batch Job scree ns may loo k like and are not i ntended to represent the final approved screen lay outs. | |
553 | ||
554 | Figure 210 : Login Sc reen | |
555 | ||
556 | Figure 211 : View Bat ch Job Scr een | |
557 | Configure Batch Job | |
558 | Each batch job can b e configur ed to run automatica lly on a d aily basis or manual ly. To con figure a b atch job, the CBSS U ser would select ‘Co nfig’ on t he appropr iate batch job to be configure d. If dail y is selec ted, the u ser must e nter a tim e the job will run. The follow ing screen mockup pr ovides a v isual of w hat the Co nfigure Ba tch Job sc reens may look like and is not intended to represe nt the fin al approve d screen l ayout. | |
559 | ||
560 | Figure 212 : Configur e Batch Jo b screen | |
561 | View Batch Job Statu s | |
562 | To view th e status o f a comple ted batch job, selec t the Comp lete statu s hyperlin k. The sys tem will d isplay the following Batch Job Status sc reen. The status scr een will h ave specif ic informa tion for e ach batch job as lis ted. | |
563 | ||
564 | Figure 213 : Sample F PS Batch J ob Status Screen | |
565 | Manually R un Batch J ob | |
566 | To view a manually r un batch j ob, select the Run h yperlink. The system will disp lay a conf irmation s creen veri fying the run. The c onfirmatio n screen w ill provid e the abil ity to con tinue and run the jo b or to ca ncel. Sele cting Cont inue will start the job and ma ke the Run hyperlink become un available for select ion. Selec ting Cance l will sto p the run action lea ving the R un hyperli nk availab le for sel ection. | |
567 | ||
568 | Figure 214 : Run Conf irmation | |
569 | Manage IC N | |
570 | CBSS will interact w ith Master Veteran I ndex (MVI) and Ident ity and Ac cess Manag ement Serv ices (IAM) in order to stay in synch wit h the Ente rprise uni que patien t identifi cation. MV I is the a uthoritati ve source for patien t identity data. It maintains identity d ata for pa tients acr oss VA sys tems, prov ides a uni que univer sal identi fier for e ach patien t, stores identity d ata as cor relations for each s ystem wher e a patien t is known , provides a probabi listic mat ching algo rithm, and includes the Master Patient I ndex (MPI) , Person S ervice Ide ntity Mana gement (PS IM), and T oolkit (TK ). | |
571 | CBSS will subscribe to an MVI service wh ich will n otify CBSS whenever a change i s made to a patient’ s identity trait(s) (merged wi th another ICN, etc. ). This w ill enable CBSS to p erform app ropriate p atient ide ntity acti ons, and e nsure that CBSS pati ent identi fication i s in sync with VistA sites and other Ent erprise pr ocessing. CBSS shall utilize t he MVI dec entralized hybrid in tegration pattern an d shall st ore/mainta in the ICN as a trai t of the M VI Correla ted identi fier, subs cribe to M VI mainten ance messa ges, and s ubscribe t o/process the same M VI ICN not ifications as VistA. CBSS will follow IA M guidelin es for int eracting w ith MVI. | |
572 | Generate FPS (VistA AR) | |
573 | The VistA AR stateme nt generat ion proces s will be enhanced t o add addi tional att ributes to the FPS f ile. The additional attribute s are requ ired to su pport the production of consol idates mon thly bill ing statem ents and a re defined in Table 26. The s tatement g eneration process wi ll be modi fied to ru n 16 times a month a nd will pr oduce stat ement data based on the patien t’s last n ame as def ined in Ta ble 2-7. Tables out lining the new FPS a ttributes and the br eakdown of the proce ssing sche dule are s hown below . | |
574 | Table 27: New Attrib utes Added to The FP S File | |
575 | New Field | |
576 | Descriptio n | |
577 | ICN | |
578 | Patient Id entifier ( Integrated Control N umber) | |
579 | ICN Checks um | |
580 | Validation Identifie r for the ICN | |
581 | AR Flag | |
582 | Indicates if the Pat ient’s add ress was p ulled from the VistA billing f ile (If th e AR Flag is Yes, th en the add ress is fr om the Vis tA file, o therwise, the addres s is from the Patien t File.) | |
583 | Last Bill Prepared D ate | |
584 | The date o f the last (most rec ent) charg e made to the Patien t | |
585 | Table 28: Modified S chedule fo r FPS File Generatio n by Patie nt Last Na me | |
586 | Day of the Month | |
587 | Last Name Beginnings With | |
588 | 1 | |
589 | A,BA,BU | |
590 | 2 | |
591 | B (EXCLUDE BA,BU) | |
592 | 4 | |
593 | CI,CR,CU,D | |
594 | 6 | |
595 | C (EXCLUDE CI,CR,CU) | |
596 | 7 | |
597 | E,F,I,Q | |
598 | 8 | |
599 | G,HE | |
600 | 10 | |
601 | H (EXCLUDE HE) | |
602 | 12 | |
603 | J,K | |
604 | 14 | |
605 | L,O | |
606 | 15 | |
607 | M (EXCLUDE MC,MI) | |
608 | 17 | |
609 | MC,MI,N,TI -TZ | |
610 | 19 | |
611 | R,TA-TE | |
612 | 21 | |
613 | S (EXCLUDE SC,SH,SI, SM) | |
614 | 22 | |
615 | SC,SH,SI,S M,V,TF-TH | |
616 | 24 | |
617 | P,U,X,Y,Z | |
618 | 26 | |
619 | W | |
620 | Send Night ly Bill In formation | |
621 | Each VAMC will gener ate and se nd a night ly file of bill info rmation to CBSS. The file will contain t he ICN, ol dest bill date, and oldest bil l amount f or each Ve teran. Th e data lay out of the file is d ocumented in the Pay ment Updat e Data Lay out Design document (Data_Layo ut_Payment _Update_VA MC_To_CBSS .docx). | |
622 | Enhance Vi stA AR Rep orts | |
623 | Three exis ting VistA AR report s have bee n identifi ed that re quire modi fication t o accommod ate the ne w processi ng schedul e for the generation of the pa tient stat ement data files. T he three r eports inc lude the f ollowing: | |
624 | CCPC State ment Error s Report | |
625 | CCPC Total s Report | |
626 | Reprint Pa tient Stat ements | |
627 | All three reports ar e found by navigatin g to the C lerk’s AR Menu and t hen the Fo llow-up Le tter Menu . | |
628 | CCPC State ment Error s Report | |
629 | The CCPC S tatement E rrors repo rt will be updated t o report o n statemen t errors b ased on th e new 16-d ay cycle, which star ts the fir st of the month rath er than th e current full-month monthly c ycle. Th e VistA AR user will be presen ted with a new optio n to run t he report for any da te on whic h there ar e error co des, or ru n the repo rt for all dates on which erro r codes ex ist. | |
630 | ||
631 | Figure 215 : CCPC Pat ient State ment Error s report – ran for o ne stateme nt date | |
632 | ||
633 | ||
634 | Figure 216 : CCPC Pat ient State ment Error s report – ran for a ll statem ent error dates | |
635 | CCPC Total s Report | |
636 | The CCPC T otals repo rt will be updated t o report o n statemen t totals b ased on th e newly mo dified 16- day cycle which star ts the fir st day of the month rather tha n the curr ent full-m onth month ly cycle. The report can be ra n for a si ngle summa ry total, subtotals by date, o r a single user sele cted date. | |
637 | ||
638 | Figure 217 : CBSS Tot als report – ran for a single summary to tal | |
639 | ||
640 | Figure 218 : CBSS - T otals repo rt – ran f or subtota ls by date , and gran d summary total | |
641 | ||
642 | Figure 219 : CBSS Mes sage Total s report – ran for a user sele cted date | |
643 | Reprint Pa tient Stat ements | |
644 | The Reprin t Patient Statement menu optio n will all ow all sta tements to be reprin ted based on the new ly modifie d 16-day c ycle which starts th e first da y of the m onth rathe r than the current f ull-month monthly cy cle. | |
645 | ||
646 | ||
647 | Figure 220 : Reprint Patient St atements m enu option | |
648 | Enhance Au to-Correct ion Proce ssing Log ic | |
649 | When proce ssing cond itions res ult in eit her a miss ing transa ction amou nt or inco mplete tra nsaction d iscrepancy for an ac count that is report ed as out- of-balance , the Auto -Correctio n process logic show n in Figur e 2-17 wil l amend pr ocessing r esults to make the o verall acc ount balan ce equal t he Patient Statement balance. All transa ction type s, except for the “C omment Tra nsaction” will be co nsidered w hen correc ting proce ssing resu lts for th e discrepa ncies. | |
650 | The enhanc ement to t he Auto-Co rrection p rocessing logic will consider non-active bills tha t affect o verall acc ount balan ce for bot h incomple te transac tion and m issing amo unt transa ction disc repancies. The enh ancement w ill also i nclude the appropria te calcula tion to be performed to determ ine the ap propriate transactio n amount w hen fixing missing a mount tran saction di screpancie s. | |
651 | ||
652 | ||
653 | Figure 2-2 21: Auto-C orrection Batch Proc ess | |
654 | Enhance th e Increase /Decrease Adjustment Menu Opti on | |
655 | The Decrea se/Increas e Adjustme nt menu op tion in Vi stA AR cal culates th e Bill Bal ance incor rectly in that it in cludes any and all t ransaction s flagged as incompl ete includ ing those marked as incomplete by the Au to-Correct ion Proces s. | |
656 | The enhanc ement to t he Decreas e/Increase Adjustmen t menu opt ion logic that calcu lates bill balance w ill consid er only in complete t ransaction that shou ld be incl uded in th e bill’s o verall bal ance. | |
657 | Functional Requireme nts | |
658 | Phase 2 de velopment culminates with the developmen t of proce sses, feat ures and d ata necess ary to gen erate a si ngle month ly consoli dated pati ent statem ent. Table 2-9 inclu des the fu nctional r equirement s necessar y to imple ment the c apabilitie s identifi ed in Sect ion 2.6 to generate consolidat ed patient statement s and dist ribute pay ments. In order to p rovide tra ceability across pro ject artif acts, the following section is organized by the Bu siness Nee d identifi ed in the PSE PWS an d the capa bilities i dentified in Section 2. | |
659 | Table 29 C BS Functio nal Requir ements | |
660 | PWS Ref | |
661 | BN | |
662 | Item | |
663 | Type | |
664 | Business N eed | |
665 | PWS 5.5.1 | |
666 | BN 2 | |
667 | ||
668 | ||
669 | Create the foundatio n of a con solidated patient st atement. | |
670 | ||
671 | BN 2.1 | |
672 | ||
673 | ||
674 | Analyze an d design t he foundat ion softwa re and pro cesses for the creat ion of a c onsolidate d patient statement. | |
675 | ||
676 | BN 2.2 | |
677 | ||
678 | ||
679 | Create the prelimina ry feature s of an in itial syst em contain ing a mont hly consol idated pat ient state ment that reflects a ctivity th roughout t he VA syst em. | |
680 | ||
681 | BN 3 | |
682 | ||
683 | ||
684 | Consolidat e patient statement( s) within a single b illing cyc le. | |
685 | ||
686 | BN 3.3 | |
687 | ||
688 | ||
689 | The system shall gen erate a co nsolidated statement combining all activ e outstand ing accoun t charges (regardles s of the V A facility ) based on the Veter an's billi ng cycle. | |
690 | ||
691 | BN 7 | |
692 | ||
693 | ||
694 | The system shall emp loy PIV 2 Factor Aut henticatio n for appl ication ac cess and s ecurity. | |
695 | ||
696 | ||
697 | 1.0.0 | |
698 | Epic | |
699 | Load FPS D ata | |
700 | ||
701 | BN 2.2, 4 | |
702 | 1.1.0 | |
703 | User Story | |
704 | As a VistA user, I w ant FPS da ta sent to CBSS so t hat facili ty patient statement transacti ons can be consolida ted into a single pa tient stat ement. | |
705 | ||
706 | BN 2.1, 4 | |
707 | 1.1.1 | |
708 | Req | |
709 | Each VAMC shall send FPS data to CBSS 1 6 times a month. Eac h transmis sion will contain a set of Vet erans base d on last name. (Se e the Tabl e 28.) | |
710 | Note: It i s assumed that dupli cate patie nt stateme nt data is not sent per site. | |
711 | ||
712 | BN 2.2, 4 | |
713 | 1.1.2 | |
714 | Req | |
715 | The FPS da ta file sh all be enh anced to i nclude new data elem ents. (CBS file layo ut can be found in t he Phase 2 SDD.) (T he new dat a elements are ident ified in t he Table 2 7 in this RSD.) | |
716 | ||
717 | BN 2.2, 4 | |
718 | 1.1.3 | |
719 | Req | |
720 | If the ICN is null i n the FPS file, a Ma ilman mess age will b e sent in order to i dentify th e records contains t he null IC N. | |
721 | ||
722 | BN 2.2, 4 | |
723 | 1.1.4 | |
724 | Req | |
725 | Each VAMC shall send bill data to CBSS. (See the section in the RSD “ Send Night ly Bill In formation” .) | |
726 | ||
727 | BN 2.2, 4 | |
728 | 1.1.5 | |
729 | Req | |
730 | CBSS will perform va lidations on the bil l data fil e. (See t he table “ Validation s for Upda te Bill Da ta Routine ” in this RSD.) | |
731 | ||
732 | BN 2.2, 4 | |
733 | 1.1.6 | |
734 | Req | |
735 | If a valid ation chec k of the b ill data f ile fails, the speci fic record that fail s will be rejected. | |
736 | ||
737 | BN 2.2, 4 | |
738 | 1.1.7 | |
739 | Req | |
740 | If the bil l data fil e itself i s corrupt, the entir e file wil l be rejec ted and no data reco rds contai ned in the file will be proces sed. | |
741 | ||
742 | BN 2.4, 4 | |
743 | 1.2.0 | |
744 | User Story | |
745 | As a CBSS user, I wa nt FPS dat a files pr ocessed by CBSS so t hat facili ty patient statement transacti ons can be consolida ted into a single pa tient stat ement. | |
746 | ||
747 | BN 2.2, 4 | |
748 | 1.2.1 | |
749 | Req | |
750 | CBSS shall have an a utomated b atch job t o load and store FPS data file s from eac h VAMC sit es. | |
751 | ||
752 | BN 2.2, 4 | |
753 | 1.2.2 | |
754 | Req | |
755 | CBSS shall create a unique pat ient accou nt number for each V eteran. | |
756 | ||
757 | BN 2.1, 4 | |
758 | 1.2.3 | |
759 | Req | |
760 | CBSS shall capture a nd store t he status of the bat ch job. | |
761 | ||
762 | BN 2.2, 4 | |
763 | 1.2.4 | |
764 | Req | |
765 | CBSS shall capture t he date an d time eac h file is loaded. | |
766 | ||
767 | BN 2.2, 4 | |
768 | 1.2.5 | |
769 | Req | |
770 | CBSS shall capture t he process ing status and/or er ror reason of failur e for each FPS file. | |
771 | ||
772 | BN 2.2, 4 | |
773 | 1.2.6 | |
774 | Req | |
775 | CBSS shall send an e mail notif ication up on complet ion of the batch job to the CB SSMonitori ng email d istributio n group. | |
776 | ||
777 | ||
778 | 2.0.0 | |
779 | Epic | |
780 | Generate C BS | |
781 | ||
782 | BN 2.1, 3. 3 | |
783 | 2.1.0 | |
784 | User Story | |
785 | As a CBSS user, I wa nt the abi lity to ag gregate an d calculat e FPS so t hat a CBS can be gen erated. | |
786 | ||
787 | BN 2.1, 3. 3 | |
788 | 2.1.1 | |
789 | Req | |
790 | CBSS shall aggregate and calcu late patie nt account balances for transa ctions tha t occurred across VA MCs during the patie nt’s billi ng cycle. Patient ac count bala nce includ es: Previo us Balance (unpaid t ransaction s from pre vious stat ements), C urrent Bal ance (char ges minus payments r eceived du ring the c urrent sta tement cyc le), and T otal Balan ce (combin es Previou s Balance and Curren t Charge a mounts). | |
791 | ||
792 | BN 2.1, 3. 3 | |
793 | 2.1.2 | |
794 | Req | |
795 | CBSS shall prefix th e Veterans ’s primary site DFN followed b y the firs t 5 charac ters of th e Veteran last name as the acc ount numbe r on the C BS. | |
796 | ||
797 | BN 2.1, 3. 3 | |
798 | 2.1.3 | |
799 | Req | |
800 | CBSS shall use the P erson Trai ts from th e FPS data with the most recen t visit da te. | |
801 | ||
802 | BN 2.1, 3. 3 | |
803 | 2.1.4 | |
804 | Req | |
805 | CBSS shall use the V eteran add ress from the FPS da ta with th e most rec ent visit date. | |
806 | ||
807 | BN 2.1, 3. 3 | |
808 | 2.1.5 | |
809 | Req | |
810 | CBSS shall use the S ite Id and Address f rom the FP S data wit h the most recent vi sit date. | |
811 | ||
812 | BN 2.1, 3. 3 | |
813 | 2.1.6 | |
814 | Req | |
815 | CBSS shall use the S tatement C ycle Date from the F PS data wi th the mos t recent v isit date. | |
816 | ||
817 | BN 2.2, 3. 3 | |
818 | 2.1.7 | |
819 | Req | |
820 | CBSS shall capture a nd store t he status of the Gen erate CBS batch job. | |
821 | ||
822 | BN 2.2, 3. 3 | |
823 | 2.1.8 | |
824 | Req | |
825 | CBSS shall capture t he process ing status and/or er ror reason of failur e for each CBS. | |
826 | ||
827 | BN 2.2, 3. 3 | |
828 | 2.1.9 | |
829 | Req | |
830 | CBSS shall send an e mail notif ication up on complet ion of the batch job to the CB SS User gr oup email distributi on list. | |
831 | ||
832 | ||
833 | 3.0.0 | |
834 | Epic | |
835 | Send CBS | |
836 | ||
837 | BN 2.2, 3. 3 | |
838 | 3.1.0 | |
839 | User Story | |
840 | As a CBSS user, I wa nt the abi lity to cr eate and s end CBS fi les to AIT C/CCPC so that the C BS can be formatted and mailed to Vetera ns. | |
841 | ||
842 | BN 2.2, 3. 3 | |
843 | 3.1.1 | |
844 | Req | |
845 | CBSS shall have conf igurable b atch jobs to generat e and send CBS file( s) to AITC /CCPC. | |
846 | ||
847 | BN 2.2, 3. 3 | |
848 | 3.1.2 | |
849 | Req | |
850 | CBSS shall have the ability to send dail y CBS file s to AITC/ CCPC. | |
851 | For each C BS transmi ssion to A ITC, two f iles are s ent: | |
852 | The “P1” f ile includ es Veteran s who have statement data from only one site withi n the stat ement date range. | |
853 | The “Multi -Site” fil e includes Veterans who have s tatement d ata from t wo or more sites wit hin the st atement da te range. | |
854 | For the Mu lti-Site f ile, the d ata is sor ted so tha t the prim ary site d ata is fir st to allo w printing of the pr imary site transacti on data at the top o f Billing Statement’ s transact ion detail section. The file is sorted further al phabetical ly by site name for all other site data. | |
855 | ||
856 | BN 2.2, 3. 3 | |
857 | 3.1.3 | |
858 | Req | |
859 | AITC/CCPC shall send CBSS ackn owledgemen t of CBS. | |
860 | ||
861 | BN 2.2, 3. 3 | |
862 | 3.1.4 | |
863 | Req | |
864 | CBSS shall have the ability to receive c onsolidate d acknowle dgements f rom AITC. | |
865 | ||
866 | BN 2.2, 3. 3 | |
867 | 3.1.5 | |
868 | Req | |
869 | CBSS shall have the ability to translate consolida ted acknow ledgements into indi vidual VAM C acknowle dgements a nd then se nd to AITC /CCPC for distributi on to VAMC s. | |
870 | ||
871 | BN 2.2, 3. 3 | |
872 | 3.1.6 | |
873 | Req | |
874 | AITC/CCPC shall have the abili ty to rece ive and di stribute s ite acknow ledgements to each V AMC. | |
875 | ||
876 | BN 2.2, 3. 3 | |
877 | 3.1.7 | |
878 | Req | |
879 | VistA AR s hall have the abilit y to recei ve site ac knowledgem ents from AITC/CCPC. | |
880 | ||
881 | BN 2.2, 4 | |
882 | 3.1.8 | |
883 | Req | |
884 | CBSS shall capture a nd store t he status of the bat ch job. | |
885 | ||
886 | BN 2.2 | |
887 | 3.1.9 | |
888 | Req | |
889 | CBSS shall capture t he process ing status and/or er ror reason of failur e. | |
890 | ||
891 | BN 2.2 | |
892 | 3.1.10 | |
893 | Req | |
894 | CBSS shall send an e mail notif ication up on complet ion of the batch job to the CB SS User gr oup email distributi on list. | |
895 | ||
896 | BN 2.2 | |
897 | 3.1.11 | |
898 | Req | |
899 | CBSS shall identify when a sec ond CBS ha s been cre ated (for a Veteran for the mo nth) so th at AITC/CC PC can add an explan ation mess age to the statement . | |
900 | ||
901 | BN 2.2 | |
902 | 3.1.12 | |
903 | Req | |
904 | CBSS shall send an e mail notif ication wh en an erro r occurs i n the prin t acknowle dgement fi les. | |
905 | ||
906 | BN 2.2 | |
907 | 3.1.13 | |
908 | Req | |
909 | VistA AR s hall have the abilit y to updat e the stat ement run date for s ites that run at the end of th e month so that Vete rans will not receiv e multiple statement s. | |
910 | ||
911 | BN2.2 | |
912 | 3.1.14 | |
913 | Req | |
914 | Whenever t he Send CB S job is s tarted, CB SS shall p erform a c heck to se e if the G enerate CB S job is a lready act ively runn ing. If t he Generat e CBS proc ess is run ning, the Send CBS b atch job w ill not be started. | |
915 | ||
916 | BN2.2 | |
917 | 3.1.15 | |
918 | Req | |
919 | When the S end CBS jo b does not initially start bec ause the G enerate CB S job is a ctively ru nning, CBS S shall re try a star t every 15 minutes a nd will st op retryin g after 2 hours. If the Send CBS stops due to the 2 hour re try timeou t, CBSS wi ll send an email not ification to the CBS S distribu tion group that the job did no t run and needs to b e manually started. | |
920 | ||
921 | ||
922 | 4.0.0 | |
923 | Epic | |
924 | Manage Bil l | |
925 | ||
926 | BN 3.3, 4 | |
927 | 4.1.0 | |
928 | User Story | |
929 | As a CBSS user, I wa nt ICN, ol dest bill balance an d date sen t from eac h VAMC to CBSS so th at CBSS ca n determin e payment allocation . | |
930 | ||
931 | BN 3.3, 4 | |
932 | 4.1.1 | |
933 | Req | |
934 | CBSS shall have an a utomated n ightly bat ch job to load and s tore bill data from each VAMC. | |
935 | ||
936 | BN 3.3, 4 | |
937 | 4.1.2 | |
938 | Req | |
939 | CBSS shall capture a nd store t he status of the fil e processe d by the P rocess Bil l Data bat ch job. | |
940 | ||
941 | BN 3.3, 4 | |
942 | 4.1.3 | |
943 | User Story | |
944 | CBSS shall capture a nd store t he status of the bat ch job. | |
945 | ||
946 | BN 3.3, 4 | |
947 | 4.1.4 | |
948 | User Story | |
949 | CBSS shall capture t he process ing status and/or er ror reason of failur e. | |
950 | ||
951 | BN 3.3, 4 | |
952 | 4.1.5 | |
953 | User Story | |
954 | CBSS shall send an e mail notif ication up on complet ion of the batch job to the CB SS User gr oup email distributi on list. | |
955 | ||
956 | BN 3.3, 4 | |
957 | 4.2.0 | |
958 | User Story | |
959 | As a Vista user, I w ant to sen d a nightl y file of ICN, oldes t bill bal ance and d ate so tha t CBSS can correctly determine payment a llocation. | |
960 | ||
961 | BN 3.3, 4 | |
962 | 4.2.1 | |
963 | Req | |
964 | CBSS shall send AITC /Lockbox a nightly f ile of pay ment alloc ation for all Vetera ns who hav e a bill b alance gre ater than zero. | |
965 | ||
966 | ||
967 | 5.0.0 | |
968 | Epic | |
969 | Manage Bat ch Jobs | |
970 | ||
971 | BN 2.2 | |
972 | 5.1.0 | |
973 | User Story | |
974 | As a CBSS user, I ne ed the abi lity to vi ew batch j ob informa tion so th at CBS fil es can be effectivel y managed. | |
975 | ||
976 | BN 2.2 | |
977 | 5.1.1 | |
978 | Req | |
979 | CBSS shall provide t he ability to view t he status of each ba tch job. | |
980 | ||
981 | BN 2.2 | |
982 | 5.1.2 | |
983 | Req | |
984 | CBSS shall provide t he ability to view t he batch j ob start a nd end dat e/time. | |
985 | ||
986 | BN 2.2 | |
987 | 5.1.4 | |
988 | Req | |
989 | CBSS shall provide t he ability to view t he status of a compl eted job. | |
990 | ||
991 | BN 2.2 | |
992 | 5.2.0 | |
993 | User Story | |
994 | As a CBSS user, I ne ed the abi lity to co nfigure a batch job so that CB S files ar e processe d correctl y. | |
995 | ||
996 | BN 2.2 | |
997 | 5.2.1 | |
998 | Req | |
999 | CBSS shall provide t he ability to config ure a job to be run manually o r automati cally dail y on a spe cific time . | |
1000 | ||
1001 | BN 2.2 | |
1002 | 5.2.2 | |
1003 | Req | |
1004 | CBSS shall store the date/time and user modifying the batch job. | |
1005 | ||
1006 | BN 2.2 | |
1007 | 5.3.0 | |
1008 | User Story | |
1009 | As a CBSS user, I ne ed the abi lity manua lly run a batch job so that CB S files ar e processe d correctl y. | |
1010 | ||
1011 | BN 2.2 | |
1012 | 5.3.1 | |
1013 | Req | |
1014 | CBSS shall provide t he ability to manual ly run a b atch job. | |
1015 | ||
1016 | BN 7 | |
1017 | 5.4.0 | |
1018 | User Story | |
1019 | As a CBSS User, I wa nt the sys tem to req uire two f actor auth entication (i.e., PI V card and PIN) and authorizat ion throug h the IAM Provisioni ng service s so that only autho rized user s are succ essfully l ogged in a nd granted access to CBSS. | |
1020 | ||
1021 | ||
1022 | 6.0.0 | |
1023 | Epic | |
1024 | Manage ICN | |
1025 | ||
1026 | BN 2.1, 4 | |
1027 | 6.1.0 | |
1028 | User Story | |
1029 | As a CBSS user, I wa nt to upda te an ICN for a Vete ran when i t is chang ed by MVI so that Ve terans are uniquely identified by the co rrect ICN in CBSS. | |
1030 | ||
1031 | BN 2.1, 4 | |
1032 | 6.1.1 | |
1033 | Req | |
1034 | CBSS shall register all new si te and DFN combinati ons with M VI. | |
1035 | ||
1036 | BN 2.1, 4 | |
1037 | 6.1.2 | |
1038 | Req | |
1039 | CBSS shall receive a nd update ICN change s based on broadcast ICN updat es from MV I. | |
1040 | ||
1041 | BN 2.2 | |
1042 | 6.1.3 | |
1043 | Req | |
1044 | CBSS shall capture a nd store t he status of the bat ch job. | |
1045 | ||
1046 | BN 2.2 | |
1047 | 6.1.4 | |
1048 | Req | |
1049 | CBSS shall capture t he process ing status and/or er ror reason of failur e. | |
1050 | ||
1051 | BN 2.2 | |
1052 | 6.1.5 | |
1053 | Req | |
1054 | CBSS shall send an e mail notif ication up on complet ion of the batch job to the CB SS User gr oup email distributi on list. | |
1055 | ||
1056 | BN 2.2 | |
1057 | 6.1.6 | |
1058 | Req | |
1059 | CBSS shall retransmi t a regist er request every 24 hours unti l a respon se is rece ived. | |
1060 | ||
1061 | BN 2.2 | |
1062 | 6.1.7 | |
1063 | Req | |
1064 | CBSS shall inform th e CBSS Use r when no response i s received back from MVI to th e registra tion reque st. | |
1065 | ||
1066 | ||
1067 | 7.0.0 | |
1068 | Epic | |
1069 | View CBS | |
1070 | ||
1071 | BN 2.2 | |
1072 | 7.1.0 | |
1073 | User Story | |
1074 | As a CRM u ser, I wan t to view the consol idated pat ient state ment so th at I can r espond to patient in quiries re garding th eir bill. | |
1075 | ||
1076 | BN 2.1 | |
1077 | 7.1.1 | |
1078 | Req | |
1079 | CRM shall call CCPC to get the Veteran C BS PDF usi ng the DFN . | |
1080 | ||
1081 | BN 2.2 | |
1082 | 7.1.2 | |
1083 | Req | |
1084 | CCPC shall translate the CBS d ata to a P DF and sen d to CRM. | |
1085 | ||
1086 | ||
1087 | 8.0.0 | |
1088 | Epic | |
1089 | Enhance Vi stA AR Rep ort Proces ses | |
1090 | ||
1091 | BN 2.2, 4 | |
1092 | 8.1.0 | |
1093 | User Story | |
1094 | As a VistA AR user, I want the reports t o reflect the new 16 -day trans mission cy cle so tha t I can ac curately v iew statem ent data e rrors and reprint st atements b ased on th e modified billing s tatement s chedule. | |
1095 | ||
1096 | BN 2.1 | |
1097 | 8.1.1 | |
1098 | Req | |
1099 | The CCPC S tatement E rrors repo rt in Vist A shall be updated t o reflect the new 16 -day proce ssing cycl e. | |
1100 | ||
1101 | BN 2.1 | |
1102 | 8.1.1.1 | |
1103 | Req | |
1104 | VistA AR s hall allow the CCPC Patient St atement Er rors repor t to run f or all dat es or for only one c alendar da te on whic h statemen t errors e xist. | |
1105 | ||
1106 | BN 2.1 | |
1107 | 8.1.1.2 | |
1108 | Req | |
1109 | When the V istA AR us er runs th e CCPC Pat ient State ment Error s report f or multipl e days, th e VistA AR system sh all allow the user t o continue or exit t he report display af ter each r eported da te is disp layed on t he screen. | |
1110 | ||
1111 | BN 2.1 | |
1112 | 8.1.1.3 | |
1113 | Req | |
1114 | When the V istA AR us er selects to run th e CCPC Sta tement Err ors report for a day on which no stateme nt errors exist, the system wi ll display the messa ge “There are no err or files f or that da te.” | |
1115 | ||
1116 | BN 2.1 | |
1117 | 8.1.2 | |
1118 | Req | |
1119 | The CCPC T otals repo rt in Vist A shall be updated t o reflect the new 16 -day proce ssing cycl e. | |
1120 | ||
1121 | BN 2.1 | |
1122 | 8.1.2.1 | |
1123 | Req | |
1124 | VistA AR s hall allow the CBSS Message To tals repo rt to be r un by thre e criteria : | |
1125 | A single s ummary tot al of all available statement message da tes | |
1126 | Subtotals for each a vailable s tatement m essage dat e, with a grand tota l of all d ates at th e end of t he report. | |
1127 | A single t otal for a user sele cted state ment messa ge date. | |
1128 | ||
1129 | BN 2.1 | |
1130 | 8.1.2.2 | |
1131 | Req | |
1132 | When the V istA AR us er selects to run th e CBSS Mes sage Total s report f or a day o n which no statement messages exist, the system wi ll display the messa ge “There are no rec ords for t hat date.” | |
1133 | ||
1134 | BN 2.1 | |
1135 | 8.1.3 | |
1136 | Req | |
1137 | The Reprin t Patient Statement report in VistA shal l be updat ed to refl ect the se lection of the repri nt dates b ased on th e modified 16-day pr ocessing c ycle. | |
1138 | ||
1139 | BN 2.1 | |
1140 | 8.1.3.1 | |
1141 | Req | |
1142 | VistA AR s hall allow the Repri nt Patient Statement s menu opt ion to run for any d ate in whi ch re-prin table pati ent statem ents exist for the V istA site. | |
1143 | NOTE: Pati ent Statem ents will be availab le for rep rint after a print a cknowledge ment has b een proces sed at the VistA sit e. | |
1144 | ||
1145 | BN 2.1 | |
1146 | 8.1.3.2 | |
1147 | Req | |
1148 | When the V istA AR us er selects to run th e Reprint Patient St atements m enu option for a day on which no re-prin table stat ements exi st, the sy stem will display th e message “No notifi cations se nt on that date”, th en the sys tem redisp lays the l ist of dat es availab le for re print. | |
1149 | ||
1150 | BN 2.1 | |
1151 | 8.1.4 | |
1152 | Req | |
1153 | The CCPC S tatement E rrors repo rt, CCPC T otal repor t and the Reprint Pa tient Stat ement repo rt shall n ot exceed 78 charact ers in wid th so that if queued to MailMa n or print ed in hard copy the report wil l render w ithout wra pping line s. | |
1154 | ||
1155 | ||
1156 | 9.0.0 | |
1157 | Epic | |
1158 | Manage Pri nt Acknowl edgement | |
1159 | ||
1160 | BN 2.4, 4 | |
1161 | 9.1.0 | |
1162 | User Story | |
1163 | As a CBSS user, I wa nt print v endor data files pro cessed by CBSS so th at CBSS ha s confirma tion that a Veteran’ s CBS is p rinted and mailed. | |
1164 | ||
1165 | BN 2.2, 4 | |
1166 | 9.1.1 | |
1167 | Req | |
1168 | CBSS shall have an a utomated b atch job t o validate , load, an d process print ackn owledgemen t data fil es receive d from AIT C/CCPC. | |
1169 | ||
1170 | BN 2.2, 4 | |
1171 | 9.1.2 | |
1172 | Req | |
1173 | CBSS shall capture t he process ing status and/or er ror reason of failur e for each print ack nowledgeme nt file. | |
1174 | ||
1175 | BN 2.2, 4 | |
1176 | 9.1.3 | |
1177 | Req | |
1178 | CBSS shall send an e mail notif ication up on complet ion of the batch job to the CB SSMonitori ng email d istributio n group. | |
1179 | ||
1180 | BN 2.2, 4 | |
1181 | 9.1.4 | |
1182 | Req | |
1183 | CBSS shall reject th e entire P rint Ackno wledgement file if a ny validat ion error occurs. | |
1184 | Table 210 Auto-Corre ction and Transactio n Discrepa ncy Fix Fu nctional R equirement s | |
1185 | PWS Ref | |
1186 | BN | |
1187 | Item | |
1188 | Type | |
1189 | Business N eed | |
1190 | ||
1191 | ||
1192 | US001 | |
1193 | User Story | |
1194 | As a user, I want th e Accounts Receivabl e applicat ion to det ect and co rrect acco unt balanc e discrepa ncies as p art of nor mal operat ions, so t hat I do n ot have to perform t he task ma nually. | |
1195 | ||
1196 | ||
1197 | ACJ007 | |
1198 | Req | |
1199 | If missing dollar am ounts in t he TRANS A MOUNT fiel d (#15) of the AR TR ANSACTION file (#433 ), for any transacti on type ot her than a “COMMENT TRANSACTIO N”, causes a patient ’s account to be out -of-balanc e, then th e Auto-Cor rection Jo b shall co rrect the out-of-bal ance by en tering the amount in the TRANS AMOUNT fi eld (#15). | |
1200 | See Append ix A - Mis sing Trans action Amo unt exampl e | |
1201 | ||
1202 | ||
1203 | ACJ015 | |
1204 | Req | |
1205 | If a trans action in the AR TRA NSACTION f ile (#433) has the I NCOMPLETE TRANSACTIO N FLAG fie ld (#10) s et to 1 fo r any tran saction ty pe other t han a “COM MENT TRANS ACTION” fo r a bill t hat is cur rently in a status o ther than ‘Active’ o r ‘Open’, and causes a patient ’s account to be out -of-balanc e, then th e Auto-Cor rection Jo b shall co rrect the out-of-bal ance condi tion by re placing th e value of 1 with a value of 0 in the IN COMPLETE T RANSACTION FLAG fiel d on the i ncomplete transactio n record. | |
1206 | ||
1207 | ||
1208 | ACR015 | |
1209 | Req | |
1210 | The Auto-C orrection Report sha ll be enha nced to tr ack and re port on Mi ssing Tran saction Am ount balan ce discrep ancies. | |
1211 | Note: The following AR VistA menu optio n runs the Auto-Corr ection Rep ort: Auto -Correct P atient Dis crepancy R eport | |
1212 | ||
1213 | ||
1214 | US008 | |
1215 | User Story | |
1216 | As a VistA AR user I want the ability to run the A uto-Correc tion Repor t sorted b y Auto-Cor rect reaso n so that I can quic kly identi fy the lis t of ‘Not Fixable’ b ills that need manua l interven tion to re solve. | |
1217 | ||
1218 | ||
1219 | US009 | |
1220 | User Story | |
1221 | As a VistA user, whe n I am man ually adju sting a AR bill (usi ng the ‘Ad justment t o an AR re cord’ menu option) I want the VistA AR s ystem to c alculate a nd update the bill’s balances correctly so that th e Veteran’ s monthly billing st atements a re not del ayed in th e normal m onthly pri nting proc ess. | |
1222 | ||
1223 | ||
1224 | AR001 | |
1225 | Req | |
1226 | When an AR bill’s tr ansaction total is c alculated to determi ne if the bill is in balance t he followi ng transac tions, if flagged as incomplet e, shall b e excluded from the calculated transacti on total ( all other incomplete transacti on’s shall be includ ed): | |
1227 | Decrease A djustment, when crea ted by the system fr om the Pre payment pr ocess. | |
1228 | Increase A djustment, when crea ted by the system fr om the Pre payment pr ocess. | |
1229 | Any transa ction mark ed as inco mplete by the Auto-C orrection Batch Job process. | |
1230 | Any transa ction that was manua lly flagge d as incom plete beca use it was identifie d as a dup licate. | |
1231 | ||
1232 | Non-Functi onal Requi rements | |
1233 | PWS Ref | |
1234 | BN | |
1235 | Item | |
1236 | Type | |
1237 | Business N eed | |
1238 | ||
1239 | ||
1240 | US010 | |
1241 | User Story | |
1242 | As a CBSS System Adm inistrator , I want t he CBSS sy stem to ar chive off billing da ta on a 16 rolling c ycle so th at the vol ume of CBS data in t he databas e and on t he server does not b ecome a pe rformance issue. | |
1243 | ||
1244 | ||
1245 | US011 | |
1246 | User Story | |
1247 | As a VistA FileMan u ser I want to see ac curate fie ld descrip tions in F ile #349 s o that I h ave access to usable descripti ons about the file’s data. | |
1248 | ||
1249 | ||
1250 | AR003 | |
1251 | Req | |
1252 | The correc t spelling of the wo rds “recip ients” and “acknowle dgement” s hall be up dated in t he FileMan descripti ons of the fields in node 349. 11,.01 and 349.151,. 01 respect ively. | |
1253 | Additional PWS Requi rements | |
1254 | The follow ing table provides P WS require ments that were iden tified for Phase 3. These requ irements w ere review ed with PS E Stakehol ders durin g the Requ irement El aboration Meeting he ld 10/26/2 015, durin g which it was deter mined to m ove these requiremen ts to Phas e 2, as in terface re quirements are part of Phase 2 developme nt. | |
1255 | Existing i nterfaces and proces ses betwee n AITC/CCP C, AITC/Lo ckbox, VAM C, FMS, TO P, DMC, an d CCPC wil l not be i mpacted du ring Phase 2 develop ment so th ey are out of scope for develo pment. How ever, thes e requirem ents are s till part of the ove rall end-t o-end stat ement proc ess and th erefore le ft in scop e from a t esting per spective t o ensure n o impact f rom the ch anges to e xisting fu nctionalit y. | |
1256 | Table 211 Additional Requireme nts | |
1257 | Req. ID | |
1258 | Primary Te xt | |
1259 | Requiremen t Status | |
1260 | 5.5 | |
1261 | Provide fu nctionalit y to allow and ensur e that pay ments can be made by Veterans by using a n online f eature (Pa y.gov). | |
1262 | Existing f unctionali ty and out of scope for develo pment acti vities how ever will need to be tested to ensure th ere are no impacts f rom the ne w system. | |
1263 | 5.13 | |
1264 | The system shall mai ntain exis ting inter faces with Pay.gov. | |
1265 | Existing f unctionali ty and out of scope for develo pment acti vities how ever will need to be tested to ensure th ere are no impacts f rom the ne w system. | |
1266 | 5.14 | |
1267 | The system shall mai ntain exis ting inter faces with Treasury Offset Pro gram (TOP) . | |
1268 | Existing f unctionali ty and out of scope for develo pment acti vities how ever will need to be tested to ensure th ere are no impacts f rom the ne w system. | |
1269 | 5.15 | |
1270 | The system shall mai ntain exis ting inter faces with 90-day De bt Managem ent Center (DMC). | |
1271 | Existing f unctionali ty and out of scope for develo pment acti vities how ever will need to be tested to ensure th ere are no impacts f rom the ne w system. | |
1272 | 5.16 | |
1273 | The system shall mai ntain exis ting inter faces with CCPC Prin t Contract or. | |
1274 | Existing f unctionali ty and out of scope for develo pment acti vities how ever will need to be tested to ensure th ere are no impacts f rom the ne w system. | |
1275 | 5.17 | |
1276 | The system shall mai ntain exis ting inter faces with Lockbox B ank of Ame rica. | |
1277 | Existing f unctionali ty and out of scope for develo pment acti vities how ever will need to be tested to ensure th ere are no impacts f rom the ne w system. | |
1278 | Graphical User Inter face (GUI) Specifica tions | |
1279 | Features a nd functio nality wit hin the ne w CBSS sha ll adhere to accessi bility, se curity and 508 compl iance stan dards. | |
1280 | Enhancemen ts made to VistA and CBSS user interface s shall ad here to cu rrent acce ssibility, security and 508 co mpliance s tandards. | |
1281 | Multi-divi sional Spe cification s | |
1282 | There are no new mul ti-divisio nal capabi lity requi rements of VistA AR. Changes i n support of CBSS mu st be seam less to al l VistA us ers and no n-disrupti ve to exis ting VistA AR functi onality. | |
1283 | Performanc e Specific ations | |
1284 | This secti on identif ies the dy namic nume ric specif ications r equired fo r CBSS, AR package a nd the num ber of use rs who int eract with the AR pa ckage. | |
1285 | CBSS will support th e current volume of two millio n statemen ts printed and sent to Veteran s. CBSS ar chitecture is design ed to supp ort an inc rease in n umber of V eteran sta tements to the month ly cycle ( with addit ion to CBS S infrastr ucture, th is capabil ity will b e benchmar ked during the Perfo rmance Tes ting phase of CBSS). | |
1286 | The CBSS w ill suppor t processi ng of at l east 150 F PS sites i n a 12-hou r period. | |
1287 | CBSS archi tecture is flexible to accommo date a 10% future gr owth in CB SS Applica tion usage . | |
1288 | Quality At tributes S pecificati on | |
1289 | Quality at tribute sp ecificatio ns will en hance the supportabi lity, main tainabilit y, portabi lity, test ability, a nd reusabi lity of th e VistA AR and CBSS. The enhan cements to VistA AR and develo pment of t he CBSS wi ll include applicabl e coding s tandards, naming con ventions, class libr aries, mai ntenance a ccess, and maintenan ce utiliti es. The qu ality attr ibutes spe cification s are achi eved by th e accepted design fo r VistA AR enhanceme nts and CB SS. | |
1290 | Reliabilit y Specific ations | |
1291 | CBSS shall be availa ble 24 hou rs per day , 365 days per year, except du ring perio ds of sche duled main tenance. T his projec t will not change or impact th e existing VistA AR package av ailability . | |
1292 | Scope Inte gration | |
1293 | Vista AR i s an exist ing packag e of VistA . The PSE project wi ll be maki ng enhance ments to t he VistA A R package. The enhan cements wi ll include changes t o the stat ement run process an d a new in terface to the CBSS system. Vi stA AR wil l send old est bill i nformation to CBSS. Existing a rchitectur e will be utilized f or sending FPS data to CBSS, a s well as receiving acknowledg ements fro m CBSS. | |
1294 | CBSS is a new system with inte rfaces to AITC/CCPC, AITC/Lock box, and M VI. The AI TC interfa ces will u se existin g infrastr ucture use d by VistA today sen ding and r eceiving s tatement a nd payment informati on. There will be on e new type of interf ace betwee n CBSS and MVI which will be i mplemented using MLL P protocol or SOAP ( as appropr iate for C BSS archit ecture in concurrenc e with MVI SME’s). P lease refe rence the below CBSS Interface Diagram f or more de tails on t he flow. | |
1295 | ||
1296 | Figure 222 : CBSS Int erface | |
1297 | Legend | |
1298 | ||
1299 | Security S pecificati ons | |
1300 | The enhanc ement to V istA AR an d developm ent of the CBSS will include n ecessary s tandards, procedures , and tech nical aspe cts of the solution required f or achievi ng system certificat ion and ac creditatio n. The des ign will a ddress con trols list ed in Fede ral Inform ation Proc essing Sta ndards (FI PS) PUB 20 0, Minimum Security Requiremen ts for Fed eral Infor mation and Informati on Systems . Addition al securit y specific ations inc luded in t he design will addre ss: | |
1301 | Compliance with stan dards and regulatory requireme nts publis hed in VA Handbook a nd Directi ve 6500: V eterans Af fairs Dire ctives > V A Handbook and Direc tive 6500. | |
1302 | Compliance with FIPS PUB 140-2 , Security Requireme nts for Cr yptographi c Modules, and for a ll voice a nd data tr affic encr yption: Co mputer Sec urity Divi sion > Pub lications > Federal Informatio n Processi ng Standar ds > FIPS PUB 140-2. | |
1303 | Additional ly, due to patient s afety cons iderations , data pro tection me asures suc h as backu p interval s and redu ndancy sha ll be cons istent wit h systems categorize d as criti cal. | |
1304 | System Fea tures | |
1305 | CBSS featu res are de fined in S ection 2.6 of this d ocument. | |
1306 | Usability Specificat ions | |
1307 | There are no changes to usabil ity specif ications f or VistA A R enhancem ents. PSE shall conf orm to the current u sability s tandards w ithin the AR package . | |
1308 | CBSS user interface designs wi ll be revi ewed by th e actual b usiness us ers early in design and develo pment to e nsure a hi gh level o f usabilit y. | |
1309 | Purchased Components | |
1310 | The CBSS s ystem will run on th e VA cloud -based env ironment. | |
1311 | CBSS hardw are archit ecture des ign will b e composed of Virtua l Machines (VM) base d and depl oyed on ha rdware at AITC data centers in a Virtual farm foll owing VA’s Cloud Fir st directi ve. The de ployment w ill have V M servers for sFTP, Proxy serv er for Loa d Balancin g, VM WebL ogic Appli cation ser vers for t he Applica tion Clust er, and Or acle Datab ase server s. | |
1312 | The CBSS a pplication server an d Oracle D atabase se rvers will run on an RHEL Ente rprise Edi tion platf orm. The R HEL versio n will con form to VA TRM. | |
1313 | CBSS-Web A pplication : will be hosted by WebLogic A pplication Server an d Oracle D atabase Se rver (with RHEL as o perating s ystem). | |
1314 | Internal S ystem Inte rfaces: | |
1315 | CBSS-Web A pplication : Local VA MC (AR pac kage), AIT C (Lockbox etc.). | |
1316 | CBSS appli cation is in the ear ly design phase of i ts lifecyc le. The RS D will be signed off prior to MS1 and th e SDD is r eady for M S1 but wil l be updat ed through out the de velopment phase. | |
1317 | Table 31 o utlines th e Detail V M Requirem ents for d eploying C BSS applic ation. | |
1318 | Table 31 C BSS VM Req uirements | |
1319 | S.N0 | |
1320 | VM | |
1321 | Ram(GB) | |
1322 | OS Storage (GB) | |
1323 | Disk Stora ge (GB) | |
1324 | OS | |
1325 | CPUs | |
1326 | VM Descrip tion | |
1327 | 1 | |
1328 | 4 | |
1329 | 32 for eac h VM | |
1330 | Total=32x4 | |
1331 | 60x4 | |
1332 | 80x4 | |
1333 | RHEL- Linu x | |
1334 | 4x4 | |
1335 | WebLogic A pplication Server Cl uster (2 c lusters) t o Host CBS S applicat ion | |
1336 | 2 | |
1337 | 2 | |
1338 | 64x2 | |
1339 | 60x2 | |
1340 | 700x2 | |
1341 | RHEL- Linu x | |
1342 | 4x2 | |
1343 | Oracle Dat abase Serv er Cluster to Host C BSS applic ation Data base | |
1344 | 3 | |
1345 | 2 | |
1346 | 32x2 | |
1347 | 60 | |
1348 | 500x2 | |
1349 | RHEL-Linux | |
1350 | 4x2 | |
1351 | Red Hat Li nux (sFTP) Server. | |
1352 | 4 | |
1353 | 1 | |
1354 | 16 | |
1355 | 60 | |
1356 | 80 | |
1357 | RHEL- Linu x | |
1358 | 4 | |
1359 | Load Balan cer and Re verse Prox y | |
1360 | Note: The above requ irements w ill be fur ther refin ed during SEDR proce ss and wor king with AITC archi tects. CPU , RAM and disk space requireme nts will b e based on performan ce testing results r equired to attain th e SLA-dire cted throu ghput for number of concurrent users and transacti on respons e time. Ch anges may be made to these est imates as functional ity is add ed to the applicatio n and perf ormance te sting cont inues. | |
1361 | ||
1362 | Approval S ignatures | |
1363 | ||
1364 | REVIEW DAT E: | |
1365 | SCRIBE: | |
1366 | ||
1367 | Signed: | |
1368 | ||
1369 | __________ __________ __________ __________ __________ __________ __________ ________ | |
1370 | Integrated Project T eam (IPT) ChairDate | |
1371 | ||
1372 | __________ __________ __________ __________ __________ __________ __________ ________ | |
1373 | Business S ponsorDate | |
1374 | ||
1375 | __________ __________ __________ __________ __________ __________ __________ ________ | |
1376 | IT Program ManagerDa te | |
1377 | ||
1378 | __________ __________ __________ __________ __________ __________ __________ ________ | |
1379 | Project Ma nagerDate | |
1380 | ||
1381 | ||
1382 | Appendix | |
1383 | CBSS User | |
1384 | The CBSS U ser Role m ust be ful ly defined through c ollaborati on between OIT and t he Busines s. The fol lowing def inition wa s provided to OIT an d the Busi ness 12/3/ 2015 Requi rement Ela boration M eeting. | |
1385 | CBSS User Role: this role shal l have a g lobal view of the ge neration o f statemen ts. This p erson is l ogging in and managi ng the pro cess of st atements. This perso n does not need to b e technica l, but wil l log in t o make sur e schedule d processe s are exec uting corr ectly, rev iewing bat ch schedul e failures , and re-g enerating scheduled events tha t fail. | |
1386 | Will commu nicate wit h HPC when files fai l from VAM Cs (not re ceived or cannot be processed) | |
1387 | Will commu nicate wit h AITC whe n file tra nsmission errors occ ur | |
1388 | Identify i ssues or e nhancement s that nee d to be ma de to the CBSS syste m to corre ct or impr ove proces ses | |
1389 | Open chang e requests for issue s and/or e nhancement s | |
1390 | Work direc tly with C BSS applic ation owne r to resol ve issues, or develo pment proc ess improv ements |
Araxis Merge (but not the data content of this report) is Copyright © 1993-2016 Araxis Ltd (www.araxis.com). All rights reserved.