This wiki has undergone a migration to Confluence found Here
Difference between revisions of "AID 201510 Meeting in Atlanta"
Jump to navigation
Jump to search
Rene spronk (talk | contribs) |
Rene spronk (talk | contribs) |
||
Line 19: | Line 19: | ||
==Minutes== | ==Minutes== | ||
− | #Administrative ( | + | #Administrative |
+ | #*Rene: as per our DMP I'm asking for your permission to record and publish video of the various presentations. No objections were raised. | ||
+ | #Simple JSON Parser Mobile App (Jeff Ting, Systems Made Simple, US) | ||
+ | #*I wrote a mobile app for the first time, and one that can parse JSON to any level of depth to reach FHIR elements of interest. I will discuss the parsing design, as well as lessons learned on user interface layouts for mobile. | ||
+ | #*Comment by James Agnew: could also use HAPI, it has an Android library. | ||
#General FHIR Server Design Review (Brian Postlethwaite, Healthconnex, AU) | #General FHIR Server Design Review (Brian Postlethwaite, Healthconnex, AU) | ||
#*Covers different types and approaches for implementing a FHIR server (Generic FHIR Server, Publish/Sync, Façade, Cache) | #*Covers different types and approaches for implementing a FHIR server (Generic FHIR Server, Publish/Sync, Façade, Cache) | ||
#*Aims to raise discussion about these various approaches | #*Aims to raise discussion about these various approaches | ||
− | # | + | #*Comment by Ewout: may lead to situation whereby primary key (as used internal to the persistence layer) is publicly exposed as the resource.id. |
− | #* | + | #*Question by Rene: excellent overview, IMHO should be used as a starter version for one of our whitepapers. does this room also feel that to be the case? Yes. Also a whitepaper on the v2-FHIR mapping issues. |
+ | #clinFHIR implementation experiences (David Hay, Orion Health, NZ) | ||
+ | #*See [http://clinfhir.com/ http://clinfhir.com/] for the clinFHIR site. | ||
#FHIR Enable Epic EHR using Cloverleaf (Ron Archambault, Infor, US) | #FHIR Enable Epic EHR using Cloverleaf (Ron Archambault, Infor, US) | ||
#*Infor developed FHIR DSTU-2 Message bundles with patient and questionnaire resources using the Epic InterConnect API | #*Infor developed FHIR DSTU-2 Message bundles with patient and questionnaire resources using the Epic InterConnect API | ||
− | |||
− | |||
#Development of "FHIR cell for i2b2" (Kavi Wagholikar MD, MGH, US) | #Development of "FHIR cell for i2b2" (Kavi Wagholikar MD, MGH, US) | ||
#*This presentation will describe the technical details and learnings in the development of the fhir interface for [https://www.i2b2.org/ i2b2]. | #*This presentation will describe the technical details and learnings in the development of the fhir interface for [https://www.i2b2.org/ i2b2]. | ||
#*Over 100 institutions in the US have i2b2 installations for identifying research cohorts. The fhir api is aimed at providing a readonly interface to the data hosted in the i2b2 instances, allowing the institutions to run SMART apps over i2b2. | #*Over 100 institutions in the US have i2b2 installations for identifying research cohorts. The fhir api is aimed at providing a readonly interface to the data hosted in the i2b2 instances, allowing the institutions to run SMART apps over i2b2. | ||
+ | #*Executes a query agains an in-memory bundle of resources. | ||
#HL7 ORM v2.3 into FHIR REST-API (Joerg-Uwe Meyer, MT2IT, DE) | #HL7 ORM v2.3 into FHIR REST-API (Joerg-Uwe Meyer, MT2IT, DE) | ||
#*Migration/translation issue v2-FHIR | #*Migration/translation issue v2-FHIR | ||
#Creating the FHIR interface for the NHS FGM Risk Identification System (Richard Kavanagh, HSCIC, England) | #Creating the FHIR interface for the NHS FGM Risk Identification System (Richard Kavanagh, HSCIC, England) | ||
#*An overview of the journey of implementing FHIR into the English NHS national architecture (see http://data.developer.nhs.uk/fhir/fgm/ ). The challenges of moving away from HL7v3, dealing with a DSTU standard and the absence of tooling infrastructure. Lessons learned and the roadmap for the future. | #*An overview of the journey of implementing FHIR into the English NHS national architecture (see http://data.developer.nhs.uk/fhir/fgm/ ). The challenges of moving away from HL7v3, dealing with a DSTU standard and the absence of tooling infrastructure. Lessons learned and the roadmap for the future. | ||
− | #' | + | #*Challenge will be 'using FHIR at scale'. |
+ | #Adjournement at 17:00 | ||
==Monday Q3== | ==Monday Q3== |
Revision as of 15:19, 6 October 2015
This is the agenda of the AID HL7 'user group' for the WGM in Atlanta (October 2015)
Wednesday Q4
- Administrative
- Project and issue review
- Project #550 - Whitepaper review: List of AID Whitepapers
- Project #1178 - Implementation Packages
- Issue List Category:AID_Issue
- Update AID three year plan
- Update/review AID Mission and Charter
Sunday Q3/Q4 (hosting FHIR)
Attendance
- Rene Spronk, and 40 others (40 in Q3, 24 in Q4)
Minutes
- Administrative
- Rene: as per our DMP I'm asking for your permission to record and publish video of the various presentations. No objections were raised.
- Simple JSON Parser Mobile App (Jeff Ting, Systems Made Simple, US)
- I wrote a mobile app for the first time, and one that can parse JSON to any level of depth to reach FHIR elements of interest. I will discuss the parsing design, as well as lessons learned on user interface layouts for mobile.
- Comment by James Agnew: could also use HAPI, it has an Android library.
- General FHIR Server Design Review (Brian Postlethwaite, Healthconnex, AU)
- Covers different types and approaches for implementing a FHIR server (Generic FHIR Server, Publish/Sync, Façade, Cache)
- Aims to raise discussion about these various approaches
- Comment by Ewout: may lead to situation whereby primary key (as used internal to the persistence layer) is publicly exposed as the resource.id.
- Question by Rene: excellent overview, IMHO should be used as a starter version for one of our whitepapers. does this room also feel that to be the case? Yes. Also a whitepaper on the v2-FHIR mapping issues.
- clinFHIR implementation experiences (David Hay, Orion Health, NZ)
- See http://clinfhir.com/ for the clinFHIR site.
- FHIR Enable Epic EHR using Cloverleaf (Ron Archambault, Infor, US)
- Infor developed FHIR DSTU-2 Message bundles with patient and questionnaire resources using the Epic InterConnect API
- Development of "FHIR cell for i2b2" (Kavi Wagholikar MD, MGH, US)
- This presentation will describe the technical details and learnings in the development of the fhir interface for i2b2.
- Over 100 institutions in the US have i2b2 installations for identifying research cohorts. The fhir api is aimed at providing a readonly interface to the data hosted in the i2b2 instances, allowing the institutions to run SMART apps over i2b2.
- Executes a query agains an in-memory bundle of resources.
- HL7 ORM v2.3 into FHIR REST-API (Joerg-Uwe Meyer, MT2IT, DE)
- Migration/translation issue v2-FHIR
- Creating the FHIR interface for the NHS FGM Risk Identification System (Richard Kavanagh, HSCIC, England)
- An overview of the journey of implementing FHIR into the English NHS national architecture (see http://data.developer.nhs.uk/fhir/fgm/ ). The challenges of moving away from HL7v3, dealing with a DSTU standard and the absence of tooling infrastructure. Lessons learned and the roadmap for the future.
- Challenge will be 'using FHIR at scale'.
- Adjournement at 17:00
Monday Q3
- Administrative
- Approval of the minutes of the May WGM in Paris, available at AID 201505 Meeting in Paris
- Use of a RIM-lite OWL triple store to calculate quality measures (Peter Hendler, KP)
- Peter has been working with Oxford University UK dept of Computer Science and KP National Quality. They have an OWL ontology based on Entities in Roles Participating in Acts (ERPA; it is not the full RIM by any means, it is their own RIM lite OWL). They have successfully calculated some Diabetes quality measures using OWL, RDF and SNOMED.
- Peter will discuss some of the core design considerations, as well as other experiences.
- See http://www.cs.ox.ac.uk/isg/tools/RDFox/ for details of RDFox, a highly scalable in-memory RDF triple store.