Alfonso.
Projects

Backend / SaaS / Security

Healthcare scheduling and patient management

I developed a product connecting appointment requests with practitioner schedules and administrative work.

5 roles

An appointment management product developed to the pre-commercial stage.

Who can change an appointment

Authorizing clinic scheduling operationsPatients use a booking portal and clinic staff use a management dashboard. When a request arrives, the server checks role permissions before acting on the schedule.Booking portalPatientClinic dashboardClinic staffAPI · RBACServer-side checksClinic scheduleVisits and patients
Simplified architecture · Patients request appointments through the portal. Staff use their dashboard. Both paths pass through server-side authorization.

Engineering decision

Protecting direct API operations

I designed each scheduling transition alongside the permissions of the role performing it. A direct API request goes through the same checks as an operation initiated on screen.

Read the full technical study

Context and responsibility

I modelled patients, practitioners, availability and appointment states in Frappe. Patients could request appointments through a portal and administrative staff had their own management screens.

Authorization

BUSINESS_OWNER, CLINIC_MANAGER, FRONT_DESK, PRACTITIONER and PATIENT had different responsibilities. JavaScript guards guided navigation. Business operations required server-side permission checks, including direct API requests.

Outcome and lessons

I implemented scheduling, email notifications and multi-role workflows. The product reached a developed, pre-commercial stage. Designing each appointment transition required being explicit about who could perform it.