Next-generation study databases require FAIR, EHR-integrated, and scalable Electronic Data Capture for medical documentation and decision support.

Structured patient data play a key role in all types of clinical research. They are often collected in study databases for research purposes. In order to describe characteristics of a next-generation study database and assess the feasibility of its implementation a proof-of-concept study in a German university hospital was performed. Key characteristics identified include FAIR access to electronic case report forms (eCRF), regulatory compliant Electronic Data Capture (EDC), an EDC with electronic health record (EHR) integration, scalable EDC for medical documentation, patient generated data, and clinical decision support. In a local case study, we then successfully implemented a next-generation study database for 19 EDC systems (n = 2217 patients) that linked to i.s.h.med (Oracle Cerner) with the local EDC system called OpenEDC. Desiderata of next-generation study databases for patient data were identified from ongoing local clinical study projects in 11 clinical departments at Heidelberg University Hospital, Germany, a major tertiary referral hospital. We compiled and analyzed feature and functionality requests submitted to the OpenEDC team between May 2021 and July 2023. Next-generation study databases are technically and clinically feasible. Further research is needed to evaluate if our approach is feasible in a multi-center setting as well.

3LGM2IHE: Requirements for Data-Protection-Compliant Research Infrastructures-A Systematic Comparison of Theory and Practice-Oriented Implementation.

OBJECTIVES: The TMF (Technology, Methods, and Infrastructure for Networked Medical Research) Data Protection Guide (TMF-DP) makes path-breaking recommendations on the subject of data protection in research projects. It includes comprehensive requirements for applications such as patient lists, pseudonymization services, and consent management services. Nevertheless, it lacks a structured, categorized list of requirements for simplified application in research projects and systematic evaluation. The 3LGM2IHE ("Three-layer Graphbased meta model - Integrating the Healthcare Enterprise [IHE] " ) project is funded by the German Research Foundation (DFG). 3LGM2IHE aims to define modeling paradigms and implement modeling tools for planning health care information systems. In addition, one of the goals is to create and publish 3LGM2 information system architecture design patterns (short "design patterns") for the community as design models in terms of a framework. A structured list of data protection-related requirements based on the TMF-DP is a precondition to integrate functions (3LGM2 Domain Layer) and building blocks (3LGM2 Logical Tool Layer) in 3LGM2 design patterns. METHODS: In order to structure the continuous text of the TMF-DP, requirement types were defined in a first step. In a second step, dependencies and delineations of the definitions were identified. In a third step, the requirements from the TMF-DP were systematically extracted. Based on the identified lists of requirements, a fourth step included the comparison of the identified requirements with exemplary open source tools as provided by the "Independent Trusted Third Party of the University Medicine Greifswald" (TTP tools). RESULTS: As a result, four lists of requirements were created, which contain requirements for the "patient list", the "pseudonymization service", and the "consent management", as well as cross-component requirements from the TMF-DP chapter 6 in a structured form. Further to requirements (1), possible variants (2) of implementations (to fulfill a single requirement) and recommendations (3) were identified. A comparison of the requirements lists with the functional scopes of the open source tools E-PIX (record linkage), gPAS (pseudonym management), and gICS (consent management) has shown that these fulfill more than 80% of the requirements. CONCLUSIONS: A structured set of data protection-related requirements facilitates a systematic evaluation of implementations with respect to the fulfillment of the TMF-DP guidelines. These re-usable lists provide a decision aid for the selection of suitable tools for new research projects. As a result, these lists form the basis for the development of data protection-related 3LGM2 design patterns as part of the 3LGM2IHE project.

Structured, Harmonized, and Interoperable Integration of Clinical Routine Data to Compute Heart Failure Risk Scores.

