search

corona-warn-app / cwa-wishlist

Central repository to collect community feature requests and improvements. The CWA development ends on May 31, 2023. You still can warn other users until April 30, 2023. More information:
https://coronawarn.app/en/faq/#ramp_down
Apache License 2.0
105 stars 14 forks source link

Inform/Remind user about different way to register a (positive) test #270

Closed not-a-feature closed 1 year ago

not-a-feature commented 3 years ago

Motivation and Background

I work in a Lab that performs over 2000 PCR tests on SARS-CoV2 per day. I am in close contact with those that are calling people full time.

It came to our attention that patients try to add the test via QR-Code which doesn't work on about 500/day because the test-centre uses some other kind of "Ü-Schein" (neither the new 10C nor OEGD) which can't be registered by our system. From those 500 patients, about 50-60 are positive and approx. 40 tried to scan the code / tried to add a positive result.

After calling them they are usually surprised that they can add the result anyway by calling the hotline.

Current Implementation

After a failed QR-Code scan the user is notified with a popup. From this position, he/she can try again or aboard.

Suggested Enhancements

1) After the failed scan, the user should be (visually) notified that there is a way to add a positive test result. For example by highlighting the third card "Request TAN" with a greenish colour. Fading the colour in an out 2-3 times.

2) Create a push notification 24, 36, 48 hours after a

Expected Benefits

The users don't forget to add a positive test result.

Demo for 1)

something like that:

GIF of a possible visual implementation

Internal Tracking ID: EXPOSUREAPP-5124

dsarkar commented 3 years ago

Dear @not-a-feature ,

Thank you very much for this interesting proposal. We have created a ticket for the bug (Internal Tracking ID: EXPOSUREAPP-3953) in the internal Jira system. The developers will look into this issue now. Any further developments will be notified here in this Github issue.

Best wishes, DS

Corona-Warn-App Open Source Team

heinezen commented 3 years ago

Similar ideas from other issues:

Corona-Warn-App Open Source Team

achisto commented 3 years ago

These thoughts that were originally posted under issue #287. As @heinezen stated over there, this feedback has already been added to the EXPOSUREAPP-3953 Jira-ticket. However there have been some recent developments which I added at the bottom of this comment.

In my opinion there is another huge problem evolving around the whole teleTAN-process:

Problem

When a user adds a test by scanning its QR-Code right after the testing procedure but that test's result is never transmitted to CWA they will not know that

Suggestion

There should be a notice on the "waiting for result" screen which reminds the user

Optional, that notice could only be shown after e.g. 3 days have passed since the test was added. In that case there should be a push-notification.

Expected Benefits

I personally know two people, who received a positive result by SMS while the CWA didn't show the positive result for several days. Both did not know they could call the TAN-hotline and warn their contacts by requesting a teleTAN.

There is no way of finding out about this alternative because not only does CWA fail to show a hint on the test-screen but, even worse, after having added the test there is no way of going back to the "add your result"-screen in order to find out about other verification methods.

While there is still a significant number of labs not integrated into the CWA-infrastructure I am afraid that there could be a lot of people willing to share their result who simply don't know how to accomplish that. Adding a hint to the "waiting for result"-screen could significantly improve the number of people warning other users.

Recent Developments

I originally published this issue as issue #287 three days ago along with a Twitter-thread. In this thread I basically just explained what can also be found in the corresponding FAQ-entry but was still surprised to see the thread being shared with several people experiencing the exact problem outlined above. These users did add their test by scanning the QR-code but never received a result and therefore thought that there's no way of warning others. This is a huge problem, especially because one could assume that users willing to add their test to CWA are also the ones willing to share their positive result and warn others.

alanrick commented 3 years ago

@not-a-feature Not wanting to detract from your great suggestion... but I'm curious about the remaining 1500 PCR tests that do rely on a 10C/OEGD form.

According to the RKI CWA download statistics we can expect 20%-33% have the CWA checkbox ticked. My suspicion is that the ratio is lower, because doctors surgeries and test-centers complete the form without the patient present and err on the side of caution (GDPR etc). My other suspicion is that it is a design bug that the this checkbox exists at all, and that all results should be fed (anonymously) into the result server and this won't impact privacy standards. I created a question about this 10 days ago but no-one has been able to answer it so far.

I'd be very keen to hear your opinion, especially as to whether 300-500 of the 2000 PCR tests do indeed have the checkbox ticked.

ndegendogo commented 3 years ago

According to the RKI CWA download statistics we can expect 20%-33% have the CWA checkbox ticked.

@alanrick is there such a statistics?

I am aware that the ratio of lab results available via cwa was disappointing low in late summer, for various reasons. Hopefully it is better now. The checkbox was one 'culprit', but there were many other reasons, like:

