All projects

Full stack / Doctor booking / 2026

MediFlow

Integration in progress

A doctor-booking project with patient, doctor, and admin interfaces and a separate NestJS API for authentication, availability, appointments, and medical records.

My role

Full-stack development

Skills & technologies

  • Next.js
  • React
  • TypeScript
  • Tailwind CSS
  • NestJS
  • Prisma
  • PostgreSQL
  • JWT
  • Swagger

The Problem

What needs to change

Patients need to discover doctors and arrange appointments, while doctors need to manage availability and patient care. Administrators need a separate view of the platform rather than sharing the same workflow as patients.

The Solution

How MediFlow helps

MediFlow organizes discovery, booking, availability, and care into patient, doctor, and admin interfaces, supported by a modular NestJS backend. Frontend/API integration is still in progress, and some screens remain mock-backed.

01 / Contribution

What I worked on

Developed the healthcare application across separate frontend and backend repositories, covering role-specific interfaces and a modular NestJS API.

02 / Capabilities

What the project includes

  • Patient, doctor, and admin interfaces for discovery, booking, availability, and platform management.
  • NestJS API modules for authentication, users, doctors, clinics, availability, and appointments.
  • Backend modules for prescriptions, medical records, reviews, notifications, and reporting.
  • Prisma/PostgreSQL data access, JWT and role guards, DTO validation, and Swagger API documentation.

03 / Architecture

System overview

  1. 01Next.js / React role-specific interfaces
  2. 02API integration boundaries / remaining mock datasets
  3. 03NestJS modules / JWT and role guards
  4. 04DTO validation / service layer
  5. 05Prisma / PostgreSQL

Responsibility map · Read alongside the implementation status above.

04 / Decisions

Engineering notes

Role-specific organization

Next.js App Router groups the public, patient, doctor, and admin experiences while shared components provide consistent interactions.

Modular backend responsibilities

NestJS separates authentication, availability, appointments, and records into modules, with application-wide JWT and role guards. Prisma provides the PostgreSQL data-access layer.

Separate repositories

The Next.js frontend and NestJS API are maintained independently. The frontend configures the API base URL, while the backend configures the allowed frontend origin.

05 / Validation

Validation & scope

Reviewed both READMEs, package manifests, and the backend application module. These confirm separate frontend and backend implementations. The frontend README includes auth integration instructions but also retains prototype and mock-data limitations; a running end-to-end deployment has not been verified.

06 / References

Source & technical evidence

Next project

SurplusLink AI