Open ColmByrne opened 4 years ago
yonglid
commented
4 years ago There are a lot of disparate sites being backed by reputable orgs/hospitals etc: https://covidnearyou.org/#!/ https://covid.joinzoe.com/us (started in uk) https://apps.apple.com/us/app/healthlynked-covid-19-tracker/id1500575377 I wonder if it's possible to reach out and help add to their database / get data from them
ColmByrne
commented
4 years ago Yes. We are reaching out to them. Good note
On Wed, Apr 8, 2020, 8:10 PM Yong Li Dich notifications@github.com wrote:
There are a lot of disparate sites being backed by reputable orgs/hospitals etc: https://covidnearyou.org/#!/ https://covid.joinzoe.com/us
I wonder if it's possible to reach out and help add to their database / get data from them
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/zerobase-io/smart-tracing/issues/257#issuecomment-611138852, or unsubscribe https://github.com/notifications/unsubscribe-auth/AO3H2IOOOTVU6UGN5TPXISDRLTD2LANCNFSM4MEBUDQQ .
twoangstroms
commented
4 years ago There are web-based self-checkers:
Apple (so far the best one I've seen): https://www.apple.com/covid19/ CDC (need to tap a button): https://www.cdc.gov/coronavirus/2019-ncov/symptoms-testing/testing.html
twoangstroms
commented
4 years ago From design perspective, the issue is going to be how to earn the user's trust -- asking them to flag themselves as possibly infected can be or be perceived to be a huge privacy and trust hurdle (here's a good example of running something by legal). How might we assure the user that this will not be shared or publicized with anyone before asking them to start the process of self-reporting?
Also, how might we receive results if they've used an outside site, like Apple's or the CDC's?
twoangstroms
commented
4 years ago This is also something we might have to think about: https://twitter.com/ashk4n/status/1248669443590217728
Text: "While the privacy of @Apple/@Google contact tracing system look robust (user-controlled rolling ephemeral subkeys) -- the architecture still side-steps the HARD issue of how-to verify if a user is actually diagnosed (vs is just 'crying wolf’)"
JohnCLo
commented
4 years ago Updated Copy and Designs can be found on the IVD doc: https://docs.google.com/document/d/1JS6jr1VoasJITgNEI3YdGoCcMKlWSfv7G8VnTa39KfQ/edit?usp=sharing
Roadmap goal: Self-Declare (SD)
WHAT? A self-declaration (SD) feature that can help PHOs assess individual and community exposure for analysis or notifications. A self-declaration of positive test results isn't the same quality of data as a certified lab test. Therefore we won't action this data for automatic contact tracing but used as 'warm data' for PHOs to decide how to action on.
Ideation, Validation, Design: https://docs.google.com/document/d/1JS6jr1VoasJITgNEI3YdGoCcMKlWSfv7G8VnTa39KfQ/edit?usp=sharing
WHY? The advice from Health agencies currently in many countries and specifically in the USA is to self-isolate and not get tested. This is even if the individuals have key symptoms without underlying risks or anything that would put them in a group of people who can develop severe symptoms and require medical help at health facilities. If we don't have SD symptoms we are not including people that the CDC is assuming (for now) that they have C19. Moreover, we don’t have the integration of testing facilities so the best way to get the data about possible exposure of C19 is from end-users.
HOW? We will create a flow for SD, which would be based on Apple's flow (based on CDC spec) and a few other examples.
Full spec is here with info reviewed, approaches discussed is here: Deck: https://docs.google.com/presentation/d/1m56xQf3zlHFYSQaBP3qE6Yq3Hn6owRP12C_iqVETOh0/edit?usp=sharing Doc: https://docs.google.com/document/d/1Y4p_oPL8Gh6H9WDBrmhDIwasJtF-LEJ-/edit?ts=5e961683#
Ticket Info Ticket breakdown: