USPS API for Mailing and Physical Address validation(Feb release)

[rohanjay10]

• USPS API would be used to validate mailing and physical address for User Profile
• Once built out, this needs feedback from Ops prior to testing
• Built into User Profile, PWA(user info), and SMDB

Look into partial entry of Physical Address fields:
If any one of Physical Address fields Line 1, City, State, and Zip are entered, then all those fields must be required otherwise error given. However as Physical Address is not required all the fields can be blank

[jhflorey]

https://nih.app.box.com/file/1749535340406

[rohanjay10]

Hi @robertsamm @brotzmanmj, @jhflorey is currently working on the USPS API. Is there a date you have in mind for a demo of the API User Interface Experience? This is part of the February release, per the priority list

[rohanjay10]

2/7 Requirements call notes by @Davinkjohnson

1. How to interpret API results (when/what messages to display when minor changes are found vs invalid addresses)

Suggested Address field changes:

• Accepting/Declining - Use “suggested change” modal
• @depietrodeanna to provide language

English/Spanish translations for current messages
• "Invalid Zip code"
• "Address not found"
• Other (@rohanjay10 to add)
• @depietrodeanna to confirm language for these

How/Where error messages would be shown. Address validated after UP submission
• Have the errors display “in line” as a field is filled in check to see whether all boxes are populated if so then call API
• Find a way to force API error results to log in DataDog (check with Tony/Warren for this)
• Interim modal will check if there are any errors for the addresses (and email address) and display those.
• Ideally have a message saying “reach out to NORC if errors continue” – @depietrodeanna to provide

2. How to interpret and respond to PO boxes
   • @jhflorey will do a little more testing to see if API handles
   • No change in the logic for this (hopefully just better flagging whether this IS a PO Box)

3. Mailing vs Physical addresses
   • User Profile - Keep as-is (no changes to display/logic)
   • MyProfiles – no changes for how data are displayed, required vs optional, edited, etc.
   • SMDB - No changes required

4. Edits for MyProfile - Implement API changes (have the API run when a participant clicks “save/submit”)

5. Edits for SMDB – No changes required

6. How to manage Partial addresses• Partial address logic is working as expected – no changes needed
   • Including non required Physical Address fields

@depietrodeanna Error messages to return:

• "Address not found"
• "Invalid Zip Code"
• "Invalid City"
• "Invalid State"
• "Invalid"
Example wording from mockup for suggested address:
"You originally entered xyz, the suggested address is abc, do you want to use the suggested address or keep the original address?"
• Buttons: "keep original address" "use suggested address"

[depietrodeanna]

@rohanjay10 @jhflorey For the errors found during validation within UP submission, add a modal with language stating, “Please fix the errors in the information you entered before continuing. If you are having problems fixing these errors and can't submit your profile, please reach out to the Connect Support Center (Dev, either hyperlink CSC or add “at MyConnect.cancer.gov/support”) for help.”

For address validation, add this error message:
"We can’t verify your address but found a close match. Please confirm the correct address or enter a different address." (Dev- if they want to go back and re-enter a diff address, is there a way to go back with a button that we should reference in the message, or will it be clear that they can go back and make a new entry? Kind of like the "try again" hyperlinked in the example modal from the presentation)

Display both original and suggested addresses alongside these buttons: "Keep address I entered" or "Use suggested address"

tagging @robertsamm and @brotzmanmj to review messaging- let me know if you have any concerns about the above.

I will ask NORC to translate the above messages as well as these phrases:
"Address not found"
"Invalid Zip Code"
"Invalid City"
"Invalid State"
"Invalid"

@rohanjay10 if there are any others please add to this list.

[depietrodeanna]

@rohanjay10 and @jhflorey, Spanish translations provided below:

English message for UP submission: “Please fix the errors in the information you entered before continuing. If you are having problems fixing these errors and can’t submit your profile, please reach out to the Connect Support Center for help.”

Spanish message for UP submission: Por favor, corrija los errores en la información que ingresó antes de continuar. Si tiene problemas para corregir estos errores y no puede enviar su perfil, póngase en contacto con el Centro de Asistencia de Connect para obtener ayuda.

English message for address validation: "We can’t verify your address but found a close match. Please confirm the correct address or enter a different address."

