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 1: Line 1:
This is the RIMBAA agenda for the May 2012 WGM in Vancouver, CA
+
[[category:RIMBAA Minutes]]These are the RIMBAA minutes of the May 2012 WGM held in Vancouver, CA
 
 
==Tuesday Q6 (Tooling / RIMBAA)==
 
*Joint meeting with Tooling, hosted by Tooling
 
 
 
==Thursday Q1==
 
#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).
 
#using the FHIR data types as a persistence model for ISO data types (Grahame)
 
 
 
=Minutes=
 
  
 
==Monday Q2 (RIMBAA)==
 
==Monday Q2 (RIMBAA)==
 
Minutes for Monday Q2 now available at [[Media:http://www.hl7.org/documentcenter/public/wg/java/minutes/201201_RIMBAA_SanAntonio.zip
 
]]
 
 
  
 
#Administrative agenda items
 
#Administrative agenda items
Line 30: Line 16:
  
 
==Monday Q3 (Tooling / RIMBAA)==
 
==Monday Q3 (Tooling / RIMBAA)==
*Joint meeting with Tooling, hosted by Tooling
+
*Joint meeting with Tooling, hosted by Tooling. See the tooling WG for minutes.
 
*Main topic: [[Tools for RIM based software development]]
 
*Main topic: [[Tools for RIM based software development]]
  
==Thursday Q1++
+
==Tuesday Q6 (Tooling / RIMBAA)==
*All about FHIR implementations with Ewout, Grahame and Lloyd
+
*Joint meeting with Tooling, hosted by Tooling. See the tooling WG for minutes.
Minutes can be found at :
+
 
http://www.hl7.org/documentcenter/public/wg/java/minutes/RIMBAA%20THU%20Q1%20WGM%205-17-2012%20FHIR.rtf
+
==Thursday Q1==
 +
#Attendance:
 +
#*Lee Coller
 +
#*Michael Van Der Zel
 +
#*Peter Hendler
 +
#*Ewout Kramer
 +
#*David Hay
 +
#*Shimil Nizamov
 +
#*Mark tucker
 +
#*Lloyd McKenzie
 +
#*Amnon Shabo
 +
#*Justin Fyfe
 +
#*Vinayak Kulkami
 +
#*Grahame Grieve
 +
#*Phil Pochun
 +
#*Elaine Ayres
 +
#*Steve Hufnagel
 +
#*Abdul Malik Shakir
 +
#*Michael Rossman
 +
#Peter calls to order at 09:00
 +
#Implementing FHIR on MongoDb with .NET (Ewout Kramer, Furore)
 +
#*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).
 +
#*Discuss 4 uses of FHIR.  SMIRF based message receiver, a PHR, Just messages in to a DB, for research as a way to take input from all sources and normalizing them into a Vender Neutral Archive.
 +
#**This reference implementation is the FHIR directly using REST and just put it into storage directly with no changes.  Uses Fidler to get things into the service and just Browser Queries for queries.
 +
#**JSON/XML comes in and gets parsed by parsers already part of the release. Then tern  them into POCO/POJO and then to Storage.  Or even simpler just directly store the JSON/XML
 +
#**In this example no ORM as MongoDb is not Relational.
 +
#**It's easier to manipulate XML then to manipulate JSON, so he did manipulations in XML but then had to store it in the Mongo in JSON. One problem was the reliable round trip from XML to JSON.
 +
#**You have to add special characters to the JSON to represent meta data (Like which data types are arrays). Shows side by side examples of XML resources and JSON.
 +
#**No XML attributes in FHIR and no complex types. Show basic code of MongoDB how to store a new object. How to build in memory BSON documents and store in MongoDb.
 +
#** Json → XML → BSON → JSON
 +
#**RESTful services list of functions for Instance and Manager.
 +
#**How the Query URLs work http://server/path/patients
 +
#**Meta data VersionID, LastModified and MasterLocation is in HTTP header.
 +
#**Aggregations are all done with ATOM feeds but... you can actually have the resources contained within the ATOM feed itself.  The ATOM feed is a bit like a header for the document and does not mean that the resources are only references but can be internal references.
 +
#**Stores multiple versions of each resource, Author, Creation date, and Record State.
 +
#**The in memory object has methods.
 +
#**No true transactions in Mongo so must use “FindAndModifyIdQuery” which is an atomic operation.
 +
#*Brewer's CP theorem. (Consistency, Availability, Partition tolerance) CAP you can pick any two. But not all 3.
 +
#*Use Fidler to update to he server on http://fhir.apphb.com/fhir/
 +
#FHIR Implementation in Delphi (Grahame Grieve)
 +
#*Very different implementation build in Delphi. Added FHIR to his pre existing Delphi interface engine.
 +
#**Grahame's in on Amazon Cloud server.
 +
#**Published reference implementations, Object models with JSON serializers and parsers.
 +
Want's to add Objective C. Current reference implementations do not do persistence yet, but may add a MongoDb one.
 +
#**Convert incoming into the object model.  Uses in transactional DB SQL server. The resource is stored as a Blob but it is pre indexed for searching.
 +
#**Shows a JavaScript that can covert an HL7 V2 message into a JSON resource.
 +
#**Complex to reconcile V2 PID with Restful resource Ids. FHIR resource mapping to RIM graph. Difference between definitional mapping and implementable mapping.
 +
#*Lloyd goes over the RIM mapping of LabReport. Somewhat complex Xpath like syntax to describe the mappings. Mentioned someone from OMG may be working on an official syntax to specify implementable RIM mappings.
 +
#Peter adjournes the meeting at 10:30
 +
#After the meeting was adjourned Grahame and Peter invoked the FHIR spirits with dueling Didgeridoos.

Revision as of 13:05, 11 July 2012

These are the RIMBAA minutes of the May 2012 WGM held in Vancouver, CA

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)Example.jpg

Monday Q3 (Tooling / RIMBAA)

Tuesday Q6 (Tooling / RIMBAA)

  • Joint meeting with Tooling, hosted by Tooling. See the tooling WG for minutes.

Thursday Q1

  1. Attendance:
    • Lee Coller
    • Michael Van Der Zel
    • Peter Hendler
    • Ewout Kramer
    • David Hay
    • Shimil Nizamov
    • Mark tucker
    • Lloyd McKenzie
    • Amnon Shabo
    • Justin Fyfe
    • Vinayak Kulkami
    • Grahame Grieve
    • Phil Pochun
    • Elaine Ayres
    • Steve Hufnagel
    • Abdul Malik Shakir
    • Michael Rossman
  2. Peter calls to order at 09:00
  3. Implementing FHIR on MongoDb with .NET (Ewout Kramer, Furore)
    • 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).
    • Discuss 4 uses of FHIR. SMIRF based message receiver, a PHR, Just messages in to a DB, for research as a way to take input from all sources and normalizing them into a Vender Neutral Archive.
      • This reference implementation is the FHIR directly using REST and just put it into storage directly with no changes. Uses Fidler to get things into the service and just Browser Queries for queries.
      • JSON/XML comes in and gets parsed by parsers already part of the release. Then tern them into POCO/POJO and then to Storage. Or even simpler just directly store the JSON/XML
      • In this example no ORM as MongoDb is not Relational.
      • It's easier to manipulate XML then to manipulate JSON, so he did manipulations in XML but then had to store it in the Mongo in JSON. One problem was the reliable round trip from XML to JSON.
      • You have to add special characters to the JSON to represent meta data (Like which data types are arrays). Shows side by side examples of XML resources and JSON.
      • No XML attributes in FHIR and no complex types. Show basic code of MongoDB how to store a new object. How to build in memory BSON documents and store in MongoDb.
      • Json → XML → BSON → JSON
      • RESTful services list of functions for Instance and Manager.
      • How the Query URLs work http://server/path/patients
      • Meta data VersionID, LastModified and MasterLocation is in HTTP header.
      • Aggregations are all done with ATOM feeds but... you can actually have the resources contained within the ATOM feed itself. The ATOM feed is a bit like a header for the document and does not mean that the resources are only references but can be internal references.
      • Stores multiple versions of each resource, Author, Creation date, and Record State.
      • The in memory object has methods.
      • No true transactions in Mongo so must use “FindAndModifyIdQuery” which is an atomic operation.
    • Brewer's CP theorem. (Consistency, Availability, Partition tolerance) CAP you can pick any two. But not all 3.
    • Use Fidler to update to he server on http://fhir.apphb.com/fhir/
  4. FHIR Implementation in Delphi (Grahame Grieve)
    • Very different implementation build in Delphi. Added FHIR to his pre existing Delphi interface engine.
      • Grahame's in on Amazon Cloud server.
      • Published reference implementations, Object models with JSON serializers and parsers.

Want's to add Objective C. Current reference implementations do not do persistence yet, but may add a MongoDb one.

      • Convert incoming into the object model. Uses in transactional DB SQL server. The resource is stored as a Blob but it is pre indexed for searching.
      • Shows a JavaScript that can covert an HL7 V2 message into a JSON resource.
      • Complex to reconcile V2 PID with Restful resource Ids. FHIR resource mapping to RIM graph. Difference between definitional mapping and implementable mapping.
    • Lloyd goes over the RIM mapping of LabReport. Somewhat complex Xpath like syntax to describe the mappings. Mentioned someone from OMG may be working on an official syntax to specify implementable RIM mappings.
  1. Peter adjournes the meeting at 10:30
  2. After the meeting was adjourned Grahame and Peter invoked the FHIR spirits with dueling Didgeridoos.