Difference between revisions of "MDHT Template Sub Project"
| Line 3: | Line 3: | ||
== Overview == | == Overview == | ||
The goal of this pilot is to demonstrate how the [https://mdht.projects.openhealthtools.org Model-Driven Health Tools (MDHT)] [https://mdht.projects.openhealthtools.org/cda CDA Tools project] can be used to design and implement CDA templates. This includes the generation of a published implementation guide and an EMF-based Java runtime API that supports programmatic production, consumption, and validation of CDA XML instances. | The goal of this pilot is to demonstrate how the [https://mdht.projects.openhealthtools.org Model-Driven Health Tools (MDHT)] [https://mdht.projects.openhealthtools.org/cda CDA Tools project] can be used to design and implement CDA templates. This includes the generation of a published implementation guide and an EMF-based Java runtime API that supports programmatic production, consumption, and validation of CDA XML instances. | ||
| + | |||
| + | An example application developer scenario would be to use the generated Java library to create an EHR system adapter that exports CDA TB Progress Note instances for exchange with external entities, or receive TB Progress Note instances and load them into domain-specific Java objects that may be processed to display or import data into the EHR system, and to validate instance (imported or exported) for conformance to the implementation guide template rules. | ||
== Project Status == | == Project Status == | ||
Revision as of 17:04, 26 February 2010
Back to Structured Document Template Design Pilot
Contents
Overview
The goal of this pilot is to demonstrate how the Model-Driven Health Tools (MDHT) CDA Tools project can be used to design and implement CDA templates. This includes the generation of a published implementation guide and an EMF-based Java runtime API that supports programmatic production, consumption, and validation of CDA XML instances.
An example application developer scenario would be to use the generated Java library to create an EHR system adapter that exports CDA TB Progress Note instances for exchange with external entities, or receive TB Progress Note instances and load them into domain-specific Java objects that may be processed to display or import data into the EHR system, and to validate instance (imported or exported) for conformance to the implementation guide template rules.
Project Status
- Milestone 1 -- February 26, 2010
- Completed UML model of all pilot conformance rules
- Generated implementation guide to PDF and Eclipse Help format (html)
- Generated Java runtime classes for creating, consuming, and validating CDA instances based on the pilot templates. Wrote small test Java program to demonstrate use.
- Next steps:
- Refine model representation for value sets
- Refine published implementation guide
- Expand example Java program to illustrate embedding TB Progress Note in a small application
Project Execution Phase
Use CDA Tools to design CDA templates for example use case
We will create all of the templates required by the template tool pilot use case. This includes creating classes for each template and specifying all conformance rules using property redefinitions, directed associations, and directly using OCL expressions (if necessary).
Project Delivery Phase
Generate published implementation guide in DITA format
By producing the DITA format, we can target multiple publication formats such as XHTML, Eclipse Help, and PDF.
Generate Java-based Runtime API
The template model will be transformed and ultimately imported into EMF. The EMF model will be used to produce Java source code.
