Appointment data, not medical records.

Public booking data

Name, email and/or phone, appointment type, appointment mode, chosen time, consent timestamp and booking status.

The booking form deliberately has no symptom, diagnosis or free-text medical-history field.

Private operational data

The doctor may add a short operational note for scheduling or arrival. This note is not intended for clinical documentation.

Private links and Admin keys must be treated as secrets.

Storage and exports

Live deployments use the configured LightBookMed Netlify Blobs store. The practice can export its own data as JSON. Archiving stops public booking but does not silently destroy records.

Medical-suite handoffs

Each appointment receives a pseudonymous visit reference. When the doctor opens LightConsent, LightDocNote, LightInvoice GOÄ or LightDriveLog, the launch URL contains only that reference, a destination label and a short-lived exchange token in the URL fragment.

Patient details are returned only after the receiving tool redeems the token. LightDocNote receives the patient name and appointment context but not email or phone; contact details are available only to LightConsent and LightInvoice GOÄ. LightDriveLog receives the patient name and appointment context, but no email, phone, operational note or clinical content. No private Desk key is transferred.

Practice responsibility

The deploying practice remains responsible for its privacy notice, retention rules, legal basis, processor agreements, email configuration and secure handling of exported data.

This package does not claim legal or medical compliance merely because it is technically deployable.