Risk prediction in patients with heart failure (HF) is essential to improve the tailoring of preventive, diagnostic, and therapeutic strategies for the individual patient, and effectively use health care resources. Risk scores derived from controlled clinical studies can be used to calculate the risk of mortality and HF hospitalizations. However, these scores are poorly implemented into routine care, predominantly because their calculation requires considerable efforts in practice and necessary data often are not available in an interoperable format. In this work, we demonstrate the feasibility of a multi-site solution to derive and calculate two exemplary HF scores from clinical routine data (MAGGIC score with six continuous and eight categorical variables; Barcelona Bio-HF score with five continuous and six categorical variables). Within HiGHmed, a German Medical Informatics Initiative consortium, we implemented an interoperable solution, collecting a harmonized HF-phenotypic core data set (CDS) within the openEHR framework. Our approach minimizes the need for manual data entry by automatically retrieving data from primary systems. We show, across five participating medical centers, that the implemented structures to execute dedicated data queries, followed by harmonized data processing and score calculation, work well in practice. In summary, we demonstrated the feasibility of clinical routine data usage across multiple partner sites to compute HF risk scores. This solution can be extended to a large spectrum of applications in clinical care.

The Process of Modeling Information System Architectures with IHE.

IHE has defined more than 200 integration profiles in order to improve the interoperability of application systems in healthcare. These profiles describe how standards should be used in particular use cases. These profiles are very helpful but their correct use is challenging, if the user is not familiar to the specifications. Therefore, inexperienced modelers of information systems quickly lose track of existing IHE profiles. In addition, the users of these profiles are often not aware of rules that are defined within these profiles and of dependencies that exist between the profiles. There are also modelers that do not notice the differences between the implemented actors, because they do not know the optional capabilities of some actors. The aim of this paper is therefore to describe a concept how modelers of information systems can be supported in the selection and use of IHE profiles and how this concept was prototypically implemented in the "Three-layer Graph-based meta model" modeling tool (3LGM2 Tool). The described modeling process consists of the following steps that can be looped: defining the use case, choosing suitable integration profiles, choosing actors and their options and assigning them to application systems, checking for required actor groupings and modeling transactions. Most of these steps were implemented in the 3LGM2 Tool. Further implementation effort and evaluation of our approach by inexperienced users is needed. But after that our tool should be a valuable tool for modelers planning healthcare information system architectures, in particular those based on IHE.

Using openEHR in XDS.b Environments - Opportunities and Challenges.

The HiGHmed research project as part of Germany's Medical Informatics Initiative aims to establish Medical Data Integration Centers (MeDIC) at each participating institution to integrate data of multiple primary information systems in a single place. The MeDICs are based on an IHE XDS.b Affinity Domain in conjunction with an openEHR clinical data repository. This paper presents two ways of storing and retrieving structured and semantically annotated data from an openEHR repository whilst keeping data integrated in an existing IHE XDS.b infrastructure. Furthermore, the paper discusses multiple benefits of the presented approach as well as challenges and corresponding solutions.

Towards a comprehensive and interoperable representation of consent-based data usage permissions in the German medical informatics initiative.

BACKGROUND: The aim of the German Medical Informatics Initiative is to establish a national infrastructure for integrating and sharing health data. To this, Data Integration Centers are set up at university medical centers, which address data harmonization, information security and data protection. To capture patient consent, a common informed consent template has been developed. It consists of different modules addressing permissions for using data and biosamples. On the technical level, a common digital representation of information from signed consent templates is needed. As the partners in the initiative are free to adopt different solutions for managing consent information (e.g. IHE BPPC or HL7 FHIR Consent Resources), we had to develop an interoperability layer. METHODS: First, we compiled an overview of data items required to reflect the information from the MII consent template as well as patient preferences and derived permissions. Next, we created entity-relationship diagrams to formally describe the conceptual data model underlying relevant items. We then compared this data model to conceptual models describing representations of consent information using different interoperability standards. We used the result of this comparison to derive an interoperable representation that can be mapped to common standards. RESULTS: The digital representation needs to capture the following information: (1) version of the consent, (2) consent status for each module, and (3) period of validity of the status. We found that there is no generally accepted solution to represent status information in a manner interoperable with all relevant standards. Hence, we developed a pragmatic solution, comprising codes which describe combinations of modules with a basic set of status labels. We propose to maintain these codes in a public registry called ART-DECOR. We present concrete technical implementations of our approach using HL7 FHIR and IHE BPPC which are also compatible with the open-source consent management software gICS. CONCLUSIONS: The proposed digital representation is (1) generic enough to capture relevant information from a wide range of consent documents and data use regulations and (2) interoperable with common technical standards. We plan to extend our model to include more fine-grained status codes and rules for automated access control.

