This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "RIMBAA 200909 WGM Minutes"

From HL7Wiki
Jump to navigation Jump to search
Line 1: Line 1:
==Monday Q4 [[Image:Business-Icon.jpg]] [[Image:Technical med.gif]]==
+
==Agenda of Tuesday Q4 [[Image:Technical med.gif]]==
'''Meeting Room: Georgia 7'''
 
*Approval of agenda for the week (5 minutes)
 
*Approval of the minutes of the January 2009 WGM [[RIMBAA_200901_WGM_Minutes]]. The WG didn't meet in Kyoto. (5 minutes)
 
*Gunther Schadow has resigned as a RIMBAA co-chair.
 
**Motion to appoint an interim co-chair.
 
*Review and approve [[RIMBAA SWOT]] (max. 15 minutes)
 
*Review [[RIMBAA in the HL7 Roadmap]] (max. 10 minutes)
 
*Actions resulting from [http://gforge.hl7.org/gf/download/frsrelease/509/6471/FTSD-WorkGroupHealth2009Sept.pdf Work Group Health]
 
*Announcement of European meeting, see [http://hl7book.net/index.php?title=RIMBAA-Europe_Agenda_8 Agenda for Amsterdam RIMBAA meeting Oct. 27th]
 
**Motion to designate the Oct. 27th meeting in Amsterdam as an out-of-cycle meeting of the RIMBAA WG.
 
*Agree upon the future goals of the RIMBAA WG: (discussion, max. 20 minutes)
 
*#Marketing - Public exposure of successes (of v3 implementability and the RIM itself)
 
*#Sharing of experiences and solutions
 
*#*Document/describe (for all possible cell transitions) how those steps could be supported/achieved.
 
*#*We focus on Patterns for Application Development. Guidance, no normative outcomes.
 
*#*Reference Implementation (Java SIG materials, extend OHT?)
 
*#*Outreach to RIMBAA implementers (especially those not present at RIMBAA meetings); publish reviews of existing RIMBAA implementations
 
*#Education - for newbies to RIMBAA
 
*#Standard Improvement
 
*#*Identify issues in HL7 standards during the implementation process
 
*#*Work with ITS WG on an RS XML ITS and the identification of CS-RS transition issues
 
*#*Identify issues caused by the ‘interoperability mindset’ of the RIM
 
*#*V3 constructs: Context Conduction, Update Mode, Object Versioning
 
*#*Work on SAEAF [[Platform-Specific_-_Engineering]]
 
*Define the scope of the delivarable (max. 20  minutes)
 
**Something that can be published as part of the v3 standard. "Guidelines for RIMBAA implementations" (?). Discussion of table of contents; timeline ([[RIMBAA three year plan]]).
 
* Work on a RIMBAA slide deck (time permitting)
 
** (use the [http://www.ringholm.de/download/20090407_rimbaa_overview.pptx this file] as a starter?). Note: "Save As" .pptx, not as a .zip.
 
 
 
==Tuesday Q4 [[Image:Technical med.gif]]==
 
 
'''Meeting Room: Atlanta 1'''
 
'''Meeting Room: Atlanta 1'''
 
*'''Processing/validating RIM Based Models.''' (max. 45 minutes) One of the main problems to tackle, whether for messaging/documents or in memory objects structures in RIMBAA, is the testing of validity of constraint models, which includes evrything from a CIM, a LIM or a DCM, with GELLO/OCL. In a RIMBAA environment one would normally do code generation from the MIF/EMF to tackle this.
 
*'''Processing/validating RIM Based Models.''' (max. 45 minutes) One of the main problems to tackle, whether for messaging/documents or in memory objects structures in RIMBAA, is the testing of validity of constraint models, which includes evrything from a CIM, a LIM or a DCM, with GELLO/OCL. In a RIMBAA environment one would normally do code generation from the MIF/EMF to tackle this.
Line 48: Line 18:
 
**With a slot for a presentation on RIMBAA tooling (no opportunity for discussions)
 
**With a slot for a presentation on RIMBAA tooling (no opportunity for discussions)
 
**ItalTBS (Andrea Ceiner et.al.) will present new features of their toolkit
 
**ItalTBS (Andrea Ceiner et.al.) will present new features of their toolkit
 +
 +
==Minutes of Monday Q4 [[Image:Business-Icon.jpg]] [[Image:Technical med.gif]]==
 +
*Attendees:
 +
**Peter Hendler, KP
 +
**Amnon Shabo, IBM research
 +
**Davide Magni, ITAL TBS
 +
**Andy Stechishin, GPi
 +
**Luigi Sison, VA
 +
**Andrea Ceiner, ITAL TBS
 +
**Vassil Peytchev, Epic
 +
**Rene Spronk, Ringholm
 +
*Peter Hendler calls to order at 15:40
 +
*Motion to approve the agenda for the week (Andy/Rene, 7-0-0)
 +
*Motion to approve the minutes of the January 2009 WGM [[RIMBAA_200901_WGM_Minutes]]. The WG didn't meet in Kyoto. (Rene/Amnon, 7-0-0)
 +
*Gunther Schadow has resigned as a RIMBAA co-chair.
 +
**Motion to appoint Rene as an interim RIMBAA co-chair (Andy/Amnon, 7-0-0).
 +
*''Peter hands the gavel to Rene''
 +
*''Luigi leaves the meeting''
 +
*Action item for Rene: inform HL7 HQ of the new interim co-chair.
 +
*Review and approve [[RIMBAA SWOT]]. Motion to approve the SWOT (Andy/Peter, 6-0-0)
 +
*Review [[RIMBAA in the HL7 Roadmap]]
 +
*Review the [http://gforge.hl7.org/gf/download/frsrelease/509/6471/FTSD-WorkGroupHealth2009Sept.pdf Work Group Health] sheet created by the steering division
 +
**Action item for Rene: ask Wilfried (HL7 HQ) to create a project in HL7 Gforge that references the existing Java SIG repository.
 +
*Announcement of European meeting, see [http://hl7book.net/index.php?title=RIMBAA-Europe_Agenda_8 Agenda for Amsterdam RIMBAA meeting Oct. 27th]
 +
**Motion to designate the Oct. 27th meeting in Amsterdam as an out-of-cycle meeting of the RIMBAA WG (Andy/Peter, 6-0-0).
 +
**Action item for Rene: notify HL7 HQ of this decision.
 +
*Agree upon the future goals of the RIMBAA WG: (discussion, max. 20 minutes)
 +
*#Marketing - Public exposure of successes (of v3 implementability and the RIM itself)
 +
*#Sharing of experiences and solutions
 +
*#*Document/describe (for all possible cell transitions) how those steps could be supported/achieved.
 +
*#*We focus on Patterns for Application Development. Guidance, no normative outcomes.
 +
*#*Reference Implementation (Java SIG materials, extend OHT?)
 +
*#*Outreach to RIMBAA implementers (especially those not present at RIMBAA meetings); publish reviews of existing RIMBAA implementations
 +
*#Education - for newbies to RIMBAA
 +
*#Standard Improvement
 +
*#*Identify issues in HL7 standards during the implementation process
 +
*#*Work with ITS WG on an RS XML ITS and the identification of CS-RS transition issues
 +
*#*Identify issues caused by the ‘interoperability mindset’ of the RIM
 +
*#*V3 constructs: Context Conduction, Update Mode, Object Versioning
 +
*#*Work on SAEAF
 +
*Discussion of the RIMBAA delivarables. Motion to approve the following two projects (Andy/Peter, 6-0-0)
 +
*#A set of harmonized whitepapers that detail the things one needs to be aware about when creating a RIMBAA implementation. Initial whitepaper: "ORM Approaches".
 +
*#Reference Implementation(s). Documentation of the reference implementation and the design process associated with these applications.
 +
*Action item for Peter/Rene: create project statements for these projects and bring those to the steering division for approval.
 +
*Adjournement by Rene at 17:07

Revision as of 21:59, 21 September 2009

Agenda of Tuesday Q4 Technical med.gif

Meeting Room: Atlanta 1

  • Processing/validating RIM Based Models. (max. 45 minutes) One of the main problems to tackle, whether for messaging/documents or in memory objects structures in RIMBAA, is the testing of validity of constraint models, which includes evrything from a CIM, a LIM or a DCM, with GELLO/OCL. In a RIMBAA environment one would normally do code generation from the MIF/EMF to tackle this.
    • Presentation of an EMF driven Template/OCL code generator by Dave Carlson and John Timm (IBM Research)
      • The tool has the prime intent to facilitate the use of CDA templates. It is part of the OHT efforts on the Eclipse platform. Focus of the RIMBAA presentation will be on the code generation aspect.
      • It will show the use of EMF code generation with OCL constraints, from UML models. Although the example models are CDA restrictions, most of the principles should apply to RIM restriction also. They are very interested in generalizing their approach for RIM and v3 messages, and also for DCM.
      • A longer presentation of the tool will be held in a meeting of the Structured Documents WG on Monday Q3, and the Tooling WG during Tuesday Q2.
  • Mapping data in legacy databases to RIM Based Models (max. 45 minutes). Given the amount of legacy databases a way has to be found to encapsulate those datbases in a layer which provides the programmer with a virtual RIM based API - inclusive of object based querying using RIM terms.
    • Presentation by Robert Worden about a semantic mapping tool he's been working on. Focus of the presentation will be om the mapping between legacy ER databases and RIM Based models.
      • The tool is primarily oriented towards message mappings (the AO-CS, and AO-CP and AS-CO cell-transitions in the technology matrix); it can however also be used to map legacy database structures to RIM based models (AP to CO/RO mapping).
  • RIMBAA Issues/talking points
  • Discuss impact of proposed RIM changes to RIMBAA, e.g. negationInd, datatypes R2

Tuesday Q6 (19:00-21:00) Technical med.gif

  • Tooling demonstration (hosted by the tooling committee)
    • With a slot for a presentation on RIMBAA tooling (no opportunity for discussions)
    • ItalTBS (Andrea Ceiner et.al.) will present new features of their toolkit

Minutes of Monday Q4 Business-Icon.jpg Technical med.gif

  • Attendees:
    • Peter Hendler, KP
    • Amnon Shabo, IBM research
    • Davide Magni, ITAL TBS
    • Andy Stechishin, GPi
    • Luigi Sison, VA
    • Andrea Ceiner, ITAL TBS
    • Vassil Peytchev, Epic
    • Rene Spronk, Ringholm
  • Peter Hendler calls to order at 15:40
  • Motion to approve the agenda for the week (Andy/Rene, 7-0-0)
  • Motion to approve the minutes of the January 2009 WGM RIMBAA_200901_WGM_Minutes. The WG didn't meet in Kyoto. (Rene/Amnon, 7-0-0)
  • Gunther Schadow has resigned as a RIMBAA co-chair.
    • Motion to appoint Rene as an interim RIMBAA co-chair (Andy/Amnon, 7-0-0).
  • Peter hands the gavel to Rene
  • Luigi leaves the meeting
  • Action item for Rene: inform HL7 HQ of the new interim co-chair.
  • Review and approve RIMBAA SWOT. Motion to approve the SWOT (Andy/Peter, 6-0-0)
  • Review RIMBAA in the HL7 Roadmap
  • Review the Work Group Health sheet created by the steering division
    • Action item for Rene: ask Wilfried (HL7 HQ) to create a project in HL7 Gforge that references the existing Java SIG repository.
  • Announcement of European meeting, see Agenda for Amsterdam RIMBAA meeting Oct. 27th
    • Motion to designate the Oct. 27th meeting in Amsterdam as an out-of-cycle meeting of the RIMBAA WG (Andy/Peter, 6-0-0).
    • Action item for Rene: notify HL7 HQ of this decision.
  • Agree upon the future goals of the RIMBAA WG: (discussion, max. 20 minutes)
    1. Marketing - Public exposure of successes (of v3 implementability and the RIM itself)
    2. Sharing of experiences and solutions
      • Document/describe (for all possible cell transitions) how those steps could be supported/achieved.
      • We focus on Patterns for Application Development. Guidance, no normative outcomes.
      • Reference Implementation (Java SIG materials, extend OHT?)
      • Outreach to RIMBAA implementers (especially those not present at RIMBAA meetings); publish reviews of existing RIMBAA implementations
    3. Education - for newbies to RIMBAA
    4. Standard Improvement
      • Identify issues in HL7 standards during the implementation process
      • Work with ITS WG on an RS XML ITS and the identification of CS-RS transition issues
      • Identify issues caused by the ‘interoperability mindset’ of the RIM
      • V3 constructs: Context Conduction, Update Mode, Object Versioning
      • Work on SAEAF
  • Discussion of the RIMBAA delivarables. Motion to approve the following two projects (Andy/Peter, 6-0-0)
    1. A set of harmonized whitepapers that detail the things one needs to be aware about when creating a RIMBAA implementation. Initial whitepaper: "ORM Approaches".
    2. Reference Implementation(s). Documentation of the reference implementation and the design process associated with these applications.
  • Action item for Peter/Rene: create project statements for these projects and bring those to the steering division for approval.
  • Adjournement by Rene at 17:07