HL7 FHIR DevDays 2020, Virtual Edition, November 17–20, 2020 | @FirelyTeam | #fhirdevdays | www.devdays.com/november-

2020

HL7®, FHIR® and the flame Design mark are the registered trademarks of Health Level Seven International and are used with permission.

Introduction to HL7® FHIR®

Simone Heckmann, Gefyra GmbH, HL7 Germany

1

Simone HeckmannCEO Gefyra GmbHTC Chair HL7 Germany

sh@gefyra.de

@GefyraGmbH

2

Health Level 7

● accredited ‘Standards Developing Organisation’ (SDO)

● organisation of volunteers worldwide

● Working Group Meetings, eMail-lists, phone

conferences...

● join any WG: http://www.hl7.org > Resources > ListServs >

subscribe

3

CDA R2

1986 1987 1988 1989 1990 1991 1992 1993 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 .. 2007 .. 2011 .. 2018..

First WGM

V1

V2 V2.1 V2.2

First IG

V2.3 V2.3.1

Arden

Syntax2.0

V2.4 V2.5 V2.6

CDA R1

FHIR

Foundation of

HL7 DE

Version3.0

CCOW

The History of HL7

4

HL7 Version 2

Status QuoThe old world

6

The new world

• Cloud based

• Query driven

• Open API

• JSON

• HTTP

A new vision

9

FHIR - The Acronym

• F = Fast

• H = Healthcare

• I = Interoperability

• R = Resources

10

The History of HL7 FHIR®

2011 ... 2012 ... 2013 ... 2014 … 2015 … 2016 … 2017 … 2018 … 2019 … 2020 … 2021 … 2022 … 2023 …

1. Connectathon

1. Draft DSTU1 DSTU2 STU3

R4(normative)

10. Connectathon

R6 (update)

18. Connectathon

R5 (update)

11

The FHIR Manifesto

• focus on implementers

• focus on the 80% solution

• focus on established webbased technologies

• focus on human readable information

• focus on the community

• focus on scalability

13

14

15

Narrative

Extensions

Elements

18

REST

Operations

everything else

MessagingStorage

Exchange Paradigms

19

get a resource from the WWW

19

20

get a resource from a FHIR Server

20

21

search the WWW

22

search a FHIR Server

23

FHIR and universal interoperability....

24

FHIR Implementation Guides are special

● they are machine and human readable

● they contain all required profiles for a specific use case

profiles can be used for validation, code an UI generation

● they provide syntactical and semantical interoperability

● they are FHIR resources (can be searched, accessed through API)

● they add the “I” to “FHIR” ☺

25

Resource

+ Extensions

+ Constraints

___________

= „Profile“

26

Find an Implementation Guide:http://www.fhir.org/guides/registry/

27

Never work alone…!

28

29