CareGraf announced a new release for FMQL:The latest FMQL (FileMan Query Language) has just posted on caregraf.org (http://www.caregraf.org/semanticvista). FMQL let's you query any and all data in a VistA EHR. Some highlights of this release:all
... [More]
web-clients use the latest HTML5 standards and still support IE 7"Query Maker", a new "click and query" web client for learning how to create FMQL. The FileMan Rambler client has fully query exposure too.improved VistA vocabulary management to leverage version 2 of Caregraf's public datasets (see below)fine-grained control for walks through deep and wide containment hierarchiesimproved paging support for walking larger filesimproved projection of lab package data: lab data now looks like any other information in FileMan FMQL is completely open source and can be seen in action and downloaded from http://www.caregraf.org/semanticvista *** coming Monday July 18th: the next chapter for Caregraf's Public Datasets (http://www.caregraf.org/datasets), medical vocabularies published as linked-data to promote patient data exchange. The emphasis is on SNOMED and the VA's national vocabularies and, through FMQL, VistA is fully integrated. [Less]
|
Hugo Toche has released an updated mobile EHRAccess application for the iPhone via the Apple iTunes Store. It is free to download and use. With this application you can securely access the patient data in your OpenVista system. All you need to do
... [More]
is install the OpenVista REST module and point the application to it via the server field in the login screen. This is where you can get the open source OpenVista REST module. No data is kept on the device for security purposes. Hugo is active here on Medsphere.org, so feel free to ask him questions or provide feedback. You can also view his other mobile applications at Troche Labs. [Less]
|
We are pleased to announce OVID 1.1.2 has been released. We would like to offer our thanks and appreciation to the MITRE Corporation who worked with OpenVista and OVID as a part of their MedCafe.org research, and generously contributed their changes
... [More]
back to the community. Highlights of the updates in this release:
MSCVJAVA developer utility creates FM java class from FileMan schema
Enhanced Patient Medication class
Enhanced Patient Repository class
Ability to Create and Sign notes, as well as add additional Signers
Thanks to the hard work and generous contributions by the MITRE Corporation, a number of new and enhanced repositories were added. This work was done as part of the MedCafe project, a research effort designed to explore the viability of specific system design principles for EHR access. The developers used OVID as part of their data access strategy and in the process created and enhanced the available repositories that are released with OVID. Thanks to their contributions, we have incorporated that work back into the OVID mainline for this release.
Ability to Add and Update a patient
The PatientVisit domain was greatly enhanced to include:
CPTs
Diagnosis
Name Components
Religion
Room-Bed
State
Exam
Health Factors
Immunizations
Patient Education
Purpose Of Visit
Provider
Skin Test
Treatment
and more
The PatientAllergy domain was enhanced to support the Addition and Update of patient allergies, as well as data from the following areas:
Drug Class
Drug Ingredients
Generics
Allergies (GMR, Patient and Comments)
Symptoms
[Less]
|
We are happy to announce the latest version of OVID has been released into open source -- binaries and source repository are available from the project homepage and on LaunchPad.net. This release brings significant refactoring of project structure
... [More]
and methods in order to improve authentication, connection management, logging, and more -- for details see What's New in OVID Release 1.1. Additional OVID domains have been added and existing ones updated. Finally, this release also brings a community requested change to the license -- OVID 1.1 is now available under the LGPL license. Please read the release notes for specifics on changes and added/updated domains.Please read the license change FAQ to understand why the change and how it might affect your project.Please review the various new and updates tutorials on using OVID in your projects. [Less]
|
We've recently updated the ovid source project in Launchpad to integrate several enhancements and bug fixes that have been developed over the last few months. Included in this release: @FMAnnotateFieldInfo annotations can now be placed on getters as
... [More]
well as on class variables.OVID supports inheritance to an extent. Note the FMPatientContact extends FMDemographicPatient, which extends FMPatient. Each class adds new fields along the way. This makes it much easier to extend existing behavior.Bug fixes and enhancements to the mumps routines are provided in two new KIDS buids: MSCRES.1.3.KID and MSCFM.1.3.KID.Some additions to existing domains are included, such as RaceInformation tied to an FMPatient. (See PatientRepository.java).Of course, general bug fixes are also included in the java sources. This release should be backwards compatibile to any projects developed against previous version of OVID. It is recommended that you apply the new KIDS builds and drop in new ovid.jar and ovid-domain.jar. Installation instructions can be found at http://medsphere.org/docs/DOC-1719. Don't hesitate to post questions and/or suggestions to the OVID project. Please submit bugs to https://launchpad.net/ovid. [Less]
|
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
... [More]
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. . [Less]
|
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
... [More]
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 [Less]
|
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
... [More]
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 RPCBrokerSupport for CIABrokerThe 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. [Less]
|
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
... [More]
(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 [email protected] 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. [Less]
|
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
... [More]
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. [Less]
|