New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IMPORTANT (CovPassCheck): Add a 'Booster'-Info to the "Certificate valid"-Screen... #139
Comments
|
Vote +1 that this is important. It may also be integrated/combined together with #107 . |
|
This is, in the very end, a duplicate of Digitaler-Impfnachweis/covpass-ios#73. But since this issue only underlines how important this change would be, I'm fine with leaving it open. |
|
Thanks for requesting this feature. We're currently refining enhancements to address this situation. Instead of showing more details on the verification result screen in the CheckApp we're going to add verification settings. This setting can be enabled and results in handling 2G+ situations equally with test or booster. Feature is planned to be delivered in release 1.17 . |
|
@oliver-steinbrecher Any ETA? We're at 1.13 now, so this could take till beginning of February, I assume? |
|
Yes |
|
is it possible to change the prioritization? Or are planned changes up to v.1.17 more important? Or is the workload so high? (I know that all discussions about the relief for boosted people are a bit open in view of Omicron - according to today's reports, a decision should be made before Christmas. |
|
We’re aware of the topic’s importance. Currently I can’t confirm anything else. |
|
It can currently be assumed that today (01/07/2022), at least for the gastronomy in Germany, “2G plus” (2G +) will be decided and will therefore come into force in the next few days. So we need - especially for the controls - on the one hand a practicable handling to check the "complete vaccination incl. test" and on the other hand the "complete vaccination incl. booster vaccination". This seems to me to be a must and ideally should be available at the same time as the regulation comes into force. In relation to the title here: Add a 'Booster'-Info to the "Certificate valid"-Screen... to CovPassCheck as soon as possible! |
And already decided! See e.g.: Bund und Länder einigen sich auf 2G plus für Gastronomie – deutschlandweit
|
|
will apply to NRW by 13. January 2022, see: |
|
The EU has explicitly ensured that the QR code can also be presented in paper form without a cell phone. As of today, I am therefore lost in NRW, as the CovPassCheck app cannot distinguish a Booser from an ordinary vaccination at entrance. So I have to get tested despite booster or use again the 40 years old WHO vaccination certificate. |
|
Is there anyone with write access to make a review on that pull request? #156 |
|
FWIW: There are news articles out there where the German Federal Ministry of Health (Bundesministerium für Gesundheit, BMG) states that CovPassCheck App will not be changed to address this issue, mainly for data privacy reasons. No idea if this ministry is capable to decide over an open source project, tho. |
|
As the app is published by the RKI (see https://digitaler-impfnachweis-app.de/impressum), which is, according to https://www.rki.de/DE/Content/Institut/institut_node.html, "[...] ein Bundesinstitut im Geschäftsbereich des Bundesministeriums für Gesundheit." So, in the end, I think: Yes, they can decide. |
This article does not reflect the reality. As already said improvements are planed for release 1.17 . Further improvements related to booster detection are planned for release 1.18. |
|
Thank you very much for the swift clarification. |
I guess this is simple missinterpretation. If I understood correctly @oliver-steinbrecher they are implementing an enhanced solution to check 3g/2g/2g+ and whatever solution. The required enhancement stated in the article proposes to show the number/date of vaccination. This ministry is stating that this would not be able to implement. Checking for specific rules does not explicitly reveal more information, but is only checking for a logic in the background, so this is a different case and must be validated by data privacy department. (I assume this has already been done but not yet published). Though I understand the CWA and the CovPass projects should be open source projects. In regards to that it is very helpful and supporting that people can raise questions and issues via GitHub. Anyhow I cannot understand why the developers do not share more information and actually discuss the requirement in more details. Making applications open source can only enhance the user experience efficiently if all stakeholders incl. the users are part of the full application life cycle. This includes the business analysis and requirement refinement process. |
|
Just some more thoughts:
In my opinion (as discussed in Digitaler-Impfnachweis/covpass-ios#96) it would be best to provide the CovPassCheckApp operator with a menu something like this: As it is the most transparent, flexible and (in my opinion) intuitive interface for this. |
|
@Kamik423, |
|
Just wait till the wave is through. So you don't have to implement that feature.
Am I supposed to print "3 of 3" on the card, so "Otto-Normal"-people accept the state of vaccination, which is in the QRCode? |
|
@oliver-steinbrecher as long there is no other PR for this I would like to propose the following.
Reason: while the chance is minimal a manipulation or offset e. g. wrong summer/winter time from the mobile provider could lead to wrong expiration calculations of vaccination status. Now that the rules get more complicated and involve expiration based on number of days, allowance to boost after x days, etc correct time is essential. See also (#97)
a country, a german federal state or other country from a dropdown list in app settings. The new version should point out that before a check a valid country and or state has to be set up. This would reflect the flexibility needed when checking the credibility of the recovery and or vaccination status in different regions, due to quite unfortunate regional regulations, that are by no means covered at the moment.
Message: ~~4.
the entrance regulations in Covpass check app settings (2G, 2G plus, 3G etc.) ~~
Message:
Usecase: this allows a self control next to the check app to avoid missing a new effective regulation that affects the state. If I missed anything please feel free to add. Hope this list can be double checked against the 1.18 release plans and it helps to make this important release most successful. Currently there is a high risk for wrong entrance allowances. Thanks for your time and feedback! |
Do you have an overview over the different rules in the different federal states? EDIT: Seems like something is planned for 1.18: Digitaler-Impfnachweis/covpass-ios#73 (comment) |
|
Hello @Ein-Tim personally I don't have a list of all regulations per country / federal state. This could be either collected in a PR for future updates by the community or become the responsibility of the owners. I have some where found a list in which EU countries outside of Germany the apps are supported, but unfortunately I didn't bookmark this reference. It was missing some bigger countries like Spain but included smaller countries like Andorra. |
It's okay that you don't have such a list, the problem is that even BMG/RKI seem to not have such a list.
Yes, this is where the apps can be downloaded, however, Spain and all other EU countries have their own wallet & check apps. So CovPasCheck doesn't have to include their rules. |
|
Sounds like a typical case of german regulations. |
|
I don't think that CovPassCheck should know and evaluate all regulations from all regions and locations. I assume it's impossible to keep up with that. But as of now its still not possible to gain all information from the output that is needed for a decision in 2G+ scenarios to decide if an additional test is needed or not. This is the most important thing: Show all needed info. Like "Booster #1 XX days ago" or maybe just "Immunisation 3/3 XX days ago" or similar, which at the moment means the same as "fully boostered". It can be made prettier afterwards. Of course the date of last immunisation is a sensitive information, but as government has decided that this value is part of the rules, it's obviously okay to share. |
|
Thank you for your opinion @sleeksorrow. Looking forward for the implementation in 1.18. Especially for the CovPass Check app. Without doubt it is confusing and from a programmatical point of view the solution should be sustainable. I do not expect a near end of the situation and more boosters and / or more dependencies, this should be considered in the code. That's why I drafted a wide range solution from the logical point of view. As the app is owned by the RKI they should have all regulations that are valid for Germany, or they need to establish a political or business process to assure they receive the information, as @Ein-Tim mentioned they do not publish it at the moment. Currently, even though offtopic for the PR, the discussion about the recovered state and the duration shows that the political decisions favor a central publication for Germany of the regulations, but this is a heated debate, and is currently only tied to the recovery, not other aspects, afaik. |
|
@sleeksorrow I disagree. The point of the app is to make checking regulations easier. This entails not juggling a bunch of numbers in your head to match against. Its entire purpose is it to show a big green check mark if a certificate is valid for entry and a big red x if it is not. |
|
Hans dixit:
***@***.*** I disagree. The point of the app is to make checking
***@***.*** easier. This entails not juggling a bunch of numbers in
***@***.*** head to match against. Its entire purpose is it to show a big
***@***.*** check mark if a certificate is valid for entry and a big red x
***@***.*** it is not.
But this makes checking regulations harder or impossible
because regulations change, or there may be site-local,
venue-local, usecase-local etc. requirements (by law or
by site/venue policy).
|
|
I'd appreciate if the app can make checking easier and I approve any steps towards this even if I assume as well that this is technically impossible. But before we can make checking easier, we first need to make checking possible which it is not as of now without displaying the age of latest immunization. |
|
all regulations are logical, so I suspect they can be coded. Depending on the structure it should be flexible enough to adjust the result to a number of combinations. I hope that the developers will also comment the ideas here. It's too important to get things wrong. Clock is ticking. |
I need to know all regulations first before I can decide on that statement. Please list them all in complete, for all german states, with all their requirements and all their exceptions. I'm desperately searching for such a list since May 2020.
I don't think that they can be coded (edited because I mistranslated your sentence before). That's why I disagree and they should be second objective at best.
Indeed, that's why we need to show all raw information from the vaccination code so that as soon as possible the checking person even has a chance to decide, instead of investing weeks on the perfect shiny solution that comes too late then. |
This is really the problem here, it seems like neither the RKI, nor the BMG have a public list over all the different regulations in the federal states. The development teams of the apps have to search the information by themselves and make sure they always update the information. |
|
As stated in a post by me above, I think the best way would be to include a UI like this: There should be preset buttons (2G, 3G, 2G+) but it should have local concepts for what constitutes those (I.e. if 2G+ is fulfilled by a booster) and what counts as a booster (I.e. 2/1 or only 3/3). I think this is the necessary thing to do, as this can cover all options that will be needed while remaining intuitive, accessible and flexible. |
|
@Kamik423 I fully agree to keep it simple and let the checking person evaluate. I just want to mention that your proposal does not cover all options, because in 2G+ situations in some (all? dunno) federal states a full vaccination without booster can be enough without the additional test, if the date of immunization is less than 90 days. That's why the app needs to show the days since last immunization. |
|
No question - of course there is a basic logic that can or could also be programmed. But the many, partly local, exceptions, their half-lives, etc. can quickly undermine a basic logic or make it significantly more difficult or even impossible to program it. A good example is the shortening of the convalescent status to 3 months, introduced overnight - which is now being overturned by the courts. Under such framework conditions - and that was just a very simple example - I don't want to be a programmer / person in charge! Nevertheless, time is ticking. Also because increasing loosening is at least being discussed, which wants to reduce or even end access restrictions. |
|
based on the information of Android the app is published by the RKI so ultimately, they should have the responsibility about the reliability of checks @Ein-Tim. We are note discussing an entire open source application which is maintained by people in their free time, do we? |
|
@Karl-WE absolutely true, it not only a free-time project. Even if we do not know what is going on behind the scenes, I am also wondering why the app is not reliable at the moment. I know I am repeating this wherever I post something, but for me the currently "classic" example is the one-dose Johnson & Johnson vacc which is still represented valid as "fully vaccinated" - which is not true anymore. I don't have a recovery certificate at hand which would be over 90 days but still under 180 to check this, but I assume it would also still be valid even the 90 days rule came in. Can someone explain what the business rules are ment for as they are show in the app to be updated every now and then. I thought, these rules may include exactly these cases which could be updated ad hoc without a real app update via stores. I really would like to understand this logic. |
|
This is by no means a free-time project CovPass wird fünfmal so teuer wie geplant
|
|
I think the 3g,2g+ check feature is broken and should better be removed entirely at this point. For example, there is no SINGLE certificate that can combine vaccinated-recovered-vaccinated status. This certificate simply can not be created in the pharmacies due to fact that the certificates are given by the EU. A certificate for the second vaccine will simply omit the information about the recovery. As the app currently only has one active certificate and checks are performed only on a single cert, it will show "Certificate does not fulfill all conditions" when 14 days haven't passed since the second shot. I think it would be better if the CovPassCheck App simply shows if the certificate is valid in general and not in regard to wrongly interpreted rules (that keep changing faster than the release cycle of this app anyway). It creates a lot of confusion and distrust among personal that is using the app to check validity. Imagine, they are dealing with all those edge cases several times a day. Many don't seem to take "Invalid Certificate" serious anymore. This is my personal observation. I have been chasing the reasons and responsibilities behind this edge case now since a week as I am one of the affected. The RKI doesn't make the rules, it just releases guidelines. The states implement rules inspired by the RKI guidelines. The wording in those rules (Verordnungen) is ambiguous and fuzzy. If you call the authorities (Gesundheitsamt, Senatskanzlei, Corona Hotline) in Berlin 5 times you get 5 different interpretations on their own rules. I think the developers can not expect to be given an "up to date" list of the regulations in the different states because it seems there is no authority that is responsible for such information. Due to the complex nature of the problem, it is understandable that the App can not keep up. Please redesign the features in a way that it makes the users (personal that checks 3g/2g+) feel responsible to make their own judgement of the situation. At the moment, the app is misleading and wrongfully denying entry to perfectly immunized people. PS: the swiss "Covid Check" app seems to be able to validate my certificate as 2g+. Not sure what they are doing different but it shows that my certificate is valid in general. |
|
The way it's currently going is just vain endeavor. Always too late, still too confusing. I was trying to keep up with it but even I am now lost as what constitutes what. A solution could be to have the rule set separately on the server, so not everyone has to wait for a new app release. PS: Anyways, there are still fake mickey mouse certificates going around from over 3 months ago. So what's all the fuzz. This project is lost effort. |
|
@dadaphl wrote:
In fact, today was the first time I experienced that a valid 'booster certificate' (my wife's) shown with CovPass (v 1.17.0) was supposedly invalid. Unfortunately, there was no way of clarifying the circumstances, but the readable text "3/3" in the paper DCC led to admission. Since I assume that testing was done with CovPassCheck, I suspect either an operator error or an old version of the app. Back home I checked the supposedly invalid certificate with a second Android smartphone (CovPassCheck v1.17.0) - and it is displayed as valid under "Check 3G" (and under "Check 2G+" as "2G proof valid"). Conclusion: I still don't think that the checks mentioned above are broken or that they are superfluous. |
Are you refering to the checkes mentioned in your own text or mine? It seems like that the operator made a mistake or the app was not up to date in your case. In my case however the apps are up to date and I can assure you there is no operator error going on. The checks are broken in the CovPassCheck app. |
|
@dadaphl:
In this respect I think it would be helpful if you open your own bug report and name all the circumstances you are aware of. So which smartphone was used, which operating system, which app version, ... was scanned from paper or from an display on another smartphone, how often the problem occurred / occurs etc. Why / what is the background to this? I remember several problems around certificate scanning. Be it that the smartphone libraries used had difficulties, be it that cell phone cameras didn't always want to focus or something similar. Therefore, from my point of view, my conclusion remains. |
|
Did you check with version 1.18? When scanning a booster certificate in the 2G+-Modus, the app will show "Auffrischimpfung gültig", see: Do you want to close this issue as implemented? |
|
yes, the result of a 2G+ check is now displayed as shown. With that I will close this point. |

Avoid duplicates
Current Implementation
If vaccination certificates are scanned with CovPassCheck (v1.13.3), the current situation is as follows:
A scan of a vaccination certificate (e.g. BionTech 2 of 3) delivers "Certificate valid".
A scan of a vaccination certificate (e.g. BionTech 3 of 3) from the same person also provides "certificate valid".
That is correct so far.
Suggested Enhancement
Against the background of the new regulation, which has already been partially introduced, that 'boosted' people no longer need an additional corona test, this 'boosted' information must be displayed as additional information in CovPassCheck (and CWA).
According to current information, the above-mentioned regulation - i.e. no additional tests for 'boosted' / people with a booster vaccination - should be decided in the coming week for all of Germany.
Expected Benefits
This is the only way to determine at a glance whether an additional corona test is actually necessary or not during an access control, for example.
E.g.:
"Booster #1" is an idea to count boosters when more than one booster (i.e. a second, third, ...) booster is needed.
Additional context
When making the solution, it must certainly be taken into account that further booster vaccinations will be necessary for the future and of course all vaccine combinations must be taken into account when determining the 'booster'.
The text was updated successfully, but these errors were encountered: