|
|
| Line 22: |
Line 22: |
| | *JGZ v3 (Kyndylan Nienhuis, NL, k.nienhuis@allegro-sultum.nl) | | *JGZ v3 (Kyndylan Nienhuis, NL, k.nienhuis@allegro-sultum.nl) |
| | | | |
| − | ==DD 2016== | + | ==DD 2017== |
| | | | |
| − | ===Wednesday===
| + | *mari.peltola-nykyri@kela.fi |
| − | *Marc de Graauw (IKNL, Netherlands), Using FHIR for the Dutch National Cancer Registry (20 mins, Wednesday 9-9:40 timeslot)
| + | **Finnish PHR (confirm title and time slot in Sept) |
| − | **The Dutch National Cancer Registry is rolling out an ambitious programme to collect data on each cancer treatment on a national level. Guidelines will be implemented in decision support systems, and feedback from the diagnostics to treatment will be used to improve those guidelines. The data needed for this feedback loop will be exchanged using FHIR. Using FHIR to supply registries with information poses some special challenges not present in primary care. The scale of the program also requires a generic approach, where logical models of the cancer data, developed in the ART DECOR toolset, are used to feed the FHIR specification process.
| |
| − | *Jens Stockhausen (TomTec Imaging Systems GmbH, Germany), Challenges using FHIR in the domain of US diagnostics and reporting (20 mins, Wednesday 9-9:40 timeslot)
| |
| − | **TomTec provides solutions in the domain of ultrasound (US) diagnostics and reporting. By adapting FHIR interfaces we encountered some challenges related to the particularities of the US modalities. Especially regarding the huge amount of different measurements provided in SRs (Structured Reporting, the structured document format defined by the DICOM standard) and the proprietary content of US DICOM images. We will share some of these challenges we met doing our first steps integration FHIR interfaces into our system; these are mainly related to the Observations and the AuditEvent Resources.
| |
| − | *Sebastien Letelier (Hacking Health, France), Disruptive hackers, the power to change the world of healthcare (Wednesday, 11:15-11:55 slot, 40mins)
| |
| − | **Innovation in healthcare is on the way and we are, as developers, the guys who make this happens. But the only way to do it well is to do it in collaboration with users (health professionals and patients) and put the power of APIs and agility to easily build simple tools that people want.
| |
| − | | |
| − | ===Thursday===
| |
| − | *Alexander Henket (Nictiz, Netherlands), Dutch Personal Health Environment Project (20 mins, Thursday 09:00-09:40 slot)
| |
| − | **Nictiz is working with the Dutch Patient Federation, Ministry of Health and many parties in the field on a Personal Health Environment or Personal Health Record. There is a FHIR component to it all, in addition to organizational, legal and infrastructural issues. Primary initial focus: medication, lab, allergy-intolerances, self assessments, letters. In the slipstream of that the more general resources patient, care provider, organization. It's a project that could be viewed upon as Argonaut if you will. Relevance for implementers and people with similar projects that include many stakeholders.
| |
| − | *Amir Mehrkar (Orion Health, UK), the English INTEROPen interoperability movement (20, Thursday 09:00-09:40 slot)
| |
| − | **Amir co-founded the English NHS interoperability movement called www.INTEROPen.com (@INTEROPenAPI) which has as its first founding project a FHIR programme of work geared at establishing a national set of FHIR profiles for patient care across all care settings, with the purpose of real implementation by vendors and provider care organisations. Amir wil share the lessons and challenges, how they started it, and where they are with this, picking up on the methods of working together to define the profiles, an approach to clinical validation and how we have garnered support from national influencers. We are still learning how to do this best and so it would be great to seek feedback from the audience too.
| |
| − | | |
| − | *Oliver Krauss (FH Hagenberg, Austria), FHIR workflow to support tumor boards (20, Thursday 11:15-11:55 slot)
| |
| − | **Collaborative Interdisciplinary Medical Boards (KIMBO) is a project with our partner CGM Austria. In it we are working on interoperable tumor boards between different hospital organizations and general practicioners. We describe the workflow of a tumor board using the FHIR-Plan Definition resource and apply some automation to the process as well.
| |
| − | *Susan Collins (IBM Watson health, Ireland) Watson Health on FHIR (20 mins, Thursday 11:15-11:55 slot)
| |
| − | **An overview of how IBM Watson Health are using FHIR to support delivering cognitive and analytic insights to mobile apps. The presentation will delve into details on patterns of using FHIR for supporting analytics and how we are looking to enable existing Natural Language Processing services via FHIR.
| |
| − | | |
| − | ===Friday===
| |
| − | | |
| − | *Friday 9:00-9:40, Tool presentations, about 5 minutes each
| |
| − | **Lloyd McKenzie, IG publishing tool (TBC)
| |
| − | **Michel Rutten Forge new features (TBC)
| |
| − | **James Agnew, HAPI based FHIR database (TBC)
| |
| − | **Bryn Rhodes, ad-hoc CQL execution environment (TBC)
| |
| − | **Nicola Ruzjkov, tool update (TBC)
| |
| − | | |
| − | *Friday 9:45-10:25, Tool presentations, about 5 minutes each
| |
| − | **Pascal Pfiffner, Validation using Swift and Python FHIR clients(TBC)
| |
| − | **Grahame Grieve, electric FHIR client (TBC)
| |
| − | **Christiaan Knaap, Spark update (TBC)
| |
| − | **Brad Genereaux, RESTful DICOM related toools (TBC) | |
| − | **David Hay, ClinFHIR update
| |
| − | **Ardon Toonstra, Simplifier update
| |
| − | | |
| − | *Alexander Henket (Nictiz, the Netherlands), Building towards integrating ART-DECOR and Simplifier capabilities (20 minutes, Friday 10:30-11:10 slot)
| |
| − | **Nictiz has, based on the Personal Health Environment project, an acute tooling issue. We solve this partly within ART-DECOR, our platform of choice for specifications, and partly outside of ART-DECOR using Simplifier based on our brand new cooperation with Furore to this end. The challenge is to seamlessly bring together functional and technical artifacts in a consistent package that satisfies needs at various levels."
| |
| − | *Christiaan Knaap (Furore, Netherlands), FHIR Server implementation using Spark examples (20 minutes, Friday 10:30-11:10 slot)
| |
| − | **Every environment has different expectations from a FHIR server. To accommodate that, a flexible set of FHIR server components is needed, that can be combined and customized to the need at hand. We'll discuss componentization, cross-database design and customization hooks, with examples from the .Net Spark code.
| |
