Skip to content
Back to projects
AI2024

HayattaKAL

A Gemini-powered system that routes patients to the right appointment, built for Teknofest with a team I founded.

The HayattaKAL logo
Competition
Teknofest — AI in Health
Result
Passed the first stage, demo delivered
My role
Team founder & developer

Technologies

  • Gemini API
  • Web
  • Healthcare
  • Prototype

Overview

In 2024 I founded a team and entered Teknofest’s AI in health competition. We passed the first stage and turned the idea into a working demo: patients go through a structured pre-assessment before booking, and the Gemini API uses those answers to help them reach the right appointment.

The problem: appointments carry no information

When a patient books an appointment, all the system receives is a date and a department. What the complaint is, how long it has lasted, which medications are involved — all of it gets asked from scratch in the first minutes of the consultation.

Worse, patients usually pick the department by guessing. An appointment booked into the wrong department wastes both the patient’s time and the system’s capacity.

Our starting point was this: the patient already holds the information, it is just collected at the wrong moment and nobody uses it for routing.

Routing with the Gemini API

In the demo, a structured form comes before booking: what the complaint is, where the pain is felt, its severity out of ten, past and current medications, allergies, age, how long it has lasted and whether it is acute, any major operations, and whether the condition might be contagious.

Those answers go to the Gemini API, and the model helps route the patient to the right appointment. Diagnosis was never the goal — we ruled it out of scope from the start. The goal was to help the patient work out which department to go to, and how urgently.

The contagion question was there on purpose: a contagious complaint changes not only when an appointment is scheduled but how.

The system had three flows — booking, tracking and a calendar — so the pre-assessment became part of the patient’s own history rather than a one-off survey.

Founding a team, and knowing the scope

This was as much an organisational experience as a technical one. It was the first time I put an idea forward myself, gathered a team around it, split the work and managed the submission calendar.

Passing the first stage meant the idea held up in writing as well as in code, and that showed me how decisive it is to explain a problem clearly before building anything.

We never took on interface design; time was short and we prioritised showing the idea working. Looking back, I think in a demo the visual language is part of the argument too — that lesson came from this project.

Gallery

  • Pre-assessment form
    The structured form completed before booking — the input passed to the Gemini API.

Other projects