HealthSync.

01

Context & problem

HealthSync explores a focused health-data workflow: recording blood glucose, viewing trends, and exporting records. The work began as a three-person university course assignment before I rebuilt it as an independent full-stack project.

02

My role

In the original group assignment, I focused on the mobile module. In the independent rebuild, I owned the codebase end to end, from requirements and schema design through frontend, backend, migration, and deployment.

03

How it works

The browser connects to a Flask backend for authentication, health-data logging, and CSV exports. PostgreSQL stores the records; Chart.js supports trend visualisation.

Docker packages the application for Render. Environment-based configuration and a health-check endpoint support deployment and service checks.

04

Key decisions

The rebuild moved from SQLite to PostgreSQL for the deployed application. Docker and environment configuration made the runtime and database connection explicit parts of the delivery process.

I worked through port binding, database authentication, and configuration issues while bringing the application online.

05

What I built

Delivered authentication, data logging, CSV export, and visualisation as part of the independent rebuild.

Completed a database migration and containerised deployment. These are implementation outcomes, rather than evidence of clinical impact or adoption.

06

Limits & next steps

This project demonstrates application development and deployment, rather than clinical validation. No health outcomes or user-adoption metrics are claimed.

The migration and deployment work highlighted the importance of checking configuration alongside application behaviour. Formal usability and impact evaluation remain outside the evidence available for this case study.