Case study: hospital system with a medical appointment app

2026-09-24 · 5 min read

Admissions, medical records, an appointment app for patients and doctors, and the hospital's website: how the three pieces fit together.

The problem

A hospital in Peru handled admissions, appointments and each doctor's slots through separate processes. Patients stood in line to get an appointment, doctors didn't know in advance how many patients they would see, and medical records weren't kept in one place.

What we built

1. Web hospital system (Genesis). Admissions and opening of medical records, patient search, triage, shifts and department modules, with a view that works the same on desktop and tablet. See the project.
2. Appointment app (Genesis Citas). Two logins, patient and doctor. The patient picks the day, specialty, office and time slot; the doctor sees their slots by date. See the project.
3. Institutional website. The hospital's public face, with access to its services. See the project.

The key decision: a single system

The app has no database of its own: it uses the same hospital system. That way, an appointment booked from a phone lands in the patient's medical record and in the doctor's schedule at the same time, with no syncing and no double entry.

Privacy by design

• Role-based access: admissions, doctors, administration.
• Patients only see their own appointments.
• Backups and access logs.
• In the project's public screenshots, patient data is pixelated.

What we learned

In healthcare, the tool has to adapt to the hospital's process, not the other way around. Starting with admissions and medical records, and adding the app later, meant each piece reached a team that already trusted the system. If your clinic or hospital needs something similar, see software for hospitals and clinics.

Start a project