From 5af91deaea4b755e770eac29a1ef2faa106271f8 Mon Sep 17 00:00:00 2001 From: Marco Pashkov Date: Tue, 19 May 2020 22:16:17 -0700 Subject: [PATCH 1/2] Clarification and contextual link to the diagrams `main approaches` implies that the app will eventually only use either option 1 or option 2. However, I am guessing the author meant that those are both options to be used in the production app. I further highlighted the two options visually and removed clutter. --- solution_architecture.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/solution_architecture.md b/solution_architecture.md index 0055082..58f7288 100644 --- a/solution_architecture.md +++ b/solution_architecture.md @@ -46,7 +46,9 @@ The app pursues two objectives: First, supporting individuals in finding out whe ### Retrieval of lab results and verification process Reporting positive tests to the app is crucial for others to get informed about a relevant exposure and potential infection. On the other hand, a verification before the uploaded of diagnosis keys is required in order to prevent misuse. -There are two main approaches for this verification: The first option is to use the integrated functionality of the Corona-Warn-App to retrieve the results of a SARS-CoV-2 test. Through this integration, the positive test result is already verified and the diagnosis keys can be uploaded right after users have given their consent. The second option is to receive a human-readable token (e.g. a number or a combination of words) and provide this as verification to the app. This token is called teleTAN. +There are two ways for receiving this verification: +1. Use of the integrated functionality of the Corona-Warn-App to retrieve the results of a SARS-CoV-2 test from a verification server (see Figure 4a). Through this integration, the positive test result is already verified and the diagnosis keys can be uploaded right after users have given their consent. +2. Use of a human-readable token (e.g. a number or a combination of words) and provide this as verification to the app. This token is called teleTAN (see Figure 4b). ![Figure 2: Interaction flow for verification process](images/solution_architecture/figure_2.svg "Figure 2: Interaction flow for verification process") From 0b5b99107e49f709713964f7a8ae035bc305cced Mon Sep 17 00:00:00 2001 From: Marco Pashkov Date: Tue, 19 May 2020 22:19:16 -0700 Subject: [PATCH 2/2] correction of the figures --- solution_architecture.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/solution_architecture.md b/solution_architecture.md index 58f7288..a8fa584 100644 --- a/solution_architecture.md +++ b/solution_architecture.md @@ -47,8 +47,8 @@ The app pursues two objectives: First, supporting individuals in finding out whe Reporting positive tests to the app is crucial for others to get informed about a relevant exposure and potential infection. On the other hand, a verification before the uploaded of diagnosis keys is required in order to prevent misuse. There are two ways for receiving this verification: -1. Use of the integrated functionality of the Corona-Warn-App to retrieve the results of a SARS-CoV-2 test from a verification server (see Figure 4a). Through this integration, the positive test result is already verified and the diagnosis keys can be uploaded right after users have given their consent. -2. Use of a human-readable token (e.g. a number or a combination of words) and provide this as verification to the app. This token is called teleTAN (see Figure 4b). +1. Use of the integrated functionality of the Corona-Warn-App to retrieve the results of a SARS-CoV-2 test from a verification server (see Figure 2, Step 4a). Through this integration, the positive test result is already verified and the diagnosis keys can be uploaded right after users have given their consent. +2. Use of a human-readable token (e.g. a number or a combination of words) and provide this as verification to the app. This token is called teleTAN (see Figure 2, Step 4b). ![Figure 2: Interaction flow for verification process](images/solution_architecture/figure_2.svg "Figure 2: Interaction flow for verification process")