Difference between revisions of "AID 201406 Agenda"

From HL7Wiki
Jump to navigation Jump to search
 
Line 1: Line 1:
These are the minutes of the [[AID]] out-of-cycle meeting held in Amsterdam, the Netherlands, on June 3rd 2014.
+
[[category:RIMBAA Minutes]]These are the minutes of the [[AID]] out-of-cycle meeting held in Amsterdam, the Netherlands, on June 3rd 2014.
  
==Attendance==
+
Summary: this meeting ended up being focused on OpenEHR implementations - and how one can implement IHE/HL7 interfaces on top of an OpenEHR based CDR.
 +
 
 +
==Amsterdam AID Minutes==
 +
{| border="1" cellpadding="2" cellspacing="0" style="background:#f0f0f0;" width="100%"
 +
|-
 +
!width=”35%”|Workgroup
 +
!width="20%"| Date/Time
 +
!width="15%"| Location
 +
!width="30%"| Chair/Scribe
 +
|-
 +
|'''AID HL7 User Group'''||2014-06-03, <br/>09:00-16:30||Amsterdam, NL||Chair/Scribe: Rene Spronk
 +
|}
 +
==Attendees==
 
#Rene Spronk, Ringholm, NL
 
#Rene Spronk, Ringholm, NL
 
#Ewout Kramer, Furore, NL
 
#Ewout Kramer, Furore, NL
Line 21: Line 33:
 
#***No objections were raised.
 
#***No objections were raised.
 
#*Aproval of the agenda
 
#*Aproval of the agenda
#*MOTION To approve the minutes of the [[AID 201401 Agenda|San Antonio January 2014 WGM]]
+
#*'''MOTION''' To approve the minutes of the [[AID 201401 Agenda|San Antonio January 2014 WGM]]
 
#**Approved 10-0-2(y-n-a, Ewout/Alexander)
 
#**Approved 10-0-2(y-n-a, Ewout/Alexander)
#*MOTION To approve the minutes of the [[AID 20140504 Agenda|Phoenix May 2014 WGM]]
+
#*'''MOTION''' To approve the minutes of the [[AID 20140504 Agenda|Phoenix May 2014 WGM]]
 
#**Approved 10-0-2(y-n-a, Ewout/Alexander)
 
#**Approved 10-0-2(y-n-a, Ewout/Alexander)
 
#*User Groups
 
#*User Groups
Line 32: Line 44:
 
#***Ewout: I have an intrinsic motivation to 'share', having the shared information behind some 'membership only wall' doesn't motivate me to share.
 
#***Ewout: I have an intrinsic motivation to 'share', having the shared information behind some 'membership only wall' doesn't motivate me to share.
 
#*Review/update [[AID Activities]]
 
#*Review/update [[AID Activities]]
#**Discussion deferred until later in the agenda.
+
#**Dropped due to a lack of time
 
#Implementation aspects of my own PHR (Dirk Jan van der Pol, [http://www.quli.nl Quli], NL)  
 
#Implementation aspects of my own PHR (Dirk Jan van der Pol, [http://www.quli.nl Quli], NL)  
 
#*Dirk Jan had to cancel his talk due to illness.
 
#*Dirk Jan had to cancel his talk due to illness.
#FHIR and DICOM (Ewout Kramer, Furore)
+
#FHIR and DICOM (Ewout Kramer, Furore, see [http://www.hl7.org/documentcenter/public/wg/java/20140603_Ewout_Kramer_WADO_AND_FHIR.PPTX http://www.hl7.org/documentcenter/public/wg/java/20140603_Ewout_Kramer_WADO_AND_FHIR.PPTX] for slides, and the video at [https://vimeo.com/97308387 https://vimeo.com/97308387])
 
#*Ewout took part in the SIIM hackathon, a diagnostic imaging hacking event. He will briefly present his experiences in blending RESTful DICOM approaches with FHIR.
 
#*Ewout took part in the SIIM hackathon, a diagnostic imaging hacking event. He will briefly present his experiences in blending RESTful DICOM approaches with FHIR.
 
#**Ewout had no knowledge of DICOM prior to SIIM. The FHIR resource combines study/series/instance data, whereas QIDO/WADO-RS deals with those individually. Smaller issues reletaed to data types.  
 
#**Ewout had no knowledge of DICOM prior to SIIM. The FHIR resource combines study/series/instance data, whereas QIDO/WADO-RS deals with those individually. Smaller issues reletaed to data types.  
 
