Keywords

1 Background

During the last two decades, there was a considerable increase in the capacity to develop and manufacture systems that employ smart components highly integrated and miniaturized [1]. Because of this remarkable development, ubiquitous computing is nowadays part of our everyday and social life and impacts our surrounding environments.

According to the vision of Weiser [2], ubiquitous computing aims the enhancement of the computer use by bringing computing devices into everyday life (e.g. integration of computing power and sensing features into anything, including everyday objects like white goods, toys or furniture), making them available throughout the physical environment in such a way that the users would not notice their presence. In turn, ubiquitous communication comprises multiple technologies to allow the interaction among multiple devices anytime and anywhere.

Pervasive health has emerged as a specialization of eHealth and deals with the application of ubiquitous computing [3, 4] for health and wellness management, aiming to make health care more seamlessly to our everyday life [5]. Pervasive health can contribute, with different roles, to personalize health and wellness services promoting an evolution from a medical approach to individual-centric operational models, in which the individual becomes an active partner in the care process [5].

Health care services are highly mobile in nature [6] and involve multiple locations (e.g. clinics, outpatients’ services or patients’ homes), particularly when dealing with older adults and their respective major diseases [7]: cardiovascular disease, hypertension, stroke, diabetes, cancer, chronic obstructive pulmonary disease, musculoskeletal conditions, mental health conditions or visual impairment and blindness. Therefore, the pervasive health landscape includes mobile health (mHealth) application. For that smartphones are fairly robust, truly pervasive and accessible - they are accessible to over 90% of the global population [1] - and they provide ubiquitous user interfaces and have the ability to collect, store and communicate information [1]. Furthermore, an interesting feature of smartphone devices is the availability of short-distance wireless data transmission, such as Bluetooth [6]. This enables the smartphone applications to work with a wide range of hardware devices (e.g. glucose meters, pulse oximeter or thermometers) from different vendors.

Meeting the specific individual needs, namely providing care services at individuals’ home together with intelligent applications, is one of the main strategies to guarantee independent living of older people [8]. Considering this context, important goals are to promote personal assistance (e.g. medication reminder) and distance support (e.g. telerehabilitation programs) or to provide the caregiver with accurate and up-to-date information in order to be delivered the right care at the right time (e.g. continuous monitoring of physiological parameters or behaviors, emotions and activities), which can contribute to the overall effort to provide personalized and affordable access to essential services with efficacy and efficiency [9,10,11]. Therefore, a typical pervasive health application consists in monitoring health conditions or the progress of some chronic diseases.

For monitoring applications, sensors are required to collect relevant physiological data. A wide range of sensors, including pressure and thermal sensors, might be used to measure blood pressure, body temperature, blood glucose, heart sound, heart rate, respiration, respiratory rate, blood oxygen saturation or perspiration. Some sensors are non-invasive, but various biological signals require invasive sensors such as electrodes. Non-invasive wearable and textile devices present a considerable potential, and, for instance, they allow measuring physiological parameters through the use of techniques such as infrared or optical sensing [12].

In health care delivery, there is significant amount of information available, so the problem is less the volume and more the value that is created with the available information. Major difficulties are related to the aggregation of information from different sources, with different formats and meanings, as well as the lack of tools to identify, within all the available information, the one that is relevant for each particular situation and to make it useful rather than just being visible [13].

The information is no longer stored and exclusively managed by the Electronic Health Records (EHR) of the health care institutions [14,15,16,17]. Although EHR are adequate for the presentation of information from patients, collected and aggregated in local healthcare information systems, the reality is that the provision of health care is not restricted to an institution or even to a single care provision system. All caregivers need comprehensive, up-to-date, safe and congruent information from the patient, immediately accessible at the place of care, to ensure the highest levels of clinical quality. For instance, when considering the home monitoring of a patient with a chronic disease (e.g. diabetes, heart failure or chronic obstructive pulmonary disease), the resulting monitoring information should be distributed within an information network ranging from clinicians, social care network, and family members to the patients themselves. These requirements promote the emergence of new technological approaches such as Personal Health Record (PHR) [18] that aimed at electronic management of information between the patients and their formal and informal health care providers, and that might contribute to the availability of the patients’ clinical information that is collected throughout their lives [13].

