1. 1

2. 2 Implementing FHIR Fast Healthcare Interoperability Resources Connecting Michigan for Health 2016 Workshop on FHIR Wayne Kubick, CTO, HL7

3. 3 Topics for Today My brief overview of FHIR Uses of FHIR The Argonaut Experience The FHIR Community and Connectathons Coming Attractions

4. 4 What Matters Most to HL7 HL7 Vision: A world in which everyone can securely access and use the right health data when and where they need it. HL7 Mission: to empower global health data interoperability by developing the best, right standards and enabling their adoption and implementation.

5. 5 Why FHIR? Source: HIMSS 2016

6. 6 Metcalf’s Law: Value of a Network = (Number of users) 2

7. 7 Source : KLAS HL7 FHIR: Peak of the Hype Cycle

8. 8

9. 9 9

10. 10 6/23/20166/23/20166/23/20166/23/20166/23/2016 10 In (a) Learning Health System we collect data, feed it through an analytic engine so it affects (the) next patient.” -- Tom Sullivan @SullyHIT

11. 11 Some Basics of FHIR A next generation standards framework & platform, built on 30 years’ experience, designed for implementation RESTful Services technology (used by Facebook, Twitter…) Flexible outputs: messages, documents, data, services Based on Resources: essential modular information components easily assembled into working systems.

12. 12 Principles of FHIR Data resides at the source of truth APIs access data: pull what you need, instead of only getting what’s pushed Focus on implementers Include rigorous semantics Design for the common 80%; extensions for the rest Off-the-shelf security and authorization Speed, scalability, ease of understanding Everything is human readable and free.

13. May 2016 Survey Results – Priority Resources Patient Observation Practitioner Medication Condition (aka Problem) AllergyIntolerance Organization Encounter MedicationOrder DiagnosticReport Immunization MedicationStatement DiagnosticOrder MedicationAdministration Bundle MedicationDispense CarePlan Procedure Conformance Person

14. 14 The international FHIR Maturity Model was envisioned to ensure developers of the value and stability of FHIR Connectathon International Adoption 1 2 3 4 5 Stable build Passed ballot Tested, published, prototyped

15. 15 JASON Task Force & the Argonauts

16. * JASON Task Force recommendations on market-based interoperability governance and coordination, and call to action on “public APIs” * Market experience with MU 2 and associated certification *Industry desire to involve private sector and bring market discipline to standards development Argonaut Project Origins

17. Some Argonaut Project Members Accenture athenahealth Beth Israel Deaconess Medical Center Cerner Epic Intermountain Healthcare Mayo Clinic Meditech McKesson Partners HealthCare System SMART at the Boston Children’s Hospital Surescripts The Advisory Board Company Currently 89 Total Participants

18. 18 Why Another Standard? Source: Micky Tripathi

19. The Argonaut Project Leverages the work of other initiatives such as the S&I framework and SMART Accelerates the maturation of FHIR for the industry Open to all participants Argonaut is not an organization, competitive or proprietary in nature.

20. 20 Some Argonaut Tasks Accelerate the market readiness of the FHIR specification Support the creation of a community of FHIR implementers Prioritize and create implementation guides for querying common MU dataset, CCDA, provider directory, security and authorization Support conformance testing, and publish results Continuous improvement through frequent sprints.

21. 21 Focus on Common Data Set

22. 22 Implementation Guides Based on Data Access Framework (DAF) Profiles

23. Argonaut Implementation Guides: FHIR Restful APIs & Oauth/OIDC Source: Micky Tripathi

24. Argonaut Implementation Program

25. 25 Some Lessons from Argonaut Argonaut has proven speed of FHIR development (from several months to 2 week sprints) Competitors are willing to collaborate for interoperability Foundation is in place, but more needed (search parameters, granularity) Rapid increase in market demand for Argonaut and FHIR (provider directories, Sync4Science, ONC calls for patient apps) Need to define market ecosystem (terms, IP, safety, contracts) Source: Micky Tripathi

26. Links to Argonaut Outputs

27. 27 FHIR Connectathons

28. 28 May 2016 Connectathon Tracks

29. 29 Clinicians on FHIR Periodic workshops where clinicians collaborate with FHIR developers Goal to engage clinicians in evaluating fit for purpose of FHIR resources in use case snippets built around clinical workflows. Clinicians interact with FHIR developers, using a tool (ClinFHIR) to build and visualize resource instances and simple profiles.

30. Clinicians Using ClinFhir

31. 31 The HL7 Partners in Interoperability is a coalition of various stakeholders, including Medical Societies, BioPharma, and the Payer community, paving a path toward interoperability Next meeting planned for October 17-18 2016

32. 32 More than 200 clinical organizations, IT developers, government agencies and healthcare systems worldwide are now committed to developing FHIR applications

33. 33 A 2-day FHIR Roundtable of implementations and deployed applications will be held at Harvard Medical School, Boston on July 27-28

34. 34 The mission of the newly announced FHIR Foundation is the support of implementers and implementation* *FHIR.org

35. 35 What’s Next for FHIR? STU 3 ballot: Sign-up July 27 (Resources, Workflow) Baltimore Connectathon Sept. 17 New product roadmap: RDF / Base Ontology work Fluentpath and a new mapping language Clinical decision support resources CIMI / logical model development.

36. 36 A Normative version of FHIR is planned for the Spring of 2017

37. 37 Implementing FHIR Fast Healthcare Interoperability Resources Connecting Michigan for Health 2016 Workshop on FHIR Wayne Kubick, CTO, HL7