Difference between revisions of "MIF based code generation"
Rene spronk (talk | contribs) |
Rene spronk (talk | contribs) |
||
| Line 9: | Line 9: | ||
==UML== | ==UML== | ||
| + | Galen Mulrooney/Dave Carlson/Iona (all involved on behalf of the VA): These software components are being built as part of the Open Health Tools project, "Modeling Tools for Healthcare", which is an open-source project to produce tooling that can be used by Standards Development Organizations to produce and publish interoperability specifications (i.e., Messaging, Documents, SOA) using UML and other Open Standards-based platforms. | ||
| + | |||
Anyone concerned that we cannot represent HL7 concepts in UML ignores the fact that UML can be extended using something called a "UML profile". When RIM.coremif is imported all the HL7-specific extensions are imported into stereotype properties. Nothing is lost. We are using two profiles: | Anyone concerned that we cannot represent HL7 concepts in UML ignores the fact that UML can be extended using something called a "UML profile". When RIM.coremif is imported all the HL7-specific extensions are imported into stereotype properties. Nothing is lost. We are using two profiles: | ||
#HDF profile based on the profile authored by Abdul Malik, if you recall, some time ago | #HDF profile based on the profile authored by Abdul Malik, if you recall, some time ago | ||
Revision as of 15:14, 18 January 2009
Contents
Summary
When it comes to code generation the best (most complete) code should be generated from the MIF. An alternative is Schema based code generation.
Analysis
The primary source for the code generation is likely to be one of the options shown below:
- MIF - the code generator has to be aware of the structure of the MIF
- UML (derived from the MIF) - the code generator has to know UML, including a few extensions that are v3 specific
UML
Galen Mulrooney/Dave Carlson/Iona (all involved on behalf of the VA): These software components are being built as part of the Open Health Tools project, "Modeling Tools for Healthcare", which is an open-source project to produce tooling that can be used by Standards Development Organizations to produce and publish interoperability specifications (i.e., Messaging, Documents, SOA) using UML and other Open Standards-based platforms.
Anyone concerned that we cannot represent HL7 concepts in UML ignores the fact that UML can be extended using something called a "UML profile". When RIM.coremif is imported all the HL7-specific extensions are imported into stereotype properties. Nothing is lost. We are using two profiles:
- HDF profile based on the profile authored by Abdul Malik, if you recall, some time ago
- RIM profile that allows us to track clones to the RIM and to store the class/type and moodCode which would a look redundant to an audience outside HL7.
To install and use these profiles (along with the vocabulary and abstract datatypes) you need update Eclise-based UML 2 tool and install the HL7 plugin as specified in: RSM Quickstart.doc. IBM is providing free RSM licenses for those who need UML tools for HL7 standard development (DAM, DIM, etc.).
If you wish to learn more about the UML extensions and how they are represented as UML stereotypes, please take a look at: UML BOF Wiki.
The HL7 plugin will be maintained and improved by the Open Health Tools' Modeling Tools for Healthcare project.
We have imported RIM.coremif into UML and checked into SVN at: this directory (RIM.emx).
