Out-of-the-box eHealth interoperability?

Ewout Kramere.kramer@furore.com

EHiN, november 4thm 2014

Fast(well, that’s relative)

HealthcareInteroperability(that’s what we need)

Resources(the web technology bit)

Focus on implementersKeep common scenarios simpleLeverage existing technologiesMake content freely available

FHIR Manifesto (abridged)

If your neighbour 's son can’t hack an app with <technology X> in a weekend…..

Focus on implementers

you won’t get adopted

6

www.programmableweb.com

REST

Slice & dice your data into “resources”

How many resources?Currently: about 60

• Administrative– Patient, Location, Encounter,

Organization, • Clinical Concepts

– AllergyIntolerance, Questionnaire, Observation

• Infrastructure– ValueSet, Composition, Profile,

Conformance

Next up…still about 60 to go

• Scheduling- Appointment, Availability, Slot

• Financial- Claim, Account, Coverage

• Consent• Devices

– Metric, DeviceComponent

• Care TransferFull support for C-CDA

Generic Specific

Flexibility vs. useability

Re-useable Single purpose

HL7v3 RIMHL7 CDA

C-CCD

openEHR RM

HL7v2

IHE PDQFHIR

openEHR Archetypes

openEHR Templates

HL7v3 CMETS

+ =

Cover the 80% out of the box…

Race

Middle name

Lunar Hijri birthdate

FHIR RepositoryStandardFHIR REST

CustomOperations

Read

Update

Search

Check Drug Interaction

MergePatient

Standardize with your partners…not the world

Conformance & Profile

Compliance

Publication

Guidance

Implementation

Find & maintain

Retrieve & use

Repository

Message

Document

REST

Packaging & transport

Yes, v2 style messagingis also supported! √Yes, v3 CDA style documentsare also supported!

√

Document from the resource to the wireHTTP/1.1 200 OKContent-Type: application/json;charset=utf-8Content-Length: 627Content-Location: /fhir/person/@1/history/@1Last-Modified: Tue, 29 May 2012 23:45:32 GMTETag: "1“

"Person":{"id":{"value":"1"},"identifier":[{"type":{"code":"ssn","system":"http://hl7.org/fhir/sid

What’s Next?

• Februari 2014 First Draft Standard for Trial Use (DSTU)– Semi-stable platform for implementers Additional DSTU versions

roughly annually to make fixes, introduce new resources

• June 2015 Second Draft Standard for Trial Use (DSTU2)• Normative – 2016?

– We want *lots* of implementation experience before committing to backward compatibility

17

pagina 18

International HL7 FHIR Developer Days

November 24-26, 2014 in Amsterdam

Education– 14 tutorials

Connectathon– Meet fellow developers– Put FHIR to the test

Networking– FHIR experts and authors on hand

http://fhir.furore.com/devdays

Questions?