Interoperability in health and social care: organisational issues are the biggest challenge

Afeezat Oyeyemi

School of Computing, University of Portsmouth, Portsmouth, UK

Philip Scott

School of Computing, University of Portsmouth, Portsmouth, UK

Author address for correspondence:

Philip Scott

School of Computing

University of Portsmouth

Portsmouth, UK

Email: Philip.scott@port.ac.uk

Cite this article: Oyeyemi A, Scott P. Interoperability in health and social care: organisational issues are the biggest challenge. J Innov Health Inform. 2018;25(3):196–198.

Copyright © 2018 The Author(s). Published by BCS, The Chartered Institute for IT under Creative Commons license http://creativecommons.org/licenses/by/4.0/


Keywords: interoperability, health, information exchange, communication


INTRODUCTION

Interoperability in health and social care is complex and the term has many definitions. This paper adopts the Institute of Electrical and Electronics Engineers (IEEE) definition as cited by the United States Office of the National Coordinator for Health Information Technology (ONC): ‘the ability of two or more systems or components to exchange information and use the information that has been exchanged’.1 As the ONC commentary highlights, this definition encompasses not only health information exchange, but the ability to use that information. The concept is broad and multi-dimensional and there is a limited in-depth knowledge of what it means within the care practitioner workforce.2,3

According to NHS Digital,4 the primary benefit of interoperability is to offer safe and reliable information transfer, improve data sharing across the care pathway and reduce the likelihood of adverse clinical outcomes. Essentially, interoperability supports continuity of care. It is widely agreed that a set of harmonised standards is the most effective and efficient way to achieve and deliver best interoperable healthcare.

Interoperability standards and layers

Interoperability standards provide a common language which enables and supports health service improvements, economic benefits and safety improvements in care delivery.3 Some of the widely used healthcare interoperability standards are:

• Health Level Seven (HL7)

• SNOMED CT

• Integrating the Healthcare Enterprise

• OpenEHR

Interoperability is usually described using various layers of abstraction.2,5 NHS England6 depicts it as two layers that need to be resolved to achieve interoperability: the ‘how’ (technical interoperability) and the ‘what’ (semantic interoperability).

• Technical interoperability is the process of moving data between two systems and is not dependent on the type of information being moved. At this layer, there is no requirement at the receiving end of the system to interpret the content of the data.2 This is what is elsewhere defined as information exchange. This NHS definition is not interoperability in the IEEE sense.

• Semantic interoperability ensures each system has the ability to understand the information received from others without ambiguity. This layer uses coded clinical terminologies, messaging schemes, value sets and profiles.7 An example of semantic interoperability is GP2GP, which enables patients’ electronic health records to be transferred safely between general practices in England.4

Figure 1 Why healthcare interoperability is hard (from2)

As an alternative to moving data between multiple producers and consumer systems, information can be consolidated into a shared data repository. Of course, this still requires at least ‘technical interoperability’ between source systems and the shared record. Shared care records can facilitate common access to clinical information across and between health systems to enable joined-up care and improve health care outcomes. Examples of shared records, some of which are summaries and some are rich longitudinal records, in the United Kingdom are:

• Care and Health Information Exchange – CHIE8

• Summary Care Record (SCR) in England9

• Oxford Care Summary10

• Northern Ireland emergency care record11

• Individual Health Record (IHR) in Wales12

• Emergency Care Summary (ECS) in Scotland13


OBJECTIVE

This paper reports an investigation of stakeholder views about the major interoperability challenges in health and social care data in England. It is widely acknowledged that there are numerous barriers to achieving an interoperable healthcare environment, as shown in Figure 1 below. This study set out to determine the relative importance of these barriers.


METHODS

Primary data were collected through semi-structured telephone interviews and surveys with an opportunistic sample of IT practitioners and clinicians within health and social care organisations in England. A mixed methods approach using both quantitative and qualitative data was utilised. The interview and survey were designed for this study as no prior relevant instruments were identified from the literature. As this work comprised part of an undergraduate degree project, time did not permit a measurement study to validate the instruments. Quantitative data were analysed using descriptive statistics and qualitative data were analysed using content analysis.


RESULTS

It was found that NHS organisations have a limited pool of experts who specialise in this area. Given this and the project time constraints, it was impractical to obtain a large sample size. In total, we had 14 survey participants and four interviewees.

