Doc4All
Appointments, payments, and medical-report sharing in one healthcare application.
Project credit · Ansak Mahir
An academic application from Ansak’s project work, with a React frontend and separate Spring Boot BFF and application backends.
What it includes
Appointments and payments
Booking interfaces connect to backend booking services and a Braintree payment integration.
Medical-report sharing
Patients can upload reports, share them with a doctor, and revoke that access.
Different roles, connected workflows
Patient, doctor, dispensary, and administrator interfaces are supported by authentication and approval flows.
The challenge
Healthcare booking involves several connected workflows: finding a dispensary, managing doctor availability, booking an appointment, and sharing reports with a doctor.
The approach
The application brings these workflows into role-specific interfaces for patients, doctors, dispensaries, and administrators. A backend-for-frontend layer handles authentication and routes requests to the application backend.
The work
The project includes appointment and cancellation flows, a payment integration, and patient report upload and sharing. It demonstrates how a healthcare application can connect different users and services.
One application, three repositories
The frontend provides the screens and interactions. The BFF handles authentication, authorization, and routing. The application backend contains the booking, doctor, dispensary, payment, and report workflows. Together, they form one portfolio project.
This case study describes the academic project’s source code. It does not claim a live clinical deployment or measured patient outcomes.