However, the implementation of this vision is bounded by a set of problems: for instance, clinical information is blocked in healthcare information systems silos, generated and stored in different systems that either do not communicate with one another or are unable to synthesize information to make it meaningful and usable. Therefore, interoperability must be ensured, in terms of communications protocols and semantic normalization, between a wide range of information sources and eHealth applications. Hence, efforts carried out by international institutions such as the Continua Health Alliance, the Health Care Information and Management Systems Society (HIMSS), the National Institute of Standards and Technology (NIST) and the Integrating the Healthcare Enterprise (IHE), have been crucial to overcome interoperability difficulties and to promote a homogeneous eHealth ecosystem [19].

According to the European Commission [20], interoperability is a key precondition for ensuring more and better coordination and integration in health care delivery, which includes health information sharing.

The need to ensure technological and semantic interoperability in the European context is reinforced, with a set of objectives such as: defining guidelines for the type of data to be included in patient summaries, developing standards and specifications (e.g. for technological and semantic interoperability) and the promotion of systems for testing and certifying the interoperability of solutions. The Commission therefore proposes a greater effort in the development and validation of specifications and components. This effort should be extended to the pervasive health developments [21, 22].

There are also two other dimensions of interoperability mentioned in the European Commission’s report [20], which should be stated, given the importance they are assumed to have in achieving the objectives of the health services. These are organizational and legal interoperability. Organizational interoperability is directly related to the integration of processes (and conditions of information sharing between organizations) in order not to compromise collaborative work. Concerning the legal framework, there are a number of legal issues related to the issue of interoperability, such as those relating to data protection rules for patients and citizens, as well as regulatory issues (e.g. lack of definition of the roles of the various actors in the system) around mHealth applications, which offer more possibilities for self-administration of care.

Given this background, the main purpose of the systematic review reported in the present article was to explore if interoperability is a real concern when developing concrete pervasive solutions (e.g. telehealth, mHealth or ambient assisted living applications) to gather patients’ information, both clinical and contextual information.

2 Methods

The purpose of this systematic review was to identify and analyse in more detail articles related to home monitoring, which reveal an explicit concern with interoperability requirements. The general goals of this systematic review, that extends the results present in [23] were to identify, within the selected references, how interoperability is addressed in the solutions being proposed, how they are validated and if there is effective technological and semantic interoperability. The goal of this analysis was to assess if, in addition to allowing information sharing, the solutions proposed are able to produce meaningful and contextualized information that can be integrated into EHR, that is, if the information they collect is qualified to be integrated and usable in the care service provision. Moreover, if this is the case, it is important to identify the healthcare interoperability standards that are most commonly used.

2.1 Study Design

Considered the aforementioned purposes, the systematic review of the present study was informed by the following research question: Is there an explicit concern related to interoperability during the development of new eHealth applications to gather patients’ information in their home environments?

Within references selected as expressing an effective concern related to interoperability, some sub-questions were raised:

  • What are the target users being considered?

  • What interoperability solutions are being proposed?

  • What healthcare interoperability standards are being used?

  • Which methods are being used to validate the proposed interoperability implementations?

To achieve these goals, initially, a systematic review of literature published between 2011 and 2017 was performed.

Exclusively the references that had the keywords “interoperability” or “interoperable” in title or abstract were considered for further assessment and classification, being excluded the first group of references.

Subsequently, the references included for analysis were assessed and some more were excluded reflecting specified criteria, which is described below. The remaining references were then categorized according to the degree of significance to answer the questions posed within this research, that is to say, the option was to analyse in greater depth the references that proposed solutions in which it was assumed as relevant that the information produced could be integrated into the health care service provision.

The methods used to conduct this systematic review of literature as well as the subsequent categorization of search results is described in the following subsections.

2.2 Data Sources and Searches

The research was carried out using the Scopus, Web of Science and IEEE Xplore Digital Library databases, in the publications titles, abstracts and keywords.

