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

RIMBAA 201201 Minutes San Antonio

From HL7Wiki
Jump to navigation Jump to search

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

MON Q2 (11:00-12:30) Business-Icon.jpg Technical med.gif

  1. Administrative agenda items
  2. THEME: implementation aspects of terminology
  3. 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.

MON Q3 (13:45-15:00) RIMBAA joint with Tooling Business-Icon.jpg Technical med.gif

  1. Tooling WG hosts a joint meeting with RIMBAA
  2. Implementation-tools
    • to discuss. Standardized resources to be incorporated into software as APIs are being discussed in MnM from Grahame’s FHIR.
    • to discuss how RIMBAA uses the datatypes reference.

TUE Q6 (19:00-21:00) MnM

  1. MnM (without formal involvement of RIMBAA)
    • MnM to host a 2-hour "informational session"/"roadshow" related to the topic of FHIR ("Fire", previously known as RFH). This is a "FHIR 101" session.

WED Q0 (07:00-08:00) Education

  1. This is a free "RIMBAA Overview" presentation. It covers the various RIMBAA architectural principles; focusing on the use of the RIM other than for the purposes of interoperability.

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

  1. RIMBAA meeting
    • No entry-level FHIR content this quarter, given the Tuesday Q6 session
  2. 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.

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

  1. RIMBAA meeting