Produced by Araxis Merge on 10/4/2017 8:04:42 AM Central Daylight Time. See www.araxis.com for information about Merge. This report uses XHTML and CSS2, and is best viewed with a modern standards-compliant browser. For optimum results when printing this report, use landscape orientation and enable printing of background images and colours in your browser.
| # | Location | File | Last Modified |
|---|---|---|---|
| 1 | rdk.zip\rdk\product\tests\acceptance-tests\features | F883_Triage_Consult.feature | Mon Aug 21 12:51:01 2017 UTC |
| 2 | rdk.zip\rdk\product\tests\acceptance-tests\features | F883_Triage_Consult.feature | Tue Oct 3 20:20:24 2017 UTC |
| Description | Between Files 1 and 2 |
|
|---|---|---|
| Text Blocks | Lines | |
| Unchanged | 55 | 274 |
| Changed | 54 | 138 |
| 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 | @F883 @JBP M @future | |
| 2 | Feature: T riage a Co nsult Orde r | |
| 3 | # Sep 6 42 1 | |
| 4 | ||
| 5 | @signed_co nsult_in_t asks | |
| 6 | Scenario: | |
| 7 | Given a pa tient with pid " R E D A CTED ;100728" h as been sy nced throu gh the RDK API | |
| 8 | And the client has the curre nt deploym entid | |
| 9 | And the us er " R E D A CTED ; DNS " has star ted a cons ult with p arameters | |
| 10 | | pa rameters | v alue | | |
| 11 | | icn | R E D A CTED ;100728 | | |
| 12 | | as signedTo | [ FC:PANORAM A(500)/TF: Physical T herapy(81) ] | | |
| 13 | | executio nUserId | urn:va:u ser: R E D A CTED :100000002 72 | | |
| 14 | | ex ecutionUse rName | K HAN, VIHAA N | | |
| 15 | | fo rmAction | a ccepted | | |
| 16 | | or deringProv ider displ ayName | K HAN, VIHAA N | | |
| 17 | | ordering Provider u id | urn:va:u ser: R E D A CTED :100000002 72 | | |
| 18 | | de stination facility c ode | 5 00 | | |
| 19 | | de stination facility n ame | P ANORAMA | | |
| 20 | And a su ccessful r esponse is returned | |
| 21 | And the successful response contains a processIn stanceId | |
| 22 | ||
| 23 | When the " R E D A CTED ; DNS " client r equests ta sks instan ces for "u ser" and " teamroles" | |
| 24 | Then a s uccessful response i s returned | |
| 25 | And the task assoc iated with the proce ssInstance Id has | |
| 26 | | pa rameter | v alue | | |
| 27 | | ASSIGNED TO | R E D A CTED ;100000002 72, | | |
| 28 | | TA SKNAME | S ign Consul t | | |
| 29 | | ST ATUS | R eserved | | |
| 30 | | DE FINITIONID | C onsult.Sig n | | |
| 31 | | AC TIVITYASSI GNEDTO | [ FC:PANORAM A(500)/TF: Physical T herapy(81) ] | | |
| 32 | ||
| 33 | When the " R E D A CTED ; DNS " client r equests th e sign upd ate start | |
| 34 | | pa rameter | v alue | | |
| 35 | | icn | R E D A CTED ;100728 | | |
| 36 | | st ate | s tart | | |
| 37 | Then a successful response is returne d | |
| 38 | ||
| 39 | When the " R E D A CTED ; DNS " client s igns the c onsult ord er | |
| 40 | | pa rameter | value | | |
| 41 | | pid | R E D A CTED ;100728 | | |
| 42 | | site | R E D A CTED | | |
| 43 | | uid | urn:va:u ser: R E D A CTED :100000002 72 | | |
| 44 | | duz site | R E D A CTED | | |
| 45 | | du z id | 1000000027 2 | | |
| 46 | | fa cility | PANORAMA | | |
| 47 | | fi rstname | VIHAAN | | |
| 48 | | la stname | KHAN | | |
| 49 | | di vision | 500 | | |
| 50 | Then a s uccessful response i s returned | |
| 51 | And the response r eports val id signatu re | |
| 52 | When the " R E D A CTED ; DNS " client r equests th e task is updated to be signed | |
| 53 | | pa rameter | v alue | | |
| 54 | | patient_ pid | R E D A CTED ;100728 | | |
| 55 | | icn | R E D A CTED ;100728 | | |
| 56 | | executio nUserId | urn:va:u ser: R E D A CTED :100000002 72 | | |
| 57 | | ex ecutionUse rName | K HAN, VIHAA N | | |
| 58 | | fo rmAction | a ccepted | | |
| 59 | | or deringProv ider displ ayName | K HAN, VIHAA N | | |
| 60 | | ordering Provider u id | urn:va:u ser: R E D A CTED :100000002 72 | | |
| 61 | | st ate | c omplete | | |
| 62 | Then a s uccessful response i s returned | |
| 63 | ||
| 64 | When the " R E D A CTED ; PL " client r equests ta sks instan ces for "u ser" and " teamroles" | |
| 65 | Then a s uccessful response i s returned | |
| 66 | And the task assoc iated with the proce ssInstance Id has | |
| 67 | | para meter | v alue | | |
| 68 | ||
| 69 | ||
| 70 | @eConsult @DE6792 | |
| 71 | Scenario: | |
| 72 | Given a pa tient with pid " R E D A CTED ;100728" h as been sy nced throu gh the RDK API | |
| 73 | And the client has the curre nt deploym entid | |
| 74 | And the us er R E D A CTED ; DNS has create d and sign ed a consu lt for pat ient " R E D A CTED ;100728" | |
| 75 | And the us er " R E D A CTED ; PL " signals to activat e order | |
| 76 | | pa rameter | value | | |
| 77 | | userId | urn:va:u ser: R E D A CTED :100000002 72 | | |
| 78 | ||
| 79 | When the u ser " R E D A CTED ; PL " requests to update task to e Consult (s tart) | |
| 80 | | pa rameter | v alue | | |
| 81 | | icn | R E D A CTED ;100728 | | |
| 82 | | st ate | s tart | | |
| 83 | ||
| 84 | Then a s uccessful response i s returned | |
| 85 | When the u ser " R E D A CTED ; PL " requests to update task to e Consult | |
| 86 | | pa rameter | v alue | | |
| 87 | | icn | R E D A CTED ;100728 | | |
| 88 | | st ate | c omplete | | |
| 89 | | or deringProv ider displ ayName | K HAN, VIHAA N | | |
| 90 | | ordering Provider u id | urn:va:u ser: R E D A CTED :100000002 72 | | |
| 91 | | fo rmAction | e Consult | | |
| 92 | | executio nUserId | urn:va:u ser: R E D A CTED :100000002 71 | | |
| 93 | | ex ecutionUse rName | X IU, MARGAR ET | | |
| 94 | | de stination facility c ode | 5 00 | | |
| 95 | | de stination facility n ame | P ANORAMA | | |
| 96 | Then a s uccessful response i s returned | |
| 97 | ||
| 98 | When the " R E D A CTED ; PL " client r equests ta sks instan ces for "p atient" an d "teamrol es" for pa tient " R E D A CTED ;100728" | |
| 99 | Then a s uccessful response i s returned | |
| 100 | And the task assoc iated with the proce ssInstance Id has | |
| 101 | | parame ter | val ue | | |
| 102 | | TASKNA ME | Com plete Cons ult | | |
| 103 | | DEFINI TIONID | C onsult.Com plete | | |
| 104 | ||
| 105 | @return_fo r_clarafic ation | |
| 106 | Scenario: | |
| 107 | Given a pa tient with pid " R E D A CTED ;100728" h as been sy nced throu gh the RDK API | |
| 108 | And the client has the curre nt deploym entid | |
| 109 | And the us er R E D A CTED ; DNS has create d and sign ed a consu lt for pat ient " R E D A CTED ;100728" | |
| 110 | And the us er " R E D A CTED ; PL " signals to activat e order | |
| 111 | | pa rameter | value | | |
| 112 | | userId | urn:va:u ser: R E D A CTED :100000002 72 | | |
| 113 | When the u ser " R E D A CTED ; PL " requests to update task to R eturn for Claraficat ion (start ) | |
| 114 | | pa rameter | v alue | | |
| 115 | | icn | R E D A CTED ;100728 | | |
| 116 | | st ate | s tart | | |
| 117 | Then a s uccessful response i s returned | |
| 118 | When the u ser " R E D A CTED ; PL " requests to update task to R eturn for Claraficat ion | |
| 119 | | pa rameter | v alue | | |
| 120 | | icn | R E D A CTED ;100728 | | |
| 121 | | st ate | c omplete | | |
| 122 | | or deringProv ider displ ayName | K HAN, VIHAA N | | |
| 123 | | ordering Provider u id | urn:va:u ser: R E D A CTED :100000002 72 | | |
| 124 | | executio nUserId | urn:va:u ser: R E D A CTED :100000002 71 | | |
| 125 | | ex ecutionUse rName | X IU, MARGAR ET | | |
| 126 | | fo rmAction | c larificati on | | |
| 127 | | fo rmComment | T est Questi on | | |
| 128 | Then a s uccessful response i s returned | |
| 129 | ||
| 130 | ||
| 131 | @Referred_ to_communi ty_care | |
| 132 | Scenario: | |
| 133 | Given a pa tient with pid " R E D A CTED ;100728" h as been sy nced throu gh the RDK API | |
| 134 | And the client has the curre nt deploym entid | |
| 135 | And the us er R E D A CTED ; DNS has create d and sign ed a consu lt for pat ient " R E D A CTED ;100728" | |
| 136 | And the us er " R E D A CTED ; PL " signals to activat e order | |
| 137 | | pa rameter | value | | |
| 138 | | userId | urn:va:u ser: R E D A CTED :100000002 72 | | |
| 139 | When the u ser " R E D A CTED ; PL " requests to update task to R eferred to Community Care (sta rt) | |
| 140 | | pa rameter | v alue | | |
| 141 | | icn | R E D A CTED ;100728 | | |
| 142 | | st ate | s tart | | |
| 143 | Then a s uccessful response i s returned | |
| 144 | When the u ser " R E D A CTED ; PL " requests to update task to R eferred to Community Care | |
| 145 | | pa rameter | v alue | | |
| 146 | | icn | R E D A CTED ;100728 | | |
| 147 | | st ate | c omplete | | |
| 148 | | or deringProv ider displ ayName | K HAN, VIHAA N | | |
| 149 | | ordering Provider u id | urn:va:u ser: R E D A CTED :100000002 72 | | |
| 150 | | executio nUserId | urn:va:u ser: R E D A CTED :100000002 71 | | |
| 151 | | ex ecutionUse rName | X IU, MARGAR ET | | |
| 152 | | fo rmAction | c ommunityCa re | | |
| 153 | | co mmunityCar eStatus | s cheduled | | |
| 154 | | co mmunityCar eType | S haring agr eement | | |
| 155 | Then a s uccessful response i s returned | |
| 156 | ||
| 157 | @assign_to _triage_me meber | |
| 158 | Scenario: | |
| 159 | Given a pa tient with pid " R E D A CTED ;100728" h as been sy nced throu gh the RDK API | |
| 160 | And the client has the curre nt deploym entid | |
| 161 | And the us er R E D A CTED ; DNS has create d and sign ed a consu lt for pat ient " R E D A CTED ;100728" | |
| 162 | ||
| 163 | When the u ser " R E D A CTED ; PL " requests to update task to A ssign to t riage memb er (start) | |
| 164 | | pa rameter | v alue | | |
| 165 | | icn | R E D A CTED ;100728 | | |
| 166 | | st ate | s tart | | |
| 167 | Then a s uccessful response i s returned | |
| 168 | When the u ser " R E D A CTED ; PL " requests to update task to A ssign to t riage memb er | |
| 169 | | pa rameter | value | | |
| 170 | | icn | R E D A CTED ;100728 | | |
| 171 | | st ate | complete | | |
| 172 | | ac ceptingPro vider disp layName | EHMP, UATT WO (Physic ian) | | |
| 173 | | acceptin gProvider uid | urn:va:u ser: R E D A CTED :100000002 36 | | |
| 174 | | executio nUserId | urn:va:u ser: R E D A CTED :100000002 71 | | |
| 175 | | ex ecutionUse rName | XIU, MARGA RET | | |
| 176 | | fo rmAction | assigned | | |
| 177 | | de stination facility c ode | 500 | | |
| 178 | | de stination facility n ame | PANORAMA | | |
| 179 | | or deringProv ider displ ayName | KHAN, VIHA AN | | |
| 180 | | ordering Provider u id | urn:va:u ser: R E D A CTED :100000002 72 | | |
| 181 | Then a s uccessful response i s returned | |
| 182 | ||
| 183 | @send_to_s cheduling | |
| 184 | Scenario: | |
| 185 | Given a pa tient with pid " R E D A CTED ;100728" h as been sy nced throu gh the RDK API | |
| 186 | And the client has the curre nt deploym entid | |
| 187 | And the us er R E D A CTED ; DNS has create d and sign ed a consu lt for pat ient " R E D A CTED ;100728" | |
| 188 | When the u ser " R E D A CTED ; PL " requests to update task to S end to Sch eduling (s tart) | |
| 189 | | pa rameter | v alue | | |
| 190 | | icn | R E D A CTED ;100728 | | |
| 191 | | st ate | s tart | | |
| 192 | Then a s uccessful response i s returned | |
| 193 | When the u ser " R E D A CTED ; PL " requests to update task to S end to Sch eduling | |
| 194 | | pa rameter | v alue | | |
| 195 | | icn | R E D A CTED ;100728 | | |
| 196 | | st ate | c omplete | | |
| 197 | | or deringProv ider displ ayName | K HAN, VIHAA N | | |
| 198 | | ordering Provider u id | urn:va:u ser: R E D A CTED :100000002 72 | | |
| 199 | | executio nUserId | urn:va:u ser: R E D A CTED :100000002 71 | | |
| 200 | | ex ecutionUse rName | X IU, MARGAR ET | | |
| 201 | | de stination facility c ode | 5 00 | | |
| 202 | | de stination facility n ame | P ANORAMA | | |
| 203 | | or deringProv ider displ ayName | K HAN, VIHAA N | | |
| 204 | | ordering Provider u id | urn:va:u ser: R E D A CTED :100000002 72 | | |
| 205 | | fo rmAction | t riaged | | |
| 206 | Then a s uccessful response i s returned |
Araxis Merge (but not the data content of this report) is Copyright © 1993-2016 Araxis Ltd (www.araxis.com). All rights reserved.