Pharmacy delivery, built for Epic Willow.

Your pharmacists are verifying fills in Willow. Your drivers are running deliveries with paper manifests and group texts. Somewhere between those two workflows, deliveries get missed, signatures get lost, and someone calls the pharmacy at 4pm asking where their mother’s metoprolol is.

Zippykind closes that gap. We connect to your Epic environment, pull verified fills as they happen, dispatch your drivers with optimized routes, capture proof of delivery on a mobile app, and write the result back to the patient chart. The pharmacy staff never opens a second system.

Request the Implementation Guide

What pharmacy delivery looks like without us

You already know. A tech reads off the day’s verified fills. Someone copies addresses into a spreadsheet, or worse, prints them. A driver gets handed a clipboard. The pharmacy manager texts the driver around 2pm asking whether the Rite Aid order went out. The patient signs a paper slip that gets stuffed in a manila envelope until someone files it.

Most pharmacy delivery operations run this way. It works until it doesn’t, and when it doesn’t, the failure mode is usually a missed delivery for a patient who needed their medication today.

What changes when you connect

Once your Epic environment is licensed to Zippykind and the integration is live, the workflow changes in a few specific ways:

A pharmacist verifies a fill in Willow as they normally would.
Within an hour, that fill appears as a delivery ticket in Zippykind, populated with patient name, address, phone, and prescription details from the Epic record.
Zippykind’s dispatch board assigns the ticket to a driver based on your rules. The driver sees the route on their phone, optimized across every pending delivery they’re responsible for.
The driver scans the prescription bag at pickup. At the doorstep, they capture a photo, GPS pin, and signature. If the patient isn’t home, the driver can send a contactless signature link to the patient’s phone instead.
The delivery event posts back to Epic via FHIR. The status appears on the patient’s chart in Willow. No one re-types anything.

Your pharmacy staff opens Willow. Your drivers open the Zippykind app. The integration is the only thing that knows about both.

Routing that actually saves time

Most “route optimization” in delivery software is window dressing. A list of stops in alphabetical order with a Google Maps link. Zippykind runs a traveling-salesman solver against road network data from OSRM, so a driver carrying 40 prescriptions across three zip codes gets a sequence that minimizes drive time, not just distance.

The solver handles up to 200 waypoints per driver and recalculates the route when a delivery gets added or cancelled mid-shift. Multi-store chains can run drivers out of one location and dispatch deliveries from another. Pickup-then-dropoff pairs stay coupled in the route, so a driver collecting a return script and dropping off a new fill at the same address gets routed once, not twice.

For pharmacies running same-day or two-hour delivery windows, this isn’t optional. It’s the difference between hitting your SLA and missing it.

The driver experience

Native iOS and Android apps. Drivers see their day as an ordered list, switch to a map when they need it, scan items at pickup to confirm chain of custody, and capture proof of delivery without typing anything. GPS coordinates are stamped on every event. Signatures and photos upload in the background even if cell coverage drops mid-route.

If a patient prefers not to sign on a stranger’s phone, the driver sends a one-time link by SMS. The patient signs from their own device. The signature comes back into Zippykind and writes through to Epic the same way an in-person signature would.

Security and compliance

Pharmacy IT teams will ask about this first. Here’s the short version:

HIPAA. Zippykind operates as a Business Associate. A signed BAA is required before any production credentials are exchanged.
Infrastructure. Zippykind runs on AWS HIPAA-eligible services (RDS, ECS, S3, Secrets Manager, ElastiCache) under our AWS BAA.
Encryption. AES-256 at rest, TLS 1.2 or higher in transit, KMS-managed keys for storage and backups. Per-pharmacy private keys for FHIR authentication are wrapped with a dedicated key encryption key stored in AWS Secrets Manager. A database dump alone would not yield a usable credential.
Authentication to Epic. OAuth 2.0 client credentials with signed JWT assertions (RS256), following the SMART Backend Services specification. Each pharmacy holds its own Client ID, issued by Epic, isolated from every other pharmacy on the platform.
Audit logging. Every read and write against your Epic environment is logged with timestamp, endpoint, HTTP code, and resource ID. Logs are immutable and retained seven years.
Minimum-necessary PHI. Zippykind retains recipient identifiers and delivery records. Clinical context (drug name, dose, sig) is read in real time when needed for the delivery ticket and is not persisted in our database beyond the active delivery cycle.
Documentation. SOC 2 attestation, penetration test summary, HIPAA Security Risk Assessment, network architecture diagram. Available under NDA on request.

What we read from Epic, and what we write back

Zippykind requests the minimum FHIR scopes needed for delivery dispatch and nothing else. No clinical notes. No labs. No billing data. No diagnoses.

FHIR Resource	Operation	Why
MedicationDispense	Search, Read	Identify verified fills ready for delivery
MedicationRequest	Read	Prescription details for the delivery label
Patient	Read	Recipient name, address, phone
Task	Read, Update, Create	Read existing delivery task if Willow created one; write or create delivery status events

If Willow created a Task for the delivery, Zippykind updates that Task. If not, Zippykind creates one when the first status event happens, so the patient chart shows the delivery either way.

Onboarding

The first pharmacy through this integration took six weeks. We’ve shortened it considerably since then.

BAA. Three to five business days for most legal teams. We provide the template.
App license on Epic. Your Epic representative installs the Zippykind Pharmacy Delivery App into your environment, either through Showroom or via direct install by your Epic Technical Services contact. Your environment generates a Client ID specific to your pharmacy.
Sandbox testing. About a week, depending on your Epic analyst’s availability. We run end-to-end test fills through your non-production environment. Both teams sign off on the test plan before any production credential is exchanged.
Production cutover. A few hours. Promote credentials to your production environment, train pharmacy staff on the Zippykind dispatch interface, and you’re live.

Most pharmacies are running production deliveries within two to three weeks of countersigning the BAA.

Pricing

Zippykind charges per delivery ticket. Pharmacy Suite is a small add-on that bundles the features specific to pharmacy operations: Epic integration, multi-location dispatch, contactless signature, scanner-verified pickup. We’re rolling out a flat-rate subscription option for higher-volume pharmacies later this year. Talk to us about your delivery volume and we’ll quote both options.

Roadmap

Epic has confirmed they’re actively developing dedicated Shipping Management APIs for the pharmacy delivery use case. When those APIs become available, Zippykind will migrate from hourly polling to push notifications. The migration requires nothing on your end. Same Client ID. Same FHIR endpoint. Deliveries appear in Zippykind in seconds instead of within an hour, and your Epic environment serves fewer API calls.

We track the Epic Technology Guidance program and are in contact with the team building those APIs. When they ship, our customers will be among the first migrated.

What to do next

If your pharmacy is on Epic Willow and you’re running delivery operations on spreadsheets, paper, or an in-house tool that doesn’t write back to Epic, this integration will pay for itself in staff hours within the first quarter.

Request our Implementation Guide. It’s a detailed technical document covering the Epic-side setup steps, the FHIR scope list your Epic analyst will need, the sandbox testing protocol, and the security and compliance posture in full. We send it to engaged prospects under NDA.