Skip navigation

Manage categories

Close

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

Categories in OpenVista Server
Add a new category (0 remaining)
Loading widget...

Recent Discussions

Refresh this widget

Recent Documents

Refresh this widget

Recent Commits

Loading widget...

OpenVista Server

OpenVista Server is an Electronic Health Record (EHR) and Health Information System (HIS) derived from the VA Freedom of Information Act (FOIA) VistA server release and includes defect corrections and a selection of commercial enhancements equivalent to what has been released at Medsphere client sites.

The OpenVista Server distribution is released as a snapshot of a running system for new installations and as a series of KIDS builds so existing users can patch up from a previous release.

Quick Links

Recent Blog Posts

Refresh this widget
0

We've been a little behind with our OpenVista Server releases, so Service Pack 3 and 4 are being released simultaneously.  From the NEWS file:

 

1.5 Service Pack 4
==================
 
Service Pack 4 contains defect corrections and minor enhancements.  These are
some of the higher priority corrections and enhancements that have been
implemented:
 
Defects
 * Several problems with ADT and billing interfaces were resolved.
 * The most current diet was not displaying in the Current Diet patient data
   object.
 * Several HL7-related problems when running on GT.M were resolved.
 * ASPIRIN allergy under VA classification was not triggering an allergy alert.
 * After setting up Incomplete Record Tracking (IRT), a crash was occurring on
   the orders tab.
 * Sulfa Drugs allergies were not triggering an allergy alert.
 * An infinite loop when looking up an item in the lexicon was fixed.
 * Discontinued or auto-discontinued inpatient orders were not viewable in the
   terminal interface, but were still visible in CPRS.
 * Several problems with laboratory and radiology interfaces were resolved.
 * BCMA was not reading patient movement file correctly.
 
Enhancements
 * A parameter was added to allow charging based on BCMA versus charging on
   dispensing.
 * ZTMGRSET no longer attempts to recompile routines that have not changed.
 * New point of care specimen collection system from IntelliDOT.
 * Multiple enhancements to laboratory interfaces.
 * Options were added to write nightly Pharmacy MARs and Profiles to the HFS
   where they can be obtained in case of downtime.
 * Several new pharmacy reports, including billing and medication
   administration summary by ward.
 * Radiology auto registration creates a case number when radiology orders are
   submitted, allowing sites with a PACS system to populate the PACS worklist.
 
 
1.5 Service Pack 3
==================
 
Service Pack 3 is another service pack release that contains defect corrections
and minor enhancements.  These are some of the higher priority corrections and
enhancements that have been implemented:
 
Defects
 * Multiple problems with various interfaces were resolved.
 * The IRT UPDATE STANDARD DEFICIENCIES option only updated Discharge Summary
   notes.
 * OWN MEDICATION orders were not changing to Signed status.
 * The Ward Collect Report was printing an extra blank page at the beginning.
 * Consult tracking updates were not being shown when IFC language was
   disabled.
 * Radiology exam requests were not being printed automatically when ordered
   via the command-line interface.
 * Entering an ICD number from CPC/ICD9CM coding caused an error.
 * HL7 listeners did not show correct shutdown state.
 * Medication replenishment report was incorrectly calculating number of doses
   administered.
 * Infinite loop in LEXAS6.
 * Undefined variable error on Orders tab after setting up IRT.
 * Allergy of ASPRIN listed under VA Classification does not fire allergy alert.
 * "Sulfa Drugs" allergy did not work.
 * Printing to a network printer caused an error.
 
Enhancements
 * Pick Lists can be printed with or without Ward Stock items.
 * Three order request forms have been created for use by Radiology users.
 * Added new Transfer To Inpatient and Transfer to Outpatient statuses for home
   medications.
 * About OpenVista option shows copyright and version information.
 * Report showing Medication Administration Summary by Ward was added.
 * Automatically check patients into radiology system and assign a case number
   to radiology orders when an exam is ordered.

 

As usual, Service Pack 4 includes the latest OVID and GT.M Integration work.  If you are doing a new install, note that ^%ZOSF("CLUSTER") has been pre-set to GTM and the BOX:VOLUME pair in the TASKMAN SITE PARAMETERS file has been pre-set to OPEN:GTM.  You no longer have to configure the BOX:VOLUME pair with the hostname of the machine you're running on.  If you want the old behavior back, simply K ^%ZOSF("CLUSTER").  See LP #422885 for more details.

 

You can download the releases as either KIDS builds (for upgrading existing installations) or as full databases (for new installs) from our downloads page.

310 Views 0 Comments Permalink Tags: release, openvista_server
0

The bazaar repository upgrade has been completed.  OpenVista Server's mainline branch still shows an "updating" message on Launchpad.net, but the branch itself is completely upgraded and we've been able to push new revisions to it.  If you have a checkout of OpenVista Server, please upgrade your repository with "bzr upgrade".

