SlideShare une entreprise Scribd logo
1  sur  80
© 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
Introduction to
HL7® FHIR®
Ewout Kramer
FHIR Core team (and software developer)
Furore (Amsterdam, NL)
email: e.kramer@furore.com
web: http://thefhirplace.com
http://fhir.furore.com
skype: ewoutkramer
© 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
© 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
© 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
Relative – No technology can make integration as fast as we’d like
That’s why we’re here
Building blocks – more on these to follow
The Acronym
© 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
© 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
HL7 v2.0
© 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
?
HL7 v3
© 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
Focus on implementers
Keep common scenarios simple
Leverage existing technologies
Make content freely available
Invoke the community
© 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
If your neighbour 's son can’t
hack an app with
<your technology X>
in a weekend…..
you won’t get adopted
Focus on implementers..
© 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
THE RISE OF THE API
Background
10
© 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
Your “Mobile” device becomes the Big Aggregator and Coordinator of data and functionality
What I want from my
healthcare app
© 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
The API economy
12
Where companies expose their (internal) digital business assets or services in
the form of (web) APIs to third parties with the goal of unlocking additional
business value through the creation of new assets
© 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
3rd-party becomes the
norm
13
© 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
2012
The Rise of the API
2016
© 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
So what about HL7 &
FHIR?
 With FHIR, HL7 joins the ranks of the API troopers.
 But other than Twitter, Facebook etc. HL7 has no “services” or
“functionality” to offer
 FHIR is just a set of flexible standardized models and best-
practices that others can use to create healthcare API’s
 3rd-party (app/software) developers can then seamlessly connect
to your FHIR API.
© 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
App marketplace…
© 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
NO: Region Helse-Vest
© 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
EHR Vendors…
© 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
COMPONENTS OF FHIR
In-Depth
© 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
Divide health care data in discrete “building blocks”
MedicationPrescription Problem
A FHIR ‘Resource’
• Cover “the 80%”
• Unit of exchange
• Maintained & documented independently
• Have a textual description
© 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
Resources - example
© 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
Example – Patient
Resource
References
to other
Resources
© 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
References between
resources
A web of resources that can tell any story
© 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
Clinical Scenario
 First consultation
 Complaining of pain in the r) ear for 3 days
with an elevated temperature. On
examination, temperature 38.5 degrees and
an inflamed r) ear drum with no perforation.
Diagnosis Otitis Media, and prescribed
Amoxil 250mg TDS for 5 days
 Follow up consultation
 5 days later returned with an itchy skin rash.
No breathing difficulties. On examination,
urticarial rash on both arms. No evidence
meningitis. Diagnosis of penicillin allergy.
Antibiotics changed to erythromycin and
advised not to take penicillin in the future.
Condition
Observation
Med
Allergy
Encounter
5 year old boy
Patient
© 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
Resource view
© 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
Extending Patient
References
to other
Resources
Yes, but where are:
• citizenship
• mothersmaidenname,
• us-core-race
Don’t worry, you can add extensions: your own elements –
FHIR even defines a few favorite ones!
© 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
+ =
Cover the 80% out of the box…
Everyone needs
extensions…
Simple choice – design for absolutely
everything or allow extensions
Everyone needs extensions, everyone
hates them!
© 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
Resource Anatomy
28
© 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
Resource Anatomy
29
© 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
Exchange Patterns
30
REST
Documents Messages
Services
(API)
© 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
REST:“Repository”
model of healthcare
Hospital System
Create
Record
Create
Encounter
FHIR server
Patient Observation
Patient Patient
Order Observation
Observation
Diagnostic
Report
Notify new
Lab results
Update
Patient
data
Lab System
Post
Lab resultQuery
Lab orders
© 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
FHIR Messages
32
 Used to inform or
instruct
 Patient Admitted
 Lab result
available
 Similar to v2
messaging
© 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
FHIR Documents
33
 Use for ‘point in time’
record
 Discharge Summary
 Referral
 Similar to CDA
© 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
FHIR
Repository
Regardless of paradigm, the content is
the same
Lab System
FHIR
Message FHIR Document
National
Exchange
© 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
35
Questions?
(and then small break!)
© 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
WHY (UNIVERSAL)
STANDARDIZATION IS
HARD
36
© 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
1st: Ego’s
© 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
2nd: Cost
“Communicate first, standardize later”
“I need to be ready next month”
“Standardize first, communicate later”
“This needs to be done right, takes time”
CHAOS?
“He who ships code, wins”
© 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
Interoperability
 Interoperability: A model is agreed to that
allows all systems to exchange what needs to
be exchanged, without requiring any
design changes to the way their systems
works. 
 Well known deficiencies of this: semantic
scalability, fragmentation etc. 
39
© 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
Intraoperability
 Rework the core structures of the systems
to function in an agreed way. Because all
the systems work the same way, then
exchange between the systems is easy
and straight forward. 
 Intraoperability has fewer deficiencies, but
they are much bigger: it’s much harder to
get agreement… 
40
© 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
3rd: Different communities
and timelines
GP System –
Uses Prescriptions
Cancer Center –
Uses Prescriptions
Regional collaborations
– share prescriptions
Other regions – trying
the same thing
© 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
What can we do
promote interoperability
 Produce basic building blocks everyone needs. Quickly!
 Cooperate with your region/countries biggest players to
get them adopted
 Open up a (FHIR, openEHR) registry to promote reusable
profiles, patterns & practices.
 Let everyone publish their specialized “dialect” of FHIR
 Re-integrate when need arises (= there’s interest and
money)
 Promote, facilitate. Much more successful than
enforcement and subsidized projects.
© 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
“… the mad dreamers who tried to build a perfect
language” (terminology, information model)
A history lesson…
© 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
FHIR PROFILING
Adapting FHIR
© 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
The need for profiling
Need to be able to describe adaptations based
on use and context
 Which resources and elements are used?
 Which API features are used?
 Which terminologies are used?
 How to map these to local
requirements/implementations?
© 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
Layered profiles
 Country adapts a national profile
 Regions or specialties may develop
specialized versions of national profile
 Profile with use-case specific constraints
