why mhealth wants to be on fhir · 2017-09-27 · deputy technical manager since 2016, member since...

@oliveregger

Why mHealth wants to be on FHIROliver Egger, ahdis gmbh

© HIMSS Europe GmbH2

• mHealth / App development• standards to the rescue? • short FHIR introduction• SMART on FHIR: Apps with FHIR• Q&A

WHY MHEALTH WANTS TO BE ON FHIR

@ oliveregger


Build an mHealth app that gives dosage recommendationsbased on your glucose data and expected food.

Source: https://www.e-health-suisse.ch/fileadmin/user_upload/Dokumente/2017/D/170315_mHealth_UseCase_d.pdf

MHEALTH / APP DEVELOPMENT

@ oliveregger


• 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?

MHEALTH / APP DEVELOPMENT

@ oliveregger


• ISO/IEE11073

• HL7

• IHE

• Continua Guidelines from Personal Connected Health Alliance

STANDARDS AND GUIDELINES TO THE RESCUE

@ oliveregger


CONTINUA GUIDELINES

@ oliveregger

Copyright © 2017 Personal Connected Health Alliance. All rights reserved. http://www.pchalliance.org/sites/pchalliance/files/Fundamentals_Data_Exchange_20170404_0.pdf


HL7 STANDARDS

@ oliveregger

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


@ oliveregger

F Fastfaster to develop, learn, implement

H HealthcareI Interoperability

R ResourcesResources as bricks, REST API

FHIR


• 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.

FHIR RESOURCES

@ oliveregger


• Examples: Patient, Practitioner, MedicationStatement

• 80/20 Rule, Extensions Framework

• Profiling: Interoperability out-of-the-box,adaptable for local requirements

• Maturity Level for Resources

FHIR RESOURCES

@ oliveregger


• 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

FHIR API

@ oliveregger


• 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

• MitrendS App and midata.coop based on SMART on FHIR architecture

SMART: APPS ON FHIR

@ oliveregger

FHIR OAuthOpenIDConnect


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: http://www.hl7.fi/wp-content/uploads/Nordic-Reference-Architecture-for-Personal-Connected-Health-Technology-2017-03-19.pdf

TOWARDS A NORDIC REFERENCE ARCHITECTURE

@ oliveregger


• 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

TAKE HOME MESSAGE

@ oliveregger


• 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 CHvisit FHIR DevDays in Amsterdam in November

WANT TO KNOW MORE?

@ oliveregger


QUESTIONS?

@ oliveregger


OLIVER EGGER

2015 - founder ahdis gmbh2003 - 2014 visionary AG, docbox2002 - 2003 Ecofin Research & Consulting AG1994 – 2001 SPEAG

Dozent BFH Bern, ZHAW WinterthurMedizininformatik, Interoperabilität

HL7.chTechnical Manager, member hl7 since 2009

IHE SuisseDeputy Technical Manager since 2016, member since 2015

Dipl. Inf. ETH, ETH Zürich, 1996IHE XDS Advanced Training, 2015Certified HL7 CDA Specialist, 2015Certified Scrum Master, 2014NDK eHealthcare, Nottwil, 2009

phone: [email protected]: @oliveregger

why mhealth wants to be on fhir · 2017-09-27 · deputy technical manager since 2016, member since...

Documents