mirror of
https://github.com/corona-warn-app/cwa-documentation
synced 2024-12-29 16:12:13 +01:00
Fix markdown styling to remove linter errors
This commit is contained in:
parent
fe1c33ef0b
commit
2962ac5980
@ -243,7 +243,6 @@ The information listed above is not visible to the user, but is used internally
|
||||
|
||||
![Figure 13: Risk calculation](images/solution_architecture/trl_mapping.svg "Figure 13: Risk calculation")
|
||||
|
||||
|
||||
The Exposure Notification framework allows to attach as "days since onset of symptoms" parameter to the diagnosis key while uploading them to the server. As this parameter strongly influences the infectiousness during an encounter, it is also used in the risk calculation. However, the ENF only allows a translation from the DSOS to either "no risk" (0), "low risk" (1) or "high risk" (2). To allow a more fine grained interpretation of the exposure windows, the additional parameter "report type" (four possible values) is used to derive an internal "Transmission Risk Level" with eight possible values. Of those eight values, two are dropped by the ENF automatically, as the report type "recursive" might be dropped in current implementations. It is important to understand, that the field "report type" does not correspond to the actual report type, but is only technically used as a 2 bit field. The mapping is also shown in Figure 13.
|
||||
|
||||
![Figure 14: Risk calculation](images/solution_architecture/risk_calculation.svg "Figure 14: Risk calculation")
|
||||
|
Loading…
x
Reference in New Issue
Block a user