Produced by Araxis Merge on 10/5/2018 1:26:32 PM 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 | SHRPE_iter_1_build_4.zip | SHRPE_SDD_B2_v2.0.docx | Thu Oct 4 15:05:51 2018 UTC |
2 | SHRPE_iter_1_build_4.zip | SHRPE_SDD_B2_v2.0.docx | Fri Oct 5 16:59:34 2018 UTC |
Description | Between Files 1 and 2 |
|
---|---|---|
Text Blocks | Lines | |
Unchanged | 1 | 5258 |
Changed | 0 | 0 |
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 | Suicide Hi gh Risk Pa tient Enha ncements | |
2 | System Des ign Docume nt | |
3 | ||
4 | March 2018 | |
5 | Version 2. 0 | |
6 | Department of Vetera ns Affairs | |
7 | Revision H istory | |
8 | Date | |
9 | Version | |
10 | Descriptio n | |
11 | Author | |
12 | 03/19/18 | |
13 | 2.0 | |
14 | Build 2 Sp rint 1 ver sion | |
15 | Shavkat Sh amukhamedo v | |
16 | 12/21/17 | |
17 | 1.0 | |
18 | Initial ve rsion | |
19 | Shavkat Sh amukhamedo v | |
20 | Robert Kai ser | |
21 | Kristen Kr iwox | |
22 | Uma Karthi keyan | |
23 | Keri Vogtm ann (Revie wer) | |
24 | Artifact R ationale | |
25 | The System Design Do cument (SD D) is a du al-use doc ument that provides the concep tual desig n as well as the as- built desi gn. This d ocument wi ll be upda ted as the product i s built, t o reflect the as-bui lt product . | |
26 | Table of C ontents | |
27 | 1.Introduc tion8 | |
28 | 1.1.Patien t Record F lag Workst ream Scope 8 | |
29 | 1.2.Copaym ent Modifi cations Wo rkstream S cope9 | |
30 | 1.3.Other Than Disho norable Di scharge Mo dification s Workstre am Scope10 | |
31 | 1.4.User P rofiles10 | |
32 | 1.4.1.Pati ent Record Flag Work stream10 | |
33 | 1.4.2.Copa yment Modi fications Workstream 10 | |
34 | 1.4.3.Othe r Than Dis honorable Discharge Modificati ons Workst ream11 | |
35 | 2.Backgrou nd11 | |
36 | 2.1.Overvi ew of the System11 | |
37 | 2.1.1.Pati ent Record Flag Work stream11 | |
38 | 2.1.2.Copa yment Modi fications Workstream 12 | |
39 | 2.1.3.Othe r Than Dis honorable Discharge Modificati ons Workst ream13 | |
40 | 2.2.Overvi ew of the Business P rocess15 | |
41 | 2.2.1.Pati ent Record Flag Work stream15 | |
42 | 2.2.2.Copa yment Modi fications Workstream 15 | |
43 | 2.2.3.Othe r Than Dis honorable Discharge Modificati ons Workst ream17 | |
44 | 2.3.Overvi ew of Sign ificant Re quirements 19 | |
45 | 2.3.1.Over view of Fu nctional R equirement s19 | |
46 | 2.3.1.1.Pa tient Reco rd Flag Wo rkstream S cope19 | |
47 | 2.3.1.2.Co payment Mo dification s Workstre am Scope24 | |
48 | 2.3.1.3.Ab out OTH Mo dification s Workstre am Scope27 | |
49 | 2.3.2.Over view of Fu nctional W orkload/Pe rformance Requiremen ts29 | |
50 | 2.3.3.Over view of Op erational Requiremen ts29 | |
51 | 2.3.4.Over view of Te chnical Re quirements 29 | |
52 | 2.3.5.Over view of Se curity or Privacy Re quirements 29 | |
53 | 2.3.6.Over view of Sy stem Criti cality and High Avai lability R equirement s29 | |
54 | 2.3.7.Sing le Sign-on Requireme nts30 | |
55 | 2.3.8.Requ irement fo r Use of E nterprise Portals30 | |
56 | 2.3.9.Spec ial Device Requireme nts30 | |
57 | 3.Conceptu al Design3 0 | |
58 | 3.1.Concep tual Appli cation Des ign30 | |
59 | 3.1.1.Appl ication Co ntext30 | |
60 | 3.1.2.High -Level App lication D esign32 | |
61 | 3.1.2.1.PR F/TIU Work stream32 | |
62 | 3.1.2.2.Co payment Mo dification s Workstre am33 | |
63 | 3.1.2.3.Ot her than D ishonorabl e Discharg e Modifica tions Work stream34 | |
64 | 3.1.3.Appl ication Lo cations35 | |
65 | 3.2.Concep tual Data Design35 | |
66 | 3.2.1.Proj ect Concep tual Data Model35 | |
67 | 3.2.1.1.PR F/TIU work stream36 | |
68 | 3.2.1.2.Co pays Works tream36 | |
69 | 3.2.1.3.OT H Workstre am38 | |
70 | 3.2.2.Data base Infor mation38 | |
71 | 3.2.3.User Interface Data Mapp ing39 | |
72 | 3.2.3.1.Ap plication Screen Int erface39 | |
73 | 3.2.3.1.1. Patient Re cord Flag Workstream 39 | |
74 | 3.2.3.1.2. DGPF RECOR D FLAG ASS IGNMENT Sc reen41 | |
75 | 3.2.3.1.3. The Copaym ent Modifi cations Wo rkstream42 | |
76 | 3.2.3.1.4. The Other Than Disho norable Di scharge Mo dification s Workstre am43 | |
77 | 3.2.3.2.Ap plication Report Int erface43 | |
78 | 3.2.3.3.Un mapped Dat a Element4 3 | |
79 | 3.3.Concep tual Infra structure Design44 | |
80 | 3.3.1.Syst em Critica lity and H igh Availa bility44 | |
81 | 3.3.2.Spec ial Techno logy45 | |
82 | 3.3.3.Tech nology Loc ations45 | |
83 | 3.3.4.Conc eptual Inf rastructur e Diagram4 5 | |
84 | 3.3.4.1.Lo cation of Environmen ts and Ext ernal Inte rfaces45 | |
85 | 3.3.4.2.Co nceptual P roduction String Dia gram45 | |
86 | 4.System A rchitectur e45 | |
87 | 4.1.Hardwa re Archite cture45 | |
88 | 4.2.Softwa re Archite cture45 | |
89 | 4.3.Networ k Architec ture48 | |
90 | 4.4.Servic e Oriented Architect ure / ESS4 8 | |
91 | 4.5.Enterp rise Archi tecture49 | |
92 | 5.Data Des ign49 | |
93 | 5.1.DBMS F iles49 | |
94 | 5.1.1.Logi cal Model4 9 | |
95 | 5.1.2.DBMS Schemas, Subschemas , Records, Sets, Tab les, Stora ge Page Si zes49 | |
96 | 5.1.3.Acce ss Methods 50 | |
97 | 5.1.4.Esti mate the D atabase Fi le Size50 | |
98 | 5.1.5.Upda te Frequen cy51 | |
99 | 5.1.6.Esti mates on t he Number of Transac tions52 | |
100 | 5.2.Non-DB MS Files52 | |
101 | 5.3.Data V iew53 | |
102 | 6.Detailed Design53 | |
103 | 6.1.Hardwa re Detaile d Design53 | |
104 | 6.2.Softwa re Detaile d Design53 | |
105 | 6.2.1.Conc eptual Des ign53 | |
106 | 6.2.1.1.Pr oduct Pers pective54 | |
107 | 6.2.1.1.1. User Inter faces54 | |
108 | 6.2.1.1.2. Hardware I nterfaces5 4 | |
109 | 6.2.1.1.3. Software I nterfaces5 4 | |
110 | 6.2.1.1.4. Communicat ions Inter faces55 | |
111 | 6.2.1.1.5. Memory Con straints55 | |
112 | 6.2.1.1.6. Special Op erations55 | |
113 | 6.2.1.2.Pr oduct Feat ures55 | |
114 | 6.2.1.2.1. Patient Re cord Flag Workstream 55 | |
115 | 6.2.1.2.2. Copayment Modificati ons Workst ream56 | |
116 | 6.2.1.2.3. Other Than Dishonora ble Discha rge Modifi cations Wo rkstream56 | |
117 | 6.2.1.3.Us er Charact eristics56 | |
118 | 6.2.1.4.De pendencies and Const raints57 | |
119 | 6.2.2.Spec ific Requi rements57 | |
120 | 6.2.2.1.Da tabase Rep ository57 | |
121 | 6.2.2.1.1. Patient Re cord Flag Workstream 57 | |
122 | 6.2.2.1.2. Copayment Modificati ons Workst ream59 | |
123 | 6.2.2.1.3. Other Than Dishonora ble Discha rge Modifi cations Wo rkstream59 | |
124 | 6.2.2.2.Sy stem Featu res59 | |
125 | 6.2.2.3.De sign Eleme nt Tables6 0 | |
126 | 6.2.2.3.1. Routines ( Entry Poin ts)60 | |
127 | 6.2.2.3.1. 1.Other Th an Dishono rable Disc harge Modi fications Workstream 60 | |
128 | 6.2.2.3.1. 2.Copaymen t Modifica tions Work stream71 | |
129 | 6.2.2.3.1. 3.Patient Record Fla g Workstre am75 | |
130 | 6.2.2.3.2. Templates8 1 | |
131 | 6.2.2.3.3. Bulletins8 1 | |
132 | 6.2.2.3.4. Data Entri es Affecte d by the D esign81 | |
133 | 6.2.2.3.5. Unique Rec ord(s)82 | |
134 | 6.2.2.3.6. File or Gl obal Size Changes82 | |
135 | 6.2.2.3.7. Mail Group s83 | |
136 | 6.2.2.3.8. Security K eys83 | |
137 | 6.2.2.3.9. Options83 | |
138 | 6.2.2.3.10 .Protocols 83 | |
139 | 6.2.2.3.11 .Remote Pr ocedure Ca ll (RPC)84 | |
140 | 6.2.2.3.11 .1.Patient Record Fl ag Workstr eam84 | |
141 | 6.2.2.3.11 .2.Other T han Dishon orable Dis charge Mod ifications Workstrea m85 | |
142 | 6.2.2.3.12 .Constants Defined i n Interfac e87 | |
143 | 6.2.2.3.13 .Variables Defined i n Interfac e87 | |
144 | 6.2.2.3.14 .Types Def ined in In terface87 | |
145 | 6.2.2.3.15 .GUI - fFr ame87 | |
146 | 6.2.2.3.16 .GUI Class es88 | |
147 | 6.2.2.3.17 .Current F orm88 | |
148 | 6.2.2.3.18 .Modified Form89 | |
149 | 6.2.2.3.19 .Component s on Form8 9 | |
150 | 6.2.2.3.20 .Events90 | |
151 | 6.2.2.3.21 .Methods90 | |
152 | 6.2.2.3.22 .Special R eferences9 0 | |
153 | 6.2.2.3.23 .Class Eve nts91 | |
154 | 6.2.2.3.24 .Class Met hods91 | |
155 | 6.2.2.3.25 .Class Pro perties91 | |
156 | 6.2.2.3.26 .Uses Clau se91 | |
157 | 6.2.2.3.27 .GUI Class es92 | |
158 | 6.2.2.3.28 .Current F orm92 | |
159 | 6.2.2.3.29 .Modified Form93 | |
160 | 6.2.2.3.30 .Component s on Form9 3 | |
161 | 6.2.2.3.31 .Events93 | |
162 | 6.2.2.3.32 .Methods93 | |
163 | 6.2.2.3.33 .Special R eferences9 4 | |
164 | 6.2.2.3.34 .Class Eve nts94 | |
165 | 6.2.2.3.35 .Class Met hods94 | |
166 | 6.2.2.3.36 .Class Pro perties94 | |
167 | 6.2.2.3.37 .Uses Clau se94 | |
168 | 6.2.2.3.38 .Forms95 | |
169 | 6.2.2.3.39 .Functions 95 | |
170 | 6.2.2.3.40 .Dialog95 | |
171 | 6.2.2.3.41 .Help Fram e95 | |
172 | 6.2.2.3.42 .HL7 Appli cation Par ameter95 | |
173 | 6.2.2.3.43 .HL7 Logic al Link95 | |
174 | 6.2.2.3.44 .COTS Inte rface95 | |
175 | 6.3.Networ k Detailed Design95 | |
176 | 6.4.Securi ty and Pri vacy95 | |
177 | 6.4.1.Secu rity95 | |
178 | 6.4.2.Priv acy95 | |
179 | 6.4.3.Serv ice Descri ption for <Consumed Service Na me>96 | |
180 | 6.4.4.Serv ice Design for <Prov ided Servi ce Name>96 | |
181 | 6.4.4.1.In troduction 96 | |
182 | 6.4.4.1.1. Purpose an d Scope of Service96 | |
183 | 6.4.4.1.2. Links to O ther Docum ents96 | |
184 | 6.4.4.2.Se rvice Deta ils96 | |
185 | 6.4.4.2.1. Service Id entificati on96 | |
186 | 6.4.4.2.2. Service Ve rsions96 | |
187 | 6.4.4.2.3. Summary of Design an d Platform Details96 | |
188 | 6.4.4.2.3. 1.SOA Patt ern(s) Imp lemented96 | |
189 | 6.4.4.2.3. 2.COTS Pla tform Vend or Names a nd Version s for Host ing Platfo rm96 | |
190 | 6.4.4.3.De pendencies 96 | |
191 | 6.4.4.4.Se rvice Desi gn Details 96 | |
192 | 6.4.4.4.1. Service Na me96 | |
193 | 6.4.4.4.2. Interface9 6 | |
194 | 6.4.4.4.3. End Points 97 | |
195 | 6.4.4.4.4. Message Sc hemas97 | |
196 | 6.4.4.4.5. Informatio n Model97 | |
197 | 6.4.4.4.5. 1.Mappings from ELDM to Standa rds Based Schemas97 | |
198 | 6.4.4.4.5. 2.Use Case s (Use Cas e Model)97 | |
199 | 6.4.4.4.5. 3.Interact ion Diagra ms97 | |
200 | 6.4.4.5.Ga p Analysis 97 | |
201 | 6.4.4.5.1. Variances from Enter prise Targ et Archite cture97 | |
202 | 6.4.4.5.2. Variances from SLDs9 7 | |
203 | 6.4.4.5.3. Variances from Stand ards and P olicies97 | |
204 | 6.4.4.5.4. Justificat ion for Ex ceptions a nd Mitigat ion97 | |
205 | 7.External System In terface De sign98 | |
206 | 7.1.Interf ace Archit ecture98 | |
207 | 7.2.Interf ace Detail ed Design9 8 | |
208 | 8.Human-Ma chine Inte rface98 | |
209 | 8.1.Interf ace Design Rules98 | |
210 | 8.2.Inputs 98 | |
211 | 8.3.Output s98 | |
212 | 8.4.Naviga tion Hiera rchy98 | |
213 | 8.4.1.Scre en [x.1]98 | |
214 | 8.4.2.Scre en [x.2]98 | |
215 | 8.4.3.Scre en [x.3]98 | |
216 | 9.Attachme nt A – App roval Sign atures99 | |
217 | A.1.Identi fication o f Technolo gy and Sta ndards100 | |
218 | A.2.Constr aining Pol icies, Dir ectives an d Procedur es100 | |
219 | A.3.Requir ements Tra ceability Matrix100 | |
220 | A.4.Packag ing and In stallation 100 | |
221 | A.5.Design Metrics10 0 | |
222 | Appendix A : Data Dic tionaries Created/Mo dified101 | |
223 | Appendix B : Future C apabilitie s113 | |
224 | ||
225 | Introducti on | |
226 | Three work streams ha ve been de fined unde r the Suic ide High R isk Patien t Enhancem ents (SHRP E) project . These wo rkstreams enhance th e ability of the Dep artment of Veterans Affairs (V A) to alle viate fina ncial and emotional stressors of patient s who are flagged at being at High Risk for Suicid e (HRfS). In additio n to ensur ing clinic al informa tion regar ding High Risk statu s of all p atients, t he workstr eams are a ccurately shared wit hin Vetera ns Health Informatio n Systems and Techno logy Archi tecture (V istA) syst ems. | |
227 | The Patien t Record F lag workst ream addre sses: | |
228 | Display fa ilures for National Category 1 Patient R ecord Flag s (PRFs) | |
229 | Providing electronic request p rocess/abi lity to tr ansfer own ership of PRFs | |
230 | Removal of TIU Note with PRF a nd PRF enh ancement | |
231 | The Copaym ent Modifi cations wo rkstream a ddresses c hanges for billing s ystem for the patien t with an active Nat ional Cate gory 1 Pat ient Recor d Flag Hig h Risk for Suicide a ddresses: | |
232 | Enhance sy stems/appl ications ( e.g., Vist A/CPRS, fi nancial sy stem, etc. ) for copa yment modi fications for outpat ient visit s and spec ified medi cation cat egories fo r Veterans at high a cute clini cal risk f or suicide , identifi ed by an a ctive Cate gory 1 PRF . | |
233 | The abilit y provided for presc ribed medi cations to be dispen sed to Vet erans at h igh acute clinical r isk for su icide in a mounts les s than 30 days (e.g. , 2-week o r less sup ply) witho ut incurri ng additio nal costs to the Vet eran becau se of more frequent refills. | |
234 | The Other Than Honor able Disch arge (OTH) workstrea m addresse s: | |
235 | Identifica tion of fo rmer servi ce member’ s with an “Other tha n Honorabl e” service discharge and their eligibili ty for eme rgency men tal health services. | |
236 | Track form er service member’s status wit hin a 90 D ay episode of care. | |
237 | View forme r service member’s e ligibility and 90 Da y status i n the Comp uterized P atient Rec ord System (CPRS). | |
238 | Historical ly, the Bu siness Req uirement D ocument (B RD) and th e Requirem ents Speci fication D ocument (R SD) were i ncluded in this docu ment. With the imple mentation of the Vet eran-Focus ed Integra tion Proce ss (VIP), and the ap plication of the Rat ional Jazz tools, th e business and OIT c ompliance requiremen ts (epics, sub-epics , user sto ries) and their link ages, rela tionships are captur ed in the Rational J azz tools for this p roject and can be fo und in Rat ional’s MH LTH namesp ace RM mod ule and “S HRPE” repo sitory. | |
239 | Patient Re cord Flag Workstream Scope | |
240 | The aforem entioned e nhancement s will mod ify variou s VistA ap plications , primaril y the Vist A registra tion (DG n amespace). The scope of these enhancemen ts will in clude: | |
241 | Fixing HL7 message f ailures; | |
242 | On specifi c National Category 1 Patient Record Fla g scenario s identifi ed by Tier II/III su pport. | |
243 | By introdu cing a mor e robust s olution wh ich uses t he externa l values o f PRF flag s for iden tification purposes in HL7 mes saging ins tead of ut ilizing PR F names. | |
244 | Introducin g two new subfiles i n two exis ting VistA files to store info rmation to support t he busines s linkage between a National C ategory 1 Behavioral Patient R ecord Flag assigned to a patie nt, and an y open Dis ruptive Be havior Rep orting Sys tem (DBRS) case(s) f or the sam e patient. DBRS data will be t ransmitted to other sites the patient is registere d. | |
245 | Adding fun ctionality that disp lays DBRS data on th e CPRS Pat ient Recor d Flag scr een. | |
246 | A new repo rt will be created w ithin Vist A which di splays his torical ac tions take n on DBRS data on a PRF. | |
247 | Introducin g a new el ectronic m ethod whi ch authori zed users can transf er ownersh ip of a Pa tient’s Ac tive or In active Nat ional Cate gory 1 Hig h Risk for Suicide P atient Rec ord Flags between VA facilitie s. | |
248 | Adding fun ctionality that disp lays origi nating fac ilities fo r unlinked PRF flag actions on the CPRS Progress N otes Prope rties scre en and all ow the use r to sort the data b y all colu mns. | |
249 | The ‘Assig nment Acti ons Not Li nked’ repo rt will be updated w ith new re port selec tion crite ria which will enabl e a much m ore granul ar look in to PRF Ass ignment Ac tions Not Linked to any PRF. T his will p rovide the authorize d PRF user s the abil ity to ‘cl ean up’ an y actions taken agai nst a flag but not y et linked. | |
250 | ||
251 | Copayment Modificati ons Workst ream Scope | |
252 | The scope of the pro ject “Modi fying Copa yments for At Risk V eterans” i ncludes: | |
253 | Identify V eterans wh o are at r isk for su icide. | |
254 | Assign the “National Category 1 “High Ri sk for Sui cidal” fla g. | |
255 | Waive the Copay amou nt for out patient vi sit when t he flag is active so that the Veteran a re not fin ancially b urdened | |
256 | Prescribe the outpat ient medic ations in smaller qu antities t o reduce t he risk of overdosin g. This in cludes all Tier 1, T ier 2, and Tier 3 cl ass medica tions. | |
257 | Prorate co pay amount when fill ing or ref illing an outpatient prescript ion for a less than 30-day sup ply, so th at copayme nt increas e due to f requent di spensing i s eliminat ed. | |
258 | Other Than Dishonora ble Discha rge Modifi cations Wo rkstream S cope | |
259 | Department of Vetera ns Affairs Secretary , Dr. Davi d J. Shulk in, is req uesting th e ability to expand provisions for urgen t mental h ealth care needs to former ser vice membe rs with Ot her Than H onorable ( OTH) admin istrative discharges . This inc ludes expa nding acce ss to assi st former OTH servic e members who are in mental he alth distr ess and ma y be at ri sk for sui cide or ot her advers e behavior s. | |
260 | Currently, the VA pr ovides lim ited emerg ent care t o certain former ser vice membe rs with OT H Discharg e from the military that have not gone t hrough Vet erans Bene fits Admin istration (VBA) adju dication. | |
261 | Enhancemen ts will mo dify the V istA Regis tration pa ckage (DG namespace) and CPRS. | |
262 | User Profi les | |
263 | Patient Re cord Flag Workstream | |
264 | The intend ed users o f these en hancements will be R egistratio n (DG name space) aut horized st aff (Table 1) workin g in VA fa cilities a nd Veteran s Integrat ed Service Network ( VISN) offi ces with a ccess to t he Patient Record Fl ags (PIMS/ ADT) (DGPF namespace ) menus. T he average user will have a ba sic knowle dge of how to use a computer a nd will ha ve previou s experien ce with Vi stA in a R egistratio n (DG) set ting. | |
265 | Table 1: A uthorized Staff and Access Lev els (Prima ry) | |
266 | User Level | |
267 | Role | |
268 | Responsibi lities | |
269 | Access Lev el | |
270 | Primary Us er | |
271 | DGPF autho rized user s | |
272 | Allow the creation, edit, owne rship tran sfers of N ational Ca tegory 1 P RFs. | |
273 | Read/Write | |
274 | Copayment Modificati ons Workst ream | |
275 | The intend ed users o f these en hancements will be R egistratio n, Integra ted Billin g, CPRS, a nd adminis trative st aff workin g in VA fa cilities a nd VISN of fices (Tab le 2). The average u ser will h ave a basi c knowledg e of how t o use a co mputer and will have previous experience with Vist A in Regis tration (D G namespac e), Integr ated Billi ng (IB), T IU and CPR S (OR) set ting (Tabl e 3). The user shoul d have a f air unders tanding of the proce sses in th e healthca re system of the Dep artment of Veterans Affairs Me dical Cent ers (VAMC) . | |
276 | Table 2: A uthorized Staff and Access Lev els (Cont) | |
277 | User Level | |
278 | Role | |
279 | Responsibi lities | |
280 | Access Lev el | |
281 | Primary Us er | |
282 | IB Staff | |
283 | Track copa ys charges . | |
284 | Read/Write | |
285 | Primary Us er | |
286 | VA Service Providers | |
287 | Check out patient fo r outpatie nt visits. | |
288 | Prescribe medication s. | |
289 | Read/Write | |
290 | Primary Us er | |
291 | Pharmacist s | |
292 | Release me dications. | |
293 | Read/Write | |
294 | Secondary User | |
295 | System Adm inistrator | |
296 | Maintain V istA - DG (registrat ion), TIU (Text Inte gration Ut ility) IB (Integrate d Billing) and OR (C PRS) syste ms. | |
297 | Full Contr ol | |
298 | Other Than Dishonora ble Discha rge Modifi cations Wo rkstream | |
299 | Table 3: A uthorized Staff and Access Lev els (Cont) | |
300 | User Level | |
301 | Role | |
302 | Responsibi lities | |
303 | Access Lev el | |
304 | Primary Us er | |
305 | DG authori zed users | |
306 | Registrati on clerks | |
307 | Read/Write | |
308 | Primary Us er | |
309 | CPRS user | |
310 | Healthcare providers | |
311 | Read/Write | |
312 | Background | |
313 | Overview o f the Syst em | |
314 | Patient Re cord Flag Workstream | |
315 | The NSR in cluded in this effor t, as well as an ove rview of i t, is prov ided below . | |
316 | Suicide Hi gh Risk Pa tient Enha ncements-P RF | |
317 | (NSR # 201 60415 Suic ide High R isk Patien t Enhancem ents) | |
318 | Currently, when a Na tional Cat egory 1 Pa tient Reco rd Flag is assigned to a patie nt, or the Ownership of that P RF changes from one VA facilit y to anoth er (based on where t he patient receives outpatient treatment ) there ar e instance s where th e HL7 mess aging whic h is suppo sed to kee p the PRF data in sy nc amongst VistA ins tances, fa ils. | |
319 | After this proposed enhancemen t, the roo t cause of the HL7 m essaging f ailures fo r PRFs in the busine ss scenari os provide d, will be rectified and a sol ution will be develo ped, teste d and impl emented. | |
320 | The curren t process for transf erring Nat ional Cate gory 1 Hig h Risk for Suicide ( HRfS) PRF ownership is a manua lly intens ive series of steps. The facil ity which seeks to b ecome the owner of t he PRF (mo st likely due to the patient r eceiving o utpatient treatment regularly at this fa cility) mu st phone t he owning facility a nd request that they re-assign the PRF t o their fa cility. Th is can tak e days to move throu gh the nec essary com munication and ultim ately tran sfer the P RF ownersh ip. This i s an unacc eptable ti me length when deali ng with th e sharing of clinica l informat ion relate d to a hei ghtened ri sk of suic ide for th e patients . | |
321 | After this proposed enhancemen t, Inactiv e National Category 1 PRFs HRf S will be electronic ally trans ferred to a requesti ng facilit y via one reassignme nt step. A ctive Cate gory 1 PRF s HRfS wil l be elect ronically requested to have th eir owners hip transf erred, the request w ill be acc epted or r ejected an d ownershi p will tra nsfer elec tronically or will r emain assi gned to it s current facility. The bottom portion o f the ‘Pro gress Note s Properti es’ pop up box in CP RS which d isplays un linked fla g actions, will be s orted by d efault to display un linked fla g actions which ‘bel ong’ to th e same fac ility as t he logged- in user fi rst and th en flag ac tions from other fac ilities. A fter that users can change the order by sorting en tries for each of th e columns in ascendi ng and des cending or der of the ir values. | |
322 | There is a current V A directiv e which pu ts forth t he require ment that a progress note must be linked to a flag action, w ithin CPRS on a pati ent record . That dir ective is being chan ged to NOT make the linking of a progres s note to a flag act ion mandat ory. It wi ll still b e technica lly possib le; but it will not be mandato ry within the busine ss process . Because informatio n from the current p rogress no te linkage to a Nati onal Categ ory 1 Beha vior PRF, for exampl e, flows d ownstream into the M yHealtheVe t system, this is ca using stre ss to pati ents who s ee that a ‘Behaviora l’ PRF has been plac ed on thei r patient record. | |
323 | After this proposed enhancemen t, two new fields wi ll be plac ed on the National C ategory 1 ‘Behaviora l’ PRF to capture ‘D BRS Case N umber’ and ‘Other.’ This will allow heal th care pr oviders wi thin the V HA Workpla ce Violenc e Program the abilit y to link a patient’ s behavior al PRF wit h a case n umber(s) f rom the VA ’s Disrupt ive Behavi oral Repor ting Syste m. These D BRS case n umbers hav e no meani ng to the patients a nd should induce no unnecessar y emotiona l stress. These fiel ds will be added to existing R ecord Flag Assignmen t options/ screens as well as t o the PRF History fi le and wil l also be displayed on the Pat ient Recor d Flag wit hin CPRS. The Progre ss Notes P roperties box will a lso be upd ated to in clude the Facility ( if determi nable) for each unli nked flag action. A new report will also be create d to displ ay histori cal action s taken on the DBRS data on a PRF. The r eport crit eria will also be up dated on t he “Assign ment Actio n Not Link ed” report to includ e new/diff erent opti ons provid ing the us er a myria d of ways to slice/d ice assign ment actio ns which a re not lin ked to any PRF. | |
324 | Copayment Modificati ons Workst ream | |
325 | The NSR in cluded in this effor t, as well as an ove rview of i t, is prov ided below . | |
326 | Suicide Hi gh Risk Pa tient Enha ncements- Copayment | |
327 | Suicide Hi gh Risk Pa tient Enha ncements e ffort inco rporates t he Modifyi ng High Ri sk patient Copayment s (NSR # 2 0160415) | |
328 | The Depart ment of Ve terans Aff airs (VA) has noted that there are subst antial num bers of ve terans at risk for s uicide. In order to prevent th e suicidal attempts, the VA pr oposes the following rules: | |
329 | For vetera ns who are at risk f or suicide , increase the frequ ency of ou tpatient m ental heal th visits to provide more inte nse care b y eliminat ing the ou tpatient m edical car e copaymen t so that they are n ot financi ally burde ned. | |
330 | When a pat ient with an active Category 1 Record Fl ag (HRfS) orders fil l or refil l of medic ation they are provi ded with a two-week supply or less of me dication a t a pro-ra ted copaym ent amount so that t hey are pr otected fr om the lik elihood of fatal or medically serious ov erdoses.Th e work is needed to ensure tha t all Vete rans at HR fS get app ropriate a ssessment and receiv e appropri ate elemen ts of the enhanced c are model for suicid e preventi on. | |
331 | Other Than Dishonora ble Discha rge Modifi cations Wo rkstream | |
332 | Modificati ons are ne eded to Vi stA to ens ure former service m embers wit h OTH admi nistrative discharge , and thei r eligibil ity for em ergency me ntal healt h care ser vices, are identifia ble in the electroni c health r ecord, and VA staff can track the former service m ember’s st atus withi n a 90day episode of care. | |
333 | The curren t process does not a llow the h ealth care team to r eadily ide ntify a fo rmer servi ce member’ s OTH disc harge type and eligi bility sta tus in the electroni c health r ecord. | |
334 | The curren t process does not c apture and track whe re the for mer servic e member f alls withi n the 90-d ay episode of care d uring prov ision of m ental heal th care. | |
335 | The curren t process does not a llow the h ealth care team to v iew former service m embers wit h OTH admi nistrative discharge s and thei r eligibil ity and 90 -day statu s in CPRS for emerge ncy mental health ca re service s. | |
336 | The challe nges to th e current process wi ll be addr essed with the follo wing enhan cements: | |
337 | New Second ary Eligib ility Code A new seco ndary elig ibility co de (OTH 90 Day Menta l Health) will be im plemented in VistA. This new c ode identi ties forme r service members wi th an OTH discharge type to VH A healthca re team me mbers, and allows th em to be t racked. Th e new code will disp lay in Reg istration and CPRS. | |
338 | 90 Day Sta tus | |
339 | Per VA pol icy, the f ormer serv ice member is allowe d two 90-d ay episode s of care within a 3 65 day per iod. The V ISN Chief Medical Of ficer must approve a second 90 -day episo de of care . | |
340 | The 90-Day Status wi ll consist of a coun tdown cloc k to be di splayed in CPRS. Thi s clock wi ll inform VHA health care team members th e number o f days rem aining wit hin a 90da y episode of care. T he countdo wn clock i s initiate d at the n umber 90, decrements by 1 dail y, and cou nts down t o zero. A value of 9 0 indicate s that the 90-Day Ep isode of C are has st arted, and a value o f zero ind icates tha t the 90-D ay Episode of Care h as expired . | |
341 | Example 1: Patient “ A” has “X” days rema ining in a 90-Day Ep isode of C are. | |
342 | Example 2: Patient “ A” has 90 days remai ning in a 90-Day Epi sode of Ca re. | |
343 | Example 3: Patient “ A” has 60 days remai ning in a 90-Day Epi sode of Ca re. | |
344 | Example 4: Patient “ A” has 30 days remai ning in a 90-Day Epi sode of Ca re. | |
345 | Example 5: Patient “ A” has 0 d ays remain ing in a 9 0-Day Epis ode of Car e. | |
346 | OTH status diaplayed on the CP RS screen | |
347 | OTH Button displays in the CPR S header a nd consist s of the f ollowing: | |
348 | Part 1 – D isplay the status of former se rvice memb er as “OTH ” | |
349 | Part 2 – D isplay the number of treatment days rema ining in a 90-Day Ep isode of C are | |
350 | Part 3 – D isplay whi ch period for the 90 -Day-Episo de of Care | |
351 | ||
352 | OTH | |
353 | 4D,P1 | |
354 | ||
355 | OTH | |
356 | 4D,P1 | |
357 | Exam ple: | |
358 | Part 1 - S tatus of f ormer serv ice member is “OTH” | |
359 | Part 2 - 4 days rema in in a 90 -Day Episo de of Care | |
360 | Part 3 - P eriod 1 or the first 90-Day Ep isode of C are | |
361 | CPRS scree n capture (Figure 1) : | |
362 | OTH [butto n] – 4D,P1 (4 days r emain in t he 1st per iod) | |
363 | Click on b utton to d isplay the following [pop-up b ox] messag e (Figure 2): | |
364 | “4 Days Re maining in a 90-Day Episode of Care(Figu re 3) | |
365 | Figure 1: CPRS Scree n Capture | |
366 | Figure 2: Screen cap uture – Ex panded hel p [wide bu tton] | |
367 | ||
368 | Figure 3: Screen cap uture – Ex panded hel p [tool ti p] | |
369 | ||
370 | Overview o f the Busi ness Proce ss | |
371 | Patient Re cord Flag Workstream | |
372 | The busine ss process es affecte d by these requireme nts are th e creation , update, and owners hip transf er of Nati onal Categ ory 1 PRFs . These pr ocesses ar e outlined in the di agram in s ection 3.2 .1.1PRF/TI U Workstre am. | |
373 | Refer to t he diagram in sectio n 3.2.1.1. PRF/TIU W orkstream. | |
374 | Copayment Modificati ons Workst ream | |
375 | The busine ss process es for pre scribing m edications (Figure 4 ) are affe cted by th ese requir ements. Th e provider s will be prescribin g medicati ons to the patients with activ e National Category 1 Patient Record Fla g High Ris k for Suic ide to be dispensed in amounts less than 30 days ( e.g., 2-we ek or less supply) a t prorated amount wi thout incu rring addi tional cos ts to the Veteran be cause of m ore freque nt refills . | |
376 | The new fu nctionalit y requires exempting patients with the a ctive Nati onal Categ ory 1 Pati ent Record Flag High Risk for Suicide fr om visit c opay charg es. These exemptions will be p rocessed i n backgrou nd and wil l be invis ible for t he user wh o checks t he patient out in th e clinic. | |
377 | Figure 4: Copayment Modificati ons Workst ream | |
378 | ||
379 | Other Than Dishonora ble Discha rge Modifi cations Wo rkstream | |
380 | The busine ss process for other than hono rable disc harge (Fig ure 5) inv olves the following: | |
381 | Identify f ormer serv icemembers with an O ther than Honorable discharge status bei ng treated for emerg ent mental health in VistA. | |
382 | Track the episode of care for the patien t. | |
383 | Limit the episode of care for the patien t to two 9 0-day peri ods (no mo re than 18 0 days) pe r every 36 5 days. | |
384 | Currently, this is a manual pr ocess that the VA se eks to imp rove with modificati ons to Vis tA and CPR S. | |
385 | Figure 5: Business P rocess for Other tha n Honorabl e Discharg e | |
386 | ||
387 | Overview o f Signific ant Requir ements | |
388 | See Sectio n 1.1 Pati ent Record Flag Work stream Sco pe for in formation regarding requiremen ts. | |
389 | Overview o f Function al Require ments | |
390 | Patient Re cord Flag Workstream Scope | |
391 | The Suicid e High Ris k Preventi on Enhance ments exec utes the f ollowing ( Table 4). Note that additional requireme nts will b e added as -needed to the Ratio nal reposi tory. | |
392 | Table 4: F unctional Requiremen ts | |
393 | Epic (EP)/ Req. ID # | |
394 | Owner Requ irement (O WNR) | |
395 | Acceptance Criteria | |
396 | Supporting Informati on | |
397 | NSR: 20160 415 | |
398 | EPIC 84503 5 | |
399 | Suicide Pr evention H igh Risk P atient Enh ancements | |
400 | For Vetera ns Health Administra tion healt h care tea m members (e.g., pro viders, an cillary se rvices, ad ministrati ve staff, etc.) | |
401 | Who need t o identify and provi de enhance d services to suppor t Veterans at risk f or suicide | |
402 | A Process is needed to easily identify, track, and consisten tly commun icate the suicide ri sk status of Veteran s and allo w subseque nt actions (e.g., as sessments, reporting , referral s, etc.) t o be taken | |
403 | That suppo rts access to care a nd improve d Veteran experience through a broad ran ge of elem ents in th e enhanced suicide p revention model of c are for hi gh risk Ve terans for suicide t o include more frequ ent contac ts, restri cting acce ss to mean s for suic ide, provi ding preve ntative re sources su ch as Nalo xone, ensu ring effec tiveness a nd reliabi lity of th e Patient Record Fla g (PRF) fo r identifi cation of individual s at high risk, and providing the abilit y to track referrals to Mental Health (M H) based o n risk ass essment an d disposit ion | |
404 | Unlike the current p rocesses t hat pose b arriers to accessing care and require ex tensive ma nual worka rounds | |
405 | Our proces s will imp rove custo mer servic e for VA p roviders a nd other m embers of the health care team by implem enting aut omated pro cesses to support id entificati on and tra cking of n ew referra ls to MH b y risk sta tus while reducing t he financi al barrier s that may interfere with high risk indi viduals re ceiving en hanced lev els of car e reducing errors an d time ass ociated wi th manuall y correcti ng PRF own ership and display i ssues supp orting bes t practice s and qual ity as pro moting ope n access t o care for Veterans. | |
406 | Our proces s will imp rove custo mer servic e for VA p roviders a nd other m embers of the health care team by implem enting aut omated pro cesses to support id entificati on and tra cking of n ew referra ls to MH b y risk sta tus while reducing t he financi al barrier s that may interfere with high risk indi viduals re ceiving en hanced lev els of car e. | |
407 | ||
408 | This reduc es errors and time a ssociated with manua lly correc ting PRF o wnership a nd display issues, w hile suppo rting best practices and quali ty, as wel l as promo ting open access to care for V eterans. | |
409 | ||
410 | Sub Epic 7 33239 | |
411 | Display Ca tegory 1 P atient Rec ord Flag ( PRF) | |
412 | For Vetera ns Health Administra tion healt h care tea m members (e.g., pro viders, Me ntal Healt h [MH] Tre atment Coo rdinators, and admin istrative staff) | |
413 | Who need t o identify Veterans at risk fo r suicide | |
414 | The proces s of shari ng the Cat egory 1 PR F informat ion for a Veteran’s episode of care is n eeded | |
415 | That will ensure app ropriate a nd reliabl e display of PRFs en terprise-w ide | |
416 | Unlike mai ntaining t he status quo of tod ay where t he potenti al exists for staff to miss th e threat t o their sa fety, the safety of others, or the Veter an themsel ves, becau se the PRF does not display co nsistently across fa cilities | |
417 | Our Proces s allows f or the cor rect ident ification and subseq uent monit oring and follow up for Vetera ns at risk for suici de across VA facilit ies, impro ving quali ty of heal th care se rvices and reducing costs asso ciated wit h staff ti me by elim inating th e need for coordinat ing the tr ansfer of ownership across mul tiple site s and comp leting man ual correc tion when the PRF do es not app ly properl y, support ing best p ractices a nd quality . | |
418 | ||
419 | ||
420 | User Story 913039 | |
421 | As a Veter ans Health Administr ation heal th care te am member, I need to be able t o view act ive Catego ry I Patie nt Record Flags wher ever the V eteran is receiving treatment to include all facil ities wher e the Vete ran is reg istered fo r care, so that I ca n ensure t he patient receives the approp riate time ly care. | |
422 | Note: App ropriate d isplays en sure that active fla g is displ ayed in sy stem (Comp uterized P atient Rec ord System as a pop- up Flag al ways witho ut opening the remot e view). | |
423 | • All Acti ve Categor y I Flags are succes sfully dis played in the Vetera n's chart at all fac ilities wh ere the Ve teran is r egistered (Electroni c Health R ecord). | |
424 | • The Acti ve/Inactiv e Flags ar e successf ully displ ayed in Vi stA Flag M enus. | |
425 | • The Curr ent/Histor ical Flags are displ ayed in Vi stA Flag M enus. | |
426 | ||
427 | User Story 913040 | |
428 | As a Veter ans Health Administr ation heal th care te am member (staff tha t manages Patient Re cord Flags ), I need the abilit y to captu re ownersh ip of an i nactive fl ag if in i nactive st ate and ow ned at ano ther facil ity, witho ut requiri ng any act ion by the current o wner of th e flag to transfer o wnership, so that I can ensure the patie nt receive s the appr opriate ti mely care. | |
429 | ||
430 | Note: The issue is t hat it sho uld be a “ pull” proc ess that d oes not re quire acti on (and th erefore th e need to contact) t he owning site, then an active push noti fication f rom the si te that is changing ownership to the sit e that “ow ns” the fl ag so the previous o wning site is aware of the cha nge. | |
431 | • The Flag ownership is succes sfully cap tured by n ew owner. | |
432 | • The Flag ownership is succes sfully tra nsferred w ithout rea ctivation. | |
433 | • The Noti fication o f ownershi p change i s successf ully trans mitted to prior owne r. | |
434 | ||
435 | User Story 913041 | |
436 | As a Veter ans Health Administr ation heal th care te am member, I need th e ability to capture ownership of an act ive flag b y electron ically req uesting th at the Cat egory 1 Fl ag be tran sferred to the reque sting site , so that I can ensu re the pat ient recei ves the ap propriate timely car e. | |
437 | • The Elec tronic Req uest is su ccessfully transmitt ed to curr ent facili ty owner o f active f lag. | |
438 | • The Elec tronic Req uest is su ccessfully received by current facility owner. | |
439 | • The Curr ent Owners hip facili ty accepts the reque st for Own ership tra nsfer. | |
440 | • The New Owner has successful ly receive d the tran sferred ac tive flag. | |
441 | • The Elec tronic Not ification is success fully tran smitted to prior fac ility owne r. | |
442 | • The Elec tronic Not ification is success fully rece ived by pr ior facili ty owner. | |
443 | ||
444 | User Story 913044 | |
445 | As a Syste m, I need the abilit y to proce ss Patient Record Fl ags (PRF) without re quiring an electroni c transmis sion of Te xt Integra tion Utili ty (TIU) N otes to be linked be tween the PRF and TI U systems, so that t he safety of the Vet eran and c linical st aff is mai ntained. | |
446 | • The Requ irement fo r “Linkage ” between Text Integ ration Uti lity Notes and Flags is succes sfully rem oved. | |
447 | • The Disr uptive Beh avior Repo rting iden tification number is successfu lly captur ed. | |
448 | • The Opti on for Cat egory 1 re port to di splay Pati ent Record Flags ass ignment hi story acti ons is suc cessfully removed fo r a specif ic date ra nge. | |
449 | ||
450 | ||
451 | Copayment Modificati ons Workst ream Scope | |
452 | The Workst ream is de scribed by following the SubEp ics (Table 5) throug h the User Stories. | |
453 | Note that additional requireme nts will b e added as -needed to the Ratio nal reposi tory. | |
454 | Table 5: C opayment M odificatio n Workstre am | |
455 | Epic (EP)/ Req. ID # | |
456 | Owner Requ irement (O WNR) | |
457 | Acceptance Criteria | |
458 | Supporting Informati on | |
459 | NSR: 20160 415 | |
460 | SubEpic | |
461 | 714252 | |
462 | Modifying High Risk Veterans’ Copayments | |
463 | For Vetera ns, Vetera ns Health Administra tion (VHA) providers , pharmaci sts, admin istrative, and busin ess staff | |
464 | Who are at high risk for suici de and the VA staff who provid e services to Vetera ns at high risk for suicide (t o include processing copayment bills) | |
465 | A process is needed to modify or elimina te copayme nts for ou tpatient v isits and specific m edications that are dispensed in less th an 30 day quantities for a Vet eran ident ified by C ategory I Patient Re cord Flag | |
466 | That will anticipate and meet the needs of our mos t vulnerab le Veteran s, support ing an enh anced evid ence-based care mode l for trea ting Veter ans at hig h risk for suicide. | |
467 | Unlike the current s ystem that presents a barrier to Veteran s at high risk for s uicide by increased costs asso ciated wit h both cop ayments fo r more fre quent visi ts and med ication fi lls in sma ller amoun ts. | |
468 | Our proces s will rem ove the fi nancial ba rriers by automatica lly adjust ing or eli minating c opayment a mounts for outpatien t visits a nd medicat ions for i ndividuals at high r isk for su icide and determine clinical n eed for Na loxone res cue kits w ith new op ioid presc riptions, with optio n to remov e if Veter an already has curre nt rescue kit, thus reducing t he risk of suicide a nd address ing VHA pr iorities r elated to access to care. | |
469 | ||
470 | ||
471 | User Story | |
472 | 913042 | |
473 | As a Presc ribing Pro vider, I n eed the ab ility to e nter outpa tient pres criptions for less t han 30 day quantitie s for high risk medi cations fo r Veterans with an a ctive Cate gory 1 Hig h Risk Pat ient Recor d Flag wit hout gener ating addi tional med ication co payments w ithin a Th irty (30) day period , so that I can decr ease the f inancial b urden for the Enhanc ed Care Mo del with V eterans at risk for suicide an d improve access to care.. | |
474 | • The Addi tional Med ication Co payments f or prescri ptions wri tten for l ess than 3 0day quant ities are successful ly elimina ted within a thirty (30) day p eriod. | |
475 | • The Addi tional Med ication Co payments f or prescri ptions wri tten for l ess than 3 0 day quan tities are successfu lly elimin ated only for Vetera ns assigne d Category 1 Patient Record Fl ag status. | |
476 | ||
477 | User Story | |
478 | 913043 | |
479 | As a Provi der, I nee d the abil ity to ens ure that p atients wi th an acti ve High Ri sk Cat 1 P atient Rec ord Flag b e seen for outpatien t visits a s many tim es as indi cated by t he Enhance d Care Mod el without copayment s being ch arged for the patien t high ris k status a nd until t he Categor y I Flag h as been in activated, so that a financial burden is not cause d to the V eteran by the need f or enhance d level of care. | |
480 | The Patien t (Veteran ) is succe ssfully se en during outpatient visits as many time s as neces sary witho ut copays. | |
481 | The Patien t (Veteran ) is succe ssfully no t charged copays for visit onl y if assig ned Patien t Record F lag Catego ry 1 statu s.The Pati ent (Veter an) is suc cessfully seen durin g outpatie nt visits without co pays until Cat 1 Fla g is inact ivated. | |
482 | ||
483 | About OTH Modificati ons Workst ream Scope | |
484 | The OTH ex ecutes the following workstrea m (Table 6 ). | |
485 | Table 6: O ther than Dishonorab le Dischar ge (OTH) M odificatio ns Workstr eam Scope | |
486 | Epic (EP)/ Req. ID # | |
487 | Owner Requ irement (O WNR) | |
488 | Acceptance Criteria | |
489 | Supporting Informati on | |
490 | Epic | |
491 | 959986 | |
492 | Expanding VA Mental Health Car e for Vete rans with Other Than Honorable Discharge . | |
493 | Provide th e ability for former service m embers wit h OTH disc harge type and eligi bility for VA emerge ncy mental health ca re service s to be ac curately i dentifiabl e and imme diately vi sible in t he electro nic health record. | |
494 | ||
495 | Sub-Epic | |
496 | 959988 | |
497 | Identifica tion of fo rmer servi ce members with OTH discharge and eligib ility for emergency mental hea lth care s ervices. | |
498 | Provide th e ability to capture and displ ay a secon dary eligi bility cod e (OTH 90 Day MH) to capture t he specifi c eligibil ity for fo rmer servi ce members with OTH service di scharge ty pe being s een under this expan ded author ity. | |
499 | ||
500 | Sub-Epic | |
501 | 960011 | |
502 | Track form er service member’s status wit hin a 90-d ay episode of care. | |
503 | Provide th e ability to identif y where th e former s ervice mem bers falls within th e 90-day e pisode of care durin g mental h ealth care treatment . | |
504 | ||
505 | Sub-Epic | |
506 | 960012 | |
507 | View forme r service members el igibility and 90-day status in CPRS. | |
508 | Provide th e ability to view a former ser vice membe rs OTH dis charge typ e, eligibi lity, and 90-day sta tus in CPR S. | |
509 | ||
510 | Overview o f Function al Workloa d/Performa nce Requir ements | |
511 | Not applic able – thi s project is compose d of multi ple VistA applicatio ns: DG (Re gistration ), TIU (Te xt Integra tion Utili ty) IB (In tegrated B illing) an d OR (CPRS ). There a re no chan ges to fun ctional wo rkload/per formance r equirement s associat ed with th is project . | |
512 | Overview o f Operatio nal Requir ements | |
513 | Not applic able – the re are no changes to existing operationa l requirem ents. | |
514 | Overview o f Technica l Requirem ents | |
515 | Not applic able – the re are no changes to technical requireme nts that c hange the conceptual design of VistA. | |
516 | Overview o f Security or Privac y Requirem ents | |
517 | All VA and VHA secur ity or pri vacy requi rements wi ll be adhe red to. Cr oss-cuttin g security requireme nts are co ntained in the VA En terprise R equirement s Reposito ry (ERR). Efforts th at involve the colle ction and maintenanc e of Perso nally Iden tifiable I nformation (PII) mus t be cover ed by a Pr ivacy Act system of records no tice. | |
518 | Applicable security and privac y requirem ents are l oaded into Rational Tools (see Patient R ecord Flag Workstrea m Scope se ction). | |
519 | Overview o f System C riticality and High Availabili ty Require ments | |
520 | The system modified in this pr oject is c omposed of multiple VistA appl ications: DG (Regist ration), T IU (Text I ntegration Utility) IB (Integr ated Billi ng) and OR (CPRS). E ach of the se applica tions has its own av ailability and downt ime requir ements whi ch will be VAMC depe ndent. The applicati ons listed above do not impose any requi rements be yond the r equirement already s pecified b y each of the applic ations. | |
521 | Single Sig n-on Requi rements | |
522 | Not applic able – acc ess is con trolled by the VistA applicati on and the underlyin g operatin g system. This appli cation doe s not mand ate any ad ditional a ccess or s ign-on req uirements. | |
523 | Requiremen t for Use of Enterpr ise Portal s | |
524 | Not applic able – the re are no changes to the requi rements fo r use of e nterprise portals. | |
525 | Special De vice Requi rements | |
526 | Not applic able – no special de vices are required. | |
527 | Conceptual Design | |
528 | This proje ct is comp osed of Vi stA, IB, R egistratio n, TIU, an d CPRS mod ifications , and ther e are no c onceptual design con sideration s since th e new func tionality is embedde d to the e xisting ap plication code as mo dification s. The tea m has star ted making modificat ions as a part of th e VIP Agil e developm ent proces s. Changes in the de sign can b e made dur ing the Ag ile proces ses in the future as necessary in respon se to cust omers' fee dback. | |
529 | The actual software detailed d esign is p resented i n Section 6.2.2Speci fic Requir ements. | |
530 | Conceptual Applicati on Design | |
531 | Not applic able – the re are no conceptual design co nsideratio ns. | |
532 | Applicatio n Context | |
533 | VistA comp rises near ly 200 dis tinct appl ications/m odules, 15 ,000 routi nes, and m illions of lines of computer c ode (Table 7). VistA interoper ates with numerous C ommercial- Off-the-Sh elf (COTS) software applicatio ns, with s elected in formation technology systems o f other fe deral agen cies and, increasing ly, with h ealth info rmation ex change net works (Fig ure 6). | |
534 | Figure 6: Applicatio ns Context Diagram f or OTH, Co pay and PR F /TIU fun ctionality | |
535 | ||
536 | Table 7 (G rouping): Applicatio n Context Descriptio n | |
537 | ID | |
538 | Name | |
539 | Descriptio n | |
540 | Interface Name | |
541 | Interface System | |
542 | No externa l interfac es are mod ified by t his projec t. | |
543 | ||
544 | ||
545 | ||
546 | ||
547 | Table 8: I nterfaces External t o OIT | |
548 | ID | |
549 | Name | |
550 | Related Ob ject | |
551 | Input Mess ages | |
552 | Output Mes sages | |
553 | External P arty | |
554 | No externa l interfac es are mod ified by t his projec t. | |
555 | ||
556 | ||
557 | ||
558 | ||
559 | ||
560 | ||
561 | ID | |
562 | Name | |
563 | Related Ob ject | |
564 | Input Mess ages | |
565 | Output Mes sages | |
566 | External P arty | |
567 | HL7 | |
568 | ORU^R01 | |
569 | ||
570 | Registrati on module | |
571 | unsolicite d update, DBRS data sent to an other site where the same pati ent is reg istrered | |
572 | unsolicite d update, DBRS data sent to an other site where the same pati ent is reg istrered | |
573 | Registrati on module in another VA site | |
574 | HL7 | |
575 | ORF^R04 | |
576 | Registrati on module | |
577 | query resp onse, DBRS data sent to anothe r site whe re the sam e patient is registr ered | |
578 | query resp onse, DBRS data sent to anothe r site whe re the sam e patient is registr ered | |
579 | Registrati on module in another VA site | |
580 | Table 9: E xternally Shared Dat a Stores | |
581 | ID | |
582 | Name | |
583 | Data Store d | |
584 | Owner | |
585 | Access | |
586 | No changes to extern ally share d data | |
587 | ||
588 | ||
589 | ||
590 | ||
591 | High-Level Applicati on Design | |
592 | This proje ct does no t require any change s to the h igh-level conceptual applicati on design. There are no change s to the h igh-level applicatio n design o f Registra tion, TIU, IB, and C PRS applic ations. | |
593 | For inform ational pu rposes and applicati on context , display the exitin g interfac es that ar e used for three wor kstreams. | |
594 | PRF/TIU Wo rkstream | |
595 | Figure 7.F igure 8. A nd Figure 9 display the HL7 me ssages exc hange betw een differ ent VA loc al system (VA sites) that ensu re that th e PRF flag changes a re propaga ted and up dated in a ll VA site s (in whic h the pati ent is reg istered). | |
596 | The modifi cation to the existi ng ICR 438 3 DGPF ASS IGNMENT LI NK TIU PN and the ne w ICR 6874 DGPF DBRS DATA have been subm itted for approval f or this wo rkstream. | |
597 | Figure 7: High-Level Applicati on Design Diagram wi th HL7 Exc hanges for Updating PRF Flags | |
598 | ||
599 | Copayment Modificati ons Workst ream | |
600 | Requests to subscri be IB (Int egrated Bi lling) app lication t o existing ICRs 5491 and 4903 have abee n approved in FORUM. These API s provide IB with th e access t o the Suic ide High R isk Patien t Flag dat a. | |
601 | Figure 8: High-Level Applicati on Design Diagram wi th HL7 Exc hanges for Updating PRF Flags | |
602 | Other than Dishonora ble Discha rge Modifi cations Wo rkstream | |
603 | Figure 9 d isplays th e internal interface s between applicatio ns within VistA. | |
604 | The the ne w ICR 6873 DG OTH EL IGIBILITY CLOCK STAT US has bee n submitte d for the approval f or this wo rkstream. | |
605 | Figure 9: High-Level Applicati on Design Diagram wi th HL7 Exc hanges for Updating PRF Flags | |
606 | Applicatio n Location s | |
607 | Not applic able – thi s project does not r equire any changes t o the appl ication lo cations. | |
608 | Conceptual Data Desi gn | |
609 | Project Co nceptual D ata Model | |
610 | Models wil l be added in a late r edition. | |
611 | PRF/TIU wo rkstream | |
612 | Figure 10: PRF/TIU C onceptual Data Model Figure | |
613 | Copays Wor kstream | |
614 | Figure 11: Copays Mo dification s Conceptu al Data Mo del | |
615 | ||
616 | OTH Workst ream | |
617 | Figure 12: (OTH) Mod ifications Conceptua l Data Mod el | |
618 | Database I nformation | |
619 | Table 10: Database I nventory | |
620 | Database N ame | |
621 | Descriptio n | |
622 | Type | |
623 | Steward | |
624 | 26.13 | |
625 | ||
626 | PRF ASSIGN MENT | |
627 | Modify | |
628 | REGISTRATI ON | |
629 | 26.14 | |
630 | ||
631 | PRF ASSIGN MENT HISTO RY | |
632 | Modify | |
633 | REGISTRATI ON | |
634 | 33 | |
635 | OTH ELIGIB ILITY CLOC K | |
636 | Create | |
637 | REGISTRATI ON | |
638 | 350.9 | |
639 | IB SITE PA RAMETERS | |
640 | Modify | |
641 | INTEGRATED BILLING | |
642 | 8 | |
643 | ELIGIBILIT Y CODE | |
644 | Modify | |
645 | REGISTRATI ON | |
646 | User Inter face Data Mapping | |
647 | Applicatio n Screen I nterface | |
648 | Patient Re cord Flag Workstream | |
649 | Figure 13: DGPF RECO RD FLAG AS SIGNMENT S creen Used to Enter DBRS Info | |
650 | RECORD FLA G ASSIGNME NT Mar 16, 20 18@17:14 Pa ge: 1 o f 1 | |
651 | Patient: T EST,PATIEN T (7090101 59P) DOB: 0 1/01/59 | |
652 | ICN: 4 420041589V 782553 CMOR: CH EYENNE VAM C | |
653 | ||
654 | Flag Assig ned Revie w Date Ac tive Loca l Owner S ite | |
655 | 1 BEHAVIO RAL 01/29 /18 N/A YE S NO CHEYENN E VAMC | |
656 | ||
657 | ||
658 | ||
659 | ||
660 | ||
661 | ||
662 | ||
663 | ||
664 | ||
665 | Enter ?? f or more ac tions | |
666 | SP Select Patient EF Edit F lag Assign ment | |
667 | DA Displa y Assignme nt Details CO Change Assignmen t Ownershi p | |
668 | AF Assign Flag FT PRF Ow ner Transf er Pull/Re quest | |
669 | Select Act ion:Quit// EF Edit Flag Assi gnment | |
670 | ||
671 | Selec t one of t he followi ng: | |
672 | ||
673 | C Continue A ssignment | |
674 | I Inactivate Assignmen t | |
675 | E Entered in Error | |
676 | X DBRS/Other Field Edi t Only | |
677 | ||
678 | Select an assignment action: X DBRS/Oth er Field E dit Only | |
679 | ||
680 | Select DBR S NUMBER: ? | |
681 | Answer with DBRS NUMBER | |
682 | Choose from: | |
683 | 111AA.1 23456 | |
684 | 333RR.1 11111 | |
685 | 444RR.2 22222 | |
686 | ||
687 | Yo u may ente r a new DB RS NUMBER, if you wi sh | |
688 | An swer must be 10-18 c haracters in length, <site#>.N NNNNN | |
689 | ||
690 | Select DBR S NUMBER: 555.334567 | |
691 | Are you adding '55 5.334567' as a new D BRS NUMBER ? No// y (Yes) | |
692 | DBRS NU MBER "DBRS Other": t est data | |
693 | ||
694 | Select DBR S NUMBER: | |
695 | ||
696 | Approved B y: DG,CLER K | |
697 | ||
698 | Enter the reason for editing t his assign ment: | |
699 | Patient Re cord Flag - Edit Rea son Text | |
700 | ==[ WRAP ] ==[INSERT ]========= ==< Edit R eason Text >=[Press <PF1>H for help]==== | |
701 | test | |
702 | ||
703 | ||
704 | ||
705 | <=======T= ======T=== ====T===== ==T======= T=======T= ======T=== ====T===== ==T>====== | |
706 | ||
707 | ||
708 | REVIEW OF EDIT FLAG ASSIGNMENT DATA INPU T BEFORE F ILING | |
709 | ---------- ---------- ---------- ---------- ---------- ----- | |
710 | Pat ient Name: TEST,PATI ENT | |
711 | Flag Name: BEHAVIORA L | |
712 | Flag Type: BEHAVIORA L | |
713 | Flag Category: I (NATION AL) | |
714 | Assignme nt Status: ACTIVE | |
715 | Initial A ssignment: 1/29/2018 @09:36:32 | |
716 | Last Re view Date: 2/15/2018 | |
717 | Next Re view Date: 0 | |
718 | O wner Site: CHEYENNE VAMC | |
719 | Origina ting Site: CHEYENNE VAMC | |
720 | Assignme nt Action: DBRS#/OTH ER FIELD U PDATE | |
721 | Ac tion Date: 3/16/2018 @17:15:22 | |
722 | E ntered By: DG,CLERK | |
723 | Ap proved By: DG,CLERK | |
724 | DBRS No.: 555.33456 7 | |
725 | DBRS Othe r: test da ta | |
726 | DBRS No.: 111AA.123 456 | |
727 | DBRS Othe r: testing AAA | |
728 | ||
729 | Type <Ente r> to cont inue or '^ ' to exit: | |
730 | ||
731 | ||
732 | REVIEW OF EDIT FLAG ASSIGNMENT DATA INPU T BEFORE F ILING | |
733 | ---------- ---------- ---------- ---------- ---------- ----- | |
734 | DBRS No.: 333RR.111 111 | |
735 | DBRS Othe r: test 11 11 | |
736 | DBRS No.: 444RR.222 222 | |
737 | DBRS Othe r: test 22 22 | |
738 | ||
739 | Record Fl ag Assignm ent Narrat ive: | |
740 | --------- ---------- ---------- ---- | |
741 | test | |
742 | ||
743 | Action Co mments: | |
744 | --------- ------- | |
745 | test | |
746 | ||
747 | ||
748 | Do you wan t to revie w again? N O// | |
749 | ||
750 | ||
751 | DGPF RECOR D FLAG ASS IGNMENT Sc reen | |
752 | Table 11: DGPF RECOR D FLAG ASS IGNMENT Sc reen Descr iption | |
753 | Graphical User Inter face (GUI) Field | |
754 | Table (Dat abase Tabl e that fie ld connect s to) | |
755 | Field (Fie ld in Tabl e that the GUI field connects to) | |
756 | Comments | |
757 | DBRS numbe r(s) assoc iated with the flag: | |
758 | PRF ASSIGN MENT file #(26.13) | |
759 | (#.01) DBR S NO. of t he (#2) DB RS NO. mul tiple | |
760 | The DBRS # from the DBRS syste m | |
761 | DBRS other informati on | |
762 | PRF ASSIGN MENT file #(26.13) | |
763 | (#.02) OTH ER of the (#2) DBRS NO. multip le | |
764 | Other DBRS informati on from th e DBSR sys tem | |
765 | DBRS date | |
766 | PRF ASSIGN MENT file #(26.13) | |
767 | (#.03) DAT E of the ( #2) DBRS N O. multipl e | |
768 | The DBRS d ate from t he DBRS sy stem | |
769 | DBRS numbe r(s) assoc iated with the flag: | |
770 | PRF ASSIGN MENT HISTO RY file #( 26.14) | |
771 | (#.07) DBR S NO. | |
772 | The DBRS # from the DBRS syste m | |
773 | DBRS other informati on | |
774 | PRF ASSIGN MENT HISTO RY file #( 26.14) | |
775 | (#.08) OTH ER DBRS DA TA | |
776 | Other DBRS informati on from th e DBSR sys tem | |
777 | Originated facility | |
778 | PRF ASSIGN MENT HISTO RY file #( 26.14) | |
779 | (#.09) ORI GINATING F ACILITY | |
780 | Originatii ng facilit y | |
781 | The Copaym ent Modifi cations Wo rkstream | |
782 | No user in terface ch anges are required f or the vis it copays exemption for the Ca t 1 High R isk for Su icide pati ents’ modi fication t hat were i mplemented in Sprint 1 of Buil d 2. | |
783 | No user in terface ch anges are required f or prorati ng RX pres cription c opays for the Cat 1 High Risk for Suicid e patients ’ modifica tion that were imple mented in Sprint 1 o f Build 2. | |
784 | The new ca ncellation reason “E XEMPT BY R EGULATION” has been added to t he file (# 350.3) so it can be selected w hen the us er cancels charges m ade for th e Cat 1 Hi gh Risk fo r Suicide patients. | |
785 | The new wa rning mess age is gen erated whe n the user s attempts to add vi sit copay charges ma nually for the Cat 1 High Risk for Suici de patient s. | |
786 | In further sprints u ser inter face chang es will be made to p rocess man ual charge s for copa ys. | |
787 | The SHRPE copay func tionality can be app lied to th e Cat 1 Hi gh Risk fo r Suicide patients o nly when t he appropr iate legia lariton ch anges are approved b y the gove rnment. If the softw are modifi cations ar e released prior to the date w hen the le gislation comes to t he effect then the n ew functio nalit y wi ll stay do rmant unti l the new field (#70 .02) SHRP E ACTIVATI ON DATE in the IB SI TES PARAME TERS FILE (#350.9) will be po pulated wi th the eff ective dat e for this legislati on. This new field serves as a switch t hat turns ON/OFF the functiona lity. This approach assumes th at a separ ate “infor mational” patch will be issued juts befo re the eff ective dat e with ins tructions for VA si tes how to access an d populate that fiel d and what date to u se. | |
788 | The Other Than Disho norable Di scharge Mo dification s Workstre am | |
789 | Please ref er to the following sections t o see the screenshot s of CPRS screens mo dified in Sprint 1 o f Build 2: | |
790 | 6.2.2.3.17 .Current F orm | |
791 | 6.2.2.3.18 Modified F orm | |
792 | 6.2.2.3.29 .Current F orm | |
793 | 6.2.2.3.30 .Modified Form | |
794 | Applicatio n Report I nterface | |
795 | Not applic able. No r eport chan ges are ex pected in the curren t build. | |
796 | Unmapped D ata Elemen t | |
797 | The data i n the OTH ELIGIBILIT Y CLOCK FI LE (#33)(F igure 14) will be us ed to trac k the Othe r Than Dis honorable Discharge (OTH) stat us for the patient a nd to calc ulate the OTH status informati on. These data will not be ent ered by th e user and will not be display s directly to the us er. | |
798 | Figure 14: OTH Eligi bility Clo ck File (# 33) | |
799 | ||
800 | FIELD FIELD | |
801 | NUMBER NAME | |
802 | ||
803 | .01 PATIENT (R P2'), [0;1 ] | |
804 | .02 STATUS (S) , [0;2] | |
805 | .03 VBA ADJUDI CATION (S) , [0;3] | |
806 | .04 CREATED BY (P200'), [0;4] | |
807 | .05 DATE CREAT ED (D), [0 ;5] | |
808 | 1 OTH 365 DA YS CLOCK ( Multiple-3 3.01), [1; 0] | |
809 | .01 365 D AYS PERIOD NUMBER (M NJ3,0), [0 ;1] | |
810 | .02 START DATE (D), [0;2] | |
811 | .03 AUTHO RIZED BY ( P200'), [0 ;3] | |
812 | .04 DATE AUTHORIZED (D), [0;4 ] | |
813 | .05 ENTER ED OR EDIT ED BY (P20 0'), [0;5] | |
814 | .06 DATE ENTERED OR EDITED (D ), [0;6] | |
815 | 1 OTH 9 0 DAYS CLO CK (Multip le-33.11), [1;0] | |
816 | .01 90 DAYS PE RIOD NUMBE R (MNJ1,0) , [0;1] | |
817 | .02 START DATE (D), [0;2 ] | |
818 | .03 AUTHORIZED BY (P200' ), [0;3] | |
819 | .04 DATE AUTHO RIZED (D), [0;4] | |
820 | .05 ENTERED OR EDITED BY (P200'), [0;5] | |
821 | .06 DATE ENTER ED OR EDIT ED (D), [0 ;6] | |
822 | Conceptual Infrastru cture Desi gn | |
823 | Not applic able. This project r elies on a nd uses th e existing VistA inf rastructur e and does n’t modify the exist ing mode m odificatio n. | |
824 | System Cri ticality a nd High Av ailability | |
825 | Not applic able – no changes ar e being ma de, nor ar e there an y design c onsiderati ons taken into accou nt with re spect to s ystem crit icality an d high ava ilability for this p roject. Th e disaster relief pl ans for Vi stA are no t affected by this p atch. | |
826 | Special Te chnology | |
827 | Not applic able. No s pecial tec hnology is involved in the pat ch. | |
828 | Technology Locations | |
829 | Not applic able – the re are no changes to technolog y location s. | |
830 | Conceptual Infrastru cture Diag ram | |
831 | Not applic able. No c onceptual production string di agram exis ts. | |
832 | Location o f Environm ents and E xternal In terfaces | |
833 | Not applic able. Ther e are no e xternal in terfaces o r special environmen ts involve d. | |
834 | Conceptual Productio n String D iagram | |
835 | Not applic able. No c onceptual production string di agram exis ts. | |
836 | System Arc hitecture | |
837 | This proje ct is to b e composed of VistA patches th at do not require ch anges to t he VistA a rchitectur e or hardw are archit ecture. Ho wever, bri ef descrip tions of t hese entit ies are pr ovided bel ow. | |
838 | Hardware A rchitectur e | |
839 | The DG (Re gistration ), TIU (Te xt Integra tion Utili ty) IB (In tegrated B illing) an d OR (CPRS ) modules are part o f the Vist A suite of applicati ons. The V istA Monog raph state s: | |
840 | “VistA is deployed u niversally across VH A at more than 1,500 sites of care, incl uding each VAMC, Com munity Bas ed Outpati ent Clinic (CBOC) an d Communit y Living C enter (CLC ), as well as at nea rly 300 VA Vet Cente rs. These locations will have a variety of hardwar e platform s but all meet a min imal stand ard requir ed to supp ort VistA. ” | |
841 | Software A rchitectur e | |
842 | The entire VistA app lication c onsists of 200+ modu les. The V istA monog raph inclu des this d escription for VistA : | |
843 | “VistA is an integra ted Electr onic Healt h Record ( EHR) infor mation tec hnology sy stem with applicatio n packages that shar e a common data stor e and comm on interna l services . The data store and VistA ker nel are im plemented in the Mas sachusetts General H ospital Ut ility Mult i-Programm ing System (MUMPS) c omputer la nguage, an d the Comp uterized p atient rec ord System (CPRS) Gr aphical Us er Interfa ce (GUI) i s implemen ted in Del phi. Appli cation cli ents use a highly-ef ficient pr oprietary protocol t o access d ata. VistA is highly configura ble and cu stomizable , and in a ddition to appropria te connect ivity amon gst VistA modules, V istA suppo rts the in tegration of best-of -breed app lications at multipl e levels, including MUMPS, App lication P rogramming Interface (API), Re mote Proce dure Call (RPC), Med ical Domai n Web Serv ices (MDWS ), Health Level 7 (H L7), and d ata exchan ge via Blu e Button o r eHealth Exchanges. VistA com prises nea rly 200 di stinct app lications/ modules, 1 5,000 rout ines, and millions o f lines of computer code. | |
844 | The backbo ne of VHA’ s clinical and admin istrative informatio n technolo gy capabil ity, VistA has histo rically be en built o n a client -server ar chitecture , which ti es togethe r workstat ions and p ersonal co mputers wi th GUIs at VA facili ties. The CPRS GUI i s as highl y customiz able and r uns on wor kstations, laptops, tablets (i ncluding i Pads) and smart phon es. VistA interopera tes with n umerous CO TS softwar e applicat ions and w ith select ed informa tion techn ology syst ems of oth er federal agencies and, incre asingly, h ealth info rmation ex change net works. At the time o f publicat ion of thi s edition of the Mon ograph, co mprehensiv e proposed enhanceme nts to Vis tA were in the initi al stages; referred to as “Vis tA Evoluti on” these enhancemen ts are wil l reflect developmen t and arch itecture e nhancement s to allow greater i nteraction with data and great er efficie ncy for th e VistA sy stem.” | |
845 | Note that the change s required by this p roject are based in the MUMPS computer l anguage an d Delphi/P ascal comp uter langu age for CP RS GUI cha nges (Tabl e 12). | |
846 | GUE code c hanges for CPRS need s to be in cluded in appropriat e version of CPRS: | |
847 | Table 12: Namespaces for MUMPS Codes | |
848 | Workstream | |
849 | CPRS versi on | |
850 | Namespaces for the M UMPS code that will be deliver ed with CP RS | |
851 | Namespaces for the M UMPS code that will be deliver ed separat ely | |
852 | OTH | |
853 | V. 31b | |
854 | OR | |
855 | DG | |
856 | PRF/TIU | |
857 | TBD | |
858 | TIU, OR | |
859 | DG | |
860 | In order t o minimize any negat ive impact on CPSR t eam schedu le and eli minate any dependenc y between CPRS and S HRPE relea ses’ sched ule, the t eam design ed the sol ution(Figu re 15) tha t allows t o release CPRS and S HRPE produ cts indepe ndently: | |
861 | Solution f or the OTH workstrea m: | |
862 | Figure 15: SHRPE OTH Modificat ions | |
863 | ||
864 | Solution f or the PRF workstrea m (Figure 16): | |
865 | ||
866 | Figure 16: SHRPE PRF Modificat ions | |
867 | ||
868 | Network Ar chitecture | |
869 | The DG (Re gistration ), TIU (Te xt Integra tion Utili ty), IB (I ntegrated Billing), and OR (CP RS) applic ations mod ified in t his projec t rely on existing N etwork arc hitecture for VistA. | |
870 | Service Or iented Arc hitecture / ESS | |
871 | The DG (re gistration ), TIU (Te xt Integra tion Utili ty), IB (I ntegrated Billing), and OR (CP RS) applic ations mod ified in t his projec t do not u se Service Oriented Architectu re (SOA)/E nterprise Shared Ser vices (ESS ) (Figure 17). | |
872 | Enterprise Architect ure | |
873 | Figure 17: Enterpris e Architec ture | |
874 | ||
875 | The scope of work do es not int roduce any new tools or techno logies. Th e team wil l use exis ting VistA tools and technolog ies approv ed by the Technical Referance Model (TRM ). | |
876 | Data Desig n | |
877 | The DG (Re gistration ), TIU (Te xt Integra tion Utili ty) and IB (Integrat ed Billing ) modules are part o f the Vist A suite of applicati ons. The D atabase Ma nagement S ystem (DBM S) in use is VA File Man. | |
878 | The VistA The DG (re gistration ), TIU (Te xt Integra tion Utili ty) and IB (Integrat ed Billing ) packages use the s tandard VA FileMan D ata Dictio naries (DD s) and fil es. (See A ppendix A for all da ta diction aries modi fied by th is project .) | |
879 | DBMS Files | |
880 | The VistA The DG (Re gistration ), TIU (Te xt Integra tion Utili ty) IB (In tegrated B illing) pa ckages sto re data in standard VA FileMan files. | |
881 | Logical Mo del | |
882 | Not applic able. This is not a relational database. | |
883 | DBMS Schem as, Subsch emas, Reco rds, Sets, Tables, S torage Pag e Sizes | |
884 | See Append ix A | |
885 | Access Met hods | |
886 | Standard F ileMan API s are used to access data for reading an d writing. Certain f ields are indexed an d indexes are used t o access t he data. | |
887 | Estimate t he Databas e File Siz e | |
888 | Estimate t he databas e file siz e or volum e of data within the file, dat a pages, i ncluding o verhead re sulting fr om access methods an d free spa ce. | |
889 | Figure 14: OTH Eligi bility Clo ck File (# 33) | |
890 | The projec t adds the new file (#33) for the OTH cl ock; the s ize of the file depe nds on the number of patients with the n ew OTH eli gibility. The projec t team has requested this info rmation fr om SMEs an d doesn’t have this informatio n at the m oment. | |
891 | DBRS field s | |
892 | The projec t adds thr ee new fie lds for th e VistA da tabase fil es (#26.13 ) and 6 f ields (#26 .14) to ca pture the DBRS data from the D BRS system . | |
893 | The growth rate of t hese two V istA datab ase files due to sto ring DBRS data depen ds on the number DBR S cases ar e entered yearly in average. | |
894 | The DBRS t eam provid ed the fol lowing inf ormation: | |
895 | Below is t he total n umber of e vents repo rted over the past f our fiscal years (Ta ble 13). | |
896 | Table 13: Events ove r the Past 4 Fiscal Years | |
897 | Fiscal Yea r | |
898 | 2014 | |
899 | 2015 | |
900 | 2016 | |
901 | 2017 | |
902 | Events Rep orted | |
903 | 2,304 | |
904 | 5,857 | |
905 | 19,963 | |
906 | 29,618 | |
907 | The DBRS t eam is not expecting the same rate of gr owth to co ntinue as the years represent the roll o ut of DBRS to all fa cilities. DBRS is re cording ev ents at mo st VHA fac ilities. T he DBRS te am is expe cting to s ee as much as a 10% growth thi s year, un less there are subst antial cha nges to th e practice norms for reporting disruptiv e behavior . They als o expect t o see even ts reporte d to top o ut at abou t 50,000 p er year at some poin t in the f uture. | |
908 | The projec t team is assuming 5 0,000 new DBRS recor ds per yea r for all VA sites ( approximat ely 150 Vi sta databa se instanc es). See T able 14 an d Table 15 . | |
909 | Each new r ecords req uires: | |
910 | Table 14: File #26.1 3, the (#2 6.131) DBR S NO. mult iple | |
911 | Field | |
912 | Type | |
913 | Length (AS CII charac ters/bytes ) | |
914 | (#.01) DBR S NO. | |
915 | Number | |
916 | 18 | |
917 | Separator | |
918 | ||
919 | 1 | |
920 | (#.03) OTH ER DBRS DA TA | |
921 | Free text | |
922 | 60 | |
923 | Separator | |
924 | ||
925 | 1 | |
926 | (#.02) DA TE | |
927 | Fileman Da te | |
928 | 7 | |
929 | Total leng th | |
930 | ||
931 | 87 | |
932 | Table 15: File #26.1 4 | |
933 | Field | |
934 | Type | |
935 | Length (AS CII charac ters/bytes ) | |
936 | (#.07) DBR S NO. | |
937 | Number | |
938 | 18 | |
939 | Separator | |
940 | ||
941 | 1 | |
942 | (#.08) OTHER DBRS DATA | |
943 | Free text | |
944 | 60 | |
945 | Separator | |
946 | ||
947 | 1 | |
948 | (#.09) ORIGINATIN G FACILITY | |
949 | Pointer | |
950 | 10 | |
951 | DBRS NUMBE R 2;0 Mul tiple #26. 142 | |
952 | ||
953 | ||
954 | (#.01) DBR S NO. | |
955 | Number | |
956 | 18 | |
957 | Separator | |
958 | ||
959 | 1 | |
960 | (#.02) OTHER DBRS DATA | |
961 | Free text | |
962 | 60 | |
963 | Separator | |
964 | ||
965 | 1 | |
966 | (#.03) DBR S DATE | |
967 | Fileman Da te | |
968 | 7 | |
969 | Separator | |
970 | ||
971 | 1 | |
972 | (#.04)DBRS OTHER ACT ION | |
973 | Set of cod es | |
974 | 10 | |
975 | Total leng th | |
976 | ||
977 | 188 | |
978 | The yearly growth fo r a single local Vis ta databas e instance is calcul ated as | |
979 | = { [ File (#26.13) total DBRS records s ize + File (#26.14) total DBRS records s ize ] * nu mbers of e xpected n ew DBRS re cords per year} / nu mber of VA sites | |
980 | The yearly growth fo r a single local Vis ta databas e instance = ((87+18 8)*50000)/ 150 = 9166 7 = 92 kby tes/ year | |
981 | Update Fre quency | |
982 | Definition of the up date frequ ency of th e database tables, v iews, file s, areas, records, a nd sets | |
983 | OTH clock file (#33) | |
984 | The projec t adds the new file (#33) for the OTH cl ock, the u pdate freq uency depe nds on the number of patients with the n ew OTH eli gibility. The projec t team has requested this info rmation fr om SMEs an d doesn’t have this informatio n at the m oment. | |
985 | DBRS field s | |
986 | The projec t adds thr ee new fie lds for th e two Vist A database files (#2 6.13) and (#26.14) t o capture the DBRS d ata from t he DBRS sy stem manua lly. | |
987 | The update frequency of these two VistA database f iles due t o storing DBRS data depends on the numbe r DBRS cas es that ar e entered yearly on average. | |
988 | The DBRS t eam expect s to see D BRS events reported top out at about 50, 000 per ye ar in the future. | |
989 | The update frequency for DBRS entries in the singl e local Vi stA databa se instanc e is calcu lated as n umber of n ew DBRS ca ses entere d in VistA local sit e every da y: | |
990 | = Numbers of expecte d new DBRS records p er year / number of VA sites / 365 days | |
991 | Expected n umber of n ew DBRS ca ses entere d in VistA local sit e every da y is 50000 /150/365 = 0.91 | |
992 | Estimates on the Num ber of Tra nsactions | |
993 | Estimates on the num ber of tra nsactions that the d atabase ma y have to process. | |
994 | OTH clock file (#33) | |
995 | The projec t adds the new file (#33) for the OTH cl ock, the n umber of t ransaction s depends on the num ber of pat ients with the new O TH eligibi lity. The project te am has req uested thi s informat ion from S MEs and do esn’t have this info rmation at the momen t. | |
996 | DBRS field s | |
997 | The projec t adds thr ee new fie lds for th e two Vist A database files (#2 6.13) and (#26.14) t o capture the DBRS d ata from t he DBRS sy stem manua lly. | |
998 | The number of transa ctions for these two VistA dat abase file s due to s toring DBR S data dep ends on th e number D BRS cases are entere d yearly i n average. | |
999 | The DBRS t eam expect s to see D BRS events reported top out at about 50, 000 per ye ar in the future. | |
1000 | The number of transa ctions for DBRS entr ies in the single lo cal VistA database i nstance is calculate d as numbe r of new D BRS cases in both fi les entere d in VistA local sit e every ye ar: | |
1001 | = 2 files * (Numbers of expect ed new DBR S records per year / number of VA sites) | |
1002 | Expected n umber of t ransaction s processe d in a sin gle VistA local site every yea r for DBRS records i s 2*50000/ 150 = 667 | |
1003 | Non-DBMS F iles | |
1004 | Not applic able. No c hanges or updates No n-DBMS fil es are ant icipated. | |
1005 | Data View | |
1006 | Not applic able. The VistA data base that is used in the proje ct is MUMP S based no n-relation al databas e. | |
1007 | Detailed D esign | |
1008 | The detail ed design will be up dated as d esign and developmen t continue s; this se ction will be update d and incl uded with later vers ions of th is System Design Doc ument (SDD ). Blank s ections ha ve been ma intained f or version control. | |
1009 | Hardware D etailed De sign | |
1010 | This proje ct does no t require any change s to the e xisting ha rdware. Th ese enhanc ements may require a n addition al amount of storage for the n ew files d escribed a bove. Furt her analys is will be done as a part of t he Systems Engineeri ng and Des ign Review . | |
1011 | Software D etailed De sign | |
1012 | The follow ing softwa re must be installed prior to the releas e of this product: | |
1013 | InterSyste ms Mumps V ersion Cac he 2014.1. 3 Ad Hoc 1 4809 | |
1014 | VA FileMan Version 2 2.2 | |
1015 | VistA Kern el Version 8.0 | |
1016 | VistA Mail Man Versio n 8.0 | |
1017 | VistA Fee Basis Vers ion 3.5 | |
1018 | Vista IB V ersion 2.0 | |
1019 | VistA Regi stration V ersion 5.3 | |
1020 | VistA CPRS Version 3 1b (the ve rsion that will be u sed as a b aseline fo r the rele ase needs to be dete rmined) | |
1021 | Other tool s utilized during de velopment and testin g: | |
1022 | Rational T eam Concer t: Release 6.0 (VA N etwork-wid e version) | |
1023 | Conceptual Design | |
1024 | The projec t modifies the exist ing Vista applicatio ns DG (Reg istration) , TIU (Tex t Integrat ion Utilit y) IB (Int egrated Bi lling), an d CPRS by using stan dard VistA developme nt tools a pproved by TRM like FileMan da ta diction aries and APIs, Kern el infrast ructure to ols and AP Is, ListMa n, RPCs, H ealth Leve l Seven Op timized (H LO) applic ation for HL7 messag ing. | |
1025 | The access to other namespaces is contro lled via I CRs in FOR UM. | |
1026 | The softwa re code is released by using t he standar d VistA Cl ass 1 rele ase proces s by issui ng patches and regis tering the m in FORUM . | |
1027 | Product Pe rspective | |
1028 | The portio n of the V istA Regis tration (D G) applica tion that is modifie d by the p roject int eracts wit h the exte rnal Enrol lment Syst em (ES) an d Master V eteran Ind ex (MVI) s ystems. No te: the pr oject does n’t make m odificatio ns to thes e interfac es. It als o interact s with CPR S via RPCs . | |
1029 | The portio n of the V istA Integ rated Bill ing (IB) a pplication that is m odified by the proje ct doesn’t interact with exter nal applic ations. It interacts with mult iple VistA applicati ons like R egistratio n, Outpati ent Pharma cy, Schedu ling, CMOP , and AR v ia registe red API ca lls (ICRs) . | |
1030 | User Inter faces | |
1031 | This proje ct doesn’t introduce any new i nterfaces. It modifi es existin g interfac es for CPR S users an d Registra tion users . | |
1032 | For the CP RS GUI use r interfac e changes, please re fer to the SDD secti ons: | |
1033 | 6.2.2.3.17 .1. For fF rame | |
1034 | 6.2.2.3.17 .2. For Pt SelDemog | |
1035 | 6.2.2.3.18 .1. For fF rame | |
1036 | 6.2.2.3.18 .2. For fP tSelDemog | |
1037 | For the Re gistration roll and scroll use r interfac e changes, please re fer to the SDD secti on: | |
1038 | 3.2.3.1.1. DGPF RECO RD FLAG AS SIGNMENT m enu option | |
1039 | Hardware I nterfaces | |
1040 | Communicat ions betwe en VistA s ites pass through th e Local Ar ea Network s (LANs) a nd across the VA int ranet. | |
1041 | Software I nterfaces | |
1042 | The follow ing softwa re must be installed prior to the releas e of this product: | |
1043 | InterSyste ms Mumps V ersion Cac he 2014.1. 3 Ad Hoc 1 4809 | |
1044 | VA FileMan Version 2 2.2 | |
1045 | VistA Kern el Version 8.0 | |
1046 | VistA Mail Man Versio n 8.0 | |
1047 | VistA Fee Basis Vers ion 3.5 | |
1048 | Vista IB V ersion 2.0 | |
1049 | VistA Regi stration V ersion 5.3 | |
1050 | VistA CPRS Version 3 1b (the ve rsion that will be u sed as a b aseline fo r the rele ase needs to be dete rmined) | |
1051 | Other tool s utilized during de velopment and testin g: | |
1052 | Rational T eam Concer t: Release 6.0 (VA N etwork-wid e version) | |
1053 | Communicat ions Inter faces | |
1054 | The portio n of the V istA Regis tration (D G) applica tion that is modifie d by the p roject wil l modify t he existin g HL7 mess ages that are used t o send inf ormation b etween VA sites. | |
1055 | The projec t doesn't make any m odificatio ns to the HL7 applic ation that is respon sible for HL7 messag es process ing. | |
1056 | The portio n of the V istA Regis tration (D G) applica tion that is modifie d by the p roject wil l introduc e the new RPCs to se t the OTH clock and get the OT H clock da ta. The RP C will be used by th e CPSR GUI software to display the OTH s tatus on t he screen. | |
1057 | The projec t will als o modify t he existin g TIU RPCs to set se nd facilit y informat ion to CPR S. | |
1058 | The projec t doesn't make any m odificatio ns to the VistA soft ware handl es RPC cal ls with CP RS GUI. | |
1059 | Memory Con straints | |
1060 | There are no memory constraint s associat ed with th is project . | |
1061 | Special Op erations | |
1062 | There are no special operation s associat ed with th is project . | |
1063 | Product Fe atures | |
1064 | The projec t modifies the exist ing Vista applicatio ns DG (Reg istration) , TIU (Tex t Integrat ion Utilit y) IB (Int egrated Bi lling), an d CPRS. | |
1065 | Patient Re cord Flag Workstream | |
1066 | This part of the pro ject modif ies the ex isting Vis tA applica tion DG (R egistratio n) to prov ide the fo llowing fu nctionalit y: | |
1067 | Improve an d fix issu es with th e HL7 mess aging proc ess which is suppose d to keep the PRF da ta in sync h amongst VistA inst ances and occasional ly fails. | |
1068 | After this proposed enhancemen t, the roo t cause of the HL7 m essaging f ailures fo r PRFs in the busine ss scenari os provide d, will be rectified , tested a nd impleme nted. | |
1069 | Inactive N ational Ca tegory 1 P RFs HRfS w ill be ele ctronicall y transfer red to a r equesting facility v ia one rea ssignment step. Acti ve Categor y 1 PRFs H RfS will b e electron ically req uested to have their ownership transferr ed, the re quest will be Accept ed or Reje cted and O wnership w ill transf er electro nically or will rema in assigne d to its c urrent fac ility. | |
1070 | The bottom portion o f the ‘Pro gress Note s Properti es’ pop up box in CP RS which d isplays un linked fla g actions, will be f iltered to only disp lay unlink ed flag ac tions whic h ‘belong’ to the sa me facilit y as the l ogged-in u ser. | |
1071 | Implement the direct ive to NOT make the linking of a progres s note to a flag act ion, manda tory. It will still be techni cally poss ible, but it will ju st not be mandatory within the business process. B ecause inf ormation f rom the cu rrent prog ress note linkage to a Nationa l Category 1 Behavio r PRF, for example, flows down stream int o the MyHe altheVet s ystem, thi s has caus ed stress to patient s who see that a ‘Be havioral’ PRF has be en placed on their p atient rec ord. | |
1072 | New fields will be p laced on t he Nationa l Category 1 ‘Behavi oral’ PRF to capture ‘DBRS Cas e Number,’ ‘DBRS dat e’, ‘Other DBRS info rmation’ a nd ‘DBRS a ction.’ Th is will al low health care prov iders with in the VHA Workplace Violence Program th e ability to link a Patient’s Behavioral PRF with a case num ber(s) fro m the VA’s Disruptiv e Behavior al Reporti ng System. These DBR S case num bers have no meaning to the pa tients and should in duce no un necessary emotional stress. Th ese fields will be a dded to ex isting Rec ord Flag A ssignment options/sc reens as w ell as to the PRF hi story file . The repo rt criteri a will be updated on the Assig nment Acti on Not Lin ked report to includ e new/diff erent opti ons. | |
1073 | Copayment Modificati ons Workst ream | |
1074 | This part of the pro ject modif ies the ex isting Vis tA applica tion IB (I ntegrated Billing) t o provide the follow ing functi onality: | |
1075 | -Exempt th e HRfS pa tients fro m outpatie nt visit c opays. | |
1076 | -Apply pro -rated cop ay amounts for the HRfS patie nts when t hey were t he origina l medicati on was bro ken down i nto severa l refills less than 30 days ea ch | |
1077 | Other Than Dishonora ble Discha rge Modifi cations Wo rkstream | |
1078 | This part of the pro ject modif ies the ex isting Vis tA applica tion DG (R egistratio n) to prov ide the fo llowing fu nctionalit y: | |
1079 | Add the ne w “Other T han Honora ble” (OTH) eligibili ty to the Registrati on (DG) ap plication so it can be selecte d only as the second ary/other eligibilit y for the patient an d used to track pati ent eligib ility | |
1080 | Track the OTH eligib ility 90 d ays and 36 5 days per iods for t he patient in the OT H clock (s et the clo ck, reset the clock) | |
1081 | Capture th e authoriz ation for the 2nd 90 days peri od in the database. | |
1082 | Capture ur gent menta l health r elated tre atment in the databa se. | |
1083 | Display th e OTH cloc k informat ion on the CPRS scre en. | |
1084 | User Chara cteristics | |
1085 | The resour ces that s hall work with the I B need to be knowled geable in the copay calculatio n. | |
1086 | The resour ces that s hall work with the R egistratio n (DG) nee d to be kn owledgeabl e in the a rea of | |
1087 | making dec ision of a ssigning e ligibiliti es to the patient, | |
1088 | entering/e diting PRF informati on, transf erring PRF ownership to anothe r site | |
1089 | The resour ces that s hall work with the R egistratio n (DG) nee d to be kn owledgeabl e in the p olicies an d process of authori zing the O TH eligibi lity. | |
1090 | Dependenci es and Con straints | |
1091 | Regulatory policies: Policies that regu late the c opays have not been approved b y the gove rnment yet . The IB p atch will be release d as a dor mant code that will require an other acti vation pat ch to be r eleased wh en the eff ective dat e becomes known. The project i mplements the switch that can turn the f unctionali ty ON by r eleasing t he “inform ational” p atch with instructio ns and the effective date. | |
1092 | Parallel o peration: The CPRS changes ne ed to be i ncluded in the appro priate CPR S release. | |
1093 | Interfaces with othe r applicat ions: The team need s to get a pprovals f or ICRs an d HL7 mess age modifi cations. | |
1094 | VA Standar ds and Con ventions f or MUMPS d evelopment . | |
1095 | VA Technic al Referen ce Model ( TRM). | |
1096 | Specific R equirement s | |
1097 | Please see Section 2 .3.1. Over view of Fu nctional R equirement s. | |
1098 | Database R epository | |
1099 | Patient Re cord Flag Workstream | |
1100 | Please ref er to the section 3. 2.1.1. PRF /TIU works tream for the Logica l database design. | |
1101 | lists the new field s added to the datab ase. | |
1102 | Table 16: New Fields Added to the Databa se | |
1103 | VistA file | |
1104 | Field | |
1105 | Type of in formation | |
1106 | Frequency of use | |
1107 | Requiremen t | |
1108 | PRF ASSIGN MENT | |
1109 | (#.01) DBR S NO. of t he (#2) DB RS NO. mul tiple | |
1110 | The DBRS # from the DBRS syste m | |
1111 | See the se ction 5.1. 5.Update f requency | |
1112 | B1S1 PRF T IU: As a d eveloper, I need to develop th e new Data Dictionar y fields i n VistA fo r DBRS so that I can test entr y of DBRS Case Numbe rs and Oth er informa tion on a Nat Catego ry 1 PRF. | |
1113 | PRF ASSIGN MENT | |
1114 | (#.02) OTH ER of the (#2) DBRS NO. multip le | |
1115 | Other DBRS informati on from th e DBSR sys tem | |
1116 | See the se ction 5.1. 5.Update f requency | |
1117 | B1S1 PRF T IU: As a d eveloper, I need to develop th e new Data Dictionar y fields i n VistA fo r DBRS so that I can test entr y of DBRS Case Numbe rs and Oth er informa tion on a Nat Catego ry 1 PRF. | |
1118 | PRF ASSIGN MENT | |
1119 | (#.03) DAT E of the ( #2) DBRS N O. multipl e | |
1120 | The DBRS d ate from t he DBRS sy stem | |
1121 | See the se ction 5.1. 5.Update f requency | |
1122 | B1S1 PRF T IU: As a d eveloper, I need to develop th e new Data Dictionar y fields i n VistA fo r DBRS so that I can test entr y of DBRS Case Numbe rs and Oth er informa tion on a Nat Catego ry 1 PRF. | |
1123 | PRF ASSIGN MENT HISTO RY | |
1124 | (#.07) DBR S NO. | |
1125 | The DBRS # from the DBRS syste m | |
1126 | See the se ction 5.1. 5.Update f requency | |
1127 | B1S1 PRF T IU: As a d eveloper, I need to develop th e new Data Dictionar y fields i n VistA fo r DBRS so that I can test entr y of DBRS Case Numbe rs and Oth er informa tion on a Nat Catego ry 1 PRF. | |
1128 | PRF ASSIGN MENT HISTO RY | |
1129 | (#.08) OTH ER DBRS DA TA | |
1130 | Other DBRS informati on from th e DBSR sys tem | |
1131 | See the se ction 5.1. 5.Update f requency | |
1132 | B1S1 PRF T IU: As a d eveloper, I need to develop th e new Data Dictionar y fields i n VistA fo r DBRS so that I can test entr y of DBRS Case Numbe rs and Oth er informa tion on a Nat Catego ry 1 PRF. | |
1133 | PRF ASSIGN MENT HISTO RY | |
1134 | (#.09) ORI GINATING F ACILITY | |
1135 | Originatin g facility | |
1136 | See the se ction 5.1. 5.Update f requency | |
1137 | B2S1 PRF T IU - As a VHA team m ember, I n eed to see the value of 'unkno wn' for an y flag act ion listed in the Pr ogress Not es Propert ies box if the origi nating sit e is not k nown. | |
1138 | Copayment Modificati ons Workst ream | |
1139 | Please ref er to sect ion 3.2.1. 2. Copays Workstream for the c urrent Log ical datab ase design . | |
1140 | The new fi eld (#70.0 2) SHRPE ACTIVATION DATE in t he IB SITE S PARAMETE RS FILE (# 350.9) wa s added in the Sprin t 1 of Bu ild 2. Ple ase see de tails abou t its curr ent implem entation i n the Appe ndix A. | |
1141 | ||
1142 | Other Than Dishonora ble Discha rge Modifi cations Wo rkstream | |
1143 | Please ref er to sect ion 3.2.1. 3. Other T han Dishon orable Dis charge (OT H) Workstr eam for th e current Logical da tabase des ign. | |
1144 | The new fi le (#33) O TH ELIGIBI LITY CLOCK was added to the da tabase. Pl ease see d etails abo ut its cur rent imple mentation in the App endix A. | |
1145 | System Fea tures | |
1146 | System fea tures intr oduced by the projec t will imp lement the requireme nts listed in sectio n 2.3.1. O verview of Functiona l Requirem ents. | |
1147 | Design Ele ment Table s | |
1148 | Informatio n in the s ections be low provid es details about the implement ation for specific s oftware co mponents. | |
1149 | Routines ( Entry Poin ts) | |
1150 | Routine ch anges belo w are grou ped by wor ksterams. | |
1151 | Other Than Dishonora ble Discha rge Modifi cations Wo rkstream | |
1152 | Note: The sections p rovides th e code for major API s implemen ted for th e workstre am. | |
1153 | The M-rout ine below implements the Get m ethod (Tab le 17) use d by the R PC to prov ide OTH cl ock data t o CPRS scr een to dis play the O TH clock. | |
1154 | Table 17: OTHDCLCK M ethod | |
1155 | Routines | |
1156 | Activities | |
1157 | Routine Na me | |
1158 | OTHDCLCK^D GOTHD | |
1159 | Enhancemen t Category | |
1160 | New | |
1161 | Modify | |
1162 | Delete | |
1163 | No Change | |
1164 | RTM | |
1165 | Sub Epic 9 60012 | |
1166 | Related Op tions | |
1167 | None | |
1168 | ||
1169 | Related Ro utines | |
1170 | Routines “ Called By” | |
1171 | Routines “ Called” | |
1172 | ||
1173 | None | |
1174 | None | |
1175 | ||
1176 | Routines | |
1177 | Activities | |
1178 | Data Dicti onary (DD) Reference s | |
1179 | OTH ELIGIB ILITY CLOC K FILE (#3 3) | |
1180 | Related Pr otocols | |
1181 | None | |
1182 | Related In tegration Control Re gistration s (ICRs) | |
1183 | None | |
1184 | Data Passi ng | |
1185 | Input | |
1186 | Output Re ference | |
1187 | Both | |
1188 | Global Re ference | |
1189 | Local | |
1190 | Input Attr ibute Name and Defin ition | |
1191 | Parameters : | |
1192 | DGDFN - t he patient 's IEN in the file ( #2) | |
1193 | DGDATE - the date t o calculat e status | |
1194 | default = DT (today | |
1195 | Output Att ribute Nam e and Defi nition | |
1196 | Name: RET | |
1197 | Return va lues: ret urn 0 if patient i s not elig ible for O THD in reg istration if patient does not have an en try in the OTHD cloc k file (#3 3) Retur ns the inf ormation t o display informatio n about th e OTHD clo ck The re turn strin g is of th e followin g format: if some k ind of err or conditi on is enco untered, r eturn -1^error m essage el se return p1^p2^p3^p 4^p5^p6^p7 ^p8 where: p1 = 1 . . n 1..n - the late st sequenc e number o f the 365 period p2 = 1,2,or 3 1 if th e patient is in the first 90 d ay period 2 if the patient is in the se cond 90 da y period 3 if the p atient has used all 180 days i n this 365 day perio d p3 = FM date for the start of the clo ck for the first 90 day period p4 = FM date for t he end of the clock for the fi rst 90 day period p 5 = the nu mber of da ys left in the first 90 day pe riod p6 = FM date f or the sta rt of the clock for the second 90 day pe riod p7 = FM date f or the end of the cl ock for th e second 9 0 day peri od p8 = t he number of days le ft in the second 90 day period p9 = FM date of th e authoriz ation for the 2nd pe riod (null if no aut horization ) | |
1198 | ||
1199 | Current Lo gic | |
1200 | Not applic able. | |
1201 | ||
1202 | Modified L ogic (Chan ges are in bold) | |
1203 | ;Function ality: ; I mplements ICR# 6873 ; This fun ction is c alled from GET^OROTH CL to supp ort ; the "OR OTHD C LOCK GET" RPC ;It ch ecks if th e patient is eligibl e for OTHD ;and retu rns the OT HD status on the giv en date ; ; ;Paramet ers: ; DGD FN - the p atient's I EN in the file (#2) ; DGDATE - the date to calcula te status ; default = DT (toda y) ; ;Retu rn values: ; ;return 0 ; if p atient is not eligib le for OTH D in regis tration ; if patient does not have an en try in the OTHD cloc k file (#3 3) ; ; ;Re turns the informatio n to displ ay informa tion about the OTHD clock ;Th e return s tring is o f the foll owing form at: ; if s ome kind o f error co ndition is encounter ed, return ; -1^e rror messa ge ; else return p1^ p2^p3^p4^p 5^p6^p7^p8 where: ; p1 = 1 .. n ; 1..n - the lates t sequence number of the 365 p eriod ; p2 = 1,2,or 3 ; 1 if t he patient is in the first 90 day period ; 2 if th e patient is in the second 90 day period ; 3 if th e patient has used a ll 180 day s in this 365 day pe riod ; p3 = FM date for the st art of the clock for the first 90 day pe riod ; p4 = FM date for the en d of the c lock for t he first 9 0 day peri od ; p5 = the number of days l eft in the first 90 day period ; p6 = FM date for the start of the clo ck for the second 90 day perio d ; p7 = F M date for the end o f the cloc k for the second 90 day period ; p8 = th e number o f days lef t in the s econd 90 d ay period ; p9 = FM date of th e authoriz ation for the 2nd pe riod (null if no aut horization ) ; | |
1204 | OTHDCLCK(D GDFN,DGDAT E) ; N DGN ,RET,DGIEN 33,DGRET,D GLS365D,DG LS365I,DG9 0A,DGARR,D GDIF N DGP 0,DGP1,DGP 2,DGP3,DGP 4,DGP5,DGP 6,DGP7,DGP 8,DGP9,DGA UTH I $$IS OTHD^DGOTH D(DGDFN)=0 Q 0 S DGD ATE=$S($G( DGDATE)>0: DGDATE,1:D T) S DGIEN 33=+$O(^DG OTH(33,"B" ,DGDFN,0)) I DGIEN33 =0 Q "0" D GETS^DIQ( 33,DGIEN33 _",",".01; .02;.03;1* ","I","DGA RR") I $G( DGARR(33,D GIEN33_"," ,.02,"I")) '=1 Q 0 ;n ot eligibl e for OTHD because O THD clock has been i nactivated I $G(DGAR R(33,DGIEN 33_",",.03 ,"I"))=1 Q 0 ;not el igible for OTHD beca use VBA AD JUDICATION has been COMPLETED S DGLS365D =+$O(^DGOT H(33,DGIEN 33,1,"B",9 99),-1) I DGLS365D'> 0 Q "-1^no 365 days clocks sta rted" S DG LS365I=+$O (^DGOTH(33 ,DGIEN33,1 ,"B",DGLS3 65D,0)) S DGN=0 F S DGN=+$O(^ DGOTH(33,D GIEN33,1,D GLS365I,1, "B",DGN)) Q:DGN=0 S DG90A(DGN) =+$O(^DGOT H(33,DGIEN 33,1,DGLS3 65I,1,"B", DGN,0)) I '$D(DG90A) Q "-1^the re are no 90 days pe riods for the 365 da ys period # "_DGLS36 5D I '$D(D G90A(1)) Q "-1^missi ng the 1st 90 days p eriod for the 365 da ys period # "_DGLS36 5D I $O(DG 90A(2)) Q "-1^there are more t han two 90 days peri ods for th e 365 days period # "_DGLS365D S (DGP0,D GP1,DGP2,D GP3,DGP4,D GP5,DGP6,D GP7,DGP8,D GP9,DGAUTH )="" S DGP 1=DGLS365D ;calculat ion for th e 1st 90 d ays period S DGP3=$G (DGARR(33. 11,DG90A(1 )_","_DGLS 365I_","_D GIEN33_"," ,.02,"I")) ,DGP4=$$FM ADD^XLFDT( DGP3,90),D GDIF=$$FMD IFF^XLFDT( DGP4,DGDAT E,1),DGP5= $S(DGDIF>0 :DGDIF,1:0 ) ;calcula tion for t he 2nd 90 days perio d if any I $D(DG90A( 2)) D . S DGP6=$G(DG ARR(33.11, DG90A(2)_" ,"_DGLS365 I_","_DGIE N33_",",.0 2,"I")) I DGP6>0 S D GP7=$$FMAD D^XLFDT(DG P6,90),DGD IF=$$FMDIF F^XLFDT(DG P7,DGDATE, 1),DGP8=$S (DGP5>0:90 ,DGDIF>0:D GDIF,1:0) . S DGAUTH =$G(DGARR( 33.11,DG90 A(2)_","_D GLS365I_", "_DGIEN33_ ",",.03,"I ")) . I DG AUTH'="" S DGP9=$P($ G(DGARR(33 .11,DG90A( 2)_","_DGL S365I_","_ DGIEN33_", ",.04,"I") ),".") S D GP2=$S(((D GP5=0)&($D (DG90A(2)) &(DGP6>0)) &(DGP8=0)) :3,($D(DG9 0A(2))&(DG P6>0)):2,' $D(DG90A(1 )):-1,DGP3 '>0:-1,1:1 ) I DGP5>0 S DGP2=1 S DGRET=DG P1_U_DGP2_ U_DGP3_U_D GP4_U_DGP5 _U_DGP6_U_ DGP7_U_DGP 8_U_DGP9 Q DGRET ; | |
1205 | The M-rout ine below implements the FRSTC LCK method (Table 18 ) used by Registrati on [DG LOA D EDIT SCR EEN 7] ca reen to se t the OTH clock data . | |
1206 | Table 18: FRSTCLCK Method | |
1207 | Routines | |
1208 | Activities | |
1209 | Routine Na me | |
1210 | FRSTCLCK^D GOTHD1 | |
1211 | Enhancemen t Category | |
1212 | New | |
1213 | Modify | |
1214 | Delete | |
1215 | No Change | |
1216 | RTM | |
1217 | Sub Epic 9 60011 | |
1218 | Related Op tions | |
1219 | None | |
1220 | ||
1221 | Related Ro utines | |
1222 | Routines “ Called By” | |
1223 | Routines “ Called” | |
1224 | ||
1225 | None | |
1226 | None | |
1227 | ||
1228 | Routines | |
1229 | Activities | |
1230 | Data Dicti onary (DD) Reference s | |
1231 | OTH ELIGIB ILITY CLOC K FILE (#3 3) | |
1232 | Related Pr otocols | |
1233 | None | |
1234 | Related In tegration Control Re gistration s (ICRs) | |
1235 | None | |
1236 | Data Passi ng | |
1237 | Input | |
1238 | Output Re ference | |
1239 | Both | |
1240 | Global Re ference | |
1241 | Local | |
1242 | Input Attr ibute Name and Defin ition | |
1243 | Parameters : DGDFN - patient IE N DGSTRTDT - startin g date | |
1244 | Output Att ribute Nam e and Defi nition | |
1245 | Return va lues: <0 if error 1 if every thing was created pr operly | |
1246 | ||
1247 | Current Lo gic | |
1248 | Not applic able. | |
1249 | ||
1250 | Modified L ogic (Chan ges are in bold) | |
1251 | ;Set the very first clock ;P arameters: ; DGDFN - patient I EN ; DGSTR TDT - star ting date ;Return va lues: ; <0 if error ; 1 if eve rything wa s created properlyFR STCLCK(DGD FN,DGSTRDT ) ; N DGIE N33,DGIEN3 65,DGIEN90 ;does the patient h ave the cl ock? S DGI EN33=$$HAS CLOCK^DGOT HD2(DGDFN) I DGIEN33 >0 Q -2 ; already ha s clock ;i f not then create it I DGIEN33 =0 S DGIEN 33=$$CROTH CLK^DGOTHD 2(DGDFN) ; if error t hen return error I D GIEN33<0 Q DGIEN33 ; create the very firs t 365 days clock S D GIEN365=$$ CR365CLK^D GOTHD2(+DG IEN33,1,DG STRDT) ;if error the n return e rror I DGI EN365<0 Q DGIEN365 ; create the very firs t 90 days clock S DG IEN90=$$CR 90CLK^DGOT HD2(+DGIEN 33,+DGIEN3 65,1,DGSTR DT) ;if er ror then r eturn erro r I DGIEN9 0<0 Q DGIE N90 Q 1 ; | |
1252 | The M-rout ine (Table 19) imple ments the post-insta ll code fo r the patc h DG*5.3*9 52 that ad ds the new eligibili ty code to the file (#8): | |
1253 | Table 19: M Routine | |
1254 | Routines | |
1255 | Activities | |
1256 | Routine Na me | |
1257 | ^DG53P952 | |
1258 | Enhancemen t Category | |
1259 | New | |
1260 | Modify | |
1261 | Delete | |
1262 | No Change | |
1263 | RTM | |
1264 | Epic 95998 6, Sub Epi c 959988 | |
1265 | Related Op tions | |
1266 | None | |
1267 | ||
1268 | Related Ro utines | |
1269 | Routines “ Called By” | |
1270 | Routines “ Called” | |
1271 | ||
1272 | None | |
1273 | None | |
1274 | ||
1275 | Routines | |
1276 | Activities | |
1277 | Data Dicti onary (DD) Reference s | |
1278 | The ELIGIB LITY CODE file (#8) | |
1279 | Related Pr otocols | |
1280 | None | |
1281 | Related In tegration Control Re gistration s (ICRs) | |
1282 | None | |
1283 | Data Passi ng | |
1284 | Input | |
1285 | Output Re ference | |
1286 | Both | |
1287 | Global Re ference | |
1288 | Local | |
1289 | Input Attr ibute Name and Defin ition | |
1290 | None | |
1291 | ||
1292 | Output Att ribute Nam e and Defi nition | |
1293 | None | |
1294 | ||
1295 | ||
1296 | Current Lo gic | |
1297 | Not applic able. | |
1298 | Modified L ogic (Chan ges are in bold) | |
1299 | DG53P952 ; SLC/SS - P OST-INIT ; 12/05/17 ; ;5.3;Regis tration;** 952**;Aug 13, 1993;B uild 29 ; ;DG*5.3*95 2 post - i nstall ent ry point ; ;ICRs Use d: ;DBIA # 10141 XPDU TL ;DBIA # 2053 Data Base Serve r API: Edi ting Utili tiesEN ; ; skip addin g the new eligibilit y to the f ile #8 if it is alre ady there I $O(^DIC( 8,"B","OTH ER THAN HO NORABLE",0 ))>0 D Q .D BMES^XP DUTL("The OTHER THAN HONORABLE already e xists in t he file #8 - ") .D M ES^XPDUTL( " skip add ing OTHER THAN HONOR ABLE eligi bility to the file # 8.") ; ;ot herwise ad d the new eligibilit y to the f ile #8 N D GVALS,DGIE N D BMES^X PDUTL("Add ing OTHER THAN HONOR ABLE eligi bility ent ry to the file #8") S DGVALS(. 01)="OTHER THAN HONO RABLE" S D GVALS(1)=" RED" S DGV ALS(2)="OT H" S DGVAL S(3)=6 S D GVALS(4)=" N" S DGVAL S(5)="OTHE R THAN HON ORABLE" S DGVALS(7)= 1 S DGVALS (8)="OTHER THAN HONO RABLE" S D GVALS(9)=" VA STANDAR D" S DGVAL S(11)="VA" S DGVALS( 12)="YES" S DGIEN=$$ INSREC(8," ",.DGVALS, ,"E",,,1) I DGIEN<0 D . D BMES ^XPDUTL("E rror:") . D BMES^XPD UTL(" the OTHER THAN HONORABLE eligibili ty was not added to the file # 8: ") . D MES^XPDUTL (" "_$P(DG IEN,U,2)) ; I $O(^DI C(8,"B","O THER THAN HONORABLE" ,0))>0 D Q .D BMES^ XPDUTL("Th e OTHER TH AN HONORAB LE eligibi lity has b een added to the fil e #8 succe ssfully.") Q ; ; | |
1300 | ;/** ;Cre ates a new entry (or node for multiple w ith .01 fi eld) ; ;DG FILE - fil e/subfile number ;DG IEN - ien of the par ent file e ntry in wh ich the ne w subfile entry will be insert ed ;DGZFDA - array w ith values for the f ields ; fo rmat for D GZFDA: ; D GZFDA(.01) =value for #.01 fiel d ; DGZFDA (3)=value for #3 fie ld ;DGRECN O -(option al) specif y IEN if y ou want sp ecific val ue ; Note: "" then t he system will assig n the entr y number i tself. ;DG FLGS - FLA GS paramet er for UPD ATE^DIE ;D GLCKGL - f ully speci fied globa l referenc e to lock ;DGLCKTM - time out for LOCK, if LOCKTIM E=0 then t he functio n will not lock the file ;DGN EWRE - opt ional, fla g = if 1 t hen allow to create a new top level reco rd ; ;ou tput : ; p ositive nu mber - rec ord # crea ted ; <=0 - failure^ error mess age ; ;Exa mple: ;S D GVALS(.01) ="OTHD" W $$INSREC^D G53952(8.1 ,"",.DGVAL S,,,,,1)IN SREC(DGFIL E,DGIEN,DG ZFDA,DGREC NO,DGFLGS, DGLCKGL,DG LCKTM,DGNE WRE) ;*/ I ('$G(DGFI LE)) Q "0^ Invalid pa rameter" I +$G(DGNEW RE)=0 I $G (DGRECNO)> 0,'$G(DGIE N) Q "0^In valid para meter" N D GSSI,DGIEN S,DGERR,DG FDA,DIERR N DGLOCK S DGLOCK=0 I '$G(DGRE CNO) N DGR ECNO S DGR ECNO=$G(DG RECNO) I D GIEN'="" S DGIENS="+ 1,"_DGIEN_ "," I $L(D GRECNO)>0 S DGSSI(1) =+DGRECNO I DGIEN="" S DGIENS= "+1," I $L (DGRECNO)> 0 S DGSSI( 1)=+DGRECN O M DGFDA( DGFILE,DGI ENS)=DGZFD A I $L($G( DGLCKGL)) L +@DGLCKG L:(+$G(DGL CKTM)) S D GLOCK=$T I 'DGLOCK Q -2 ;lock failure D UPDATE^DIE ($G(DGFLGS ),"DGFDA", "DGSSI","D GERR") I D GLOCK L -@ DGLCKGL I $D(DGERR) Q "-1^"_$G (DGERR("DI ERR",1,"TE XT",1),"Up date Error ") Q +$G(D GSSI(1)) ; | |
1301 | The M-rout ine () imp lements th e CPRS MUM PS code to provide O TH status for the RP C : | |
1302 | Table 20: FRSTCLCK Method | |
1303 | Routines | |
1304 | Activities | |
1305 | Routine Na me | |
1306 | GET^OROTHC L | |
1307 | Enhancemen t Category | |
1308 | New | |
1309 | Modify | |
1310 | Delete | |
1311 | No Change | |
1312 | RTM | |
1313 | Sub Epic 9 60011 | |
1314 | Related Op tions | |
1315 | None | |
1316 | ||
1317 | Related Ro utines | |
1318 | Routines “ Called By” | |
1319 | Routines “ Called” | |
1320 | ||
1321 | None | |
1322 | None | |
1323 | ||
1324 | Routines | |
1325 | Activities | |
1326 | Data Dicti onary (DD) Reference s | |
1327 | OTH ELIGIB ILITY CLOC K FILE (#3 3) | |
1328 | Related Pr otocols | |
1329 | None | |
1330 | Related In tegration Control Re gistration s (ICRs) | |
1331 | 6873 | |
1332 | Data Passi ng | |
1333 | Input | |
1334 | Output Re ference | |
1335 | Both | |
1336 | Global Re ference | |
1337 | Local | |
1338 | Input Attr ibute Name and Defin ition | |
1339 | Parameters : DGDFN - patient IE N DGSTRTDT - startin g date | |
1340 | Output Att ribute Nam e and Defi nition | |
1341 | Return va lues: <0 if error 1 if every thing was created pr operly | |
1342 | ||
1343 | Current Lo gic | |
1344 | Not applic able. | |
1345 | ||
1346 | Modified L ogic (Chan ges are in bold) | |
1347 | OROTHCL ;S LC/SS/RM - OTHD CLOC K INTERFAC E ;11/27/2 017 ;;3.0; ORDER ENTR Y/RESULTS REPORTING; **437**;De c 17, 1997 ;Build 4 ; ; ;Functi onality: ; This funct ion is cal led from t he "OR OTH D CLOCK GE T" RPC ; ; ICR: ; Sup ports the ICR# 6873 ; between DG (custod ial) and O R (subscri ber) names paces ; ;P arameters: ; RET - r eference t ype parame ter to ret urn data ; DFN - pat ient's IEN in the fi le (#2) ; ORDATE - t he date to calculate status ; default = DT (today) ; ; RET(0 ) - contai ns the num ber of arr ay element s with dat a ; RET(1) - contain s all the informatio n the clie nt needs ; to displa y informat ion about the OTHD c lock witho ut the cli ent having to ; do a ny calcula tions. The return st ring is of the follo wing forma t: ;If som e kind of error cond ition is e ncountered , return ; -2^OTH fu nctionalit y is not a vailable ( DG API is not availa ble) ; -1^ error mess age ; Else return p1 ^p2^p3^p4^ p5^p6^p7^p 8 where ; p1 = 0,1,2 ,or 3 ; 0 means pati ent is not OTHD elig ible ; 1 i f the pati ent is in the first 90 day per iod ; 2 if the patie nt is in t he second 90 day per iod ; 3 if the patie nt has use d all 180 days in a 365 day pe riod | |
1348 | ; p2 = FM date for the start of the clo ck for the first 90 day period ; p3 = FM date for the end of the clock for the f irst 90 da y period ; p4 = the number of days left in the fir st 90 day period ; p 5 = FM dat e for the start of t he clock f or the sec ond 90 day period ; p6 = FM da te for the end of th e clock fo r the seco nd 90 day period ; p 7 = the nu mber of da ys left in the secon d 90 day p eriod ; p8 = FM date of the au thorizatio n for the 2nd period (null if no authori zation) ; RET(2) - C ustomized message fo r the loca l VA site for the po p-up OTH d etails win dow on the CPRS scre en. ;GET(R ET,DFN,ORD ATE) ; ;ch eck if DG patch with OTHD cloc k function ality is i nstalled/r eleased S RET(0)=1 I $T(OTHDCL CK^DGOTHD) ="" S RET( 1)="-2^OTH D clock fu nctionalit y is not a vailable" Q N ORZ1 I $G(DFN)'> 0 S RET(1) ="-1^patie nt IEN is not define d" Q ;an error K R ET S ORDAT E=$S($G(OR DATE)>0:OR DATE,1:DT) S ORZ1=$$ OTHDCLCK^D GOTHD(DFN, ORDATE) I ORZ1'>0 S RET(1)=ORZ 1 Q S RET( 1)=$P(ORZ1 ,U,2,99) ; remove the first pie ce (the 36 5 days per iod number to meet t he format expected b y the RPC) ;insert t ext to get the local message S RET(0)=2, RET(2)="Ca ll Registr ation team for detai ls." Q ;G ET ; | |
1349 | Copayment Modificati ons Workst ream | |
1350 | Note: The sections p rovides th e code for major API s implemen ted for th e workstre am. | |
1351 | Routine ch anges belo w implemen t the logi c to exemp t the pati ent with H RfS from v isit copay charges ( ). | |
1352 | Table 21: Copayment Modificati ons Workst ream | |
1353 | Routines | |
1354 | Activities | |
1355 | Routine Na me | |
1356 | NEW^IBAMTC 1 | |
1357 | Enhancemen t Category | |
1358 | New | |
1359 | Modify | |
1360 | Delete | |
1361 | No Change | |
1362 | RTM | |
1363 | NSR: 20160 415 | |
1364 | Related Op tions | |
1365 | None | |
1366 | ||
1367 | Related Ro utines | |
1368 | Routines “ Called By” | |
1369 | Routines “ Called” | |
1370 | ||
1371 | ^IBAMTS | |
1372 | $$CHKHRFS( DFN | |
1373 | ||
1374 | Routines | |
1375 | Activities | |
1376 | Data Dicti onary (DD) Reference s | |
1377 | None | |
1378 | Related Pr otocols | |
1379 | None | |
1380 | Related In tegration Control Re gistration s (ICRs) | |
1381 | ICR 3860 | |
1382 | Data Passi ng | |
1383 | Input | |
1384 | Output Re ference | |
1385 | Both | |
1386 | Global Re ference | |
1387 | Local | |
1388 | Input Attr ibute Name and Defin ition | |
1389 | Name: DFN | |
1390 | Definition : Patient IEN in the file (#2) | |
1391 | Output Att ribute Nam e and Defi nition | |
1392 | None | |
1393 | ||
1394 | Current Lo gic | |
1395 | ; - perfo rm batch o f edits I '$$CHKS G NEWQ ; ; - quit if A O/IR/SWA/M ST/HNC/CV/ SHAD expos ure is ind icated, or SC relate d D CLSF(0 ,.IBCLSF) I IBCLSF[1 G NEWQ ; S IBSL="40 9.68:"_IBO E | |
1396 | ||
1397 | Modified L ogic (Chan ges are in bold) | |
1398 | ; - perfo rm batch o f edits I '$$CHKS G NEWQ ; ; - quit if A O/IR/SWA/M ST/HNC/CV/ SHAD expos ure is ind icated, or SC relate d D CLSF(0 ,.IBCLSF) I IBCLSF[1 G NEWQ ; ; - quit i f the Pt i s Visit Co pay exempt based on HRfS flag (IB*2.0*61 4) I $$CHK HRFS^IBAMT S3(DFN,IBD AT) G NEWQ ; S IBSL= "409.68:"_ IBOE ; | |
1399 | Routine ch anges belo w implemen t the logi c to exemp t the pati ent with H RfS from v isit copay charges ( Table 22). | |
1400 | Table 22: Exempt the Patient w ith HRfS f rom Visit Copay Char ges | |
1401 | Routines | |
1402 | Activities | |
1403 | Routine Na me | |
1404 | CHKHRFS^IB AMTS3 | |
1405 | Enhancemen t Category | |
1406 | New | |
1407 | Modify | |
1408 | Delete | |
1409 | No Change | |
1410 | RTM | |
1411 | NSR: 20160 415 | |
1412 | Related Op tions | |
1413 | None | |
1414 | ||
1415 | Related Ro utines | |
1416 | Routines “ Called By” | |
1417 | Routines “ Called” | |
1418 | ||
1419 | NEW^IBAMTS 1 | |
1420 | ^DGPFAPI | |
1421 | ||
1422 | Routines | |
1423 | Activities | |
1424 | Data Dicti onary (DD) Reference s | |
1425 | None | |
1426 | Related Pr otocols | |
1427 | None | |
1428 | Related In tegration Control Re gistration s (ICRs) | |
1429 | ICR 3860 | |
1430 | Data Passi ng | |
1431 | Input | |
1432 | Output Re ference | |
1433 | Both | |
1434 | Global Re ference | |
1435 | Local | |
1436 | Input Attr ibute Name and Defin ition | |
1437 | Name: IBDF N | |
1438 | Definition : Patient IEN in the file (#2) | |
1439 | Output Att ribute Nam e and Defi nition | |
1440 | None | |
1441 | ||
1442 | Current Lo gic | |
1443 | Not appli cable | |
1444 | ||
1445 | Modified L ogic (Chan ges are in bold) | |
1446 | CHKHRFS(IB DFN,STDT,E NDDT) ; Fu nction to determine Visit Copa y exemptio n based on HRfS flag (IB*2.0*6 14) ;input : IBDFN - Patient IE N ; STDT - (optional ) date to begin look ing for th e flag ; E NDDT - (op tional) En d date to look for F lag, defau lts to tod ay if not entered. ; ;Output: 1 - HRfS f lag active on date o f service ; 0 - HRfS not activ e or non-e xistent N IBFLAG,RES ULT,IBREF, SHRPEDT ;D ue to legi slative re quirements , this fun ction is a ctive only after app roved, whe n IB*2.0*6 14 is rele ased the S HRPE activ ation date will be n ull S SHRP EDT=$$GET1 ^DIQ(350.9 ,1,70.02," I") ; Acti vation dat e for SHRP E copaymen t calculat ions/waive rs I $G(SH RPEDT)="" Q 0_"^SHRP E copaymen t adjustme nts have n ot been ac tivated ye t!" ; Qui t if date not active S STDT=$G (STDT),STD T=$S(STDT= "":DT,1:ST DT),ENDDT= $S($G(ENDD T)="":STDT ,1:ENDDT) I STDT<SHR PEDT Q 0_" ^HRfS Flag wasn't ac tive on da te of serv ice" ; Da te of serv ice is bef ore activa tion date, quit S IB FLAG="HIGH RISK FOR SUICIDE",I BREF=$$GET FLAG^DGPFA PIU(IBFLAG ,"N") I $G (IBREF)="" Q 0_"^Pt doesn't ha ve the HRf S flag" ; Natl flag not found I $G(IBD FN)="" Q 0 ; No Pt e ntered N I BARR,REVDT K IBARR S RESULT=$$ GETINF^DGP FAPIH(IBDF N,IBREF,ST DT,ENDDT," IBARR") I RESULT=0 Q 0_"^HRfS flag NOT a ctive for this Pt at date of s ervice" Q 1_"^HRfS f lag is act ive at dat e of servi ce" ; | |
1447 | ||
1448 | Routine ch anges belo w implemen t the logi c to prora te RX copa y amount f or the pat ient with HRfS (Tabl e 23). | |
1449 | Table 23: Prorating RX copays for the pa tient with HRfS | |
1450 | Routines | |
1451 | Activities | |
1452 | Routine Na me | |
1453 | PRORATE^IB AMTS3 | |
1454 | Enhancemen t Category | |
1455 | New | |
1456 | Modify | |
1457 | Delete | |
1458 | No Change | |
1459 | RTM | |
1460 | NSR: 20160 415 | |
1461 | Related Op tions | |
1462 | None | |
1463 | ||
1464 | Related Ro utines | |
1465 | Routines “ Called By” | |
1466 | Routines “ Called” | |
1467 | ||
1468 | ^IBARX1 | |
1469 | None | |
1470 | ||
1471 | Routines | |
1472 | Activities | |
1473 | Data Dicti onary (DD) Reference s | |
1474 | None | |
1475 | Related Pr otocols | |
1476 | None | |
1477 | Related In tegration Control Re gistration s (ICRs) | |
1478 | None | |
1479 | Data Passi ng | |
1480 | Input | |
1481 | Output Re ference | |
1482 | Both | |
1483 | Global Re ference | |
1484 | Local | |
1485 | Input Attr ibute Name and Defin ition | |
1486 | IBAMNT - A mount of t he Normal copayment Tier cost for an Rx IBDAYS - N umber of d ays supply (ceck to see if les s than 30) | |
1487 | Output Att ribute Nam e and Defi nition | |
1488 | Output: Re turns eith er the una djusted co st, or a p rorated co st Example if Tier c ost is $11 .00 for 30 day but s upply is f or 15 days , prorate amount to $5.50 - Da ys supply/ 30 * Tier cost (AMOU NT) | |
1489 | ||
1490 | Current Lo gic | |
1491 | Not appli cable | |
1492 | ||
1493 | Modified L ogic (Chan ges are in bold) | |
1494 | PRORATE(IB AMNT,IBDAY S) ;prorat e the cost if HRfS f lag and da ys supply is less th at 30 days ; Inputs: IBAMNT - Amount of the Normal copayment Tier cost for an Rx ; IBDAYS - Number of days su pply (ceck to see if less than 30) ; Out put: Retur ns either the unadju sted cost, or a pror ated cost ; Example if Tier co st is $11. 00 for 30 day but su pply is fo r 15 days, prorate a mount to $ 5.50 - Day s supply/3 0 * Tier c ost (AMOUN T) ; N IBC OST S IBCO ST=IBAMNT S IBAMNT=$ G(IBAMNT), IBDAYS=$G( IBDAYS) I 'IBAMNT Q IBAMNT ; check for not equal to 0 I IB DAYS>29 Q IBAMNT ; greater th an 29 day supply S I BCOST=IBDA YS/30*IBAM NT ;calcu late new a mount to b ill S IBCO ST=$S($P(I BCOST,".", 2)="":IBCO ST,1:$P(IB COST,".",1 )_"."_$E($ P(IBCOST," .",2),1,2) ) ;pass ba ck dollar amount rou nded down not up Q I BCOST ; | |
1495 | ||
1496 | Patient Re cord Flag Workstream | |
1497 | Note: The sections p rovides th e code for major API s implemen ted for th e workstre am. | |
1498 | Routine ch anges belo w implemen t the logi c to provi de DBRS in formation for the pa tient with PRF flag to CPRS (T able 24). | |
1499 | Table 24: Return DBR S data for the patie nt with PR F flag | |
1500 | Routines | |
1501 | Activities | |
1502 | Routine Na me | |
1503 | GETDBRS^DG PFDBRS | |
1504 | Enhancemen t Category | |
1505 | New | |
1506 | Modify | |
1507 | Delete | |
1508 | No Change | |
1509 | RTM | |
1510 | ||
1511 | Related Op tions | |
1512 | None | |
1513 | ||
1514 | Related Ro utines | |
1515 | Routines “ Called By” | |
1516 | Routines “ Called” | |
1517 | ||
1518 | ^ORPRF | |
1519 | GETS^DIQ | |
1520 | ||
1521 | Routines | |
1522 | Activities | |
1523 | Data Dicti onary (DD) Reference s | |
1524 | None | |
1525 | Related Pr otocols | |
1526 | None | |
1527 | Related In tegration Control Re gistration s (ICRs) | |
1528 | 6874 | |
1529 | Data Passi ng | |
1530 | Input | |
1531 | Output Re ference | |
1532 | Both | |
1533 | Global Re ference | |
1534 | Local | |
1535 | Input Attr ibute Name and Defin ition | |
1536 | Parameters : | |
1537 | DGDFN - p atient's D FN | |
1538 | DGRETARR - array to return in formation in the for mat: | |
1539 | ARR(1)="D BRS#^DBRS date^DBRS other info rmation" | |
1540 | ARR(2)="D BRS#^DBRS date^DBRS other info rmation" | |
1541 | ... | |
1542 | ARR(n)="D BRS#^DBRS date^DBRS other info rmation" | |
1543 | Note: the DBRS entr ies are li sted in th e reversed order. | |
1544 | ARR(1) co ntains the latest en try | |
1545 | DGFLAG - for which flag the D BRS entry data need to be retu rned | |
1546 | Note: Def ault is "B EHAVIORAL" | |
1547 | Output Att ribute Nam e and Defi nition | |
1548 | Returns: | |
1549 | the late st entry A RR(1) - if any entri es exist | |
1550 | or | |
1551 | "" - if no entries found | |
1552 | "" - if the patien t doesn't have a PRF flag | |
1553 | ||
1554 | Current Lo gic | |
1555 | Not appli cable | |
1556 | ||
1557 | Modified L ogic (Chan ges are in bold) | |
1558 | ;The API to get the DBRS info rmation ;I mplements the ICR# 6 874 ;Param eters: ; D GDFN - pat ient's DFN ; DGRETAR R - array to return informatio n in the f ormat: ; A RR(1)="DBR S#^DBRS da te^DBRS ot her inform ation" ; A RR(2)="DBR S#^DBRS da te^DBRS ot her inform ation" ; . .. ; ARR(n )="DBRS#^D BRS date^D BRS other informatio n" ; Note: the DBRS entries ar e listed i n the reve rsed order . ; ARR(1 ) contains the lates t entry ; DGFLAG - f or which f lag the DB RS entry d ata need t o be retur ned ; Not e: Default is "BEHAV IORAL" ; ; Returns: ; the lates t entry AR R(1) - if any entrie s exist ;o r ; "" - i f no entri es found ; "" - if t he patient doesn't h ave a PRF flag ;GETD BRS(DGDFN, DGRETARR,D GFLAG) ; N DG2613,DG ARR,DGIEN, DGCNT,DGCU RFLG S DGF LAG=$G(DGF LAG,"BEHAV IORAL") S DG2613=0 F S DG2613 =$O(^DGPF( 26.13,"B", DGDFN,DG26 13)) Q:+DG 2613=0 D . K DGARR . D GETS^DI Q(26.13,DG 2613_","," .02;2*","E ","DGARR") . S DGCUR FLG=$G(DGA RR(26.13,D G2613_",", .02,"E")) . I DGCURF LG']"" Q . S DGIEN=" Z",DGCNT=0 . F S DG IEN=$O(DGA RR(26.131, DGIEN),-1) Q:DGIEN'] "" D . . S DGCNT=DG CNT+1 S DG RETARR(DGC URFLG,DGCN T)=DGARR(2 6.131,DGIE N,.01,"E") _U_DGARR(2 6.131,DGIE N,.02,"E") I '$D(DGR ETARR) Q " " Q $G(DGR ETARR(DGFL AG,1)) | |
1559 | Routine ch anges belo w implemen t the logi c to retur n facilty toTIU | |
1560 | Table 22: Add facili ty column to RPC for TIU | |
1561 | Routines | |
1562 | Activities | |
1563 | Routine Na me | |
1564 | GETACTS ^T IUPRF2 | |
1565 | Enhancemen t Category | |
1566 | New | |
1567 | Modify | |
1568 | Delete | |
1569 | No Change | |
1570 | RTM | |
1571 | ||
1572 | Related Op tions | |
1573 | None | |
1574 | ||
1575 | Related Ro utines | |
1576 | Routines “ Called By” | |
1577 | Routines “ Called” | |
1578 | ||
1579 | N/A | |
1580 | $$GETHTIU^ DGPFAPI1 | |
1581 | $$AVAILACT ^TIUPRFL | |
1582 | ||
1583 | Routines | |
1584 | Activities | |
1585 | Data Dicti onary (DD) Reference s | |
1586 | None | |
1587 | Related Pr otocols | |
1588 | None | |
1589 | Related In tegration Control Re gistration s (ICRs) | |
1590 | 3860 | |
1591 | Data Passi ng | |
1592 | Input | |
1593 | Output Re ference | |
1594 | Both | |
1595 | Global Re ference | |
1596 | Local | |
1597 | Input Attr ibute Name and Defin ition | |
1598 | Input: DF N - [Requi red] IEN o f PATIENT (#2) file TIUTTL - [Required] IEN of TI U DOCUMENT DEFINITIO N (#8925.1 ) file RE TURN ARRAY .TIUY - passed by reference see descr iption of return arr ay from GE THTIU^DGPF API1 refo rmat data for TIU RP C return dg*951 bro ught in p8 TIUY(ACT ID) = p1^p 2^p3^p4^p5 ^p6^p7^p8 where p1 = flag nam e p5 = act ion date, FM interna l p2 = as signment i en [.001/# 26.13] p6 = action d ate, exter nal p3 = action nam e [.03/#26 .14] p7 = file 8925 ien p4 = action ien p8 = orig inate faci lity name | |
1599 | Output Att ribute Nam e and Defi nition | |
1600 | Returns linkable a ction for Patient DF N and flag assoc w/ TIUTTL Ac tion may b e currentl y linked o r not Exc ludes UNLI NKABLE act ions Ente red in Err or actions (EIE) Ac tions take n prior to that EIE action Pr ior to DG* 5.3*951, r eturn arra y used ACT ID from GE THTIU^DGPF API1 DG*5 .3*951 sor t array by Originati ng Facilit y, always lists the History r ecords cre ated by th e local fa cility fir st. | |
1601 | ||
1602 | Current Lo gic | |
1603 | GETACTS(TI UY,TIUTTL, DFN) ;RPC Gets PRF A ction info ;"Action" is shorth and for As signment H istory ent ry ;Return s data in the follow ing format for each Action: ;T IUY(ACTID) = ; FLAGN AME^ASSGNI EN^ACTIONN AME^ACTION IEN^ACTION DATEI^ACTI ONDATEE^TI UIEN ; whe re Integer ACTID = s ubscript a fter "HIST ORY" in ar ray return ed ; by GE THTIU^DGPF API1 ;Retu rns linkab le actions (whether linked or not) for P atient DFN ; and fla g assoc w/ TIUTTL. ; Excludes U NLINKABLE actions = Entered in Error act ions (EIE) or ; acti ons taken prior to a n EIE acti on. ;Erron eous and E IE actions may be fo r the wron g patient, etc. N TI UDG,ACTID, TIUFLAG,UN LINKBL,ARR AYNM S TIU Y=1,ARRAYN M="^TMP("" TIUPRFH"", $J)" S TIU DG=$$GETHT IU^DGPFAPI 1(DFN,TIUT TL,ARRAYNM ) I 'TIUDG S TIUY="0 ^"_$P(TIUD G,U,2) G G ETACTX ; - - If no un linked, li nkable act ions exist , say so b ut go on: I '$$AVAIL ACT^TIUPRF L("^TMP("" TIUPRFH"", $J)",,.UNL INKBL) S T IUY="0^All linkable Flag actio ns are alr eady linke d" ; -- Re turn ALL l inkable ac tions (lin ked or not ): S TIUFL AG=$P(^TMP ("TIUPRFH" ,$J,"FLAG" ),U,2)_U_$ P(^TMP("TI UPRFH",$J, "ASSIGNIEN "),U) S AC TID=0 F S ACTID=$O( ^TMP("TIUP RFH",$J,"H ISTORY",AC TID)) Q:'+ ACTID D . Q:$G(UNLI NKBL(ACTID )) . S TIU Y(ACTID)=T IUFLAG . S TIUY(ACTI D)=TIUY(AC TID)_U_$P( ^TMP("TIUP RFH",$J,"H ISTORY",AC TID,"ACTIO N"),U,2) . S TIUY(AC TID)=TIUY( ACTID)_U_$ P(^TMP("TI UPRFH",$J, "HISTORY", ACTID,"HIS TIEN"),U,1 ) . S TIUY (ACTID)=TI UY(ACTID)_ U_$P(^TMP( "TIUPRFH", $J,"HISTOR Y",ACTID," DATETIME") ,U,1) . S TIUY(ACTID )=TIUY(ACT ID)_U_$P(^ TMP("TIUPR FH",$J,"HI STORY",ACT ID,"DATETI ME"),U,2) . S TIUY(A CTID)=TIUY (ACTID)_U_ $P(^TMP("T IUPRFH",$J ,"HISTORY" ,ACTID,"TI UIEN"),U,1 )GETACTX ; K ^TMP("T IUPRFH",$J ) Q | |
1604 | ||
1605 | Modified L ogic (Chan ges are in bold) | |
1606 | GETACTS(TI UY,TIUTTL, DFN) ; RPC TIU GET P RF ACTIONS ; RPC Get s PRF Acti on info ; Action in PRF is the reason a History (# 26.14) rec ord was cr eated ; In put: ; DFN - [Requir ed] IEN of PATIENT ( #2) file ; TIUTTL - [Required] IEN of TI U DOCUMENT DEFINITIO N (#8925.1 ) file ; R ETURN ARRA Y ; .TIUY - passed b y referenc e ; see de scription of return array from GETHTIU^D GPFAPI1 ; reformat d ata for TI U RPC retu rn ; dg*95 1 brought in p8 ; TI UY(ACTID) = p1^p2^p3 ^p4^p5^p6^ p7^p8 wher e ; p1 = f lag name p 5 = action date, FM internal ; p2 = assi gnment ien [.001/#26 .13] p6 = action dat e, externa l ; p3 = a ction name [.03/#26. 14] p7 = f ile 8925 i en ; p4 = action ien p8 = orig inate faci lity name ; ; Return s linkable action fo r Patient DFN and fl ag assoc w / TIUTTL ; Action ma y be curre ntly linke d or not ; Excludes UNLINKABLE actions ; Entered i n Error ac tions (EIE ) ; Action s taken pr ior to tha t EIE acti on ; Prior to DG*5.3 *951, retu rn array u sed ACTID from GETHT IU^DGPFAPI 1 ; DG*5.3 *951 sort array by O riginating Facility, always li sts the ; History re cords crea ted by the local fac ility firs t. ; N I,X ,ACTID,ARR AYNM,APPRV BY,FLAG,HE RE,UNLINKB L ; S ARRA YNM=$$SET S HERE=$$H ERE K ^TMP ($J) S TIU Y=1 S X=$$ GETHTIU^DG PFAPI1(DFN ,TIUTTL,AR RAYNM) I ' X S TIUY=" 0^"_$P(X,U ,2) G KILL ; | |
1607 | ; -- If n o unlinked , linkable actions e xist, say so but go on: I '$$A VAILACT^TI UPRFL(ARRA YNM,,.UNLI NKBL) D . S TIUY="0^ All linkab le Flag ac tions are already li nked" . Q ; ; -- Ret urn ALL li nkable act ions (link ed or not) S FLAG=$$ GETP("FLAG ",2)_U_$$G ETP("ASSIG NIEN",1) S ACTID=0 F S ACTID= $O(@ARRAYN M@("HISTOR Y",ACTID)) Q:'ACTID D . Q:$G( UNLINKBL(A CTID)) . N X,Y,APPRV BY,FNM,IEN ,ST3,STR . S APPRVBY =$$GETPA(" APPRVBY",1 ) . S STR= FLAG . S $ P(STR,U,3) =$$GETPA(" ACTION",2) . S $P(ST R,U,4)=$$G ETPA("HIST IEN",1) . S $P(STR,U ,5)=$$GETP A("DATETIM E",1) . S $P(STR,U,6 )=$$GETPA( "DATETIME" ,2) . S $P (STR,U,7)= $$GETPA("T IUIEN",1) . ; . ; dg *951 - for mat by ori ginating f acility na me . S IEN =$$GETPA(" ORIG FAC") . S X=$$S TN("SN",IE N,1,APPRVB Y) . S ST3 =$P(X,U,5) ,FNM=$P(X, U,4) . S $ P(STR,U,8) =FNM . S ^ TMP($J,ST3 ,FNM,ACTID )=STR . Q ; now set up the ret urn array S I=0,X=$N A(^TMP($J) ) F S X=$ Q(@X) Q:X= "" Q:$QS( X,1)'=$J S I=I+1,TI UY(I)=@X K ^TMP($J) G KILL | |
1608 | Templates | |
1609 | No templat es are use d/modified /created/d esigned in Sprint 1 of Build 2 . | |
1610 | Bulletins | |
1611 | No bulleti ns are use d/modified /created/d esigned in Sprint 1 of Build 2 . | |
1612 | Data Entri es Affecte d by the D esign | |
1613 | The new en tries have been adde d to the f iles (#8)( Figure 18) and (#8.1 )(Figure 1 9): | |
1614 | Figure 18: File (#8) | |
1615 | ||
1616 | NAME: OTHE R THAN HON ORABLE CARD COLOR : RED | |
1617 | ABBREVIA TION: OTH VA CODE NU MBER: 6 | |
1618 | TYPE: NO N-VETERAN PRINT NAME : OTHER TH AN HONORAB LE | |
1619 | SELECT A S ADDITION AL: YES | |
1620 | MAS ELIG IBILITY CO DE: OTHER THAN HONOR ABLE | |
1621 | ID FORMA T: VA STAN DARD AGENCY: VA | |
1622 | ADDITION AL ONLY: Y ES | |
1623 | Figure 19: File (#8. 1) | |
1624 | ||
1625 | NAME: OTHE R THAN HON ORABLE CARD COLOR : RED | |
1626 | ABBREVIA TION: OTH VA CODE NU MBER: 6 | |
1627 | TYPE: NO N-VETERAN PRINT NAME : OTHER TH AN HONORAB LE | |
1628 | SELECT A S ADDITION AL: YES | |
1629 | Unique Rec ord(s) | |
1630 | The new en tries have been adde d to the f iles (#8)( Figure 20) and (#8.1 )(Figure 2 1): | |
1631 | Figure 20: File (#8, updated) | |
1632 | File (#8) | |
1633 | NAME: OTHE R THAN HON ORABLE CARD COLOR : RED | |
1634 | ABBREVIA TION: OTH VA CODE NU MBER: 6 | |
1635 | TYPE: NO N-VETERAN PRINT NAME : OTHER TH AN HONORAB LE | |
1636 | SELECT A S ADDITION AL: YES | |
1637 | MAS ELIG IBILITY CO DE: OTHER THAN HONOR ABLE | |
1638 | ID FORMA T: VA STAN DARD AGENCY: VA | |
1639 | ADDITION AL ONLY: Y ES | |
1640 | Figure 21: File (#8. 1, updated ) | |
1641 | File (#8.1 ) | |
1642 | NAME: OTHE R THAN HON ORABLE CARD COLOR : RED | |
1643 | ABBREVIA TION: OTH VA CODE NU MBER: 6 | |
1644 | TYPE: NO N-VETERAN PRINT NAME : OTHER TH AN HONORAB LE | |
1645 | SELECT A S ADDITION AL: YES | |
1646 | ||
1647 | File or Gl obal Size Changes | |
1648 | OTH clock file (#33) | |
1649 | The projec t adds the new file (#33) for the OTH cl ock; the s ize of the file depe nds on the number of patients with the n ew OTH eli gibility. The projec t team has requested this info rmation fr om SMEs an d does not have this informati on at the moment. | |
1650 | DBRS field s | |
1651 | The projec t adds new fields fo r the two VistA data base files (#26.13) and (#26.1 4) to capt ure the DB RS data fr om the DBR S system m anually. | |
1652 | The growth rate of t hese two V istA datab ase files due to sto ring DBRS data depen ds on the number DBR S cases ar e entered yearly in average. | |
1653 | Based on t he informa tion provi ded by the DBRS team the numbe rs of expe cted new D BRS record s per year is 50000: | |
1654 | The yearly growth fo r a single local Vis ta databas e instance for each file calcu lated as | |
1655 | = {File (# 26.13) tot al DBRS re cords size * number of expecte d new DBRS records p er year} / number of VA sites | |
1656 | = {File (# 26.14) tot al DBRS re cords size * number of expecte d new DBRS records p er year} / number of VA sites | |
1657 | Each DBRS records ta kes 87 byt es for the file (#26 .13) and 1 88 bytes f or the fil e (#26.14) and (See section 5 .1. DBMS F iles for m ore detail s) | |
1658 | Thus the y early grow th for eac h files fo r a single local Vis ta databas e instance = (87*500 00)/150 = 29000 = 29 Kbytes/ y ear (Table 25) | |
1659 | (188*50000 )/150 = 62 666 = 63 K bytes/ yea r (Table 2 5) | |
1660 | Table 25: File or Gl obal Size Changes | |
1661 | File/Globa l Name(s) | |
1662 | Estimated Increase | |
1663 | Estimated Decrease | |
1664 | (#26.13) | |
1665 | 29 Kbytes/ year | |
1666 | Not applic able. | |
1667 | (#26.14) | |
1668 | 63 Kbytes/ year | |
1669 | Not applic able. | |
1670 | Mail Group s | |
1671 | No mail gr oups are u sed/modifi ed/created /designed in Sprint 1 of Build 2. | |
1672 | Security K eys | |
1673 | No securit y keys are used/modi fied/creat ed/designe d in Sprin t 1 of Bui ld 2. | |
1674 | Options | |
1675 | No options are used/ modified/c reated/des igned in S print 1 of Build 2. | |
1676 | Protocols | |
1677 | No protoco ls are use d/modified /created/d esigned in Sprint 1 of Build 2 . | |
1678 | Remote Pro cedure Cal l (RPC) | |
1679 | ||
1680 | Patient Re cord Flag Workstream | |
1681 | Table 26: OR OTHD CL OCK GET RP C | |
1682 | RPCs | |
1683 | Activities | |
1684 | Name | |
1685 | TIU GET PR F ACTIONS | |
1686 | TAG^RTN | |
1687 | GETACTS^TI UPRF2 | |
1688 | Input Para meters | |
1689 | DFN This i s a pointe r to the P ATIENT fil e (#2). | |
1690 | Results Ar ray | |
1691 | Single Va lue | |
1692 | Array | |
1693 | Word Proc essing | |
1694 | ||
1695 | Global Ar ray | |
1696 | Global In stance | |
1697 | ||
1698 | ||
1699 | ||
1700 | ||
1701 | ||
1702 | Descriptio n | |
1703 | NAME: TIU GET PRF AC TIONS TAG: GETAC TS | |
1704 | ROUTINE: TIUPRF2 RETURN VAL UE TYPE: A RRAY | |
1705 | INACTIVE : ACTIVE APP PROXY ALLOWED: Y es | |
1706 | DESCRIPTI ON: | |
1707 | This RPC gets the P atient Rec ord Flag H istory Ass ignments/A ctions for a | |
1708 | Patient/T itle Combi nation. | |
1709 | INPUT PARA METER: TIU TTL PARAMETER TYPE: LITE RAL | |
1710 | REQUIRED : YES SEQUENCE N UMBER: 1 | |
1711 | DESCRIPTI ON: | |
1712 | TIU DOCUM ENT DEFINI TION (TITL E) IEN | |
1713 | INPUT PARA METER: DFN PARAMETER TYPE: LITE RAL | |
1714 | REQUIRED : YES SEQUENCE N UMBER: 2 | |
1715 | DESCRIPTI ON: | |
1716 | Patient P ointer (fi le 2 IEN) | |
1717 | RETURN PA RAMETER DE SCRIPTION: | |
1718 | Returns d ata in the following format fo r each Fla g Assignme nt/Action | |
1719 | ||
1720 | FLAG NAME ^FLAG IEN^ ACTION NAM E^ACTION I EN^ACTION DATE I^ACT ION DATE E ^TIU | |
1721 | IEN^ORIGI NATING FAC ILITY E | |
1722 | ||
1723 | ||
1724 | Else return p1^ p2^p3^p4^p 5^p6^p7 wh ere | |
1725 | p1 = 0,1,2,o r 3 | |
1726 | p2 = FM date for the s tart of th e clock fo r the firs t 90 day p eriod | |
1727 | p3 = FM date for the e nd of the clock for the first 90 day per iod | |
1728 | p4 = the num ber of day s left in the first 90 day per iod | |
1729 | p5 = FM date for the s tart of th e clock fo r the seco nd 90 day | |
1730 | period | |
1731 | p6 = FM date for the e nd of the clock for the second 90 day pe riod | |
1732 | p7 = the num ber of day s left in the second 90 day pe riod | |
1733 | ||
1734 | Type <Ente r> to cont inue or '^ ' to exit: | |
1735 | p8 = FM date of the a uthorizati on for the 2nd perio d (null if no | |
1736 | authori zation) | |
1737 | ||
1738 | p1 = 0 means pa tient is n ot OTH eli gible | |
1739 | p1 = 1 if the p atient is in the fir st 90 day period | |
1740 | p1 = 2 if the p atient is in the sec ond 90 day period | |
1741 | p1 = 3 if the p atient has used all 180 days i n a 365 da y period | |
1742 | ||
1743 | ARR(2): c ontains th e customiz ed message for the l ocal VA si te for the | |
1744 | p op-up OTH details wi ndow on th e CPRS scr een. | |
1745 | ||
1746 | ||
1747 | Other Than Dishonora ble Discha rge Modifi cations Wo rkstream | |
1748 | Table 27: OR OTHD CL OCK GET RP C | |
1749 | RPCs | |
1750 | Activities | |
1751 | Name | |
1752 | OR OTHD CL OCK GET | |
1753 | TAG^RTN | |
1754 | GET^OTOTHC | |
1755 | Input Para meters | |
1756 | DFN This i s a pointe r to the P ATIENT fil e (#2). | |
1757 | Results Ar ray | |
1758 | Single Va lue | |
1759 | Array | |
1760 | Word Proc essing | |
1761 | ||
1762 | Global Ar ray | |
1763 | Global In stance | |
1764 | ||
1765 | ||
1766 | Descriptio n | |
1767 | NAME: OR O THD CLOCK GET TAG: GET | |
1768 | ROUTINE: OROTHCL RETURN VAL UE TYPE: A RRAY | |
1769 | AVAILABI LITY: SUBS CRIPTION | |
1770 | DESCRIPTI ON: | |
1771 | The Other Than Hono rable Disc harge init iative all ow for cer tain patie nts | |
1772 | to have l imited men tal health access. These indi viduals ar e entitled to | |
1773 | two 90 da y terms of care in a 365 day p eriod. Th ese RPC re turns the | |
1774 | status of the clock for an ap plication to display as it see s fit. | |
1775 | INPUT PARA METER: DFN PARAMETER TYPE: LITE RAL | |
1776 | MAXIMUM DATA LENGT H: 100 REQUIRED: YES | |
1777 | SEQUENCE NUMBER: 1 | |
1778 | DESCRIPTI ON: | |
1779 | This is a pointer t o the PATI ENT file. | |
1780 | INPUT PARA METER: ORD ATE PARAMETER TYPE: LITE RAL | |
1781 | MAXIMUM DATA LENGT H: 100 REQUIRED: NO | |
1782 | SEQUENCE NUMBER: 2 | |
1783 | DESCRIPTI ON: | |
1784 | (Optional ) The date to calcul ate status in FileMa n format. | |
1785 | RETURN PA RAMETER DE SCRIPTION: | |
1786 | This retu rn paramet er should contain al l the info rmation th e client n eeds | |
1787 | to displa y informat ion about the OTH cl ock withou t the clie nt having to | |
1788 | ||
1789 | Type <Ente r> to cont inue or '^ ' to exit: | |
1790 | do any ca lculations . The ret urn string is of the following format: | |
1791 | ||
1792 | Array of strings: | |
1793 | ARR(0): t he number of arrays elements w ith data | |
1794 | If err or then AR R(0) will always be 1, | |
1795 | if no errors, th en can be either 1 ( if no loca l message provided) | |
1796 | or 2 ( if the loc al message is return ed). | |
1797 | ||
1798 | ARR(1): c ontains al l the info rmation th e client n eeds to di splay | |
1799 | i nformation about the OTH clock . | |
1800 | If so me kind of error con dition is encountere d, return | |
1801 | -1 ^error mes sage | |
1802 | ||
1803 | ||
1804 | Else return p1^ p2^p3^p4^p 5^p6^p7 wh ere | |
1805 | p1 = 0,1,2,o r 3 | |
1806 | p2 = FM date for the s tart of th e clock fo r the firs t 90 day p eriod | |
1807 | p3 = FM date for the e nd of the clock for the first 90 day per iod | |
1808 | p4 = the num ber of day s left in the first 90 day per iod | |
1809 | p5 = FM date for the s tart of th e clock fo r the seco nd 90 day | |
1810 | period | |
1811 | p6 = FM date for the e nd of the clock for the second 90 day pe riod | |
1812 | p7 = the num ber of day s left in the second 90 day pe riod | |
1813 | ||
1814 | Type <Ente r> to cont inue or '^ ' to exit: | |
1815 | p8 = FM date of the a uthorizati on for the 2nd perio d (null if no | |
1816 | authori zation) | |
1817 | ||
1818 | p1 = 0 means pa tient is n ot OTH eli gible | |
1819 | p1 = 1 if the p atient is in the fir st 90 day period | |
1820 | p1 = 2 if the p atient is in the sec ond 90 day period | |
1821 | p1 = 3 if the p atient has used all 180 days i n a 365 da y period | |
1822 | ||
1823 | ARR(2): c ontains th e customiz ed message for the l ocal VA si te for the | |
1824 | p op-up OTH details wi ndow on th e CPRS scr een. | |
1825 | ||
1826 | Constants Defined in Interface | |
1827 | No constan ts Defined in Interf ace are us ed/modifie d/created in Sprint 1 of Build 2. | |
1828 | Variables Defined in Interface | |
1829 | No Variabl es Defined in Interf ace are us ed/modifie d/created in Sprint 1 of Build 2. | |
1830 | Types Defi ned in Int erface | |
1831 | No types d efined in Interface are used/m odified/cr eated in S print 1 of Build 2. | |
1832 | ||
1833 | GUI - fFra me | |
1834 | Table 28 a nd Table 2 9 are desc riptions o f GUIs cha nges for t his projec t. | |
1835 | Table 28: GUI - fFra me | |
1836 | Unit Name | |
1837 | Descriptio n | |
1838 | fFrame | |
1839 | Main form of CPRS | |
1840 | GUI Classe s | |
1841 | Table 29: For fFrame | |
1842 | GUI Classe s | |
1843 | Descriptio n | |
1844 | Class Name | |
1845 | TfrmFrame | |
1846 | Derived Fr om Class | |
1847 | TfrmBase50 8Form | |
1848 | Purpose | |
1849 | Main form | |
1850 | Current Fo rm | |
1851 | Figure 22: Main CPRS screen (f Frame) | |
1852 | ||
1853 | Modified F orm | |
1854 | Figure 23: Main CPRS Screen (f Frame) | |
1855 | ||
1856 | Components on Form | |
1857 | Table 30: fFrame | |
1858 | Name | |
1859 | Type | |
1860 | Descriptio n | |
1861 | pnlOTHD | |
1862 | TKeyClickP anel | |
1863 | Container for OTHD c ountdown c lock | |
1864 | lblOTHDTit le | |
1865 | TStaticTex t | |
1866 | Title for countdown clock | |
1867 | lblOTHD | |
1868 | TStaticTex t | |
1869 | Countdown clock disp lay | |
1870 | Events | |
1871 | Table 31: Events | |
1872 | Name | |
1873 | Type | |
1874 | Descriptio n | |
1875 | pnlOTHD | |
1876 | onClick | |
1877 | Calls pnlO THDClick | |
1878 | pnlOTHD | |
1879 | onEnter | |
1880 | Calls pnlO THDEnter | |
1881 | pnlOTHD | |
1882 | onExit | |
1883 | Calls pnlO THDExit | |
1884 | lblOTHD | |
1885 | onClick | |
1886 | Calls lblO THDClick | |
1887 | lblOTHDTit le | |
1888 | onClick | |
1889 | Calls lblO THDTitleCl ick | |
1890 | Methods | |
1891 | Table 32: Methods | |
1892 | Method Nam e | |
1893 | Procedure/ Function | |
1894 | Descriptio n | |
1895 | ChangeFont | |
1896 | Procedure | |
1897 | Added lblO THD and lb lOTHDTitle to reset of font si zes | |
1898 | ClearPatie nt | |
1899 | Procedure | |
1900 | Hide and d isable pnl othd, disa ble lbloth dtitle, cl ear lblOTH D.Caption, OTHDShort Str, OTHDL ongStr1, O THDLongStr 2, OTHDLoc alMsg | |
1901 | SetupPatie nt | |
1902 | Procedure | |
1903 | Call getOT HD. If suc cessful, s etup pnlOT HD and sub components ; assign g lobal vers ions of OT H strings | |
1904 | pnlOTHDCli ck | |
1905 | Procedure | |
1906 | Display OT HDLongStr1 , non-empt y OTHDLong Str2, and non-empty OTHDLocalM sg in a po pup. | |
1907 | pnlOTHDEnt er | |
1908 | Procedure | |
1909 | Display wi de version of OTH me ssages by widening “ button” | |
1910 | pnlOTHDExi t | |
1911 | Procedure | |
1912 | Return “bu tton” to n ormal widt h and disp lay abbrev iated OTH message | |
1913 | lblOTHDCli ck | |
1914 | Procedure | |
1915 | Call pnlOT HDClick(lb lOTHD) | |
1916 | lblOTHDTit leClick | |
1917 | Procedure | |
1918 | Call pnlOT HDClick(lb lOTHDTitle ) | |
1919 | Special Re ferences | |
1920 | Table 33: Special Re ferences | |
1921 | Special Re ference Na me | |
1922 | Type | |
1923 | Descriptio n | |
1924 | OTHDShortS tr | |
1925 | String | |
1926 | Implementa tion-level abbreviat ed string used in “b utton” | |
1927 | OTHDLongSt r1 | |
1928 | String | |
1929 | Implementa tion-level first lin e of expan ded text | |
1930 | OTHDLongSt r2 | |
1931 | String | |
1932 | Implementa tion-level second li ne of expa nded text | |
1933 | OTHDLocalM sg | |
1934 | String | |
1935 | Implementa tion-level locally ( facility) defined to do message | |
1936 | Class Even ts | |
1937 | Table 34: Class Even ts | |
1938 | Name | |
1939 | Type | |
1940 | Descriptio n | |
1941 | n/a | |
1942 | n/a | |
1943 | n/a | |
1944 | Class Meth ods | |
1945 | Table 35: Class Meth ods | |
1946 | Name | |
1947 | Procedure/ Function | |
1948 | Descriptio n | |
1949 | getOTHD | |
1950 | Function | |
1951 | function g etOTHD(DFN Str, NameS tr: String ; out Shor tStr, Long Str1, Long Str2, Loca lMsg: Stri ng): Boole an; Retrie ves countd own clock data and o utputs for matted rem aining day s, period, and local message b ased on st atus from RPC OR OTH D CLOCK GE T. | |
1952 | TfrmFrame. ClearPatie nt | |
1953 | Procedure | |
1954 | Modified t o setup pn lOTHD | |
1955 | TfrmFrame. SetupPatie nt | |
1956 | Procedure | |
1957 | Added code to call g etOTHD and update pn lOTHD, lbl OTHDTitle, and lblOT HD | |
1958 | Class Prop erties | |
1959 | Table 36: Class Prop erties | |
1960 | Class Prop erties Nam e | |
1961 | Type | |
1962 | Visibility | |
1963 | Descriptio n | |
1964 | n/a | |
1965 | n/a | |
1966 | n/a | |
1967 | n/a | |
1968 | Uses Claus e | |
1969 | N/AGUI - f NoteProps | |
1970 | Table 37: GUI | |
1971 | Unit Name | |
1972 | Descriptio n | |
1973 | fNoteProps | |
1974 | Progress N otes Prope rties dial og | |
1975 | GUI Classe s | |
1976 | Table 38: GUI Classe s | |
1977 | GUI Classe s | |
1978 | Descriptio n | |
1979 | Class Name | |
1980 | TfrmNotePr operties | |
1981 | Derived Fr om Class | |
1982 | TfrmBase50 8Form | |
1983 | Purpose | |
1984 | Progress N otes Prope rties dial og | |
1985 | Current Fo rm | |
1986 | Figure 24: Current F orm | |
1987 | ||
1988 | Modified F orm | |
1989 | Figure 25: Modified Form | |
1990 | ||
1991 | Components on Form | |
1992 | Table 39: Components on Form | |
1993 | Name | |
1994 | Type | |
1995 | Descriptio n | |
1996 | n/a | |
1997 | n/a | |
1998 | n/a | |
1999 | Events | |
2000 | Table 40: Events | |
2001 | Name | |
2002 | Type | |
2003 | Descriptio n | |
2004 | lvPRF | |
2005 | onColumnCl ick | |
2006 | Calls lvPR FColumnCli ck | |
2007 | lvPRF | |
2008 | onCompare | |
2009 | Calls lvPR FCompare | |
2010 | Methods | |
2011 | Table 41: Methods | |
2012 | Method Nam e | |
2013 | Procedure/ Function | |
2014 | Descriptio n | |
2015 | lvPRFColum nClick | |
2016 | Procedure | |
2017 | Sorts colu mn in asce nding/desc ending ord er | |
2018 | lvPRFCompa re | |
2019 | procedure | |
2020 | Calls Comp areText to do alphan umeric sor t | |
2021 | formShow | |
2022 | Procedure | |
2023 | Modified t o initiali ze sort di rection an d column i n lvPRF | |
2024 | ShowPRFLis t | |
2025 | Procedure | |
2026 | Initialize lvPRF sor t directio n arrows t o show no image | |
2027 | ShowAction sOnList | |
2028 | Procedure | |
2029 | Insert Fac ility colu mn in seco nd positio n using ei ghth piece returned from RPC. If eighth piece is e mpty, set facility c olumn widt h to 0 to hide the c olumn. Fa cility col umn shows only for C AT 1 Behav ioral flag with TIU patch inst alled. | |
2030 | Special Re ferences | |
2031 | Table 42: Special Re ferences | |
2032 | Special Re ference Na me | |
2033 | Type | |
2034 | Descriptio n | |
2035 | n/a | |
2036 | n/a | |
2037 | n/a | |
2038 | Class Even ts | |
2039 | Table 43: Class Even ts | |
2040 | Name | |
2041 | Type | |
2042 | Descriptio n | |
2043 | n/a | |
2044 | n/a | |
2045 | n/a | |
2046 | Class Meth ods | |
2047 | Table 44: Class Meth ods | |
2048 | Name | |
2049 | Procedure/ Function | |
2050 | Descriptio n | |
2051 | n/a | |
2052 | n/a | |
2053 | n/a | |
2054 | Class Prop erties | |
2055 | Table 45: Class Prop erties | |
2056 | Class Prop erties Nam e | |
2057 | Type | |
2058 | Visibility | |
2059 | Descriptio n | |
2060 | n/a | |
2061 | n/a | |
2062 | n/a | |
2063 | n/a | |
2064 | Uses Claus e | |
2065 | n/a | |
2066 | ||
2067 | Forms | |
2068 | No forms a re used/mo dified/cre ated so fa r in Sprin t 1 of Bui ld 2. | |
2069 | Functions | |
2070 | No functio ns are use d/modified /created s o far in S print 1 of Build 2. | |
2071 | Dialog | |
2072 | No dialog messages a re used/mo dified/cre ated so fa r in Sprin t 1 of Bui ld 2. | |
2073 | Help Frame | |
2074 | No Help Fr ames are u sed/modifi ed/created so far in Sprint 1 of Build 2 . | |
2075 | HL7 Applic ation Para meter | |
2076 | No HL7 App lication P arameters are used/m odified/cr eated so f ar in Spri nt 1 of Bu ild 2. | |
2077 | HL7 Logica l Link | |
2078 | No HL7 Log ical Link are used/m odified/cr eated so f ar in Spri nt 1 of Bu ild 2. | |
2079 | COTS Inter face | |
2080 | No COTS In terface ar e used/mod ified/crea ted in Spr int 1 of B uild 2. | |
2081 | Network De tailed Des ign | |
2082 | Communicat ions betwe en VistA s ites pass through th e Local Ar ea Network s (LANs) a nd across the VA int ranet. | |
2083 | While proj ect modifi cations fo r VistA Re gistration (DG) rely on the ne twork infr astructure , they do not make a ny changes to this i nfrastruct ure. The n umber of a dditional messages s ent betwee n sites du e to the p roject cha nges insig nificant. | |
2084 | Security a nd Privacy | |
2085 | The workst reams empl oys measur es for sec urity and privacy. | |
2086 | Security | |
2087 | The projec t modifica tions do n ot make an y changes to the sec urity mech anisms of existing V istA appli cations. | |
2088 | The scope of work do es not imp act existi ng securit y controls and priva cy conside rations. | |
2089 | Privacy | |
2090 | The projec t modifica tions do n ot make an y changes that impac t privacy mechanisms at the ex isting Vis tA applica tions. | |
2091 | The scope of work do es not imp act existi ng securit y controls and priva cy conside rations. | |
2092 | Service Or iented Arc hitecture / ESS Deta iled Desig n | |
2093 | Not applic able. | |
2094 | Service De scription for <Consu med Servic e Name> | |
2095 | Not applic able. | |
2096 | Service De sign for < Provided S ervice Nam e> | |
2097 | Not applic able. | |
2098 | Introducti on | |
2099 | Purpose an d Scope of Service | |
2100 | Not applic able. | |
2101 | Links to O ther Docum ents | |
2102 | Not applic able. | |
2103 | Service De tails | |
2104 | Not applic able. | |
2105 | Service Id entificati on | |
2106 | Not applic able. | |
2107 | Service Ve rsions | |
2108 | Not applic able. | |
2109 | Summary of Design an d Platform Details | |
2110 | SOA Patter n(s) Imple mented | |
2111 | Not applic able. | |
2112 | COTS Platf orm Vendor Names and Versions for Hostin g Platform | |
2113 | Not applic able. | |
2114 | Dependenci es | |
2115 | Enrollment System (E S) | |
2116 | Service De sign Detai ls | |
2117 | Not applic able. | |
2118 | Service Na me | |
2119 | Not applic able. | |
2120 | Interface | |
2121 | Not applic able. | |
2122 | End Points | |
2123 | Not applic able. | |
2124 | Table 46: Operations or Method s | |
2125 | Operation Name | |
2126 | Inputs | |
2127 | Outputs | |
2128 | Transactio nal Qualit ies if rel evant (Upd ating? Ato mic?, Can participat e in trans action?) | |
2129 | Pre and Po st Conditi ons | |
2130 | Exception (s) | |
2131 | Not applic able. | |
2132 | ||
2133 | Not applic able. | |
2134 | Not applic able. | |
2135 | Not applic able. | |
2136 | Not applic able. | |
2137 | Not applic able. | |
2138 | Not applic able. | |
2139 | Not applic able. | |
2140 | Not applic able. | |
2141 | Not applic able. | |
2142 | Not applic able. | |
2143 | Not applic able. | |
2144 | Message Sc hemas | |
2145 | Not applic able. | |
2146 | Informatio n Model | |
2147 | Not applic able. | |
2148 | Mappings f rom ELDM t o Standard s Based Sc hemas | |
2149 | Not applic able. | |
2150 | Use Cases (Use Case Model) | |
2151 | Not applic able. | |
2152 | Interactio n Diagrams | |
2153 | Not applic able. | |
2154 | Gap Analys is | |
2155 | Not applic able. | |
2156 | Variances from Enter prise Targ et Archite cture | |
2157 | Not applic able. | |
2158 | Variances from SLDs | |
2159 | Not applic able. | |
2160 | Variances from Stand ards and P olicies | |
2161 | Not applic able. | |
2162 | Justificat ion for Ex ceptions a nd Mitigat ion | |
2163 | Not applic able. | |
2164 | External S ystem Inte rface Desi gn | |
2165 | There are no externa l interfac es or spec ial enviro nments inv olved. | |
2166 | Interface Architectu re | |
2167 | There are no externa l interfac es or spec ial enviro nments inv olved. | |
2168 | Interface Detailed D esign | |
2169 | There are no externa l interfac es or spec ial enviro nments inv olved. | |
2170 | Human-Mach ine Interf ace | |
2171 | This proje ct does no t change t he human-m achine int erface, wh ich is don e via the VistA user options a nd CPRS GU I. | |
2172 | Interface Design Rul es | |
2173 | Not applic able. | |
2174 | Inputs | |
2175 | Not applic able. | |
2176 | Outputs | |
2177 | Not applic able. | |
2178 | Navigation Hierarchy | |
2179 | Not applic able. | |
2180 | Screen [x. 1] | |
2181 | Not applic able. | |
2182 | Screen [x. 2] | |
2183 | Not applic able. | |
2184 | Screen [x. 3] | |
2185 | Not applic able. | |
2186 | ||
2187 | Attachment A – Appro val Signat ures | |
2188 | This secti on is used to docume nt the app roval of t he System Design Doc ument. The review sh ould be co nducted fa ce to face where sig natures ca n be obtai ned ‘live’ during th e review. If unable to conduct a face-to -face meet ing then i t should b e held via LiveMeeti ng and con currence c aptured du ring the m eeting. Th e Scribe s hould add /es/name b y each pos ition cite d. Example provided below. | |
2189 | The Busine ss Sponsor and Proje ct Manager are requi red to sig n. | |
2190 | ||
2191 | __________ __________ __________ __________ __________ __________ __________ ________ | |
2192 | Signed:Dat e: | |
2193 | < Business Sponsor > | |
2194 | ||
2195 | __________ __________ __________ __________ __________ __________ __________ ________ | |
2196 | Signed:Dat e: | |
2197 | Loren Behu niak, Proj ect Manage r | |
2198 | ||
2199 | ||
2200 | Additional Informati on | |
2201 | This secti on and its sub-secti ons are to be determ ined. Blan k sections have been maintaine d for vers ion contro l. | |
2202 | Identifica tion of Te chnology a nd Standar ds | |
2203 | Not applic able. | |
2204 | Constraini ng Policie s, Directi ves and Pr ocedures | |
2205 | Not applic able. | |
2206 | Requiremen ts Traceab ility Matr ix | |
2207 | Not applic able. | |
2208 | Packaging and Instal lation | |
2209 | Not applic able. | |
2210 | Design Met rics | |
2211 | Not applic able. | |
2212 | ||
2213 | Appendix A : Data Dic tionaries Created/Mo dified | |
2214 | (See Below ) | |
2215 | Data Dicti onaries Cr eated/Modi fied | |
2216 | ||
2217 | CONDENSED DATA DICTI ONARY---OT H ELIGIBIL ITY CLOCK FILE (#33) UCI: VISTA ,ROU VER SION: 5.3 | |
2218 | ||
2219 | STORED IN: ^DGOTH(33 , MA R 16,2018 PAGE 1 | |
2220 | ---------- ---------- ---------- ---------- ---------- ---------- ---------- ---------- ---------- ---------- ---------- ---------- ---------- -- | |
2221 | ||
2222 | FILE SECUR ITY | |
2223 | DD SE CURITY : @ DE LETE SECUR ITY: @ | |
2224 | READ SECURITY : @ LA YGO SECURI TY : @ | |
2225 | WRITE SECURITY : @ | |
2226 | CROSS REFE RENCED BY: | |
2227 | PATI ENT(B) | |
2228 | ||
2229 | ||
2230 | FILE ST RUCTURE | |
2231 | ||
2232 | FIELD FIELD | |
2233 | NUMBER NAME | |
2234 | ||
2235 | .01 PATIENT (R P2'), [0;1 ] | |
2236 | .02 STATUS (S) , [0;2] | |
2237 | .03 VBA ADJUDI CATION (S) , [0;3] | |
2238 | .04 CREATED BY (P200'), [0;4] | |
2239 | .05 DATE CREAT ED (D), [0 ;5] | |
2240 | 1 OTH 365 DA YS CLOCK ( Multiple-3 3.01), [1; 0] | |
2241 | .01 365 D AYS PERIOD NUMBER (M NJ3,0), [0 ;1] | |
2242 | .02 START DATE (D), [0;2] | |
2243 | .03 AUTHO RIZED BY ( P200'), [0 ;3] | |
2244 | .04 DATE AUTHORIZED (D), [0;4 ] | |
2245 | .05 ENTER ED OR EDIT ED BY (P20 0'), [0;5] | |
2246 | .06 DATE ENTERED OR EDITED (D ), [0;6] | |
2247 | 1 OTH 9 0 DAYS CLO CK (Multip le-33.11), [1;0] | |
2248 | .01 90 DAYS PE RIOD NUMBE R (MNJ1,0) , [0;1] | |
2249 | .02 START DATE (D), [0;2 ] | |
2250 | .03 AUTHORIZED BY (P200' ), [0;3] | |
2251 | .04 DATE AUTHO RIZED (D), [0;4] | |
2252 | .05 ENTERED OR EDITED BY (P200'), [0;5] | |
2253 | .06 DATE ENTER ED OR EDIT ED (D), [0 ;6] | |
2254 | ||
2255 | ||
2256 | Select DAT A DICTIONA RY UTILITY OPTION: | |
2257 | FILE ST RUCTURE | |
2258 | ||
2259 | FIELD FIELD | |
2260 | NUMBER NAME | |
2261 | ||
2262 | .001 NUMBER (NJ 15,0I), [ ] | |
2263 | .01 PATIENT NA ME (RP2'I) , [0;1] | |
2264 | .02 FLAG NAME (RV), [0;2 ] | |
2265 | .03 STATUS (RS ), [0;3] | |
2266 | .04 OWNER SITE (RP4'I), [0;4] | |
2267 | .05 ORIGINATIN G SITE (RP 4'I), [0;5 ] | |
2268 | .06 REVIEW DAT E (DI), [0 ;6] | |
2269 | 1 ASSIGNMENT NARRATIVE (Multiple -26.132), [1;0] | |
2270 | .01 ASSIG NMENT NARR ATIVE (WL) , [0;1] | |
2271 | 2 DBRS NUMBE R (Multipl e-26.131), [2;0] | |
2272 | .01 DBRS NUMBER (MF J18), [0;1 ] | |
2273 | .02 OTHER DBRS DATA (FJ60), [ 0;2] | |
2274 | .03 DATE (D), [0;3] | |
2275 | ||
2276 | FILE ST RUCTURE | |
2277 | ||
2278 | FIELD FIELD | |
2279 | NUMBER NAME | |
2280 | ||
2281 | .001 NUMBER (NJ 15,0I), [ ] | |
2282 | .01 PRF ASSIGN MENT (RP26 .13'I), [0 ;1] | |
2283 | .02 DATE/TIME (RDI), [0; 2] | |
2284 | .03 ACTION (RS I), [0;3] | |
2285 | .04 ENTERED BY (RP200'I) , [0;4] | |
2286 | .05 APPROVED B Y (RP200'O I), [0;5] | |
2287 | .06 TIU PN LIN K (RP8925' I), [0;6] | |
2288 | .07 DBRS NO. ( FJ14), [0; 7] | |
2289 | .08 OTHER DBRS DATA (FJ6 0), [0;8] | |
2290 | .09 ORIGINATIN G FACILITY (P4'), [0 ;9] | |
2291 | 1 HISTORY CO MMENTS (Mu ltiple-26. 141), [1;0 ] | |
2292 | ||
2293 | .01 HISTO RY COMMENT S (WL), [0 ;1] | |
2294 | 2 DBRS NUMBE R (Multipl e-26.142), [2;0] | |
2295 | .01 DBRS# (MFJ18), [0;1] | |
2296 | .02 DBRS OTHER (FJ6 0), [0;2] | |
2297 | .03 DATE (D), [0;3] | |
2298 | .04 DBRS OTHER (FJ6 0), [0;4] | |
2299 | .05 DBRS OTHER ACTI ON (S), [0 ;5] | |
2300 | ||
2301 | ||
2302 | ||
2303 | FILE ST RUCTURE | |
2304 | ||
2305 | FIELD FIELD | |
2306 | NUMBER NAME | |
2307 | ||
2308 | .01 NAME (RNJ1 ,0X), [0;1 ] | |
2309 | .02 FACILITY N AME (R*P4' ), [0;2] | |
2310 | .03 FILE IN BA CKGROUND ( S), [0;3] | |
2311 | .04 FILER STAR TED (D), [ 0;4] | |
2312 | .05 FILER STOP PED (D), [ 0;5] | |
2313 | .06 FILER LAST RAN (D), [0;6] | |
2314 | .07 FILER UCI, VOL (F), [ 0;7] | |
2315 | .08 FILER HANG TIME (NJ2 ,0), [0;8] | |
2316 | .09 COPAY BACK GROUND ERR OR GROUP ( P3.8'), [0 ;9] | |
2317 | .1 FILER QUEU ED (S), [0 ;10] | |
2318 | .11 MEANS TEST BILLING M AIL GROUP (P3.8'), [ 0;11] | |
2319 | .12 PER DIEM S TART DATE (D), [0;12 ] | |
2320 | .13 COPAY EXEM PTION MAIL GROUP (P3 .8), [0;13 ] | |
2321 | .14 USE ALERTS (*S), [0; 14] | |
2322 | .15 SUPPRESS M T INS BULL ETIN (S), [0;15] | |
2323 | .16 LAST LTC C OMPLETION DATE (D), [0;16] | |
2324 | 1.01 NAME OF CL AIM FORM S IGNER (F), [1;1] | |
2325 | 1.02 TITLE OF C LAIM FORM SIGNER (F) , [1;2] | |
2326 | 1.03 *CAN REVIE WER AUTHOR IZE? (S), [1;3] | |
2327 | 1.04 *REMARKS O N EACH EDI CLAIM (F) , [1;4] | |
2328 | 1.05 FEDERAL TA X NUMBER ( RF), [1;5] | |
2329 | 1.06 BLUE CROSS /SHIELD PR OVIDER # ( RF), [1;6] | |
2330 | 1.07 BILL CANCE LLATION MA ILGROUP (P 3.8'), [1; 7] | |
2331 | 1.08 BILLING SU PERVISOR N AME (RP200 '), [1;8] | |
2332 | 1.09 BILL DISAP PROVED MAI LGROUP (P3 .8'), [1;9 ] | |
2333 | 1.11 *CAN INITI ATOR REVIE W (S), [1; 11] | |
2334 | 1.14 MAS SERVIC E POINTER (RP49'), [ 1;14] | |
2335 | 1.15 CAN CLERK ENTER NON- PTF CODES? (S), [1;1 5] | |
2336 | 1.16 ASK HINQ I N MCCR (S) , [1;16] | |
2337 | 1.17 USE OP CPT SCREEN? ( S), [1;17] | |
2338 | 1.18 *DEFAULT A MB SURG RE V CODE (*P 399.2'), [ 1;18] | |
2339 | 1.19 TRANSFER P ROCEDURES TO SCHED? (S), [1;19 ] | |
2340 | 1.2 HOLD MT BI LLS W/INS (S), [1;20 ] | |
2341 | 1.21 MEDICARE P ROVIDER NU MBER (F), [1;21] | |
2342 | 1.22 MULTIPLE F ORM TYPES (S), [1;22 ] | |
2343 | 1.23 CAN INITIA TOR AUTHOR IZE? (S), [1;23] | |
2344 | 1.24 BASC START DATE (D), [1;24] | |
2345 | 1.25 DEFAULT DI VISION (P4 0.8'), [1; 25] | |
2346 | 1.27 CMS-1500 A DDRESS COL UMN (NJ2,0 ), [1;27] | |
2347 | 1.28 *DEFAULT R X REFILL R EV CODE (* P399.2'), [1;28] | |
2348 | 1.29 DEFAULT RX REFILL DX (*P80'), [1;29] | |
2349 | 1.3 DEFAULT RX REFILL CP T (*P81'), [1;30] | |
2350 | 1.31 UB-04 ADDR ESS COLUMN (NJ2,0), [1;31] | |
2351 | 1.32 CMS-1500 P RINT LEGAC Y ID (S), [1;32] | |
2352 | 1.33 UB-04 PRIN T LEGACY I D (S), [1; 33] | |
2353 | 2.01 *AGENT CAS HIER MAIL SYMBOL (F) , [2;1] | |
2354 | 2.02 *AGENT CAS HIER STREE T ADDRESS (F), [2;2] | |
2355 | 2.03 *AGENT CAS HIER CITY (F), [2;3] | |
2356 | 2.04 *AGENT CAS HIER STATE (P5'), [2 ;4] | |
2357 | 2.05 *AGENT CAS HIER ZIP C ODE (FX), [2;5] | |
2358 | 2.06 *AGENT CAS HIER PHONE NUMBER (F ), [2;6] | |
2359 | 2.07 CANCELLATI ON REMARK FOR FISCAL (F), [2;7 ] | |
2360 | 2.08 INPT HEALT H SUMMARY (P142'), [ 2;8] | |
2361 | 2.09 OUTPT HEAL TH SUMMARY (P142'), [2;9] | |
2362 | 2.1 *FACILITY NAME FOR B ILLING (RF ), [2;10] | |
2363 | 2.11 SITE CONTA CT PHONE N UMBER (F), [2;11] | |
2364 | 3.01 *CONVERSIO N LAST BIL L DATE (D) , [3;1] | |
2365 | 3.02 *CONVERSIO N BREAK DA TE (D), [3 ;2] | |
2366 | 3.03 COPAY EXEM PTION CONV . STARTED (NJ7,0), [ 3;3] | |
2367 | 3.04 COPAY EXEM PTION LAST DFN (NJ9, 0), [3;4] | |
2368 | 3.05 TOTAL PATI ENTS CONVE RTED (NJ9, 0), [3;5] | |
2369 | 3.06 TOTAL PATI ENTS EXEMP T (NJ9,0), [3;6] | |
2370 | 3.07 TOTAL PATI ENT NON-EX EMPT (NJ9, 0), [3;7] | |
2371 | 3.08 COUNT OF E XEMPT BILL S (NJ9,0), [3;8] | |
2372 | 3.09 AMOUNT OF CHARGES CH ECKED (NJ9 ,0), [3;9] | |
2373 | 3.1 TOTAL EXEM PT DOLLAR AMOUNT (NJ 9,0), [3;1 0] | |
2374 | 3.11 AMOUNT OF NON-EXEMPT CHARGES ( NJ9,0), [3 ;11] | |
2375 | 3.12 AMOUNT OF CANCELED C HARGES (NJ 9,0), [3;1 2] | |
2376 | 3.13 COPAY EXEM PTION STAR T DATE (RD ), [3;13] | |
2377 | 3.14 COPAY EXEM PTION STOP DATE (RDI ), [3;14] | |
2378 | 3.15 NON-EXEMPT PATIENTS CONVERTED (NJ9,0), [ 3;15] | |
2379 | 3.16 TOTAL BILL S DURING C ONVERSION (NJ9,0), [ 3;16] | |
2380 | 3.17 COUNT OF B ILLS CANCE LED (NJ9,0 ), [3;17] | |
2381 | 3.18 INSURANCE CONVERSION COMPLETE (RDI), [3; 18] | |
2382 | 3.19 BILL/CLAIM S CONV. CO MPLETE (RD I), [3;19] | |
2383 | 3.2 CURRENT IN PATIENTS L OADED (RDI ), [3;20] | |
2384 | 4.01 INSURANCE EXTENDED H ELP (S), [ 4;1] | |
2385 | 4.02 PATIENT OR INSURANCE COMPANY ( V), [4;2] | |
2386 | 4.03 HEALTH INS URANCE POL ICY (F), [ 4;3] | |
2387 | 4.04 NEW INSURA NCE MAIL G ROUP (P3.8 '), [4;4] | |
2388 | 4.05 CENTRAL CO LLECTION M AIL GROUP (F), [4;5] | |
2389 | 4.06 INSURANCE COMPANY (* P36'), [4; 6] | |
2390 | 4.07 IVM CENTER MAIL GROU P (F), [4; 7] | |
2391 | 4.08 INS. CO. D ELETION TA SK (NJ12,0 ), [4;8] | |
2392 | 5.01 ADMISSION SHEET HEAD ER LINE 1 (F), [5;1] | |
2393 | 5.02 ADMISSION SHEET HEAD ER LINE 2 (F), [5;2] | |
2394 | 5.03 ADMISSION SHEET HEAD ER LINE 3 (F), [5;3] | |
2395 | 6.01 CLAIMS TRA CKING STAR T DATE (D) , [6;1] | |
2396 | 6.02 INPATIENT CLAIMS TRA CKING (S), [6;2] | |
2397 | 6.03 OUTPATIENT CLAIMS TR ACKING (S) , [6;3] | |
2398 | 6.04 PRESCRIPTI ON CLAIMS TRACKING ( S), [6;4] | |
2399 | 6.05 PROSTHETIC S CLAIMS T RACKING (S ), [6;5] | |
2400 | 6.06 USE ADMISS ION SHEETS (S), [6;6 ] | |
2401 | 6.07 RANDOM SAM PLE DATE ( D), [6;7] | |
2402 | 6.08 MEDICINE S AMPLE SIZE (RNJ2,0), [6;8] | |
2403 | 6.09 MEDICINE W EEKLY ADMI SSIONS (NJ 2,0), [6;9 ] | |
2404 | 6.1 MEDICINE R ANDOM NUMB ER (NJ2,0) , [6;10] | |
2405 | 6.11 MEDICINE E NTRIES MET (NJ2,0), [6;11] | |
2406 | 6.12 MEDICINE A DMISSION C OUNTER (NJ 2,0), [6;1 2] | |
2407 | 6.13 SURGERY SA MPLE SIZE (NJ2,0), [ 6;13] | |
2408 | 6.14 SURGERY WE EKLY ADMIS SIONS (NJ2 ,0), [6;14 ] | |
2409 | 6.15 SURGERY RA NDOM NUMBE R (NJ2,0), [6;15] | |
2410 | 6.16 SURGERY EN TRIES MET (NJ2,0), [ 6;16] | |
2411 | 6.17 SURGERY AD MISSION CO UNTER (NJ2 ,0), [6;17 ] | |
2412 | 6.18 PSYCH SAMP LE SIZE (N J2,0), [6; 18] | |
2413 | 6.19 PSYCH WEEK LY ADMISSI ONS (NJ2,0 ), [6;19] | |
2414 | 6.2 PSYCH RAND OM NUMBER (NJ2,0), [ 6;20] | |
2415 | 6.21 PSYCH ENTR IES MET (N J2,0), [6; 21] | |
2416 | 6.22 PSYCH ADMI SSION COUN TER (NJ2,0 ), [6;22] | |
2417 | 6.23 REPORTS AD D TO CLAIM S TRACKING (S), [6;2 3] | |
2418 | 6.24 AUTO PRINT UNBILLED LIST (S), [6;24] | |
2419 | 6.25 UNBILLED M AIL GROUP (P3.8'), [ 6;25] | |
2420 | 7.01 AUTO BILLE R FREQUENC Y (NJ4,0), [7;1] | |
2421 | 7.02 LAST AUTO BILLER DAT E (D), [7; 2] | |
2422 | 7.03 INPATIENT STATUS (AB ) (S), [7; 3] | |
2423 | 7.04 NUMBER OF DAYS PT CH ARGES HELD (RNJ2,0), [7;4] | |
2424 | 7.05 DEFAULT RX REFILL DX ICD-10 (* P80'), [7; 5] | |
2425 | 8.01 LIVE TRANS MIT 837 QU EUE (F), [ 8;1] | |
2426 | 8.02 DAYS TO WA IT TO PURG E MSGS (NJ 3,0), [8;2 ] | |
2427 | 8.03 AUTO TRANS MIT BILL F REQUENCY ( NJ4,0), [8 ;3] | |
2428 | 8.04 MAX # BILL S IN A BAT CH (NJ2,0) , [8;4] | |
2429 | 8.05 LAST 837 A UTO-TRANSM IT DATE (D ), [8;5] | |
2430 | 8.06 HOURS TO T RANSMIT BI LLS (FX), [8;6] | |
2431 | 8.07 ONLY 1 INS CO PER CL AIM BATCH (S), [8;7] | |
2432 | 8.09 TEST TRANS MIT 837 QU EUE (F), [ 8;9] | |
2433 | 8.1 EDI/MRA AC TIVATED (S ), [8;10] | |
2434 | 8.11 AUTOMATIC MRA EOB PR OCESS? (S) , [8;11] | |
2435 | 8.12 ALLOW MRA EOB PROCES SING? (S), [8;12] | |
2436 | 8.13 DATE MRA F IRST ACTIV ATED (D), [8;13] | |
2437 | 8.14 CMS-1500 A UTO PRINTE R (P3.5'), [8;14] | |
2438 | 8.15 UB-04 AUTO PRINTER ( P3.5'), [8 ;15] | |
2439 | 8.16 EOB AUTO P RINTER (P3 .5'), [8;1 6] | |
2440 | 8.17 AUTOMATIC REG EOB PR OCESS? (S) , [8;17] | |
2441 | 8.19 MRA AUTO P RINTER (P3 .5'), [8;1 9] | |
2442 | 9.01 BILLING PO RT (F), [9 ;1] | |
2443 | 9.02 AWP PORT ( F), [9;2] | |
2444 | 9.03 TCP/IP ADD RESS (F), [9;3] | |
2445 | 9.04 PRIMARY BI LLING TASK (F), [9;4 ] | |
2446 | 9.05 SECONDARY BILLING TA SK (F), [9 ;5] | |
2447 | 9.06 PRIMARY AW P TASK (F) , [9;6] | |
2448 | 9.07 SECONDARY AWP TASK ( F), [9;7] | |
2449 | 9.08 DATE PRIMA RY TASK ST ARTED (D), [9;8] | |
2450 | 9.09 DATE PRIMA RY TASK LA ST RAN (D) , [9;9] | |
2451 | 9.1 SHUTDOWN B ACKGROUND JOBS (S), [9;10] | |
2452 | 9.11 TASK UCI,V OL (F), [9 ;11] | |
2453 | 9.12 AWP CHARGE SET (*P36 3.1'), [9; 12] | |
2454 | 9.13 PRESCRIBER ID (F), [ 9;13] | |
2455 | 9.14 DEA# OVERR IDE PRESC. ID (S), [9;14] | |
2456 | 9.15 PHARM CALC COMPOUND CODE (S), [9;15] | |
2457 | 10.01 PATIENT OR FACILITY (V), [10;1 ] | |
2458 | 10.02 TP INPATIE NT ACTIVE (S), [10;2 ] | |
2459 | 10.03 TP OUTPATI ENT ACTIVE (S), [10; 3] | |
2460 | 10.04 TP PHARMAC Y ACTIVE ( S), [10;4] | |
2461 | 10.05 TP PROSTHE TICS ACTIV E (S), [10 ;5] | |
2462 | 11.01 HIPAA NCPD P ACTIVE F LAG (Sa), [11;1] | |
2463 | 11.03 DEFAULT PA Y-TO PROVI DER (NJ4,0 ), [11;3] | |
2464 | 11.04 DEFAULT TR ICARE PAY- TO PROV (N J4,0), [11 ;4] | |
2465 | 13.01 HMS DIRECT ORY (F), [ 13;1] | |
2466 | 13.02 EII ACTIVE (S), [13; 2] | |
2467 | 13.03 RESULT FIL E NAME (F) , [13;3] | |
2468 | 13.04 DAY OF MON TH RESULT FILE DUE ( NJ2,0), [1 3;4] | |
2469 | 13.05 DAYS BEFOR E LATE MES SAGE SENT (NJ2,0), [ 13;5] | |
2470 | 13.06 MAX EXT FI LE QUE CON FIRM TIME (NJ2,0), [ 13;6] | |
2471 | 13.07 MAX NUM OF RECORDS P ER MESSAGE (NJ4,0), [13;7] | |
2472 | 13.08 EXTRACT FI LES (Multi ple-350.90 06), [13.0 8;0] | |
2473 | .01 EXTRA CT FILE TY PE (MS), [ 0;1] | |
2474 | .02 EXTRA CT FILE AC TIVE (S), [0;2] | |
2475 | .03 FILE NAME (F), [0;3] | |
2476 | .04 AITC DMI QUEUE EMAIL ADDR ESS (F), [ 0;4] | |
2477 | .05 DAY O F MONTH EX TRACT FILE DUE (NJ2, 0), [0;5] | |
2478 | .06 DAYS BEFORE LAT E MESSAGE SENT (NJ1, 0), [0;6] | |
2479 | 15 PRINTED CL AIMS RC EX CLUSIONS ( Multiple-3 50.9399), [15;0] | |
2480 | .01 REVEN UE CODE (P 399.2'), [ 0;1] | |
2481 | 19 PAY-TO PRO VIDERS (Mu ltiple-350 .9004), [1 9;0] | |
2482 | .01 FACIL ITY (M*P4' ), [0;1] | |
2483 | .02 NAME (RF), [0;2 ] | |
2484 | .03 FEDER AL TAX NUM BER (F), [ 0;3] | |
2485 | .04 TELEP HONE NUMBE R (F), [0; 4] | |
2486 | .05 PAREN T PAY-TO P ROVIDER (N J4,0), [0; 5] | |
2487 | 1.01 STREE T ADDRESS 1 (FJ55), [1;1] | |
2488 | 1.02 STREE T ADDRESS 2 (FJ55), [1;2] | |
2489 | 1.03 CITY (F), [1;3] | |
2490 | 1.04 STATE (P5'), [1 ;4] | |
2491 | 1.05 ZIP ( F), [1;5] | |
2492 | 20 BILLING PR OVIDER FAC TYPES (Mu ltiple-350 .9005), [2 0;0] | |
2493 | .01 BILLI NG PROVIDE R FAC TYPE S (M*P4.1' ), [0;1] | |
2494 | .02 PAY-T O PROVIDER TYPE? (S) , [0;2] | |
2495 | 29 TRICARE PA Y-TO PROVI DERS (Mult iple-350.9 29), [29;0 ] | |
2496 | .01 TC FA CILITY (*P 4'), [0;1] | |
2497 | .02 TC NA ME (RF), [ 0;2] | |
2498 | .03 TC FE DERAL TAX NUMBER (F) , [0;3] | |
2499 | .04 TC TE LEPHONE NU MBER (F), [0;4] | |
2500 | .05 TC PA RENT PAY-T O PROVIDER (NJ4,0), [0;5] | |
2501 | 1.01 TC ST REET ADDRE SS 1 (F), [1;1] | |
2502 | 1.02 TC ST REET ADDRE SS 2 (F), [1;2] | |
2503 | 1.03 TC CI TY (F), [1 ;3] | |
2504 | 1.04 TC ST ATE (P5'), [1;4] | |
2505 | 1.05 TC ZI P (F), [1; 5] | |
2506 | 50.01 RUNNING CL AIMSMANAGE R? (S), [5 0;1] | |
2507 | 50.02 CLAIMSMANA GER WORKIN G OK? (S), [50;2] | |
2508 | 50.03 GENERAL ER ROR MSG MA IL GROUP ( P3.8'), [5 0;3] | |
2509 | 50.04 COMM ERR M SG MAIL GR OUP (P3.8' ), [50;4] | |
2510 | 50.05 CLAIMSMANA GER TCP/IP (F), [50; 5] | |
2511 | 50.06 CLAIMSMANA GER PORTS (Multiple- 350.9001), [50.06;0] | |
2512 | .01 CLAIM SMANAGER P ORTS (MF), [0;1] | |
2513 | 50.07 MAILMAN ME SSAGE FLAG (S), [50; 7] | |
2514 | 51.01 FRESHNESS DAYS (RNJ3 ,0), [51;1 ] | |
2515 | 51.02 DAILY MAIL MAN MSG (S ), [51;2] | |
2516 | 51.03 DAILY MSG TIME (FX), [51;3] | |
2517 | 51.04 MESSAGES M AILGROUP ( RP3.8'), [ 51;4] | |
2518 | 51.05 TIMEOUT DA YS (NJ1,0) , [51;5] | |
2519 | 51.06 NUMBER RET RIES (NJ1, 0), [51;6] | |
2520 | 51.07 TIMEOUT MA ILMAN MSG (S), [51;7 ] | |
2521 | 51.08 INQUIRE IN ACTIVE INS URANCE (S) , [51;8] | |
2522 | 51.09 INQUIRE PO PULAR PAYE RS (S), [5 1;9] | |
2523 | 51.1 NO. POPULA R PAYERS ( NJ2,0), [5 1;10] | |
2524 | 51.11 POPULAR IN SUR CO. FR OM DATE (D ), [51;11] | |
2525 | 51.12 POPULAR IN SUR CO. TH RU DATE (D ), [51;12] | |
2526 | 51.13 HL7 RESPON SE PROCESS ING (RS), [51;13] | |
2527 | 51.14 HL7 START TIME (RFX) , [51;14] | |
2528 | 51.15 HL7 MAXIMU M NUMBER ( RNJ5,0), [ 51;15] | |
2529 | 51.16 *CONTACT P ERSON (RP2 00'), [51; 16] | |
2530 | 51.17 BATCH EXTR ACTS (Mult iple-350.9 002), [51. 17;0] | |
2531 | .01 BATCH EXTRACTS (MRS), [0; 1] | |
2532 | .02 ACTIV E? (RS), [ 0;2] | |
2533 | .03 SELEC TION CRITE RIA #1 (NJ 3,0), [0;3 ] | |
2534 | .04 SELEC TION CRITE RIA #2 (NJ 3,0), [0;4 ] | |
2535 | .05 MAXIM UM EXTRACT NUMBER (R NJ5,0), [0 ;5] | |
2536 | .06 SUPPR ESS BUFFER CREATION (S), [0;6] | |
2537 | 51.18 POPULAR PA YERS (Mult iple-350.9 003), [51. 18;0] | |
2538 | .01 POPUL AR PAYER ( MP365.12') , [0;1] | |
2539 | 51.19 HL7 STOP T IME (RFX), [51;19] | |
2540 | 51.2 FAILURE MA ILMAN MSG (S), [51;2 0] | |
2541 | 51.21 MOST POPUL AR LAST SA VE DATE (D ), [51;21] | |
2542 | 51.22 REGISTRATI ON COMPLET E (S), [51 ;22] | |
2543 | 51.23 INQUIRE SE CONDARY IN SURANCES ( S), [51;23 ] | |
2544 | 51.24 MOST POPUL AR LAST SA VED BY (RP 200'), [51 ;24] | |
2545 | 51.25 MEDICARE P AYER (P365 .12'), [51 ;25] | |
2546 | 51.26 RETRY FLAG (S), [51; 26] | |
2547 | 51.27 270 MASTER SWITCH RE ALTIME (S) , [51;27] | |
2548 | 51.28 270 MASTER SWITCH NI GHTLY (S), [51;28] | |
2549 | 51.29 DAILY NIF STATUS CHE CK TIME (F X), [51;29 ] | |
2550 | 52.01 PURGE DAYS 277 RFAI (NJ4,0), [ 52;1] | |
2551 | 52.02 WORKLIST P URGE DAYS 277 RFAI ( NJ2,0), [5 2;2] | |
2552 | 60.01 DEFAULT SE RVICE TYPE CODE 1 (R P365.013') , [60;1] | |
2553 | 60.02 DEFAULT SE RVICE TYPE CODE 2 (P 365.013'), [60;2] | |
2554 | 60.03 DEFAULT SE RVICE TYPE CODE 3 (P 365.013'), [60;3] | |
2555 | 60.04 DEFAULT SE RVICE TYPE CODE 4 (P 365.013'), [60;4] | |
2556 | 60.05 DEFAULT SE RVICE TYPE CODE 5 (P 365.013'), [60;5] | |
2557 | 60.06 DEFAULT SE RVICE TYPE CODE 6 (P 365.013'), [60;6] | |
2558 | 60.07 DEFAULT SE RVICE TYPE CODE 7 (P 365.013'), [60;7] | |
2559 | 60.08 DEFAULT SE RVICE TYPE CODE 8 (P 365.013'), [60;8] | |
2560 | 60.09 DEFAULT SE RVICE TYPE CODE 9 (P 365.013'), [60;9] | |
2561 | 60.1 DEFAULT SE RVICE TYPE CODE 10 ( P365.013') , [60;10] | |
2562 | 60.11 DEFAULT SE RVICE TYPE CODE 11 ( P365.013') , [60;11] | |
2563 | 61.01 SITE SELEC TED SERVIC E CODE 1 ( P365.013') , [61;1] | |
2564 | 61.02 SITE SELEC TED SERVIC E CODE 2 ( P365.013') , [61;2] | |
2565 | 61.03 SITE SELEC TED SERIVC E CODE 3 ( P365.013') , [61;3] | |
2566 | 61.04 SITE SELEC TED SERVIC E CODE 4 ( P365.013') , [61;4] | |
2567 | 61.05 SITE SELEC TED SERVIC E CODE 5 ( P365.013') , [61;5] | |
2568 | 61.06 SITE SELEC TED SERVIC E CODE 6 ( P365.013') , [61;6] | |
2569 | 61.07 SITE SELEC TED SERVIC E CODE 7 ( P365.013') , [61;7] | |
2570 | 61.08 SITE SELEC TED SERVIC E CODE 8 ( P365.013') , [61;8] | |
2571 | 61.09 SITE SELEC TED SERVIC E CODE 9 ( P365.013') , [61;9] | |
2572 | 62.01 LIMIT LENG TH OF EIV FIELDS? (S ), [62;1] | |
2573 | 62.02 CPAC ADM F UTURE DAYS (NJ3,0), [62;2] | |
2574 | 62.03 CPAC APPT PAST DAYS (NJ3,0), [ 62;3] | |
2575 | 62.04 CPAC ADM P AST DAYS ( NJ3,0), [6 2;4] | |
2576 | 62.05 TRICARE AP PT FUTURE DAYS (NJ3, 0), [62;5] | |
2577 | 62.06 TRICARE AD M FUTURE D AYS (NJ3,0 ), [62;6] | |
2578 | 62.07 TRICARE AP PT PAST DA YS (NJ3,0) , [62;7] | |
2579 | 62.08 TRICARE AD M PAST DAY S (NJ3,0), [62;8] | |
2580 | 62.09 PURGE DAYS (RNJ4,0), [62;9] | |
2581 | 62.1 INQUIRY TR IGGER APPT (NJ2,0), [62;10] | |
2582 | 62.11 INQUIRY TR IGGER ADM (NJ2,0), [ 62;11] | |
2583 | 62.12 HSCR RESPO NSE PURGE DAYS (NJ2, 0), [62;12 ] | |
2584 | 62.13 CPAC APPT FUTURE DAY S (NJ3,0), [62;13] | |
2585 | 63 HCSR CLINI C LIST (Mu ltiple-350 .963), [63 ;0] | |
2586 | .01 NAME (P44'), [0 ;1] | |
2587 | .02 INCLU DE FOR ALL PAYERS? ( S), [0;2] | |
2588 | 1 INCLU DE CLINIC FOR PAYERS (Multiple -350.9631) , [1;0] | |
2589 | .01 PAYER (P36 5.12'), [0 ;1] | |
2590 | 64 HCSR WARD LIST (Mult iple-350.9 64), [64;0 ] | |
2591 | .01 NAME (P42'), [0 ;1] | |
2592 | .02 INCLU DE FOR ALL PAYERS? ( S), [0;2] | |
2593 | 1 INCLU DE WARD FO R PAYERS ( Multiple-3 50.9641), [1;0] | |
2594 | .01 PAYER (P36 5.12'), [0 ;1] | |
2595 | 65 HCSR INSCO APPT LIST (Multiple -350.965), [65;0] | |
2596 | .01 NAME (P36'), [0 ;1] | |
2597 | .02 PROTE CTED (NJ1, 0), [0;2] | |
2598 | 66 HCSR INSCO ADM LIST (Multiple- 350.966), [66;0] | |
2599 | .01 NAME (P36'), [0 ;1] | |
2600 | .02 PROTE CTED (NJ1, 0), [0;2] | |
2601 | 70.01 HPID/OEID ACTIVE? (S ), [70;1] | |
2602 | 70.02 SHRPE ACTI VATION DAT E (D), [70 ;2] | |
2603 | 81 PRIMARY PA YER ID TYP ES MED (Mu ltiple-350 .981), [81 ;0] | |
2604 | .01 PRIMA RY PAYER I D TYPES ME D (MP355.9 8), [0;1] | |
2605 | 82 PRIMARY PA YER ID TYP ES COM (Mu ltiple-350 .982), [82 ;0] | |
2606 | .01 PRIMA RY PAYER I D TYPES CO M (MP355.9 8), [0;1] | |
2607 | 99 INS. CO's WITHHOLDIN G SUPPLIME NTAL PAYME NTS (Multi ple-350.99 9), [99;0] | |
2608 | .01 INS. CO'S FOR M RA EXTRACT (MP36'), [0;1] | |
2609 | 100 IB SSVI DI SABLE/ENAB LE (S), [1 00;1] | |
2610 | 101 IB SSVI LA ST INS DAT E XFER (DX ), [100;2] | |
2611 | 102 IB CURRENT PIVOT ENT RY (NJ9,0) , [HL7;1] | |
2612 | 103 IB PIVOT F ILE DAYS T O RETAIN ( NJ3,0), [H L7;2] | |
2613 | ||
2614 | ||
2615 | Select DAT A DICTIONA RY UTILITY OPTION: | |
2616 | ||
2617 | Appendix B : Future C apabilitie s | |
2618 | Activity | |
2619 | New Capabi lity (1) | |
2620 | Feature En hancement (2) | |
2621 | Field Depl oyment (A) | |
2622 | Yes | |
2623 | Yes | |
2624 | Cloud/Web Deployment (B) | |
2625 | No | |
2626 | No | |
2627 | Mobile App lication ( C) | |
2628 | No | |
2629 | No |
Araxis Merge (but not the data content of this report) is Copyright © 1993-2016 Araxis Ltd (www.araxis.com). All rights reserved.