FHIR: 9 Things HIT Execs Need to Know

What’s the flash surrounding FHIR? Major HIT vendors, policymakers and large, notable provider organizations have rallied around Health Level 7’s newest standard, Fast Healthcare Interoperability Resource (FHIR). What’s involved in this interoperability standard, why are expectations so high and sho

Author
HDM Staff
Save
Share

    FHIR: 9 Things HIT Execs Need to Know

    What’s the flash surrounding FHIR? Major HIT vendors, policymakers and large, notable provider organizations have rallied around Health Level 7’s newest standard, Fast Healthcare Interoperability Resource (FHIR). What’s involved in this interoperability standard, why are expectations so high and should widespread enthusiasm be tempered? Platforms in Healthcare, a recent report from Chilmark Research, included these details as part of a discussion assessing the interoperability of electronic health records vendors. (Photo: Fotolia)


    FHIR's Role as the Universal Application Programming Interface

    Many advocates suggest that FHIR be the universal API for data across healthcare. FHIR will rely on Representational State Transfer (REST) and web standards, promising an easier-to-program alternative to Simple Object Access Protocol (SOAP)-based IHE profiles. It is expected to provide access to discrete data, to expand on document-centric access methods now readily available. Its scope encompasses public health, clinical research, multi-venue patient care and administrative/financial processes that tie together different healthcare organizations. (Photo: Fotolia)


    A Way to Give a Uniform View of Data

    Vendors who develop EHR, HIE/CNM and other HIT products can incorporate FHIR into their products to provide a consistent and uniform view of data. Applications sharing data via FHIR APIs could provide interoperability for faster, more efficacious IT-based innovation in healthcare.


    The Key Building Blocks of FHIR

    FHIR’s basic building block is called a resource. Each resource (expressed in programs as either JSON or XML) has a name, a description, a summary, data and a way to handle data variability. Programmers implement FHIR with REST HTTP calls. Resources can be created (HTTP POST), retrieved (HTTP GET), updated (HTTP PUT), or removed (HTTP DELETE). FHIR’s support of document- and message-exchange further positions it as an alternative to conventional HL7 messaging. (Photo: Fotolia)


    Advantages of FHIR - Simplicity, Data Access

    The main advantages of FHIR are its relative programming simplicity and better support for discrete data access. It promises to be an easier way for programmers to use and consume healthcare data than existing HL7- and CDA-based exchange mechanisms. Every major HIT vendor expresses strong to nearly complete enthusiasm for FHIR and its potential benefits. Even so, FHIR is still only a draft standard and does not figure prominently in any HIT vendor’s plans for near-term products. (Photo: Fotolia)


    FHIR’s Promise Will Take Time to Deliver

    FHIR offers tremendous promise for improving data liquidity. However, it is too early to say that FHIR will be a panacea. The industry won’t know how FHIR’s impact until billions of healthcare records are made available via FHIR profiles and millions of lines of code have been deployed into production at healthcare organizations. The Chilmark report predicts it will take two years for FHIR-based offerings to become generally available and five years for its effects to become widespread. (Photo: Fotolia)


    Tempering Expectations for FHIR

    The growing number of publicly available FHIR servers is a testament to the level of interest and the apparent inevitability of adoption. There is a need to temper current expectations for FHIR because large-scale deployments will take more time than FHIR’s advocates suggest. If FHIR ultimately proves itself, every healthcare constituent will need to evolve its applications to both expose and consume FHIR resources. (Photo: Fotolia)


    Some Question the Need for FHIR

    In Chilmark’s research, it found that some independent software vendors don’t perceive a need for healthcare-specific standards like HL7 or FHIR. These vendors are important, if often ignored, constituents in HIT because they are actively developing systems of engagement for a variety of healthcare organizations. Many don’t believe HL7 and FHIR always enable better applications. Instead, they advocate that every HIT vendor provide simple REST API-based access to its data. In other words, they believe that healthcare-based standards are overkill. (Photo: Fotolia)


    Some Doubt FHIR for Charting Data

    Major HIT vendors – and hospital EHR vendors in particular –support FHIR, but most would probably reject the idea of using simple REST API for charting data, because of the lack of clinical context that such APIs provide. That said, most EHR vendor API programs are not FHIR-based, but Chilmark expects that to change over the next year. (Photo: Fotolia)


    Current Messaging Approaches May Still Deliver Value

    Still other vendors believe that existing Direct-based exchange of CCDs or CDAs is more than adequate as long as the data attached to the documents are consistent. Most of these developers believe that they could manage the semantic interoperability and data variability issues on a case-by-case basis for their provider customers with even these most rudimentary forms of access to underlying EHR data. They believe that existing messaging-based mechanisms have not yet run their course. (Photo: Fotolia)