Develop Requirements for Submission History API

[chris-kuryak]

Problem statement

External users have been asking questions about how to use the Submission History API. So beyond just documenting existing functionality, we need to define requirements on how it should work to inform the Platform team on how to create tests for the API Submission functionality.

What you need to know

• Mural Showing Existing Research
• This is primarily a Product Responsibility, but will be consulting with engineers to accomplish this task

Acceptance criteria

• [ ] Product Requirements that impact the Submission History API are documented with reference to user need.

To do

• [ ] Product Requirements document created

[chris-kuryak]

New Status: "Failed to Deliver" -- got this specific question from CarbonHealth since a message will sit on "Waiting to Deliver" indefinitely

"Partially Delivered" -- Carbon health wants insight into what is still in process of delivery, which got delivered, and if they should continue to wait

[chris-kuryak]

• Add Send Fail/Retry status in the Submissions History API -- request from Flexion ETOR Newborn Screening and ELIMS to have a status/awareness that they can communicate to their sender when we are waiting for more retries