#**First time that Ewout was in contact with respresentatives from imaging companies, FHIR resourse dev in close cooperation, they'll visit HL7 connectathons as well.  
 
#**First time that Ewout was in contact with respresentatives from imaging companies, FHIR resourse dev in close cooperation, they'll visit HL7 connectathons as well.  
 
#**Discussion around getting more DICOM implementers to the join these meetings? Good idea.
 
#**Discussion around getting more DICOM implementers to the join these meetings? Good idea.
#An OpenEHR RESTful Archetyped API (Jan-Marc Verlinden, [http://www.medvision360.com/ Medvision360], NL) (max 40 minutes)
+
#An OpenEHR RESTful Archetyped API (Jan-Marc Verlinden, [http://www.medvision360.com/ Medvision360], NL)  
 
#*Jan-Marc and Ralph are working on a RESTful API (see http://www.medrecord.nl/medrecord-json-api/) for MEDRecord, an open source OpenEHR based application. They will show how the API is related to the back end EHR, as well as how one could create a FHIR frontend on top of this API.
 
#*Jan-Marc and Ralph are working on a RESTful API (see http://www.medrecord.nl/medrecord-json-api/) for MEDRecord, an open source OpenEHR based application. They will show how the API is related to the back end EHR, as well as how one could create a FHIR frontend on top of this API.
 
#*(side note) Developed PAAS for dicom data, we found its impossible to store that mass amount of data, found non-fiber netweroks uncable for cloud storage of the data. Project at Univ. of Utrecht, used project hackathon to push the project forward. Show combined medical images (MRI and 24 channel EEG) in 3D. Philips MRI fMRI. DICOM + Philips DICOM. Two vendors related to image processing and viewing.  
 
#*(side note) Developed PAAS for dicom data, we found its impossible to store that mass amount of data, found non-fiber netweroks uncable for cloud storage of the data. Project at Univ. of Utrecht, used project hackathon to push the project forward. Show combined medical images (MRI and 24 channel EEG) in 3D. Philips MRI fMRI. DICOM + Philips DICOM. Two vendors related to image processing and viewing.  
Line 50: Line 62:
 
#*Jan-Marc: in OpenEHR, split between communications model and knowledge system, shows HL7 VMR model (for decision support) mapping.  
 
#*Jan-Marc: in OpenEHR, split between communications model and knowledge system, shows HL7 VMR model (for decision support) mapping.  
 
#*Jan-Marc: no problem creating a FHIR interface. Would need mappings. Ian: it's actually not that hard. Not a surprise that they are similar.  
 
#*Jan-Marc: no problem creating a FHIR interface. Would need mappings. Ian: it's actually not that hard. Not a surprise that they are similar.  
#Teach yourself (some) FHIR (Fleur Kelpin, [http://www.umcg.nl/ UMCG], NL)  
+
#Teach yourself (some) FHIR (Fleur Kelpin, [http://www.umcg.nl/ UMCG], NL, see [http://www.hl7.org/documentcenter/public/wg/java/20140603_Fleur_Kelpin_Teach%20yourself%20(some)%20FHIR.pdf http://www.hl7.org/documentcenter/public/wg/java/20140603_Fleur_Kelpin_Teach%20yourself%20(some)%20FHIR.pdf] for slides)  
 
#*Fleur and her team have implemented a FHIR interface on top of existing services for the EHR-System and she will share her experience with doing that.
 
#*Fleur and her team have implemented a FHIR interface on top of existing services for the EHR-System and she will share her experience with doing that.
 
#**Team of 5, started with FHIR on their own (didn't go to a training course). One day development project.
 
#**Team of 5, started with FHIR on their own (didn't go to a training course). One day development project.
 
#**Use toolkit developed by Josh Mandel - developed an iPad app. Build an App on top of a new FHIR API build for their clinical data repository (called PoliPlus, which already had APIs). Also have an XDS-ish document repository. Use case: get documents for patient ID. Basic HTTP authentication, to put authentican out of scope. Spring tools. defauklt Spring serialization of POJOs different than FHIR serialization.
 
#**Use toolkit developed by Josh Mandel - developed an iPad app. Build an App on top of a new FHIR API build for their clinical data repository (called PoliPlus, which already had APIs). Also have an XDS-ish document repository. Use case: get documents for patient ID. Basic HTTP authentication, to put authentican out of scope. Spring tools. defauklt Spring serialization of POJOs different than FHIR serialization.
 
