The ST108 workflow your hospital can actually operate.

AAMI ST108 created a concrete operational framework for water used in medical device processing. Caseore gives SPD, facilities, and infection prevention one shared workflow for the full compliance lifecycle.

AAMI ST108
Sterile processing technician illustration

Running a single ambulatory surgery center instead of a hospital SPD program?

Start with the ASC-specific ST108 pilot page if your immediate problem is getting one center survey-ready without hospital-scale tooling.

What Caseore manages for ST108 compliance

Your vendor may help manage water quality. You still need your own system of record for findings, actions, approvals, and closure.

Asset and water-system registry

Model washers, AERs, sterilizers, RO systems, and distribution loops with ST108 requirement linkage so you know which equipment depends on which water quality classification.

Scheduled checks and monitoring

Configure recurring checks for utility water, critical water, and steam with completion, deviation, and missed-check visibility per shift or schedule.

Deviation detection and case opening

When a check or sample fails, a compliance case opens with linked context: which system, which requirement, which threshold, and what equipment is affected.

Cross-functional coordination

SPD, facilities, infection prevention, and outside vendors work in one case thread instead of chasing service records across email or vendor portals.

Evidence capture

Service records, lab results, photos, validation documents, and approval signatures all attach to the case, not to separate binders or shared drives.

Remediation verification and closure

Verify corrective work with retest or re-inspection, then close with signoff and a complete audit-ready record of the deviation lifecycle.

How an ST108 deviation becomes a closed case

01

Scheduled check or sample

Routine water-quality check for a washer-disinfector, AER, or critical-water point reaches its scheduled time.

02

Deviation detected

Result falls outside configured performance criteria and is linked to the affected equipment and water classification.

03

Case opened with context

Compliance case is created with linked assets, applicable ST108 requirements, and the specific threshold breached.

04

Team tasks assigned

SPD investigates process impact, facilities addresses the water system, infection prevention reviews risk, and vendors are pulled in as needed.

05

Evidence collected

Service reports, lab results, photos, internal notes, and vendor documentation are attached to the same case record.

06

Remediation verified

Follow-up testing or inspection confirms the issue is resolved and verification evidence is attached.

07

Closed with signoff

Authorized review closes the case with a complete evidence packet for survey, audit, or internal review.

Questions we ask in every first conversation

Who currently owns ST108 readiness across SPD, facilities, and infection prevention?
Are water checks, lab results, service records, and remediation actions stored in one system or several?
If a water-quality issue affects a washer, AER, or sterile-processing workflow, how is that tracked end to end?
Are you relying on a vendor portal, binders, shared drives, or email to show compliance?
Can leadership quickly see what is open, overdue, or repeated across sites?
Do you have a clean distinction today between monitoring data and the case record for responding to an exception?

What we hear and how we respond

Our water-treatment vendor already helps with this.
That may be true, but many hospitals still need their own system of record for findings, internal approvals, cross-team tasks, and closure.
This sounds like facilities software.
Only partly. ST108 sits across SPD operations, infection prevention, and facilities. The problem is not only equipment maintenance, it is documenting the full compliance case when water quality or process requirements are not met.
We already have tickets for maintenance.
Maintenance tickets do not usually capture the full compliance narrative: what requirement applied, what evidence was attached, who reviewed the deviation, what retest confirmed closure, and what signoff was obtained.
We are still early in ST108 adoption.
That is exactly why a lightweight workflow helps. Start with readiness, exceptions, and documentation before the process sprawls into binders and disconnected spreadsheets.

One hospital. One department. 60-90 days.

Pilot includes asset and system registry, scheduled checks, deviations, document capture, and remediation workflow for one hospital or flagship SPD site.

Scope
1 hospital site
Timeline
60-90 days
Focus
Deviation workflow

What to expect

1

Discovery call

We learn about your program, current workflow, and the specific compliance pain you want to fix.

2

Tailored walkthrough

We show the Caseore workflow that fits your environment instead of a generic feature tour.

3

Pilot scope

If there is a fit, we outline the rollout, timeline, and the workflow we would stand up first.

Request a demo

We respond within one business day. A real person reads every request.