Sample. Fictional data.

Sample record: a hospital room

This is one terminal clean in a hospital room, recorded the way CleanZ records it in a pilot. The room, the people and the readings are invented; the fields are the ones a pilot record holds. Each part has a note on why it is there and what an auditor reads in it.

Sample

Terminal clean, room 4-212

Sample hospital ยท

Verified to facility protocol v3

1 Room and time

Room
4-212, medical / surgical
Clean
Terminal clean after discharge
Isolation
C. difficile
Marked dirty
by S. Okafor, EVS supervisor
Started
by R. Alvarez, EVS technician
Approved
by S. Okafor

Why it's here

A surveyor asks for a room and a date. The record answers with both, and with who started and approved the clean. Isolation status is part of the room because it decides which protocol loads.

2 Protocol

Protocol
Terminal clean, C. difficile isolation
Version
v3, in force from
Loaded because
Room flagged for C. difficile
Requires
11 steps, 3 timed, 2 photos
PPE
Gown and gloves

Why it's here

Protocols change. The record names the version in force that night, so a March record is read against March's steps. Your facility writes the protocol; CleanZ runs the version you approved.

3 Products and contact times

Product
Sporicidal disinfectant (sample)
EPA Reg. No.
12345-678 (sample)
Contact time on each timed step
Timed stepRequiredTimedResult
High-touch surfaces4:004:00Met
Bed and rails4:004:00Met
Bathroom and fixtures4:004:00Met

Why it's here

The timer comes from your product library, so the contact time on screen is the one for the approved product in use. The record keeps whether each timed step ran its full time. The product name and EPA number here are samples.

4 Steps and photos

  1. PPE on, isolation signage checkeddone
  2. Waste and linen removeddone
  3. Privacy curtain changeddone
  4. High-touch surfaces wiped12 pointsdone
  5. Bed and railsdone
  6. Mattress checkedException, resolveddone
  7. Bathroom and fixturesPhotodone
  8. Equipment wipeddone
  9. Floor, edges indone
  10. Final walk-throughPhotodone
  11. Room released for reviewdone

Why it's here

One line per step, in your protocol's order. The cleaner saw the same steps, one per screen. Photos are of surfaces, and only where the protocol asks for one.

5 Exceptions

Logged
by R. Alvarez
Step
Mattress checked
Reason
Mattress cover torn at the foot. Can't complete as written.
Resolved
, mattress replaced, by S. Okafor

Why it's here

When something outside the cleaner's control blocks a step, the reason goes on the record instead of a skipped step. The problem is visible, and it is not on the cleaner.

6 Rules check

Required steps
11 of 11
Required photos
2 of 2
Contact times
3 of 3 timed steps met
Open exceptions
None
Result
Passed, submitted at

Why it's here

The room can't be submitted until every required item is there. The rules are your facility's settings, checked the same way every time. AI plays no part in pass or fail.

7 Review and rework

Returned
Sent back for rework at by S. Okafor
Reason
Bed rail, left side. This step needs another look: residue near the latch.
Re-cleaned
By R. Alvarez, contact time 4:00 met, photo attached. Resubmitted at .

Why it's here

A returned room keeps its first attempt, the reason it came back and the fix. An auditor wants failures kept, not only the final pass. The reason names the step, not the person.

8 Approval and seal

Approved
by S. Okafor, EVS supervisor
Status
Verified to facility protocol v3
Sealed
. Entries after this are added, never edited.

Why it's here

Approval seals the record. "Verified" always names the protocol it was verified against: it means your protocol was followed, and it makes no claim about the condition of a surface.

9 Spot test, added after approval

Added
by M. Chen, infection prevention

Fluorescent marker

Surfaces marked
5, before the clean
Marks removed
5 of 5
Result
Met the facility's acceptance criteria

ATP

Surface
Bed rail, left side
Reading
118 RLU, photo of the meter attached
Meter
Sample meter, model A
Threshold
250 RLU or lower, set by the facility for this model (sample value)
Result
Met the facility's acceptance criteria

Why it's here

Infection prevention runs spot tests on sampled rooms, not the cleaning team. Each result keeps its method, its device, the threshold that applied and who tested. CleanZ doesn't recommend thresholds; your facility sets one for each meter model.

How monitoring results are kept

10 Record history

  1. Room marked dirty S. Okafor, EVS supervisor
  2. Clean started, room tag scanned R. Alvarez, EVS technician
  3. Exception logged: mattress cover torn R. Alvarez
  4. Exception resolved: mattress replaced S. Okafor
  5. Rules check passed, room submitted R. Alvarez
  6. Returned for rework: bed rail, left side S. Okafor
  7. Re-cleaned and resubmitted R. Alvarez
  8. Approved, record sealed S. Okafor
  9. Spot test added M. Chen, infection prevention

Why it's here

Every entry has a time and a name, and nothing is written over. The history is how an auditor sees that the record was not tidied up after the fact.

Why a reading needs its meter

ATP readings in relative light units are not comparable across meter brands.

Different brands produce widely different log10 RLU values for the same fixed quantity of ATP, so an acceptance threshold belongs to one device model and cannot be carried across to another. Repeatability is also poor near the commonly quoted 100 RLU mark, and published cutoffs in the literature range from 100 to 500 RLU.

Source: Healthcare Infection (CSIRO Publishing), 2012

That is why the meter model and the facility's threshold sit beside every ATP reading. A number alone could not be checked later.

What the record does not say

The record shows that your protocol was followed and whether monitoring results met your acceptance criteria. It makes no claim about the condition of a surface. It holds nothing about the patient who was in the room.

What is built, and what is planned

Everything in this record is in the pilot release. These parts of it come later:

  • ATP file import Planned

    Planned: load a meter's exported result file instead of typing readings.

  • Meter photo reading Planned

    Planned: read the RLU value from a photo of the meter display.

  • EPA label lookup Planned

    Planned: pull contact times from the registered product label.

  • Trends Planned

    Planned: results over time by area, shift and surface.

See how one terminal clean becomes one record.

A person replies within one business day.