London SynEx Demonstrator Site: Impact Assessment Report

The key ingredients of the SynEx-UCL software components are: 1. A comprehensive and federated electronic healthcare record that can be used to reference or to store all of the necessary healthcare information acquired from a diverse range of clinical databases and patient-held devices. 2. A directory service component to provide a core persons demographic database to search for and authenticate staff users of the system and to anchor patient identification and connection to their federated healthcare record. 3. A clinical record schema management tool (Object Dictionary Client) that enables clinicians or engineers to define and export the data sets mapping to individual feeder systems. 4. An expansible set of clinical management algorithms that provide prompts to the patient or clinician to assist in the management of patient care. CHIME has built up over a decade of experience within Europe on the requirements and information models that are needed to underpin comprehensive multiprofessional electronic healthcare records. The resulting architecture models have influenced new European standards in this area, and CHIME has designed and built prototype EHCR components based on these models. The demonstrator systems described here utilise a directory service and object-oriented engineering approach, and support the secure, mobile and distributed access to federated healthcare records via web-based services. The design and implementation of these software components has been founded on a thorough analysis of the clinical, technical and ethico-legal requirements for comprehensive EHCR systems, published through previous project deliverables and in future planned papers. The clinical demonstrator site described in this report has provided the solid basis from which to establish "proof of concept" verification of the design approach, and a valuable opportunity to install, test and evaluate the results of the component engineering undertaken during the EC funded project. Inevitably, a number of practical implementation and deployment obstacles have been overcome through this journey, each of those having contributed to the time taken to deliver the components but also to the richness of the end products. UCL is fortunate that the Whittington Hospital, and the department of cardiovascular medicine in particular, is committed to a long-term vision built around this work. That vision, outlined within this report, is shared by the Camden and Islington Health Authority and by many other purchaser and provider organisations in the area, and by a number of industrial parties. They are collectively determined to support the Demonstrator Site as an ongoing project well beyond the life of the EC SynEx Project. This report, although a final report as far as the EC project is concerned, is really a description of the first phase in establishing a centre of healthcare excellence. New EC Fifth Framework project funding has already been approved to enable new and innovative technology solutions to be added to the work already established in north London

Design and implementation of a federated health record server

This paper describes the practical implementation of a federated health record serverbased on a generic and comprehensive public domain architecture and deployed in alive clinical setting.The authors, working at the Centre for Health Informatics and MultiprofessionalEducation (University College London), have built up over a decade of experiencewithin Europe on the requirements and information models that are needed to underpincomprehensive multi-professional electronic health records. This work has involvedcollaboration with a wide range of healthcare and informatics organisations and partnersin the healthcare computing industry across Europe though the EU Health Telematicsprojects GEHR, Synapses, EHCR-SupA, SynEx and Medicate. The resultingarchitecture models have influenced recent European standards in this area, such asCEN TC/251 ENV 13606. UCL has now designed and built a federated health recordserver based on these models which is now running in the Department ofCardiovascular Medicine at the Whittington Hospital in north London. A new EC FifthFramework project, 6WINIT, is enabling new and innovative IPv6 and wirelesstechnology solutions to be added to this work.The north London clinical demonstrator site has provided the solid basis from which toestablish "proof of concept" verification of the design approach, and a valuableopportunity to install, test and evaluate the results of the component engineeringundertaken during the EC funded projects

ROMOP: a light-weight R package for interfacing with OMOP-formatted electronic health record data.

