Why mhealth wants to be on FHIR

Transcription

1 Why mhealth wants to be on FHIR Oliver Egger, ahdis

2 @ oliveregger WHY MHEALTH WANTS TO BE ON FHIR mhealth / App development standards to the rescue? short FHIR introduction SMART on FHIR: Apps with FHIR Q&A 2

3 @ oliveregger MHEALTH / APP DEVELOPMENT Build an mhealth app that gives dosage recommendations based on your glucose data and expected food. 3 Source:

4 @ oliveregger MHEALTH / APP DEVELOPMENT Technical Implications Hardware: Device, Mobile phone, Server Software: Embedded, Native on Phone, Web Apps, Hybrid Apps, Portal Communication: Bluetooth, Wi-Fi, REST API, Web Services Highly fragmented, fast changing environment Health data interoperability? 4

5 @ oliveregger STANDARDS AND GUIDELINES TO THE RESCUE ISO/IEE11073 HL7 IHE Continua Guidelines from Personal Connected Health Alliance 5

6 @ oliveregger CONTINUA GUIDELINES Copyright 2017 Personal Connected Health Alliance. All rights reserved. 6

7 @ oliveregger HL7 STANDARDS 7 HL7, HEALTH LEVEL SEVEN, FHIR are trademarks owned by Health Level Seven International, registered with the United States Patent and Trademark Office.

8 @ oliveregger FHIR 8 F Fast faster to develop, learn, implement H I Healthcare Interoperability R Resources Resources as bricks, REST API

9 @ oliveregger FHIR RESOURCES 9 A collection of information models that define the data elements, constraints and relationships for the business objects most relevant to healthcare. FHIR resources are represented in XML or JSON. Resources build on an information model, but developers do not have to know or learn the model behind it.

10 @ oliveregger FHIR RESOURCES Examples: Patient, Practitioner, MedicationStatement 80/20 Rule, Extensions Framework Profiling: Interoperability out-of-the-box, adaptable for local requirements Maturity Level for Resources 10

11 @ oliveregger FHIR API 11 REST API based on Resources Strong foundation in Web standards XML, JSON, HTTP, OAuth, etc. Strong focus on implementation Multiple implementation libraries Specification is free for use with no restrictions In addition seamless exchange of information using messages or documents and service based architectures

12 @ oliveregger SMART: APPS ON FHIR Apps platform on top of FHIR Authorization Framework based on OAuth/OpenID Connect Launch Context for Apps In the process of being integrated into the FHIR core standard FHIR OAuth OpenID Connect MitrendS App and midata.coop based on SMART on FHIR architecture 12

13 @ oliveregger TOWARDS A NORDIC REFERENCE ARCHITECTURE for Personal Connected health and care Technology (March 2017) The model will likely have a role in communicating Nordic requests for enhancements in the Continua Guidelines to PCHA. Among the most important requests is the use of more modern and developer-friendly frameworks, such as HL7 FHIR. Source: 13

14 @ oliveregger TAKE HOME MESSAGE 14 FHIR as an API for mhealth developers Resources for interoperability over all architecture types SMART on FHIR: don t roll your own security Engage in the new open standards ecosystem

15 @ oliveregger WANT TO KNOW MORE? FHIR workshop tomorrow during ehealth Summit 11:30-13:00: General introduction for health professionals, executives and software developers. 14:30-15:30: Technical aspects, basic IT background is helpful. Registration at Information Desk contact HL7 CH visit FHIR DevDays in Amsterdam in November 15

16 @ oliveregger QUESTIONS? 16

17 founder ahdis gmbh visionary AG, docbox Ecofin Research & Consulting AG SPEAG Dozent BFH Bern, ZHAW Winterthur Medizininformatik, Interoperabilität HL7.ch Technical Manager, member hl7 since 2009 OLIVER EGGER phone: oliver.egger@ahdis.ch IHE Suisse Deputy Technical Manager since 2016, member since 2015 Dipl. Inf. ETH, ETH Zürich, 1996 IHE XDS Advanced Training, 2015 Certified HL7 CDA Specialist, 2015 Certified Scrum Master, 2014 NDK ehealthcare, Nottwil,