OVID

As a part of this month's community call (Community Call: Achieving Go Live Success ), George Lilly, Andy Pardue and Richard Braman provide an update on status of the CCR project, including next steps and details of the work done connecting to the NHIN.  

We have recently restructured our ovid source code to make it more conducive for use with Launchpad.  Previously, Ovid consisted of a handful of separate, modular projects.  Now, we've combined things quite a bit and have one Ovid project and one ... [More] reference domain implementation.  You can learn more about Launchpad from the online documentation available on site, but as a rough tutorial, you get up to speed by: Registering to become a launchpad user.  Its free.Installing the bazaar version control client.  Also free at http://bazaar-vcs.org.Grabbing the source by issuing the following command:bzr branch lp:ovid ovid-devThis will create a directory named ovid-dev with an ovid and ovid-domain project beneath.  View the README file for more info about each.Please continue to post questions about Ovid here on medsphere.org.  However, you can use the Launchpad bug tracker also if you find a bug or want to request an enhancement.  We also welcome any patches you want to submit with an eye toward integrating them into the mainline when at all possible. [Less]

Today, we've created a new open source project in launchpad for a CCR (Continuity of Care Record) web service utilizing OVID as the domain layer.  This project leverages the CCR mumps routines and RPCs fostered by George Lilly and the CCR/CCD team ... [More] , exposing them as java web services.  As exposed web services, a CCR can be accessed by any language/platform that can consume WSDL.  Hopefully, this will enable the CCR work by George et al to enjoy a farther reach. You can get the source from launchpad via: bzr branch lp:ccr-webservice If you are unfamiliar with bzr (bazaar) and launchpad, I'd suggest that you peruse the documentation available on the launchpad site.  It is a good resource of information. A CCR is a structured XML document that represents the clinical record of a patient.  The ccr/ccd group has done a great deal of work putting together the mumps routines that generate (and eventually consume) these CCD/CCR streams.  You can find more info at http://groups.google.com/group/ccd-ccr-project. Since we've been collaborating with George Lilly and Richard Braman on this project, we've preconfigured it to utilize a WorldVista instance they've establish that is running on an Amazon cloud that has OVID and the CCR RPCs installed.  You can get the source and utilize that same resource, or change the settings to use another instance.   We've tested against an OpenVista as well as a WorldVista implementation. There is a simple web application to demonstrate use.  Simply point your browser to http://ec2-75-101-247-83.compute-1.amazonaws.com:8080/ccr/.  The password is already supplied, so just press login and choose a patient to see the CCR.  Note that this is only a demo application.  Gratuitous screenshots below...   There are also a couple of C# clients that demonstrate use of the web service layer.  They are both almost identical, except in how they access the web service reference; one uses mono and the other uses .Net (Microsoft Visual Studio).  You'll find these projects in ccr-webservice/src/csharp.  Both the web application (JSP) and web service clients follow the same OVID-to-CCR RPC path to fetch the CCR stream. The webservice layer itself can be built and deployed in either tomcat or glassfish.  Other containers (jboss, jetty, etc.) might easily work also, but those are the only two we've focused on so far. The launchpad project contains README and INSTALL files that will direct you in building and deploying.  Feel free to take a look and join in.  If you find a problem, please post it as a bug using launchpad. [Less]

Lately, we've been working with Ignacio Valdes to get see if OVID could work with the WorldVistA implementation.  Our initial goal is to have the get-patients.sh script which is included with the OVID package sucessfully return a list of patients ... [More] from the WorldVistA implementation.  We needed to make one change to the server code and a couple of iterations of testing/installing.  Yesterday, using the astronaut installer, we quickly installed WorldVistA in one of our development environments and, with a few minutes of tweaking, got it working.  This isn't to say that there might not be bumps later on down the road, but it was nice to see it work up to this point./tmp/ovid-0.9.0/ovid$ sh get-patients.sh Enter host that vistalink runs on (localhost): sql.medsphere.com Enter port that vistalink listens on (8002): Enter access code: OV1234 Enter verify code: patient: ZZ PATIENT,TEST ONE sex = FEMALE dob = Wed Jan 24 14:18:13 CDT 1945 eid = null id = null age = 64.0 display age = null room-bed = null current room = null attending = null ward = null current movement = null current admission = null admitting physician = null admitting diagnosis = null patient: ZZ PATIENT,TEST THREE sex = MALE dob = Mon Jan 15 14:18:13 CST 1968 eid = null id = null age = 41.0 display age = null room-bed = null current room = null attending = null ward = null current movement = null current admission = null admitting physician = null admitting diagnosis = null patient: ZZ PATIENT,TEST TWO sex = MALE dob = Wed Dec 25 14:18:13 CST 1957 eid = null id = null age = 51.0 display age = null room-bed = null current room = null attending = null ward = null current movement = null current admission = null admitting physician = null admitting diagnosis = null [Less]