Actions
Epic #366
openEpic #121: Combined Peptide Stack Protocols
Provider Can Start Assigned Peptide After Patient Purchase
Start date:
01/14/2026
Due date:
% Done:
0%
Description
Description
When a provider assigns a peptide to a patient, the provider should only be able to start/initiate that peptide after the patient has successfully purchased it. This ensures treatment begins only when the peptide is paid for and available.
Requirements
- A provider must not be able to start a peptide unless its purchase status is Completed.
- Once the patient completes the purchase, the assigned peptide becomes eligible to start.
- The provider must have a clear action (e.g., “Start Peptide”) available after purchase.
- The peptide start action must update the peptide status (e.g., Assigned → Active).
- Appropriate messaging should be shown if the provider attempts to start a peptide before purchase.
Updated by Abhishek Thakur 14 days ago
- Status changed from New to Ready to QA
- Assignee changed from Abhishek Thakur to Deeksha Singh
Updated by Deeksha Singh about 15 hours ago
- Status changed from Ready to QA to Ready To PROD
Updated by Deeksha Singh about 15 hours ago
- Status changed from Ready To PROD to Ready To UAT
QA test cases
- Verify provider cannot start/initiate a peptide when the purchase status is not Completed.
- Verify appropriate validation message is shown if provider attempts to start a peptide before patient purchase.
- Verify peptide becomes eligible to start immediately after the patient completes the purchase.
- Verify “Start Peptide” action becomes visible/enabled only after purchase completion.
- Verify provider can successfully start the peptide after purchase.
- Verify peptide status updates correctly from Assigned to Active after starting.
- Verify peptide start action is not available for unpaid or pending purchase states.
Actions