Spanish message for address validation:"No podemos verificar su dirección, pero hemos encontrado una coincidencia cercana. Por favor, confirme la dirección correcta o ingrese una dirección diferente."

Button responses: English- "Keep address I entered" and "Use suggested address"

Spanish- “Mantener dirección ingresada” and “Usar dirección sugerida”

Other phrases for translation:

English- "Address not found"

Spanish- “Dirección no encontrada”

English- "Invalid Zip Code"

Spanish- “Código postal no válido”

English- "Invalid City"

Spanish- “Ciudad no válida”

English- "Invalid State"

Spanish- “Estado no válido”

English- "Invalid"

Spanish- “No válido”

[rohanjay10]

Thanks for sharing @depietrodeanna .

English message for UP submission: “Please fix the errors in the information you entered before continuing. If you are having problems fixing these errors and can’t submit your profile, please reach out to the Connect Support Center for help.”

Spanish message for UP submission: Por favor, corrija los errores en la información que ingresó antes de continuar. Si tiene problemas para corregir estos errores y no puede enviar su perfil, póngase en contacto con el Centro de Asistencia de Connect para obtener ayuda.

Hi @jhflorey for the above text the "Connect Support Center" in English and "Centro de Asistencia de Connect" in Spanish would be hyperlinked to MyConnect.cancer.gov/support or have the “at MyConnect.cancer.gov/support”.

For address validation, add this error message:
"We can’t verify your address but found a close match. Please confirm the correct address or enter a different address." (Dev- if they want to go back and re-enter a diff address, is there a way to go back with a button that we should reference in the message, or will it be clear that they can go back and make a new entry? Kind of like the "try again" hyperlinked in the example modal from the presentation)

@depietrodeanna this is the example from the powerpoint(which would be updated with the language).

I also wanted to get confirm requirements for the error messages in UP:

1. Should the "try again" portion be kept for address re-entry when original and suggested addresses are displayed?
2. If a suggested address is displayed by USPS, should the user be allowed to submit the original address if they select it, instead of the USPS provided address? As it wouldn't be an error such as "Address not found"
3. Would this CSC error message be shown with every error message in the User Profile

“Please fix the errors in the information you entered before continuing. If you are having problems fixing these errors and can't submit your profile, please reach out to the Connect Support Center (Dev, either hyperlink CSC or add “at MyConnect.cancer.gov/support”) for help.”

[depietrodeanna]

@rohanjay The example from the PowerPoint is fine UX from my perspective. Answers to your questions:

1. yes, which would bring them back to the main UP entry of address
2. I'm unsure, this is really a question for the leads. @brotzmanmj do we want to allow users to submit original addresses if they don't perfectly match the suggested? I would think yes if we are providing the option to select a suggested address, and there may be rare cases in which the original address is slightly distinct from the suggested but still accurate. I defer on this decision.
3. The CSC error message should be shown for all errors, I would think. I don't see a reason not to include it.

[rohanjay10]

@depietrodeanna Thanks for the answers. For the suggested/original address modal, would either modal below @jhflorey has with the "Close" button or "X" instead of the "Try again" from the example work?

[jhflorey]

@depietrodeanna Please also provide Spanish text of Address Verification

[depietrodeanna]

@depietrodeanna Thanks for the answers. For the suggested/original address modal, would either modal below @jhflorey has with the "Close" button or "X" instead of the "Try again" from the example work?

Hi @rohanjay10 either is fine, I think the one with "Close" is preferred but could we change the button text to "Go back" or something to indicate that they are exiting to go back to the UP entry fields? Not extremely important but if we have flex to edit the button it might provide clarity.

[rohanjay10]

Hi @depietrodeanna thanks for the input. I checked @jhflorey and we can use the "Close" modal but with the text saying "Go back" instead. We would also need the Spanish translation for "Go back"(along with "Address Verification") if it doesn't exist already.

[depietrodeanna]

Great, I just passed off to NORC for translation and will update here soon.

[rohanjay10]

Sounds good, thanks. I've added that to the requirements doc here: https://nih.app.box.com/file/1774806243655

[brotzmanmj]

I agree we should allow them to proceed to submit the original address if they choose and not block them from proceeding to submit the UP

[depietrodeanna]

@jhflorey
English: Address Verification
Spanish: Verificación de dirección

English: Go back
Spanish: Regresar