Code Convergence Work Group

The purpose of this group is to identify key modules of the VistA EHR architecture which are universal to the vast majority of configurations, and harmonize these modules to allow the community to operate from a unified ‘core’ base.

The issue tracker used to coordinate this project is located here:

The wiki used to track documentation and other document artifacts.

Please join us for Weekly calls on: Thursdays :  3:00pm - 4:00pm EST

Phone U.S. & Canada:  1-415-655-0002     Access code: 739 548 224

Web Screen Sharing:

Group Email:


- Private group -
No questions have been added to this group.

KIDS/Certification Submission Requirements

In order for a submission of code to be compiled into a KIDs file, and submitted for certification through the OSEHRA process, a number of artifacts and data points are required.  This wiki is to capture these elements, please use this document to identify them.

This document will overlap with the requirements of the certification process, and the working group associated with it.  We will work collaboratively to ensure the expectations of both of these efforts meet.

KIDS file Pre-requisite Element Summary:

Code Convergence Milestones

This wiki is meant to document current and ongoing project milestones, and targeted completion dates, for activities of the code convergence group.  This document is in wiki format to encourage contribution from the community members.

Milestone 1 - In progress

The code convergence group intends to, by 4.30.2012, have successfully completed the following objectives:

ANSI X11.1-1995 M Considerations

As GT.M currently only supports the ANSI X11.1-1995 version of M/MUMPS, it doesn't incorporate extensions made to the standard by Intersystems.  As part of code convergence, some version have incorporated Intersystems extensions.  These must documented for resolution.

Greater than or equal to expression.

Cache Expression:  >=

ANSI Expression: '<

Less than or equal to expression.

Cache Expression:  <=

VistA Analytics - FOIA vs the other VistAs

VistA Analytics

Latest: Upgrade forks and age reports. Added report for RPMS

VistA Analytics identifies the configuration and dynamic state of a VistA ("VistA being analysed"). It then compares this information against the configuration and state of a Baseline VistA. This tool should help in the VA's 10-1 effort and in code-convergence, the effort to merge 3rd party VistA's with FOIA VistA.

VistA Audit: OpenVistA vs WorldVistA

Background: define a baseline VistA by querying deployed VistAs about their configurations and dynamic state and comparing the results. A work-in-progress. Three reports comparing WorldVistA (Latest Release/George Lilly's) and OpenVistA (Caregraf): Packages [[|WVvsOVPackages]] In general the packages are the same though WV is more up to date. Both are behind FOIA (see dates in builds in the packages report), in some cases a lot behind - dates of 2006 or 2008 and FOIA is at 2011/2012.