daveloyall / mu2

Meaningful Use 2 Certification

The Meaningful Use (MU2) Repository of Useful Information

This repository contains information on Meaningful Use Stage 2 Certification. Contents include, test data, test software, links to public test tool servers, and other related information. Much of the information included here is in documentation in Markdown format (with the extension .md) so this repository is in part a wiki.

The materials found here cover the NIST test tools for meaningful use stage 2. The NIST tools are under continued development and are frequently updated.
The information here may not represent final releases of information by any government organization. This information is provided "as-is" for convenience.
Check back for frequent updates.

For more information on Meaningful Use 2, a bookmarked version of the final rule can be found here:

• The CMS EHR Incentive Program Stage 2 Final Rule
• ONC Certification Criteria Program 2014 Edition

For more information on Meaningful Use 2 and Certification, visit HealthIT.gov

Contents

• Transport Tools - includes CCDA, Direct, SOAP, SAML, etc.
• HL7v2 Tools - includes ELR, LRI, Syndromic, & Immunization
• CDA-C32 Tools - includes Cancer Registry
• ePrescribing - includes SCRIPT XML, SCRIPT EDIFAC

Quick Links

• Direct Hello World
• How to Create Direct Certificates using NIST's pre-configured Virtual Machine
• TTT Configuration
• NIST Tools as AMI and VMWare Image
• Using the VMWare Image to Create Certificates for TTT

List of Google Groups

To see all the Google Groups on a single page go to http://bit.ly/nistgg or http://meaningfuluse.s3.amazonaws.com/googlegroups.html

Name	Email	URL	Accessibility
ATL Tools	[email protected]	https://groups.google.com/d/forum/atl-tools	For Accredited Testing Labs Only
Cancer Reg Testing Tool	[email protected]	https://groups.google.com/d/forum/cancer-reg-testing-tool	Public for Viewing & Posting
ePrescribing Testing Tool	[email protected]	https://groups.google.com/d/forum/erx-testing-tool	Public for Viewing & Posting
HL7v2 Immunization Testing	[email protected]	https://groups.google.com/d/forum/hl7v2-immunization-testing	Public for Viewing & Posting
HL7v2 Lab Testing	[email protected]	https://groups.google.com/d/forum/hl7v2-lab-testing	Public for Viewing & Posting
HL7v2 Reportable Lab Testing	[email protected]	https://groups.google.com/d/forum/hl7v2-reportable-lab-testing	Public for Viewing & Posting
HL7v2 Syndromic Testing	[email protected]	https://groups.google.com/d/forum/hl7v2-syndromic-testing	Public for Viewing & Posting
Transport Testing Tool	[email protected]	https://groups.google.com/d/forum/transport-testing-tool	Public for Viewing & Posting

mu2's Issues

Not all of NIST's MU code is online.

Problem

Despite being really valuable for specific use cases, the NIST MU validation tools are not as valuable as they could be.

Cause

I am unable to make minor changes to NIST MU validation tools and subsequently rebuild the tools.

Root Cause

I haven't been able to find the source code for some classes used in the MU validation tools suite. I believe that these items simply aren't online.

Examples

Note: this is not an exhaustive list. I think that there is a lot missing.

• mu-lab-1.5.0.zip:mu-lab-1.5.0/mu-lab.war:WEB-INF/classes/gov/nist/healthcare/mu/controller/Er7TreeControllerImpl.class

Resolution

• Put all the code in one place online.
• Document the builds.
• Make sure that daily work regarding MU at NIST is based on and stored in the public repositories. (Reader, ask me why.)

Roadblocks between here and a solution

We can't ask the NIST folks to organize their repositories and document their builds without necessarily asking them to spend less time on other important things--like validation internals. I for one want them to keep working on those things. Thus, I don't want the NIST folks to clean up their repositories and document their builds.

Proposed path to resolution

Ask the NIST folks to open their internal filesystems to the public or a small group (n=[1..3]) of volunteers. These volunteers will carry copy things over to the public repos, document the builds, and provide support to NIST folks with regard to using the public repos for daily work. (Incidentally, I think that https://github.com/meaningfuluse would be a fine location for the proposed repos.)