1 / 35

VistA Imaging Services Architecture (VISA)

VistA Imaging Services Architecture (VISA). Class 764 Julian Werfel. VistA Imaging. System evolved since late 1980s Collection of client and server applications Image and Text Gateway Routing Purge and Background Processor Verifier VistARad Clinical Display, Capture and TeleReader

matana
Download Presentation

VistA Imaging Services Architecture (VISA)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. VistA Imaging Services Architecture (VISA) Class 764 Julian Werfel

  2. VistA Imaging • System evolved since late 1980s • Collection of client and server applications • Image and Text Gateway • Routing • Purge and Background Processor • Verifier • VistARad • Clinical Display, Capture and TeleReader • Management Utilities (MAG Enterprise, ET Phone Home)

  3. As Is Architecture • Several clients all doing similar tasks • Business logic in server and client • Functionality not encapsulated • Difficult to reuse existing functionality • Each application creates own access to data (many RPC calls) • Proprietary Storage • Very functional system providing access to over 1.4 billion images

  4. As Is Architecture • Clients require intimate knowledge of internal systems • Difficult to add new functionality (particularly to multiple clients) • Functionality duplicated • Several clients do the same job (display images, generate abstracts, store images) • Business logic sometimes in client, sometimes in server

  5. As Is Architecture • Business functionality not consistently applied • Clients do same tasks differently • Functional redundancy in Remote Procedure Calls (similar but inconsistent) • Difficult to share data with other groups/enterprises

  6. As Is Architecture Logical View

  7. As Is Remote Image Views • Client handles all communication with remote sites

  8. Transitional Architecture • Business logic moves from client and databases to middle tier • Service oriented facades to express Imaging to the enterprise using industry standards • Use latest languages and technologies (Java, Web Services) • Transition occurs over several years as part of several patches

  9. Transitioning with VISA • VistA Imaging Service Architecture • SOA for VistA Imaging • Provides framework for VistA Imaging components and functionality as services • Improves maintainability and reusability • Sharing of similar functionality • Componentization provides extensibility

  10. Transitioning with VISA • Faster addition of new features and sources of data • Separate clients from actual sources of data • Sources can change without client changes • Clients do less work • First implementation is Imaging Patch 83 VIX (VistA Imaging Exchange) service for sharing images with DoD

  11. Transitional Architecture Logical View

  12. VISA Layers

  13. VISA Components

  14. VISA Processing Sequence • Facade – entry point to clients. Translates client requests into core business semantics • Command Factory – used by Facades to create a command • Command – Executes business functionality • Artifact Source Resolution Service – Resolves the location of the data for the command into URLs • Data Source Factory – Creates a Data Source from the URL for the command • Data Source – provides data access for the command. Converts source information into core business semantics

  15. VISA Provides • Separation of client and source • Clients can communicate with multiple sources without understanding semantics of that source • New Data Sources can be added without changing business logic • Facades, Data Sources and Commands are installable • A VISA implementation may only include certain components • Multiple products come from same core but include different pieces

  16. VISA Provides • Developed as J2SE objects, does not require J2EE infrastructure • Lower overhead requirements • Abstraction of functionality to increase reusability • Similar functionality is used in several places consistently

  17. VISA Flexibility • Allows faster interfacing with multiple sources of data • Provide data to new interfaces and clients quickly • VA/DoD Artifact sharing with XCA (Cross Community Access) • Will be able to support NHIN (National Health Information Network) and VLER (Virtual Lifetime Electronic Record)

  18. Implementations of VISA • VIX Service – Imaging Patch 83 • Share images with DoD, Enhanced Remote Image Views for VA • New DICOM Gateway – Imaging Patch 34 • Store all DICOM objects • New data structure for storing images • Increase efficiency • Groundwork for subsequent enhancements

  19. Implementations of VISA • New Image Storage Management System – Patch 112 • Centralized VIX (CVIX) – Imaging Patch 104/105 • Provide VA images to VistaWeb users • VA/DoD artifact sharing • NCAT (Neurocognitive Assessment Test) reports for VA users

  20. Consumers of VISA Services • Clinical Display Enhanced Remote Image Views with VIX – Imaging Patch 93 • VistARad Viewing DoD and Remote VA images – Imaging Patch 90 • DoD Artifact Viewing in Clinical Display – Future Imaging Patch • Advanced Web Image Viewer (AWIV) – Imaging Patch 105

  21. Enhanced RIV Benefits • Take advantage of VIX Caching and Compression • Image is compressed at source before transfer over WAN • Compressed image higher quality • Image cached at local and remote VIX • VIX handles remote connection rather than client • Fewer connections over WAN • Enhanced RIV seamless to user

  22. Enhanced Remote Image Views • Images cached and compressed to improve performance

  23. VIX Implementation of VISA

  24. Federation Component View • VISA shares components

  25. Reducing Client Connections • Client makes request to VIX, improves security and performance

  26. VISA VA/DoD Image Sharing • NDAA El Paso project • VIX implements VISA • VistARad and Clinical Display consume VISA services

  27. Future VISA VA/DoD Image Sharing • Client access through site VIX • Site VIX communicates with CVIX

  28. CVIX Implementation of VISA

  29. VISA Implementations and Consumers

  30. To Be Architecture • Image access and other services encapsulated by VISA • Clients consume VISA services • Enhanced M database structure • Storing both DICOM and non-DICOM objects • Clients focus on display of data rather than business logic processing

  31. To Be Architecture Logical View

  32. VISA • 21st Century Design • Easier to add new functionality • Encapsulation • Shared functionality • Clients focus on client behavior rather than business logic • Reusability and consistency

  33. Questions? Julian Werfel Julian.werfel@va.gov (240) 638-2634

  34. VISA Design Team • Julian Werfel (julian.werfel@va.gov) • Keith Buck (donald.buck@va.gov) • Chris Beckey (christopher.beckey@va.gov) • Csaba Titton (csaba.titton@va.gov) • Roger Coney (roger.coney@va.gov) • Dezso Csipo (dezso.csipo@va.gov)

  35. Future Image Sharing

More Related