This wiki has undergone a migration to Confluence found Here

Difference between revisions of "Fresh Look"

From HL7Wiki
Jump to navigation Jump to search
Line 27: Line 27:
 
*** US National Cancer Institute: https://cdebrowser.nci.nih.gov/CDEBrowser/
 
*** US National Cancer Institute: https://cdebrowser.nci.nih.gov/CDEBrowser/
 
*** Tolven
 
*** Tolven
 +
*** [[List of template registries]]
 
** Proper rules for transformations from different model artifacts to other artifacts, and validation of these.
 
** Proper rules for transformations from different model artifacts to other artifacts, and validation of these.
 
** Clear migration strategy, which is tested to work, before changing HL7 v3 proper to not frustrate the ongoing implementations which are now just starting to be moving ahead (Alexander)
 
** Clear migration strategy, which is tested to work, before changing HL7 v3 proper to not frustrate the ongoing implementations which are now just starting to be moving ahead (Alexander)

Revision as of 09:01, 2 June 2011

Note: Please keep the content on this page polite, and insightful. Content here is public, and also community moderated.

Triage

Please add your points as a bullet under here. Links to other pages welcome.

Wishlist items

  • Grahame: Keep it simple as can be - implementers first
  • Ann's list of 4:
    • PIIM
    • Implementer's Guides
      • What exactly does this mean? Implementer vs Implementation guide .. Rene spronk
    • greenCDA
    • simplified wire format (end-to-end greening)
  • William/Michael
  • Rene: implementers either need PIIM for MDA implementations, OR simplified wire format - with normative associated schema.
    • This is AND/OR, not XOR, correct? (Gerald)
    • Yes, AND/OR, although most implementers will choose to use one XOR the other (e.g. if the scope of the project is limited to a very few models, use a simplified wire format. If the project uses tons of models, use MDA). HL7 needs to provide implementers with both options. (Rene)
  • Gerald
    • Clear understanding and separation of interaction models
      • Documents - to stand on their own with context included within artifact
      • Messages
      • Services - context determined by service contract (and perhaps federation agreement)

Concrete next Steps

For actual things that should be done

  • ahh.... ?
  • Some ideas (Gerald)
    • Decide which approach to develop as part of this activity
      • My favorite: start with RIM as design model; develop process for creating an implementation model; describe requirements for tracing back to RIM (and/or other semantic models such as Archtypes).
    • Decide on the process for working this - HL7 project? Open participation? Collaboration with other SDO?
    • Setup a conference call/meeting and prepare time line
    • Evaluate existing (partial?) solutions