HL7 FHIR & IHE MHD yet more choices IHE NL 2012 - Changing the Way Healthcare Connects Presentatie IHE-Jaarcongres Spant!, 9 november 2012 Ewout Kramer
Korte Introductie Mijn naam: Ewout Kramer Adviseur Integratietechnologie en Architectuur in de zorg bij Furore Gegevensstandaarden Gegevensmodellering HL7 Internationaal Co-auteur HL7 FHIR RIMBAA Medical Intelligence e.kramer@furore.com IHE jaarcongres 2012 #IHENL 2
de verschillende keuzes RMIM CCR Archetypes FHIR HL7 v3 Templates CEN CEM HL7 v2 openehr REST UML CMET HMD HTML SNOMED DCM CCD LRA CDA Implementatie XDS handleiding Affinity domain
Why so many choices? We re programmers. Programmers are, in their hearts, architects, and the first thing they want to do when they get to a site is to bulldoze the place flat and build something grand. Joel Spolsky -- Things you Should Never Do, Part I IHE jaarcongres 2012 #IHENL
Cover All Usecases, (N)ever Specific IHE PDQ IHE MDH HL7v2 CCD FHIR CDA R3 HL7v3 RIM Generic IHE jaarcongres 2012 #IHENL openehr RM EN13606 RM
Culprits #1 On the HL7 side.. Grahame G. Lloyd M. Ewout K.
Culprit #2 On the IHE side.. and probably many more John Moehrke
HL7 Fresh Look If someone is building a new ios healthcare app, what standard do we point them at? If a vendor wants to provide a simple to use API to cloud based, what standard should they extend? Actually, where the heck is the spec?
Interoperability in 2012
We need something simple for mobile devices to use XDS mmmmm.. IHE IT Infrastructure Technical Framework Supplement Mobile access to Health Documents 33, intro, line 235
The Mobile access to Health Documents (MHD) profile defines one standardized interface to health documents for use by mobile devices so that deployment of mobile applications is more consistent and reusable. These transactions leverage the metadata concepts from XDS, but simplify the technology requirements for access by mobile devices.
Cover All Usecases, (N)ever Specific IHE PDQ IHE MDH HL7v2 CCD FHIR CDA R3 HL7v3 RIM Generic IHE jaarcongres 2012 #IHENL openehr RM EN13606 RM
Profiling Resources address the most mainstream use-cases and leave the edge-cases for extensions Profile Person Race + ReligiousAffiliation Prescription + Problem + +
Support the 3 Paradigms Message Document n n REST n
MHD transactions a small set of transactions that map to REST IHE IT Infrastructure Technical Framework Supplement Mobile access to Health Documents 33.4.4, line 400
All the way to the wire GET fhir.furore.com/fhir/person/@1 {"Person":{"id":{"value":"1"},"identifier":[{"type":{"code":"ssn","system":"http://hl7.org/fhir/sid/fhir/identifiertype"},"identifier":{"system":"http://hl7.org/fhir/sid/usssn","id":"444222222"}}],"name":[{"use":"official","part":[{"type":"family","value":"Everywoman"},{"type":"give JSON n","value":"eve"}]}],"address":[{"use":"home","part":[{"type":"line","value":"2222 Home Street"}]}],"contact":[{"system": phone","value":"555-555-2003","use":"work"}],"dob":{"value":"1973-05- 31"},"gender":{"text":"F"},"text":{"status":"generated","div":"<div xmlns=\"http://www.w3.org/1999/xhtml\">everywoman, Eve. SSN: 444222222</div>"}}} <Person xmlns="http://hl7.org/fhir"><id>1</id><identifier><type><code>ssn</code><system>http://hl7.org/fhir/sid/fhir/ide ntifier-type</system></type><identifier><system>http://hl7.org/fhir/sid/usssn</system><id>444222222</id></identifier></identifier><name><use>official</use><part><type>family</type>< value>everywoman</value></part><part><type>given</type><value>eve</value></part></name><address><use XML >home</use><part><type>line</type><value>2222 Home Street</value></part></address><contact><system>phone</system><value>555-555- 2003</value><use>work</use></contact><dob>1973-05- 31</dob><gender><text>F</text></gender><text><status>generated</status><div xmlns="http://www.w3.org/1999/xhtml">everywoman, Eve. SSN: 444222222</div></text></Person> OMG hdata RESTful compliant interface
HL7 & IHE at Baltimore August 2012 Sept 2012
Why re-invent the wheel? HL7 FHIR HTTP + REST Resource-based modelling Xml, JSON and Atom HL7v3-based datatypes Structured documents, opaque documents IHE MHD HTTP + REST DocumentEntry etc. as resource Xml, JSON and Atom HL7v2 datatypes Opaque documents
FHIR Connectathon The excitement is not due to any one thing, nor any specific combination. It is not REST. It is not simple-xml or JSON. It is not Grahame. The excitement is driven by all of these factors converging at just the right time and place. John Moehrke Mike Henderson
HL7 FHIR offers Flexible, extensible datamodel Broad range of communication paradigms Implementable specification all the way to the wire
FHIR Getting Started Find the FHIR specification at: http://www.hl7.org/fhir Try it out: http://fhir.furore.com http://hl7connect.healthintersections.com.au /svc/fhir
ihe.net ihe-nl.org ihe-europe.net @IHENL