Skip directly to search

Skip directly to content


How to Improve Interoperability in Healthcare


Next Gen Insights | Les Jordan |
02 March 2021


Gone are the days when an admin “pulled your chart” when you visited the doctor. Today, a visit to the doctor often looks like this: the doctor types while speaking with you. This introduces a whole new set of questions: How much time is the doctor spending with you vs. doing documentation? Did the doctor (or scribe) capture the depth of your information correctly, or just a summary? 

The problem is compounded when you go to an emergency room or specialists outside of your doctor’s practice, who most likely do not have access to your primary doctor’s medical records. You are stuck repeating the same background information to every doctor you visit. 

So, what can Health and Healthtech organisations, i.e. those responsible for implementing the health IT systems that we rely on, do to reduce the inefficiencies inherent in the current environment?


Previously, health providers as well as the software companies that serve them focused on the digitalisation of medical records for single organisations. In the US, some of this focus can be attributed to the HITECH Act of 2009, which incentivised the implementation of electronic medical records (EMR) in hospitals and physician practices; however, the notion of communication between health providers was all but missing. The Health Information Exchanges (HIEs) created as part of the HITECH Act were supposed to be the first step in implementing data exchange between hospitals, but the HIEs were only regional, and participation was not mandated, leading many organisations to not participate. 

More recently, with the passage of the 21st Century Cures Act of 2016 in the US and the European Commission adopting the Recommendation for a European Electronic Health Record exchange format, greater focus is being put on interoperability and the availability of data to the individual patient. 


Of course, there are standards, most prominently Health Level 7 (HL7) and Fast Healthcare Interoperability Resources (FHIR), which are intended to ease integration and interoperability between health software. These standards define what the data format should be, and – in the case of FHIR – how health data should be transmitted between software products, specifying the use of standard APIs. 

The problem, with HL7 in particular, lies in the implementation: many of the major EMR vendors have their own approach to these standards, resulting in less-than-perfect methods for integrating between those vendors. 

In addition, while these standards dictate the format and integration method of the data, what’s missing is where they should integrate. This leaves either the use of the few existing HIEs or point-to-point communication between healthcare providers. 

With EMR implementations now being pervasive, and standards being available for integrating between EMR providers, we should be able to provide patient-level health information to the doctor and the patient, regardless of which doctor or provider is being visited. In the following, I will examine three approaches that health software companies can take to support the interchange of health data between provider organisations to get that data into the hands of patients. 


Major EMR vendors offer their own HIE solutions to providers and patients using their software. Here, patients and providers get access to the patient’s health information, regardless of the doctor they visit, as long as those doctors use the same EMR software. 

This has some distinct advantages, especially for the patient. As a patient, I am able to log into my primary physician’s patient portal and see all my data collected by that doctor as well as the data entered by any other doctor who uses the same EMR software as my primary physician.  

Likewise, my physician is able to see the results from my visits to other doctors or hospitals, including conditions, current and past medication lists, physician notes and discharge summaries.

Chart 1

For health software companies, integrating with the handful of EMR providers offers some distinct advantages. By integrating your software with some of the major vendors, you allow your software to be used by the majority of patients. 

The problem with this approach is that the major vendors are not necessarily open to software providers directly connecting with their software. While they offer integration APIs and make their documentation (somewhat) available, their integration documentation is largely aimed at their customers, not third parties.

The solution for many software providers is twofold:

  1. Write your software around HL7 and FHIR
  2. Utilise an EMR integration engine

The first step for any organisation looking to integrate their health data with the patient’s data in the EMR is to write their integration APIs in a way that utilises HL7 for the data format and FHIR around the data format and APIs. While this may be obvious, many companies don’t think about external integration and interoperability when they design their applications. However, this really should be part of the architecture from the beginning. 

The second step is to utilise an EMR integration engine. There are many of them in the market today, and all of them provide some integration with the major EMR vendors. 


As mentioned above, the first HIEs were geographically based, i.e. groups of providers from a given region or geography would come together and agree on how to share their data. They were frequently sponsored by either the providers themselves or by state governments. These HIEs had to develop everything from scratch, including decisions on how to share data, what data to share, or how to match patients between providers.

Chart 2

For patients, this type of integration still (somewhat) excludes them. While their data is shared by the various health providers, they themselves are still required to log into multiple provider EMRs in order to get access to their data. 

For third-party software vendors, this approach still requires them to integrate with each EMR vendor in order to connect to patient data (see Approach 1).

The solution for many software providers is to connect to an interoperability framework like Carequality, which gives software “implementers” a standard way of communicating with each other. While utilising HL7, it goes beyond that in providing software vendors with a way of actually exchanging the data itself, without having to resort to point-to-point connections.

When Carequality is combined with the CommonWell Health Alliance, which provides a connection between software vendors and not just the definition of that connection, health software vendors are enabled to have their software interoperate and exchange data with each other.


Similar to the first approach, this one requires health software providers to reach out to each organisation they want to integrate with and negotiate access to their data using HL7 and/or FHIR. However, instead of reaching out to the EMR vendors, this approach requires negotiating with each healthcare provider about getting access to their EMR. 

An example of this can be seen in the approach of major personal health record (PHR) vendors. By using HL7 CCD (Continuity of Care Document), PHRs can download the data from the EMR and present it to the patient.  

This is a useful and convenient solution for patients, as they now have one place to find all their relevant health data. For the implementing software company, the disadvantage is that they not only need to know where to get the data from each vendor’s software, but they also have to reach out to individual health systems in order to gain access to their data. While the mechanisms for doing this have been standardised, agreements with each provider still need to be found. 


Even though we live in an age where data exchange has become ubiquitous, data interchange in the healthcare sector still proves to be a challenge. To add immense value, health software companies must look not only at the best technical ways to transmit health information but should also consider the best and most comfortable solution for their end users: patients, doctors and medical professionals in hospitals and other institutions. 

Les Jordan

Independent Consultant

As an expert in health and life sciences technology, Les has spent his 25+ year career helping organisations large and small implement game changing technology, with a particular focus on patient engagement, mHealth and clinical trials. Outside of work, he enjoys spending time with his family and getting outdoors, whether it be for a long hike in the woods or as a referee on the soccer field.


Related Articles

  • 17 December 2019

    Demystifying omnichannel and making it a reality

  • 07 May 2019

    Failure to launch - Why contactless in the US is behind the rest of the world

  • 08 April 2019

    Get Emotional - How Feelings Dominate Decision Making

  • 04 February 2019

    Can a business thrive in the age of continuous innovation?

  • 07 January 2019

    Delivering Business Value at Speed: A Recipe in Three Steps


From This Author

  • 25 March 2020

    The Cultural Adoption of Healthtech

Most Popular Articles

Current Challenges in the Transportation & Logistics Industry

Transportation & Logistics Insights | Brian Estep | 22 March 2022

Current Challenges in the Transportation & Logistics Industry

AI Art in Game Production – an XDS 2022 Table Discussion

AI | Thomas Bedenk | 27 September 2022

AI Art in Game Production – an XDS 2022 Table Discussion

Payments Data Monetisation is Key to Driving Sustainable Growth

Payments | Annmarie Mahabir | 20 September 2022

Payments Data Monetisation is Key to Driving Sustainable Growth

4 Buy Now Pay Later Trends Set to Disrupt the Industry

Payments | Annmarie Mahabir | 22 February 2022

4 Buy Now Pay Later Trends Set to Disrupt the Industry

The New Ways of Issuing Cards

Payments | Peter Theunis | 19 July 2022

The New Ways of Issuing Cards

Buy Now Pay Later: Will Regulation Burst the Bubble?

Payments | Annmarie Mahabir | 01 February 2022

Buy Now Pay Later: Will Regulation Burst the Bubble?

Buy or Build? A Game-Changing Question in Insurance

Next Gen Insights | Robert Anderson | 12 January 2022

Buy or Build? A Game-Changing Question in Insurance

Top Challenges in Warehouse and Distribution Centers

Transportation & Logistics Insights | Brian Estep | 01 March 2022

Top Challenges in Warehouse and Distribution Centers

The Metaverse Evolution and Learning from the Games Industry

Next Gen Insights | Thomas Bedenk | 30 March 2022

The Metaverse Evolution and Learning from the Games Industry



  • 27 September 2022

    AI Art in Game Production – an XDS 2022 Table Discussion

  • 20 September 2022

    Payments Data Monetisation is Key to Driving Sustainable Growth

  • 13 September 2022

    Navigating the Healthcare Ecosystem

  • 30 August 2022

    hey y’all! I’m Ashley Grant

  • 23 August 2022

    5 Ways to Fix Your Data Spine in Banking

  • 16 August 2022

    De-risking Digitalisation

  • 09 August 2022

    hi, I’m Brian Estep

  • 02 August 2022

    hey! I’m Lia Rollman

  • 19 July 2022

    The New Ways of Issuing Cards

  • 12 July 2022

    Scores on the Door: Rating Autonomous Vehicles

  • 06 July 2022

    Data-Driven Impact: Don’t Settle for Less

  • 06 July 2022

    We’re in Nottingham – a Q&A on Endava’s New Delivery Centre in the UK

  • 05 July 2022

    hey, I’m Chris Hart

  • 28 June 2022

    Platforms: a Blessing or a Curse?

  • 23 June 2022

    A Payments View on Marketplaces – How to Be(come) Successful

  • 21 June 2022

    Intelligent Commercial Underwriting

  • 14 June 2022

    The Future of Supply Chain: What’s Next?

  • 31 May 2022

    The Future of Autonomous Vehicles in T&L

  • 26 May 2022

    hello! I’m Hannah McCarthy

  • 24 May 2022

    Going Native: Why Cloud-Native Services are Essential

  • 19 May 2022

    How to Tackle Legacy – Breaking Down Walls Between Change and Run

  • 17 May 2022

    Advantages of a Yard Management System

  • 12 May 2022

    Are Phones About to Become the New POS Terminals?

  • 10 May 2022

    The Digital Economy is an Upgrade of Smart Cities and Communities

  • 05 May 2022

    hello! I’m Sumita Davé

  • 03 May 2022

    Physical Automation in the T&L Industry

  • 28 April 2022

    zdravo! I’m Andrej Kotar

  • 26 April 2022

    Open Banking in the US

  • 20 April 2022

    hello! I’m Paul Maguire

  • 19 April 2022

    Digital Automation in the T&L Industry

  • 12 April 2022

    How Do Banks Embrace Embedded Finance – Have the Fintechs Already Won?

  • 06 April 2022

    ESG Data Architecture is a Business Imperative – How to Get Started

  • 05 April 2022

    hi! I am Roy Murphy

  • 05 April 2022

    Modernizing the Shipping and Cargo Process

  • 30 March 2022

    The Metaverse Evolution and Learning from the Games Industry

  • 29 March 2022

    Do Androids Dream of Trading Electric Sheep for Digital Wood? An Introduction to Automated Game Design

  • 23 March 2022

    Real-Time Payments in Australia – Why Corporates Should Get on Board

  • 22 March 2022

    Current Challenges in the Transportation & Logistics Industry

  • 16 March 2022

    bok! I’m Sanja Cvetkovic

  • 15 March 2022

    Rapidly Transforming: Healthtech Trends in 2022

  • 08 March 2022

    How to Digitize Warehouses and Distribution Centers

  • 01 March 2022

    Top Challenges in Warehouse and Distribution Centers

  • 28 February 2022

    Tackling CIB Legacy at its Core

  • 23 February 2022

    salut! I am Isabela Buhai

  • 22 February 2022

    4 Buy Now Pay Later Trends Set to Disrupt the Industry

  • 15 February 2022

    salut! I’m Natalia Ciobanu

  • 14 February 2022

    Product-Led Innovation – a Q&A with Joe Dunleavy

  • 01 February 2022

    Buy Now Pay Later: Will Regulation Burst the Bubble?

  • 31 January 2022

    Innovation Will Spur Ireland’s Race to the Top

  • 28 January 2022

    The Value of Digital and Automation in the Product Returns Process

  • 26 January 2022

    Virtually Disrupted? Keeping Pace with Accelerating Customer Expectations

  • 19 January 2022

    The 3 Big Ps in Modern Insurance: Personalisation, Prediction and Prevention

  • 18 January 2022

    An Introduction to Mobility as a Service in the US

  • 12 January 2022

    Buy or Build? A Game-Changing Question in Insurance

  • 12 January 2022

    hello! I’m Paul Willoughby

  • 11 January 2022

    Payment Service Providers 2.0

  • $name

We are listening

How would you rate your experience with Endava so far?

We would appreciate talking to you about your feedback. Could you share with us your contact details?