Create designs for pipeline errors

[sarahtress]

Need to think about how we inform the user if something goes wrong in our processing of the eCR - will look similar to the type of error messaging we put together for the demo UI

List of errors we might expect to happen/should have designs for:

• Authentication error --> what would be the suggested action to resolve? log into NBS again?
• Generic error: something went wrong, catch all for any errors we don't specifically call out --> what would be the suggested action to resolve? log into NBS again?
• Couldn't find requested record --> what would be the suggested action to resolve? contact DIBBs team? contact IT?
• Oops page: bad url, page doesn't exist (this would replace "home page")
• Fields we found in eCR but didn't have a place for in table: create a new field in eCR Viewer to display this data, near unavailable info
• Failed to convert to FHIR --> would we still display the field in the right place or would it go into the category above? (for ex: if DOB failed to convert but we still had data for it, what would happen?)
• Failed to standardize: put a label/message on fields that we should have cleaned but couldn't for some reason --> is there a chance we would fail to standardize a whole ecr? bc then I'd need to make a global error message for this too. also, which fields do we standardize?
• Failed to geocode: put a label/message on fields that we should have geocoded but couldn't for some reason. also create a global message if geocoding service is down and whole eCR can't be geocoded
• any other errors I'm missing?

[sarahtress]

blocked for now by techincal spike into errors

[ashton-skylight]

Error Language: https://docs.google.com/spreadsheets/d/148ft3WEQ_jKW5Tq9zNuv4A2-DeqFXBobhaeuDdsFLjg/edit?usp=sharing

Last 3 errors (FHIR, standardization, geocode) might be covered by the Team4 work