borismirsky/medical-booking

Purpose and Runtime

Medical-Booking is a role-based doctor discovery, scheduling, booking, and clinical-record system. It runs as a .NET Web API backend with a Next.js/React/TypeScript frontend. Roles are admin, doctor, and patient. Primary entry points are backend/MedicalBookingProject/src/MedicalBookingProject.Web/Program.cs and frontend/medical-booking/app/page.tsx.

Backend Layering

The backend follows a Clean Architecture-style split:

• Domain owns entities, DTOs, and service/repository interfaces: backend/MedicalBookingProject/src/MedicalBookingProject.Domain/Models, backend/MedicalBookingProject/src/MedicalBookingProject.Domain/Abstractions.

• Application implements use-case services: backend/MedicalBookingProject/src/MedicalBookingProject.Application/Services/BookingService.cs, backend/MedicalBookingProject/src/MedicalBookingProject.Application/Services/AppointmentService.cs, backend/MedicalBookingProject/src/MedicalBookingProject.Application/Services/TimeslotService.cs.

• Data access implements persistence and JWT infrastructure: backend/MedicalBookingProject/src/MedicalBookingProject.DataAccess/MedicalBookingDbContext.cs, backend/MedicalBookingProject/src/MedicalBookingProject.DataAccess/Repo, backend/MedicalBookingProject/src/MedicalBookingProject.DataAccess/Scripts/JwtGenerator.cs.

• Web exposes HTTP contracts and controllers: backend/MedicalBookingProject/src/MedicalBookingProject.Web/Controllers, backend/MedicalBookingProject/src/MedicalBookingProject.Web/Contracts.

Identity and Authorization Boundary

Admin, doctor, and patient are distinct domain user models, with roles represented in the domain. Authentication issues JWTs; the browser stores tokens in localStorage. This is the critical trust boundary between frontend requests and protected backend workflows. Relevant paths: backend/MedicalBookingProject/src/MedicalBookingProject.Domain/Models/Users, backend/MedicalBookingProject/src/MedicalBookingProject.DataAccess/Scripts/JwtGenerator.cs, frontend/medical-booking/app/Services/service.tsx.

Scheduling and Booking Flow

Admins create doctors and schedules/timeslots. Patients inspect available doctor slots, create or cancel bookings, and see their booking history. Doctors view their schedules; booked slots lead to appointment creation. Core models and services are backend/MedicalBookingProject/src/MedicalBookingProject.Domain/Models/Shedules/Timeslot.cs, backend/MedicalBookingProject/src/MedicalBookingProject.Application/Services/TimeslotService.cs, and backend/MedicalBookingProject/src/MedicalBookingProject.Application/Services/BookingService.cs.

Appointment and Medical Record Flow

A doctor turns a booked consultation into an appointment and records clinical information. Appointment and medical-record services mediate this transition before repository persistence. API boundaries are represented by request/response contracts and dedicated controllers: backend/MedicalBookingProject/src/MedicalBookingProject.Web/Controllers/AppointmentsController.cs, backend/MedicalBookingProject/src/MedicalBookingProject.Web/Controllers/MedicalrecordsController.cs, backend/MedicalBookingProject/src/MedicalBookingProject.Application/Services/MedicalrecordService.cs.

Persistence and Infrastructure

Entity Framework configurations map domain entities through the DbContext and repository implementations. The deployed/local persistence dependency is a checked-in SQLite database rather than an external managed service: backend/MedicalBookingProject/src/MedicalBookingProject.DataAccess/Database/medical_booking_db.db, backend/MedicalBookingProject/src/MedicalBookingProject.DataAccess/Configuration, backend/MedicalBookingProject/src/MedicalBookingProject.DataAccess/Repo.

Frontend Role Workspaces

Next.js App Router pages route users into separate role-oriented entry and profile pages. Components encode the primary user workflows: admin manages doctors/schedules, patient registers and books, and doctor manages appointments and records. Paths: frontend/medical-booking/app/profileadmin/page.tsx, frontend/medical-booking/app/profilepatient/page.tsx, frontend/medical-booking/app/profiledoctor/page.tsx.