1 / 9

FHIR in 15

FHIR in 15. Lloyd McKenzie June 6, 2014. FHIR Manifesto. Focus on Implementers Target support for common scenarios Leverage cross-industry web technologies Require human readability as base level of interoperability Make content freely available

zola
Download Presentation

FHIR in 15

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. FHIR in 15 Lloyd McKenzie June 6, 2014

  2. FHIR Manifesto • Focus on Implementers • Target support for commonscenarios • Leverage cross-industry web technologies • Require human readability as base level of interoperability • Make content freely available • Support multiple paradigms & architectures • Demonstrate best practice governance

  3. Extension with reference to its definition Human Readable Summary • Standard Data Content: • MRN • Name • Gender • Date of Birth • Provider

  4. hl7.org/fhir (FHIR home)

  5. V2 and FHIR Similarities FHIR Differences Each chunk (resource) is independently addressable More than messages Human readable required Extensions don’t collide, are discoverable Modern tools/skills Instances easy to read Lighter, modern spec • Built around re-usable “chunks” of data • Strong forward/backward compatibility rules • Extensibility mechanism

  6. V3 and FHIR Similarities FHIR Differences Simpler models & syntax (reference model hidden) Friendly names Extensibility with discovery Easy inter-version wire compatibility Messages, documents, etc. use same syntax JSON syntax too • Based on RIM, vocab & ISO Data types foundations • Support XML syntax

  7. V3 and CDA Similarities FHIR Differences Can use out of the box – no templates required Not restricted to just documents Implementer tooling generated with spec (See v3 differences on prior slide) • Support profiling for specific use-cases • Human readability is minimum for interoperability • APIs, validation tooling, profile tooling • (See v3 similarities on prior slide)

  8. Timeline 2011-09 – Conceptual first draft published 2012-09 – 1st “draft for comment” ballot 2013-09 – 1st DSTU ballot 2014-01 – 1st DSTU published 2015-03 – 2nd DSTU published (approx) 2016? – First normative version Additional normative releases every 1-2 years

  9. Questions? http://hl7.org/fhirlloyd@lmckenzie.com

More Related