#**Found FHIR easy to start with. FHIR vs just XML-JSON: value would be in reuse of app in multiple FHIR enabled settings. Images in FHIR (model representation) quite useful.  
 
#**Found FHIR easy to start with. FHIR vs just XML-JSON: value would be in reuse of app in multiple FHIR enabled settings. Images in FHIR (model representation) quite useful.  
#Using an OpenEHR platform in a HL7/IHE interoperability environment (Borut Fabjan, [http://www.marand-thinkmed.com/ Marand])
+
#Using an OpenEHR platform in a HL7/IHE interoperability environment (Borut Fabjan, [http://www.marand-thinkmed.com/ Marand], see [http://www.hl7.org/documentcenter/public/wg/java/20140603_Borut_Fabjan_InterOp_ThinkEHR.pdf http://www.hl7.org/documentcenter/public/wg/java/20140603_Borut_Fabjan_InterOp_ThinkEHR.pdf] for slides, and video recordings at [https://vimeo.com/97714771 https://vimeo.com/97714771] and [https://vimeo.com/97853645 https://vimeo.com/97853645])
 
#*The Think!EHR Platform is a big-data, high-performance solution designed to store, manage, query, retrieve and exchange structured electronic health record data based on the latest release of openEHR specifications
 
#*The Think!EHR Platform is a big-data, high-performance solution designed to store, manage, query, retrieve and exchange structured electronic health record data based on the latest release of openEHR specifications
 
#*Borut will discuss some of the architectural aspects of Think!EHR and the impact of embracing OpenEHR, as well as the support for IHE/HL7 (v2,CDA,FHIR) as an interoperability interface.
 
#*Borut will discuss some of the architectural aspects of Think!EHR and the impact of embracing OpenEHR, as well as the support for IHE/HL7 (v2,CDA,FHIR) as an interoperability interface.
Line 63: Line 75:
 
#*OpenEHR CDR, went to connectathon, as a Document Repository. Also support for IHE "on domand document" proposal.
 
#*OpenEHR CDR, went to connectathon, as a Document Repository. Also support for IHE "on domand document" proposal.
 
#**TDS/TDD openHR document type, can be stored in XDS registry. CDA L1/L2 is a transfrom from an OpenEHR template. CDA L3 is a transform, tricky, lots of academic questions about data models,   
 
#**TDS/TDD openHR document type, can be stored in XDS registry. CDA L1/L2 is a transfrom from an OpenEHR template. CDA L3 is a transform, tricky, lots of academic questions about data models,   
#The experimental HANDI HOPD demonstrator (Ian McNicoll, Ocean Informatics)
+
#The experimental HANDI HOPD demonstrator (Ian McNicoll, Ocean Informatics, see [http://www.hl7.org/documentcenter/public/wg/java/20140603_Ian_McNicoll_HANDI-HOPD.pptx http://www.hl7.org/documentcenter/public/wg/java/20140603_Ian_McNicoll_HANDI-HOPD.pptx] for slides, and the video at [https://vimeo.com/97506030 https://vimeo.com/97506030])
 
#*The HANDI HOPD demonstrator is basically smart on FHIR on openEHR - currently using Marand think!ehr but with the aim to have multiple backends in future. Free to use.
 
#*The HANDI HOPD demonstrator is basically smart on FHIR on openEHR - currently using Marand think!ehr but with the aim to have multiple backends in future. Free to use.
#A world of models - MAX model transformations (Michael van der Zel, [http://www.umcg.nl/ UMCG], NL)  
+
#A world of models - MAX model transformations (Michael van der Zel, [http://www.umcg.nl/ UMCG], NL, see [http://www.hl7.org/documentcenter/public/wg/java/20140603_Michael_vdZel_MAX.pdf http://www.hl7.org/documentcenter/public/wg/java/20140603_Michael_vdZel_MAX.pdf] for slides, and the video at [https://vimeo.com/97512611 https://vimeo.com/97512611])  
 
#*Michael has created a tool that helps in the exchanging and tranformation of models between OpenEHR, CIMI, DCM, ART-DECOR, ArchiMate, EA UML, spreadsheet and others. This is based on the use of the MAX metamodel (kind of an XMI format) for expressing the models and HL7 MAX tool.
 
#*Michael has created a tool that helps in the exchanging and tranformation of models between OpenEHR, CIMI, DCM, ART-DECOR, ArchiMate, EA UML, spreadsheet and others. This is based on the use of the MAX metamodel (kind of an XMI format) for expressing the models and HL7 MAX tool.
#Adjournment at 16:30, next meeting in Amsterdam on November 27th, 2014.
+
#Adjournment at 16:30, next meeting in Amsterdam will be on November 27th, 2014.

