This wiki has undergone a migration to Confluence found Here
Difference between revisions of "AID 201705 Meeting in Madrid"
Jump to navigation
Jump to search
Rene spronk (talk | contribs) |
Rene spronk (talk | contribs) (→Agenda) |
||
| Line 24: | Line 24: | ||
===Agenda=== | ===Agenda=== | ||
#Administrative | #Administrative | ||
| − | #*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 | + | #*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 | ||
Revision as of 09:46, 30 March 2017
Return to: WGM Minutes > 2017 > May Madrid
This is the agenda of the AID WG for the WGM in Madrid ES, May 2017.
Contents
Sunday Q3/Q4 (joint with FHIR)
Agenda
- Announcements
- FHIR related presentations
- Architecting a FHIR frontend using a legacy database backend, (Rene Spronk, Ringholm, NL)
- High level introductory discussion of implementation issues
- 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.
- Building a FHIR frontend using Spark/Vonk (Christiaan Knaap, Furore, NL)
- Vonk is the newly architected Furore FHIR database frontend
- 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.
- FHIRForms: generating clinical forms from FHIR profile definitions (Robert Worden, , UK)
- Architecting a FHIR frontend using a legacy database backend, (Rene Spronk, Ringholm, NL)
- Other presentations
Monday Q3
Agenda
- Administrative
- 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
Wednesday Q1
Agenda
- Project and issue review
- Project #550 - Whitepaper review: project details, List of AID Whitepapers
- 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.
- Issue List Category:AID_Issue
