Log test result interpretations in Azure Event

[jsutantio]

User Story

As an Engagement Engineer and Support Team member, I need to know more about the messages that have failed or got filtered out – so that I can help senders diagnose why their messages are not being delivered.

Description/Use Case

The UP Message Monitoring Dashboard in Azure will eventually be a tool used by the Support Team to monitor messages that fail to be properly processed in the UP. Although a bit old, this SOP document provides good context on the goal of the message monitoring effort.

For the [Items routed but filtered out] dashboard module, we need an Azure event that enable us to do the following:

• Need to include the test result interpretation (positive or negative or etc.)
  Consider: Adding this to the existing event: ITEM_FILTER_FAILED.

Risks/Impacts/Considerations

• Will we hit the character limit?

Dev Notes

• test result interpretation is typically used to understand why something got filtered out due to the condition filter
• The FHIR field is: Resource (observation).interpretation.coding.code

Acceptance Criteria

• Azure event created/ edited that enables us to know the test result interpretation