1 / 17

FHIR/ RfH ..... What is it ? And what’s next? Furore Ewout Kramer

FHIR/ RfH ..... What is it ? And what’s next? Furore Ewout Kramer. Disclaimer. FHIR is very early in the stages of its development Things may evolve differently than presented here While I’m reasonably involved, I’m not an expert This is an ideal time to influence outcomes. 2.

sevita
Download Presentation

FHIR/ RfH ..... What is it ? And what’s next? Furore Ewout Kramer

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/RfH.....What is it? Andwhat’s next? Furore Ewout Kramer

  2. Disclaimer • FHIR is very early in the stages of its development • Things may evolve differently than presented here • While I’m reasonably involved, I’m not an expert • This is an ideal time to influence outcomes 2

  3. Background • 01/2011, - HL7 Board initiated “Fresh Look” • “what would we do if we were to revisit the healthcare interoperability space from scratch?” • 05/2011 WGM, there was an “official” meeting of the Fresh Look taskforce, but also… • An “unofficial” meeting that took over an evening RIMBAA session and was broadly attended, discussing v3 pain points. 3

  4. V3 Pain-points • Too steep a learning curve • Not easily adopted by out-of-box tools • Specifications get caught up in the need to do everything • Standards development process is slow • Specifications are not created in a way that is directly implementable • We need to support “Drive By interoperability” From this meeting the seeds were planted for RFH/FHIR

  5. RFH/FHIR Prior to Sept. 2011 meeting, Grahame Grieve released the first draft of RFH – Resources for Healthcare • Not a complete specification • But complete enough to show roughly how it would work, including example instances and model design Reviewed at the Sept. 2011 WGM and met with a very positive response The three victims

  6. RFH or FHIR? The name on the original proposal was RFH • Duplicate of a name of a WHO project • Web domains already taken Effort by HL7 marketing to come up with a new name • Free domain names • Available for trademarking • Easy to say/remember • Positive connotation FHIR – Fast Healthcare Interoperability Resources

  7. Scope of queriesand updates “How do we knowwherean object made up of otherobjectsbegins andends?” “In any system with persistent storage of data, there must be a scope for a transaction that changes data and a way of maintaining the consistency of the data”

  8. What is FHIR? Build around the concept of “resources” • Small, discrete concepts that can be maintained independently • Aligns with RESTful design philosophy • Similar to the concept of CMETs, but there’s only *one* model per resource • Each resource has a unique id Each resource comes with built-in CRUD operations When necessary, resources can be combined into collections called “documents”

  9. Storage Model Unit of storage • Lock, create, read, update, delete as a whole • CRUD-services Only the “root” is public, rest are nestedobjects Explicit referencestoother data • Feelslike “identifiable” CMET stereotype Scope of context conduction Unit of documentation

  10. (Dis)assembler/converter Resource Storage

  11. What is FHIR? - II Each resource is modeled using developer friendly XML • XML does not reflect RIM-based modeling • No classCodes, moodCodes, etc. visible • Strong ontology behind the scenes that does link to RIM and vocabulary Uses a variant of the ISO datatypes • Simplifies some things (by moving them out of datatypes) • Adds support for simplifications such as human-readable dates, human-readable ids

  12. What is FHIR? - III Built-in extension mechanism • Extensions are defined using name, value, link-point • Name is tied to robust terminology with full RIM modeling • Link point identifies what element of the base resource or other extension the extension “attaches” to • Idea is the elements used by 80% of implementers are part of the base resource. • All other elements are handled as extensions • Wire format remains stable, even as extensions occur

  13. The 5 parts of RfH Resource definitionswith a focus on implementation- but mappedto the data dictionaryfor full definitions. A data dictionarywhichprovides a richontologicallayerwhere the resources andtheir data elements are formallydefined in a computable fashion TerminologyDefinitionsof termsandvaluesets. ConformanceStatementsthatallowforinteroperabilitybetweenparticularimplementationstobeassessed A workflow management layerthatmapsthe resources to real world business events.

  14. Todo… • Make an inventory of candidate Resources and Modules • Authoring tools. Regular UML? Custom tools? • Vocabulary binding mechanisms • ControlAct, statuses, versioning • Governance • Migration • Stick to the goal: keep it simple!

  15. Next steps… HL7 Fresh Look task-force endorsed FHIR development to go ahead TSC has approved an MnM project to more fully define the FHIR methodology Funded work for a small team to move forward with FHIR design to have something to share for the January 2012 WGM

More Related