Patient Waiting Time in Indian Clinics: A Practical Measurement and Improvement Guide

Appointment access and waiting inside the clinic are different questions.

Appointment access concerns the time between requesting care and obtaining a suitable appointment. In-clinic waiting concerns what happens after the patient arrives.

This article focuses on the second question. For booking rules, walk-ins, reminders and availability, see the clinic appointment scheduling guide.

Even within the clinic, one number is rarely enough. Choose a primary interval and define its endpoints.

These are proposed operational definitions, not universal reporting standards.

Arrival-to-consultation time may include registration and nursing activity. Total visit duration includes care as well as waiting. Neither should automatically be labelled “idle time.”

Indian public-sector quality guidance also distinguishes consultation time from waiting time. The NHSRC-hosted *Quality Standards for Urban Primary Health Centre*, October 2015, lists both as separate indicators in its general-clinic checklist. This is a useful measurement reference, not a claim that every private clinic must use that framework or a particular waiting-time target. NHSRC quality standards, printed page 68.

A timestamp can be precise and still measure the wrong event.

The time a receptionist finishes registration may be later than the patient’s arrival. Opening a consultation screen may occur before the doctor starts seeing the patient. Signing a note may happen after the patient leaves.

Before using software data, ask:

• What action creates this timestamp?
• Does it represent the real-world event we want to measure?
• Can staff enter it later?
• Can it be corrected?
• What happens when a patient changes doctor or leaves temporarily?

Observe a few visits and compare the recorded events with what happened. Use the clinic’s approved privacy process and avoid recording clinical conversations.

Separate the event from the time it was entered

If an arrival is entered retrospectively, preserve that distinction wherever the collection method allows it. Do not silently treat an administrative entry time as physical arrival.

For manual observations, use a consistent clock. For software exports, confirm the timezone and date handling.

A negative interval, such as consultation starting before the recorded arrival, should trigger a data-quality check. Do not automatically turn it into zero and keep calculating.

The clinic audit-log guide explains why time, authorship and corrections need dependable meanings.

Start with a short walkthrough involving the people who perform the work.

Write down the sequence a patient follows: arrival, registration, required intake, consultation and any subsequent services. Include loops. A patient may return to reception for a missing document or visit a second room before seeing the doctor.

NHS England’s process-mapping guidance recommends involving staff and patients and adding timings to understand how a process works. Its guidance concerns general-practice access in England; the relevant principle here is to inspect the real journey rather than assume the written procedure describes it. NHS England: Map your existing processes.

For each handoff, ask what allows the next step to begin. Is the next person notified? Is a record missing? Is a room unavailable?

Do not start by declaring reception or consultation “the bottleneck.” Establish where time accumulates before assigning a cause.

Define the observation period before collecting results.

A practical starting exercise might cover selected complete sessions over two weeks, including both morning and evening work if the clinic operates both. This is an illustrative starting point, not a statistically validated sample size.

For a low-volume session, recording every eligible visit may be simplest. In a busier clinic, agree a consistent sampling rule that staff can follow.

Avoid observing only quiet hours, cooperative patients or visits that finish quickly.

The Institute for Healthcare Improvement distinguishes measurement for local improvement from research and supports collecting enough useful data to guide learning. That does not make a small sample representative of every clinic session or patient group. IHI: Establishing measures.

Keep the collection sheet small

Useful fields might include:

• A restricted visit reference.
• Session and service.
• Scheduled appointment or walk-in.
• The defined event timestamps.
• Whether the visit was completed.
• Missing-data flags.
• A brief operational observation, where relevant.

Do not copy diagnoses, prescriptions or patient phone numbers into a waiting-time worksheet unless a specifically approved purpose requires them.

A coded reference can still be identifiable through a separate lookup. Treat it as controlled clinic information, not automatically anonymous data.

A waiting-time review becomes misleading when awkward cases quietly disappear.

Agree the rules before looking at the results.

Early arrivals

Keep actual arrival and booked time separate. An early arrival affects the patient’s time on site, but it does not necessarily mean the clinic started late.

If appointment punctuality matters, report it separately from arrival-to-consultation time.

Late arrivals and walk-ins

Retain the visit type and timing context. Do not assume that scheduled patients and walk-ins followed identical routes.

Patients who leave before consultation

Report these visits separately. They do not have a completed arrival-to-consultation interval.

Excluding them from the completed-visit calculation may be necessary, but hiding their number can make a difficult session look better than it was.

Temporary departures and interruptions

Record relevant departures or interruptions if your method supports them. Preserve the original timestamps and explain any adjusted calculation.

Clinical priority must remain clinician-led. A measurement project should never delay urgent assessment to preserve queue order or produce a cleaner dataset.

For each interval, show how many visits had valid measurements and how many did not.

If 24 visits were eligible but only 19 had both required timestamps, report that coverage. Do not describe the result as covering all 24 visits.

Useful summaries include:

• The median interval.
• The mean interval, where useful.
• The longest observed interval, with context.
• The number exceeding a clearly defined local review threshold.
• The number of incomplete visits and missing observations.

The median is the middle value after sorting the observations. The mean is their sum divided by the number of observations.

Consider six fictional ready-for-doctor waits:

8, 10, 12, 14, 16 and 60 minutes.

