Skip to main content

FHIR Status Check

 More than 2 years have past since I wrote my article on the Fast Healthcare Interoperability Resources (FHIR®) standard and it’s time to do a quick status check and revisit the predictions I made back then.

The FHIR standard continues the strong trajectory of adoption and is now used across the globe. The application programming interface (i.e. the FHIR API) is available in most major EHR systems today. According to the US Office of the National Coordinator Health Information Technology an estimated 85% of hospitals have FHIR in their systems. The NHS has been quick to adopt FHIR and the adoption curve in the UK is high. The NPfIT (NHS Care Record Service) HL7 V3 interfaces are being redeveloped in FHIR®, and new NHS specifications such as the CareConnect standard for secured Transfer of Care  are being specified in FHIR® by default.

Despite the industry enthusiasm about the potential of FHIR still the old and faithful HL7 v2 remains the predominant interoperability standard in use today and serves as the interoperability backbone in most health organizations. 

According to a recent HIMSS case study the use-cases for using FHIR are: enhancing consumer engagement (52%), improving payer-provider convergence (49%), bridging gaps-in-care (38%), regulatory compliance (37%) and provider engagement (25%).


It is my belief that the fact FHIR struggles to replace HL7 v2 is that the latter do an excellent job in event driven scenarios were information needs to be pushed from a source system to multiple destinations. This model of data - exchange perfectly suites common cases in healthcare such as patient flow and test results updates.

Being a RESTful standard the method to implement event driven interfaces is through a pub/sub mechanism via the use of webhooks.

FHIR is evolving, through an incremental process, each year. The current release 4 defines a subscription Resource which is FHIR implementation of webhooks. This recourse has a “Maturity level” of  3 out of 5 levels, which means that it has been verified by the work group, but not yet tested and published. 

Despite the hurdles yet to overcome for fulfilling the high expectations of the HCIT community I feel confident that FHIR will continue its strong adoption and  will eventually become the predominant interoperability standard in healthcare.


Comments

Post a Comment

Popular posts from this blog

Get ready for the invasion of the healthcare bots

Everywhere I go lately I hear people chatting about chatbots. It seems that every health organization is preparing to launch a chatbot service or at least has it on their roadmap. Once I noticed this trend, I keep asking the people I meet about their "bot strategy" and thus having my own small contribution to the trend. There are countless cases where a digital personal assistant or a chatbot could help physicians, nurses, patients or their families. From assistance in simple routine tasks like finding a doctor or scheduling an appointment, to better organization of patient pathways, medication management, help in emergency situation and offering a solution for simpler medical issues. The general idea behind the buzz is that in the future, these talking or texting smart algorithms might become the first contact point for primary care. Patients will not get in touch with caregivers directly for health questions but will turn to chatbots first. Only in case the bot can ...
Post a Comment
Read more

Clinical data warehouses: Sometimes it's worth being lazy

If you are a health organization you probably have or thinking of having a clinical data warehouse. A Clinical Data Warehouse (CDW), sometimes called Clinical Data Repository (CDR), is a database that consolidates data from a variety of clinical sources to form a unified view of a the data for various purposes. Typical data types which are often found within a CDW include: clinical laboratory test results, vital signs, patient demographics, administered meds, hospital admissions, ICD-9 codes and more. Developing and sustaining an effective CDW operations unit is a substantial effort and long-term commitment. The main challenge in designing a CDW is defining its scope and the use cases it should support. In theory a CDW can serve as a basis for reporting, studying and planning. The use case that is often mentioned in relate to CDW is supporting clinical trials. This would allow for researchers to have all the information from a study in one place as well as let other researchers benefit...
Post a Comment
Read more

The case for PAA

PAA stands for Patient Admission App. In a nutshell it is a platform in which the hospital can communicate with its patients and their relatives before, during and after their stay in  the hospital. A patient's encounter with a hospital is often a traumatic event to both the patient and his family. A lack of  proper communication between the parties can have major implications on the hospital efficiency and the patient's experience which research shows has a critical impact on the quality of care. From red tape to red carpet  A PAA should accompany the patient throughout his journey by keeping him informed and engaged. This starts prior to the actual admission when the patient feels scared, anxious and confused. A PAA should provide the patient with all the information related to his upcoming treatment. This can include treatment reminders such as not to eat x hours before a planned anesthesia, orientation map, etc. It should also handle in...
Post a Comment
Read more