Evidence

Evidence is how an answer stops being an assertion. It can be a policy document, a training register, a photograph of a hand hygiene station, an audit record, or anything else showing that the indicator is genuinely met.

1. Open the indicator you want to support.
2. Upload the file. Record what it is and, where relevant, its date.
3. The evidence is listed as awaiting review.
4. A reviewer, somebody other than the person who uploaded it, verifies or rejects it.

What to upload, and what not to

Upload programme documents: policies, standard operating procedures, committee terms of reference and minutes, training records and attendance sheets, audit summaries, procurement and maintenance records.

Do not upload patient-identifiable information. IPC360 assesses an infection prevention and control programme, not patients, and it is not a clinical record system. A surveillance line list is the usual risk: if you need to evidence that surveillance happens, upload the summary report or the audit result rather than the line list itself.

Note: If a document you need to attach contains patient names, medical record numbers, bed numbers or dates of admission, remove or redact them before uploading.

Who can see it

Evidence carries the privacy of the assessment it substantiates. A file attached to your own private assessment is visible to you, and to a Super Administrator, and to nobody else at your hospital, exactly as the assessment itself is. Evidence that is not attached to any assessment is held as a hospital document and is visible to colleagues at your hospital.

Why verification is separate

The person who collects evidence must not be the person who attests to it. IPC360 enforces that separation, which is what makes “evidence verified” a meaningful figure on the report rather than a self-declaration.

Verification is carried out by a user holding the Evidence Reviewer role, which a Super Administrator grants for a named hospital. An ordinary doctor account cannot verify evidence, including its own.

Note: Evidence files are stored outside the web root and are only ever served through an authorising route. They are never sent to an AI provider.