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) (New page: category:RIMBAA Issue ==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 ...) |
Rene spronk (talk | contribs) |
||
| (6 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | [[category: | + | [[category:Closed AID Issue]] |
| − | |||
==Summary== | ==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. | *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? | ||
| + | |||
| + | Related: [[MIF based code generation]], [[New ITS]] | ||
==Details== | ==Details== | ||
| − | Lyssa | + | Lyssa K. 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 editor. | ||
*It does the following: | *It does the following: | ||
*#Hide all fixed values from the application | *#Hide all fixed values from the application | ||
| Line 14: | Line 17: | ||
*#etc. | *#etc. | ||
*This had been balloted as a "new ITS" but was rejected. | *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/] | + | *Mohawk College has a working version of such a system (called the "Everest Framework") available on their website: [http://everest.marc-hi.ca/ http://everest.marc-hi.ca/] |
| + | **During the Phoenix WGM (January 2010) Mohawk reported that initially their API was based on a mixture of collapsed-models and full v3 models. This only lead to confusion on the part of the implementers. Their conclusion: either hide all complexity (and use a simple [[DSL]]), or use the fullblown v3 models. Don't mix the two. | ||
Latest revision as of 08:06, 25 March 2015
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?
Related: MIF based code generation, New ITS
Details
Lyssa K. 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/
- During the Phoenix WGM (January 2010) Mohawk reported that initially their API was based on a mixture of collapsed-models and full v3 models. This only lead to confusion on the part of the implementers. Their conclusion: either hide all complexity (and use a simple DSL), or use the fullblown v3 models. Don't mix the two.
