Case studyHealthcare11 min read

ChikitsaOne: fixing a multi-specialty hospital's OPD, one queue at a time

A multi-specialty hospital's outpatient department had patients waiting hours with no idea when they would be seen, and doctors writing on paper that nobody could read later. We built ChikitsaOne: online appointments, a live token and queue system, a fast doctor's console with structured prescriptions, and lab and pharmacy integration — 27 features built around fifteen-minute consultations.

27
Features shipped
4
Apps & platforms
9
Team members
22
Weeks to rollout
ChikitsaOne patient app and doctor console
ChikitsaOne: from booking to prescription, without the paper.
01

Three hours in the waiting room

Our first meeting with ChikitsaOne's medical director was not in a boardroom. She asked us to sit in the orthopaedic OPD waiting area for a morning. Patients arrived at nine for appointments that did not happen until noon. Nobody knew their position in the queue; relatives hovered at the doctor's door asking "how many more?"; staff answered the same question hundreds of times.

Inside the consultation rooms, doctors were writing prescriptions by hand, reading old paper files that patients had to carry, and ordering tests on slips that the lab sometimes could not decipher. The hospital's clinical quality was excellent. Its outpatient experience did not reflect it.

“Our doctors give a patient fifteen good minutes. Then we make them wait three hours for it.”

— ChikitsaOne's medical director
02

Mapping the OPD flow

We mapped the patient's path through the OPD: registration, billing, vitals, waiting, consultation, tests, pharmacy and follow-up booking. The biggest discovery was that queues were not really about doctor speed. They were about unpredictable arrivals, walk-ins mixed with appointments with no rules, and patients returning with test reports and joining the back of the line.

We also timed consultations. Doctors spent a surprising share of each consultation searching for previous information — earlier prescriptions, test values, allergies — that was either on paper or in a system that took too many clicks to reach.

What actually caused the waits
  • All appointment patients told to arrive at the start of the session
  • Walk-ins and appointments mixed without rules
  • Patients returning with reports rejoining the full queue
  • Doctors searching for past records during consultations
IT professional working with network equipment
Mapping the OPD flow from registration to pharmacy.
03

Designing the doctor's fifteen minutes

We designed the doctor console with one metric in mind: seconds of doctor attention spent on software. The patient summary loads before the patient walks in — allergies, chronic conditions, last prescription, recent results. Prescriptions are built from favourites and recent medicines with dose defaults; a common prescription takes a few taps. Doctors who prefer speaking can dictate notes, which are transcribed into the record for them to review.

We tested the console with doctors from four departments using real (anonymised) cases and a stopwatch. If a change added time, it did not ship.

04

The team

We included a clinical informatics consultant — a doctor with software experience — to review every clinical workflow alongside the hospital's own department heads.

1
Engagement lead

Department rollout planning and on-floor support.

1
Clinical informatics consultant

Clinical workflow review and safety checks.

1
Product designer

Doctor console, queue experience and patient app.

1
Mobile engineer

Patient app for appointments, tokens and records.

2
Frontend engineers

Doctor console, reception and queue displays.

2
Backend engineers

Scheduling, clinical records, lab and pharmacy integration.

1
QA engineer

Clinical scenarios, load testing for peak OPD hours.

9 people in total, working as one team.

05

Decisions we made with the clinicians

In healthcare, every design decision is also a safety decision. Each of these was reviewed with the medical director and department heads.

01

One arrival time or time slots?

  • All patients arrive at session start
  • Time-slotted appointments with walk-in rules

Our call: Time-slotted appointments with walk-in rules. Waiting was driven by everyone arriving at once. Slots spread arrivals, and clear walk-in rules kept emergencies and walk-ins fair.

02

Free-text or structured prescriptions?

  • Free-text typing
  • Structured prescriptions with favourites and safety checks

Our call: Structured prescriptions with favourites and safety checks. Structured prescriptions enable allergy and interaction checks, legible printouts and pharmacy integration, while favourites keep them fast.

03

Should AI suggest diagnoses?

  • AI diagnosis suggestions
  • AI only for dictation and summarising history

Our call: AI only for dictation and summarising history. Clinical decisions belong to doctors. AI saves time by transcribing notes and summarising records, never by suggesting diagnoses.

04

Cloud or hospital-hosted?

  • Public SaaS
  • Private cloud controlled by the hospital

