Skip to content
This repository has been archived by the owner on May 16, 2023. It is now read-only.

Transmission risk level paper correction #384

Closed
daimpi opened this issue Jul 16, 2020 · 8 comments
Closed

Transmission risk level paper correction #384

daimpi opened this issue Jul 16, 2020 · 8 comments
Assignees
Labels
bug Something isn't working documentation Improvements or additions to documentation

Comments

@daimpi
Copy link

daimpi commented Jul 16, 2020

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.

@daimpi daimpi added bug Something isn't working documentation Improvements or additions to documentation labels Jul 16, 2020
@SebastianWolf-SAP
Copy link
Member

Thanks for the information. We will reach out to RKI to get feedback in that case.

Mit freundlichen Grüßen/Best regards,
SW
Corona Warn-App Open Source Team

@mhoehle
Copy link

mhoehle commented Aug 13, 2020

See also ehylau/COVID-19#2

@mhoehle
Copy link

mhoehle commented Aug 16, 2020

Correction of the He et al. (2020) paper now posted: https://www.nature.com/articles/s41591-020-1016-z

@mhoehle
Copy link

mhoehle commented Sep 10, 2020

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/:

The app is based on technologies with a decentralized approach and notifies users if they have been exposed to SARS-CoV-2. Transparency is key to both protect the app's end-users and to encourage adoption.

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...

@daimpi
Copy link
Author

daimpi commented Sep 10, 2020

@hoehleatsu if you want you can join our community Slack (we're mainly in the #cwa channel) 🙂.

@ghost
Copy link

ghost commented Sep 30, 2020

Hello @daimpi,

to keep you in the loop, I have been told, that the document adjustment has been done.
Currently, we are reviewing the document and will inform you as soon as possible, when the updated document is available.

Thanks,
LMM

Corona-Warn-App Open Source Team

@mhoehle
Copy link

mhoehle commented Oct 19, 2020

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.

@daimpi
Copy link
Author

daimpi commented Oct 19, 2020

@hoehleatsu great, thanks for the info I'll close this issue then 🙂.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

4 participants