Danil Sidorov
RU EN DE
Telegram

Online booking for a dental clinic

Booking without phone calls, one shared schedule and separate areas for patients, doctors and administrators

Web service / Healthcare

Live interactive demo stand

Book a visit, check it in the patient area and open the shared schedule. A separate scenario simulates two requests for the same slot.

From an available time to a booking in the shared schedule

StackC#, ASP.NET Core, EF Core, SQL Server

The demo interface is in Russian. The clinic and patients are fictional. Data stays in this browser until reload; no emails or requests to a medical system are sent.

What to test in the stand:
  1. Choose a service, doctor and time; open your appointment and download its calendar file
  2. Add an available slot as administrator and find it in online booking
  3. Run the two-request simulation and compare the outcome for each patient
https://aurora-dent.example/schedule
Live Stand
Москва · демонстрационная клиника Ежедневно 8:00–23:00
+7 (495) 000-00-00
Аврора Дентстоматология
АК Анна КузнецоваПациент
Главная / Запись на приём

Онлайн-запись

Выберите услугу, врача и удобное время. Занимает меньше минуты.

Выберите услугу или продолжите без неё.

1. Какая услуга нужна? (необязательно)

Можно продолжить без выбора услуги. На следующем шаге покажем подходящих врачей.

Демо на вымышленных данных. Письма не отправляются. Изменения сохраняются до сброса или перезагрузки.

Turnkey implementation

Need a similar system for your business processes?

I will develop the architecture, fault-tolerant backend, and fast interface. Protected by NDA, clean transferable code, and transparent milestones.

  1. Free timeline and budget estimate within one day
  2. Contract and invoice
  3. Warranty and post-launch support

On weekdays usually within a couple of hours

I will reply personally, no aggressive sales pitch

Task

The clinic needed self-service booking without calls to reception. Patients should see available times and book independently while staff manage appointments in one system. A single slot must never go to two patients.

The project is under NDA. The clinic is not named; Aurora Dent, the doctors, patients and contact details in the demo are fictional.

Solution

Built a web application with ASP.NET Core, EF Core and SQL Server. Patients choose a service, doctor and available time. Their appointment appears in the patient area and shared schedule; cancellation releases it for another patient. The application supports email confirmations and calendar attachments.

Patients, doctors, managers and administrators have separate permissions. Doctors manage the current visit and recommendations, managers moderate reviews, and administrators maintain schedules and profiles.

This page contains a browser demonstration of the main workflows. It has no connection to the clinic, sends no emails and contains no medical records. A simulation of two requests explains the outcome of the original application’s double-booking protection.

What was done

  • Built service, doctor and available-time selection
  • Protected a slot against simultaneous bookings with a conditional UPDATE
  • Connected booking and cancellation to the patient area and shared schedule
  • Built current-visit controls, recommendations and patient history for doctors
  • Separated patient, doctor, manager and administrator permissions
  • Set up confirmation emails with calendar attachments
  • Prepared Russian, English, French and German interfaces
  • Added tests and a Docker build

Result

Patients can book without calling, doctors have their schedule and current visit, and administrators have a shared appointment list. Changes stay in one system without copying appointments between separate lists.

The demo supports booking and cancellation, calendar downloads, saving recommendations and adding an available slot.

Developer's note

Danil Sidorov
Danil Sidorov Project developer

What was hard

The main technical challenge was preventing two patients from taking the same slot. BookingService uses a conditional UPDATE that assigns a patient only while the slot is still free. One request updates the row; the next changes zero rows and receives a clear response that the time is taken. Tests in the original application cover this workflow.

Cancellation also needs consistent cleanup. It releases the slot and clears the former visit’s recommendations and services. The demo connects this behavior to one schedule model, and resetting cancels unfinished actions.

What came easy

Booking follows a clear sequence. The service is optional, doctors are filtered by the selected service, and available times belong to the chosen specialist. Patients can follow one understandable path without calling or searching across sections.

A shared access check handles role permissions. This made it possible to separate the areas consistently and test that patients work with their own visits and doctors with appointments assigned to them.

Technologies

C#ASP.NET CoreEF CoreSQL ServerDocker

Tell me about your task

Telegram