From 5b67f5c50749915a98a3df5e4abef7fe0a6e9538 Mon Sep 17 00:00:00 2001 From: jensjensenjens <> Date: Sat, 20 Jun 2020 16:04:07 +0200 Subject: [PATCH 1/9] modified solution architecture in an attempt to make it clearer how things are computed --- solution_architecture.md | 14 ++++++-------- 1 file changed, 6 insertions(+), 8 deletions(-) diff --git a/solution_architecture.md b/solution_architecture.md index 4585d8d..2c22895 100644 --- a/solution_architecture.md +++ b/solution_architecture.md @@ -211,26 +211,24 @@ The information listed above is not visible to the user, but is used internally *Figure 12* displays how the total risk score is being calculated. The application is provided with a set of parameters, which are marked in blue within the figure. Those parameters are regularly downloaded from the CWA Server, which means they can be modified without requiring a new version of the application. -Each risk category (days since exposure, exposure duration, weighted signal attenuation, and the transmission risk factor) receives an input value from the event which is then mapped to a predefined value range. -According to the [documentation of the framework](https://developer.apple.com/documentation/exposurenotification/enexposureconfiguration), "the attenuation is weighted by the duration at each risk level and averaged for the overall duration". -Each of those value ranges is assigned a risk score from 0-8, where 0 represents a very low risk and 8 represents a very high risk. This means that from each of the rows in the figure, one value is selected according to the input value for the corresponding category. The product of the risk scores is used as the **total risk score** of the individual exposure. +Each of the four risk categories (days since exposure, exposure duration, weighted signal attenuation, and the transmission risk factor) receives an input value from the event which is then mapped to a predefined input value interval. As an example: an exposure duration of D=15.3 minutes is mapped to the interval 15 < D <= 20. Note: the transmission risk category does not use input intervals and instead just consists of the values 1-8. Each of those input value intervals is then assigned a risk score from 0-8, where 0 represents a very low risk and 8 represents a very high risk. This means that from each of the rows in the figure, one value is selected according to the input value for the corresponding category. The particular values can be found in the file [`exposure-config.yaml`](https://github.com/corona-warn-app/cwa-server/blob/eb8be6c3e9c723c62c619784e41889d10054cc93/services/distribution/src/main/resources/master-config/exposure-config.yaml) on the CWA server. The product of the four risk scores is used as the **total risk score** of the individual exposure. -In order to incorporate the time spent within the ranges of attenuation buckets mentioned before, each of those three buckets is assigned a weight value as shown in *Figure 13*. +According to the [documentation of the framework](https://developer.apple.com/documentation/exposurenotification/enexposureconfiguration), "the attenuation is weighted by the duration at each risk level and averaged for the overall duration". In order to incorporate the time spent within the ranges of attenuation buckets mentioned before, each of those three buckets is assigned a weight value as shown in *Figure 13*. The individual time values are multiplied with their according weight (*weight_1*, *weight_2* and *weight_3*). Their sum and a default bucket offset (called *weight_4* in *Figure 13*) forms the *Exposure Score*. - The *total risk score* provided by the Exposure Notification Framework is then normalized and multiplied with the exposure score, resulting in the combined risk score. +Finally, the maximum of the *total risk score* over all the considered events, i.e. the largest risk score, is normalized and then multiplied with the above exposure score. The resulting product of the *exposure score* and the *normalized maximum total risk score* is then denoted the **combined risk score**. -The combined risk score is used to determine which defined risk level should be displayed to the user, e.g. “low risk” or “high risk”. For this decision, app-defined thresholds for the individual risk levels apply. +The combined risk score is used to determine which defined risk level should be displayed to the user, e.g. “low risk” or “high risk”. For this decision, [app-defined thresholds](https://github.com/corona-warn-app/cwa-server/blob/eb8be6c3e9c723c62c619784e41889d10054cc93/services/distribution/src/main/resources/master-config/risk-score-classification.yaml) for the individual risk levels apply. As the values above are multiplied with each other, a single category with a risk score of 0 means that the overall risk score is also 0. Additionally, a central threshold for the combined risk score specifies whether an exposure event should be considered or not. Furthermore the Google/Apple framework allows to set a [```minimalRiskScore```](https://developer.apple.com/documentation/exposurenotification/enexposureconfiguration/3583692-minimumriskscore) to exclude exposure incidents with scores lower than the value of this property. In the current version of the API the time spent within the ranges of attenuation buckets are accumulated over all exposure incidents during one matching session. Since the number of requests is currently limited, it is not possible to get these values for each day and each exposure incident separately. -While by default there is no minimum value set, this value is being configured accordingly, so that resumably irrelevant exposure incidents are excluded. +While by default there is no minimum value set, this value is being configured accordingly, so that presumably irrelevant exposure incidents are excluded. ![Figure 13: Calculation of the combined risk score](images/solution_architecture/figure_13.svg "Figure 13: Calculation of the combined risk score") -Note that the transmission risk level plays a special role: It can be defined by the app and be associated with each individual diagnosis key (i.e. specific for each day of an infected person) that is being sent to the server. It contains a value from 1 to 8, which can be used to represent a calculated risk defined by the health authority and estimates the infectiousness and hence the likelihood of transmitting the disease. +Note that the transmission risk level plays a special role in the above calculations: It can be defined by the app and be associated with each individual diagnosis key (i.e. specific for each day of an infected person) that is being sent to the server. It contains a value from 1 to 8, which can be used to represent a calculated risk defined by the health authority. As an example it could contain an estimate of the infectiousness of the potential infector at the time of contact and, hence, the likelihood of transmitting the disease. The specific values are defined as part of the [app](https://github.com/corona-warn-app/cwa-app-android/blob/ddb1f94f1d577f08863ae319c195d80cacf0bc3e/Corona-Warn-App/src/main/java/de/rki/coronawarnapp/util/ProtoFormatConverterExtensions.kt) - a motivation of the parameter choices is found in the document [Epidemiological Motivation of the Transmission Risk Level](https://github.com/corona-warn-app/cwa-documentation/blob/master/transmission_risk.pdf). ### Data Transfer and Data Processing From 8d6539540b0413a838bc1c12a8d6866c96ac3268 Mon Sep 17 00:00:00 2001 From: jensjensenjens <> Date: Sat, 20 Jun 2020 16:07:28 +0200 Subject: [PATCH 2/9] moved link to particular values --- solution_architecture.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/solution_architecture.md b/solution_architecture.md index 2c22895..16a3060 100644 --- a/solution_architecture.md +++ b/solution_architecture.md @@ -210,8 +210,8 @@ The information listed above is not visible to the user, but is used internally ![Figure 12: Risk calculation](images/solution_architecture/figure_12.svg "Figure 12: Risk calculation") *Figure 12* displays how the total risk score is being calculated. The application is provided with a set of parameters, which are marked in blue within the figure. -Those parameters are regularly downloaded from the CWA Server, which means they can be modified without requiring a new version of the application. -Each of the four risk categories (days since exposure, exposure duration, weighted signal attenuation, and the transmission risk factor) receives an input value from the event which is then mapped to a predefined input value interval. As an example: an exposure duration of D=15.3 minutes is mapped to the interval 15 < D <= 20. Note: the transmission risk category does not use input intervals and instead just consists of the values 1-8. Each of those input value intervals is then assigned a risk score from 0-8, where 0 represents a very low risk and 8 represents a very high risk. This means that from each of the rows in the figure, one value is selected according to the input value for the corresponding category. The particular values can be found in the file [`exposure-config.yaml`](https://github.com/corona-warn-app/cwa-server/blob/eb8be6c3e9c723c62c619784e41889d10054cc93/services/distribution/src/main/resources/master-config/exposure-config.yaml) on the CWA server. The product of the four risk scores is used as the **total risk score** of the individual exposure. +Those parameters are regularly downloaded from the CWA Server, which means they can be modified without requiring a new version of the application (see [`exposure-config.yaml`](https://github.com/corona-warn-app/cwa-server/blob/eb8be6c3e9c723c62c619784e41889d10054cc93/services/distribution/src/main/resources/master-config/exposure-config.yaml) for details). +Each of the four risk categories (days since exposure, exposure duration, weighted signal attenuation, and the transmission risk factor) receives an input value from the event which is then mapped to a predefined input value interval. As an example: an exposure duration of D=15.3 minutes is mapped to the interval 15 < D <= 20. Note: the transmission risk category does not use input intervals and instead just consists of the values 1-8. Each of those input value intervals is then assigned a risk score from 0-8, where 0 represents a very low risk and 8 represents a very high risk. This means that from each of the rows in the figure, one value is selected according to the input value for the corresponding category. The product of the four risk scores is used as the **total risk score** of the individual exposure. According to the [documentation of the framework](https://developer.apple.com/documentation/exposurenotification/enexposureconfiguration), "the attenuation is weighted by the duration at each risk level and averaged for the overall duration". In order to incorporate the time spent within the ranges of attenuation buckets mentioned before, each of those three buckets is assigned a weight value as shown in *Figure 13*. The individual time values are multiplied with their according weight (*weight_1*, *weight_2* and *weight_3*). From e4ea91b13f99af85285b1768fc570ae2d62d1268 Mon Sep 17 00:00:00 2001 From: jensjensenjens <> Date: Sat, 20 Jun 2020 16:15:02 +0200 Subject: [PATCH 3/9] added value to the duration example --- solution_architecture.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/solution_architecture.md b/solution_architecture.md index 16a3060..39a5e46 100644 --- a/solution_architecture.md +++ b/solution_architecture.md @@ -211,7 +211,8 @@ The information listed above is not visible to the user, but is used internally *Figure 12* displays how the total risk score is being calculated. The application is provided with a set of parameters, which are marked in blue within the figure. Those parameters are regularly downloaded from the CWA Server, which means they can be modified without requiring a new version of the application (see [`exposure-config.yaml`](https://github.com/corona-warn-app/cwa-server/blob/eb8be6c3e9c723c62c619784e41889d10054cc93/services/distribution/src/main/resources/master-config/exposure-config.yaml) for details). -Each of the four risk categories (days since exposure, exposure duration, weighted signal attenuation, and the transmission risk factor) receives an input value from the event which is then mapped to a predefined input value interval. As an example: an exposure duration of D=15.3 minutes is mapped to the interval 15 < D <= 20. Note: the transmission risk category does not use input intervals and instead just consists of the values 1-8. Each of those input value intervals is then assigned a risk score from 0-8, where 0 represents a very low risk and 8 represents a very high risk. This means that from each of the rows in the figure, one value is selected according to the input value for the corresponding category. The product of the four risk scores is used as the **total risk score** of the individual exposure. +Each of the four risk categories (days since exposure, exposure duration, weighted signal attenuation, and the transmission risk factor) receives an input value from the event which is then mapped to a predefined input value interval. + Each of those input value intervals is then assigned a risk score from 0-8, where 0 represents a very low risk and 8 represents a very high risk. This means that from each of the rows in the figure, one value is selected according to the input value for the corresponding category. As an example: an exposure duration input value of D=15.3 minutes is mapped to the interval 15 < D <= 20, which in the current implementation has a value of 1 assigned to it. The product of the four risk scores is used as the **total risk score** of the individual exposure. According to the [documentation of the framework](https://developer.apple.com/documentation/exposurenotification/enexposureconfiguration), "the attenuation is weighted by the duration at each risk level and averaged for the overall duration". In order to incorporate the time spent within the ranges of attenuation buckets mentioned before, each of those three buckets is assigned a weight value as shown in *Figure 13*. The individual time values are multiplied with their according weight (*weight_1*, *weight_2* and *weight_3*). @@ -228,7 +229,8 @@ While by default there is no minimum value set, this value is being configured a ![Figure 13: Calculation of the combined risk score](images/solution_architecture/figure_13.svg "Figure 13: Calculation of the combined risk score") -Note that the transmission risk level plays a special role in the above calculations: It can be defined by the app and be associated with each individual diagnosis key (i.e. specific for each day of an infected person) that is being sent to the server. It contains a value from 1 to 8, which can be used to represent a calculated risk defined by the health authority. As an example it could contain an estimate of the infectiousness of the potential infector at the time of contact and, hence, the likelihood of transmitting the disease. The specific values are defined as part of the [app](https://github.com/corona-warn-app/cwa-app-android/blob/ddb1f94f1d577f08863ae319c195d80cacf0bc3e/Corona-Warn-App/src/main/java/de/rki/coronawarnapp/util/ProtoFormatConverterExtensions.kt) - a motivation of the parameter choices is found in the document [Epidemiological Motivation of the Transmission Risk Level](https://github.com/corona-warn-app/cwa-documentation/blob/master/transmission_risk.pdf). +Note that the transmission risk level plays a special role in the above calculations: It can be defined by the app and be associated with each individual diagnosis key (i.e. specific for each day of an infected person) that is being sent to the server. It contains a value from 1 to 8, which can be used to represent a calculated risk defined by the health authority. As an example it could contain an estimate of the infectiousness of the potential infector at the time of contact and, hence, the likelihood of transmitting the disease. The specific values are defined as part of the [app](https://github.com/corona-warn-app/cwa-app-android/blob/ddb1f94f1d577f08863ae319c195d80cacf0bc3e/Corona-Warn-App/src/main/java/de/rki/coronawarnapp/util/ProtoFormatConverterExtensions.kt) - a motivation of the parameter choices is found in the document [Epidemiological Motivation of the Transmission Risk Level](https://github.com/corona-warn-app/cwa-documentation/blob/master/transmission_risk.pdf). Note also that the transmission risk category does not use input intervals and instead directly uses the values 1-8. + ### Data Transfer and Data Processing From 1c2293df53c94f94e45340a7f62eb5aacc3e9af9 Mon Sep 17 00:00:00 2001 From: jensjensenjens <> Date: Sat, 20 Jun 2020 16:16:31 +0200 Subject: [PATCH 4/9] added result of exposure risk --- solution_architecture.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/solution_architecture.md b/solution_architecture.md index 39a5e46..ca28f56 100644 --- a/solution_architecture.md +++ b/solution_architecture.md @@ -212,7 +212,7 @@ The information listed above is not visible to the user, but is used internally *Figure 12* displays how the total risk score is being calculated. The application is provided with a set of parameters, which are marked in blue within the figure. Those parameters are regularly downloaded from the CWA Server, which means they can be modified without requiring a new version of the application (see [`exposure-config.yaml`](https://github.com/corona-warn-app/cwa-server/blob/eb8be6c3e9c723c62c619784e41889d10054cc93/services/distribution/src/main/resources/master-config/exposure-config.yaml) for details). Each of the four risk categories (days since exposure, exposure duration, weighted signal attenuation, and the transmission risk factor) receives an input value from the event which is then mapped to a predefined input value interval. - Each of those input value intervals is then assigned a risk score from 0-8, where 0 represents a very low risk and 8 represents a very high risk. This means that from each of the rows in the figure, one value is selected according to the input value for the corresponding category. As an example: an exposure duration input value of D=15.3 minutes is mapped to the interval 15 < D <= 20, which in the current implementation has a value of 1 assigned to it. The product of the four risk scores is used as the **total risk score** of the individual exposure. + Each of those input value intervals is then assigned a risk score from 0-8, where 0 represents a very low risk and 8 represents a very high risk. This means that from each of the rows in the figure, one value is selected according to the input value for the corresponding category. As an example: an exposure duration input value of D=15.3 minutes is mapped to the interval 15 < D <= 20, which in the current implementation has a value of 1 assigned to it, i.e. the *Exposure Risk* would be equal to 1 in this example. The product of the four risk scores is used as the **total risk score** of the individual exposure. According to the [documentation of the framework](https://developer.apple.com/documentation/exposurenotification/enexposureconfiguration), "the attenuation is weighted by the duration at each risk level and averaged for the overall duration". In order to incorporate the time spent within the ranges of attenuation buckets mentioned before, each of those three buckets is assigned a weight value as shown in *Figure 13*. The individual time values are multiplied with their according weight (*weight_1*, *weight_2* and *weight_3*). From 1fc94e5da39bdaee2672c25017c2205c08bc0978 Mon Sep 17 00:00:00 2001 From: jensjensenjens <> Date: Sat, 20 Jun 2020 16:18:04 +0200 Subject: [PATCH 5/9] definition of combined risk score --- solution_architecture.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/solution_architecture.md b/solution_architecture.md index ca28f56..450f791 100644 --- a/solution_architecture.md +++ b/solution_architecture.md @@ -217,7 +217,7 @@ Each of the four risk categories (days since exposure, exposure duration, weight According to the [documentation of the framework](https://developer.apple.com/documentation/exposurenotification/enexposureconfiguration), "the attenuation is weighted by the duration at each risk level and averaged for the overall duration". In order to incorporate the time spent within the ranges of attenuation buckets mentioned before, each of those three buckets is assigned a weight value as shown in *Figure 13*. The individual time values are multiplied with their according weight (*weight_1*, *weight_2* and *weight_3*). Their sum and a default bucket offset (called *weight_4* in *Figure 13*) forms the *Exposure Score*. -Finally, the maximum of the *total risk score* over all the considered events, i.e. the largest risk score, is normalized and then multiplied with the above exposure score. The resulting product of the *exposure score* and the *normalized maximum total risk score* is then denoted the **combined risk score**. +Finally, the maximum of the *total risk score* over all the considered events, i.e. the largest risk score, is normalized and then multiplied with the above exposure score. The resulting product of the *exposure score* and the *normalized maximum total risk score* then forms the so called **combined risk score**. The combined risk score is used to determine which defined risk level should be displayed to the user, e.g. “low risk” or “high risk”. For this decision, [app-defined thresholds](https://github.com/corona-warn-app/cwa-server/blob/eb8be6c3e9c723c62c619784e41889d10054cc93/services/distribution/src/main/resources/master-config/risk-score-classification.yaml) for the individual risk levels apply. As the values above are multiplied with each other, a single category with a risk score of 0 means that the overall risk score is also 0. From 8e723c9d6b6081e66974d2126f5c7be93ed25b92 Mon Sep 17 00:00:00 2001 From: jensjensenjens <> Date: Sat, 20 Jun 2020 16:19:21 +0200 Subject: [PATCH 6/9] removed text about input intervals for the transmission risk --- solution_architecture.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/solution_architecture.md b/solution_architecture.md index 450f791..26d2110 100644 --- a/solution_architecture.md +++ b/solution_architecture.md @@ -229,7 +229,7 @@ While by default there is no minimum value set, this value is being configured a ![Figure 13: Calculation of the combined risk score](images/solution_architecture/figure_13.svg "Figure 13: Calculation of the combined risk score") -Note that the transmission risk level plays a special role in the above calculations: It can be defined by the app and be associated with each individual diagnosis key (i.e. specific for each day of an infected person) that is being sent to the server. It contains a value from 1 to 8, which can be used to represent a calculated risk defined by the health authority. As an example it could contain an estimate of the infectiousness of the potential infector at the time of contact and, hence, the likelihood of transmitting the disease. The specific values are defined as part of the [app](https://github.com/corona-warn-app/cwa-app-android/blob/ddb1f94f1d577f08863ae319c195d80cacf0bc3e/Corona-Warn-App/src/main/java/de/rki/coronawarnapp/util/ProtoFormatConverterExtensions.kt) - a motivation of the parameter choices is found in the document [Epidemiological Motivation of the Transmission Risk Level](https://github.com/corona-warn-app/cwa-documentation/blob/master/transmission_risk.pdf). Note also that the transmission risk category does not use input intervals and instead directly uses the values 1-8. +Note that the transmission risk level plays a special role in the above calculations: It can be defined by the app and be associated with each individual diagnosis key (i.e. specific for each day of an infected person) that is being sent to the server. It contains a value from 1 to 8, which can be used to represent a calculated risk defined by the health authority. As an example it could contain an estimate of the infectiousness of the potential infector at the time of contact and, hence, the likelihood of transmitting the disease. The specific values are defined as part of the [app](https://github.com/corona-warn-app/cwa-app-android/blob/ddb1f94f1d577f08863ae319c195d80cacf0bc3e/Corona-Warn-App/src/main/java/de/rki/coronawarnapp/util/ProtoFormatConverterExtensions.kt) - a motivation of the parameter choices is found in the document [Epidemiological Motivation of the Transmission Risk Level](https://github.com/corona-warn-app/cwa-documentation/blob/master/transmission_risk.pdf). ### Data Transfer and Data Processing From 014b11a7158a08802478819445321d2a9a459faf Mon Sep 17 00:00:00 2001 From: jensjensenjens <57993322+jensjensenjens@users.noreply.github.com> Date: Sun, 21 Jun 2020 18:56:54 +0200 Subject: [PATCH 7/9] Update solution_architecture.md Linking to master instead of specific version of exposure-config.yaml. Co-authored-by: Michael Frey --- solution_architecture.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/solution_architecture.md b/solution_architecture.md index 26d2110..ed2de15 100644 --- a/solution_architecture.md +++ b/solution_architecture.md @@ -210,7 +210,7 @@ The information listed above is not visible to the user, but is used internally ![Figure 12: Risk calculation](images/solution_architecture/figure_12.svg "Figure 12: Risk calculation") *Figure 12* displays how the total risk score is being calculated. The application is provided with a set of parameters, which are marked in blue within the figure. -Those parameters are regularly downloaded from the CWA Server, which means they can be modified without requiring a new version of the application (see [`exposure-config.yaml`](https://github.com/corona-warn-app/cwa-server/blob/eb8be6c3e9c723c62c619784e41889d10054cc93/services/distribution/src/main/resources/master-config/exposure-config.yaml) for details). +Those parameters are regularly downloaded from the CWA Server, which means they can be modified without requiring a new version of the application (see [`exposure-config.yaml`](https://github.com/corona-warn-app/cwa-server/blob/master/services/distribution/src/main/resources/master-config/exposure-config.yaml) for details). Each of the four risk categories (days since exposure, exposure duration, weighted signal attenuation, and the transmission risk factor) receives an input value from the event which is then mapped to a predefined input value interval. Each of those input value intervals is then assigned a risk score from 0-8, where 0 represents a very low risk and 8 represents a very high risk. This means that from each of the rows in the figure, one value is selected according to the input value for the corresponding category. As an example: an exposure duration input value of D=15.3 minutes is mapped to the interval 15 < D <= 20, which in the current implementation has a value of 1 assigned to it, i.e. the *Exposure Risk* would be equal to 1 in this example. The product of the four risk scores is used as the **total risk score** of the individual exposure. From fad0c580b8b684b1ea2be4cd4b626afbee026e2e Mon Sep 17 00:00:00 2001 From: jensjensenjens <57993322+jensjensenjens@users.noreply.github.com> Date: Sun, 21 Jun 2020 18:57:24 +0200 Subject: [PATCH 8/9] Update solution_architecture.md Linking to master instead of specific file version. Co-authored-by: Michael Frey --- solution_architecture.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/solution_architecture.md b/solution_architecture.md index ed2de15..f07e063 100644 --- a/solution_architecture.md +++ b/solution_architecture.md @@ -219,7 +219,7 @@ According to the [documentation of the framework](https://developer.apple.com/do Their sum and a default bucket offset (called *weight_4* in *Figure 13*) forms the *Exposure Score*. Finally, the maximum of the *total risk score* over all the considered events, i.e. the largest risk score, is normalized and then multiplied with the above exposure score. The resulting product of the *exposure score* and the *normalized maximum total risk score* then forms the so called **combined risk score**. -The combined risk score is used to determine which defined risk level should be displayed to the user, e.g. “low risk” or “high risk”. For this decision, [app-defined thresholds](https://github.com/corona-warn-app/cwa-server/blob/eb8be6c3e9c723c62c619784e41889d10054cc93/services/distribution/src/main/resources/master-config/risk-score-classification.yaml) for the individual risk levels apply. +The combined risk score is used to determine which defined risk level should be displayed to the user, e.g. “low risk” or “high risk”. For this decision, [app-defined thresholds](https://github.com/corona-warn-app/cwa-server/blob/master/services/distribution/src/main/resources/master-config/risk-score-classification.yaml) for the individual risk levels apply. As the values above are multiplied with each other, a single category with a risk score of 0 means that the overall risk score is also 0. Additionally, a central threshold for the combined risk score specifies whether an exposure event should be considered or not. Furthermore the Google/Apple framework allows to set a [```minimalRiskScore```](https://developer.apple.com/documentation/exposurenotification/enexposureconfiguration/3583692-minimumriskscore) to exclude exposure incidents with scores lower than the value of this property. From 5390cab699a33a48a5d3874a3a29398108aff2d4 Mon Sep 17 00:00:00 2001 From: jensjensenjens <57993322+jensjensenjens@users.noreply.github.com> Date: Sun, 21 Jun 2020 18:58:44 +0200 Subject: [PATCH 9/9] Update solution_architecture.md Linking to master/main instead of specific version. Co-authored-by: Michael Frey --- solution_architecture.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/solution_architecture.md b/solution_architecture.md index f07e063..d55b0b9 100644 --- a/solution_architecture.md +++ b/solution_architecture.md @@ -229,7 +229,7 @@ While by default there is no minimum value set, this value is being configured a ![Figure 13: Calculation of the combined risk score](images/solution_architecture/figure_13.svg "Figure 13: Calculation of the combined risk score") -Note that the transmission risk level plays a special role in the above calculations: It can be defined by the app and be associated with each individual diagnosis key (i.e. specific for each day of an infected person) that is being sent to the server. It contains a value from 1 to 8, which can be used to represent a calculated risk defined by the health authority. As an example it could contain an estimate of the infectiousness of the potential infector at the time of contact and, hence, the likelihood of transmitting the disease. The specific values are defined as part of the [app](https://github.com/corona-warn-app/cwa-app-android/blob/ddb1f94f1d577f08863ae319c195d80cacf0bc3e/Corona-Warn-App/src/main/java/de/rki/coronawarnapp/util/ProtoFormatConverterExtensions.kt) - a motivation of the parameter choices is found in the document [Epidemiological Motivation of the Transmission Risk Level](https://github.com/corona-warn-app/cwa-documentation/blob/master/transmission_risk.pdf). +Note that the transmission risk level plays a special role in the above calculations: It can be defined by the app and be associated with each individual diagnosis key (i.e. specific for each day of an infected person) that is being sent to the server. It contains a value from 1 to 8, which can be used to represent a calculated risk defined by the health authority. As an example it could contain an estimate of the infectiousness of the potential infector at the time of contact and, hence, the likelihood of transmitting the disease. The specific values are defined as part of the [app](https://github.com/corona-warn-app/cwa-app-android/blob/master/Corona-Warn-App/src/main/java/de/rki/coronawarnapp/util/ProtoFormatConverterExtensions.kt) - a motivation of the parameter choices is found in the document [Epidemiological Motivation of the Transmission Risk Level](https://github.com/corona-warn-app/cwa-documentation/blob/master/transmission_risk.pdf). ### Data Transfer and Data Processing