|
Interoperability in health information systems
|
| Introduction |
Interoperability is integrated connectivity.
Interoperability
enables data and information generated by one system to be
accessed and (re-)used in a meaningful way by another system,
whether or not the latter system is based on different technologies.
Interopability in computerised healthcare information systems lags far behind
other (arguably less complex and variable) domains such as finance and transport.
Many implemented health information technologies, such as electronic patient records,
have tended to be local, proprietary and insular. Many systems in use weren't
designed to communicate with others (whether inside or outside individual health provider
organisations), so don't.
However,
interopability, using open standards to support
information and data exchange, has become a very significant issue
for health information technology developers and implementers.
It is probably the major concern of all national governments implementing or promoting the
implementation of national health information
networks and infrastructures.
Interoperability covers health and patient information, clinical knowledge and workflow,
and technical matters such as architecture, messaging, interfacing knowledge and data representation, and security (data privacy, confidentiality,
individual and organisation identifiers ...). Standards designed to support interoperability
and national policy documents are covered in more detail
elsewhere on OpenClinical (see links below). These include standards for communication,
messaging, data transfer (DICOM for medical images, HL7 for electronic patient referrals,
lab. requests and results); data representation standards (ASTM Continuity of Care Record,
HL7 Clinical Document Architecture; medical terminologies and classifications (representing clinical data, drugs, lab. tests ...)
electronic patient record architecture, structure, format (EHRcom, openEHR ...).
|
| Definitions |
The Institute of Electrical and Electronics Engineers (IEEE, USA) defines
interoperability as:
"the ability of two or more systems or components to exchange information and
to use the information that has been
exchanged".
[IEEE-USA]
In Europe, IDABC - Interoperable Delivery of European eGovernment Services to public Administrations, Businesses and Citizens - offers the following similar
definition (edited for clarity): "Interoperability means the ability
of information and
communication technology (ICT)
systems ... to exchange data and
enable the sharing of information and knowledge."
[IDABC]
The National Alliance for Health Information Technology (NAHIT, USA) expands a little on the
above definitions:
"In healthcare, interoperability is the ability of different information technology systems
and software applications to communicate, to exchange data accurately, effectively, and
consistently, and to use the information that has been exchanged.
" [NAHIT]
|
| Benefits |
For health professionals:
-
Improve access to health record data and health information anytime, anywhere.
For patients:
-
Improve quality and safety of care by improving data exchange, the quality of data flow and
access to information by
health professionals
thereby potentially
reducing errors.
For health managers:
-
Improve data collection and facilitate statistical and economic analysis.
For health researchers:
-
Improve and increase the availability of medical data.
For the healthcare technology industry:
-
Improve access to the healthcare market for more companies
(SMEs in particular who may be limited in their ability to provide technologies which can
integrate with an organisation's legacy systems).
|
| Issues |
- Without interoperability, fundamental data and information such as
patient records can't easily be shared
across and sometimes within enterprises.
- Achieving interoperability in a domain where information technologies, where they have been deployed in
routine practice,
may not have been designed to support it.
- Many standards to support interoperability are only just now being
developed - after many HIT systems have been installed.
- Where HIT standards do exist they may also compete, making interoperability more difficult to
achieve.
- A lot of computerised clinical data are stored in ageing legacy systems in
proprietary formats which are dificult for other systems to access, re-represent and
transfer for (re)use. (The use of proprietary formats may also lock customers into
specific information systems.)
- Implementation of interoperable health information systems may require a high degree of
technical expertise not readily available to small organisations in particular.
|
| Projects |
|
|
The Artemis project [aims to support] "interoperability of medical information systems through
semantically enriched Web services."
|
|
| references: interoperability in health care systems |
Brailer DJ.
Interoperability: the key to the future health care system.
Health Aff (Millwood). 2005 Jan-Jun;Suppl
[PubMed]
[Health Affairs]
|
"
The United States is building a point-of-care health information system to rival the worldwide network of electronic banking. Through health care information exchange and interoperability, clinicians will have access to a longitudinal medical record. This interoperability is a fundamental requirement for the health care system to derive the societal benefits promised by the adoption of electronic medical records (EMRs). The paper by Jan Walker and colleagues highlights some of these benefits. One critical question is whether the adoption of EMRs needs to wait for interoperability standards or whether it can proceed efficiently without them.
"
|
Hammond WE. The making and adoption of health data standards.
Standards exist, but there is no nationwide coordination process to ensure that they are useful
in everyday transaction.
Health Aff (Millwood). 2005 Sep-Oct;24(5):1205-13.
[PubMed]
[]
|
"
Health data standards are key to the U.S. quest to create an aggregated, patient-centric electronic health record; to build regional health information networks; to interchange data among independent sites involved in a person's care; to create a population database for health surveillance and for bioterrorism defense; and to create a personal health record. This paper discusses why health data standards are required, the process of creating those standards, the groups creating those standards, and some of the problems and issues that are affecting the progress and acceptance of standards. It makes a recommendation for dealing with those issues.
"
|
Engel K, Blobel B, Pharow P.
Standards for enabling health informatics interoperability.
Stud Health Technol Inform. 2006;124:145-50.
[PubMed]
[]
|
"
Most of industry countries are turning their healthcare system towards integrated care paradigms
for improving quality, efficiency, and safety of patients' care. Integrated care has to be
supported by extended communication and cooperation between the involved healthcare
establishments' information systems. The required interoperability level goes beyond technical
interoperability and simple data exchange as it has been started in the early world of
electronic data exchange (EDI). For realising semantic interoperability, series of standards
must be specified, implemented and enforced. The paper classifies standards for health
information systems needed for enabling practical semantic interoperability.
"
|
Walker J, Pan E, Johnston D, Adler-Milstein J, Bates DW, Middleton B.
The value of health care information exchange and interoperability.
Health Aff (Millwood). 2005 Jan-Jun;Suppl
[PubMed]
[Health Affairs]
|
"
In this paper we assess the value of electronic health care information exchange and
interoperability (HIEI) between providers (hospitals and medical group practices) and
independent laboratories, radiology centers, pharmacies, payers, public health departments,
and other providers. We have created an HIEI taxonomy and combined published evidence with
expert opinion in a cost-benefit model. Fully standardized HIEI could yield a net value of
dollar 77.8 billion per year once fully implemented. Nonstandardized HIEI offers smaller
positive financial returns. The clinical impact of HIEI for which quantitative estimates cannot
yet be made would likely add further value. A compelling business case exists for national
implementation of fully standardized HIEI.
"
|
Brailer DJ.
Health IT Czar focuses on interoperability.
Biomed Instrum Technol. 2006;Suppl:6-7
[PubMed]
[]
|
"
" (not available)
|
|
| References: public reports |
|
Connected Health: Quality and Safety for European Citizens.
Unit ICT for Health
in collaboration with
the i2010 sub-group on eHealth and
the eHealth stakeholders’ group.
Commission of the European Communities, Information Society & Media DG, 2006
[]
[OC]
|
"This paper outlines priority issues which must be pursued vigorously in order to reach all of these health systems goals - improve patient safety, encourage well-informed citizens and patients on health matters, and create high-quality health systems and services - and, at the same time, face international competition in the eHealth sector."
"The main reasons for accelerating the introduction of interoperable eHealth solutions in a collaborative and coordinated way in Europe are the increasing mobility of European citizens, the aging population and the empowerment of citizens, the continuity of care and the creation of a bigger, European-wide market for many health applications and technologies."
|
Commission on Systemic Interoperability.
Ending the Document Game: Connecting and Transforming Your Healthcare Through Information
Technology, NLM/NIH/HHS, 2005.
[endingthedocumentgame.gov]
[OC]
|
"
"
|
|
| links |
|
|
|
| acknowledgements |
| |
| page history |
Entry on OpenClinical (v0.1): 03 January 2007
Last main update: 29 January 2007 |
|
|