189 Views 0 Comments Permalink Tags: bazaar, openvista_server, launchpad
0

Since my last post, Lucid has been released and bzr-2.1.1 is now available in EPEL.  OpenVista Server's mainline branch on Launchpad.net will be upgraded to branch format 7/repository format 2a next week to take advantage of the performance improvements described in my last post

214 Views 0 Comments Permalink Tags: bazaar, openvista_server, revision_control
0

While installing Service Pack 3 this week, I noticed that bzr diff and bzr revert were taking a very long time -- upwards of 20 minutes each for files like P.zwr.  Of course, P.zwr is a ~200MB text file, so I wasn't expecting blazing performance, but 20 minutes on several-year-old hardware made me think that there might be room for improvement.  Since I had time on my hands while I waited for the commands to finish, I looked to see what branch/repository format I was using and what the latest format was.  As it turns out, I was using the pack-0.92 repository format with a version 6 branch format.  This was on bazaar 2.1.1 on a Lucid beta box.  I tried upgrading to the new 2a repository format, then re-ran the slow commands.  To my surprise, they finished in 10-15 seconds.

 

Obviously, this is an improvement worth upgrading for, so I began to research what it would take to upgrade the mainline branch hosted on Launchpad.net.  Again, I was pleasantly surprised -- I don't have to do anything!  The Bazaar 2.0 upgrade guide explains: "To allow isolation between public and private branches, Launchpad uses stacked branches rather than shared repositories as the core technology for efficient branch storage."  So the choice of repository format is a local decision.  If you're running a version of bazaar that can support 2a repositories, all you have to do is create a 2a repository, then branch the OpenVista Server mainline branch in it.  Version 6 branches can be hosted in a 2a repository, so the mainline branch on Launchpad.net can remain at version 6 for backwards compatibility.

 

Bazaar versions >= 2.0 use the 2a repository format by default when you run bzr init-repo, and Bazaar version 2.1.1 is included in Lucid.  Also, there's a bug in RedHat's bugzilla to upgrade the version of bazaar in EPEL to version 2.1.1, so if QA goes well, 2.1.1 will be in EPEL, too.  The bottom line is: if you're running an older version of bazaar or have migrated an existing repository created with an older version of bazaar, upgrade to the 2a repository format for much better diff/revert performance on large files.  If you're starting out with a newer version of bazaar, which will be installed by default in both Ubuntu and EPEL soon, you don't have to do anything!

 

Update: unfortunately, I can't push back to the older-format Launchpad branch from the new branch in my local 2a repository, so it looks like I'll have to upgrade the branch/repository on Launchpad.net after all. I'll revisit this once bazaar 2.1.1 is more widely available in a few months.

265 Views 0 Comments Permalink Tags: bazaar, openvista_server, revision_control
4

We released a new version of OpenVista Server today.  From the NEWS file:

Service Pack 2 includes all patches that have been completed, tested, and
packaged for the 2nd quarter.  This release contains defect corrections and
minor enhancements.  These are some of the higher priority corrections and
enhancements that have been implemented:

Defects:
 * Not all HL7 exceptions/errors were sent to an Exceptions file or the Error
   Log.
 * Visits were created without an authoritative source.
 * When merging patients, images were not properly linked to the correct
   patient.
 * Dispensing extra medication units caused an error.
 * The medical reference file loader was updated for 2009.
 * Health factor could not be added as an element to Reminder dialog box.
 * The system was storing and converting weights from kg incorrectly.

Enhancements
 * The date/time of each Alert will be shown on the first display list. The
   previous 80-character limit on the length of an individual Alert message
   (XQAMSG variable) was removed.
 * The OVID patches are included in this release, so it is no longer necessary
   to install OVID separately.
 * The OpenVista/GT.M integration project patch is included in this release,
   so it is no longer necessary to install it separately.

This release is available in a number of formats -- as routines and globals for
new GT.M installations, as a CACHE.DAT for new Cache installations, and as a
series of KIDS builds to upgrade existing installations.

 

Not being a clinical person myself, the part I'm excited about is the inclusion of OVID and the GT.M Integration Project work.  Having these two builds already installed out-of-the-box will make it a lot easier for people who are new to OpenVista to install OpenVista and develop with OpenVista.  We've also done some work to pre-configure the RPC broker and give users the right keys for a smoother install.

 

Another important change we've made is to re-license the core modules as LGPL.  We've written a FAQ about this license change, so if you're curious about why we did it or how you're affected, please take a look at the FAQ.

 

Finally, this is our first release that is available both as a new database and as a series of KIDS builds, so if you've installed OpenVista Server in production previously, you can upgrade your installation the same way we do.  You can determine the sequence in which the patches should be installed by looking at the ChangeLog file.

 

You can download the new Server release from the usual place.  We'll be releasing a new version of the Appliance that includes this new Server release and today's CIS release within the next few days.

1,061 Views 4 Comments Permalink Tags: openvista_server, release
More