The median is 13 minutes, while the mean is 20 minutes. Both calculations are correct. They describe different aspects of the same small dataset.

The 60-minute wait deserves investigation, but its presence does not prove negligence or identify the cause.

For larger datasets, a consistently calculated percentile can help describe longer waits. With very small samples, show the individual observations rather than giving a percentile more authority than the data supports.

A single clinic-wide average may mix different services, staffing arrangements and patient journeys.

Compare sensible groups such as morning and evening sessions, booked and walk-in visits, or consultation-only and procedure visits.

Do not create so many categories that each contains only one or two observations. Start with the distinction most likely to explain the operational problem.

Avoid using raw waiting times to rank doctors. Case complexity, interruptions, staffing and the services provided may differ.

Look for patterns that suggest a question to investigate:

• Does delay build before the first consultation starts?
• Does the queue grow after a particular handoff?
• Are records repeatedly unavailable?
• Does post-consultation time increase when one counter handles several tasks?

Record evidence separately from explanations. “The report was unavailable when the patient reached the room” is an observation. “Staff are inefficient” is an unsupported conclusion.

Choose a change that addresses an observed problem.

If returning patients repeatedly wait while staff locate existing records, a small test could examine whether an authorised pre-session record check helps. If patients finish consultation but cannot find the next counter, test clearer handoff instructions.

Write down the expected effect before the test. Also record what would make you stop or revise it.

IHI’s Plan-Do-Study-Act guidance describes testing a change locally, observing what happens and adapting it before wider implementation. A small trial is an opportunity to learn, not proof that the change should become permanent. IHI: Testing changes.

Watch for unintended consequences

Pair the waiting-time result with checks on what might get worse.

Examples include:

• More unfinished documentation after clinic hours.
• Additional reception overtime.
• Patients reporting that explanations felt rushed.
• More correction work at checkout.
• Longer waits at a downstream counter.

These are examples of balancing measures: checks for problems created elsewhere by an improvement effort. IHI: Establishing measures.

A faster queue is not a sufficient success criterion if necessary consultation, accessibility support or patient explanation is being squeezed out.

Consider this fictional consultation-only visit:

Using the definitions above:

• Arrival-to-consultation elapsed time: 30 minutes.
• Ready-for-doctor waiting time: 17 minutes.
• Consultation duration: 15 minutes.
• Post-consultation elapsed time: 13 minutes.
• Total visit duration: 58 minutes.

The patient did not necessarily spend all 58 minutes waiting. The first 13 minutes included the period before readiness, and the consultation itself took 15 minutes.

Some measures overlap, so they should not all be added together.

Suppose an observation shows that checkout involved repeated clarification of a service entry. The next investigation should examine that handoff. The timeline alone does not justify shortening the consultation.

After a change, compare similar visits and check whether the original problem recurs. This is an illustrative calculation, not a CliniKite customer result.

One quieter afternoon does not establish lasting improvement.

Keep the measurement definition and collection approach stable while you compare sessions. Note changes in staffing, service mix, opening times and other circumstances that could affect interpretation.

A simple time-ordered chart can show the chosen measure across successive sessions, with annotations for changes tested. IHI’s run-chart guidance emphasises examining patterns over time when assessing whether improvement has occurred and lasted. IHI: Run chart tool.

Show the number of valid visits alongside each session’s result. A median based on three visits should not look indistinguishable from one based on thirty.

If missing timestamps increase after a workflow change, investigate that too. A cleaner-looking result may reflect poorer recording rather than a better patient journey.

Measurement does not remove today’s delay.

Agree who will update patients when the clinic is running behind and what information can be given reliably.

Avoid promising an exact consultation time merely because the dashboard shows a queue position. Explain known delays, available options and how to ask for help.

Do not disclose another patient’s circumstances when explaining why the order has changed.

Check whether a person needs seating, communication assistance or another reasonable arrangement through the clinic’s established process. The clinic accessibility checklist provides a broader review of barriers across the visit.

A patient’s concern about waiting should also remain eligible for the clinic’s normal complaint process. It should not be dismissed because the session average looks acceptable.

CliniKite’s published features describe doctor schedules, check-in, walk-ins and live queue lanes for waiting, consultation and checkout. Those workflow distinctions are relevant to understanding a visit. CliniKite features.

However, a live queue is not automatically a validated waiting-time audit.

Before relying on a report, ask CliniKite to demonstrate:

1. Which events are timestamped.
2. What creates each timestamp.
3. How corrections, transfers and incomplete visits appear.
4. Whether the necessary event history can be exported.
5. Which calculations are available and which require separate analysis.

Do not assume that automated percentile reporting, reliable physical-departure timestamps or predictive waiting-time estimates are included.

Review access and export arrangements for the chosen deployment. CliniKite’s security page describes role-based access and data portability, but the exact dataset and permissions should be verified for your workflow. CliniKite security and data.

To improve patient waiting time, first make the measurement trustworthy.

Choose a clear interval, verify its timestamps, include difficult cases transparently and examine the handoffs where time accumulates. Test a focused change, then check both the waiting-time result and its effects elsewhere.

The goal is not to make every consultation shorter. It is to remove avoidable delay while preserving the care, explanation and support each patient needs.