Dental Patient Registration
A ready-to-use, end-to-end encrypted new-patient registration form for dental practices — collect contact details, medical history, insurance and consent.
A new patient arrives carrying a history the practice cannot see: the medication that interacts with adrenaline, the heart condition that changes the anaesthetic, the allergy nobody thought to mention. This template moves that history out of the waiting-room clipboard and into an encrypted form the patient completes before the appointment — so the clinician reads it before the chair reclines, not after.
What the practice knows before the patient sits down
- Patient contact details — name, date of birth, phone and email
- New or returning patient status
- Insurance provider
- Relevant medical conditions and the reason for the visit
- A signed consent to treatment and data processing
The fields, and why each one earns its place
| Field | What it changes at the chair |
|---|---|
| Name, date of birth, contact | Identifies the record and lets reception reach the patient before the appointment |
| New or returning patient | Decides the slot length — a first consultation needs longer than a recall |
| Insurance provider | Sets the billing route and flags whether a cost estimate is needed up front |
| Medical conditions | Diabetes, cardiac conditions and blood pressure all change anaesthetic and bleeding risk |
| Allergies and current medications | The field most likely to stop a prescription or an injection going wrong |
| Reason for the visit | Lets the clinician prepare instruments and plan the session |
| Consent to treatment and data processing | The record you rely on if the processing is ever questioned |
Encrypted by default
Patient health data is special-category personal data under the GDPR and sensitive personal data under the Swiss nFADP. With end-to-end encryption, submissions are unreadable to anyone but your practice — including us.
The transcription problem paper registration creates
Most practices still take new-patient details on a clipboard or a PDF attachment sent by email. Both create the same two costs. Staff re-type handwriting into the practice system, and every re-typed character is a chance to turn one medication into another. Completed sheets then accumulate in a drawer that has no retention policy and no access log, while emailed health data crosses the internet in a form the practice does not control.
Collecting the same answers as structured data before the appointment removes the transcription step entirely, shortens check-in, and gives the clinician a complete medication and allergy history at the moment it is clinically useful — which is before treatment planning, not during it.
Health data, professional secrecy and the nFADP
Dental records are health data — special-category personal data under Article 9 GDPR, sensitive personal data under the nFADP — and dentists are additionally bound by professional secrecy under Article 321 of the Swiss Criminal Code. That combination sets three practical duties: collect on a lawful basis with a stated purpose, apply security appropriate to the sensitivity, and keep the data no longer than the purpose requires. End-to-end encryption addresses the middle duty directly. Each submission is encrypted in the patient's browser and only your practice holds the Vault key, so the record stays unreadable in transit, at rest, and to the platform itself.
Putting the form in front of patients
Use this template
Copy it into your dashboard — the medical-history and consent questions come pre-built.
Trim it to your practice
Every field you remove is one less record to justify keeping. Add your branding in the builder.
Send it with the appointment confirmation
Attach the link to the booking confirmation rather than a separate email — completion rates follow the message patients already open.
Questions dental practices ask
Is an online dental registration form GDPR compliant?
It can be, and this template is built for it. Compliance comes from collecting only what you need, capturing explicit consent, and protecting the data with measures appropriate to its sensitivity. Because submissions are end-to-end encrypted and only your practice can decrypt them, the technical-measures expectation of both the GDPR and the nFADP is met by architecture rather than by policy.
What stops us from over-collecting?
Nothing automatic — that judgement stays with the practice. The useful test is to ask, for each field, what you would do differently if the answer changed. A field that changes nothing is a field you are storing without a reason, and under both the GDPR and the nFADP that is the harder position to defend.
Can patients complete the form before their appointment?
That is the intended use. The form is a link, so it works on a phone in the days before the visit. Practices that keep a tablet at reception for patients who did not fill it in beforehand get the same encrypted record either way.
See our use case for dental and orthodontic practices, the treatment consent template that pairs with this registration, and our guide to collecting health data in forms.