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

Difference between revisions of "RIMBAA 201201 Minutes San Antonio"

From HL7Wiki
Jump to navigation Jump to search
Line 7: Line 7:
 
#FHIR implementation topics (Ewout Kramer, Lloyd McKenzie)
 
#FHIR implementation topics (Ewout Kramer, Lloyd McKenzie)
 
#*This session will focus on some of the hot FHIR topics; notably those where feedback/discussion is desired.
 
#*This session will focus on some of the hot FHIR topics; notably those where feedback/discussion is desired.
#*Lloyd will e.g. discuss RIM mapping (of resources)
+
#*Lloyd will discuss RIM mapping of resources, Ewout will discuss implementability: where do we make things unneccessary hard? What can be better?
  
 
==THUR Q1 (Nueces, 09:00-10:30) [[Image:Technical med.gif]]==
 
==THUR Q1 (Nueces, 09:00-10:30) [[Image:Technical med.gif]]==

Revision as of 15:09, 18 January 2012

This is the RIMBAA WG agenda of the WGM (WGM #34) in San Antonio, January 2012

WED Q6 (Nueces, 19:00-21:00) Technical med.gif

  1. Announcements
  2. Tools for RIM based software development (max 15 minutes)
    • Discussion of the 'tool evaluation process' part of the above wiki page, for presentation tomorrow in the tooling meeting
  3. FHIR implementation topics (Ewout Kramer, Lloyd McKenzie)
    • This session will focus on some of the hot FHIR topics; notably those where feedback/discussion is desired.
    • Lloyd will discuss RIM mapping of resources, Ewout will discuss implementability: where do we make things unneccessary hard? What can be better?

THUR Q1 (Nueces, 09:00-10:30) Technical med.gif

  1. Announcements
    • Michael/Amnon: update on project 688 which shows RIMBAA as a co-sponsor (although we never discussed/approved this).
  2. RIMBAA Reference Implementation (max 10 minutes)
    • This topic was discussed during the last RIMBAA meeting in Amsterdam, where it was suggested we re-affirm the following statement during this meeting: "for a reference implementation we're depending on projects, we won't be building a reference implementation from scratch".
  3. Development of a terminology server with a "CTS-II Based Application Architecture"
    • The University of Applied sciences in Dortmund, Germany, in a project led by Prof. Dr. Peter Haas, has developed an open source terminology server. The internal structures, inclusive of the persistence layer, are based on an extended version of the CTS II data model. Extensions to the model were made to deal with things like licensing / access control, and multilingual support. The extended model was used to generate the CTS II service definitions as well as the database schema.
  4. RIM with Domain Driven Design (DDD) principles applied (George de la Torre)
    • George: The talk will be comprised on two main topics (1) explain how RIM works as a transactional command model while being flexible for application uses cases, and (2) FHIR proposal (previoulsy known as RFH) and how a RIMBAA could relate with implementation.
  5. Discussion to help finalize the RIM Based Persistence whitepaper.



Monday Q2

Workgroup Date/Time Location Chair/Scribe
RIMBAA WG 2012-01-16,
09:00-10:30
San Antonio, USA Chair/Scribe: Rene Spronk

Attendance

Attendance: Ewout, Joe Ketcherside joeketch@me.com, Peter H, Amnon, Bertil, Justin F, Michael vdZ, Diane G, Ann W, Rene S.

Minutes

  1. Rene calls to order at 11:05
  2. Administrative agenda items
    • Agenda Review/Additions/Changes
      • Rene: we had to move the presentation by George de la Torre, originally scheduled for this quarter, to Thursday Q1.
      • Thhe agenda for the week was approved by general consensus
    • Approval of the minutes of the Amsterdam RIMBAA Meeting (Nov.2011)
    • Announcements
      • Rene: there's a RIMBAA co-chair election this week. Please vote.
      • Peter: I'll be presenting some new features of the IHTSDO terminology toolbench in Vocab WG, Thursday Q3.
    • Tooling liason update (Michael)
      • Michael: the liason is supposed to update the respective groups with relevenat issues from the other group. I created a tools requirements page for RIMBAA (RIMBAA Tooling Liaison); other than that we have a tooling agenda item later this quarter.
    • Review of the highlights of the Amsterdam RIMBAA Meeting
      • Rene, whilst browsing the minutes of the Amsterdam meeting, mentions some of the more interesting aspects, in order to allow those who weren't present to look at certain presentations in more detail.
      • Rene: one of the interesting presentations was on Prosessium, a Tieto application.
        • Peter: did they use a SMIRF based persistence model, or is it a generic approach with full RIM support? Rene: the latter.
        • Peter: how about number of patients? Rene: it's used in production in Finland, multiple 100k patients.
      • We approved a minor change to the RIMBAA DMP
    • Review of RIMBAA in the HL7 Roadmap (http://wiki.hl7.org/index.php?title=RIMBAA_in_the_HL7_Roadmap&oldid=54653, modified to fit with the new 2012 Roadmap)
      • The changes were approved by general consensus. Ann notes that HL7 UK balloted the strategic initiatives to state that 'ease of implementation' includes the 'use of more generic tools' and 'the use of more generic skills'.
    • Review of the projects we're a (co-)sponsor of, see [1]
      • Project 688 shows us as supporting it; we have never seen the project plan nor endorsed it.
        • ACTION Michael to tal to the WG responsible for project 688 to ask for clarification as to whu RIMBAA is listed as a co-sponsor. He things in terms of subject of the project that there is no overlap with RIMBAA activities.
    • Planning of the next WGM in Gothenburg, Sweden (March 2012) and WGM in Vancouver, CA (May 2012)
  3. Tools for RIM based software development
    • Review of the wiki page in preparation of the joint meeting with Tooling next quarter
    • Criteria
      • The criteria were added to, no high-level additions.
    • Tool Categories
      • Michael suggests to create a visualisation of how the various tools fit together. Rene: like an image of the architecture of a RIMBAA application with interoperability capabilities, overlaid with where the tools are.
      • ACTION Michael: to create a visualisation of how the various software development tools fit together.
      • Suggestion to turn the list into a table, show whether tools are applicable for v3messaging, CDA, and/or RIMBAA.
      • Suggestion to create something akin to the "Comparison of X" pages on Wikipedia (For example: http://en.wikipedia.org/wiki/Comparison_of_feed_aggregators) for each tool category.
  4. Adjourned at 12:17

Monday Q3

Workgroup Date/Time Location Chair/Scribe
Tooling WG joint RIMBAA 2012-01-16,
11:00-12:30
San Antonio, USA Chair/Scribe: Tooling WG (host)

Informal Notes

  1. Tooling WG hosts a joint meeting with RIMBAA. The following are some informal notes from the meeting, the formal minutes are created/available from the Tooling WG.
  2. Tools for RIM based software development
    • Jane: OHT is also interested in such tools; originally they had such tools on their roadmap
    • Jane: HL7 prefers open source, not exclusive
    • Rene presents an overview of the Tools for RIM based software development page.
      • Jane suggests 'low cost' as a selection criterium
    • Jane presents a tooling strategy presentation by John Quinn during the San Diego meeting.
      • Ewout: "guide technology implementation" could include endorsing tools.. Rene: it could also just be about the creation of implementation guides.
      • We should avoid HL7 competing with its members in the toolspace; we have to be sensitive to commercial interests. "recognize and validate" the objective criteria, no endorsement, no certification.
      • Rene: I guess we need to define the process of evaluating the tools as one of the enxt steps
      • On Thursday we have the opportunity to present to the CTO
    • Jane presents the HL7 Tooling Challenge, this is in scope for RIMBAA