Clinic Accessibility Checklist for India: Booking, Arrival, Consultation, and Follow-Up

India’s Ministry of Health and Family Welfare has published Accessibility Standards for Healthcare. Its scope includes private clinics, and its coverage extends beyond entrances to outpatient areas, equipment, communication, and staff training. MoHFW accessibility standards.

Use that document when briefing an appropriately qualified accessibility professional. Ask them to identify the current requirements relevant to your premises and services, including applicable local rules.

Keep two workstreams separate:

• A professional assessment of technical requirements and necessary modifications.
• A clinic-led review of everyday arrangements and service failures.

The second cannot certify the first. Equally, a completed building modification does not establish that booking, registration, or patient communication works.

Maintain a clear list of what has been assessed, what remains uncertain, and who is responsible for resolving it.

Choose one common service, such as an outpatient consultation with an investigation request.

Write down every step the patient encounters. Include work performed outside the consultation room: finding the entrance, speaking to security, completing a form, locating the toilet, receiving a bill, and arranging another appointment.

For each step, ask:

1. What must the patient see, hear, read, reach, operate, or explain?
2. What happens if the usual method is not usable?
3. Who can arrange an alternative?
4. Does the patient know how to request it?

WHO’s disability-inclusive health services toolkit provides a framework for identifying barriers to health information and services. It is an international improvement resource, not a substitute for Indian requirements. WHO disability-inclusive health services toolkit.

For your own review, record an observed obstacle rather than a vague judgement.

“Reception available” says little. “The patient could not complete registration while seated, and staff had no agreed alternative” identifies something the clinic can investigate.

Replace broad descriptions such as “fully accessible” with specific, verified information.

Consider what a patient may need to know before travelling:

• Which entrance serves the clinic.
• Whether the route includes steps or a lift.
• Where a vehicle can stop.
• How to contact the clinic about access arrangements.
• Whether a particular service requires another room or floor.
• Whether a temporary disruption affects the visit.

Technical assessment should examine the actual route and facilities, not just whether a ramp or lift exists. The MoHFW standards address outpatient reception, waiting areas, examination spaces, and related access arrangements. MoHFW accessibility standards.

Assign someone to keep public information current. A lift outage or entrance change should not remain known only to the security guard.

Publishing a limitation does not remedy it. The clinic still needs an appropriate response and a plan to address the barrier.

A practical booking question is:

Is there anything we should arrange to help you access the clinic or use our services?

This invites an explanation of the task without requiring the receptionist to diagnose a condition.

An answer might concern a communication method, seating, assistance with a form, or access to the examination room.

For operational planning, distinguish:

• What the patient requested.
• What the clinic has agreed to arrange.
• What still needs confirmation.
• Who will confirm it.
• How the patient will receive the answer.

A request recorded in a note is not the same as an arrangement being available.

Do not promise specialist assistance before checking it. Equally, do not make the patient repeat the same request to every staff member because nobody owns the coordination.

Record only information needed for the arrangement, with appropriate access controls and an agreed review process.

Consider a fictional registration process that requires patients to scan a QR code, complete a phone form, and show the confirmation screen.

What happens when a patient cannot operate that process?

A useful alternative should connect to the same patient record. It should not create a second registration, lose an existing appointment, or require a relative to become the patient’s default contact.

Agree how authorised staff will assist while preserving privacy and allowing the patient to check what was entered.

Test practical exceptions:

• The patient can provide information verbally but cannot use the form.
• The patient prefers written communication.
• An accompanying person helps with data entry but is not the contact for clinical messages.
• The registration is interrupted and must resume without duplication.

The patient registration and family relationships guide explains the separate identity and relationship controls. Accessibility support should work with those controls, not bypass them.

An appointment can be correctly recorded while the next step remains inaccessible.

Review how patients know where to wait and when they are being called. A token display alone may not work for everyone; neither may an announcement alone.

Agree an appropriate method with the patient and identify who will use it. Do not display a diagnosis or detailed support need on a public queue screen.

Before a service begins, confirm that the required room, equipment, and competent assistance are available. The MoHFW standards discuss accessible examination equipment and the space needed to use it. MoHFW accessibility standards.

Do not improvise a physical workaround

Reception staff should not promise that someone will simply lift or carry a patient.

Questions about transfers, positioning, equipment suitability, and clinical alternatives belong with appropriately trained professionals. The administrative task is to identify the unresolved arrangement and bring it to the responsible person before it becomes a surprise.

An accompanying person may provide valuable assistance. Their presence should not automatically redirect every question away from the patient.

Agree how the patient wants the person involved, subject to the applicable consent and decision-making framework. Do not infer lack of decision-making ability from a communication or mobility difficulty.

Separate different kinds of involvement:

• Helping someone reach the room.
• Assisting with an administrative form.
• Supporting communication.
• Receiving appointment updates.
• Receiving clinical information.
• Acting under a recognised decision-making arrangement.

These are not interchangeable permissions.