48
© 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
Constraining a resource
Demand that the identifier uses your
national patient identifier
Limit names to just 1 (instead of 0..*)
Limit maritalStatus to another set of
codes that extends the one from
HL7 international
Add an extension to support
“RaceCode”
Note: hardly any
mandatory elements in
the core spec!
© 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
Extensions
50 Note: could be JSON as well
Key = location of formal definition
Value = value according to definition
© 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
In v3 CDA…”text-based”
© 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
openEHR ADL
…computable!
© 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
FHIR:
StructureDefinition
53
Computable expression: as a Resource, just like Patient!
© 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
Adapting the API
54
FHIR ServerFHIR REST
Complex
Operations
Read
Update Search
Check Drug
Interaction
Merge
Patient
Expand
ValueSet
Validate
© 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
Conformance
Conformance Resources
55 55
“Implementation Guide”
Structure
Definition
SearchParam
Definition
ValueSet
Concept
Map
NamingSystem Operation
Definition
Forge
Excel
Implementation
Guide
TestScript
© 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
Implementation Guide
Pour in your Conformance resources and add human
narrative:
 Functional Requirement and Use case(s)
 Data definitions
 Actors and Interactions
 Examples
 Technical Implementation Guidance
 Security
 Help
 Contact Information
56
© 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
© 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
Publish!
58
Author & Store
Guide
Implementhttp://simplifier.net
http://registry.fhir.org
© 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
FHIR Registry
59
© 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
FUTURE PLANS
60
© 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
FHIR Timeline
2012 20162014 2018 2020
First
Draft
2011 20152013 2017 2019
1st
DSTU
2nd
DSTU
3rd
STU Normative
First
Connectathon!
Update 1
Updates every
18-24 months
© 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
October 2015 – DSTU2
Conformance
ValueSet, Conformance,
StructureDefinition,
OperationDefinition
Scheduling
Appointment, Schedule, Slot
Workflow / PC
CarePlan, Goal, Episode, Alert,
Communication, ReferralRequest,
DiagnosticOrder
IHE XDS (MHD)
DocumentReference
DocumentManifest
IHE PCD
DeviceComponent
DeviceMetric
DICOM
ImagingStudy, ImagingObjectSelection
AuditEvent (ATNA)
W3C
Provenance
> 1.000 requests for changes processed
number of resources more or less doubled to just over 100
© 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
During the year…
63
20172016
DSTU 2 STU 3
OctMayJan
Workgroup
Meeting
Workgroup
Meeting
Workgroup
Meeting
© 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
October 2016 – STU3
 New resources & support around:
 Clinical Decision Support
 Care coordination
 Workflow management
 Genomic data
 eClaims
 Provider directories
 CCDA profiles
 Consent management
 250 requests for changes processed (so far)
64
© 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
STU?
 Standard for TRIAL Use
 “Regardless of the degree of prior
implementation, all aspects of the FHIR
specification are potentially subject to
change.”
© 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
FHIR Maturity Model
66
Level 0: “Draft”, Just added to the spec for first review
Level 1: Ready for test implementation by pilots
Level 2: Pilots exist and have interoperated with in realistic scenarios
Level 3: Meets quality guidelines, formal ballot resulting in changes
Level 4: Tested, verified and stable. Backw. compatibility becomes a prio.
Level 5: Widely implemented across scope and jurisdictions. Frozen.
© 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
Going normative
 Iterative process
 First FMM level 4/5 in 2018
 From 2018 updates every 18-24 months
 More and more parts become level 4/5
67
© 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
THE FHIR COMMUNITY
Background
68
© 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
We exist now!
69
© 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
Where in the world?
70
2015 HAPI FHIR Test Server statistics
© 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
New products every day
71
© 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
HSPC
Argonaut
SMART
(on FHIR)
US Co-operations
72
FHIR
C-CDA 1.1
FHIR Profiles
(MU3)
Profiles,
OIDC/OAuth
Services
Intermountain Healthcare, Veterans Affiars, IBM, Epic, Cerner, Mayo, Kaiser, …
© 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
Gartner hype cycle
© 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
At your service
74
© 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
Connectathons
75
© 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
FHIR foundation
Home of the community (not the SDO):
 Implementers chats
 Calender of events, webcasts
 Repository of Extensions and profiles
 Showcases, repo of FHIR projects
 Best-practices & patterns
 Open-source initiatives
Located at http://fhir.org76
© 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
FINALLY…
77
© 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
Life on the FHIR core
team
© 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
Goal achieved?
 It is fast to learn, implement and troubleshoot
 It has a vibrant and open source community and
has frequently held hackathons.
 Matures because we get LOADS of feedback
 Spontaneous adoption (of a standard!)
79
© 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
But…
 We can only make the technology bit easier
 Interoperability is hard, and is a human
problem of common process and
understanding
 FHIR cannot fix this. And it is no silver bullet.
80
© 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
81
Questions?
(and then lunch!)
© 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
82
 Tutorials
 All the latest information on FHIR
 Connectathon
 Meet fellow developers
 Put FHIR to the test
 Networking
 FHIR experts and
authors on hand
http://fhir.furore.com/devdays

Contenu connexe

Tendances

Hl7 uk fhir the basics
Hl7 uk fhir the basicsHl7 uk fhir the basics
Hl7 uk fhir the basics
Ewout Kramer
 

Tendances (20)

FHIR tutorial - Afternoon
FHIR tutorial - AfternoonFHIR tutorial - Afternoon
FHIR tutorial - Afternoon
 
Introduction to FHIR™
Introduction to FHIR™Introduction to FHIR™
Introduction to FHIR™
 
Edifecs- warming up to fhir
Edifecs- warming up to fhirEdifecs- warming up to fhir
Edifecs- warming up to fhir
 
FHIR Search for client developers by Mirjam Baltus
FHIR Search for client developers by Mirjam BaltusFHIR Search for client developers by Mirjam Baltus
FHIR Search for client developers by Mirjam Baltus
 
Profile and validation by Grahame Grieve
Profile and validation by Grahame GrieveProfile and validation by Grahame Grieve
Profile and validation by Grahame Grieve
 
FHIR Search for server developers by Martijn Harthoorn
FHIR Search for server developers by Martijn HarthoornFHIR Search for server developers by Martijn Harthoorn
FHIR Search for server developers by Martijn Harthoorn
 
FHIR Tutorial - Morning
FHIR Tutorial - MorningFHIR Tutorial - Morning
FHIR Tutorial - Morning
 
FHIR overview at EHiN 2014, Oslo
FHIR overview at EHiN 2014, OsloFHIR overview at EHiN 2014, Oslo
FHIR overview at EHiN 2014, Oslo
 
SMART on FHIR by Scot Post van der Burg
SMART on FHIR by Scot Post van der BurgSMART on FHIR by Scot Post van der Burg
SMART on FHIR by Scot Post van der Burg
 
Vitalis 2016 FHIR App Development
Vitalis 2016 FHIR App DevelopmentVitalis 2016 FHIR App Development
Vitalis 2016 FHIR App Development
 
Security in FHIR with OAuth by Grahame Grieve
Security in FHIR with OAuth by Grahame GrieveSecurity in FHIR with OAuth by Grahame Grieve
Security in FHIR with OAuth by Grahame Grieve
 
FHIR Documents by Lloyd McKenzie
FHIR Documents by Lloyd McKenzieFHIR Documents by Lloyd McKenzie
FHIR Documents by Lloyd McKenzie
 
Advanced .NET API (Ewout)
Advanced .NET API (Ewout)Advanced .NET API (Ewout)
Advanced .NET API (Ewout)
 
FHIR intro and background at HL7 Germany 2014
FHIR intro and background at HL7 Germany 2014FHIR intro and background at HL7 Germany 2014
FHIR intro and background at HL7 Germany 2014
 
FHIR DevDays 2015 - introduction to FHIR
FHIR DevDays 2015 - introduction to FHIRFHIR DevDays 2015 - introduction to FHIR
FHIR DevDays 2015 - introduction to FHIR
 
Terminology, value-sets, codesystems by Lloyd McKenzie
Terminology, value-sets, codesystems by Lloyd McKenzieTerminology, value-sets, codesystems by Lloyd McKenzie
Terminology, value-sets, codesystems by Lloyd McKenzie
 
FHIR - more than the basics
FHIR - more than the basicsFHIR - more than the basics
FHIR - more than the basics
 
Hl7 uk fhir the basics
Hl7 uk fhir the basicsHl7 uk fhir the basics
Hl7 uk fhir the basics
 
Getting started with FHIR by Ewout Kramer
Getting started with FHIR by Ewout KramerGetting started with FHIR by Ewout Kramer
Getting started with FHIR by Ewout Kramer
 
Authoring profiles by Michel Rutten
Authoring profiles by Michel RuttenAuthoring profiles by Michel Rutten
Authoring profiles by Michel Rutten
 

En vedette

En vedette (19)

HL7 Fhir for Developers
HL7 Fhir for DevelopersHL7 Fhir for Developers
HL7 Fhir for Developers
 
FHIR API for .Net programmers by Mirjam Baltus
FHIR API for .Net programmers by Mirjam BaltusFHIR API for .Net programmers by Mirjam Baltus
FHIR API for .Net programmers by Mirjam Baltus
 
Rolling out FHIR - architecture and implementation considerations by Lloyd Mc...
Rolling out FHIR - architecture and implementation considerations by Lloyd Mc...Rolling out FHIR - architecture and implementation considerations by Lloyd Mc...
Rolling out FHIR - architecture and implementation considerations by Lloyd Mc...
 
HL7 för beslutsfattare
HL7 för beslutsfattareHL7 för beslutsfattare
HL7 för beslutsfattare
 
FHIR Client Development with .NET
FHIR Client Development with .NETFHIR Client Development with .NET
FHIR Client Development with .NET
 
A whistlestop tour of FHIR API authentication and authorization
A whistlestop tour of FHIR API authentication and authorizationA whistlestop tour of FHIR API authentication and authorization
A whistlestop tour of FHIR API authentication and authorization
 
FHIR Profiles
FHIR ProfilesFHIR Profiles
FHIR Profiles
 
Accessing SNOMED CT With FHIR Terminology Services
Accessing SNOMED CT With FHIR Terminology ServicesAccessing SNOMED CT With FHIR Terminology Services
Accessing SNOMED CT With FHIR Terminology Services
 
SMART on FHIR by Scot Post van der Burg
SMART on FHIR by Scot Post van der BurgSMART on FHIR by Scot Post van der Burg
SMART on FHIR by Scot Post van der Burg
 
FHIR architecture overview for non-programmers by René Spronk
FHIR architecture overview for non-programmers by René SpronkFHIR architecture overview for non-programmers by René Spronk
FHIR architecture overview for non-programmers by René Spronk
 
FHIR Server internals - sqlonfhir
FHIR Server internals - sqlonfhirFHIR Server internals - sqlonfhir
FHIR Server internals - sqlonfhir
 
Från Meddelandeutväxling till Semantisk Interoperabilitet
Från Meddelandeutväxling till Semantisk InteroperabilitetFrån Meddelandeutväxling till Semantisk Interoperabilitet
Från Meddelandeutväxling till Semantisk Interoperabilitet
 
HL7 Interoperability Standards Review
HL7 Interoperability Standards ReviewHL7 Interoperability Standards Review
HL7 Interoperability Standards Review
 
FHIR och interoperabilitet i sjukvården
FHIR och interoperabilitet i sjukvårdenFHIR och interoperabilitet i sjukvården
FHIR och interoperabilitet i sjukvården
 
Exploring HL7 CDA & Its Structures
Exploring HL7 CDA & Its StructuresExploring HL7 CDA & Its Structures
Exploring HL7 CDA & Its Structures
 
Hl7 2016 baltimore connectathon provider directories and scheduling
Hl7 2016 baltimore connectathon provider directories and schedulingHl7 2016 baltimore connectathon provider directories and scheduling
Hl7 2016 baltimore connectathon provider directories and scheduling
 
CCDs or QRDAs for eCQM Reporting
CCDs or QRDAs for eCQM ReportingCCDs or QRDAs for eCQM Reporting
CCDs or QRDAs for eCQM Reporting
 
Route from CCDA to FHIR by Grahame Grieve
Route from CCDA to FHIR by Grahame GrieveRoute from CCDA to FHIR by Grahame Grieve
Route from CCDA to FHIR by Grahame Grieve
 
Cda
CdaCda
Cda
 

Similaire à Vitalis 2016 FHIR Introduction

Similaire à Vitalis 2016 FHIR Introduction (12)

FHIR and DICOM by Marten Smits
FHIR and DICOM by Marten SmitsFHIR and DICOM by Marten Smits
FHIR and DICOM by Marten Smits
 
