Difference between revisions of "CS API based on collapsed models"

From HL7Wiki
Jump to navigation Jump to search
Line 6: Line 6:
 
==Details==
 
==Details==
  
Lyssa Koton Neel (CIHI), on the RFP for a Canadian tool based on this mechanism:
+
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.
 
**Grahame: More specifically, as implemented in the pan-Canadian schemas / Instance editor.

Revision as of 13:40, 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 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:
    1. Hide all fixed values from the application
    2. Where possible, expose data elements using business names, not HL7 names
    3. Simplify the object model by eliminating unnecessary nesting, 1..1 relationships and similar constructs
    4. 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/