Post-flush clean is well understood by every endoscopy reprocessing team. What is less consistently established is whether it’s being captured within your traceability systems, and whether its absence is something auditors are beginning to treat as a compliance gap.

The compliance conversation that’s starting to emerge

For most endoscopy reprocessing units, the traceability system captures the decontamination workflow from dirty returns onwards. Receipt into the unit starts the production timer, manual wash is recorded, EWD cycle data is logged, and storage or dispatch is confirmed. That record is comprehensive from the unit door inward.

Post-flush clean, however, is often either recorded on a paper form or not formally captured at all. It exists outside the traceability system because most implementations begin at the point of receipt into the reprocessing unit.

The question inspections like JAG are beginning to surface is whether that structural gap is acceptable. Post-flush clean is not a preparatory step that precedes decontamination in any meaningful regulatory sense, but rather, it’s the first step of decontamination.

Departments that cannot demonstrate from their traceability record that the flush was performed, by whom, and at what time, are finding that absence noted.

At Medway Maritime Hospital, Christopher Eden’s team manages a workflow where the expectation of capacity is constant and the margin for compliance gaps is essentially 0. The rigour that characterises that team’s approach to every stage of the decontamination cycle is precisely what makes this question relevant, because if post-flush clean is not in the system, the complete record the department relies on is incomplete before the scope has arrived at the unit door.

Should post-flush clean be a mandatory scan?

The practical question that follows from the compliance argument is whether post-flush clean should be configured as a mandatory scan within the traceability system… one that prevents the scope from proceeding through the reprocessing workflow until flush completion has been confirmed.

The case for doing so is straightforward in that a mandatory scan creates an enforceable process rather than a recommended one. It closes the gap between what the guidance requires and what the record can demonstrate. And it removes the dependency on paper forms in the treatment room that sit outside the digital system and cannot be cross-referenced with the scope’s decontamination history.

Treatment rooms operate differently from reprocessing units, and capturing a bedside scan at the point of flush requires a device, a workflow, and a staff training process that extends beyond the reprocessing team itself.

For departments considering this, the starting point is understanding what currently happens in the treatment room after a procedure ends, and where in that process a scan could realistically be embedded without disrupting clinical workflow.

Procedure type and the reprocessing pathway

Closely related to the post-flush question is whether procedure type is being captured at the point of scope use and connected to the decontamination record. A scope used in one procedure carries different reprocessing considerations from one used in a another procedure, and in critical or semi-critical cases the question of whether sterilisation should be part of the pathway is one that the reprocessing team needs to be informed of.

In departments where procedure type is not being captured within the traceability system, that information exists in the clinical record but is disconnected from the decontamination record. The reprocessing team processes the scope according to its standard pathway without visibility of the clinical context in which it was used…

Where integration between the traceability system and the EPR or patient administration system exists, that gap closes, and the procedure type is retrievable from the clinical record and available to the reprocessing team at the point of receipt.

Where integration is not yet in place, the question of how procedure type is currently communicated to the reprocessing unit is worth examining. If the answer is verbal handover or paper documentation, the reliability of that communication under pressure is a risk worth understanding.

Questions for your department

Is post-flush clean being captured within your traceability system, or does it sit outside it on a paper form in the treatment room, or not formally recorded at all? If it is outside the system, it is worth considering whether that constitutes a compliance gap before an auditor raises it first.

Has post-flush clean been referenced in a recent inspection? If it has, configuring it as a mandatory scan is a practical and achievable response that closes the gap at the process level rather than the documentation level.

Is procedure type being captured at the point of scope use and connected to the decontamination record? If not, the link between clinical use and reprocessing pathway is absent from the complete picture — and in the event of a patient safety investigation, that absence is significant.