Terminology, value-sets, codesystems by Lloyd McKenzie
Terminology, value-sets, codesystems by Lloyd McKenzieTerminology, value-sets, codesystems by Lloyd McKenzie
Terminology, value-sets, codesystems by Lloyd McKenzie
 
FHIR: What's it All About?
FHIR: What's it All About?FHIR: What's it All About?
FHIR: What's it All About?
 
Validation in net and java (ewout james)
Validation in net and java (ewout james)Validation in net and java (ewout james)
Validation in net and java (ewout james)
 
Route from CCDA to FHIR by Grahame Grieve
Route from CCDA to FHIR by Grahame GrieveRoute from CCDA to FHIR by Grahame Grieve
Route from CCDA to FHIR by Grahame Grieve
 
03 FHIR Deep dive - 20191116 v2.pptx
03 FHIR Deep dive - 20191116 v2.pptx03 FHIR Deep dive - 20191116 v2.pptx
03 FHIR Deep dive - 20191116 v2.pptx
 
STATE OF MOBILE HEALTH on FHIR by Gora Datta at ScaleLA
STATE OF MOBILE HEALTH on FHIR by Gora Datta at ScaleLASTATE OF MOBILE HEALTH on FHIR by Gora Datta at ScaleLA
STATE OF MOBILE HEALTH on FHIR by Gora Datta at ScaleLA
 
Structure definition 101 (ewout)
Structure definition 101 (ewout)Structure definition 101 (ewout)
Structure definition 101 (ewout)
 
FHIR API for Java programmers by James Agnew
FHIR API for Java programmers by James AgnewFHIR API for Java programmers by James Agnew
FHIR API for Java programmers by James Agnew
 
FHIR.pptx
FHIR.pptxFHIR.pptx
FHIR.pptx
 
Fhir path (ewout)
Fhir path (ewout)Fhir path (ewout)
Fhir path (ewout)
 
Advanced .net api (ewout)
Advanced .net api (ewout)Advanced .net api (ewout)
Advanced .net api (ewout)
 

Dernier

💚 Punjabi Call Girls In Chandigarh 💯Lucky 🔝8868886958🔝Call Girl In Chandigarh
💚 Punjabi Call Girls In Chandigarh 💯Lucky 🔝8868886958🔝Call Girl In Chandigarh💚 Punjabi Call Girls In Chandigarh 💯Lucky 🔝8868886958🔝Call Girl In Chandigarh
💚 Punjabi Call Girls In Chandigarh 💯Lucky 🔝8868886958🔝Call Girl In Chandigarh
Sheetaleventcompany
 
raisen Call Girls 👙 6297143586 👙 Genuine WhatsApp Number for Real Meet
raisen Call Girls 👙 6297143586 👙 Genuine WhatsApp Number for Real Meetraisen Call Girls 👙 6297143586 👙 Genuine WhatsApp Number for Real Meet
raisen Call Girls 👙 6297143586 👙 Genuine WhatsApp Number for Real Meet
Call Girls Service
 
Patna Call Girls 👙 6297143586 👙 Genuine WhatsApp Number for Real Meet
Patna Call Girls 👙 6297143586 👙 Genuine WhatsApp Number for Real MeetPatna Call Girls 👙 6297143586 👙 Genuine WhatsApp Number for Real Meet
Patna Call Girls 👙 6297143586 👙 Genuine WhatsApp Number for Real Meet
Call Girls Service
 
dhanbad Call Girls 👙 6297143586 👙 Genuine WhatsApp Number for Real Meet
dhanbad Call Girls 👙 6297143586 👙 Genuine WhatsApp Number for Real Meetdhanbad Call Girls 👙 6297143586 👙 Genuine WhatsApp Number for Real Meet
dhanbad Call Girls 👙 6297143586 👙 Genuine WhatsApp Number for Real Meet
Call Girls Service
 
Bhagalpur Call Girls 👙 6297143586 👙 Genuine WhatsApp Number for Real Meet
Bhagalpur Call Girls 👙 6297143586 👙 Genuine WhatsApp Number for Real MeetBhagalpur Call Girls 👙 6297143586 👙 Genuine WhatsApp Number for Real Meet
Bhagalpur Call Girls 👙 6297143586 👙 Genuine WhatsApp Number for Real Meet
Call Girls Service
 
Ozhukarai Call Girls 👙 6297143586 👙 Genuine WhatsApp Number for Real Meet
Ozhukarai Call Girls 👙 6297143586 👙 Genuine WhatsApp Number for Real MeetOzhukarai Call Girls 👙 6297143586 👙 Genuine WhatsApp Number for Real Meet
Ozhukarai Call Girls 👙 6297143586 👙 Genuine WhatsApp Number for Real Meet
Call Girls Service
 
dehradun Call Girls 👙 6297143586 👙 Genuine WhatsApp Number for Real Meet
dehradun Call Girls 👙 6297143586 👙 Genuine WhatsApp Number for Real Meetdehradun Call Girls 👙 6297143586 👙 Genuine WhatsApp Number for Real Meet
dehradun Call Girls 👙 6297143586 👙 Genuine WhatsApp Number for Real Meet
Call Girls Service
 
Nanded Call Girls 👙 6297143586 👙 Genuine WhatsApp Number for Real Meet
Nanded Call Girls 👙 6297143586 👙 Genuine WhatsApp Number for Real MeetNanded Call Girls 👙 6297143586 👙 Genuine WhatsApp Number for Real Meet
Nanded Call Girls 👙 6297143586 👙 Genuine WhatsApp Number for Real Meet
Call Girls Service
 
Best Lahore Escorts 😮‍💨03250114445 || VIP escorts in Lahore
Best Lahore Escorts 😮‍💨03250114445 || VIP escorts in LahoreBest Lahore Escorts 😮‍💨03250114445 || VIP escorts in Lahore
Best Lahore Escorts 😮‍💨03250114445 || VIP escorts in Lahore
Deny Daniel
 
palanpur Call Girls 👙 6297143586 👙 Genuine WhatsApp Number for Real Meet
palanpur Call Girls 👙 6297143586 👙 Genuine WhatsApp Number for Real Meetpalanpur Call Girls 👙 6297143586 👙 Genuine WhatsApp Number for Real Meet
palanpur Call Girls 👙 6297143586 👙 Genuine WhatsApp Number for Real Meet
Call Girls Service
 
