OSEHRA Certification Priority Queue
|Title||Sponsor||Status||Comment||Start Date||Target Certification Level*|
|1||Patch XU*8.0*10001 & XU*.0*10002: Better VistA support for running on GT.M||OSEHRA||In Process||* Many bug fixes to Kernel Routines that work with GT.M, including many speed optimizations.
* IPv6 Support for GT.M.
* Better and faster System Status report.
* Support for GT.M on macOS and GT.M on Cygwin x86-32.
* Implementation of previously redacted code for cryptography in XUSHSH.
* Broker Multi-threaded Listener for GT.M.
* RPMS Entry Points support in %ZISH plus sundry other entry points for use by PSN*4.0*513.
* ZSY has gotten a lot of new features, including an option to examine currently running jobs.
|2||PSN*4.0*10001: Port PSN*4*513 to be in a reasonable shape for the VistA Community||OSEHRA||
Waiting: Dependent On XU*8.0*10002
|The purpose of this project is to port PSN*4*513 to be in a reasonable shape for the VistA Community. The package was released for use in the VA with several shortcomings|
|3||HL7 Clinical Procedures Automated Infrastructure Set Up||OSEHRA||Waiting||This program sets up and connects all the objects needed in VistA to implement a Clinical Procedures style of HL7 interface. Orders and sent to remote systems. Results are received by VistA from the remote system and connected to the patient record.|
|4||Radiology Protocol Tool Recorder (RAPTOR)||VA||Hold - Submitter Input||RAPTOR is an automated, electronic tool for capturing data that is needed by radiologists to optimize advanced medical imaging protocols including CT, MRI and nuclear medicine.||10/18/16|
|5||OSEHRA popHealth||OSEHRA||Hold - Submitter Input||Open-Source Clinical Quality Measure database and reporting engine with data presented through a web-based interface. It includes a centralized repository of clinical data.||3|
(March 2014 Release)
|VA||Hold - Submitter Input||Problem List issue - waiting for resolution from VA Product Development group||4/7/14||1|
Please join the OSEHRA Certification Work Group to participate in the ongoing certification process, or if you are interested in the management of the Certification Priority Queue, please join the OSEHRA Product Management Group.
OSEHRA Certified Applications
|Submission Organization||Description||Language||Certification Date||Certification Level*|
|Problem List Refactoring
||PWC||More modular and readable Problem List code||M||August 2013||2|
|Appointment Postcard Notification Letter v4.0
|VA Enterprise VistA
(Increment 4 - Phase 1)
|VA||The standard version adopted by the Department of Veterans Affairs for all 133 VA Medical Center VistA instances.||M||June 2014||1|
|OpenInfoButton||VHA/University of Utah||Based on contextual attributes that describe the EHR user, the patient, and the care setting, infobuttons anticipate clinicians’ information needs and provide automated links to a set of relevant knowledge resources to assist clinical decision support.||M, Java, Other||August 2014||3|
|M-Unit||VistA Expertise Network||The M-Unit package provides the ability to run unit tests on M code for a program.||M||September 2014||4|
|VA Enterprise VistA
(Increment 4 - Phase 2)
|VA||The standard version adopted by the Department of Veterans Affairs for all 133 VA Medical Center VistA instances.||M||October 2014||1|
|VA Enterprise VistA
(Increment 4 - Phase 3)
|VA||The standard version adopted by the Department of Veterans Affairs for all 133 VA Medical Center VistA instances.||M||January 2015||1|
|XU Digital Signature||OSEHRA||Three files to provide the interface between Delphi executables and the built-in Windows security functions released under the Apache 2.0 license||Delphi||April 2015||4|
|Increase Enrollment - My HealtheVet||VA||To streamline the education of patients on MHV, VA requires a prompt in the VistA pre-registration screen to indicate both the Veterans' desire to participate in the MHV program as well as their current MHV status.||M||April 2015||4|
|Enhanced XML Utilities for VistA||VistA Expertise Network||An upgraded MXML package to include
- Templating tools
|MSC FIleman 22.2||VistA Expertise Network||Enhancements and to Fileman done for various clients (notably, Cairo Cancer Center, City of Berkley, and Medsphere Corporation); enhancements done for the VISTA community; various bug fixes reported by the VISTA Community that have not been incorporated to VA Fileman 22.0 as currently deployed in the VA.||M||July 2015||2|
|OSEHRA Patch Module 2.5||VistA Expertise Network||The Patch Module is a software package that allows users and developers to create, revise, distribute, review, and receive software patches and updates for VistA. Options are provided for systematic entry, revision, and review of patches by developers, review and release of patches by verifiers, and display and distribution of the released patches to the users.||M||August 2015||3|
|Code Convergence - Inactive Allergies and Sign/Symptoms are selectable fix||OSEHRA||This patch issues a modification to one routine, HDISVF01, in the HEALTH DATA & INFORMATICS Package.
The modification ensures that only active allergies will be selectable from the GMR ALLERGIES File (#120.82) and
only active sign/symptoms from the SIGNS/SYMPTOMS file (120.83).
|Problem List Infinite Loop when removing and re-adding a problem||OSEHRA||
Problem List, formerly certified as part of OSEHRA VistA, now raises an error. In routine GMPLRPTR, there is an infinite loop at entry point REPLACE
|M-Unit Test (V 0.2)||J. Ivey||The M-Unit package provides the ability to run unit tests on M code for a program.||M||November 2015||4|
|M-Unit Test (V 1.3)||J. Ivey||The M-Unit package provides the ability to run unit tests on M code for a program.||M||January 2016||4|
|CPRS Medication Dialog Complex Order Fixes||DSS||Complex Orders for Medication (i.e. those that has use the "complex" dialog when ordering a medication in CPRS) did not calculate correct start dates in many circumstances; and the expected start date on the ordering dialog sometimes was incorrect as well.||M||January 2017||2|
|Maternity Tracker||OSEHRA/DSS||The Maternity Tracker project addresses the gaps in VistA for Maternity Tracking and Monitoring through a combination of field tested enhancements for better screening, tracking, monitoring, and sharing of maternity data. Also addressed were, improving women Veterans’ access to earlier prenatal care, complete post-partum care, and educational information with an emphasis on care coordination in and outside of the VA.||M,C#||May 2017||2|
|VFD*15.0*123 - Auto Resize Margins to fit Terminal Size||DSS||Many modern applications that use terminals (e.g. Midnight Commander, vim, emacs) are able to resize themselves to take all the available real-estate on the screen. This has not been done in VISTA world by and large, except by creating special terminal types. The changes in build VFD*15.0*123 make a few adjustments in %ZIS3, %ZIS4, and VALM0 and VALM1 in order to be able to use all the available screen real estate.||M||June 2017||3|
|Prostate Clinical Outlook Visualization System||OSEHRA||The Prostate Clinical Outlook Visualization System (PCOVS) was developed to provide the patient and the clinician with a tool to visualize probable treatment outcomes using institutional, patient specific data for comparing results of treatment.||R||July 2017||2|
|M-Unit Test 1.5||J. Ivey||The M-Unit package provides the ability to run unit tests on M code for a program.||M||August 2017||4|
|Victory Programming Environment||OSEHRA||VPE consists of a number of integrated programmer utilities that will increase productivity and decrease the number of key strokes required to complete normal programming tasks in the VISTA environment. Contrary to its name, VPE is not only for programmers. Many people perform technical tasks from programmer mode because it is so powerful. Think of VPE as enhanced programmer mode and then you will see that it is ideal for anyone who regularly operates in programmer mode.||M||October 2017||3|
|Patch XU*8.0*10001: Better VistA support for running on GT.M||OSEHRA||This patch provides the following features:
* Many bug fixes to Kernel Routines that work with GT.M, including many speed optimizations.
|OSEHRA||A list of notes for a patient in the right hand side of CPRS is supposed to
contain the Local Name of the note; VHA Enterprise Title. Due to an error in
the code, the retrieved VHA Enterprise Title is either not display or displayed
incorrectly. This patch fixes this so that the correct VHA Enterprise Title is
|Enhanced XINDEX for analysis of all M code stored in Data Dictionaries supported by KIDS (Revision 1)||OSEHRA||It has been found that XINDEX doesn't run or report on all VistA components that can be contained within a KIDS build. This creates errors of omission when trying to find other code references or compliance with the SAC.||M||March 2018||3|
|Enhanced XINDEX for analysis of all M code stored in Data Dictionaries supported by KIDS (Revision 2)||OSEHRA||It has been found that XINDEX doesn't run or report on all VistA components that can be contained within a KIDS build. This creates errors of omission when trying to find other code references or compliance with the SAC.||M||March 2018||3|
|Drug Accountability Fix for bug #R17623029FY18||DSS/OSEHRA||PSA DISPLAY LOCATION already has code to not print drugs that have been
inactivated and have a balance of zero. The problem is that a balance of zero
was not achievable since drug accountability still kept processing orders for
the inactivated drug from Outpatient, resulting in negative balances. Routine
PSAOP3 was modified to mirror the existing logic in PSADAI to exclude
inactivated drugs for the Drug Accountability location.
|PSJ*5.0*10001||OSEHRA||Disallow zero UNITS PER DOSE for dispensed drugs in Inpatient Pharmacy when
accepting/verifying an order in Inpatient Pharmacy Listman menu.
|DI*22.2*10001: Variable Pointer navigation incorrectly returns empty results||OSEHRA||Users who query Fileman for data can be given missing results if the query
contains a variable pointer relational navigation reference. This is the case
in a frequently queried field, the OBJECT OF ORDER field in the ORDER file. For
example, setting a condition of OBJECT OF ORDER:PATIENT:AGE30 will fail to
retrieve patients above 30 years of age if a. another patient with the same
name exists or b. the patient's name is not unique within the first 30
characters. If the results of such a report are used clinically, it will lead
to at least not printing data on patients; or at worst completely missing
them since they were not printed on the report--something which could have some
clinical significance to the health of the patients.
|Log4M||OSEHRA||The XTMLOG* routines provide a Log4M capability similar to Log4J. The logging commands can be embedded in the code and activated by initializing logging in one of several different ways. Otherwise, the logging commands are checked and then ignored.||M||June 2018||2|
* Download the official OSEHRA Certification Standards document for a detailed description of the process and criteria used.