search

bcgov / dts-vc-issuer-service

Digital Trust Verifiable Credential Issuer Service
Apache License 2.0
0 stars 11 forks source link

Cardinality of Vaccination record(s) in a VC #14

Closed bradhead closed 8 months ago

bradhead commented 3 years ago

Should there only be one vaccination event per VC? Or do we model the concept of a vaccination 'card' where it holds relevant vaccinations attested by the issuer?

swcurran commented 3 years ago

I suspect at minimum, there would be a vaccination status credential that would show the current state of the person's vaccinations by targeted infection. A new credential would be offered each time an event occurred, and the previous credential revoked.

There could also be a credential per event. However, that gets into some "interesting" UX on the wallet side that has not yet been handled. E.g. "Verifier has requested all your vaccination event credentials, do you want to share them?"

swcurran commented 3 years ago

Looking at the VC format proposed by others (e.g. #21 ), it definitely looks like it is a credential per vaccination event.

I suggest that the UI only allow the user to receive the latest of the string of vaccinations (e.g. where the disease or the "medicinalProductName" is the same. Not clear how to identify the stream, but that should be the goal.