Difference between revisions of "RIMBAA 201005 Minutes"

Revision as of 15:28, 5 February 2010

Agenda for the May 2010 WGM in Rio de Janeiro

Approval of agenda for the week (5 minutes)
Administrative agenda items
- Announcements
  - Upcoming RIMBAA meetings: September 7(?) - Amsterdam; WGM in Cambridge in October; November 4(?) - London UK.
- Approval of the minutes of the Out-of-cycle meeting on March 11 in Amsterdam (5 minutes)
- Draft agenda for the September meeting in Amsterdam and the Cambridge WGM.
RIMBAA Product presentation:
- TBD
Work on the deliverable(s)
- 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

Product/Tooling demonstrations
- TBD
Work on the deliverable(s)
- Grahame Grieve, to lead a discussion on RIM ITS implementation experiences
- Grahame Grieve, presentation/discussion related to data type / RIMBAA issues:
  1. 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. Some data type specific issues will be addressed, e.g. software implementation of GTS

Product/Tooling demonstrations
Cecil Lynch (Ontoreason LLC) on OWL based 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.
Work on the deliverable(s)

@@ Line 23: / Line 23: @@
 **Grahame Grieve, to lead a discussion on [[RIM ITS]] implementation experiences
 **Grahame Grieve, presentation/discussion related to data type / RIMBAA issues:
-**#Using R2 data types in your object model, and R1 data types on the wire. The differences will be explored - with Eclipse parser examples.
+**#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]])
 **#Some data type specific issues will be addressed, e.g. [[GTS implementation guidance|software implementation of GTS]]