Produced by Araxis Merge on 8/19/2017 8:21:12 PM Eastern Daylight Time. See www.araxis.com for information about Merge. This report uses XHTML and CSS2, and is best viewed with a modern standards-compliant browser. For optimum results when printing this report, use landscape orientation and enable printing of background images and colours in your browser.
# | Location | File | Last Modified |
---|---|---|---|
1 | OSCIF_VSE_v1.3.2_SD_5_3_671.zip | VSE_VIP_25_Epic_User_Stories_Final_July2017.docx | Thu Jul 20 18:14:56 2017 UTC |
2 | OSCIF_VSE_v1.3.2_SD_5_3_671.zip | VSE_VIP_25_Epic_User_Stories_Final_July2017.docx | Sat Aug 19 22:55:37 2017 UTC |
Description | Between Files 1 and 2 |
|
---|---|---|
Text Blocks | Lines | |
Unchanged | 1 | 494 |
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 | VistA Sche duling Enh ancements (VSE 1.3) | |
2 | Veteran Fo cused Inte gration Pr ocess (VIP ) | |
3 | Epic 25 Au to-Populat e CID from RTC | |
4 | User Story Document | |
5 | ||
6 | ||
7 | ||
8 | ||
9 | ||
10 | April 2017 | |
11 | ||
12 | ||
13 | Table of C ontents | |
14 | 1.Purpose2 | |
15 | 2.Assumpti ons, Notes and Gener al Require ments2 | |
16 | 3.Epic Use r Stories3 | |
17 | 3.1.Epic 2 5 – Auto-p opulate CI D from RTC (Rational ID RM 899 126, RTC 4 94688)3 | |
18 | 3.1.1Sub-E pic 25.1 ( Rational I D) – Displ ay ‘Open’ requests a nd auto-po pulate dat a3 | |
19 | 3.1.2Sub-E pic 25.2 ( Rational I D) – Servi ce Connect ed5 | |
20 | 3.1.3Sub-E pic 25.3 ( Rational I D) – View Pre-requis ite Inform ation6 | |
21 | 4.Appendix A – Futur e Requirem ents8 | |
22 | 4.1.Displa y Order De tails as a pop-up wi ndow.8 | |
23 | 4.2.Highli ght New Ap pointment Request8 | |
24 | 4.3.Search Tool8 | |
25 | 4.4.Label change8 | |
26 | 4.5.Transf er to Reca ll/PtCSch8 | |
27 | 5.Appendix B – Scree nshots9 | |
28 | 6.Appendix C – Dispo sition Det ails11 | |
29 | ||
30 | ||
31 | ||
32 | ||
33 | ||
34 | ||
35 | ||
36 | ||
37 | ||
38 | ||
39 | Purpose | |
40 | The VIP Ep ic User St ory Docume nt is auth ored by th e business community for the p urpose of capturing and descri bing the b usiness ne eds of the customer. This doc ument iden tifies wha t capabili ties the s takeholder s and the target use rs need an d provides a focused overview of the req uest requi rements. | |
41 | Assumptio ns, Notes and Genera l Requirem ents | |
42 | The return to clinic (RTC) com munication between p rovider an d schedule r will con tinue to b e through CPRS Order s. | |
43 | Note: Ther e is no di rect link to the Ord ers file. | |
44 | At any tim e an RTC a ppt reques t is dispo sitioned, a notifica tion is se nt to CPRS and the C PRS order will be di scontinued with the dispositio n type. CP RS will th en handle the notifi cation and alert the provider, if necess ary. | |
45 | At any tim e an RTC a ppt reques t is dispo sitioned a ccidentall y, a notif ication is sent to C PRS with t he disposi tion type. CPRS will then hand le the not ification and alert the provid er, if nec essary. | |
46 | If an RTC Order is c anceled by the Provi der, CPRS will notif y VSE; VSE will hand le this di sposition automatica lly and ca ncels the Appointmen t Request on VS GUI with the d isposition reason ‘R emoved/No longer nec essary’. | |
47 | If any act ion is tak en in VSE on the “Ap pointment” (RTC) Req uest the O rder in CP RS will be marked as completed or discon tinued as appropriat e accordin g to busin ess rules. | |
48 | If the app ointment i s schedule d or moved to PtCSch , EWL, etc ., then th e order in CPRS is c ompleted; there will be the ca pability t o transfer the RTC/A PPT REQUES T to PtCSc h. | |
49 | VSE only c ommunicate s with CPR S when the RTC/APPT REQUEST is dispositi oned. | |
50 | ||
51 | ||
52 | ||
53 | ||
54 | ||
55 | Epic User Stories | |
56 | Epic 25 – Auto-popul ate CID fr om RTC (Ra tional ID RM 899126, RTC 49468 8) | |
57 | Sub-Epic 2 5.1 (Ratio nal ID) – Display ‘O pen’ reque sts and au to-populat e data | |
58 | ||
59 | End User: VS GUI Sch edulers an d supervis ors (of sc hedulers) | |
60 | End User A ttributes/ Circumstan ce: Schedu lers/super visors vie w/audit/va lidate pat ient appoi ntment inf ormation | |
61 | Purpose: S chedulers and superv isors view /audit/val idate Clin ically Ind icated Dat e (CID) im ported fro m RTC (Ret urn To Cli nic) order | |
62 | Problem to be solved : The curr ent VistA Scheduling (VS) GUI system req uires manu al update of CID and related f ields that is causin g errors a nd delays in schedul ing the ap pointments . | |
63 | Business P rocess Imp rovement G oal: The G UI must au to-populat e CID and other fiel ds from RT C orders i n CPRS. | |
64 | ||
65 | ||
66 | User Story | |
67 | Features | |
68 | Non-Functi onal Requi rement | |
69 | Business R ules | |
70 | Acceptance Criteria | |
71 | (RationalI D RM 89912 8, RTC 522 255) | |
72 | US 25.1.1 | |
73 | As a VS GU I schedule r, I can v iew order informatio n auto-pop ulated fro m an RTC o rder displ ayed as AP PT/RTC req uest. | |
74 | (RationalI D 899130) | |
75 | FEAT25.1.1 -1 Request ed By (ord ering clin ic locatio n), Reques tor (order ing provid er), Ente red Date, CID, and C linic/Serv ice (clini c location to be sch eduled) fr om VistA a re automat ically imp orted and auto-popul ated in VS GUI as AP PT/RTC Req uest. | |
76 | (RationalI D 899131) | |
77 | FEAT25.1.1 -2 The inf ormation f rom the or der will p opulate in the appt request, t o include the commen ts. | |
78 | (RationalI D 899136) | |
79 | NFR 25.1.1 -1 Must be 508 -Comp liant | |
80 | (RationalI D 899138) | |
81 | BR25.1.1-1 VS GUI wi ll display only ‘Ope n’ request s. | |
82 | ||
83 | Note: When an order is opened in CPRS, a new Appt Request wi ll be crea ted and di splayed on RM Grid. If an orde r is cance lled, the appt reque st will be dispositi oned as “R emoved/No longer nee ded”. This will affe ct display of the re quest on t he RM Grid , rather t han the or der’s stat us directl y. | |
84 | ||
85 | (RationalI D 899139) | |
86 | BR25.1.1-2 Requested By (order ing clinic location) , Requesto r (orderin g provider ), Entere d Date, CI D, and Cli nic/Servic e (clinic location t o be sched uled) from VistA mus t be impor ted and au to-populat ed in VS G UI. | |
87 | (RationalI D 899128) | |
88 | AC25.1.1-1 Resource Management (RM) Grid on the VS GUI displ ayed ‘Open ’ RTC orde r as APPT/ RTC and au to-populat ed with th e followin g fields: Requested By, Entere d Date, CI D, Clinic, Order Det ails. | |
89 | ||
90 | (RationalI D RM 89912 9, RTC 522 261) | |
91 | US 25.1.2 | |
92 | As a VS GU I Schedule r, I can s ee ‘No Lat er Than’ d ate from C PRS RTC in the Comme nts field of the App ointment R equest and in the No tes field of the New Appointme nt as ‘#NL T#. | |
93 | (RationalI D 899132) | |
94 | FEAT25.1.2 -1 ‘No Lat er Than’ d ate from C PRS RTC is auto-popu lated as # NLT# in th e Comments field of the Appoin tment Requ est and in the Notes field of the New Ap pointment. | |
95 | (RationalI D 899137) | |
96 | NFR 25.1.2 -1 Must be 508 compl iant | |
97 | (RationalI D 899140) | |
98 | BR25.1.2-1 No later than infor mation fro m CPRS Ord er Details is displa yed to the scheduler on the Ne w Appointm ent Notes and Appoin tment Requ ests Comme nts fields . | |
99 | Note: Scre enshots ar e included in the Ap pendix. | |
100 | (RationalI D 899129) | |
101 | AC25.1.2-1 No later than date is display ed as #NLT # in: | |
102 | Notes on N ew Appoint ment | |
103 | Comment on Appointme nt Request . | |
104 | ||
105 | ||
106 | Sub-Epic 2 5.2 (Ratio nal ID) – Service Co nnected | |
107 | ||
108 | End User: VS GUI Sch edulers an d supervis ors (of sc hedulers) | |
109 | End User A ttributes/ Circumstan ce: Schedu ler/superv isor is cr eating an appointmen t | |
110 | Purpose: S chedulers and superv isors view /audit/val idate serv ice connec ted inform ation and, if needed , update d ata | |
111 | Problem to be solved : Currentl y provider s are not entering w hether or not an app ointment i s for a se rvice conn ected cond ition when entering an RTC ord er in CPRS . | |
112 | Business P rocess Imp rovement G oal: The G UI must de fault to s ervice con nected app ointment t ype or Cli nic depend ing on the service c onnected d isabilitie s followin g business rules. | |
113 | ||
114 | ||
115 | User Story | |
116 | Features | |
117 | Non-Functi onal Requi rement | |
118 | Business R ules | |
119 | Acceptance Criteria | |
120 | (RationalI D RM 89912 9, RTC 522 261) | |
121 | US 25.2.2 | |
122 | As a VS GU I Schedule r, I can s ee that th e Service Connected is set to default fo llowing bu siness rul es. | |
123 | (RationalI D 899132) | |
124 | If SC is g reater tha n 50%, the n the serv ice connec ted is sel ected. | |
125 | If the SC is less th an 50%, th en the ser vice conne cted is no t selected . | |
126 | (RationalI D 899137) | |
127 | Must be 50 8 complian t | |
128 | (RationalI D 899140) | |
129 | Current bu siness rul es for app ointment r equest & a ppointment schedulin g need to apply for service co nnected di sabilities as well. | |
130 | SC greater than 50% = SC appoi ntment typ e will def ault but t he SC bloc k & appoin tment type is editab le. | |
131 | SC less th an 50% = c linic defa ult for ap pointment type but t he SC bloc k and appo intment ty pe is edit able. | |
132 | (RationalI D 899129) | |
133 | VS GUI Sch eduler can see that the ‘Svc R elated’ ra dio button on the Ap pointment Request is checked o r unchecke d based on the busin ess rules. | |
134 | (RationalI D RM 89912 9, RTC 522 261) | |
135 | US 25.2.3 | |
136 | As a VS GU I Schedule r, I can u pdate serv ice connec ted and ap pointment type data. | |
137 | (RationalI D 899132) | |
138 | SC block & appointme nt type is editable. | |
139 | (RationalI D 899137) | |
140 | Must be 50 8 complian t | |
141 | (RationalI D 899140) | |
142 | SC greater than 50% = SC appoi ntment typ e will def ault but t he SC bloc k & appoin tment type is editab le. | |
143 | SC less th an 50% = c linic defa ult for ap pointment type but t he SC bloc k and appo intment ty pe is edit able. | |
144 | (RationalI D 899129) | |
145 | VS GUI Sch eduler can change ‘S vc Related ’ and ‘App ointment T ype’ field s even if they conta in default informati on. | |
146 | ||
147 | Sub-Epic 2 5.3 (Ratio nal ID) – View Pre-r equisite I nformation | |
148 | End User: VS GUI Sch edulers an d Supervis ors (of Sc hedulers) | |
149 | End User A ttributes/ Circumstan ce: Schedu lers/Super visors vie w/audit/va lidate pat ient appoi ntment inf ormation | |
150 | Purpose: S chedulers and Superv isors view pre-requi sites befo re schedul ing the ap pointments . | |
151 | Problem to be solved : The curr ent VS GUI system do es not inc lude pre-r equisites for viewin g. | |
152 | Business P rocess Imp rovement G oal: VHA D irective 1 230 - Cont inuous aud iting and improvemen t process of schedul ing activi ties such as the tim eliness an d appropri ateness of schedulin g actions, accuracy of CID or PD dates a nd telepho ne call qu ality | |
153 | Assumption : Function ality and informatio n currentl y availabl e in the V S GUI is n ot to be r eplaced by any new a dditions i mplemented per this user story and assoc iated requ irement. | |
154 | ||
155 | VHA Busine ss Rules: | |
156 | ||
157 | User Story | |
158 | Features | |
159 | Non-Functi onal Requi rement | |
160 | Business R ules | |
161 | Acceptance Criteria | |
162 | US 25.3.1 | |
163 | As a VS GU I schedule r, I can v iew the pr e-requisit es. | |
164 | FEAT 25.3. 1 | |
165 | Pre-requis ites from CPRS are d isplayed t o the sche duler on t he VS GUI as view-on ly, non-ed itable inf ormation f or a sched uled appoi ntment. | |
166 | NFR 25.3.1 -1 | |
167 | Must be 50 8 complian t | |
168 | ||
169 | NFR 25.3.1 -2 | |
170 | A red flag on the re cord can b e an indic ation of t he availab ility of e ither comm ents or pr e-requisit es. | |
171 | BR 25.3.1 | |
172 | Pre-requis ites are d isplayed a s view-onl y/non-edit able data. | |
173 | AC 25.3.1- 1 | |
174 | The record is highli ghted with a red fla g indicati ng the ava ilability of pre-req uisites. | |
175 | ||
176 | AC 25.3.1- 2 | |
177 | Upon selec tion of th e record, pre-requis ite inform ation is d isplayed a s view-onl y non-edit able data on the VS GUI pop up window. | |
178 | US 25.3.2 | |
179 | As a VS GU I schedule r, I can v iew the pr e-requisit e informat ion while working on the patie nt record. | |
180 | FEAT 25.3. 2 | |
181 | Pre-requis ite inform ation is d isplayed u ntil the w indow is c losed or a new patie nt request is select ed. | |
182 | NFR 25.3.2 | |
183 | Must be 50 8 complian t | |
184 | BR 25.3.2 | |
185 | Scheduler should be able to wo rk on the record whi le the pre -requisite s window i s open. | |
186 | AC 25.3.2- 1 | |
187 | ||
188 | Pre-requis ite inform ation is d isplayed u ntil eithe r a) the w indow is c losed or b ) a new pa tient requ est is sel ected. | |
189 | ||
190 | AC 25.3.2- 2 | |
191 | Scheduler is able to work on t he record while the pre-requis ites windo w is open. | |
192 | ||
193 | ||
194 | ||
195 | ||
196 | Appendix A – Future Requiremen ts | |
197 | Display Or der Detail s as a pop -up window . | |
198 | The Order Details fr om CPRS ar e availabl e to the s cheduler i n a new “V iew Order Details” m enu select ion and po p up windo w. This wi ll allow a ll informa tion from the order in CPRS to be displa yed to the scheduler to includ e addition al fields used in th e order se t up for t hat locati on. Whate ver a user sees when they doub le click o n the orde r in CPRS should be shown in t his Order Details wi ndow. | |
199 | Scheduler is able to move betw een Order Details po p-up scree n and the transfer t o Recall/P tCSch disp osition sc reen or ma ke an appo intment sc reen. | |
200 | The Order Details po p up windo w does not close unt il the sch eduler act ively clos es it. | |
201 | Highlight New Appoin tment Requ est | |
202 | New appoin tment requ ests are f lagged or otherwise highlighte d on the R M Grid unt il viewed by the sch eduler. | |
203 | Search Too l | |
204 | Ability to use the q uery tool to search for and pr oduce a wo rk list of open RTC APPT Reque sts. | |
205 | The query tool will allow VS G UI users t o search f or and act on a list of RTC Ap pt Request s, just li ke they ca n with Vet eran or no rmal Appoi ntment Req uests | |
206 | Search rul es would r emain the same; RTC Appt Reque st is adde d as an op tion on th e filter. | |
207 | Schedulers should be able to a ct on the request li st produce d from the query too l as if th ey were in each indi vidual cha rt (make a ppt, disco ntinue/can cel, or tr ansfer Rec all/PtCSch ). | |
208 | Label chan ge | |
209 | Label chan ge from CI D/Preferre d Date to Pt Indicat ed Date (P ID). | |
210 | Transfer t o Recall/P tCSch | |
211 | A disposit ion option will be a vailable t o "Transfe r to Recal l/PtCSch”, similar t o the exis ting “Tran sfer to EW L” disposi tion optio n. | |
212 | ||
213 | ||
214 | Appendix B – Screens hots | |
215 | ||
216 | The follow ing screen shots prov ide visual to help c larify the requireme nt definit ions. | |
217 | “#NLT#” | |
218 | ||
219 | ||
220 | ||
221 | ||
222 | ||
223 | Appendix C – Disposi tion Detai ls | |
224 | ||
225 | RTC inform ation | |
226 | 409.85,21 DISPOS ITION DIS ;3 SET | |
227 | ||
228 | APPT Reque st Dispos itions | |
229 | RTC Order Dispositio n | |
230 | 'D' FOR DE ATH | |
231 | Discontinu ed – alert to Provid er | |
232 | 'NC' FOR R EMOVED/NON -VA CARE | |
233 | Discontinu ed – alert to Provid er | |
234 | 'SA' FOR R EMOVED/SCH EDULED-ASS IGNED | |
235 | Completed | |
236 | 'CC' FOR R EMOVED/VA CONTRACT C ARE | |
237 | Discontinu ed – alert to Provid er | |
238 | 'NN' FOR R EMOVED/NO LONGER NEC ESSARY | |
239 | Discontinu ed – alert to Provid er | |
240 | 'ER' FOR E NTERED IN ERROR | |
241 | Discontinu ed – alert to Provid er | |
242 | 'TR' FOR T RANSFERRED TO EWL | |
243 | Completed | |
244 | Moved to R ecall | |
245 | Completed | |
246 | ||
247 |
Araxis Merge (but not the data content of this report) is Copyright © 1993-2016 Araxis Ltd (www.araxis.com). All rights reserved.