Mathura Call Girls 👙 6297143586 👙 Genuine WhatsApp Number for Real Meet
Mathura Call Girls 👙 6297143586 👙 Genuine WhatsApp Number for Real MeetMathura Call Girls 👙 6297143586 👙 Genuine WhatsApp Number for Real Meet
Mathura Call Girls 👙 6297143586 👙 Genuine WhatsApp Number for Real Meet
Call Girls Service
 
Russian Call Girls in Noida Pallavi 9711199171 High Class Call Girl Near Me
Russian Call Girls in Noida Pallavi 9711199171 High Class Call Girl Near MeRussian Call Girls in Noida Pallavi 9711199171 High Class Call Girl Near Me
Russian Call Girls in Noida Pallavi 9711199171 High Class Call Girl Near Me
mriyagarg453
 
Call Girls Service Anantapur 📲 6297143586 Book Now VIP Call Girls in Anantapur
Call Girls Service Anantapur 📲 6297143586 Book Now VIP Call Girls in AnantapurCall Girls Service Anantapur 📲 6297143586 Book Now VIP Call Girls in Anantapur
Call Girls Service Anantapur 📲 6297143586 Book Now VIP Call Girls in Anantapur
gragmanisha42
 
Hubli Call Girls 👙 6297143586 👙 Genuine WhatsApp Number for Real Meet
Hubli Call Girls 👙 6297143586 👙 Genuine WhatsApp Number for Real MeetHubli Call Girls 👙 6297143586 👙 Genuine WhatsApp Number for Real Meet
Hubli Call Girls 👙 6297143586 👙 Genuine WhatsApp Number for Real Meet
Call Girls Service
 

Dernier (20)

💚 Punjabi Call Girls In Chandigarh 💯Lucky 🔝8868886958🔝Call Girl In Chandigarh
💚 Punjabi Call Girls In Chandigarh 💯Lucky 🔝8868886958🔝Call Girl In Chandigarh💚 Punjabi Call Girls In Chandigarh 💯Lucky 🔝8868886958🔝Call Girl In Chandigarh
💚 Punjabi Call Girls In Chandigarh 💯Lucky 🔝8868886958🔝Call Girl In Chandigarh
 
Dehradun Call Girls 8854095900 Call Girl in Dehradun Uttrakhand
Dehradun Call Girls 8854095900 Call Girl in Dehradun  UttrakhandDehradun Call Girls 8854095900 Call Girl in Dehradun  Uttrakhand
Dehradun Call Girls 8854095900 Call Girl in Dehradun Uttrakhand
 
raisen Call Girls 👙 6297143586 👙 Genuine WhatsApp Number for Real Meet
raisen Call Girls 👙 6297143586 👙 Genuine WhatsApp Number for Real Meetraisen Call Girls 👙 6297143586 👙 Genuine WhatsApp Number for Real Meet
raisen Call Girls 👙 6297143586 👙 Genuine WhatsApp Number for Real Meet
 
Patna Call Girls 👙 6297143586 👙 Genuine WhatsApp Number for Real Meet
Patna Call Girls 👙 6297143586 👙 Genuine WhatsApp Number for Real MeetPatna Call Girls 👙 6297143586 👙 Genuine WhatsApp Number for Real Meet
Patna Call Girls 👙 6297143586 👙 Genuine WhatsApp Number for Real Meet
 
dhanbad Call Girls 👙 6297143586 👙 Genuine WhatsApp Number for Real Meet
dhanbad Call Girls 👙 6297143586 👙 Genuine WhatsApp Number for Real Meetdhanbad Call Girls 👙 6297143586 👙 Genuine WhatsApp Number for Real Meet
dhanbad Call Girls 👙 6297143586 👙 Genuine WhatsApp Number for Real Meet
 
Bhagalpur Call Girls 👙 6297143586 👙 Genuine WhatsApp Number for Real Meet
Bhagalpur Call Girls 👙 6297143586 👙 Genuine WhatsApp Number for Real MeetBhagalpur Call Girls 👙 6297143586 👙 Genuine WhatsApp Number for Real Meet
Bhagalpur Call Girls 👙 6297143586 👙 Genuine WhatsApp Number for Real Meet
 
Call Girls Patiala Just Call 8250077686 Top Class Call Girl Service Available
Call Girls Patiala Just Call 8250077686 Top Class Call Girl Service AvailableCall Girls Patiala Just Call 8250077686 Top Class Call Girl Service Available
Call Girls Patiala Just Call 8250077686 Top Class Call Girl Service Available
 
Ozhukarai Call Girls 👙 6297143586 👙 Genuine WhatsApp Number for Real Meet
Ozhukarai Call Girls 👙 6297143586 👙 Genuine WhatsApp Number for Real MeetOzhukarai Call Girls 👙 6297143586 👙 Genuine WhatsApp Number for Real Meet
Ozhukarai Call Girls 👙 6297143586 👙 Genuine WhatsApp Number for Real Meet
 
Call Girls Thane Just Call 9907093804 Top Class Call Girl Service Available
Call Girls Thane Just Call 9907093804 Top Class Call Girl Service AvailableCall Girls Thane Just Call 9907093804 Top Class Call Girl Service Available
Call Girls Thane Just Call 9907093804 Top Class Call Girl Service Available
 
dehradun Call Girls 👙 6297143586 👙 Genuine WhatsApp Number for Real Meet
dehradun Call Girls 👙 6297143586 👙 Genuine WhatsApp Number for Real Meetdehradun Call Girls 👙 6297143586 👙 Genuine WhatsApp Number for Real Meet
dehradun Call Girls 👙 6297143586 👙 Genuine WhatsApp Number for Real Meet
 
Nanded Call Girls 👙 6297143586 👙 Genuine WhatsApp Number for Real Meet
Nanded Call Girls 👙 6297143586 👙 Genuine WhatsApp Number for Real MeetNanded Call Girls 👙 6297143586 👙 Genuine WhatsApp Number for Real Meet
Nanded Call Girls 👙 6297143586 👙 Genuine WhatsApp Number for Real Meet
 
Best Lahore Escorts 😮‍💨03250114445 || VIP escorts in Lahore
Best Lahore Escorts 😮‍💨03250114445 || VIP escorts in LahoreBest Lahore Escorts 😮‍💨03250114445 || VIP escorts in Lahore
Best Lahore Escorts 😮‍💨03250114445 || VIP escorts in Lahore
 