Towards a Software Tool for Planning IHE-Compliant Information Systems.

As hospital information systems are complex and the requirements for interoperability grow with the increasing networking in healthcare, careful planning becomes more and more necessary. The use of standards as described in IHE profiles, for example, are an important prerequisite for enabling interoperability. Enterprise Architecture Planning (EAP) methods should support this, but none of the currently available EAP methods offers the option of using IHE profiles. The 3LGM2IHE project wants to close this gap and implement the support of IHE profiles in the 3LGM2 tool. This paper describes how requirements for this tool were determined and presents the results.

Implementing Modular Research Consents Using IHE Advanced Patient Privacy Consents.

The re-use of healthcare information for biomedical research is increasing and with it the importance of a consent management framework implementing computable consents. Based on requirements concerning a consent representation the Advanced Patient Privacy Consents (APPC) Profile of Integrating the Healthcare Enterprise (IHE) is evaluated and mapped to these requirements. As IHE APPC was developed for computable patient consents, the mapping of consents for research projects is possible by re-using the elements defined. Compared to other approaches like gICS, approaches using APPC can be based on commercial software products and integrated into IHE environments. IHE APPC was already successfully used in EHR projects like INFOPAT. For interoperability reasons IT platforms intending to support biomedical research including clinical data, research data, biomaterial and imaging data, IHE APPC seems to be an appropriate standard to choose.

From SOMDA to application - integration strategies in the OR.NET demonstration sites.

The effective development and dissemination of the open integration for the next generation of operating rooms require a comprehensive testing environment. In this paper, we present the various challenges to be addressed in demonstration applications, and we discuss the implementation approach, the foci of the demonstration sites and the evaluation efforts. Overall, the demonstrator setups have proven the feasibility of the service-oriented medical device architecture (SOMDA) and real-time approaches with a large variety of example applications. The applications demonstrate the potentials of open device interoperability. The demonstrator implementations were technically evaluated as well as discussed with many clinicians from various disciplines. However, the evaluation is still an ongoing research at the demonstration sites. Technical evaluation focused on the properties of a network of medical devices, latencies in data transmission and stability. A careful evaluation of the SOMDA design decisions and implementations are essential to a safe and reliable interoperability of integrated medical devices and information technology (IT) system in the especially critical working environment. The clinical evaluation addressed the demands of future users and stakeholders, especially surgeons, anesthesiologists, scrub nurses and hospital operators. The opinions were carefully collected to gain further insights into the potential benefits of the technology and pitfalls in future work.

Micro- and Macrointegration Profiles for Medical Devices and Medical IT Systems.

Collecting, saving, and providing patient data are essential processes of documentation in a hospital. Many IT systems have evolved to provide solutions in this area. The automatic transfer of medical device data to these information systems is a new challenge for hospital IT systems. Some vendors are focused on the integration of medical IT systems and medical devices. They provide great solutions with magnificent features. Nevertheless, those integration solutions are proprietary and isolated, limiting the operator's selection of his medical devices and medical IT systems. Standardizing communication processes within the operating room and between medical devices and medical IT systems brings benefits for both patient and hospital staff. This work identifies and proposes micro- and macrointegration profiles as a basis for new IHE Integration Profiles for both medical IT systems and medical devices of the operating room.

Towards shared patient records: an architecture for using routine data for nationwide research.

Ubiquitous information is currently one of the most challenging slogans in medical informatics research. An adequate architecture for shared electronic patient records is needed which can use data for multiple purposes and which is extensible for new research questions. We introduce eardap as architecture for using routine data for nationwide clinical research in a multihospital environment. eardap can be characterized as terminology-based. Main advantage of our approach is the extensibility by new items and new research questions. Once the definition of items for a research question is finished, a consistent, corresponding database can be created without any informatics skills. Our experiences in pediatric oncology in Germany have shown the applicability of eardap. The functions of our core system were in routine clinical use in several hospitals. We validated the terminology management system (TMS) and the module generation tool with the basic data set of pediatric oncology. The multiple usability depends mainly on the quality of item planning in the TMS. High quality harmonization will lead to a higher amount of multiply used data. When using eardap, special emphasis is to be placed on interfaces to local hospital information systems and data security issues.