The keywords used in the search, simultaneously, were: “monitoring” and “pervasive health”, since these are the topics around which it is important to evaluate the centrality of the interoperability issue. Pervasive health is seen as a contribution to a more personalized model of care allowing individuals to be more actively involved in their care process. A classic pervasive health care application is home monitoring of health conditions, particularly patients with chronic diseases. However, it is important to note that pervasive health is more than monitoring applications as it can also include preventive applications (e.g. elderly people to live independently) [24].

The remaining keywords were: “mobile health”, “mhealth” and “ambient assisted living”. These keywords were combined so that at least one of them corresponded to the subject of the search.

2.3 Inclusion and Exclusion Criteria

References with no author, no abstract, not written in English, duplicates and editorials were excluded. References selected for review were all written in English and all who had a date of publication between 2011 and 2017. Then, all the references that did not explicitly mention the “interoperability” or “interoperable” keywords in tittle and/or in abstract were also rejected.

Subsequently, within the references’ full texts revised, those that corresponded to items out of ambit of this systematic review were also excluded. Then, in the group of references within the scope of this systematic review, were also identified and excluded those references that corresponded to categories to be rejected in view of the objectives of this analysis, specifically: overviews, political perspectives, position papers, reviews and systematic reviews.

Then, the remaining references were clustered in ascending order of importance for this study: connection between devices; intermediate components between the devices and the client applications for handling the storage and sharing of the information being gathered (e.g. architectures, gateways, middleware or data hubs); intermediate components but incorporating medical devices specificities; and end-to-end solutions.

2.4 Study Selection

After the first screening, one author assessed all titles for relevance. Those clearly not meeting the inclusion criteria were removed.

Afterwards, the abstracts of the retrieved articles were assessed against the inclusion and exclusion criteria, by two authors. Any disagreements were discussed with a third reviewer and resolved by consensus. Abstracts were then subject to a first classification and grouping.

Finally, the references that were selected by the superior interest for this study were gathered and analysed in more detail. Two authors, according to the outlines criteria, then assessed again these full texts thought to be of relevance, and any divergences were also discussed with a third reviewer and agreed by consensus.

3 Results

This systematic review followed the guidelines of the Preferred Reporting Items for Systematic Reviews and Meta-Analyses (PRISMA) [25], as described in Fig. 1.

Fig. 1.
figure 1

(extended from [23]).

PRISMA flowchart

After the initial database search, 4141 references were considered for the next phase. Then, 4060 of these references were rejected because they did not explicitly mention “interoperability” or “interoperable” in the tittle and/or in the abstract.

Afterwards, by reviewing these 81 references’ full-texts, 44 were excluded: the first 30 references grouped and classified are articles assumed as out of the scope of this study; other cluster (n = 14) are references that, although within the ambit of the present analysis, were also excluded because they correspond to position papers (n = 5), systematic reviews (n = 3), reviews (n = 1), overviews (n = 2) and political standpoints (n = 3).

The remaining 37 references were first clustered in ascending order of importance for this study.

3.1 Characteristics of the Studies

The purpose of the 37 references selected for this systematic review is presented in Table 1. The studies were categorized according to different aspects of interoperability:

  • Sensors aggregation: four references [26,27,28,29] describe solutions providing communication protocols to network a large number of sensors.

  • Data aggregation: 23 references report solutions to aggregate data from various sources to provide it in an integrated way to client applications [30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52]. These articles, though being related to health care applications, they do not allude to interoperability standards used in health care, inhibiting the information that is produced from being integrated into the health care service provision. However, what is described in the type of solutions proposed in three references [31, 33, 39], explicitly refer the use of health care standards, considering the specificity of medical devices (e.g. the already established ISO/IEEE 11073 standards-based Continua personal health ecosystem - X73 protocol [33]).

  • End-to-end solutions: ten references [53,54,55,56,57,58,59,60,61,62] propose interoperability solutions to ensure that the information produced could be integrated into the health care provision.

Table 1. Scope of the included articles.

Moreover, Fig. 2 presents the temporal distribution of the selected studies.

Fig. 2.
figure 2

Evolution of the number of articles per year between 2011 and 2017.

3.2 Target Users

Among the included articles, 19 report studies aiming to develop solutions to support elderly people in their residential environment [29, 31, 33,34,35,36, 38,39,40,41, 43, 45,46,47, 49, 51, 52, 55, 58], four articles report studies targeting patients with chronic conditions (i.e. diabetes [56], cardiovascular diseases [60, 62] and cancer [54]) and the remainder articles do not refer the target users or refer that the target users are patients, without specifying their pathologies.

3.3 Interoperability

The main problem being addressed here is the lack of interoperability among different levels of available technologies which restricts a wider deployment among intermediate and end-users [39], therefore the demand for interoperability among devices is emphasized as most commercially available devices include their own software and communication protocols, which cause serious problems and hinder the application of a standard [33]. Therefore, the shortfalls of dominating insulated available products are highlighted [31].

Concerning the type of interoperability computational support, different solutions’ designations are reported although they pursue the same objective, which is the aggregation of data from multiple sources to provide them in an integrated way to client applications, namely: architectures [36,37,38, 43, 44, 46], gateways [38, 41, 44, 45], middleware [32, 35] or data hub [43].

To address interoperability, the references reported different communication protocols, including Bluetooth Health Device Profile (HDP) [39] and Open Services Gateway initiative (OSGi), a framework for modular systems that simplifies building, deploying, and managing complex applications. OSGi is complemented with the X73 standard data model, which allowed, for instance, the modelling of the information being gathered [33] so that the information resulting from different ambient assisted living systems might be integrated [31].

Next, it will be referred the ten articles (within the 81 references assessed for inclusion) that have been highlighted by this systematic review. These ten articles correspond to end-to-end solutions and they report an effective concern related to the interoperability issue, proposing concrete solutions to ensure that the information produced could be integrated into the health care provision, as summarized in Table 2.

Table 2. Problem addressed, solution and computational support (extended from [23]).

Considering these references [53,54,55,56,57,58,59,60,61,62], which were subject to a depth analysis, in all the solutions reported the focus is on guaranteeing integration of information, being reported in every case that the resulting information is ready to be integrated in the health care service provision. However, concerning this issue, in some cases more details are given than others.

The integration of information from existing eHealth applications to provide integrated data analysis is a central concern [57]. In particular the demand to ensure interoperability of various Personal Health Devices (PHDs) and EHR for continuous monitoring and self-management of patients with chronic diseases [53,54,55,56, 58,59,60]. The need to provide sensor data in proven standard form is denoted, as the existing coding systems do not appear to be sufficient to encode the data resulting from a variety of sensors [55]. Thus, current solutions are considered to lack interoperability and obstruct the establishment of a remote patient monitoring solution market [58]. Three references are particularly focused on the need to find more advanced solutions to guarantee interconnection with the EHR as well as to improve, optimize and reduce the time in care in particular pathologies, specifically diabetes [56], cancer [54] and stroke [60].

In order to address interoperability, the reported solutions include, for instance: an application, the self-management mobile PHR that communicates with PHDs (e.g. blood pressure monitor or pulse oximeter) that have implemented standard protocols so that stored vital signs are converted to HL7 and are transmitted to PHR [59]; a PHR service, interconnected with mHealth applications that use clinical information from the EHR system from a tertiary hospital to provide services to support patients with chronic diseases, such as diabetes patients [56]; an architectural approach to integrate Home-Centred Health-Enabling Technology into Regional Health Information Systems; and a centralized registration of placeholder-documents and a decentralized data storage at patients’ home, using the Systematic Nomenclature for Contexts, Analysis methods and Problems in Health Enabling Technologies (SNOCAP-HET), which is a nomenclature to describe the context of sensor-based measurements in health-enabling technologies [55].

3.4 Interoperability Standards