Independent Call Girls Hyderabad 💋 9352988975 💋 Genuine WhatsApp Number for R...
Independent Call Girls Hyderabad 💋 9352988975 💋 Genuine WhatsApp Number for R...Independent Call Girls Hyderabad 💋 9352988975 💋 Genuine WhatsApp Number for R...
Independent Call Girls Hyderabad 💋 9352988975 💋 Genuine WhatsApp Number for R...
 
palanpur Call Girls 👙 6297143586 👙 Genuine WhatsApp Number for Real Meet
palanpur Call Girls 👙 6297143586 👙 Genuine WhatsApp Number for Real Meetpalanpur Call Girls 👙 6297143586 👙 Genuine WhatsApp Number for Real Meet
palanpur Call Girls 👙 6297143586 👙 Genuine WhatsApp Number for Real Meet
 
Mathura Call Girls 👙 6297143586 👙 Genuine WhatsApp Number for Real Meet
Mathura Call Girls 👙 6297143586 👙 Genuine WhatsApp Number for Real MeetMathura Call Girls 👙 6297143586 👙 Genuine WhatsApp Number for Real Meet
Mathura Call Girls 👙 6297143586 👙 Genuine WhatsApp Number for Real Meet
 
Russian Call Girls in Noida Pallavi 9711199171 High Class Call Girl Near Me
Russian Call Girls in Noida Pallavi 9711199171 High Class Call Girl Near MeRussian Call Girls in Noida Pallavi 9711199171 High Class Call Girl Near Me
Russian Call Girls in Noida Pallavi 9711199171 High Class Call Girl Near Me
 
Escorts Service Ahmedabad🌹6367187148 🌹 No Need For Advance Payments
Escorts Service Ahmedabad🌹6367187148 🌹 No Need For Advance PaymentsEscorts Service Ahmedabad🌹6367187148 🌹 No Need For Advance Payments
Escorts Service Ahmedabad🌹6367187148 🌹 No Need For Advance Payments
 
Call Girls Service Anantapur 📲 6297143586 Book Now VIP Call Girls in Anantapur
Call Girls Service Anantapur 📲 6297143586 Book Now VIP Call Girls in AnantapurCall Girls Service Anantapur 📲 6297143586 Book Now VIP Call Girls in Anantapur
Call Girls Service Anantapur 📲 6297143586 Book Now VIP Call Girls in Anantapur
 
Hubli Call Girls 👙 6297143586 👙 Genuine WhatsApp Number for Real Meet
Hubli Call Girls 👙 6297143586 👙 Genuine WhatsApp Number for Real MeetHubli Call Girls 👙 6297143586 👙 Genuine WhatsApp Number for Real Meet
Hubli Call Girls 👙 6297143586 👙 Genuine WhatsApp Number for Real Meet
 
Jaipur Call Girls 9257276172 Call Girl in Jaipur Rajasthan
Jaipur Call Girls 9257276172 Call Girl in Jaipur RajasthanJaipur Call Girls 9257276172 Call Girl in Jaipur Rajasthan
Jaipur Call Girls 9257276172 Call Girl in Jaipur Rajasthan
 