Objectives:Electronic health record (EHR) data are increasingly used for biomedical discoveries. The nature of the data, however, requires expertise in both data science and EHR structure. The Observational Medical Out-comes Partnership (OMOP) common data model (CDM) standardizes the language and structure of EHR data to promote interoperability of EHR data for research. While the OMOP CDM is valuable and more attuned to research purposes, it still requires extensive domain knowledge to utilize effectively, potentially limiting more widespread adoption of EHR data for research and quality improvement. Materials and methods:We have created ROMOP: an R package for direct interfacing with EHR data in the OMOP CDM format. Results:ROMOP streamlines typical EHR-related data processes. Its functions include exploration of data types, extraction and summarization of patient clinical and demographic data, and patient searches using any CDM vocabulary concept. Conclusion:ROMOP is freely available under the Massachusetts Institute of Technology (MIT) license and can be obtained from GitHub (http://github.com/BenGlicksberg/ROMOP). We detail instructions for setup and use in the Supplementary Materials. Additionally, we provide a public sandbox server containing synthesized clinical data for users to explore OMOP data and ROMOP (http://romop.ucsf.edu)

Development of grid frameworks for clinical trials and epidemiological studies

E-Health initiatives such as electronic clinical trials and epidemiological studies require access to and usage of a range of both clinical and other data sets. Such data sets are typically only available over many heterogeneous domains where a plethora of often legacy based or in-house/bespoke IT solutions exist. Considerable efforts and investments are being made across the UK to upgrade the IT infrastructures across the National Health Service (NHS) such as the National Program for IT in the NHS (NPFIT) [1]. However, it is the case that currently independent and largely non-interoperable IT solutions exist across hospitals, trusts, disease registries and GP practices – this includes security as well as more general compute and data infrastructures. Grid technology allows issues of distribution and heterogeneity to be overcome, however the clinical trials domain places special demands on security and data which hitherto the Grid community have not satisfactorily addressed. These challenges are often common across many studies and trials hence the development of a re-usable framework for creation and subsequent management of such infrastructures is highly desirable. In this paper we present the challenges in developing such a framework and outline initial scenarios and prototypes developed within the MRC funded Virtual Organisations for Trials and Epidemiological Studies (VOTES) project [2]

Building Data-Driven Pathways From Routinely Collected Hospital Data:A Case Study on Prostate Cancer

Background: Routinely collected data in hospitals is complex, typically heterogeneous, and scattered across multiple Hospital Information Systems (HIS). This big data, created as a byproduct of health care activities, has the potential to provide a better understanding of diseases, unearth hidden patterns, and improve services and cost. The extent and uses of such data rely on its quality, which is not consistently checked, nor fully understood. Nevertheless, using routine data for the construction of data-driven clinical pathways, describing processes and trends, is a key topic receiving increasing attention in the literature. Traditional algorithms do not cope well with unstructured processes or data, and do not produce clinically meaningful visualizations. Supporting systems that provide additional information, context, and quality assurance inspection are needed. Objective: The objective of the study is to explore how routine hospital data can be used to develop data-driven pathways that describe the journeys that patients take through care, and their potential uses in biomedical research; it proposes a framework for the construction, quality assessment, and visualization of patient pathways for clinical studies and decision support using a case study on prostate cancer. Methods: Data pertaining to prostate cancer patients were extracted from a large UK hospital from eight different HIS, validated, and complemented with information from the local cancer registry. Data-driven pathways were built for each of the 1904 patients and an expert knowledge base, containing rules on the prostate cancer biomarker, was used to assess the completeness and utility of the pathways for a specific clinical study. Software components were built to provide meaningful visualizations for the constructed pathways. Results: The proposed framework and pathway formalism enable the summarization, visualization, and querying of complex patient-centric clinical information, as well as the computation of quality indicators and dimensions. A novel graphical representation of the pathways allows the synthesis of such information. Conclusions: Clinical pathways built from routinely collected hospital data can unearth information about patients and diseases that may otherwise be unavailable or overlooked in hospitals. Data-driven clinical pathways allow for heterogeneous data (ie, semistructured and unstructured data) to be collated over a unified data model and for data quality dimensions to be assessed. This work has enabled further research on prostate cancer and its biomarkers, and on the development and application of methods to mine, compare, analyze, and visualize pathways constructed from routine data. This is an important development for the reuse of big data in hospitals

Consolidated List of Requirements

This document is a consolidated catalogue of requirements for the Electronic Health Care Record (EHCR) and Electronic Health Care Record Architecture (EHCRA), gleaned largely from work done in the EU Framework III and IV programmes and CEN, but also including input from other sources including world-wide standardisation initiatives. The document brings together the relevant work done into a classified inventory of requirements to inform the on-going standardisation process as well as act as a guide to future implementation of EHCRA-based systems. It is meant as a contribution both to understanding of the standard and to the work that is being considered to improve the standard. Major features include the classification into issues affecting the Health Care Record, the EHCR, EHCR processing, EHCR interchange and the sharing of health care information and EHCR systems. The principal information sources are described briefly. It is offered as documentation that is complementary to the four documents of the ENV 13606 Parts I-IV produced by CEN Pts 26,27,28,29. The requirements identified and classified in this deliverable are referenced in other deliverables