Pharmacist-owned operations, not a gig network.
Rahhawan was built by pharmacists who needed a courier they could put on a Schedule II tote. Reliability standards, licensed coverage, and selective HIPAA architecture come first.
Origin
A dispatch desk that thinks like a pharmacy
Independent counters in Morris and Passaic were stitching together rideshare, in-house techs, and a spreadsheet. Controlled totes and insulin bags cannot live in that mix. Rahhawan is the operational layer: custody, cold-chain, proof, and an alias buffer so a routing vendor never learns who lives at the stop.
Leadership sits in Morristown. Couriers are on the books, CS-authorized by name, and visible to the pharmacist who released the tote.
Licensed footprint
Morris and Passaic only. The rule engine refuses a sealed tote that would leave the licensed area.
Reliability standard
Photo proof, canvas signatures, and timestamped custody events. Failed attempts sit on the stop alias.
Compliance focus
Marketing is a non-PHI zone. Portals are the PHI zone: tenant scoping, CS authorization, anonymized processors.
Selective HIPAA
Two zones, on purpose
Pricing, about, and contact never store patient details. The pharmacy dashboard, driver web view, signatures, and photos belong on BAA-covered infrastructure. Routing vendors receive three fields: physical address, stop alias (DEL-84029), and notes such as “Cold-chain bag”.
Non-PHI
Public website, inquiry inbox, architecture docs
PHI zone
Orders, signatures, photos, temperature logs
Standards we will not relax
100%
CS stops require an authorized courier
2
Temperature captures on every refrigerated tote
3
Fields in the routing CSV — never a fourth
0
Patient names in Stripe metadata
If the tote is controlled, the person on the doorstep is on our authorization list. That is the whole product.
On-staff couriers
Not a crowdsourced pool
Morristown desk
America/New_York operations
Sealed chain
Witnessed release at the counter