Vitalis 2016 FHIR Introduction

  • 1. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. Introduction to HL7® FHIR® Ewout Kramer FHIR Core team (and software developer) Furore (Amsterdam, NL) email: e.kramer@furore.com web: http://thefhirplace.com http://fhir.furore.com skype: ewoutkramer
  • 2. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
  • 3. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
  • 4. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. Relative – No technology can make integration as fast as we’d like That’s why we’re here Building blocks – more on these to follow The Acronym
  • 5. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
  • 6. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. HL7 v2.0
  • 7. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. ? HL7 v3
  • 8. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. Focus on implementers Keep common scenarios simple Leverage existing technologies Make content freely available Invoke the community
  • 9. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. If your neighbour 's son can’t hack an app with <your technology X> in a weekend….. you won’t get adopted Focus on implementers..
  • 10. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. THE RISE OF THE API Background 10
  • 11. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. Your “Mobile” device becomes the Big Aggregator and Coordinator of data and functionality What I want from my healthcare app
  • 12. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. The API economy 12 Where companies expose their (internal) digital business assets or services in the form of (web) APIs to third parties with the goal of unlocking additional business value through the creation of new assets
  • 13. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. 3rd-party becomes the norm 13
  • 14. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. 2012 The Rise of the API 2016
  • 15. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. So what about HL7 & FHIR?  With FHIR, HL7 joins the ranks of the API troopers.  But other than Twitter, Facebook etc. HL7 has no “services” or “functionality” to offer  FHIR is just a set of flexible standardized models and best- practices that others can use to create healthcare API’s  3rd-party (app/software) developers can then seamlessly connect to your FHIR API.
  • 16. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. App marketplace…
  • 17. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. NO: Region Helse-Vest
  • 18. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. EHR Vendors…
  • 19. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. COMPONENTS OF FHIR In-Depth
  • 20. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. Divide health care data in discrete “building blocks” MedicationPrescription Problem A FHIR ‘Resource’ • Cover “the 80%” • Unit of exchange • Maintained & documented independently • Have a textual description
  • 21. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. Resources - example
  • 22. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. Example – Patient Resource References to other Resources
  • 23. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. References between resources A web of resources that can tell any story
  • 24. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. Clinical Scenario  First consultation  Complaining of pain in the r) ear for 3 days with an elevated temperature. On examination, temperature 38.5 degrees and an inflamed r) ear drum with no perforation. Diagnosis Otitis Media, and prescribed Amoxil 250mg TDS for 5 days  Follow up consultation  5 days later returned with an itchy skin rash. No breathing difficulties. On examination, urticarial rash on both arms. No evidence meningitis. Diagnosis of penicillin allergy. Antibiotics changed to erythromycin and advised not to take penicillin in the future. Condition Observation Med Allergy Encounter 5 year old boy Patient
  • 25. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. Resource view
  • 26. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. Extending Patient References to other Resources Yes, but where are: • citizenship • mothersmaidenname, • us-core-race Don’t worry, you can add extensions: your own elements – FHIR even defines a few favorite ones!
  • 27. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. + = Cover the 80% out of the box… Everyone needs extensions… Simple choice – design for absolutely everything or allow extensions Everyone needs extensions, everyone hates them!
  • 28. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. Resource Anatomy 28
  • 29. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. Resource Anatomy 29
  • 30. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. Exchange Patterns 30 REST Documents Messages Services (API)
  • 31. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. REST:“Repository” model of healthcare Hospital System Create Record Create Encounter FHIR server Patient Observation Patient Patient Order Observation Observation Diagnostic Report Notify new Lab results Update Patient data Lab System Post Lab resultQuery Lab orders
  • 32. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. FHIR Messages 32  Used to inform or instruct  Patient Admitted  Lab result available  Similar to v2 messaging
  • 33. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. FHIR Documents 33  Use for ‘point in time’ record  Discharge Summary  Referral  Similar to CDA
  • 34. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. FHIR Repository Regardless of paradigm, the content is the same Lab System FHIR Message FHIR Document National Exchange
  • 35. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. 35 Questions? (and then small break!)
  • 36. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. WHY (UNIVERSAL) STANDARDIZATION IS HARD 36
  • 37. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. 1st: Ego’s
  • 38. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. 2nd: Cost “Communicate first, standardize later” “I need to be ready next month” “Standardize first, communicate later” “This needs to be done right, takes time” CHAOS? “He who ships code, wins”
  • 39. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. Interoperability  Interoperability: A model is agreed to that allows all systems to exchange what needs to be exchanged, without requiring any design changes to the way their systems works.   Well known deficiencies of this: semantic scalability, fragmentation etc.  39
  • 40. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. Intraoperability  Rework the core structures of the systems to function in an agreed way. Because all the systems work the same way, then exchange between the systems is easy and straight forward.   Intraoperability has fewer deficiencies, but they are much bigger: it’s much harder to get agreement…  40
  • 41. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. 3rd: Different communities and timelines GP System – Uses Prescriptions Cancer Center – Uses Prescriptions Regional collaborations – share prescriptions Other regions – trying the same thing
  • 42. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. What can we do promote interoperability  Produce basic building blocks everyone needs. Quickly!  Cooperate with your region/countries biggest players to get them adopted  Open up a (FHIR, openEHR) registry to promote reusable profiles, patterns & practices.  Let everyone publish their specialized “dialect” of FHIR  Re-integrate when need arises (= there’s interest and money)  Promote, facilitate. Much more successful than enforcement and subsidized projects.
  • 43. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. “… the mad dreamers who tried to build a perfect language” (terminology, information model) A history lesson…
  • 44. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. FHIR PROFILING Adapting FHIR
  • 45. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. The need for profiling Need to be able to describe adaptations based on use and context  Which resources and elements are used?  Which API features are used?  Which terminologies are used?  How to map these to local requirements/implementations?
  • 46. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. Layered profiles  Country adapts a national profile  Regions or specialties may develop specialized versions of national profile  Profile with use-case specific constraints 48
  • 47. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. Constraining a resource Demand that the identifier uses your national patient identifier Limit names to just 1 (instead of 0..*) Limit maritalStatus to another set of codes that extends the one from HL7 international Add an extension to support “RaceCode” Note: hardly any mandatory elements in the core spec!
  • 48. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. Extensions 50 Note: could be JSON as well Key = location of formal definition Value = value according to definition
  • 49. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. In v3 CDA…”text-based”
  • 50. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. openEHR ADL …computable!
  • 51. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. FHIR: StructureDefinition 53 Computable expression: as a Resource, just like Patient!
  • 52. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. Adapting the API 54 FHIR ServerFHIR REST Complex Operations Read Update Search Check Drug Interaction Merge Patient Expand ValueSet Validate
  • 53. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. Conformance Conformance Resources 55 55 “Implementation Guide” Structure Definition SearchParam Definition ValueSet Concept Map NamingSystem Operation Definition Forge Excel Implementation Guide TestScript
  • 54. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. Implementation Guide Pour in your Conformance resources and add human narrative:  Functional Requirement and Use case(s)  Data definitions  Actors and Interactions  Examples  Technical Implementation Guidance  Security  Help  Contact Information 56
  • 55. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office.
  • 56. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. Publish! 58 Author & Store Guide Implementhttp://simplifier.net http://registry.fhir.org
  • 57. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. FHIR Registry 59
  • 58. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. FUTURE PLANS 60
  • 59. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. FHIR Timeline 2012 20162014 2018 2020 First Draft 2011 20152013 2017 2019 1st DSTU 2nd DSTU 3rd STU Normative First Connectathon! Update 1 Updates every 18-24 months
  • 60. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. October 2015 – DSTU2 Conformance ValueSet, Conformance, StructureDefinition, OperationDefinition Scheduling Appointment, Schedule, Slot Workflow / PC CarePlan, Goal, Episode, Alert, Communication, ReferralRequest, DiagnosticOrder IHE XDS (MHD) DocumentReference DocumentManifest IHE PCD DeviceComponent DeviceMetric DICOM ImagingStudy, ImagingObjectSelection AuditEvent (ATNA) W3C Provenance > 1.000 requests for changes processed number of resources more or less doubled to just over 100
  • 61. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. During the year… 63 20172016 DSTU 2 STU 3 OctMayJan Workgroup Meeting Workgroup Meeting Workgroup Meeting
  • 62. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. October 2016 – STU3  New resources & support around:  Clinical Decision Support  Care coordination  Workflow management  Genomic data  eClaims  Provider directories  CCDA profiles  Consent management  250 requests for changes processed (so far) 64
  • 63. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. STU?  Standard for TRIAL Use  “Regardless of the degree of prior implementation, all aspects of the FHIR specification are potentially subject to change.”
  • 64. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. FHIR Maturity Model 66 Level 0: “Draft”, Just added to the spec for first review Level 1: Ready for test implementation by pilots Level 2: Pilots exist and have interoperated with in realistic scenarios Level 3: Meets quality guidelines, formal ballot resulting in changes Level 4: Tested, verified and stable. Backw. compatibility becomes a prio. Level 5: Widely implemented across scope and jurisdictions. Frozen.
  • 65. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. Going normative  Iterative process  First FMM level 4/5 in 2018  From 2018 updates every 18-24 months  More and more parts become level 4/5 67
  • 66. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. THE FHIR COMMUNITY Background 68
  • 67. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. We exist now! 69
  • 68. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. Where in the world? 70 2015 HAPI FHIR Test Server statistics
  • 69. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. New products every day 71
  • 70. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. HSPC Argonaut SMART (on FHIR) US Co-operations 72 FHIR C-CDA 1.1 FHIR Profiles (MU3) Profiles, OIDC/OAuth Services Intermountain Healthcare, Veterans Affiars, IBM, Epic, Cerner, Mayo, Kaiser, …
  • 71. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. Gartner hype cycle
  • 72. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. At your service 74
  • 73. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. Connectathons 75
  • 74. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. FHIR foundation Home of the community (not the SDO):  Implementers chats  Calender of events, webcasts  Repository of Extensions and profiles  Showcases, repo of FHIR projects  Best-practices & patterns  Open-source initiatives Located at http://fhir.org76
  • 75. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. FINALLY… 77
  • 76. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. Life on the FHIR core team
  • 77. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. Goal achieved?  It is fast to learn, implement and troubleshoot  It has a vibrant and open source community and has frequently held hackathons.  Matures because we get LOADS of feedback  Spontaneous adoption (of a standard!) 79
  • 78. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. But…  We can only make the technology bit easier  Interoperability is hard, and is a human problem of common process and understanding  FHIR cannot fix this. And it is no silver bullet. 80
  • 79. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. 81 Questions? (and then lunch!)
  • 80. © 2014 HL7 ® International. Licensed under Creative Commons. HL7 & Health Level Seven are registered trademarks of Health Level Seven International. Reg. U.S. TM Office. 82  Tutorials  All the latest information on FHIR  Connectathon  Meet fellow developers  Put FHIR to the test  Networking  FHIR experts and authors on hand http://fhir.furore.com/devdays

