Epic #355
open
Epic #7: Admin Portal
Weight Management Stack (Escalation, Transition, Maintenance)
Added by Abhishek Thakur 30 days ago.
Updated about 17 hours ago.
Description
Description :
Implement functionality to support the Weight Management Stack as a multi-phase treatment stack, including Phase A (Intensive Escalation), Phase B (Stability Transition), and Phase C (Maintenance), with configurable dosing, check-ins, labs, and payment milestones per phase.
Requirements
- Admin can create and manage the Weight Management Stack with distinct phases.
- Admin can configure the following phases:
- Phase A: Intensive Escalation (Months 1–3)
- Phase B: Stability Transition (Weeks 10–12)
- Phase C: Maintenance (Ongoing, 6-month cycles)
Phase A – Intensive Escalation
- Admin can configure weekly dose escalation:
** 2.5 mg (Weeks 1–4)
** 5 mg (Weeks 5–6)
** 7.5 mg (Weeks 7–8)
** 10 mg (Weeks 9–12)
- Admin can configure required check-ins:
** 4-week check-in (dose escalation)
** 8-week check-in (dose escalation)
- Admin can configure initial payment covering:
** First 3 months of medication
** 4-week and 8-week check-ins
- No labs are required during Phase A.
Phase B – Stability Transition
- Admin can configure:
** 10-week notification for required labs and follow-up payment
** Labs + Follow-Up bundle ($199, configurable discount)
** 12-week clinical check-in
- Required labs:
(CMP, HbA1c, Fasting Insulin, Lipid Panel, Apo B, hsCRP, Ferritin, Lipase/Amylase)
Phase C – Maintenance
- Admin can configure:
** 6-month treatment cycles
** Recurring payments for medication and labs/FU bundles
** Ongoing lab monitoring every 6 months
** Ongoing clinical check-ins every 6 months
** Eligibility rules for continuation (patient stability)
Acceptance Criteria
- Admin can create, update, publish, and deactivate a multi-phase Weight Management Stack.
- Stack clearly displays Phase A, Phase B, and Phase C.
- Dose escalation is enforced during Phase A.
- Labs are required only in Phase B and Phase C.
- Payment milestones align correctly with each phase.
- Providers can view all phase details for treatment planning.
- Stack can be reused across multiple patients.
- Status changed from New to Ready to QA
- Assignee changed from Abhishek Thakur to Deeksha Singh
WMS PeptideStack – QA Flow Verification
Flow Overview
This card covers the end-to-end functional flow for Weight Management Stack (WMS), including provider assignment, patient purchase, phase start, phase progression, lab handling, reminders, and multi-phase purchases.
- Provider Assigns WMS Stack
-
- Login as Provider
-
- Open an active appointment with a patient
-
- Navigate to the Peptide tab
-
- Select a WMS Stack
-
- Assign the stack to the patient
- Patient Accesses Purchase Page
-
- Log in as Patient
-
- Open the Buy Now link from the notification or access the purchase URL
-
- View stack details
-
- Verify phase-based pricing is shown (only first phase price)
- Patient Purchases First Phase
-
- Click Buy Now
-
- Complete Stripe checkout
-
- Return to the application after payment
- Phase and Lab Initialisation
-
- System creates phase progress record for the purchased phase
-
- If the phase contains lab requirements:
-
- Lab assessment is created as the parent assessment
-
- Check-in assessments are blocked until lab is completed
-
- Lab notifications are sent first
-
- Patient must purchase a separate lab test pack
-
- Service pack lab tests cannot be used for WMS labs
- Lab Completion and Reminder Flow
-
- Lab notification is sent to the patient
-
- Patient completes lab, and lab results are received
-
- After lab results are recorded:
-
- System sends the next reminder email
-
- Check-in reminders are unlocked and scheduled
- Provider Starts Phase
-
- Provider opens the patient appointment
-
- Navigates to the Peptide tab
-
- Starts the phase
- Phase Execution
-
- Phase start date is set
-
- Check-ins follow the defined schedule
-
- Reminders are sent based on phase configuration
-
- Phase continues until all required assessments are completed
- Phase Completion and Next Phase Availability
-
- Phase is considered complete only when:
-
- All required check-ins are completed
-
- All required labs have results
-
- System determines the next available phase
-
- Next phase purchase notification is sent (if applicable)
- Multi-Phase Purchase Flow
-
- Patient can purchase the next phase before the current phase completes
-
- Multiple phases can exist in purchased state
-
- Only unstarted purchased phases can be started
-
- Phases must be started in order
-
- Reminder and Notification Flow
-
- Phase payment reminders are sent near phase end
-
- Lab reminders are sent before lab dates
-
- Check-in reminders are sent only after lab completion (if labs exist)
-
- Notifications are delivered via in-app, real-time, and email
- Status changed from Ready to QA to Reopen
- Assignee changed from Deeksha Singh to Abhishek Thakur
- Status changed from Reopen to Ready to QA
- Assignee changed from Abhishek Thakur to Deeksha Singh
QA test Cases
- Verify Provider can assign a WMS stack to a patient during an active appointment.
- Verify Patient can view WMS stack details and purchase only the first phase price.
- Verify successful payment creates phase progress and initializes lab/check-in rules correctly.
- Verify lab requirements block check-ins until lab completion and send lab notifications first.
- Verify Provider can start a phase only after prerequisites are met (labs/check-ins as applicable).
- Verify phase completes only after all required check-ins and labs are completed.
- Verify next phase becomes available and purchase notification is sent after phase completion.
- Verify multiple phases can be purchased but must be started sequentially.
- Verify reminders and notifications are triggered correctly (lab, check-in, payment, phase start).
- Status changed from Ready to QA to Reopen
- Assignee changed from Deeksha Singh to Abhishek Thakur
- Status changed from Reopen to Ready to QA
- Assignee changed from Abhishek Thakur to Deeksha Singh
- Status changed from Ready to QA to Submitted To Client
- Status changed from Submitted To Client to Ready To UAT
Also available in: Atom
PDF