Sprint 2 prescription delete and discontinue

[Manshant7]

Description

This PR implements the Prescription Management workflow for the Guardian Android application as part of Sprint 2 frontend development.

The feature allows doctors to:

• Fetch prescriptions for patients assigned to them
• View prescription details in a cleaner and structured format
• Discontinue prescriptions using a prescription ID
• Delete prescriptions using a prescription ID
• Receive confirmation dialogs before performing critical actions
• Handle backend responses and API errors properly

The implementation includes:

• Retrofit API integration for prescription endpoints
• JWT authorization handling through SessionManager
• Dynamic prescription display formatting
• Confirmation dialogs for discontinue/delete actions
• Improved UI flow and validation
• Prescription ID input handling
• Error handling and success feedback messages

The workflow was tested successfully using backend Swagger APIs and test prescription data provided during Sprint 2 development.

---

Todos

• Tested and working locally
• Code follows project structure and frontend workflow
• Self-reviewed implementation
• Added confirmation dialogs for safety
• Integrated API calls with backend
• Requested PR review from team members

---

How to Test

1. Login using a valid doctor/admin account
2. Open the Prescription Management screen
3. Click “Fetch Prescriptions”
4. Verify assigned patient prescriptions are displayed properly
5. Copy one Prescription ID from the fetched list
6. Paste the ID into the Prescription ID field
7. Test “Discontinue Prescription”
8. Verify confirmation popup appears
9. Verify prescription status updates correctly
10. Test “Delete Prescription”
11. Verify delete confirmation popup appears
12. Verify prescription is removed successfully

---

Work Done Evidence Included

---

Associated Sprint Tasks

• Sprint 2 Prescription Workflow
• Prescription Delete Functionality
• Prescription Discontinue Functionality
• Doctor Prescription Management UI

---

Known Issues

• Backend responses may vary depending on assigned patient data.
• Some API endpoints still require additional backend-side validation improvements.