Notes de l'éditeur

  1. 0:10
  2. The big aggregator – the extreme case is Apple HealthKit
  3. Dit wordt mogelijk gemaakt doordat systemen hun interne data en business processen aanbieden voor externe ontwikkelaars Op een gecontroleerde wijze – via een goed ontworpen “API” Dat was vroeger een term voor nerds, nu mag het in de board room: het is een manier van zakendoen
  4. Niet langer lijm je mensen door ze naar je website te halen, en daar diensten aan te bieden Maar steeds meer zorg je ervoor dat anderen apps kunnen bouwen waarmee zij jouw dienstenpakket versterken en aanvullen Salesforce.com generates more than half of its $2.3 billion in revenue through its APIs, not its user interfaces. Twitter is said to process 13 billion transactions a day through its APIs. Google is around 5 billion transactions a day. For it’s part, Amazon is rapidly closing in on a trillion transactions. Not bad for an online bookseller. Your portal becomes a small part of the total traffic to your sites
  5. “API” was a low-level term, but now it is about how a larger part of patient/client facing software is depending on how business start to expose their data and processes to client-facing software so it can be integrated in a larger whole. Again: Don’t expect you or your portal to be the center of the world, be humble
  6. Now I hear you say: well this is all about today newest and hottest, mobile. But we need to realize that although the conventional markets stay, a larger and larger part will be about these consumer facing devices and software, the rest just operates in the background. And HL7 really needed to get back into that part of the market. We need these others to make FHIR popular. App developers will communicate with innovative health solution providers and the big EHR vendors and only then realize that they are using a standardized API called FHIR.
  7. 0:20
  8. Readily useable, contain “the 80%” (What’s the 80%...what’s maximum reuse? That’s HL7’s core business!) Independent of context, fixed defined behaviour and meaning Can reference each other Units of exchange – suggests units of storage for implementers Addressed through HTTP or other methods
  9. This is a critical concept in FHIR – the ability to reference between resources in a ‘web’ of relationships. Also n
  10. Save resources to EHR using REST (+/- transaction), package as a document for the
  11. You can constrain away stuff you don’t need You can add stuff to the basic models for your usecase “Remove and add bricks as necessary”
  12. Build a resource in clinFHIR
  13. Build a resource in clinFHIR
  14. For each one – when to use
  15. “Standardize” medical data like “Patient”, “Order”, etc. These are resources “Standardize” how to create/query/do notifications of this data
  16. 0:45
  17. Though micro USB might be the exception ;-) Why isn’t there a world standard for A/C plugs? They sprung up in different locations, the cost of using an adapter is small (220/110?).
  18. These vendors (and the hipster connecting to them) have only one need: communication. We have to enable them to produce software that enables better healthcare. We just should not be in the way. We may have focused on the inherent value of standardization and universal semantic operability. When the “standardizers” realize not many comply to the standards, a normal reaction is to ask an authority or government to force vendors to comply. This works only incidentally, and is often costly. It would be better if the vendors have motives to comply, rather than a financial impetus. True for whole countries too (“yeah, country X started with a pilot and then they produced their local dialect ”)
  19. “Drive-by” or “bottom-up” operability: “Communicate first, standardize later” First, business partners. Then, collaborations, communities. Maybe, finally, nation-wide It’s a natural process that people will want to make it work first, then only coordinate what they really need to, and then realize they can broaden their approach to a community. “Support”, of course top-down should still be possible! Maybe even a combi in the long-term You don’t need a central authority to model your data, before you can start.
  20. “Then again, we’re not Facebook or Twitter…..we do not write an API just for our own needs….we need to be everything to everyone…..now, how can we do that?”
  21. FHIR standardizes “the 80%”, but embraces adaption so there’s 20% that can be used to invent your own models and functionality Premise seems to be that all communication needs to be standardized or put into a framework before communication can be successful. I think that we just have to focus on enabling the software vendors to search each group. Even if that means they’ll all be talking dialects What language need to be standardized, depends on the context of communication. Within colleagues (in outside the same hospital), with other specialties, with the patient. Each has a bit of shared language, and “specialized” terms – we call it “jargon”.
  22. Wie nog verder geïnspireerd wil raken: Een boek over eeuwenlang falen om talen te standaardiseren en minder dubbelzinnig te maken. Verplicht leesvoer voor terminologen en kennisredeneerders. John Wilkins 1686 (en de Grieken) James Cooke Brown (1988)
  23. 0:10
  24. Also: TestScript resource
  25. Authoring workflow  Publishing workflow
  26. Demo!
  27. 0:25
  28. Note that dates are subject to change based on resources and the standards process
  29. 0:35
  30. 0:45
  31. 0:50