[WIP] API sketch for transporting vaccine status

[mikehelmick]

Proposed Changes

• Design sketch of how the APIs might change to capture and report on vaccine status for use in risk scoring

Release Note

NONE

[google-oss-robot]

Skipping CI for Draft Pull Request. If you want CI signal for your change, please convert it to an actual PR. You can still manually trigger a test run with /test all

[google-oss-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mikehelmick

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files: - ~~[OWNERS](https://github.com/google/exposure-notifications-server/blob/main/OWNERS)~~ [mikehelmick] - ~~[internal/pb/export/OWNERS](https://github.com/google/exposure-notifications-server/blob/main/internal/pb/export/OWNERS)~~ [mikehelmick] Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment

[gurayAlsac]

Interesting. Is the idea that we would downweight an exposure from someone vaccinated? Or get a sense of vaccine dissemination/efficacy in light of potentially more resistant variants?

[mikehelmick]

Interesting. Is the idea that we would downweight an exposure from someone vaccinated? Or get a sense of vaccine dissemination/efficacy in light of potentially more resistant variants?

How this would be reflected in risk scoring is unclear - using this a a detector of mutations is a possible use.

[sethvargo]

A few things:

1. I'd like a flag to be able to quickly turn this off. Introducing a new field has broken some clients in the past, so we should have a runtime way to quickly disable this without doing a full new deployment.
2. Should we distinguish between "not given" and "unknown"?