-
Notifications
You must be signed in to change notification settings - Fork 343
Transmission risk level paper correction #384
Comments
Thanks for the information. We will reach out to RKI to get feedback in that case. Mit freundlichen Grüßen/Best regards, |
See also ehylau/COVID-19#2 |
Correction of the He et al. (2020) paper now posted: https://www.nature.com/articles/s41591-020-1016-z |
Could the CWA maintainers please provide us with some information on what type of deadlines they have in their SOP when answering such issues involving the RKI? This would help the community adjust their expectations on either how large a workload the maintainers are facing or how the transparancy statement of the App development is to be understood. From https://www.coronawarn.app/en/:
As suggested in the PR #418, there are different ways to address the issue including "doing nothing", but in the spirit of transparency some kind of answer can be expected after 56 days... |
@hoehleatsu if you want you can join our community Slack (we're mainly in the #cwa channel) 🙂. |
Hello @daimpi, to keep you in the loop, I have been told, that the document adjustment has been done. Thanks, Corona-Warn-App Open Source Team |
Finally fixed as part of f03f4cd which is now part of CWA v1.5.0. released today (2020-10-19). 90 days after the issue was opened. |
@hoehleatsu great, thanks for the info I'll close this issue then 🙂. |
Where to find the issue
This issue concerns the “Epidemiological Motivation of the Transmission Risk Level” (TRL) document here: https://github.com/corona-warn-app/cwa-documentation/blob/master/transmission_risk.pdf. In particular Section 3.1 “Infectiousness Profile due to Viral Shedding” which seems to be largly based on He et al. Nat. Med. 2020.
Describe the issue
There has been a major correction to He et al. which yields a significantly different infectivity profile:
Suggested change
Coordinate with the RKI to adjust the TRL documentation and implementation as necessary in light of the correction.
The text was updated successfully, but these errors were encountered: