Build a pharmacy e-commerce app with prescription upload

You are a developer who builds regulated e-commerce.
I work in Healthcare: a hospital and clinic network. This work matters to patients, clinicians and hospital administrators.

## Goal
Build an online pharmacy where customers order medicines, upload prescriptions and get deliveries.

## What matters in Healthcare
- People involved: doctors; nurses; hospital administrators; billing and coding staff; patients and their families; quality and infection-control teams.
- Rules and standards that usually apply: patient-privacy law (HIPAA in the US, GDPR in the EU, the DPDP Act and ABDM guidelines in India); accreditation standards such as JCI or NABH; informed consent; rules on advertising medical services; clinical content must be checked by a qualified clinician and must not diagnose.
- Numbers that matter: patient wait time; average length of stay; readmission rate; bed occupancy; patient satisfaction; insurance claim denial rate; hospital-acquired infection rate.
- Common risks to plan for: patient-safety incidents; health-record data breaches; medication errors; insurance claim denials; staff burnout; health misinformation.
- Rules differ by country. If I have not said where I work, ask me, and do not present one country's law as if it applied everywhere.

## What I will give you
- Country and pharmacy rules: [COUNTRY]
- Product count: [NUMBER]
- Delivery areas: [AREAS]
- Stack: [STACK]
- Anything else you should know: [EXTRA CONTEXT, or "none"]

## How to work through it
1. Summarise what you understood about the product, its users and the launch scope. Point out anything unclear or contradictory and ask before you guess.
2. Build the catalogue with generic names, strengths, pack sizes and substitutes.
3. Mark prescription-only items and block checkout until a prescription is approved.
4. Build prescription upload and pharmacist review.
5. Build order flow with delivery slots.
6. Add refill reminders.
7. Protect health data with encryption and access logs.
8. Build admin and pharmacist dashboards.
9. Give a launch checklist covering security, performance, SEO, accessibility, backups and monitoring.
10. List what is deliberately out of scope for version 1 and what to build next.

## What to deliver
- Plan and data model
- Phase-by-phase build
- Prescription workflow
- Compliance checklist
- Admin features

## Expert rules
- Build mobile first and make every screen work from 360px wide upwards, with labels, keyboard support and 4.5:1 contrast.
- Validate every input on the server, use prepared statements, hash passwords, protect forms with CSRF tokens and check roles on every admin action.
- Give complete files with full paths; never write "rest of the code stays the same".
- Respect HIPAA, patient privacy and clinical accuracy. If anything in my plan or inputs conflicts with them, say so plainly and suggest a fix.
- Do not invent facts, figures, laws, sources or quotes. Label anything you had to assume with "Assumption:" and tell me how to check it.

## Format
- Start with the plan (stack, structure, data model, screens), then build in numbered phases.
- Use tables for data models and endpoint lists.
- End each phase with how to run and test it.

## Before you answer
Check your draft against this list and fix anything that fails:
- The answer is practical enough to use today without rewriting.
- Every item under "What to deliver" is complete, specific to my inputs and usable as it is, with no placeholders left for me to guess.
- Where it applies, it shows the likely effect on patient wait time and readmission rate.

If something essential is missing, ask me up to 3 short questions first. Otherwise, start.