JMIR Med Informmedinform7JMIR Medical InformaticsJMIR Med Inform2291-9694JMIR PublicationsToronto, Canadav12i1e6742910.2196/67429Letter to the EditorAuthors’ Reply: The University Medicine Greifswald’s Trusted Third Party Dispatcher: State-of-the-Art Perspective Into Comprehensive Architectures and Complex Research WorkflowsWündischEricMSc1HufnaglPeterProf Dr2BruneckerPeterDr rer medic3Meier zu UmmelnSophieCEng1TrägerSarahMA1PrasserFabianProf Dr4*WeberJoachimDr med156*Core Unit Treuhandstelle, Berlin Institute of Health at Charité – Universitätsmedizin Berlin, Charitéplatz 1Berlin, GermanyDigital Pathology, Charité – Universitätsmedizin Berlin, Berlin, GermanyCore Unit Research IT, Berlin Institute of Health at Charité – Universitätsmedizin Berlin, Berlin, GermanyMedical Informatics Group, Center of Health Data Science, Berlin Institute of Health at Charité – Universitätsmedizin Berlin, Berlin, GermanyCenter for Stroke Research Berlin, Charité – Universitätsmedizin Berlin, Berlin, GermanyGerman Centre for Cardiovascular Research (DZHK), Berlin, GermanyIannaccioAmandaLeungTiffanyCorrespondence to Eric Wündisch, MSc, Core Unit Treuhandstelle, Berlin Institute of Health at Charité – Universitätsmedizin Berlin, Charitéplatz 1, Berlin, 10117, Germany, 49 1523 1394295; eric.wuendisch@charite.de
This is an open-access article distributed under the terms of the Creative Commons Attribution License (https://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work, first published in JMIR Medical Informatics, is properly cited. The complete bibliographic information, a link to the original publication on https://medinform.jmir.org/, as well as this copyright and license information must be included.
https://medinform.jmir.org/2024/1/e53075/https://medinform.jmir.org/2024/1/e65784/architecturescalabilitytrusted third partyapplicationsecurityconsentidentifying datainfrastructuremodularsoftwareimplementationuser interfacehealth platformdata managementdata privacyhealth recordelectronic health recordEHRpseudonymization
We would like to thank the authors of the letter [1] for their comments and for taking the time to engage with our work [2]. Their remarks provide us with the opportunity to clarify a key aspect of our article, and we are pleased to address the points they raised.
Most of the comments from the authors refer to functionalities provided by the TTP Dispatcher component. As mentioned in our article, our work focused on building a trusted third party (TTP) platform using open components, that is, software that is publicly available to the community [2]. For this reason, we built our platform around the core components Enterprise Identifier Cross-Referencing (E-PIX), Generic Pseudonym Administration Service (gPAS), and Generic Informed Consent Service (gICS), and we are grateful that these components are available as open versions. Consequently, we only covered the functionalities supported by these core components in the Requirements section. However, we did describe the TTP Dispatcher in the Comparison With Prior Work section and explicitly noted that it supports some of the functionalities we implemented, though not as open software at the time of writing.
Regarding authentication and authorization, we would like to note that the second table in our article [2] describes additional requirements that we elicited, which apply not only to the core components but also to the broader platform we envisioned [2]. Consequently, these requirements are not limited to the core components, and we note that E-PIX, gPAS, and gICS are not mentioned in the table. For example, the User interfaces and services requirements category, which lists the need for a “[c]ommon authentication and authorization framework with single-sign-on and associated rights and roles with the ability to connect to institutional directory services,” also includes the requirement for an “[i]ntegrated user interface across all services.” The Keycloak-based authentication and authorization mechanism we describe in the paper integrates with this user interface as well [2].
The additional information provided in the letter regarding the TTP Dispatcher’s functionalities and Keycloak support for E-PIX, gPAS, and gICS could be valuable to interested readers of our article, and we thank the authors for offering these insights. We look forward to further exchanges with the authors on the topic of TTP services, including the adoption of HL7 FHIR (Health Level Seven International Fast Healthcare Interoperability Resources).
None declared.
AbbreviationsE-PIX
Enterprise Identifier Cross-Referencing
gICS
Generic Informed Consent Service
gPAS
Generic Pseudonym Administration Service
HL7 FHIR
Health Level Seven International Fast Healthcare Interoperability Resources
TTP
trusted third party
ReferencesBialkeMStahlDLeddigTHoffmannWThe University Medicine Greifswald’s trusted third party dispatcher: state-of-the-art perspective into comprehensive architectures and complex research workflowsJMIR Med Inform202412e6578410.2196/65784WündischEHufnaglPBruneckerPDevelopment of a trusted third party at a large university hospital: design and implementation studyJMIR Med Inform2024041812e5307510.2196/5307538632712