Figure 2 Who is responsible for resolving interoperability challenges?

Figure 3 Major issues of interoperability

The study reinforced that there is no single definition for interoperability; however, it is generally defined informally by the NHS participants as communication and exchange of information between two or more systems which is similar to the IEEE definition noted in the introduction.

Only half of the participants were aware of the regulations (Data Protection Act and Information Governance) required when handling personal data. However, it was not clear if the regulations were being applied in a robust manner. Additionally, there was some misunderstanding and confusion about responsibilities for key regulatory issues.

The interviews indicated general understanding that ‘everyone’ has some role in achieving interoperability. One participant explicitly noted that ‘responsibilities do not lie on a single body or group, everyone is responsible for resolving interoperability challenges’. It is interesting to note in Figure 2 below that NHS England and NHS Digital [still called the Health and Social Care Information Centre at the time of the study] were felt to have equal greatest responsibility in solving interoperability issues. By contrast, none of our participants viewed provider organisations or standards bodies as responsible.

Over 78% agreed that organisational issues were the main interoperability challenge, as shown in Figure 3 below. Commercial competition between suppliers was an additional factor identified by participants, which was categorised as an organisational issue. ‘Other’ issues included factors such as finance, skill sets and staffing levels.


DISCUSSION

There are serious challenges to health and social care interoperability. This small-scale study has emphasised the importance of organisational barriers to interoperability, including commercial issues.


REFERENCES

1. Fridsma D. Interoperability vs health information exchange: setting the record straight. 2013. Available from: https://www.healthit.gov/buzz-blog/meaningful-use/interoperability-health-information-exchange-setting-record-straight/

2. Benson T. Principles of Health Interoperability HL7 and SNOMED. London, UK: Springer, 2010.

3. Health Information and Quality Authority Overview of Healthcare Interoperability Standards. 2013. Available from: https://www.hiqa.ie/system/files/Healthcare-Interoperability-Standards.pdf

4. NHS Digital. GP2GP. 2015. Available from: http://systems.digital.nhs.uk/gp2gp

5. Scott P. Meeting the challenges of healthcare interoperability. Healthcare IT Management 2009;4(3):24–5.

6. NHS England, HSCIC, South, Central and West Commissioning Support Unit. Interoperability Handbook. 2015. Available from: https://www.england.nhs.uk/digitaltechnology/wp-content/uploads/sites/31/2015/09/interoperabilty-handbk.pdf

7. Sicilia MÁ. Interoperability in Healthcare Information Systems: Standards, Management, and Technology: Standards, Management, and Technology. Spain: IGI Global, 2013.

8. South, Central and West Commissioning Support Unit. Care and Health Information Exchange—The Hampshire Health Record. 2016. Available from: http://hantshealthrecord.nhs.uk/

9. NHS Digital. Summary Care Record. 2016. Available from: http://systems.digital.nhs.uk/scr

10. NHS Oxfordshire CCG. Oxford Care Summary. 2013. Available from: http://www.oxfordshireccg.nhs.uk/your-health/your-health-records/oxfordshire-care-summary.htm

11. E-Health and Social Care: Northern Ireland Emergency Care Record. Information for Better Care. 2016. Available from: http://www.ehealthandcare.hscni.net/niecr/niecr.aspx

12. NHS Wales Information Services. Individual Health Record. 2016. Available from: http://www.gprecord.wales.nhs.uk/home

13. NHS Scotland. Your emergency care summary what does it mean for you? 2006. Available from: http://www.gov.scot/Resource/Doc/143714/0036499.pdf

Refbacks

  • There are currently no refbacks.


This is an open access journal, which means that all content is freely available without charge to the user or their institution. Users are allowed to read, download, copy, distribute, print, search, or link to the full texts of the articles in this journal starting from Volume 21 without asking prior permission from the publisher or the author. This is in accordance with the BOAI definition of open accessFor permission regarding papers published in previous volumes, please contact us.

Privacy statement: The names and email addresses entered in this journal site will be used exclusively for the stated purposes of this journal and will not be made available for any other purpose or to any other party.

Online ISSN 2058-4563 - Print ISSN 2058-4555. Published by BCS, The Chartered Institute for IT