Latest revision as of 07:34, 17 June 2014

These are the minutes of the AID out-of-cycle meeting held in Amsterdam, the Netherlands, on June 3rd 2014.

Summary: this meeting ended up being focused on OpenEHR implementations - and how one can implement IHE/HL7 interfaces on top of an OpenEHR based CDR.

Amsterdam AID Minutes

Workgroup Date/Time Location Chair/Scribe
AID HL7 User Group 2014-06-03,
09:00-16:30
Amsterdam, NL Chair/Scribe: Rene Spronk

Attendees

  1. Rene Spronk, Ringholm, NL
  2. Ewout Kramer, Furore, NL
  3. Michael van der Zel, UMCG, NL
  4. Jan-Marc Verlinden, Medvision360, NL
  5. Borut Fabjan, Marand, Slovenia
  6. , Marand, Solvenia
  7. Fleur Kelpin, UMCG, NL
  8. Alexander Henket, Nictiz, NL
  9. Ian McNicoll, FreshEHR, UK
  10. Arianne van de Wetering, Nictiz, NL
  11. Hans Vonkeman, Furore, NL
  12. Marten Smits, Furore, NL

Minutes

  1. Rene calls to order at 09:30
  2. Administrative agenda items
    • Announcements
      • Rene: I intent to capture (some of) the presentations on video, and as per our DMP I request permission from the group and from the speakers to do so.
        • No objections were raised.
    • Aproval of the agenda
    • MOTION To approve the minutes of the San Antonio January 2014 WGM
      • Approved 10-0-2(y-n-a, Ewout/Alexander)
    • MOTION To approve the minutes of the Phoenix May 2014 WGM
      • Approved 10-0-2(y-n-a, Ewout/Alexander)
    • User Groups
      • Rene: at some point AID may be transformed into a fullblown HL7 User Group (HUG). At this point in time the idea is that all HL7 members (of HL7 International, or of any affiliate) will be able to participate for free. Non-members pay a fee of $100 a year, and get to attend all meetings. The $100 (EUR 70) was defined for a UG with just one annual face to face meeting in mind. On the assumption we (as AID) can nearly always use a sponsored meeting room (e.g. provided by a software vendor) the meetings costs are limited to catering costs (EUR 20-45, depending on the quality thereof).
      • Review AID Transition Plan (WG to HUG)
        • A meeting fee of about EUR 30 wouldn't be an issue, it would actually show some level of commitment, and would discourage no-shows. Ewout: problem around whose bank account to use, who will do the invoicing. Rene: HL7 International doesn't wish to be involved in this. Maybe local affiliate, or some company.
        • Of the participants today only 3 are not members of HL7 nor an affiliate.
        • Ewout: I have an intrinsic motivation to 'share', having the shared information behind some 'membership only wall' doesn't motivate me to share.
    • Review/update AID Activities
      • Dropped due to a lack of time
  3. Implementation aspects of my own PHR (Dirk Jan van der Pol, Quli, NL)
    • Dirk Jan had to cancel his talk due to illness.
  4. FHIR and DICOM (Ewout Kramer, Furore, see http://www.hl7.org/documentcenter/public/wg/java/20140603_Ewout_Kramer_WADO_AND_FHIR.PPTX for slides, and the video at https://vimeo.com/97308387)
    • Ewout took part in the SIIM hackathon, a diagnostic imaging hacking event. He will briefly present his experiences in blending RESTful DICOM approaches with FHIR.
      • Ewout had no knowledge of DICOM prior to SIIM. The FHIR resource combines study/series/instance data, whereas QIDO/WADO-RS deals with those individually. Smaller issues reletaed to data types.
      • First time that Ewout was in contact with respresentatives from imaging companies, FHIR resourse dev in close cooperation, they'll visit HL7 connectathons as well.
      • Discussion around getting more DICOM implementers to the join these meetings? Good idea.
  5. An OpenEHR RESTful Archetyped API (Jan-Marc Verlinden, Medvision360, NL)
    • Jan-Marc and Ralph are working on a RESTful API (see http://www.medrecord.nl/medrecord-json-api/) for MEDRecord, an open source OpenEHR based application. They will show how the API is related to the back end EHR, as well as how one could create a FHIR frontend on top of this API.
    • (side note) Developed PAAS for dicom data, we found its impossible to store that mass amount of data, found non-fiber netweroks uncable for cloud storage of the data. Project at Univ. of Utrecht, used project hackathon to push the project forward. Show combined medical images (MRI and 24 channel EEG) in 3D. Philips MRI fMRI. DICOM + Philips DICOM. Two vendors related to image processing and viewing.
    • MEDRecord with archetyped API.
      • Tried an XML approach (w XML db first). Queries would take up to 8 seconds, too slow.
      • Postgress version. MedRecord JSON API. No AQL support, not sure what query language to support, AQL not finalized yet, currently use postgress queries. Focusing on spicif queries for specific use cases, not generic query option. Query for EHRs associated with a certain patients, then query for compositions within such EHRs. OpenEHR has an API specificed in XML.
      • XML version is open sourced, Postgress version has not been open sourced.
    • Ian: there's an interest in defining a common REST based interface for OpenEHR. We have a XML representation, JSON needs to be worked on.
    • Jan-Marc: in OpenEHR, split between communications model and knowledge system, shows HL7 VMR model (for decision support) mapping.
    • Jan-Marc: no problem creating a FHIR interface. Would need mappings. Ian: it's actually not that hard. Not a surprise that they are similar.
  6. Teach yourself (some) FHIR (Fleur Kelpin, UMCG, NL, see http://www.hl7.org/documentcenter/public/wg/java/20140603_Fleur_Kelpin_Teach%20yourself%20(some)%20FHIR.pdf for slides)
    • Fleur and her team have implemented a FHIR interface on top of existing services for the EHR-System and she will share her experience with doing that.
      • Team of 5, started with FHIR on their own (didn't go to a training course). One day development project.
      • Use toolkit developed by Josh Mandel - developed an iPad app. Build an App on top of a new FHIR API build for their clinical data repository (called PoliPlus, which already had APIs). Also have an XDS-ish document repository. Use case: get documents for patient ID. Basic HTTP authentication, to put authentican out of scope. Spring tools. defauklt Spring serialization of POJOs different than FHIR serialization.
      • Found FHIR easy to start with. FHIR vs just XML-JSON: value would be in reuse of app in multiple FHIR enabled settings. Images in FHIR (model representation) quite useful.
  7. Using an OpenEHR platform in a HL7/IHE interoperability environment (Borut Fabjan, Marand, see http://www.hl7.org/documentcenter/public/wg/java/20140603_Borut_Fabjan_InterOp_ThinkEHR.pdf for slides, and video recordings at https://vimeo.com/97714771 and https://vimeo.com/97853645)
    • The Think!EHR Platform is a big-data, high-performance solution designed to store, manage, query, retrieve and exchange structured electronic health record data based on the latest release of openEHR specifications
    • Borut will discuss some of the architectural aspects of Think!EHR and the impact of embracing OpenEHR, as well as the support for IHE/HL7 (v2,CDA,FHIR) as an interoperability interface.
    • Borut recaps the OpenEHR model, role of templates to define a subset applicable in a particular context.
      • AQL, query builders
      • Metaform builder
    • OpenEHR CDR, went to connectathon, as a Document Repository. Also support for IHE "on domand document" proposal.
      • TDS/TDD openHR document type, can be stored in XDS registry. CDA L1/L2 is a transfrom from an OpenEHR template. CDA L3 is a transform, tricky, lots of academic questions about data models,
  8. The experimental HANDI HOPD demonstrator (Ian McNicoll, Ocean Informatics, see http://www.hl7.org/documentcenter/public/wg/java/20140603_Ian_McNicoll_HANDI-HOPD.pptx for slides, and the video at https://vimeo.com/97506030)
    • The HANDI HOPD demonstrator is basically smart on FHIR on openEHR - currently using Marand think!ehr but with the aim to have multiple backends in future. Free to use.
  9. A world of models - MAX model transformations (Michael van der Zel, UMCG, NL, see http://www.hl7.org/documentcenter/public/wg/java/20140603_Michael_vdZel_MAX.pdf for slides, and the video at https://vimeo.com/97512611)
    • Michael has created a tool that helps in the exchanging and tranformation of models between OpenEHR, CIMI, DCM, ART-DECOR, ArchiMate, EA UML, spreadsheet and others. This is based on the use of the MAX metamodel (kind of an XMI format) for expressing the models and HL7 MAX tool.
  10. Adjournment at 16:30, next meeting in Amsterdam will be on November 27th, 2014.