This wiki has undergone a migration to Confluence found Here

Difference between revisions of "RIMBAA 201205 Minutes Vancouver"

From HL7Wiki
Jump to navigation Jump to search
Line 5: Line 5:
  
 
==Thursday Q1==
 
==Thursday Q1==
#MongoDB / NoSQL  based implementation of FHIR (Ewout and Graham)
+
#MongoDB / NoSQL  based implementation of FHIR (Ewout and Grahame)
 
#*Ewout: Storing FHIR resources, indeed just like SMIRFs, seems like a natural fit for this kind of databases. Of course, XML databases like eXist, are an equally good match for the same reasons. Some of my SMIRF experimentation used eXist. For now, I used MongoDb because it is offered by AppHarbor (the Cloud platform I am deploying to).  
 
#*Ewout: Storing FHIR resources, indeed just like SMIRFs, seems like a natural fit for this kind of databases. Of course, XML databases like eXist, are an equally good match for the same reasons. Some of my SMIRF experimentation used eXist. For now, I used MongoDb because it is offered by AppHarbor (the Cloud platform I am deploying to).  
 
#using the FHIR data types as a persistence model for ISO data types (Grahame)
 
#using the FHIR data types as a persistence model for ISO data types (Grahame)

Revision as of 03:12, 16 May 2012

This is the RIMBAA agenda for the May 2012 WGM in Vancouver, CA

Tuesday Q6 (Tooling / RIMBAA)

  • Joint meeting with Tooling, hosted by Tooling

Thursday Q1

  1. MongoDB / NoSQL based implementation of FHIR (Ewout and Grahame)
    • Ewout: Storing FHIR resources, indeed just like SMIRFs, seems like a natural fit for this kind of databases. Of course, XML databases like eXist, are an equally good match for the same reasons. Some of my SMIRF experimentation used eXist. For now, I used MongoDb because it is offered by AppHarbor (the Cloud platform I am deploying to).
  2. using the FHIR data types as a persistence model for ISO data types (Grahame)

Minutes

Monday Q2 (RIMBAA)

  1. Administrative agenda items
    • Agenda Review/Additions/Changes
      • Plans for the week. Interesting meetings held by other WGs, e.g. FHIR
    • Approval of the minutes of the meeting in San Antonio
    • Announcements
    • Tooling liason update (Michael)
    • Update of the RIMBAA three year plan. RIMBAA was given a 'penalty point' in the WG Health stats for not updating the three year plan within the last 10 months. This serves as a reminder to review and update the current three year plan.
  2. A RIM and SNOMED based Web Service for Active Problem List (Michael Rossman ,Kaiser Permamente)
  3. CIMI and FHIR, how are they similar and dissimilar (Michael van de Zel, UMCG)
  4. The EHR functional information mapping project and relevance to RIMBAA (Stephen Hufnagel)

Monday Q3 (Tooling / RIMBAA)