Project

Clinic scheduling

An app and backend for doctors with their own practice: locations, hours, appointments and records.

Year: Nov 2024 — Abr 2025
Role: Mobile + backend
Team: Pasantía · Blink
Stack: React NativePythonDjangoPostgreSQL

Nov 2024 — Abr 2025Clinic schedulingReact Native · Python · Django · PostgreSQL

The problem

A doctor with their own practice needed a phone channel to publish locations and hours and to work with the patient: appointments and records. It was not a hospital HIS; the cut was the doctor's own office.

Technical decisions

A React Native app and a Django API on Postgres. The model follows the clinical flow (locations, availability, visit, record), not a loose CRUD. It was built and tested on Android.

React Native, shipped on Android

One cross-platform codebase. In this cycle it was compiled and validated on Android only; there was no published iOS build.

Python, Django and PostgreSQL

The server holds practices, locations, hours, appointments and records. The app is not the system of record: it talks to that API.

A private-practice flow, not a hospital

Published locations and hours, then the visit and the record. The product fitted a doctor running their own consult, not an institutional chart.

Interface

A mobile app. Hours and locations, appointments and clinical records, the doctor–patient loop. No public screenshots or URL: the data is clinical and the repo is private.

01Clinic schedulingReact Native · Python · Django · PostgreSQL

02Clinic schedulingReact Native · Python · Django · PostgreSQL

03Clinic schedulingReact Native · Python · Django · PostgreSQL

04Clinic schedulingReact Native · Python · Django · PostgreSQL

Result

Android

validated platform

Private

repo and demo

Closed in April 2025 as an internship at Blink. No publishable count of doctors, visits or pilot practices. The cut (scheduling and the doctor–patient loop on mobile) is what later feeds Sitafacil on the booking side.

Learnings

The domain (who sees whom, at which location, at what time, with which record) drives the model. Android-only was enough to close the cycle; iOS was left out on purpose. Sitafacil reuses published hours, not the clinical chart.