slide 1 © copyright 2015 qvera llc all rights reserved 265 n main suite d140 kaysville ut 84037...

© Copyright 2015 • Qvera LLC • All rights reserved© Copyright 2015 • Qvera LLC • All rights reservedwww.qvera.com 265 N Main • Suite D140 • Kaysville • UT 84037

FHIR is a registered trademark of HL7.org

FHIR and the Future of Patient Care Device

InteroperabilityRon ShapiroJune 6, 2015

© Copyright 2015 • Qvera LLC • All rights reserved

This presentation will answer:

• What is FHIR?• Why will FHIR catch on?• Why will FHIR be widely adopted?• How will patient care devices use FHIR?


What is FHIR?

• The FHIR Acronym• pronounced “fire”

• F – Fast (to design and to implement)• H – Health• I – Interoperable• R – Resources (building blocks)

• Much of this presentation content comes from Grahame Grieve’s “Introduction to FHIR” presentation at http://www.slideshare.net/GrahameGrieve/introduction-to-fhir

• Grahame Grieve is one of the original authors of the FHIR specification.

http://www.slideshare.net/GrahameGrieve/introduction-to-fhir


What are FHIR “Resources”?

• A set of modular components• each Resource can be represented using XML or JSON• examples include a Patient with their demographics or a

Medication with it’s code and manufacturer

• Refer to each other using URLs• web URLs are easy to understand and implement• e.g. http://fhir-server/Patient/12345678

• Can be exchanged between systems• using a web approach (called a RESTful API)• can group a collection of “Resources” into a Bundle


Why was FHIR created?

• To fulfill the need to share healthcare information electronically• HL7 v2 is over 25 years old

• To increase pressure to broaden the scope of sharing• across organizations, disciplines, even borders• with mobile and cloud-based applications• faster – integration in days or weeks, not months or years


Why was FHIR created?

• Existing HL7 specifications did not have much to offer for new applications and sharing• v2 is old and limited by it’s own rules• v3 is too slow and too hard• CDA is also limited and too hard to implement• nothing suitable for light-weight integration, or for Health 2.0

• HL7 decided to undertake a “fresh look”• researched the best approach that would lead to the best

chance for widest adoption• found that using a “web” approach would provide simplest

implementation


FHIR Specification Development Progress

• July 2011 – conception• Fall 2012 – first Draft Ballot• Fall 2013 – first Draft Standard for Trial Use (DSTU)• January 2014 – DSTU finalized• ~Summer 2015 – 2nd DSTU finalized• Late 2016? – Normative Version


Why will FHIR catch on?

• Simple and quick to understand and implement• Code and example servers already exist• Specification is free for use with no restrictions• Based on the web (including security)• Can be extended and adapted for local usage


Why will FHIR be widely adopted?• Already has a vibrant and open source community with

frequently held connectathons

• The Argonaut Project ( http://argonautproject.org ) is a private sector initiative to advance industry adoption of modern, open interoperability standards – it uses FHIR

• Uses modern technologies, the same used by all major web companies (e.g. Facebook, Google)

• More people are familiar with these technologies (thus less expensive consultants)


How will patient care devices use FHIR?

FHIR resources have already been defined:

Patient

Device

DeviceMetric

DeviceMetricObservation


HL7 v2 IHE PCD Message Example


FHIR IHE PCD Message Example


Future of Interoperability?• Will be determined by the technologies and standards that

are implemented across the highest number of vendors

• FHIR seeks to provide implementers with a specification that is simple to understand, quick to adopt, easy to troubleshoot and yet provides the flexibility to accommodate local needs

• Visit http://hl7.org/fhir/ to learn more

• Questions?

• Ron Shapiro <[email protected]>

slide 1 © copyright 2015 qvera llc all rights reserved 265 n main suite d140 kaysville ut 84037...

Documents