Espejo Clinic

The four questions a clinic asks every morning

• Appointments today — total, split into completed / waiting / cancelled.
• Today's revenue — with the percentage delta against yesterday.
• Outstanding balance — billed and not yet collected, plus unpaid invoice count.
• Active treatment plans — accepted plans in progress, and how many are still drafts.

Below that: the full schedule for today, a seven-day revenue bar chart, total patient count with new patients this month, and a ranked list of the most-performed treatments.

Let patients book themselves — against real availability

A public, unauthenticated booking page — no patient login, no app to install — in three steps: choose the appointment, enter your details, confirm.

What makes it trustworthy is the availability engine behind it. A slot is offered only when it survives every constraint at once:

• Inside the clinic's configured opening hours and working days.
• Inside that professional's weekly schedule for that specific branch and weekday.
• Outside the configured lunch/break window.
• The professional is not already booked.
• A treatment room is free at that branch.

The endpoint returns free time slots and nothing else — never another patient's name, contact details or appointment.

Structured history, not a free-text box

Patients are built on a shared Person record — name, date of birth, gender, document type and number, phone, email, address and photo — the single source of truth reused by users, professionals and patients alike. The patient record adds blood type, preferred language, emergency contact, branch and clinical notes.

• Allergies with a severity grade (mild / moderate / severe).
• Medical conditions from a maintained catalogue, grouped into categories, each flagged for dental relevance and for whether it should raise an alert before treatment.
• Per-patient conditions with diagnosis date, status and notes.

Partial payments are first-class

Invoices per patient and branch, each with an invoice number, issue date, total, amount paid and a status that moves through draft → issued → partially paid → paid (or cancelled).

Payments are recorded against an invoice with an amount, a date, a reference and a method — cash, card, bank transfer or insurance. Partial payments are supported natively, which is how real dental treatment is actually paid for.

Multi-site from day one

• Branches — multiple sites, each with its own address, phone and email.
• Rooms — treatment rooms per branch, factored into availability.
• Users — with roles: Admin, Dentist, Assistant, Receptionist.
• Professionals — licence number, one or more specialties, and a personal colour used across the calendar.
• Professional schedules — the weekly working pattern per professional, per branch, per weekday, with start and end times and an optional assigned room.
• Specialties — a translatable catalogue (endodontics, orthodontics, and so on).

Nothing changes without a record

Every create, update and delete across every entity is written to an audit log automatically, recording the table, the record, the action and the timestamp.

The log is read-only through the API — it can be consulted but not edited or deleted from the application. Records that support it are soft-deleted (deactivated rather than destroyed), so history survives.