Extending the Platform. 21 st VCM, George Mason University, Fairfax, Va. Andy Pardue & Ben Mehling

Transcription

1 Extending the Platform 21 st VCM, George Mason University, Fairfax, Va. Andy Pardue & Ben Mehling

2 OVID The OVID (OpenVista Interface Domain) layer is a set of development tools designed to enable software developers easier access to OpenVista data and applications. Vital stats: OVID is a foundational technology that allows developers to build upon OpenVista (and VistA derivatives) using alternative languages (such as Java) or architectures (such as Web Services/SOA). Originally released: April 2009 License: AGPL Technologies: M, Java Downloads: Open Repository & Home: Recent whitepaper: 2

3 OVID Technical Capabilities Useful for building on the OpenVista/VistA platform: Traditional applications Web/Mobile applications Exposing OpenVista data/logic as Web Services Console based applications Automation and Integration Ability to create M to Java calls, allowing M applications to call external Java APIs Ability to create Java to M calls, allowing Java applications to call into M APIs Supports creating Java domain objects 3

4 Web/Mobile Apps Web Services Repo Domain Object Repository (Patient, Order, Medication, etc.) OVID Message OVID Connection OVID Architectural Overview Java Apps (Thick and Console) How does OVID work? Communicates over generic transports, such as RPC Broker or CIAi Broker Implements an interface for calling existing RPCs Implements an interface to FileMan s silent database API RPC/CIAi Broker OVID M/RPCs M/RPCs FileMan 4 OpenVista

5 A Platform Using the OVID technology and framework, community contributors and Medsphere have created new tools and applications: Web Services to CCR/CCD gateway Web Services to DoD KMR middle tier IHS/Medsphere Clinical Flowsheet, Pharmacy and more in development iphone/ipod application to view patient record in real-time Registration application built on OVID RESTful interface to OpenVista 5

6 Sample web front-end

7 When to consider OVID VistA provides a strong integrated solution...but, Integration is a double-edged sword VistA has not easily adapted to the changing world s in computing, platforms and devices OVID can be used in projects with varying goals: Integration the glue between disparate systems Extension or a platform on which to build Migration a transitional path 7

8 Integration HL7 OpenVista XML Image Interface Files OVID Mirth Engine WebDAV Image Repo 8

9 Extension OpenVista OV VID Domain Layer Patient Dashboard Application 9

10 Extension OpenVista OV VID Domain Layer Patient Dashboard Application RESTful WebService 10

11 Migration Clinical Flowsheets OVID-based WebServices MySQL OpenVista 11

12 Migration Clinical Flowsheets Pharmacy OVID-based WebServices MySQL OpenVista FDB DIF 12

13 Migration Clinical Flowsheets Pharmacy OVID-based WebServices AWS MySQL Bigtable OpenVista FDB DIF 13

14 Domain Layer A layer of business objects focused on defining the properties and behavior of the concepts they represent. Object oriented, reusable across applications. Isolate, as much as possible, underlying complexity and details from the users of the objects. For our purposes, a domain layer should be a simple, repository based approach to accumulating useful domain objects. Extensible to other architectures and platforms (SOAP, REST, Web, etc.) Lowers the ramp up time for new developers to become productive. 14

15 OVID API RPCBroker, CIABroker, VistalinkBroker interfaces Connection pooling Temporal caching FileMan/Mumps RPC Access Support for annotated Java beans 15

16 OVID Domains Patient (Demographics) Patient Contacts (NOK, Guarantor) Location/Ward/Institution Information Kernel Info (e.g. Platform detection) Users/Clinicians (New Person) Laboratory Test Results Problems Vital Signs Drug information Medication Administration Log Orders/Orderable Items Order status/dialog Patient Movement Prescriptions/refills Immunizations/refusals TIU Document Retrieval 16

17 Middle-tier DDSS Research Project Data Services (C83) from RPMS and OpenVista Service Orienting the Rules Engine Web app container for VueCentric DDSS & KMR Project For details, see: 17

18 KMR Services -- What s available CAL layer defines what web services are implemented Utilizes HL7 V3 XML objects for data requests and responses All service providers (RPMS, OpenVista) implement this interface. (These implementations are called mappers because they map from native data elements to the HL7 v3 objects required by the CAL layer.) CAL layer is implemented as a SOAP Java web services (jax-ws) Runs within the Glassfish application server Coding systems are used when available in source data: LOINC, ICD, CPT, NDC, HL7 Currently implements the following CAL domains: FindPatients GetPatientInfo FindProviders GetProblems GetLabResults GetMedications GetAllergies GetImmunizations GetVitalSigns 18

19 Demonstration CCD Document Creation Used anonymized data from a large sample RPMS dataset Aggregation of ~5 domains into a CCD XML file Built on OVID, automated the CCD creation from RPMS in a few hours of developer time Populating pophealth 1 Repository One CCD XML file 2 was created for each patient The import process reads a directory of CCD records in batch, loading each patient into the repository Population Health Reporting Influenza Vaccination Hypertensive BP Under Control Ad hoc reporting Incomplete CCD record due to pophealth limitation -- clinical coding incomplete/hardcoded 19

20 FM Projection FM (File Manager) Projection is a technology that projects the data structure of OpenVista into a relational database format. Users can query against FM data structures using SQL queries and tools. Vital stats: Planned release: January 2010 VCM! License: AGPL, LGPL Technologies: M, Java, C Downloads: Open Repository Home: 20

21 Architecture: FM Projection M-engine agnostic (GT.M or Cache) Implements a MySQL storage engine that is backed via a network connection to an OpenVista server Projection model uses SQLi package Capabilities: Data can then be accessed via J/ODBC data tools and compatible data access development libraries A Java-based schema and data viewer is included Current version provides read-only access Uses: Connect open source or COTS data analysis, reporting, BI tools 21

22 FileMan Projection Architecture MySQL Clients SQL Parser/Optimizer MyISAM Storage Engine InnoDB Storage Engine FileMan Storage Engine FileMan Visualizer RPC Broker SQL RPCs FileMan SQLi 22

23 To do Indexes on "New Style" FileMan indexes Provide better optimizer hints Foreign keys Prefetch results instead of RPC call per row Custom network socket connection for performance Eventually, write abilities 23

24 Demonstration 24

25 FM Visualizer (FMVis) Inspect Files Fields Data Globals Relationships Graph 25

26 Standard SQL via DBVisualizer Schema inspection Queries: Titles Users with their titles Average Age & Standard Deviation of Patients Most recent signed notes Project Files to MySQL from FMVis STATE 26

27 Jasper - ireport Sample Reports Users by Title Signed notes (previous two weeks) Patients w/ Allergies Projection, not Replication Run Report Data alteration Re-run Report 27

28 Semantic Web EMR, Wed 3:15pm Medsphere Overview, Fri 9:00am Questions 28

29