Add flexible verification code expression in Portal

[Dar-Scott]

Currently the verification code provided to a Case Investigator by the Portal must be in a form recognizable by the Verification Server.

However, customers (regions) might be better served if the expression of the verification code is more flexible. That is, the Portal translates the verification code to some human form and then translates it back.

This might also include a check digit processed solely by the Portal. The Verification Server is not bothered if the code is invalid.

This is illustrated by this markup of Google's diagram of the verification process.

Here the dotted dark red line is the extended proxy proposed. The metal gray oval is where additional timely metadata might also ride.

The verification code 12345678 might be expressed by any of these:
"12345678"
"12 34 56 78"
"123.456.789" (check digit 9 added)
"The alert cardinal swam slowly."

The expression function just has to have an inverse.

[Dar-Scott]

Extra metadata can be returned by the Portal in the blue oval.

This might be some daily stats such as % infectious and % symptomatic for the region. Maybe even % adoption.

If there is a secure way to save and recover extra metadata entered into the Portal at the time of code generation, then that can also be returned in the oval, proxied (5). If allowed, this can be added to U-metadata or added to the data associated with the TEK.

[Dar-Scott]

What does that Mean? blocked-by-product-design
@ibeckermayer