Regarding the healthcare interoperability standards applied in the proposed solutions, the choice of HL7 was made in most of the solutions in which standardized solutions are reported [53, 55, 58, 59, 61, 62]. X73 Standard Data Model was used in four cases [31, 33, 58, 59] and X73 with HL7 V2.6 was used in two cases [58, 59]. Other standards were stated such as: Bluetooth Health Device Profile [39], Continuity of Care Document (CCD) and Continuity of Care Record (CCR) [59], the standards based on Continua Personal Health ecosystem [31], openEHR [62], LOINC [62], SNOMED-CT [62], DICOM [62], CEN/ISO 13606, which has been designed to support the semantic interoperability of the communications between EHR [60], and FHIR [61, 62].

3.5 Validation

Finally, concerning the methods used to validate the proposed interoperability solutions (Table 3), in one of the cases the evaluation was carried out by meaningful use [53], in another case, after laboratory tested, it was adopted as a routine in two hospitals, having also been investigated its usability and acceptance within professionals using the system [54], and in other cases the options were the proof of concept [38, 58], prototype [28, 29, 33, 37, 44, 46, 57], simulation [48, 50, 60, 62], case study [35, 42], scenarios implementation [30], and clinical trial [59]. In the remaining cases, the validation methods were not reported.

Table 3. Validation (extended from [23]).

As an example, a clinical trial was carried out to evaluate the transmission error rate for the measured vital signs transmitted from PHD to an mHealth application and from this to PHR Systems [59]. Another case was the technological platform that was tested with clinician staff, researchers, electronic support staff and actors playing patients role, having been defined several scenarios to test the technological structure, being stated that, after this phase, the platform would be tested with patients suffering from clinical suspicion of stroke [60].

4 Conclusion

Considering the target users of the applications being reported, surprisingly in most articles the specifications are quite vague (i.e. elderly or patients, in general). Only four articles do specifically refer which are the target users (i.e. patients suffering from diabetes, cardiovascular diseases or cancer).

A central challenge for healthcare applications is how to handle the complexity and variability caused by the specificities of the healthcare processes. Deeper analyses of the healthcare process reveal the intricacy and the changeability of the clinical information and, therefore, the difficulties in dealing with information interoperability. The vague description of the target users and the respective health conditions precludes that additional elicitations of requirements are needed, which will increase the costs and the density of the resulting implementations.

The design and implementation of pervasive health applications has not yet reached its potential in terms of impact it can have on health care provision, and interoperability is assumed as being an essential requirement. In this respect, the included articles reporting end-to-end solutions aimed to turn possible PHD connected in conjunction with institutional EHR systems. For that, the studies propose interoperability platforms able to gather and distribute the clinical information [53,54,55, 57, 58, 60], or applications able to guarantee a common understanding between PHD and EHRs, using a diversity of standards (e.g. HL7, CEN/ISO 13606 or X73). In all the solutions reported the focus is on guaranteeing integration of information, being stated in every case that the resulting information is ready to be integrated in the health care service provision, although in only half of the cases the details concerning this issue, are given more objectively. The integration of information from pervasive health applications to provide integrated data analysis should be a concern. Current solutions lacking interoperability might obstruct the establishment of a remote patient monitoring solution market.

In terms of the validation of the solutions being proposed, only one study [59] included a clinical trial. However, evidence-based medicine is supported on statistical significance and the new developments must be conveniently evaluated in real world conditions. It is necessary to go behind studies aiming the design, development and evaluation of prototypes (i.e. proof-of-concept).

The results of the systematic review presented in this article show that interoperability is not the major concern of a significant number of current technological developments related to pervasive health. Indeed, it should be emphasized that of the 4141 initial references only 81 references explicitly mentioned the issue of interoperability. Moreover, within these 81 references assessed for inclusion, only ten corresponded to end-to-end solutions, since the information produced could be integrated into the health care service provision, where interoperability was considered an effective concern. Finally, within these ten references only three refer standards specifically related to semantic interoperability, used in a system whose validation is not yet reported.

Therefore, large-scale collaboration among technology developers, companies, policy makers, patient’s organizations and health professionals are essential for pervasive health surpass the interoperability challenge.