Produced by Araxis Merge on 11/8/2016 5:25:14 PM Eastern Standard Time. See www.araxis.com for information about Merge. This report uses XHTML and CSS2, and is best viewed with a modern standards-compliant browser. For optimum results when printing this report, use landscape orientation and enable printing of background images and colours in your browser.
| # | Location | File | Last Modified |
|---|---|---|---|
| 1 | rxrefill-v2.0.0 P2.zip | Rx+Refill+(RXR)+SDD+Addendum.docx | Fri Nov 4 21:49:50 2016 UTC |
| 2 | rxrefill-v2.0.0 P2.zip | Rx+Refill+(RXR)+SDD+Addendum.docx | Mon Nov 7 00:06:05 2016 UTC |
| Description | Between Files 1 and 2 |
|
|---|---|---|
| Text Blocks | Lines | |
| Unchanged | 8 | 814 |
| Changed | 7 | 22 |
| Inserted | 0 | 0 |
| Removed | 1 | 2 |
| 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 | Rx Refill (RXR) SDD Addendum | ||
| 2 | Mobile App lication S ystem Desi gn Documen t (SDD) Ad dendum | ||
| 3 | |||
| 4 | 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 . Per the Project Ma nagement A ccountabil ity System (PMAS) Gu ide, the S DD with co nceptual d esign is r equired pr ior to the Milestone 1 Review. The as-bu ilt for ea ch deliver y must be incorporat ed prior t o the Mile stone 2 Re view. | ||
| 5 | Mobile App lication I nformation | ||
| 6 | Project In crement / Release De signation: RxRefill v2 | ||
| 7 | Product Ve rsion: 2. 0.0 | ||
| 8 | |||
| 9 | Veteran | ||
| 10 | Care Giver | ||
| 11 | Provider | ||
| 12 | Public | ||
| 13 | Intended A udience fo r Mobile A pplication | ||
| 14 | X | ||
| 15 | |||
| 16 | |||
| 17 | |||
| 18 | Question | ||
| 19 | Yes | ||
| 20 | No | ||
| 21 | If yes, wh at informa tion / dat a | ||
| 22 | If yes, th en identif y any cons umer or so urce syste m(s) for t he data | ||
| 23 | Does the u ser enter informatio n or data into the m obile appl ication? | ||
| 24 | X | ||
| 25 | |||
| 26 | Authentica tion Infor mation | ||
| 27 | Auth Servi ces via DS Login. | ||
| 28 | Does Mobil e Applicat ion store informatio n or data entered by the User? If yes, w here is it stored? | ||
| 29 | X | ||
| 30 | |||
| 31 | Prescripti on Refill informatio n | ||
| 32 | The applic ation stor es success ful medica tion refil l requests in the VA MF so that it can be used for metric on number of sucessful RxRefill r equests su bmitted us ing the VA MF Rx Refi ll Applica tion. | ||
| 33 | Does Mobil e Applicat ion transm it/push da ta entered outside o f the VAMF to VA? | ||
| 34 | X | ||
| 35 | |||
| 36 | Medication Refill re quest | ||
| 37 | Enterprise Rx Refill and Track ing Servic e. | ||
| 38 | Does Mobil e Applicat ion pull d ata from a VA Databa se (extern al to VAMF )? | ||
| 39 | X | ||
| 40 | |||
| 41 | Medication s, refill tracking i nformation ,medicatio n images a nd metadat a | ||
| 42 | Enterprise Rx Refill and Track ing Servic e, CDW. | ||
| 43 | Does the M obile Appl ication st ore in the VAMF or o n the devi ce data pu lled from a VA Datab ase? | ||
| 44 | X | ||
| 45 | |||
| 46 | oAuth Toke n id | ||
| 47 | Secure Ses sion Stora ge within browser (t oken). | ||
| 48 | |||
| 49 | This appli cation can be classi fied as on e of the f ollowing: | ||
| 50 | Mobile App lication C lassificat ion (Only one box ma y be check ed) | ||
| 51 | Mark with X | ||
| 52 | 1 – Very Low: Mobil e Applicat ion does n ot use VA Resource | ||
| 53 | |||
| 54 | 2 – Low: read only access to VA Resourc e(s) (No P II / PHI) | ||
| 55 | |||
| 56 | 3 – Mediu m: write a ccess to V A Resource (s) | ||
| 57 | |||
| 58 | 4 – High: read and/ or Write a ccess of s ensitive d ata to VA Resource(s ) (Include s PII/PHI/ other sens itive) | ||
| 59 | X | ||
| 60 | |||
| 61 | Applicatio n Design | ||
| 62 | |||
| 63 | Deployment Diagram | ||
| 64 | |||
| 65 | Applicatio n Architec ture | ||
| 66 | |||
| 67 | |||
| 68 | Interfaces | ||
| 69 | |||
| 70 | |||
| 71 | |||
| 72 | |||
| 73 | Device's O S | ||
| 74 | Native | ||
| 75 | Hybrid | ||
| 76 | Web-Only | ||
| 77 | OS version supported | ||
| 78 | Targeted d evices (iP hone, iPad , Samsung model...) | ||
| 79 | Estimated Storage Re quired for Device | ||
| 80 | iOS | ||
| 81 | |||
| 82 | |||
| 83 | X | ||
| 84 | 7+ | ||
| 85 | |||
| 86 | |||
| 87 | Android | ||
| 88 | |||
| 89 | |||
| 90 | X | ||
| 91 | 4+ | ||
| 92 | |||
| 93 | |||
| 94 | Windows | ||
| 95 | |||
| 96 | |||
| 97 | X | ||
| 98 | IE11 (Wind ows 7+) | ||
| 99 | |||
| 100 | |||
| 101 | |||
| 102 | Technologi es, Librar ies, and T ools Used in the App | ||
| 103 | Version | ||
| 104 | On the TRM ? (If not, provide a link to t he waiver) | ||
| 105 | HTML5 | ||
| 106 | 5 | ||
| 107 | Yes | ||
| 108 | Backbone | ||
| 109 | 1.2.3 | ||
| 110 | Yes | ||
| 111 | Bootstrap | ||
| 112 | 3.3 | ||
| 113 | Yes | ||
| 114 | Handlebars | ||
| 115 | 4.0.0 | ||
| 116 | Yes | ||
| 117 | Underscore | ||
| 118 | 1.8.3 | ||
| 119 | Yes | ||
| 120 | jQuery | ||
| 121 | 2.2 | ||
| 122 | Yes | ||
| 123 | Bower | ||
| 124 | 1.7.9 | ||
| 125 | Yes | ||
| 126 | Jasmine | ||
| 127 | 2.4 | ||
| 128 | Yes | ||
| 129 | Jasmine-si non | ||
| 130 | 0.4.0 | ||
| 131 | Yes (reque st number: 20532) | ||
| 132 | Jasmine-jq uery | ||
| 133 | 2.1.0 | ||
| 134 | Yes (reque st number: 20531) | ||
| 135 | Marionette | ||
| 136 | 2.4.4 | ||
| 137 | Yes | ||
| 138 | Grunt | ||
| 139 | 0.4.5 | ||
| 140 | Yes | ||
| 141 | SASS | ||
| 142 | 3.4.12 | ||
| 143 | Yes | ||
| 144 | Compass | ||
| 145 | 1.0.3 | ||
| 146 | Yes | ||
| 147 | Java JDK | ||
| 148 | 1.7.x | ||
| 149 | Yes | ||
| 150 | WebLogic | ||
| 151 | 12c (12.1. 3) | ||
| 152 | Yes | ||
| 153 | Spring Fra mework | ||
| 154 | 4.1.x | ||
| 155 | Yes | ||
| 156 | Spring Sec urity | ||
| 157 | 3.2.5 | ||
| 158 | Yes | ||
| 159 | jTDS JDBC Driver | ||
| 160 | 1.3.1 | ||
| 161 | Waiver is being requ ested for all VAMF b y Lynne Ca se | ||
| 162 | Hibernate | ||
| 163 | 4.3.8.Fina l | ||
| 164 | Yes | ||
| 165 | Spring Dat a MongoDb | ||
| 166 | 1.7.2.RELE ASE | ||
| 167 | Yes | ||
| 168 | Data Archi tecture | ||
| 169 | Add a tabl e like the below for listing N oSQL data collection s stored. A complete Data Dict ionary can be found here: | ||
| 170 | |||
| 171 | Ref # | ||
| 172 | NoSQL Coll ection | ||
| 173 | Descriptio n of data collection | ||
| 174 | Source of data | ||
| 175 | Structure | ||
| 176 | 1 | ||
| 177 | RxRefill.m edicationr efillreque sts | ||
| 178 | This colle ction hold s data rel ating to s uccessfull y refilled prescript ions carri ed out thr ough the V AMF and ca n be used to provide metrics f or submiss ions throu gh the VAM F. | ||
| 179 | MVI, gener ated | ||
| 180 | _id: Strin gpatientId : Stringme dicationId : Stringre questDate: Datetime (ISO-8601) appSource : Stringdo cCreatedDa te: Dateti me (ISO-86 01) docMod ifiedDate: Datetime (ISO-8601) | ||
| 181 | 3 | ||
| 182 | N/A | ||
| 183 | This colle ction prov ides defin itions to standardiz e VA Mobil e Framewor k (VAMF) c ommon elem ents (see definition s section of the JSO N schema a ttached), such as: h elp page c ontent, ab out page c ontent, ap plication name, appl ication ab breviation , applicat ion versio n, and the last date content. The collec tion for t his releas e is store d in a fil e embedded within th e app. The structure of the co ntent will be valida ted agains t the json -schema in the struc ture colum n. | ||
| 184 | vamf-commo ns.json | ||
| 185 | {"$schema" : "
|
||
| 186 | |||
| 187 | Add tables like this for Relat ional tabl es: (NA) | ||
| 188 | Column Nam e | ||
| 189 | Data Type | ||
| 190 | Nullable | ||
| 191 | Descriptio n | ||
| 192 | PK | ||
| 193 | FK | ||
| 194 | |||
| 195 | |||
| 196 | |||
| 197 | |||
| 198 | |||
| 199 | |||
| 200 | Provide so me volume / sizing i nformation for each collection /table:(NA ) | ||
| 201 | Table or C ollection | ||
| 202 | Number of Rows / Ent ries | ||
| 203 | Estimated Size per E ntry | ||
| 204 | Total Disk (minus ov erhead for indexes, etc) | ||
| 205 | |||
| 206 | |||
| 207 | |||
| 208 | |||
| 209 | Laws / reg ulations t hat direct the imple mentation of the app ? | ||
| 210 | N/A | ||
| 211 | Expected c oncurrent and maximu m size of the user b ase? | ||
| 212 | User Categ ory | ||
| 213 | Total Numb er of User s | ||
| 214 | Concurrent Users | ||
| 215 | Veterans | ||
| 216 | limited ro llout ~ 20 0 | ||
| 217 | 10 | ||
| 218 | Interface Design | ||
| 219 | Existing V AMF Interf aces Used | ||
| 220 | Interface Name | ||
| 221 | Version | ||
| 222 | Endpoint | ||
| 223 | Data Used by Mobile App | ||
| 224 | Source of Data | ||
| 225 | Data Retri eved - pro vide speci fic data e lements us ed by this app | ||
| 226 | Authorizat ion Servic es | ||
| 227 | 4.4.0 | ||
| 228 | /ssoeproxy /veteran/a uthorize | ||
| 229 | Authentica tion Respo nse used b y Login Me chanism | ||
| 230 | DSLogon | ||
| 231 | First name , last nam e, EDIPI | ||
| 232 | Authorizat ion Servic es | ||
| 233 | 4.4.0 | ||
| 234 | /rest/last ResourceAc cessedTime | ||
| 235 | lastaccese dTime, log inTime, ti meToExpire InSeconds | ||
| 236 | VAMF Autho rization D B | ||
| 237 | User resou rce access data | ||
| 238 | Health Ada pter | ||
| 239 | 3.4.0 | ||
| 240 | /rest/publ ic/user-se ssion | ||
| 241 | MHP User | ||
| 242 | VAMF Token Store | ||
| 243 | First Name , Last Nam e, DOB, us erIdentifi er | ||
| 244 | Health Ada pter | ||
| 245 | 3.4.0 | ||
| 246 | rest/mhpus er/right-o f-access | ||
| 247 | Right of A ccess obje ct | ||
| 248 | VAMF HA DB | ||
| 249 | ROA object (userId,o bject-type ,rightOfAc cessAccept ed,rightOf AccessDate ) | ||
| 250 | Health Ada pter | ||
| 251 | 3.4.0 | ||
| 252 | /roa/index .html?url= {redirectU RI} | ||
| 253 | Right of A ccess Acce ptance web page | ||
| 254 | VAMF HA DB | ||
| 255 | None, used as a page to accept Right of Access and populate ROA in HA DB | ||
| 256 | Authorizat ion Servic es | ||
| 257 | 4.4.0 | ||
| 258 | /ssoeproxy /logout | ||
| 259 | Cleans up session an d logs use r out in d evelopment | ||
| 260 | VAMF Autho rization D B | ||
| 261 | Used for l ogout and cleanup of token sto re | ||
| 262 | authservic es-oauth-l ib | ||
| 263 | 1.0.3 | ||
| 264 | /oauth/tok en{?code=} and /oauth /infoAs do cumented a t
|
||
| 265 | As documen ted at D
|
||
| 266 | Applicatio n properti es file fo r oauth in fo and VAM F Authoriz ation DB f or token | ||
| 267 | Used for o btaining t he oauth t oken and i nformation for obtai ning the t oken such as client_ id and red irect_url | ||
| 268 | New/Update d VAMF Int erfaces Ad ded | ||
| 269 | Interface Name (incl . version #) | ||
| 270 | Version | ||
| 271 | Endpoint | ||
| 272 | HTTP Metho d | ||
| 273 | Data Used by Mobile App | ||
| 274 | Source of Data | ||
| 275 | Included i n Program- Level SDD? | ||
| 276 | RxRefill S ervice | ||
| 277 | 2.0 | ||
| 278 | /RxRefillS ervices/v2 /patient/p rescriptio n/active | ||
| 279 | GET | ||
| 280 | (See A.1 – Prescript ionsTO) | ||
| 281 | (See A.2 – Prescript ionTO) | ||
| 282 | (See A.6. – Fault) | ||
| 283 | Enterprise Rx Refill and Track ing Servic e | ||
| 284 | No | ||
| 285 | RxRefill S ervice | ||
| 286 | 2.0 | ||
| 287 | /RxRefillS ervices/v2 /patient/{ assigning- authority} /{patient- id}/prescr iption/{rx Id}?appSou rce={appso urce} | ||
| 288 | POST | ||
| 289 | (See A.6. – Fault) | ||
| 290 | Enterprise Rx Refill and Track ing Servic e | ||
| 291 | No | ||
| 292 | RxRefill S ervice | ||
| 293 | 2.0 | ||
| 294 | /RxRefillS ervices/v2 /patient/p rescriptio n/historic | ||
| 295 | GET | ||
| 296 | (See A.1 – Prescript ionsTO) | ||
| 297 | (See A.2 – Prescript ionTO) | ||
| 298 | (See A.6. – Fault) | ||
| 299 | Enterprise Rx Refill and Track ing Servic e | ||
| 300 | No | ||
| 301 | RxRefill S ervice | ||
| 302 | 2.0 | ||
| 303 | /RxRefillS ervices/v2 /patient/p rescriptio n/tracking | ||
| 304 | GET | ||
| 305 | (See A.1 – Prescript ionsTO) | ||
| 306 | (See A.2 – Prescript ionTO) | ||
| 307 | (See A.6. – Fault) | ||
| 308 | Enterprise Rx Refill and Track ing Servic e | ||
| 309 | No | ||
| 310 | RxRefill S ervice | ||
| 311 | 2.0 | ||
| 312 | /RxRefillS ervices/v2 /patient/p rescriptio n/tracking /{rxId} | ||
| 313 | GET | ||
| 314 | (See A.3. – Tracking InfoDetail sTO) | ||
| 315 | (See A.4. – Tracking InfoTO) | ||
| 316 | (See A.5. – Prescrip tionLiteTO ) | ||
| 317 | (See A.6. – Fault) | ||
| 318 | Enterprise Rx Refill and Track ing Servic e | ||
| 319 | No | ||
| 320 | RxRefill S ervice | ||
| 321 | 2.0 | ||
| 322 | /RxRefillS ervices/v2 /patient/p rescriptio n/refillRe quests | ||
| 323 | GET | ||
| 324 | (See A.7. – Medicati onRefillRe quest) | ||
| 325 | (See A.8. – Medicati onRefills) | ||
| 326 | (See A.6. – Fault) | ||
| 327 | VAMF Mongo rxrefill. medication refillrequ ests | ||
| 328 | No | ||
| 329 | RxRefill S ervice | ||
| 330 | 2.0 | ||
| 331 | /RxRefillS ervices/v2 /patient/{ assigning- authority} /{patient- id}/sessio n | ||
| 332 | GET | ||
| 333 | (See A.9 – Enterpri seSessionM gmtTO) | ||
| 334 | Enterprise Rx Refill and Track ing Servic e | ||
| 335 | No | ||
| 336 | Medication Image Lib rary Servi ce | ||
| 337 | 1.0 | ||
| 338 | /mil-resou rces/v1/{n dc} | ||
| 339 | GET | ||
| 340 | (See A.1 – AcceptedI mageMetada ta) | ||
| 341 | (See A.4 – Fault) | ||
| 342 | VAMF CDW M IL Schema (BISL_Drug Info) | ||
| 343 | No | ||
| 344 | Medication Image Lib rary Servi ce | ||
| 345 | 1.0 | ||
| 346 | /mil-resou rces/v1/im age/{image Id} | ||
| 347 | GET | ||
| 348 | JPEG | ||
| 349 | (See A.4 – Fault) | ||
| 350 | VAMF CDW M IL Schema (BISL_Drug Info) | ||
| 351 | No | ||
| 352 | Medication Image Lib rary Servi ce | ||
| 353 | 1.0 | ||
| 354 | /mil-resou rces/v1/im ages/{ndc} | ||
| 355 | GET | ||
| 356 | (See A.2 – AcceptedI mages) | ||
| 357 | (See A.4 – Fault) | ||
| 358 | VAMF CDW M IL Schema (BISL_Drug Info) | ||
| 359 | No | ||
| 360 | Medication Image Lib rary Servi ce | ||
| 361 | 1.0 | ||
| 362 | /mil-resou rces/v1/im age/{image Id}/proper ties | ||
| 363 | GET | ||
| 364 | (See A.3 – AcceptedI mage) | ||
| 365 | (See A.4 – Fault) | ||
| 366 | VAMF CDW M IL Schema (BISL_Drug Info) | ||
| 367 | No | ||
| 368 | |||
| 369 | The follow ing ICDs a re provide d to provi de technic al detail relating t o the RxRe fill Servi ce and Med ication Im age Librar y Service: | ||
| 370 | Dependenci es/SLA | ||
| 371 | Project De pendency | ||
| 372 | Point of C ontact Inf ormation | ||
| 373 | Describe D ependency | ||
| 374 | |||
| 375 | |||
| 376 | |||
| 377 | |||
| 378 | |||
| 379 | |||
| 380 | |||
| 381 | Traceabili ty | ||
| 382 | Please see JIRA proj ect for da ta below: | ||
| 383 | https:// DNS /browse/RX R -503 | ||
| 384 | |||
| 385 | EPIC | ||
| 386 | FEATURE | ||
| 387 | USER STORY | ||
| 388 | DESIGN COM PONENT | ||
| 389 | |||
| 390 | |||
| 391 | |||
| 392 | |||
| 393 | |||
| 394 | Developer & PM Conta ct Informa tion | ||
| 395 | Developer Name/Point of Contac t (POC) | ||
| 396 | VA E-Mail Address | ||
| 397 | Phone Numb er | ||
| 398 | Pratap Chi lukuri | ||
| 399 | PII | ||
| 400 | PII | ||
| 401 | Developer Organizati on/Company | ||
| 402 | Contract S tart Date | ||
| 403 | Contract E nd Date | ||
| 404 | HP Enterpr ise Servic es | ||
| 405 | September 24, 2014 | ||
| 406 | July 10, 2 017 | ||
| 407 | Web and Mo bile Solut ions PM or POC | ||
| 408 | VA E-Mail Address | ||
| 409 | Phone Numb er | ||
| 410 | Connie Mur phy | ||
| 411 | PII | ||
| 412 | PII | ||
| 413 | VA Product Developme nt PM or P OC | ||
| 414 | VA E-Mail Address | ||
| 415 | Phone Numb er | ||
| 416 | Mark Ennis | ||
| 417 | PII | ||
| 418 | PII |
Araxis Merge (but not the data content of this report) is Copyright © 1993-2016 Araxis Ltd (www.araxis.com). All rights reserved.