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

Difference between revisions of "RIMBAA 201105 Minutes Orlando"

From HL7Wiki
Jump to navigation Jump to search
Line 22: Line 22:
 
==WED Q6 (19:00-21:00) [[Image:Technical med.gif]]==
 
==WED Q6 (19:00-21:00) [[Image:Technical med.gif]]==
 
#HL7 V3 New Look Taskforce and PIIMs
 
#HL7 V3 New Look Taskforce and PIIMs
An in person continuation of our lively online discussion of what the New Look Taskforce may mean to V3.
+
#*An in person continuation of our lively online discussion of what the Fresh Look Taskforce may mean to V3. Grahame Grieve and Lloyd McKenzie will be present. This will be after the Reception and will prove to be an interesting discussion of models, RIM and other.
Grahame Grieve and Lloyd McKenzie will be present. This will be after the Reception and will prove to be an interesting discussion of models, RIM and other.
+
#**For more information, see the [[PIIM]] wiki page; and Grahame's blog on the [http://www.healthintersections.com.au/?p=137 HL7 Fresh Look Taskforce].
 +
#*A PIIM is a PIM, a Platform Independent Implementable Model. All v3 static models are to be expressed as UML models, which makes life easy for the implementers when using [[MDA]]. All ITSs may be deprecated, and no new ones defined, HL7 should not be in de business of defining ITSs at all.  
  
 
==THU Q3 [[Image:Technical med.gif]]==
 
==THU Q3 [[Image:Technical med.gif]]==

Revision as of 08:10, 7 May 2011

Agenda for the May 2011 WGM in Orlando FL USA

Notes:

  1. Rene won't be attending this WGM.
  2. one quarter to be set aside for a joint HL7 RIMBAA & OpenEHR software implementers session.

MON Q3 Business-Icon.jpg Technical med.gif

  1. Administrative agena items
    • Approval of agenda for the week
    • Announcements
    • Approval of the minutes of the Washington meeting.
  2. dbMotion. A RIM based integration platform used on a very large scale at U of PItt, Israel and elsewhere. Practical experience making RIMBAA work on a large scale for integrating disparate hospitals and facilities.
  3. Hybrid approaches to RIMBAA (Amnon Shabo)
    • Native-XML RIMBAA for semantic warehousing with XQUERY exploration
    • Exported data marts in RDF or relational formats for analytics and optimization
    • RDF-based promotion layer facilitates the defitnion of data marts
    • Data mart schemas are user-defined and mapped to the XML warehouse and/or promotion layer

WED Q2 (hosted by I/C)

  • This quarter RIMBAA will have ajoint meeting with the Implementation/Conformance WG (who are hosting) and the Tooling WG.

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

  1. HL7 V3 New Look Taskforce and PIIMs
    • An in person continuation of our lively online discussion of what the Fresh Look Taskforce may mean to V3. Grahame Grieve and Lloyd McKenzie will be present. This will be after the Reception and will prove to be an interesting discussion of models, RIM and other.
    • A PIIM is a PIM, a Platform Independent Implementable Model. All v3 static models are to be expressed as UML models, which makes life easy for the implementers when using MDA. All ITSs may be deprecated, and no new ones defined, HL7 should not be in de business of defining ITSs at all.

THU Q3 Technical med.gif

  1. Report on v3 implementation at Intermountain (Stan Huff)
    • There is more than one way to express a clinical statement in RIM. If you are using a RIM model to trigger clinical decision support rules, how do you know if two different expressions represent the same thing? Prior to the RIM and prior to OWL, Dr Huff was faced with the problem of representing clinical events in a "normalized" way so that equivalent expressions are known to be equivalent. He will discuss the "normalized" model that he and his group developed to address this problem.
  2. Kaiser Permanente, a preliminary trial of using RIMBAA (Java SIG) to aggregate data from Epic and NHIN data sources.
    • Using MySQL and the original version of the JAVA SIG API, and also developing a Clinical Data Extraction Framework (CDEF) to extract data from Epic without having to go through Clarity (Epics relational projection), Pradeep and his group at Kaiser Permanente created a system that can capture data in real time as it is being entered into Epic, and persist it in a pure RIM database (MySQL). They have a web interface that can show the data minutes later. So far this demo project us capturing Demographic data but it will be part of a wider effort to capture all clinical data.
  3. A templated RIMBAA CDR for a Hospital Wide Continuity of Care Record (Michael van der Zel)
    • Simple CRUD CDR at UMCG, static storage is easy, the dynamic behaviour is where the fun/trouble starts, report on issues we ran into creating the CDR store. And the hybrid SQL+XML database solution applied.
    • Plus, a discussion type of presentation were he wants to point out the Research specific issues @ LifeLines/Target