§ Product · Healthcare

RX Change: move a prescription between pharmacies, audited end-to-end.

RX Change is the patient-side platform for prescription transfer — letting people move a prescription from one pharmacy to another with the consent, compliance, and audit posture that regulated pharmacy work demands. Built for pharmacy chains, mail-order operators, and the D2C pharmacy brands that compete on transfer convenience.

Category
Prescription transfer / pharmacy patient surface
Built for
Pharmacy chains · Independents · Mail-order · Health systems · Telehealth
Compliance
HIPAA · PIPEDA · provincial pharmacy regulators · DEA scheduling
Engagement begins with
A scoping conversation
§ What it is

Patient-initiated. Pharmacy-verified.

RX Change is a prescription-transfer platform. A patient initiates a transfer — from their current pharmacy to a new one — and RX Change handles the verification, the inter-pharmacy communication, the consent record, the regulatory log, and the patient-facing status updates. Whether the buyer is a pharmacy chain offering it as a competitive surface, a mail-order operator routing transfers in, or a D2C brand acquiring patients via switch, the underlying workflow is the same.

  • Patient-initiated, pharmacy-verified. The patient triggers the transfer; both pharmacies verify before the prescription moves.
  • Compliance-first. HIPAA (US), PIPEDA (Canada), provincial pharmacy boards (Ontario College of Pharmacists, Ordre des pharmaciens du Québec), and DEA scheduling rules for controlled substances baked into the workflow.
  • Auditable. Every transfer logged with the patient consent state, both pharmacist signoffs, the drug schedule classification, and the regulator-ready record.
§ Who it's for

Three buyer profiles. One workflow.

Persona 01

Pharmacy chain
operations director

Runs the transfer workflow across hundreds of stores. RX Change is the customer-acquisition surface for inbound transfers and the retention surface against outbound switch.

Persona 02

Mail-order
pharmacy operator

Lives on transfers. Needs a turnkey patient-facing intake that talks to the source pharmacy and produces the regulator-ready record.

Persona 03

D2C health brand /
telehealth product

Routes patients to a fulfillment pharmacy. Needs the prescription-transfer experience to feel native to the brand, not handed off to a third party with a different UI.

§ Capabilities

Six surfaces. One audited workflow.

01 · Intake

Patient intake

Branded, mobile-first transfer initiation with identity verification and consent capture.

02 · Verification

Inter-pharmacy verification

Outbound contact to the source pharmacy via fax / phone / secure API where available; structured response capture.

03 · Controlled

Controlled-substance handling

DEA schedule II–V workflow with the additional verification each schedule requires.

04 · Notify

Status notifications

Patient-facing status updates by SMS / email / push throughout the transfer lifecycle.

05 · Audit

Regulator-ready audit log

Per-transfer record with patient consent, pharmacist signoffs, drug schedule, and inter-pharmacy correspondence — exportable for board-of-pharmacy audit.

06 · Analytics

Operator analytics

Transfer volume, conversion, time-to-complete, and source-pharmacy distribution for the operator's growth team.

§ How it integrates

What we connect to. What we replace. What we don't.

Connects to

Pharmacy systems

  • Kroll · PharmaClik
  • Fillware
  • McKesson PharmacyOne
  • NRx · QS/1
Connects to

Identity & verification

  • Persona · Stripe Identity
  • Provincial / state ID verification
Connects to

Communications

  • Twilio (SMS / voice)
  • SendGrid (email)
Connects to

e-Prescribing networks

  • Surescripts (US) where operator has access
Replaces

The fax-and-call workflow

  • Audit gaps closed.
  • Abandoned transfers recovered.
  • No more "patient runs the bottle over".
Does not replace

Clinical judgment

  • The pharmacist's clinical review.
  • The dispensing system.
  • The prescriber's authorization.
§ Built on

One enterprise stack across the portfolio.

Microsoft Azure
AI Foundry · primary cloud
Anthropic
Claude — structured extraction
Amazon AWS
Bedrock — secondary cloud
Cohere
Embeddings · fuzzy matching
§ Where it ships

Pharmacy buyers across North America.

01Pharmacy chains
02Independent pharmacies
03Mail-order pharmacies
04Health systems
05Telehealth providers
§ Engagement

From scoping call to quarterly compliance review.

01 · Scoping
01
Scoping call

Walk through the current transfer workflow and regulator posture with a senior Droz partner.

02 · Privacy
02
Privacy & compliance review

Joint review of HIPAA / PIPEDA / provincial pharmacy regulator / DEA posture before any patient data moves.

03 · Pilot
03
Pilot

One pharmacy location or D2C funnel · 90 days · defined success criteria.

04 · Production
04
Production rollout

Pilot expands to the rest of the network or funnel with a named Droz technical owner.

05 · Review
05
Quarterly compliance review

Audit trail, regulator updates, controlled-substance rule changes that affect the workflow.

§ Talk to the team
Every transfer. Verified, audited, done.