What a build includes

Refill and transfer requests

A patient asks for a refill or moves a prescription across without phoning, and the request arrives where your team already works.

The form collects what your team needs to act: who the patient is, how to reach them, and which prescription or pharmacy is involved. It is submitted over an encrypted connection and routed into your pharmacy system or a Canadian hosted intake tool, so it lands in the queue your staff already watch rather than in a shared inbox somebody has to remember to open.

Nothing about a patient's medication travels by plain email through anything we deliver. Which system the form routes into is verified with you at proposal time, because vendor features and hosting locations change.

What you get

• A refill form and a transfer form, written in plain language
• Routing into your pharmacy system or a Canadian hosted intake tool
• Encrypted submission, with no medication detail sent by plain email
• A confirmation screen that tells the patient what happens next, and when
• Fields kept to what your team needs to act on the request

What it does not do

• It is not a dispensing system and it does not hold a patient record.
• A pharmacist still reviews every request. The form moves the request, it does not decide anything.
• Routing is confirmed against your own system at proposal time, not assumed.

Where it sits. Listed under Signature as online intake forms with consent. Scoped with you at proposal. See the three build tiers.

Related: Pharmacy websites, What the compliance review covers.