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
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