Simulated proof asset · India Healthcare GrowthOS

Simulated India pharmacy prescription refill + WhatsApp DPDP diagnostic

This no-fake-client proof asset shows how AICS can inspect prescription refill, chronic-care, stock-availability, home-delivery and WhatsApp follow-up leakage before a pharmacy owner buys an AI receptionist, CRM, WhatsApp bot or delivery workflow. It is synthetic only: no real pharmacy, patient, PHI, prescription data, customer data, DPDP compliance, medicine-delivery outcome, revenue or ROI claim is made.

Important claim boundary: this page is a simulated proof-of-method demonstration. It is not a customer case study, not a testimonial, not a pharmacy-data analysis, and makes no real pharmacy, no patient, no PHI, no prescription data, no customer data, no medicine-delivery outcome, no medical advice, no legal advice, no privacy advice, no security advice, no DPDP attestation, no certification, no platform partnership, no advertising, no ranking, no revenue, no ROI and no AI-accuracy promise.
Synthetic requests1,73612 synthetic workflow/channel rows
After-hours requests295sample events needing callback ownership
Missed calls62synthetic calls not initially answered
Callback coverage proxy33.9%after-hours + missed-call base with callback in 2 hours
Refill requests1,024synthetic refill queue only
Refills not confirmed487synthetic ready/confirmation gap
Rx verification required799synthetic pharmacist-review queue
Rx verification logged36.5%292 of 799 sample rows logged
Diagnostic method

What a pharmacy owner can inspect before scaling WhatsApp, AI reception, delivery workflows or CRM follow-up

The diagnostic converts request rows into operating queues: source tagging, owner assignment, callback SLA, refill confirmation, prescription-verification logging, stockout/substitution follow-up, DPDP notice prompt, WhatsApp opt-in evidence, AI boundary disclosure, pharmacist-review route, controlled-medicine boundary and closure reasons.

Evidence/control areaSynthetic request volume with gapWhy AICS would flag it
Source captured589Owners cannot reliably compare calls, WhatsApp, referrals, delivery phone orders, app spillover, walk-ins, caregiver calls and website forms.
Pharmacy owner assigned1,032Unowned refill requests weaken callbacks, pharmacist review and delivery handoff accountability.
Prescription verification logged507Only 292 of 799 synthetic verification-required requests have verification logged; this is an operational evidence gap, not a medical or pharmacy-safety claim.
Stockout/substitution follow-up logged239Only 93 of 332 synthetic substitution or stockout follow-ups are logged, leaving customer callbacks and alternatives hard to manage.
DPDP notice prompt present1,536The workflow lacks operational evidence that data-use notice language was presented; this is not compliance advice.
WhatsApp opt-in evidence1,434Follow-up templates should distinguish permissioned messages from ad hoc staff messaging.
AI/admin boundary disclosed1,652Customers should know when they are receiving assisted/admin replies and when a human pharmacist must review.
Pharmacist review route503Automation should not bypass qualified human review for prescription, substitution or sensitive-medicine decisions.
Controlled-medicine boundary1,142Controlled/sensitive medicine requests need explicit human routing before automated responses are considered.
Closure reason captured1,620Without closure reasons, the owner cannot distinguish ready, unavailable, duplicate, pharmacist-review, no-response and cancelled requests.

Before diagnostic

  • WhatsApp refill messages, phone calls and delivery-app spillover are counted as separate queues.
  • Prescription verification is often implicit, so the owner cannot see which refill requests need pharmacist review.
  • Stockout/substitution follow-up sits in memory or chat threads rather than an owner dashboard.
  • DPDP notice prompts, WhatsApp opt-in evidence and AI boundary disclosure are not consistently evidenced.

After diagnostic operating rule

  • Every request source has an owner, status, source tag and closure reason.
  • Refill, prescription-verification and stockout/substitution queues are separated for owner review.
  • Pharmacist-review and controlled-medicine boundaries are explicit before any automation recommendation.
  • DPDP notice prompts, WhatsApp opt-in evidence and AI boundary disclosure become checklist items, not assumed compliance.

Evidence needed before publishing any real pharmacy outcome

A real pilot should collect only permissioned, minimized operational exports where possible; define callback SLA, owner, pharmacist-review and controlled-medicine boundary rules; document prescription-verification logging, stockout/substitution follow-up, notice/purpose prompts, WhatsApp opt-in handling, AI/admin boundary wording and closure reasons; and obtain explicit pharmacy approval plus qualified legal/privacy/advertising/pharmacist review before any public patient, DPDP, delivery, safety, revenue or ROI statement.

Reproducibility

Internal synthetic artifact: /home/agent/.hermes/aicloudstrategist/case-studies/simulated-india-pharmacy-prescription-refill-whatsapp-dpdp-2026-08-21/. Expected headline output: rows=12, total_requests=1736, after_hours_requests=295, missed_calls=62, callbacks_within_2h=121, callback_coverage_pct=33.9, refill_requests=1024, refills_ready_or_confirmed=537, synthetic_refills_not_confirmed=487, synthetic_refill_confirmation_rate_pct=52.4, prescription_verification_required=799, prescription_verification_logged=292, prescription_verification_logging_pct=36.5, substitution_or_stockout_followups=332, stockout_followups_logged=93, stockout_followup_logging_pct=28.0, unresolved_refill_or_stockout_risk_pct=41.8, source_gap_requests=589, pharmacy_owner_gap_requests=1032, dpdp_notice_gap_requests=1536, whatsapp_optin_gap_requests=1434, ai_boundary_gap_requests=1652, pharmacist_review_route_gap_requests=503, controlled_medicine_boundary_gap_requests=1142, closure_reason_gap_requests=1620, attention_rows=11. Input SHA256 aa2405956e29acc761c421022154cf5385ad3172d2384d6cb61302a142e72130; generator SHA256 c542e9230f3e4e08edf45f5b235f7436e828c482761b26fef3eb4cdb4569a06c; report SHA256 98d94ef1bbdbbbc73a9afbe6b85f31cd28c480a33dd858266ab1dac6ccbc00ce.

More proof assets · Healthcare GrowthOS · India clinic WhatsApp checklist · Resources