|
| 1 | +--- |
| 2 | +layout: default |
| 3 | +title: Virtual Assistant Documentation |
| 4 | +permalink: /virtual-assistant/ |
| 5 | +--- |
| 6 | + |
| 7 | +# Virtual Assistant Documentation |
| 8 | + |
| 9 | +The **DT4H Virtual Assistant (VA)** is a tool designed to support clinical researchers in cardiology and related fields. It enables researchers to interact in seven languages for the following tasks: |
| 10 | + |
| 11 | +- Search for and explore studies, cohorts, and patient datasets |
| 12 | +- Request and retrieve metadata before starting deeper exploration |
| 13 | +- Ask targeted questions regarding study characteristics, patient cohorts, or hospital nodes |
| 14 | +- Perform metadata requests in a federated way using a Secure Multi-Party Computation (SMPC) algorithm, ensuring data privacy and compliance with EU standards |
| 15 | + |
| 16 | +> **Note:** Metadata retrieval may take several minutes due to the distributed computation across nodes. It is recommended to request metadata at the beginning of a session. |
| 17 | +
|
| 18 | +All chat history with the VA is automatically stored. Researchers can browse previous conversations at any time, and they have the option to delete or export them. |
| 19 | + |
| 20 | +--- |
| 21 | + |
| 22 | +## Supported Languages |
| 23 | + |
| 24 | +The VA supports interaction in 7 languages, selectable from the top-right menu: |
| 25 | + |
| 26 | +- English |
| 27 | +- Español (Spanish) |
| 28 | +- Svenska (Swedish) |
| 29 | +- Nederlands (Dutch) |
| 30 | +- Italiano (Italian) |
| 31 | +- Română (Romanian) |
| 32 | +- Čeština (Czech) |
| 33 | + |
| 34 | +Researchers can seamlessly switch between languages during interaction, ensuring accessibility across the European research community. |
| 35 | + |
| 36 | + |
| 37 | +*Language selection in the VA* |
| 38 | + |
| 39 | +--- |
| 40 | + |
| 41 | +## Main Features |
| 42 | + |
| 43 | +### Study Search and Exploration |
| 44 | + |
| 45 | +Researchers can use the VA to look for studies with specific patient characteristics, such as chronic kidney disease (CKD). Once a study of interest is identified, the VA also provides detailed information about the hospitals (nodes) that are included in the study. The results are retrieved from the **Data Catalogue (DC)**, which displays the relevant datasets together with their associated attributes. |
| 46 | + |
| 47 | + |
| 48 | +*Example of study search in the VA (part 2)* |
| 49 | + |
| 50 | +--- |
| 51 | + |
| 52 | +### Metadata Request (Federated Step) |
| 53 | + |
| 54 | +Before starting a conversation, researchers can request cohort metadata. This step runs a secure computation across all selected nodes using the SMPC algorithm. |
| 55 | + |
| 56 | +**Steps:** |
| 57 | +1. Select *Request cohort metadata* from the left-hand menu and **Create new request** |
| 58 | +2. Choose the dataset name (e.g., `study1`) |
| 59 | +3. Select the (hospital) nodes to include (e.g., GEM, AUMC) |
| 60 | +4. Click **Create** |
| 61 | + |
| 62 | +> **Note:** This step may take several minutes to complete. The status of the metadata request is shown (e.g., running, exited). |
| 63 | +
|
| 64 | + |
| 65 | +*Overview of aggregated metadata requests* |
| 66 | + |
| 67 | + |
| 68 | +*Creating a new metadata request for a specific study and nodes* |
| 69 | + |
| 70 | +--- |
| 71 | + |
| 72 | +### Conversation with the VA |
| 73 | + |
| 74 | +Once metadata is available, researchers can: |
| 75 | +- Ask questions about patient characteristics (e.g., CKD, heart failure) |
| 76 | +- Retrieve key statistics from the datasets |
| 77 | +- Use data visualization tools for insights |
| 78 | + |
| 79 | +The VA ensures results are based on privacy-preserving federated queries across distributed hospital nodes. |
0 commit comments