Termeda gives medical practices a single, calm surface to publish their availability — and gives patients a one-breath way to book. No calls. No spam. No data sold. Just hours offered, hours taken.
Open Termeda once. Drag the hours you'll see patients onto a calm canvas — by recurring template or single day. Choose the type, the length, the room, the buffer. The moment you publish, your practice page becomes bookable. No spreadsheets. No clipboard.
"Every Monday morning, six 20-minute consultations" — define it once, Termeda generates the next 26 weeks. Edit any single instance without breaking the template.
Five minutes between patients. Wednesday afternoons for surgery. Two weeks in August. Termeda treats your time the way you do.
In-person consultation, follow-up, teleconsult, home visit, vaccination — each with its own visible duration, price tag, and intake form.
Auto-confirm low-risk bookings. Manually approve complex cases. Send reminders only at the cadence each patient consented to.
Patients open your link, see the next three days that work for them, and book — without an account, without a download, without 11 newsletter checkboxes. Termeda asks only for what the appointment actually requires.
Booking works on a six-year-old phone in poor signal. WCAG 2.2 AA tested. Big tap targets, real focus rings, real keyboard paths.
A booking link, one verification SMS, done. The patient's data is purged 90 days after the appointment unless they explicitly chose to keep a chart.
Email, SMS, both, or none. Frequency on their terms. Termeda never adds the patient to a marketing audience — that channel does not exist.
The reminder itself is the cancel link. No login wall, no friction designed to keep no-shows on the books.
Termeda is engineered for Article 5 of the GDPR, the German Patientendatenschutzgesetz, and the Swiss FADP — not retrofitted to satisfy them. Patient health data has its own class in our schema, its own keys, its own audit log, and its own deletion clock.
Every byte of patient data lives on infrastructure in Frankfurt or Zürich. No replication to the US, no CDN that touches the body. The practice chooses the region; the choice is enforced at the database level.
ISO 27001 · C5 BSISymptom notes, insurance details, and uploaded documents are encrypted on the patient's device with a per-practice key. Termeda staff cannot read them — only the practice can.
AES-256 · Libsodium sealed boxesBy default, patient records auto-expire 90 days after the appointment. A patient or practice can extend, shorten, or trigger immediate erasure — and Termeda shows you when each record will be gone.
GDPR Art. 17 · Auto-purge engineEach consent — to be reminded, to be re-contacted, to share with another practitioner — is its own record with a timestamp, a method, and a revoke link. The patient can withdraw any of them without losing the others.
GDPR Art. 7 · Consent ledgerWho viewed the chart, who edited the slot, who exported the data, when, and from where. The practice principal can export the audit trail at any time, and so can a supervisory authority on lawful request.
Immutable log · 7-year retentionTermeda runs no analytics on patient behaviour. We do not have a marketing channel for patients because we will never own the relationship. Your patients are yours.
No SDKs · No ad pixelsTermeda is delivered as a WordPress plugin that speaks to a hosted, versioned REST API. You keep your existing site, your existing brand, your existing CMS. The booking widget renders into any page with a single shortcode or block.
Your existing theme renders the booking widget via a shortcode, Gutenberg block, or REST embed. No iframe.
Versioned REST + Webhooks. OAuth 2.1 for practice login, mTLS for server-to-server, scoped per-practice tokens.
Encrypted booking engine, audit log, consent ledger. Frankfurt or Zürich, you pick at signup, can't be moved silently.
// 1. Drop into any post or page [termeda_booking practice="Termeda" type="consultation"] // 2. Or use the Gutenberg block "Termeda Booking" // 3. Programmatic access — same surface, REST GET https://api.termeda.app/v1/practices/Termeda/slots?from=2026-05-29&type=consultation POST https://api.termeda.app/v1/bookings { slot_id, patient: { ... }, consent_ids: [ ... ] } POST https://api.termeda.app/v1/slots // doctor creates a new slot template
Termeda is in private preview with twenty practices across DACH. We onboard slowly and on purpose. A demo takes 22 minutes and ends with you knowing whether it fits.