When reviewing the message detail on a single message, we have a very helpful section that lists out the warnings and errors detected for the message.
However, we don't have associated metadata about those detections on that page. I think it would be helpful to display a few things along with the issues:
How and Why to fix
The codebase metadata used to validate that issue (if it's a code)
Which shot in the message this validation is for.
The user story goes something like this:
A warning is issued for a message. In the message detail, we show that the warning is something like this: "vaccination administration date is after use age recommended for vaccine".
A user wants to understand why that issue is presented for this patient/shot. They will need to look up:
the patient age
which shot in the message this pertains to
what the CVX/NDC is for the shot
codebase information to see the use age limits to see what was the source data for this issue.
For each of these steps, we can support the user with additional metadata on the message detail page. We should be thoughtful about how to present the data in a way that's discoverable, but doesn't distract from the bigger story we're telling on the page. We want the users to be able to ignore it if that's not their goal.
When reviewing the message detail on a single message, we have a very helpful section that lists out the warnings and errors detected for the message.
However, we don't have associated metadata about those detections on that page. I think it would be helpful to display a few things along with the issues:
The user story goes something like this:
A warning is issued for a message. In the message detail, we show that the warning is something like this: "vaccination administration date is after use age recommended for vaccine".
A user wants to understand why that issue is presented for this patient/shot. They will need to look up:
the patient age
which shot in the message this pertains to
what the CVX/NDC is for the shot
codebase information to see the use age limits to see what was the source data for this issue.
For each of these steps, we can support the user with additional metadata on the message detail page. We should be thoughtful about how to present the data in a way that's discoverable, but doesn't distract from the bigger story we're telling on the page. We want the users to be able to ignore it if that's not their goal.