A SOA-Based Platform to Support Clinical Data Sharing

Abstract

The eSource Data Interchange Group, part of the Clinical Data Interchange Standards Consortium, proposed five scenarios to guide stakeholders in the development of solutions for the capture of eSource data. The fifth scenario was subdivided into four tiers to adapt the functionality of electronic health records to support clinical research. In order to develop a system belonging to the “Interoperable” Tier, the authors decided to adopt the service-oriented architecture paradigm to support technical interoperability, Health Level Seven Version 3 messages combined with LOINC (Logical Observation Identifiers Names and Codes) vocabulary to ensure semantic interoperability, and Healthcare Services Specification Project standards to provide process interoperability. The developed architecture enhances the integration between patient-care practice and medical research, allowing clinical data sharing between two hospital information systems and four clinical data management systems/clinical registries. The core is formed by a set of standardized cloud services connected through standardized interfaces, involving client applications. The system was approved by a medical staff, since it reduces the workload for the management of clinical trials. Although this architecture can realize the “Interoperable” Tier, the current solution actually covers the “Connected” Tier, due to local hospital policy restrictions.

Standards for the Reuse of Clinical Data in Research: the Connection of the Liguria HIV Network and the CISAI Cohort

“…The LHN technical implementation choices are based on the recommendations by the Electronic Source Data Interchange (eSDI) group. The whole technical structure adopted and the general architectural approach of the developed solution are completely described in [8], while the technical solutions are similar to those described in [9], [10]. In order to fulfill the European General Data Protection Regulation (GDPR) and to assure adequate protection to patients' privacy, only indispensable personal information is managed such as birth date, sex and nationality.…”

Towards an Electronic Medical Record for Precision Oncology: Information and Knowledge Management

“…Service Oriented Architecture (SOA) is the most widely adopted design strategy to support technical interoperability between real-time applications implemented in large-scale distributed environments. The main reason for the widespread of SOA paradigm is that it proposes a highly feasible strategy to easily promote the integration and alignment of new and existing solutions in a cohesive architecture, with minimal impact for service consumers, resulting in a highly reduced economic cost [19][20][21]. For these reasons, this approach was successfully adopted in distributed healthcare architectures [22,23].…”

A Terminology Service Compliant to CTS2 to Manage Semantics within the Regional HIE

“…CTS2 is one of the products of the HL7 and Object Management Group (OMG) initiative called Healthcare Service Specifi cation Project (HSSP) [13]. Th e aim of HSSP was to define health industry standards based on Service Oriented Architecture (SOA) approach to provide and guarantee an eff ective interoperability between distributed and heterogeneous applications which belong to independent socio-health system organizations [4,13,14,15,16].…”

“…As all HSSP standards, CTS2 is distributed through the HL7 Service Functional Model (SFM), which provides a service interface specification at a functional level, and the OMG Service Technical Model (STM), which specifies the technical requirements of the service [4,7,16]. In details, each OMG STM is formed by a set of human readable specifi cation documents (e.g.…”