VOE like VistA has always had lab interfacing capability....the VA uses Labcorp and I think Quest....but out of the box interfacing requires investing the time and money to make it work and the Beta process left that up to the sites and their vendors to accomplish. The beta test process followed a very "laissez faire" model and it was up to vendor/client to negotiate and fund what was configured or integrated.... unfortunately expectations in some case were not set accurately... and as a consequence we did lose a couple of sites.
Having said that....we recognized the challenges of using "vanilla" VistA lab interfacing to satisfy CCHIT certification and in meeting the needs of the target market for VOE....so in parallel to the Beta testing a more generic approach was developed for interfacing using the Mirth integration engine. This enhancement will be part of VOE and is going through final quality assurance. Joseph Daniel L. Johnson wrote: > For your info, the word at the American Health Quality Assn meeting in > N. Orleans next week was, "The lack of a lab interface torpedoed > deployment of Vista Office at some of our (CMS) beta sites." > > Dan Johnson > > On Thu, 2007-02-22 at 10:59 -0500, K.S. Bhaskar wrote: >> VistA Office EHR SemiVivA 2.3.1 (MD5 sum >> 16a0e6ae1951a512e88d83edd4e254a9) is available for downloading from >> the WorldVistA project page at Source Forge >> (http://sourceforge.net/projects/worldvista). >> >> VistA Office EHR SemiVivA 2.3.1 packages the release of VistA Office >> EHR 2.3.1 as made available at the VistA Office EHR project page at >> Source Forge (http://sourceforge.net/projects/vista-officeehr) on >> January 31, 2007. Nancy Anthracite configured the settings for it to >> run on GT.M, and provided the CPRS and Vitals executables (for >> Windows). An access code of VistAis#1 and verify code of #1isVistA >> will work for CPRS to connect. >> >> Please note that this software has not been field tested. >> Furthermore, most of the components for VOE were introduced to none of >> the usual VistA SDLC (Software Development Life Cycle) where packages >> and patches of any complexity usually endure a number of iterations >> between SQA (Software Quality Assurance) reviews, field testing and >> developer responses. This software is intended for evaluation / >> demonstration purposes. You take all responsibility for using it. >> >> This SemiViVA package is bundled with GT.M V5.2-000, as available >> under the GNU General Public License from the GT.M project page at >> Source Forge (http://sourceforge.net/projects/sanchez-gtm). A SemiVivA >> package is a one-step install of VistA and GT.M on a Linux machine. >> >> Assuming the file has been downloaded as >> /Distrib/VistAOfficeEHRSemiVivA_2.3.1.tgz, to install on your Linux >> PC, execute the following, as root: >> >> cd /usr/local >> tar zxvf /Distrib/VistAOfficeEHRSemiVivA_2.3.1.tgz >> >> This will create new directories /usr/local/VistAOfficeEHR_2.3.1 and >> /usr/local/gtm_V5.2-000. Please note that this will overwrite any >> directories or symbolic links you have with those names. You may wish >> to replace your symbolic links with new ones (i.e., the following is >> optional; also to be executed as root in /usr/local): >> >> rm gtm ; ln -s gtm_V5.2-000 gtm >> rm VistAOfficeEHR ; ln -s VistAOfficeEHR_2.3.1 VistAOfficeEHR >> >> To use it, you will need to create a working environment (see >> http://tinyurl.com/738jk for details). To create an environment in >> ~/myVistAOfficeEHR (the choice of directory name is entirely yours), >> as a normal user, execute: >> >> /usr/local/VistAOfficeEHR_2.3.1/install ~/myVistAOfficeEHR >> >> Subsequently, to get to an interactive mode GT.M prompt in that >> environment, execute: >> >> ~/myVistAOfficeEHR/gtm_V5.2-000/run >> >> To run entryref ABC^DEF in that environment, execute: >> >> ~/myVistAOfficeEHR/gtm_V5.2-000/run ABC^DEF >> >> To get a CPRS GUI to connect to the environment in ~/myVistAOfficeEHR, >> you should set up inetd/xinetd to execute >> ~/myVistAOfficeEHR/gtm_V5.2-000/cprs_direct in response to a >> connection request. If you have set up inetd/xinetd to listen at port >> P, then use "CPRSChart s=SYSTEM p=P CCOW=DISABLE" where SYSTEM is the >> name or IP address of the VistA server. >> >> Please post questions, comments & issues on the hardhats list >> (http://groups.google.com/group/hardhats) >> >> K.S. Bhaskar >> >> >> >> > > > > > Yahoo! Groups - Join or create groups, clubs, forums & communities. Links > > > > . >
