RIMBAA 201005 Minutes

Monday Q1 (Queluz III, 09:00-10:30)

• Approval of agenda for the week (5 minutes)
• Administrative agenda items (max 30 minutes)
  • Announcements
    • Upcoming RIMBAA meetings: September 15 and 16 - Rome, Italy; WGM in Cambridge in October, and November 4 - London UK.
    • Rene: I've been asked to write a "HL7 version 3 Implementation" book, see [1].
    • The co-chair position currently held by Peter Hendler is up for election this meeting. Peter forgot to ask HQ to put his name on the ballot form, he is however up for re-election. At this time no other candidates have come forward for this co-chair position. This is now effectively a write-in election, please vote and write the name of a candidate on the ballot form.
  • Approval of the minutes of the Out-of-cycle meeting on March 11 in Amsterdam, the minutes/attachments are available at http://www.hl7.org/library/committees/java/minutes/20100311_RIMBAA_minutes_attachments.zip (5 minutes)
  • Review Draft agenda for the September meeting in Rome and the Cambridge WGM.
  • Discussion related to the creation of a third RIMBAA co-chair position.
    • Amnon Shabo (IBM) has volunteered to fill such a position as an appointed ad-interim co-chair, with elections to be held at the next WGM in Cambridge.
  • Create/update RIMBAA DMP, latest template at [2]
  • Review/update RIMBAA mission&scope statement, currently [3]. A wiki version which can be edited to create an updated version: RIMBAA Mission and Charter.
    • Notably to see how we should/could add the S-column to the scope. From the minutes of the meeting in Amsterdam: Andrea: the current scope of RIMBAA is (officially) limited to the P* and O* columns of the technology matrix (i.e. the use of RIM based models within the application) - interoperability is out of scope. Rene: effectively S* column is within scope, but by focusing on those v3 implementations that use RIM based models internally (O and P), we're focusing on the most advanced, largest and complex implementations of v3. It'll be easier to learn the best practices from such implementations, than from implementations that solely want to use RIM-based models in the context of interoperability. Typically those applications use DOM/SAX/XPath and other classic XML techniques – there’s not a lot we could learn from them that’s not covered by the larger implementations as well. We could declare S* to be in scope, but with the added remark that it will not be the primary focus of RIMBAA.
  • Review/update RIMBAA Action Items.
  • IP of our work products - HL7 IP or Creative Commons?
    • Discussion of pros and cons
• Updates from the recent RIMBAA meeting in Amsterdam (max 20 minutes):
  • Context Conduction (see [4])
  • MIF meta model browser (see [5])
• SAIF vs RIMBAA - update (Michael van der Zel) I won't be in Rio :-(.
• Work on the deliverable(s)
  • ORM best practices , original aim was to finalize this during this WGM
    • Andrea: have asked a student to write a paper on this topic, using a stepwise approach as once documented by AMS for the full RIM model
  • Review code generation related RIMBAA issues
    1. Schema based code generation
    2. MIF based code generation
  • Discuss Object nets and object trees
  • Context Conduction in RIMBAA Applications

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

• Work on the deliverable(s)
  • Grahame Grieve, to lead a discussion on RIM ITS implementation experiences
    • See also: http://www.ringholm.de/persist/20100311_RIMBAA_RIM_ITS_overview.pptx (presented during the March out-of-cycle meeting held in Amsterdam)
  • Presentations/discussion related to data type / RIMBAA issues:
    1. Grahame Grieve: Using R2 data types in your object model, and R1 data types on the wire. The differences will be explored - with Eclipse parser examples. Grahame: I convert between the forms in my parser and base all the other code off the proper object model R2 represents. You can also substitute R2 for R1 on the wire if you control both ends. It's a fairly simple change to do it minimally, all you need is a mapping schema that aliases BN to BL, CE and CV to CD (an up to date list is at RIM_ITS_Specification#Appendix_.231)
    2. Cecil Lynch: CD datatype implementation in a RIM based backend database used at MD Anderson Cancer Center.
    3. Some data type specific issues will be addressed, e.g. software implementation of GTS
• Project Presentation, Maqbool Hussain
  • These are more technical variants of presentations held during the IHIC conference.
  • Subject is the (automatic) mapping of legacy/proprietary ER database schema to in-memory RIM(RMIM)-based objects (and vice versa). Using technology matrix terms: the AP-CO transition - Mapping AP (legacy ER databases) to CO (in memory R-MIM based RIM objects)
  • We have only seen Robert Worden's mapping tool which can also be used for this transition. The approach taken here is a different one and tries to automate the mapping process in different ways.
  • These papers were presented during IHIC this week, which you could choose to read prior to the meeting Tuesday Q6 (or if you're not in Rio: to send questions to the RIMBAA e-mail list to be answered by the presenters). See www.ringholm.de/persist/20100514_IHIC_mapping_RIM_db_schema.pdf and www.ringholm.de/persist/20100515_IHIC_Interactive_Mapping_Tool.pdf

Wednesday Q4 (Queluz III, 15:30-17:00)

• Product/Tooling demonstrations
• Cecil Lynch (Ontoreason LLC) on a RIMBAA implementation
  • Experience at MD Anderson Cancer Center in building a RIM based backend and an application to transformed their "structured documents" from their EMR into CDA and the transform to the backend RIM model.
    • It is based on an OWL ontology of the CDA model so that we can bind terminology to the CDA attributes using the inferencing from OWL. Expressing the v3 RIM in OWL. Cecil's company is fully based on OWL and RIM based artifacts and they have built the US CDC National Surveillance for Tuberculosis fully in OWL. That system has been in full production across the entire US since April of last year with no downtime and no errors.
      • For OWL newbies: see the Pizza example in this tutorial PDF. That little exercise goes through all the aspects of OWL introducing them one at a time. Use an online OWl browser for the Pizza example OR: download the Protege software, and download the pizza.owl ontology tutorial.
    • Cecil will also talk about the 'table per class or per hierarchy' discussion, he feels it is the is the wrong approach. You really need to think about relational theory and the cost of joins. I don't think the issue of performance is really debatable with so much literature addressing it from Codd and others. This is partly why triple stores tend to outperform relational equivalents.
• Work on the deliverable(s) - continued from Monday Q1
  • Review code generation related RIMBAA issues
    1. Schema based code generation
    2. MIF based code generation
  • Discuss Object nets and object trees
  • Context Conduction in RIMBAA Applications