Difference between revisions of "AID 201705 Meeting in Madrid"

From HL7Wiki
Jump to navigation Jump to search
Line 28: Line 28:
 
#*MOTION to approve of the [[Software Implementation of CDA]] whitepaper, as an accurate reflection of current CDA implementation best practices, the whitepaper will be up for renewal in May 2018.
 
#*MOTION to approve of the [[Software Implementation of CDA]] whitepaper, as an accurate reflection of current CDA implementation best practices, the whitepaper will be up for renewal in May 2018.
 
#*Approval of the minutes
 
#*Approval of the minutes
#**MOTION to Approve the minutes of the 2016-09 meeting held in Baltimore, as available at [[AID 201609 Meeting in Baltimore].
+
#**MOTION to Approve the minutes of the 2016-09 meeting held in Baltimore, as available at [[AID 201609 Meeting in Baltimore]].
#**MOTION to approve the minutes of the AID 2017-01 meeting held in San Antonio, as available at [[201701 Meeting in San Antonio]]
+
#**MOTION to approve the minutes of the AID 2017-01 meeting held in San Antonio, as available at [[AID 201701 Meeting in San Antonio]]
  
 
==Wednesday Q1==
 
==Wednesday Q1==

Revision as of 06:30, 5 April 2017

Return to: WGM Minutes > 2017 > May Madrid

This is the agenda of the AID WG for the WGM in Madrid ES, May 2017.

Sunday Q3/Q4 (joint with FHIR)

Agenda

  1. Announcements
  2. FHIR related presentations
    1. Architecting a FHIR frontend using a legacy database backend, (Rene Spronk, Ringholm, NL)
      • High level introductory discussion of implementation issues
    2. Building FHIR Servers on existing Relational Databases (Robert Worden, , UK)
      • To make a FHIR Server from an existing healthcare relational database, you have to develop transforms between FHIR resources and the native database formats - in both directions (for GET and PUT). One way to do this is to use the FHIR Transform Engine. This gives bi-directional transforms from declarative mappings - saving coding effort, and increasing reliability. Transforms integrate with the HAPI server engine. An example implementation is described.
      • There is an important side-benefit to this approach. RESTFul FHIR searches are converted to efficient SQL queries, automatically - supporting a wide range of searches without coding.
    3. Building a FHIR facade for an existing GP system (Christiaan Knaap, Furore, NL)
      • We have used Vonk to implement a FHIR façade to an existing GP system to open up the data to patients. We had to bridge the gap between the system’s database schema and FHIR resources, map search parameters and apply authorization based on the OAuth2 token for the patient. I will discuss the setup of the solution, what Vonk offers out of the box and what had to be coded specifically for this use case, along with difficulties we encountered.
    4. Implementing databases for FHIR - 3 years experience report (Niqoula Ruschkov, FHIRBase, RU)
      • With the upcoming SQL standard 2017 with JSON - the FHIRBase approach will be suitable for Oracle, MSSQL and other compliant databases.
    5. FHIRForms: generating clinical forms from FHIR profile definitions (Robert Worden, , UK)
      • Generate a form design from any FHIR profile or bundle; refine the design for specific use cases
      • Form can be used to view or edit FHIR resources and bundles; or for clinical validation of profiles
  3. Other presentations

Monday Q3

Agenda

  1. Administrative

Wednesday Q1

Agenda

  1. Project and issue review
    1. Project #550 - Whitepaper review: project details, List of AID Whitepapers
    2. Project #1178 - Implementation Packages
      • Upon review of the functional requirement those present agree that they reflect what a newbie implementer would find useful. Next step: find appropriate tools etc. to create the v2 implementation package.
    3. Issue List Category:AID_Issue