Skip navigation

OVID

Overview All Content (79) Discussions (55) Documents (15) Blog Screenshots Download Set as default tab

Manage categories

Close

Create and manage categories in OVID. Removing a category will not remove content.

Categories in OVID
Add a new category (0 remaining)

Recent Discussions

Refresh this widget
More

Recent Documents

Refresh this widget
More

Recent Commits

Loading widget...

Latest Bugs

Loading widget...

OVID

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.

  • If you've ever wanted to call an OpenVista RPC from java, then this tool would be of interest to you.
  • If you've ever wanted to construct a fileman call in java because you can't find a suitable, existing RPC, then OVID would be of interest to you.

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

Recent Blog Posts

Refresh this widget
Andy Pardue
0

Announcing OpenVista REST in OVID

Posted by Andy Pardue Nov 25, 2009

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.

 

 

.

456 Views 0 Comments Permalink Tags: openvista, ovid, contineo, iphone, launchpad, rest, web_services
Andy Pardue
0

We've added some new service methods to the ccr-webservice project in Launchpad.  In the CCRService:

 

  • LookupPatientsByID returns a list of FMPatient objects who have an ID that matches wholly or partially to the input parameter.
    /**
     * 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 {
        ...
    }

 

  • LookupPatientsByName returns a list of patients whose name matches wholly or partially.
    /**
     * 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

350 Views 0 Comments Permalink
Andy Pardue
0

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:

 

  • Support for RPCBroker
  • Support for CIABroker
  • The needed KIDS packages required by Ovid are now part of the project.  So, you don't have to go and find them elsewhere.
  • Better orgaization of sources.  Previously, Ovid consisted of several sub projects represented by jar names like msc-common.jar, vista-rpc.jar, rpcresadapter.jar, etc.  Now, we've incorporated all of that into a couple of projects: ovid and ovid-domain.  The project named ovid contains all the core things that Ovid needs to communicate with OpenVista and ovid-domain is a reference domain implementation.
  • Better build scripts.  Unit tests, javadocs are now working targets.
  • Support for netbeans and eclipse is improved.

 

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.

312 Views 0 Comments Permalink Tags: ovid, launchpad
Ben Mehling
0

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:

 

Watch the video directly @ http://medsphere.blip.tv.

1,460 Views 0 Comments Permalink Tags: ovid, iphone, ipod_touch, contineo
Andy Pardue
0

NHIN, CCR and OVID in OVID

Posted by Andy Pardue Sep 30, 2009

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:

 

  • Handle the MPI request and locate the patient in our WorldVista test database.  We had to physically change the name of a patient to Younger Gallow (the test patient) to make this work, however, because that was easier at the time than changing the test.
  • Handle the request for the list of documents.  This involved generating a CCR using the mumps RPC and cataloging it as document number 1.  Then, we generate a CCD (a formatted variation of the CCR) from the CCR and catalog it as document  number 2.  Both documents are then cached for 30 minutes in an expiring caching mechanism (e.g. data with a shelf life) which was already available to us within OVID.  The NHIN CONNECT project already has the needed code to create the document request reply from our document list.
  • Handle the request for a document.  By default, the NHIN CONNECT test asks for a particular document.  When this request gets to OVID, we are able to locate the document in our expiring cache and return it to the NHIN CONNECT modules which format it into the reply.  So, we don't even need to hit the Vista datastore again.  Note: This is how NHIN is supposed to work, as I understand it.  You tell the requestor which documents are available and they have X amount of time to ask for one of them, otherwise, the document is obsolete.

 

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.

442 Views 0 Comments Permalink
More