Negativer Corona-Test, Status weiterhin rot

[Oaky78]

1. App Status rot, wegen mehrerer Risikobegegnungen.
2. Test mit QR Code eingescannt
3. Negatives Testergebnis erhalten

IST: App Status weiterhin rot, auch nach Aktualisierung am nächsten Tag (Siege Screenshot)

SOLL: App sollte bei negativem Ergebnis wieder grün werden.

Technical details

• CWA version 1.5.2
• iOS Version: 13.7
• Device: iPhone 8

[dsarkar]

Dear @Oaky78,

Thank you for your report.
Can you confirm that you are using CWA version 1.5.2?
Please, have a look here #239.
I think you are basically suggesting the same, i.e. after a negative test result, you wish that the red card should change to green.
Also, how many days are between the risk encounter and the corona-test?

Best regards,
DS

Corona-Warn-App Open Source Team

[Oaky78]

1. dangerous contacts -> 21.10.
2. app turns red -> 24.10.
3. added test -> 26.10.
4. get negative result -> 28.10.

[svengabr]

I did ask the developers and this is not a bug.

The card displays the risk calculation based on the last 14 days. The fact that a user enters a test and gets a negative result does not change your personal risk score or the color of the app card.

Corona-Warn-App Open Source Team

[nschloe]

@svengabr I don't get it either. If you have a contaminated contact and get tested negative after said contact, the card should not be red. Unless you've had another contamination since your last test of course.

A negative test at any time should set the card to green for the moment of the test. Don't you agree?

[dsarkar]

Dear @Oaky78, dear @nschloe,

The current situation is:

• A person has high-risk encounters according to CWA and gets a red card in CWA.
• Based on that information, he does a test (should be done after x days of incubation time)
• He gets a negative test result
• Still, the CWA shows red for altogether 15 days.

Analysis:
Maybe is a user experience problem (not a bug), not to distinguish carefully between:
(a) Risk calculation by the CWA based on past risk encounters and
(b) Actually NOT being infected, although a risk has existed, proved by a negative test result.

Mitigation possibilities:

1. Improve web FAQ/documentation and explanation in CWA stating clearly the difference between (a) and (b)

2. Or would you like to suggest is a different user experience. Let's say you are tempted to worry unnecessarily by a red card, i.e. In the case mentioned above, your suggestion is basically: after a negative test result, the card should go green, meaning: the past high-risk encounters are irrelevant from now on?

Corona-Warn-App Open Source Team

[nschloe]

Or would you like to suggest is a different user experience. Let's say you are tempted to worry unnecessarily by a red card, i.e. In the case mentioned above, your suggestion is basically: after a negative test result, the card should go green, meaning: the past high-risk encounters are irrelevant from now on?

That'd make lot more sense imho. A red card indicates a warning, danger, the need of attention, so it's a good thing that it's shown after a high-risk contact. After a negative test, there is no danger anymore, so the card can turn green again.

The current situation has another significant disadvantage. If the card stays red for 14 days no matter what, the user will not know if she had another high-risk encounter after a negative test. If, on the other hand, the card turns green after the test and red again a few days later, it's clear that attention is required once again.

[daimpi]

@dsarkar I think you're spot on: the current behavior is not strictly speaking a "bug" but rather an annoying "feature" of CWA from a UX perspective. Regarding mitigations I think your second proposal is what #239 is aiming for and why it's placed in the wishlist repo:

2. Or would you like to suggest is a different user experience. Let's say you are tempted to worry unnecessarily by a red card, i.e. In the case mentioned above, your suggestion is basically: after a negative test result, the card should go green, meaning: the past high-risk encounters are irrelevant from now on?

[heinezen]

Hello everyone,

I agre that this issue is not really a bug, but rather a missing feature. Therefore, we have created a Jira ticket (EXPOSUREAPP-3496) for the associated feature request in #239. The thread here and the thread in #239 have been integrated into the Jira ticket, so the discussion is not lost.

I will close this issue as a duplicate of #239, so please continue the discussion there. This was done to better monitor the discussion from our side.

Regards,
CH

---

Corona-Warn-App Open Source Team

[heinezen]

Duplicate of #239