Ward A counts a hand-hygiene opportunity when a staff member enters the bay. Ward B starts at patient contact. Both send a percentage to the same dashboard.
The arithmetic can be flawless and the comparison still false.
An NABH infection-control checklist needs to preserve definitions, observation method, ownership, evidence, and follow-up. A copied list of green ticks cannot do that.
Scope note: This article is an operational evidence aid. It does not prescribe infection-prevention procedures, clinical thresholds, isolation decisions, medicines, or treatment. Use the current NABH material, national and local requirements, and policies approved by qualified infection-control and clinical leaders.
Freeze the source and programme
Write four facts at the top of the working file:
Healthcare organisation: _______________________________
NABH programme and edition: ____________________________
Local infection-control programme version: _____________
Review owner and date: _________________________________
The NABH Hospital Accreditation Standards, 6th Edition is one source for hospitals using that programme. Entry-level, SHCO, blood-centre, clinic, and other programmes have their own scopes. Do not label a checklist “NABH” without naming the programme and edition behind it.
The NABH E-Mitra page also provides implementation checklists, including hospital infection control. Treat the current official file as an input to local review, not as permission to ignore facility risk, services, state requirements, or later updates.
Build the programme spine
Begin with programme governance. If nobody can explain who approves the infection-control plan, a perfect ward checklist will not save the review.
| Programme record | Evidence to inspect | Decision owner |
|---|---|---|
| risk assessment and annual plan | approved scope, priorities, review date, change history | infection-control committee and leadership |
| roles and terms of reference | named committee, infection-control officer and nursing roles, meeting record | hospital leadership |
| approved policies and procedures | version, approval, distribution, withdrawal of old copy | qualified clinical owner |
| resource plan | staffing, supplies, training, environmental and laboratory support | leadership and programme owner |
| surveillance plan | definitions, populations, data sources, validation, reporting route | infection-control team |
| improvement record | finding, action, owner, due date, recheck, committee review | action owner and governance group |
Do not count committee meetings as proof of infection control. Open one decision from the minutes and follow it into a changed practice, completed action, or documented reason for no change.
Walk one patient route
Policies often pass while handoffs fail. Pick one service line and trace a synthetic patient journey through registration, examination, procedure if applicable, cleaning turnover, specimen handling, waste path, and discharge.
For every handoff, record:
- the approved instruction staff should follow;
- what the reviewer observed;
- the record or physical evidence available;
- the role that owns a defect;
- the recheck method and date.
The NCDC and MoHFW national infection-prevention guidelines describe programme structure and infection-prevention practices for healthcare facilities. Local clinical leaders must translate applicable guidance into approved procedures for the hospital’s services. A checklist writer should not invent a procedure from a search snippet.
Keep surveillance definitions beside results
A dashboard should never show a rate without the approved definition that produced it. At minimum, retain:
| Field | Why it matters |
|---|---|
| indicator name and purpose | stops one label from serving several questions |
| numerator and denominator | makes the calculation reproducible |
| inclusion and exclusion rules | shows the population boundary |
| observation or data method | distinguishes direct checks from record extracts |
| time period and locations | prevents unlike units from being merged |
| definition version | makes trend breaks visible |
| validator and validation sample | records whether source data were tested |
| interpretation and action | separates measurement from a clinical conclusion |
Test a definition change in the software. The old result should keep its old definition. The new rule should start a visible series or carry a clear comparability warning. Recomputing history without disclosure makes the chart tidier and the evidence worse.
Inspect training as job evidence
A roster shows attendance. It does not show that the right people received training for their actual work or that a change reached the next shift.
Select one role, one agency or contract worker, one new joiner, and one person who moved departments. Check the assigned content, trainer or approved method, date, competency evidence where the hospital requires it, missed-session route, and retraining after a policy or workflow change.
Then compare the training record with field observation. If practice and policy disagree, record the gap without rewriting the observation to match the slide deck.
Connect incidents to programme change
Choose one synthetic infection-control incident. Verify that the workflow can preserve the initial facts, restrict sensitive material, assign the investigation, record contributing conditions, open corrective action, and schedule a later effectiveness check.
Do not use the same field for immediate response, root-cause analysis, and committee conclusion. They occur at different times and may have different access rules.
Use this closure line:
Finding: _______________________________________________
Immediate containment recorded by: _____________________
Approved corrective action: ____________________________
Evidence of completion: ________________________________
Effectiveness recheck and result: _______________________
Committee or leadership review: ________________________
Make the software earn its place
An infection-control module is useful when it reduces transcription and missing ownership without making clinical decisions. Ask a vendor to demonstrate one definition, one observation sample, one exception, one action, one overdue recheck, and one version change.
Reject claims that the software itself makes a hospital “NABH compliant.” The hospital owns its programme, clinical decisions, source data, interpretation, improvement work, and accreditation process.
Patient Square does not claim NABH certification or a substitute for a specialist infection-control system. If workflow software is used for tasks or evidence, the hospital should define the boundary, permissions, record owner, export, and clinical approval path before implementation.