Our call: Private cloud controlled by the hospital. Patient records are highly sensitive. A private deployment under the hospital's control met its data-protection policy and gave predictable performance.

05

Returning patients with reports: rejoin the queue?

  • Back of the queue
  • Priority review slot with the same doctor

Our call: Priority review slot with the same doctor. Patients returning only to show a report needed a minute, not a full consultation. Priority review slots removed a major source of repeated waiting.

06

The 27 features

Everything that shipped across patients, reception, doctors and the wider hospital.

Patients
Know when to come, know where you stand.
  • 01Online appointment booking

    Doctor and slot selection with confirmation.

  • 02Live token tracking

    Queue position and estimated time on the phone.

  • 03Digital prescriptions

    Prescriptions and advice available in the app.

  • 04Test reports

    Lab results delivered to the app when ready.

  • 05Follow-up reminders

    Reminders for follow-ups and medicine refills.

  • 06Health ID linking

    Link records with the national digital health ID.

Reception and queues
Order at the front desk.
  • 07Fast registration

    New patients registered in under a minute.

  • 08Token generation

    Tokens for appointments and walk-ins with priority rules.

  • 09Waiting-area displays

    Live queues per doctor on screens.

  • 10Vitals capture

    Nurses record vitals before the consultation.

  • 11OPD billing

    Consultation and procedure billing with receipts.

Doctor console
Fifteen minutes, spent on the patient.
  • 12Pre-loaded patient summary

    Allergies, conditions, last prescription and recent results.

  • 13Structured prescriptions

    Favourites, dose defaults and one-tap repeats.

  • 14Allergy and interaction alerts

    Warnings before a prescription is saved.

  • 15Voice notes

    Dictated notes transcribed for review.

  • 16Test ordering

    Orders sent directly to lab and radiology.

  • 17Department templates

    Specialty-specific templates chosen by department heads.

Hospital integration
Connecting the departments.
  • 18Lab integration

    Orders in, results back into the record automatically.

  • 19Pharmacy integration

    Prescriptions sent to the in-house pharmacy.

  • 20Department scheduling

    Doctor rosters and session capacities.

  • 21OPD analytics

    Waiting times, consultations and no-shows by department.

Safety and compliance
Protecting patient data.
  • 22Role-based access

    Separate rights for reception, nurses, doctors and admin.

  • 23Access audit log

    Every record view and edit recorded.

  • 24Consent management

    Patient consent captured for record sharing.

  • 25Downtime mode

    Printable token and prescription fallback if systems are down.

  • 26Data backup and recovery

    Tested backups with recovery procedures.

  • 27Privacy controls

    Sensitive notes restricted to treating clinicians.

ChikitsaOne live queue display in a waiting area
The waiting-area display: every patient knows where they stand.
07

Rolling out one department at a time

We launched in orthopaedics, the busiest OPD and the one where we had started, with our team on the floor for the first two weeks. Reception staff kept a paper fallback for the first days. Time-slotted appointments changed arrivals immediately: patients with a slot came near their slot instead of at nine.

Other departments followed in waves. Each department head chose their own prescription favourites and templates before going live, which did more for doctor adoption than any training session.

  1. Weeks 1–3
    Discovery

    Waiting-area observation, OPD flow mapping, consultation timing.

  2. Weeks 4–6
    Design

    Doctor console tested with a stopwatch; queue rules agreed.

  3. Weeks 7–15
    Build

    Patient app, reception, console, displays and integrations.

  4. Weeks 16–18
    Orthopaedics pilot

    Busiest OPD live with on-floor support.

  5. Weeks 19–22
    All departments

    Department-by-department rollout with custom templates.

08

What we learned

Queues are a scheduling problem before they are a software problem. Time-slotted arrivals and clear walk-in rules did more than any display screen.

Measure the doctor's time, not the software's features. Every second saved in the console was a second returned to the patient.

Built with
  • React Native
  • Next.js
  • NestJS
  • PostgreSQL
  • FHIR-style clinical records
  • Speech-to-text for notes
  • ABDM integration
  • Private cloud
CTA Background

Building something like ChikitsaOne?

Bring the problem as it actually is, constraints included. You will get a straight answer on whether we are the right team.

View Our Work
AI-First Engineering
Secure & Scalable
Built to Deliver Impact
More case studies