Storefront Prescription Requests
Some organisations publish a storefront: a public page where a patient with no account fills in a questionnaire, names the medicines they are asking for, names the pharmacy that should receive the prescription, and pays a review fee before anything reaches you. By the time such a request appears in your queue, the patient has already paid. What they paid for is your review — not medicine, and not a prescription. Declining is a normal outcome.The patient’s email address is confirmed before they can submit anything. The storefront emails
them a link and nothing is collected until they open it, so the address the request is filed under
is one they demonstrably read mail at. Nothing else about them is verified: the name, date of birth,
address and answers are all self-reported, exactly as they are on any other request you review.Where the storefront asks for a date of birth, a self-reported one under 18 is refused at
submission, so a request in your queue never states an age below 18. That is a check on what was
typed, not proof of it.
Storefront requests only appear if your organisation runs a storefront. If yours does not, nothing
on this page applies to you and your queue is unchanged.
What patients see in the questionnaire
The questionnaire uses the available screen width responsively, so longer questions and answer choices are not compressed into a narrow column. Formatting authored in question text — including paragraphs, lists, underline, and emphasis — is rendered for the patient. The storefront also uses the questionnaire theme published from the Admin Tool, including its colours and question appearance. For safety, the storefront removes executable or unsupported markup before displaying question text. Scripts, event handlers, and embedded images are never rendered from questionnaire text.Where they appear
There is no separate list. A storefront request arrives as an ordinary prescription in the Anamnesis Center, alongside everything else you review. The one difference is that it arrives unassigned — no doctor is named on it. Any doctor in your organisation can see it and pick it up.Claiming a request
Because an unassigned request is visible to all of your colleagues, you take it before you work on it.- Reading is open. You can open an unassigned request and read it before deciding whether to take it.
- Writing needs a claim. You cannot record prescribing details on a request that is not yours.
- Only one doctor gets it. If a colleague claims the same request a moment before you, you are told that it is already claimed. You are never silently given a case someone else is reviewing, and you are never silently relieved of one.
What the patient asked for
Each requested line records the patient’s own words:- The medicine, as they described it.
- A dosage, in free text and optional — for example “one tablet in the morning”.
- A single dose (ED) and daily dose (TD), both optional.
- A quantity, with a unit (Stück, Packung, Tabletten, ml, and other common pharmacy units).
What the patient wrote is a request, not a prescription, and it does not bind you. It is kept
exactly as they typed it and is not overwritten by anything you record.
What you record
Alongside the patient’s request, you record what is actually to be prescribed:
The review form shows the patient’s entries and prefills your corresponding fields with them. Leave
a field as it is to accept the patient’s entry, or change it. You can change every one of these
fields — prescribing something other than what was asked for, in a different amount, or declining
outright, are all normal outcomes of a review.
Accepting the request accepts every entry as it is shown. There is nothing to confirm line by
line. If you changed a field, accepting saves the change first, so what you see is what is
prescribed.
Save changes stores a line without accepting the request — for example to produce the PDF with
your changes before you decide. You can fill a request in over several sittings, and correcting a
field you filled in by mistake is a normal edit.
The order line behind a storefront request points at a placeholder product, not a real
catalogue article — a patient can ask for something you do not stock. What the prescription says
comes from the fields above, never from the placeholder. If you leave the medicine name blank, the
prescription names the medicine as the patient described it.
The prescription PDF
The PDF you sign is produced from the request when you open or pull it, and again every time a line is saved — when you choose Save changes, or when you accept a request you have changed.- Medicine: the medicine you recorded; until you have recorded one, the medicine as the patient described it. The placeholder product’s name is never printed.
- Quantity: the quantity you recorded, followed by the unit the patient chose.
- Dosage: the dosage you recorded; until you have recorded one, the dosage as the patient gave it.
- Single dose (ED) and daily dose (TD): the signed line reads
product - qty - use — ED: … — TD: …. ED is the single dose you recorded, or the patient’s if you left yours blank. TD is the daily dose, the same way. A dose neither of you entered is left off the line. If both are missing, the line stays medicine, quantity and dosage only. For example:Iuvo 24/1 Petal perfume - 5 g - Inhalieren und verdampfen — ED: 0,1 g — TD: 0,3 g. - While you edit: the Anamnesis Center shows that same line on the request, under the heading Prescription line preview, as you type the single dose and the daily dose, before you save the line and before you sign.
- PZN: not printed for storefront requests, even if your organisation prints PZNs on other prescriptions.
Before you can sign
Your organisation decides which of the fields above a prescription line must carry before the request can be signed. A field counts as present when you filled it in or the patient did: an entry of the patient’s that you leave unchanged is accepted with the request. You have to supply only what the patient did not — typically a single dose or daily dose they left out, or the PZN, which a patient can never give. The check is made when you accept the request, so that you find out while you can still fill the field in — not after you have signed.- On the line: a line that still lacks a required field says so under its preview and names the fields, for example Still required before you can accept: Single dose, Daily dose. A field leaves the list as soon as you type it.
- When you accept: if a required field is still missing, the request is not accepted. You are told that a line is still missing required fields, and the request stays open in front of you.
Until your organisation sets its own list, a deliberately strict default applies: the medicine, the
quantity, the ED and the TD are all required, and the PZN is not. That default is a starting point,
not a clinical recommendation — agree the list with whoever owns clinical policy in your
organisation before you go live.
After you sign
Signing freezes what the prescription says. If someone later renames a product in the catalogue, the signed prescription still reads exactly as it did when you signed it. The signed prescription then goes to the pharmacy the patient named, by email. The patient does not receive it, and the pharmacy contacts them about the medicine, its cost and how it reaches them.After payment the patient is emailed a tracking link to their status page, and that page shows
the outcome of your review: that a prescription has gone to their pharmacy, or that none was
issued. It never shows your reason for declining, your notes, or anything else from the
prescription. If they ask you what it says, that is the whole of it.
The address the prescription is sent to
When the patient named a pharmacy email address at checkout, the review shows it above the dosage lines, in Prescription recipient. The card is not shown when no pharmacy address was given. Choose Change, enter the new address, and save. The prescription is then sent to the address you saved. Under the address, both on the card and in the editor, the page asks you to check it carefully: if it is wrong, the prescription may not reach the pharmacy, and your organisation accepts no responsibility for that. An empty address, or one that is not a valid email, is refused and nothing is changed. After the prescription has been sent, the address stays on screen and can no longer be changed. This is the pharmacy’s address, not the patient’s. Changing it does not change the email the patient is contacted on.Delivery to the pharmacy chosen at checkout
When a patient enters a pharmacy’s email address during checkout, that pharmacy receives the prescription automatically as soon as the doctor signs it. The email’s subject names your organisation. It names the patient — first name and last name, when they are on the patient record or the order — and the patient’s email address, so the pharmacy can get in touch. It contains a link to download the signed prescription PDF. The link is tied to that single prescription — it does not give access to any other document. The pharmacy does not need an RxScale account to receive or open it.Declining
Declining a storefront request works the same way as declining any other prescription: give a clear reason, which becomes part of the record.Related Topics
- Reviewing Prescriptions — Approve, decline, or place a prescription on hold.
- Signing Prescriptions — How electronic signing works.
- What the patient was told they were paying for — The wording shown at checkout, worth knowing when a patient asks.