RIMBAA 201001 WGM Agenda

Agenda for the January 2010 WGM in Phoenix

Monday Q3 (room: Sedona 3)

Meeting Attendance - :

At	Name	Affiliation	Email Address
	Peter Hendler	KP, US	peter@hendler.net
	Rene Spronk	Ringholm, NL	rene.spronk@ringholm.com
	Michael van der Zel	Groningen University Hospital, and Results4Care, NL	m.van.der.zel@ict.umcg.nl

• Rene chairs the meeting and calls to order at 13:45
• Approval of agenda for the week
  • MOTION: Approved by consensus
• Administrative agenda items
  • Announcements
    1. RIMBAA co-chair election (today only)
  • Approval of the minutes of the RIMBAA meeting in Amsterdam
    • MOTION by Ewout/Michael van der Zel, 19-0-6
  • Motion to organize two RIMBAA meetings in Europe in 2010 and to designate those as out-of-cycle meetings; the European meetings are to be held inbetween regular WGM meetings (e.g. June and November).
    • MOTION by Ann W/Ewout 25-0-0.
    • Ann suggests that one of them be held in the UK
    • Note that a March 11 out-of-cycle RIMBAA meeting has already been approved during the 20091027 out-of-cycle meeting.
  • Draft agenda for the Rio WGM
    • 50% of attendees (by show of hands) state that it's likely they'll be in Rio. We'll meet in Rio, the number of quarters has yet to be determined.
  • Accept/reject work item to describe best practices / approaches for GTS implementation (as suggested by Ewout)
    • Accepted in principle, although (by show of hands) the number of interested parties is low (4)
  • Accept/reject work item to ensure that the RIM covers software-user, account, user groups, things one needs in RIMBAA applications, but not in HL7 v3 interactions
    • Accepted in principle, although (by show of hands) the number of interested parties is low (3)
• RIMBAA Product presentation: Scott Parkey (Axolotl) presents an architectural/RIMBAA overview of the the Axolotl Elysium suite using examples from Axolotl's next generation MPI component
  • Would be nice to maintain full RIM-fidelity. Currently fully implement v3 patient/person classes.
  • Design decision: use DB2 pure XML database. Directly store XML files, indexes them based on a tree based representation. Query using XPath, no joins as in relation structure. Works pretty well with RIM, store XML. maintaining fidelity then easy, helps performance aspect.
  • Main reason for DB2: fidelity of data. Rene: probably makes sense esp. given that we're talking about CDA.
  • Custom HL7 v3 java Library (generated from MIF) Construct CDA fragments from java objects. CO-cell in the matrix. CP-CO-CS cells, all based on the CDA R2 R-MIM.
• RIMBAA Product presentation: Duane Bender (Mohawk College) presents an overview of the EVEREST Toolkit which is based on collapsed MIF models. The overview focuses on RIMBAA aspects of the toolkit: the architecture of the tool, MIF collapsing, code generation, and the manipulation of collapsed RIM objects in-memory.
  • Framework for building a higher level API. also used directly by application programmers. Provides a rich class experience, no need to deal with XML.
  • The current version is .net, working on a (port to) an Eclipse (Java) version. Open source released late 2009 as part of OHT.
  • CO-CS, RMIM oriented product. MIF v2 generated.
  • Build-in message conformance testing: Classes are conformance aware, when serialization is done it is an conformant instance.
  • Datatypes MIF not really sufficient, need to add custom code. hand written. Called helper functions in the Framework.
  • Didn't tie to one specific ITS or Datatypes release. Support both R1 as well as R2.
  • Working with HTB as a persistence platform. Persistence (in general) not within current shipped product.
  • Build-in message conformance testing: Classes are conformance aware, when serialization is done it is an conformant instance.
    • No support for Templates yet. Nor of OCL.
  • Datatypes MIF not really sufficient, need to add custom code. hand written. Called helper functions in the Framework.
  • Didn't tie to one specific ITS or Datatypes release. Support both R1 as well as R2.
  • Lesson learned: Preserve all information in MIF into the framework, including documentation.
  • Lesson learned: tried to only use business names, but had to switch back to pure RIM semantics. People couldn't understand the business names, no consistent use. Mixture of RIM terms and business names doesn't work. have to do either/or. Ann confirms that UK had similar experience.
  • Raised productivity 10-100x, by just having the Framework available
• MOTION to adjourn (Ewout/Peter H) at 15:00

Monday Q4 (room: Sedona 3)

• Product/Tooling demonstrations
• Virtual Medical Record WG (vMR) Presentation: (Andrew McIntyre, 30 minutes)
  • Keywords: vMR overview (see Virtual Medical Record (vMR)), use of GELLO, MIF-gelloclass-UML transforms, RIMBAA aspects of the ongoing vMR effort.
  • Andrew: I aim to demonstrate how GELLO can operate over a VMR (The one we have is a basic one, but RIM like, as in the one in the GELLO standard)
  • vMR is created by Clinical decision support. The model GELLO talks to. GELLO is a OCL variant, specialized for querying. To extract data out of an EHR.
  • vMR model based on various inputs in term of models. vMR could be the basis for services, is GELLO inspired as well. Interested in methods of classes next to their structure.
  • use a facade models (not real RIM) in GELLO to shorten path to access classes/attributes. No moodCode attribute, semantics in context. vMR expressed as a UML class diagram model. Model is 9should be) mappable to pure RIM.
  • Attempt is to express vMR as a level-2 CCD R-MIM. Not going for 100%.
  • Ann: OCL is designed to query an object model. Need to ensure that vMR is developed according to HL7 processes, and ensure mappability to RIM.
• RIMBAA Product presentation: RIMBAA Aspects of the DB2 PureXML database. Amnon Shabo (IBM) presents: "research effort developing a data warehouse (RIMon) that is based on the RIM"
  • Core aspect: BII - Biomedical Information Infrastructure, contains general purpose data warehouse. Called RIMon (RIM based XML storage); querying supported by XQuery. Created datamarts 9exports out of DB2 in ER tables) using RDF definitions.
• Received v3 instances are RIMified (mapped to generic RIM classes); allows for creation of Rimified queries for decision support. Archived instances are "RIM ITS" (an in-company own version thereof) based, with preserved clone names.
• RIMBAA in the (SA)EAF Matrix (Michael van der Zel) see RIMBAA: SAEAF vs RIMBAA
  • Michael: SEAF is based on ODP/RM. Views on a system, each view has a different focus.
• MOTION to adjourn by Ewout/Peter H at 16:50

(MnM: Tuesday Q1)

• MnM have a hot topics quarter on Context Conduction. This impacts a RIMBAA issue: See Context Conduction in RIMBAA Applications.

(Tooling: Tuesday Q6, 19:00-21:00)

• Tooling presentations (hosted by the Tooling WG)
  • Agenda: Tuesday Tooling - Jan 2010

Wednesday Q2 (room: Sedona 3)

• Topic: Model Driven Software Development (MDD)
  • MDD could be regarded as a best practice when it comes to RIMBAA application. What does it take to do fullblown model driven software development? PHI Technology effectively has accomplished MDD.
  • Sidebar question: What's missing in the HDF/the HL7 EAF in current v3 tooling - what are the things we'd need to have full support for MDD in HL7 v3?
• Project presentation: DSL and MDD (Charlie McCay)
  • Charlie has been working on Domain Specific Language work and will also present the relationship between HL7 and horizontal software industry methodologies (including MDD)

Thursday Q1 (room: Suite 1366)

• Joint meeting with the ITS WG (hosted by ITS)
  • RIM ITS and
  • New ITS, code generation and other aspects