Intake forms patients complete before they arrive, aftercare instructions that stay current, and clinic wayfinding — with structured clinical content that is never machine-translated or AI-paraphrased.
Waiting-room codes are scanned by people who are unwell, sometimes elderly, often in poor light. They are generated with maximum contrast and no decorative styling at all.
WHAT YOU GET
Clarity matters more than cleverness here
Every design decision on this vertical errs towards legibility and away from styling.
Intake before arrival
A form behind a code on the appointment reminder, so history and consent are captured before the patient sits down. Submissions are queued and retried and never silently lost.
Aftercare that stays current
Discharge instructions behind a code on the printed sheet. Revise the protocol and every sheet already handed out points at the current version.
Wayfinding
Department, floor and room directions from a code at the entrance, which is far easier to update than a printed board when a clinic moves.
Structured clinical content
Dosage, warnings and allergen information are structured fields with fixed meanings, reviewed per language — never free text, never model-generated.
Accessible by construction
Large type, high contrast, screen-reader tested, and every page functional without JavaScript. Colour is never the only signal for anything.
No advertising, ever
A patient scanning a code is never monetised. No ads, no interstitials, no third-party tags on any page they land on — this is architectural, not a policy we could change.
Signage outlives the subscription
Wayfinding and aftercare codes keep resolving after a plan ends. Editing and analytics stop; a code on a ward wall does not become a dead end.
Checked before it is displayed
Quiet zone, module count and contrast are measured on the code, and the print size calculator sizes it for a corridor — read at a distance, sometimes one-handed, often by someone unwell.
SETUP
Live before the next clinic
Built for a practice manager, not an IT department.
STEP 01
Build the intake form
Fields, consent text and required answers. Clinical fields are structured rather than free text.
STEP 02
Add instruction pages
Aftercare and preparation instructions per procedure, in the languages your patients read.
STEP 03
Review accessibility
Check type size and contrast at the size you will print. The defaults already clear AA.
STEP 04
Print reception signage
A4 standees, appointment card codes and department signs, audited before export.
SAFETY RULE
Clinical content is never AI-generated or machine-translated
Dosage, contraindications, allergen and safety information are structured fields with fixed values, translated once and reviewed by a qualified person. AI is not used to write, paraphrase or translate any of it — and where a scan leads to an AI assistant, structured clinical data is always shown first, with AI offered only as a secondary path.
Structured fields
Dosage, contraindications, allergens and warnings. Fixed values, human-reviewed per language.
Free text
General practice information only. Never used for clinical instruction.
AI assistance
Never the sole path. Structured data displays first; an AI option is secondary and always cited.
Patient data
Form submissions are encrypted, access is least-privilege and audit-logged, and no raw IP is stored anywhere.
PRINT PACK
Formats made for this room
Every format is rendered at its own minimum size and decode-tested before export, so a code that fits the layout is a code that scans in the room.
HEALTHCARE
Intake form210 × 297
A4 reception standee210 × 297Front desk and waiting room
Submissions are encrypted in transit and at rest, access is least-privilege and audit-logged, and no raw IP address is stored anywhere in our systems. We will sign a data processing addendum.
Can we translate aftercare instructions?
Structured clinical fields are translated once and reviewed by a qualified person, never machine-translated. General practice information can be translated more freely, and the two are kept separate by design.
Do patients need an app?
No. Everything opens as a web page from the camera, works without JavaScript for core content, and is tested with screen readers.
Will patients see any advertising?
Never, on any tier. The person scanning is not our customer and is never monetised — no ads, no interstitials, no third-party tags.
Can we update a protocol on sheets already handed out?
Yes. The printed code points at a hosted page, so a revised protocol reaches every sheet in circulation the day you publish it.
We’d like to count visits with Google Analytics and see where pages confuse people with Microsoft Clarity. Both set cookies, and nothing loads until you choose. Anything you type stays hidden from recordings.
Change it any time from “Cookie settings” at the foot of every page. Cookie policy