Create and manage categories in OVID. Removing a category will not remove content.
Loading...
The OpenVista Interface Domain (OVID) layer is a set of development tools designed to enable software developers easier access to OpenVista data. Currently, we've implemented a set of java domain classes that demonstrate how this can be accomplished.
OVID is basically an RPC resource messaging interface with java bindings. OVID can execute an RPC and get the results. It is up to the developer to construct the call and glean the results into a usable format. Further, OVID contains mumps routines and a specialized RPC that can invoke Fileman on behalf of the caller. RPC and Fileman "modes" can be easily intermixed.
Included in this release is a sample application. This Patient Dashboard application is meant to provide an example of using OVID as a data provider for a web-based application. In this case, the developers were able to quickly build this application by using OVID to build an API that accesses existing data and RPC calls. The OpenLaszlo-based Patient Dashboard is described in the Release Notes.
Quick Links
You might have viewed the online demo of the Contineo iPhone application accessing patient information from OpenVista. Contineo is a developer of mobile applications and created an iPhone application that leverages a clinical view across OpenVista patients. On the back end, the developers at Contineo created a RESTful server that utilizes OVID to access data from OpenVIsta. REST is a stateless web service architecture with an emphasis on simplicity which lends well to many types of applications.
Recently, Hugo Troche, Contineo CEO and co-Founder, announced that they were going to contribute their REST service layer as open source. With assistance from Medsphere with packaging and licensing, we are proud to announce that OpenVista REST source is now available for download from Launchpad as lp:ovrest. Any Vista on which OVID can be installed (e.g. WorldVista) could use OpenVista REST. We'll post more details on installing/building soon.
.
We've added some new service methods to the ccr-webservice project in Launchpad. In the CCRService:
/**
* get a list of patients whose id matches wholly or partially on the id parameter.
* @param id
* @return
* @throws OvidDomainException
*/
@WebMethod(operationName="LookupPatientsByID", action="LookupPatientsByID")
public Collection<FMPatient> lookupPatientsByID(String id) throws OvidDomainException {
...
}
/**
* get a list of patients whose name matches wholly or partially on name. The format
* is LAST,FIRST for the input parameter. So, JONES,CHRISTOPHER would find an exact match.
* However, if you just supply JONES, you should get all the JONES matches. Further, supplying
* JO should get JONES, JOHNSON, etc.
* @param name
* @return
* @throws OvidDomainException
*/
@WebMethod(operationName="LookupPatientsByName", action="LookupPatientsByName")
public Collection<FMPatient> lookupPatientsByName(String name) throws OvidDomainException {
...
}
These new service methods utilize the SC PATIENT LOOKUP rpc. As such, the login user needs to have the OR CPRS GUI CHART option assigned in order to work.
You can get the source for this from launchpad.net via:
bzr branch lp:ccr-webservice
... or, if you already have a local branch:
bzr merge
We've recently pushed a new incremental release of Ovid sources out to the launchpad site. Also, for those who don't want to use launchpad, we've uploaded a new source package to https://medsphere.org/download/project/ovid. This incremental release is tagged as ovid-dev-src-0.9.1.zip. If you are using the previous source tarball (ovid-src-0.9.0.tgz), you'll find the following improvements:
If you are pulling sources from launchpad (lp:ovid) via bazaar, then you are already taking advantage of most of these enhancements and this push represents a minor upgrade.
Recently Medsphere was introduced to Contineo, a silicon valley startup, whose goal is the integration of mobile devices within healthcare to provide ubiquitous portable access to critical information. In particular this company is focused on mobile (handheld) access to data, real-time alerting, secure messaging and location services. The platform is meant to aggregate data from multiple systems and present the clinicians with a honed workflow purposefully built for the device. An extremely compelling product from a healthcare delivery perspective.
You may be asking, why are we talking about such a product here in the OVID blog?
Simple: On their own, Contineo used the open source OVID platform to build an iPod Touch/iPhone application that pulls patient data directly from OpenVista. Their development team created the app, leveraging the OVID model to quickly create a new visualization of OpenVista patient data -- putting it literally into the hands of the clinicians that need it, right at the bedside.
Hugo Troche, CEO and co-Founder told us:
OVID is simple to understand and use. Yet, at the same time is powerful and highly extensible. We were able to quickly create a bridge to an OpenVistA implementation with OVID.
While Contineo's vision is to be back-end agnostic, OpenVista and OVID was a perfect starting point due to the tremendous efforts of MedSphere and the OpenVista community in providing access to a fully defined and robust system that allowed us to quickly develop our system in such a way that we did not need direct access to a production environment for the initial release. If you're an OpenVista user and would be interested in a demo, proof of concept or potential pilot, please contact us at info@contineo.us
Hugo was kind enough to record a quick demonstration (about 3 minutes) of the application in action -- enjoy:
I wanted to give an update on recent progress on our collaborative effort to bring OpenVista (and WorldVista and, eventually, RPMS) to play as a data source for the NHIN. I'm assuming that many are familiar with NHIN, CCR and OVID, but a good way to describe this collaboration would be: NHIN is the network of cooperating HIE implementations with a focus on the exchange of patient information. It is powered by the NHIN CONNECT open source project. (there are also commercial implementations). CCR is an xml data format that describes the health record of a patient. It is fast becoming a preferred format to exchange patient information. George Lily and the CCR/CCD team have done a tremendous job of creating Vista routines/RPCs that can, at this writing, generate a CCR for a Vista patient. Persisting a CCR into Vista is on the horizon.
So, we have an open source NHIN on one side that facilitates finding patients within the network of cooperating entities and transmitting patient healthcare information back and forth in a secure, standard method. On the other side is a set of mumps routines/RPCs that can create a CCR for a patient. In between, we discovered that OVID makes a good fit for hooking the two together. The NHIN CONNECT project is java-based so OVID fits well within its environment. The NHIN CONNECT project already has a testing structure that queries the NHIN for a particular patient and, once found, asks for a list of documents available for that patient. Then, the test sequence asks for one of those documents to be sent for a particular Document ID. We were pretty easily able to use OVID to:
I would be amiss not to give proper credit to Richard Braman who is really driving this particular effort. Richard built and configured the NHIN and WorldVista environments and is the person who knows how all of this is supposed to fit together. Without Richard, we would likely be struggling with the NHIN CONNECT environment.