Actions
Epic #342
openEpic #121: Combined Peptide Stack Protocols
Assign Peptide Stack to Patient from Appointment Details
Start date:
01/08/2026
Due date:
% Done:
0%
Description
Description:
Enhance the Appointment Details screen to allow Providers to assign a peptide stack to the patient associated with the appointment. Once assigned, the patient is notified and guided through purchase and payment, after which the system records the transaction and maintains history.

Requirements:
1. Appointment Details – Peptide Stack Tab
- Add a new tab “Peptide Stack” within the Appointment Details view.
- The tab should be visible to Provider role.
- Display a list of available peptide stacks (active only).
- Provider can view basic stack details before assignment.
2. Assign Peptide Stack to Patient
- Provider can assign a selected peptide stack to the patient linked to the appointment.
- No patient selection is required, as the appointment already contains patient context.
- Once assigned, the stack is marked as pending purchase for the patient.
3. Patient Notifications
- Trigger an in-app notification to the patient informing them that a peptide stack has been recommended.
- Send an email notification to the patient with the same information.
- Notification should include a “Buy Now” action.
4. Patient Purchase Flow
On Buy Now click:
- Redirect the patient to the Peptide Stack Card / Detail page.
- Display full details of the assigned peptide stack.
- On Pay Now click:
- Redirect the patient to Stripe checkout for payment.
5. Payment Success Handling
After successful payment:
- Create required entries in the relevant database tables.
- Mark the peptide stack as active for the patient.
- Record the assignment and purchase in the history / snapshot tables.
- Update patient dashboard and provider view accordingly.
6. General Behavior
- Prevent duplicate assignments of the same stack for the same appointment.
- Ensure payment failure or cancellation does not activate the stack.
- Maintain a clear audit trail of assignment and purchase.
Acceptance Criteria:
- Provider can assign a peptide stack from Appointment Details.
- Patient receives in-app and email notifications.
- Patient can view stack details and complete payment.
- Successful payment activates the stack and updates records.
- Assignment and purchase history is stored correctly.
Files
Updated by Redmine Admin about 1 month ago
- Status changed from Archieve to New
- Assignee set to Abhishek Thakur
Updated by Redmine Admin about 1 month ago
- File clipboard-202601081233-7sskb.png clipboard-202601081233-7sskb.png added
- Description updated (diff)
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 Submitted To Client
Updated by Deeksha Singh about 15 hours ago
- Status changed from Submitted To Client to Ready To UAT
Updated by Deeksha Singh about 15 hours ago
Qa test cases:
- Verify “Peptide Stack” tab is visible in Appointment Details for Provider role only.
- Verify Peptide Stack tab displays only active peptide stacks.
- Verify Provider can view basic peptide stack details before assignment.
- Verify Provider can assign a selected peptide stack to the patient linked to the appointment.
- Verify system does not require patient selection during assignment since appointment already has patient context.
- Verify assigned peptide stack is marked as pending purchase for the patient.
- Verify system prevents duplicate assignment of the same peptide stack for the same appointment.
- Verify patient receives an in-app notification when a peptide stack is assigned.
- Verify patient receives an email notification with peptide stack assignment details.
- Verify notifications include a “Buy Now” action.
- Verify clicking Buy Now redirects patient to the assigned Peptide Stack detail page.
- Verify Peptide Stack detail page displays full stack information.
- Verify clicking Pay Now redirects patient to Stripe checkout.
- Verify successful payment creates required database records.
- Verify peptide stack status updates to Active for the patient after successful payment.
- Verify assignment and purchase details are recorded in history/snapshot tables.
- Verify patient dashboard updates to reflect active peptide stack.
- Verify provider view updates to reflect purchased and active peptide stack.
- Verify payment failure or cancellation does not activate the peptide stack.
- Verify clear audit trail is maintained for peptide stack assignment and purchase events.
Actions