Several of these 'blockers' have been collected and addressed here

not-a-feature commented 3 years ago

but I'm curious about the remaining 1500 PCR tests that do rely on a 10C/OEGD form.

Good question, in our lab about 20-30% of the tests are registered online. There it depends, from which doctor we receive the "digital 10C/OEGD". Some doctors always mark the checkbox, some never. There aren't that many doctors in between. The overall mean is about 25% checked. (I'll follow up with a more accurate number, but to do so I need to run a manual SQL-query, and due to, you know, data privacy, it has to be authorized)

The Remaining "print" forms are almost never checked. And often the lower part was not handed over to the patient. (We know because we receive both parts :facepalm: ...) These come mainly from mobile test stations that test in nursing homes, asylum shelters and companies.

not-a-feature commented 3 years ago

I personally like the improvement mentioned in #287 to inform users about the teleTan if the test result isn't available after 24, 36 and 48 hours. This will probably have the strongest impact.

alanrick commented 3 years ago

According to the RKI CWA download statistics we can expect 20%-33% have the CWA checkbox ticked.

@alanrick is there such a statistics?

Almost 24 million have downloaded the app. Germany has a population of 83 million. So assuming about 80% of those downloading activate the app, then about 20% have the App. The 33% just a crude adjustment assuming that the youngest (0-10) won't be tested as much as the others so the population getting tested is less than 83million. I assume CWA users are tested as much as non-CWA users so I'd expect 20-33% of the checkboxes to be ticked.

I'm aware of the other factors. The reminder function in 1.71 doesn't seem to have made a difference. According the RKI statistics the positive reporting rate is still only around 54%

All I'm trying to investigate is the checkbox factor, which is why I'm asking @not-a-feature if the numbers tally or if there is a discrepancy indicating that the checkbox problem is a significant factor.

alanrick commented 3 years ago

Many thanks @not-a-feature The 25% mean does tally with my calculations indicating that there's nothing to worry about. On the other hand you say some doctors never check the boxes and it's unlikely that they do this because none of their patients have use the CWA. That does imply that the checkbox is problematic, and if it's not needed (as I suggest) then it is reducing the efficiency unnecessarily and the efficiency of the app could be easily improved without even changing the code.

alanrick commented 3 years ago

Some doctors always mark the checkbox, some never.

