| Literature DB >> 34694434 |
Ali Amr1,2, Marc Hinderer3, Lena Griebel3, Dominic Deuber4, Christoph Egger4, Farbod Sedaghat-Hamedani1,2, Elham Kayvanpour1,2, Daniel Huhn5, Jan Haas1,2, Karen Frese1,2, Marc Schweig6, Ninja Marnau7, Annika Krämer8, Claudia Durand9, Florian Battke9, Hans-Ulrich Prokosch3, Michael Backes7,8, Andreas Keller10, Dominique Schröder4, Hugo A Katus1,2, Norbert Frey1,2, Benjamin Meder11,12,13.
Abstract
BACKGROUND: The development of Precision Medicine strategies requires high-dimensional phenotypic and genomic data, both of which are highly privacy-sensitive data types. Conventional data management systems lack the capabilities to sufficiently handle the expected large quantities of such sensitive data in a secure manner. PROMISE is a genetic data management concept that implements a highly secure platform for data exchange while preserving patient interests, privacy, and autonomy.Entities:
Keywords: Big data democratization; Data security; Digital health; Genetic data transfer; Privacy; Whole-genome sequencing
Mesh:
Year: 2021 PMID: 34694434 PMCID: PMC9151530 DOI: 10.1007/s00392-021-01942-8
Source DB: PubMed Journal: Clin Res Cardiol ISSN: 1861-0684 Impact factor: 6.138
Fig. 1Overview of the PROMISE platform workflow. The genetic data are cryptographically encrypted after completion of the genetic sequencing (1). The encrypted data is transferred to the PROMISE Cloud for storage and the encryption key is transferred to the PROMISE app (2). This process is done only once and does not need to be repeated. Clients can send a data request to the PROMISE system (3). The request description with precise information on the requested data and the client are transferred to the PROMISE app (4). The patient has the option to accept or decline the request. A token that allows the decryption of the computation is generated for that specific query after the approval (5). The token is then encrypted and sent to the system and client (6). The client receives the encrypted key for that token (7). The computation of the data is performed on the still encrypted data. The results of the encrypted computation are sent to the client (8). The client can decrypt the output of the computation using the decrypted token received from the PROMISE app upon approval of the query. The token can only decrypt the computation for that very specific query and no other information of the patient is revealed, neither to the PROMISE Cloud nor the client
Fig. 2Schematic representation of the study protocol. The patient demographics are obtained from the clinical file at baseline (T1). Patients are requested to fill two validated questionnaires evaluating the anxiety status of the patient and the health-related quality of life: HADS-A and SF-12. The patients are also requested to complete a custom-made questionnaire and to take part in a voice-recorded questionnaire assessing their opinions on different topics regarding genetic testing and data sharing. After the training and installation of the mobile application, the patients receive up to 12 queries over a period of 4 months. A follow-up visit takes place after this time period (T2), where the patients are requested to take the same questionnaires at baseline again plus a questionnaire specifically evaluating PROMISE along with a voice-recorded interview
Fig. 3Exemplary screenshots of the PROMISE app. a A unique matrix code is generated at the initiation process at the sequencing center to register the smartphone to the patient. The encryption key to the data is sent to the patient once the smartphone is registered. b, c The patient can then receive requests from clients to access a specific part of his data. Detailed information regarding the request and the client can be displayed by clicking on the query. The patient has the opportunity to receive more information from the client and to request advice from his physicians. d A password is required to be entered to grant the request and to initiate the computation of the query
Clinical characteristics of the patients and disease-relevant genetic findings
| Gender | Phenotype | Age | Age at disease onset | NYHA class | Ventricular arrhythmia | Atrial fibrillation | LV ejection fraction (%) | Gene | Variant | |
|---|---|---|---|---|---|---|---|---|---|---|
| 1 | M | DCM | 51 | 37 | 1 | No | Yes | 15 | DSG | p.Arg49His |
| 2 | M | HCM | 32 | 30 | 1 | No | No | 65 | MYH7 | p.Asp928Asn |
| 3 | M | HCM | 34 | 25 | 2 | No | No | 65 | – | – |
| 4 | M | DCM | 53 | 37 | 1 | No | No | 35 | MYH7 | p.Arg1193His |
| 5 | M | DCM | 58 | 45 | 2 | No | No | 49 | – | – |
| 6 | F | HCM | 35 | 31 | 2 | No | No | 60 | – | – |
| 7 | M | DCM | 35 | 20 | 2 | No | Yes | 52 | EMD | p.Trp200Ter |
| 8 | F | DCM | 34 | 26 | 2 | No | No | 44 | – | – |
| 9 | F | DCM | 32 | 18 | 1 | No | No | 40 | – | – |
| 10 | M | HCM | 23 | 14 | 1 | No | No | 59 | MYBPC3 | c.3490 + 1G > T |
| 11 | M | DCM | 34 | 24 | 1 | No | No | 57 | – | – |
| 12 | F | DCM | 36 | 19 | 1 | No | No | 55 | – | – |
| 13 | M | HCM | 67 | 58 | 2 | No | Yes | 40 | – | – |
| 14 | F | PPCM/DCM | 50 | 45 | 2 | No | No | 54 | – | – |
| 15 | F | DCM | 57 | 52 | 1 | No | No | 50 | – | – |
| 16 | M | ARVC | 31 | 22 | 1 | No | No | 58 | PKP2 | c.2014-1G > C |
| 17 | F | DCM | 32 | 25 | 2 | No | No | 48 | – | – |
| 18 | M | DCM | 27 | 24 | 1 | Yes | No | 58 | – | – |
| 19 | F | DCM | 43 | 38 | 2 | Yes | Yes | 50 | – | – |
Fig. 4Graphical representation of the acceptance of genetic testing amongst the medical professionals at the university clinic. Medical professionals working at different capacities (physicians, biology researchers, and nurses) in different departments find that genetic testing is acceptable. The vast majority reported that they would undergo diagnostic genetic testing if recommended by the treating physician
Fig. 5Graphical representations of the patients' opinions before and after using the PROMISE system. The concept of PROMISE was introduced to the patients at baseline. The blue bars represent the data acquired before using the PROMISE app (T1), while the orange bars represent the data acquired after using the PROMISE app (T2). The patients were asked if the concept of PROMISE would change their attitude towards the handling of genetic data (a), to give their opinion regarding being in full control of the genetic data (b), and their position towards the security concept of PROMISE (c)
Fig. 6Figures representing the patient’s perspectives of different aspects after using the PROMISE system. The patients were questioned about their willingness to share their genetic data with different entities (university hospitals, research institutions and pharmaceutical companies). The blue and orange bars represent the responses of the patients before (T1) and after (T2) using the PROMISE app