1. Summary Report Project Name: Model-Driven Health Tools (MDHT)
Brief Project Description: Support the complete lifecycle of designing CDA implementation guides, publishing standards specification and developer docs, generating production quality Java libraries for use by application developers, and validating CDA instances to the conformance rules.
Major milestones to date: M5 milestone May 2010
Projected milestones: M6 & M7 in July & Sept 2010
Major release dates: 1.0 RC in Nov 2010, 1.0 in Jan 2011
Contribution date: July 2008
Contribution value (Person years or market value or lines of code):
Approximately 6 person years invested in the original contribution plus new work within the MDHT project team.

2. OHT MDHT 06/2010 Boca Chart Content Pressures Added Deleted & Changed
OHT Terms of Use update before 1.0 release
Need terminology services: discover and validate model constraints
Extend approach to support HL7 V3 modeling
HL7 SDWG pilot project outcome and next steps
Authoring – designing CDA templates, UI enhancements
Publishing – DITA publishing workflow
Validation – validating CDA instances against constraints in the model, terminologies
Implementation – domain-specific APIs, utilities
Support for modeling code system metadata and value sets
XML editor extensions for CDA instance validation
JUnit test suite for generated model code
Deleted & Changed
De-scoped RIM Tools development to SMD/UML model transformation
Dependencies
Packaging Editions
HL7 SDWG best practices for publishing implementation guides
Eclipse 3.5 Galileo with UML2, OCL and EMF plug-ins .
Milestones
M6, Jul 2010
M7, Sep 2010
1.0 RC, Nov 2010
1.0 Release, Jan 2011
Statistics .

3. Major Dates and Deliverables 2Q2010
12 Month Rolling Plan
Major Dates and Deliverables 2Q2010
2Q11
1.0 Release
CDA Tools
January 2011
1Q11
1.0 Release Candidate CDA Tools
November 2010
4Q10
Milestone 7 of
CDA Tools
September 2010
3Q10
Milestone 6 of
CDA Tools
July 2010
2Q10
Milestone 5 of
CDA Tools
May 2010

4. MDHT Project Benefits for CDA
Standards organizations
Author and publish implementation guides, produce CDA instance validation suites.
Formalize representation of CDA implementation guide conformance rules
Replace current practice of using MS Word for specification development
UML specification is testable for consistency and use of best practices
Enables automated model-driven development and code-generation
Automate publication of implementation guides in multiple formats (PDF and XHTML) and alternative content structure (ballot document vs. implementer view)
Automate generation of CDA instance validator from specification model (using Java and OCL)
Business Analysts
Consistent format of published implementation guide between different standards organizations (HL7, IHE, and HITSP)
Cross-referenced, hyperlinked reference material accelerates analysis and EHR mapping
Publish a “developer view” of implementation guide that combines conformance rules from all inherited templates and base CDA type
Java Implementers
Reduce Development Cost: Time and resources for analysis and implementation of CDA content and conformance rules
Reduce Maintenance Cost: High quality, domain-specific API for programmatic access to CDA content, and validating conformance with standard implementation guide rules (e.g. CCD and HITSP C32/C83)
Future support possible for non-Java implementation languages

5. Authoring

6. Publishing

7. Validation Results on Web

8. Validation in XML Editor