Wait! If some doctors always mark the checkbox (and it's unlikely that all the patients have the app), then it sounds like those doctors have figured (and demonstrated) that there's no harm done by pumping all results into the App's server. The sole role of the checkbox is to reduce the efficiency of the app!

ndegendogo commented 3 years ago

If some doctors always mark the checkbox (and it's unlikely that all the patients have the app)

@alanrick the checkbox does not indicate that somebody has the app. The checkbox does indicate that the person tested consents to her results being uploaded to the server. Of course we can now speculate if those doctors always marking take their time and convince all their patients to mark the box. Or if they just mark it by default, and nobody complains.

GisoSchroederSAP commented 3 years ago

@not-a-feature : After heavily investigating possible root causes for failed QR codes scans I's like to ask if you still observe that much persons that struggle with the registration process via QR code or with the "share your test result part of the process? The reason is, that during the last weeks and releases evolved in many ways regarding the information and usability of these steps. There is, however, a major not yet finally solved piece - the digital return of test results from the labs into the CWA infrastructure. Meanwhile, we contacted all major chains of medical facilities to pay special attention in reliability and performance of the technical interface. After investigating hundreds of cases it turns out, apparently they lost focus in this areas. Therefore, we take this very seriously and "monitor" the output of the labs on a regular basis.

If you still experience large numbers of failed QR code scans, I kindly ask you to provide evidence and details (even multiple samples) to the community mailbox: corona-warn-app.opensource@sap.com We will investigate

Many thanks in advance!

not-a-feature commented 3 years ago

Hi, I'll ask around and give you an update as soon as I know more

GisoSchroederSAP commented 3 years ago

Hi, I'll ask around and give you an update as soon as I know more

Thanks for that, much appreciated.

not-a-feature commented 3 years ago

In the last weeks, the number of tests dropped significantly (only about 500-750 p.d.). Therefore the following finding may be distorted and/or not representative.

Overall I would say that everything got a little bit better.

alanrick commented 3 years ago

if there is an "Ausbruchsgeschehen" we get the specimen. As this is happening very rarely...

Very encouraging. The outbreaks in care homes has been the main source of infections in my locality.

The RKI skipped publishing the CWA statistics yet again (demoralizing) so I guess we'll have to wait a little longer for conformation of what you suspect.

GisoSchroederSAP commented 3 years ago

In case, there are non-10C/OEGD-Qr-Code used, would you be able to provide samples of those and the source, i.e., where they come from?

To be honest, we already are in contact with mobile emergency service teams (DRK Katastrophenschutz), those meanwhile are able to add perfectly fitting QR-Codes to their individual forms on-the-fly (we tested with labs already), so there should be no necessity to go, even when the testing was forced by health authority (Gesundheitsamt) with Ü-Schein.

I don't expect we get a fading animation implemented on the short-run for the "fallback" option TeleTAN, as the current preference is to solve the underluying root cause (here: the wrong form or QR code, repectively).

Thanks!

not-a-feature commented 3 years ago

In case, there are non-10C/OEGD-Qr-Code used, would you be able to provide samples of those and the source, i.e., where they come from?

I've emailed you a sample.

To be honest, we already are in contact with mobile emergency service teams (DRK Katastrophenschutz), those meanwhile are able to add perfectly fitting QR-Codes to their individual forms on-the-fly (we tested with labs already), so there should be no necessity to go, even when the testing was forced by health authority (Gesundheitsamt) with Ü-Schein.

They are using correct 10C/OEGD qr codes, but neither is the box checked nor the qr codes handed out to the patient. (Probably due to time reason and due to the very low usage of the CWA in a nursing home)

I don't expect we get a fading animation implemented on the short-run for the "fallback" option TeleTAN, as the current preference is to solve the underluying root cause (here: the wrong form or QR code, respectively).

Why not both :D

Thanks! Glad to help

ndegendogo commented 3 years ago

In late October I got a test at our local test center at Fürstenfeldbruck. No paperwork, everything digital, self-registration via a website. The website registration gave me a QR code, and this code was then used as identifier towards the lab. In the whole process there was no form 10C or whatever. And the QR code was a different system, not cwa. I tried to scan it with cwa, but got only funny error messages. Luckily my test was not positive; and luckily I was aware of the TeleTAN fallback procedure.

I have not been there since that time. No idea if they are meanwhile better integrated with cwa infrastructure.

heinezen commented 3 years ago

@ndegendogo Maybe we should cover these non-CWA QR Codes in the FAQ...

Corona-Warn-App Open Source Team

MikeMcC399 commented 3 years ago

@ndegendogo Do you still have the local test center QR code available? If yes, could you scan it with a regular QR scanner and tell us what the format is?

According to https://update.kbv.de/ita-update/Blankoformulare/10C_OEGD/KBV_ITA_VGEX_Implementierungshinweise_10C_OEGD.pdf the format of the QR code to be scanned into CWA is:

https://localhost/?XXXXXX-XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX. for example: https://localhost/?3D6D08-3567F3F2-4DCF-43A3-8737-4CD1F87D6FDA

ndegendogo commented 3 years ago

@MikeMcC399 the number was much shorter than cwa numbers. Actually, it was not even an URL, but 'DExxxxxxxx' (DE + 8 digits). I think it was the sample number of my swab. I was given a flyer with instructions to contact the health authority and to self-quarantine in case of a positive result, and the code, to be used at the hotline in case the result is delayed.

As a user of cwa I try to scan this number. I remember that I tried several times, but got only error messages like the light is insufficient. cwa should give better error messages, e.g. if it detects that the format does not match its expectations, it should tell the user that the number is from a different system (and maybe this improvement is already implemented?)

MikeMcC399 commented 3 years ago

@ndegendogo Thank you very much for providing the details of a real problem case! Based on that I have submitted a new wishlist item #343.

dsarkar commented 3 years ago

@ndegendogo

Um die Labore lückenlos anzubinden und die Benachrichtigung des Testergebnisses durch die Warn-App sicherzustellen, möchten wir Sie bitten, folgende Informationen an corona-warn-app.opensource@sap.com zu senden: Datum, Arzt, Labor (falls bekannt), Mobilfunkanbieter, Schwierigkeiten beim Scan des QR-Codes etc. und die Information, ob Sie eine Einverständniserklärung zur Übertragung des Ergebnisses an die App gegeben haben. Je mehr Informationen wir erhalten, desto besser können wir diesen Prozess korrigieren und die Qualität der Corona-Warn-App weiter verbessern.

Thanks!

@GisoSchroederSAP FYI

ndegendogo commented 3 years ago

möchten wir Sie bitten, folgende Informationen an corona-warn-app.opensource@sap.com zu senden

@dsarkar done - thanks for reminding!

dsarkar commented 3 years ago

@ndegendogo Thanks!

dsarkar commented 3 years ago

@ndegendogo Update: They are aware of that specific case and working on it.

dsarkar commented 3 years ago

new Internal Tracking ID: EXPOSUREAPP-5124