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 24: Line 24:
 
==Thursday Q1==
 
==Thursday Q1==
 
#MongoDB / NoSQL  based implementation of FHIR (Ewout and Lloyd)
 
#MongoDB / NoSQL  based implementation of FHIR (Ewout and Lloyd)
 +
#*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 11:24, 18 April 2012

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

Note: MnM will organise educational sessions on FHIR on Sunday Q2 and Sunday Q4 (Q4 being a repeat of Q2). Those sessions are primarily aimed at the MnM facilitators, other interested parties are also welcome.

Monday Q2 (RIMBAA)

  1. Administrative agenda items
  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 Huffnagel)

Monday Q3 (Tooling / RIMBAA)

Tuesday Q6 (Tooling / RIMBAA)

  • Joint meeting with Tooling, hosted by Tooling

Thursday Q1

  1. MongoDB / NoSQL based implementation of FHIR (Ewout and Lloyd)
    • 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)