The business problem
HealthOne is a small clinic that wants to move from spreadsheets to a real database. They need patients, visits, prescriptions, and billing — a manageable schema with enough complexity to be realistic. Your job: deploy the HealthOne database to your Hostinger MySQL instance, get it answering real medical-business questions through SQL, and (optionally) wrap it with a PHP page so the front desk can use it without writing queries.
Case kit
SQL schemas (pick your engine)
- HealthOneDB.sqlGeneric SQL flavor — works in Oracle APEX.
- HealthOneDB_MySQL.sqlMySQL-tuned for Hostinger deployment.
Hostinger deployment walkthrough
- HealthOne on MySQL/Hostinger — SlidesStep-by-step deployment, from Hostinger signup to first SELECT.
- MySQL on Hostinger — General Slides
- HealthOne — Play Store Deployment GuideStretch goal: ship the app to the Google Play Store via PWA.
Practice problems & worksheets
- HealthOne — SQL Practice ProblemsBusiness questions in plain English; you write the SQL.
- Week 9 — HealthOne Medical Worksheet
Full app starter (PHP + DB)
Three packages — the bare schema, a richer schema, and a complete PHP front-end. Start with whichever fits where you are.
- healthone2.zipSchema-only package, ready to import.
- healthone_full_app.zipSchema + PHP web app — drop into Hostinger and configure DB credentials.
- healthone_reports.zipReporting layer / canned queries on top of the schema.
Topics you'll be applying
- Decision 2 — Querying · self-joins and reporting queries
- Decision 6 — Deploy · MySQL on Hostinger, the core deployment skill
- Decision 7 — Emerging Tech · the PWA / Play Store stretch goal