For example, someone who helps with arrival may not be the intended recipient of laboratory reports. Record contact arrangements deliberately rather than copying the companion’s number into every field.

The clinic’s clinical consent process remains separate. See the informed-consent guide for that documentation workflow.

Ask your website or software provider to demonstrate the task a patient must complete, not merely show an accessibility statement.

For a booking or enquiry form, useful checks include:

• Completing the form using a keyboard.
• Seeing which control has keyboard focus.
• Identifying fields from meaningful labels.
• Understanding an error and correcting it.
• Using enlarged text without losing controls.
• Understanding information without relying on colour alone.

These checks reflect introductory W3C accessibility guidance; they do not constitute a complete conformance assessment. W3C: Designing for Web Accessibility.

Test the actual destination of a link. A readable message can still lead to an unusable form.

Keep an appropriate alternative available when a digital process fails, and record the failed task for correction. Asking a relative to complete everything should not be the clinic’s automatic response.

For explaining the clinical plan itself, use the separate patient-instructions guide.

A clinic can begin with a small, access-controlled improvement register.

The following is a suggested editorial template, not an official assessment form:

Keep patient-specific information separate where possible. An improvement record usually needs a description of the barrier, not a copy of the person’s clinical history.

Use accurate outcomes. “Alternative offered” is different from “alternative worked.” “Patient cancelled” should not hide that an agreed access arrangement was unavailable.

If someone raises a complaint, connect it to the clinic’s complaint-handling process without making a complaint a prerequisite for action.

An arrangement that worked yesterday may fail today.

Create a short opening check for the access arrangements your clinic actually relies on. It might confirm that the agreed entrance is available, a designated room is usable, and staff know about any booked support arrangement.

When something changes, identify:

1. Which appointments or services may be affected.
2. Who will review the available options.
3. Who will contact the patient through the agreed route.
4. What information needs updating.
5. How the issue will remain visible until resolved.

Do not automatically cancel care because a routine arrangement fails. The responsible team should review the situation and communicate appropriate options.

Conversely, do not mark the issue resolved merely because a message was sent. Record whether the revised arrangement was confirmed.

Include access needs in the clinic’s professionally reviewed emergency and evacuation planning; this checklist is not an evacuation procedure.

Use fictional appointment details for an internal exercise. Do not ask someone to attempt an unsafe route or transfer.

The scenario

A patient has requested a particular arrival arrangement and a written notification when the clinician is ready. Reception records both.

On the morning of the visit, the planned consultation room becomes unavailable.

Ask the team to demonstrate:

• Who notices that the room change affects the arrangement.
• Who checks the alternative room.
• Whether a qualified person must assess any equipment or assistance requirement.
• How the patient is informed.
• How the agreed waiting notification reaches the person managing the queue.
• What happens if the alternative cannot be confirmed.

What the exercise should reveal

The objective is not to obtain a perfect checklist score. It is to discover where a request becomes detached from the person responsible for fulfilling it.

Record the actual failure point: an appointment note nobody sees, a room change without review, or a contact method that the patient cannot use.

Then repeat that part of the exercise after changing the process.

Staff walkthroughs are useful, but they do not represent every patient’s experience.

Invite people with different access needs to provide feedback through an appropriately planned, voluntary process. Make participation itself accessible, explain its purpose, protect privacy, and agree suitable recognition or compensation.

For digital services, W3C recommends combining evaluation with users with disabilities and standards-based assessment. It also cautions against generalising from one person’s experience to everyone with a similar disability. W3C: Involving Users in Evaluating Web Accessibility.

Keep the evaluation specific. “Could the participant find the entrance information?” is more useful than “Was the website accessible?”

Document what was tested, what was not tested, and what changed. Positive feedback on one task is not evidence that the entire clinic or software product is accessible.

CliniKite’s published features include doctor schedules, appointment booking, patient lookup, arrival workflows, and a live queue. Those capabilities provide relevant points for discussing how access arrangements can fit into daily operations. CliniKite features.

They do not establish that CliniKite has a dedicated accessibility-support module, that every output works with every assistive technology, or that a clinic meets accessibility requirements.

Bring a concrete scenario to the demonstration:

• Where could an agreed support arrangement be recorded?
• Which roles would see it?
• Would a room or clinician change make it easy to overlook?
• Could it be updated without changing patient identity?
• What information might appear on a public display?
• Which tasks require a manual process?
• What accessibility evaluation evidence is available for the functions being demonstrated?

Review CliniKite’s security and data information alongside those questions.

Software can support coordination. It cannot certify the premises, supply trained assistance, or replace a professional assessment.

A useful clinic accessibility checklist asks whether a patient can complete the visit—not merely whether individual facilities exist.

Start with one service. Identify the barriers, confirm who can arrange support, and separate immediate assistance from the longer-term correction.

Keep public information accurate, test the actual patient journey, and involve people with disabilities in evaluating improvements. Record unresolved limitations honestly and obtain qualified advice where technical or clinical decisions are required.