This wiki has undergone a migration to Confluence found Here
Difference between revisions of "CS API based on collapsed models"
Jump to navigation
Jump to search
Rene spronk (talk | contribs) |
Rene spronk (talk | contribs) |
||
| Line 8: | Line 8: | ||
Lyssa Koton Neel (CIHI), on the RFP for a Canadian tool based on this mechanism: | Lyssa Koton Neel (CIHI), on the RFP for a Canadian tool based on this mechanism: | ||
*The "collapsed" MIF is described here [[Message_reshaping_rules]] | *The "collapsed" MIF is described here [[Message_reshaping_rules]] | ||
| − | **Grahame: More specifically, as implemented in the pan-Canadian schemas / Instance | + | **Grahame: More specifically, as implemented in the pan-Canadian schemas / Instance editor. |
| − | editor. | ||
*It does the following: | *It does the following: | ||
*#Hide all fixed values from the application | *#Hide all fixed values from the application | ||
Revision as of 12:34, 13 October 2009
Summary
- If one were to create a programming API for RIM based models, one could base it on collapsed/flattened models instead of on a CIM. Code generation based on collapsed/flattened models results in smaller (more manageable) code.
- Open question: could one use collapsed/flattened models in the CO and CP cells?
Details
Lyssa Koton Neel (CIHI), on the RFP for a Canadian tool based on this mechanism:
- The "collapsed" MIF is described here Message_reshaping_rules
- Grahame: More specifically, as implemented in the pan-Canadian schemas / Instance editor.
- It does the following:
- Hide all fixed values from the application
- Where possible, expose data elements using business names, not HL7 names
- Simplify the object model by eliminating unnecessary nesting, 1..1 relationships and similar constructs
- etc.
- This had been balloted as a "new ITS" but was rejected.
- Mohawk College has a working version of such a system (called the "Everest Framework") available on their website: http://everest.marc-hi.ca/
