How we stand up a facility pilot — the repeatable engine.
The operational process from signed agreement to live-on-the-floor. Built from real implementations. The facility spends about one hour; we do the heavy lifting over the prior one to two weeks.
Phase 1 · Off-Site
Prep · ~1–2 Weeks
Agreements, info, room, workflow build & custom-workflow activation — all done before we arrive.
→
Phase 2 · On-Site
Go-Live · ~1 Hour
Tablets in hand, 30 min with key people, in-service, lunch — live before we leave.
Say It Honestly: "about an hour of your team's time." The one hour is the on-site go-live. The prep (1–2 weeks) is our work, off-site — never quote "one hour total."
Phase 1Prep · Off-Site · ~1–2 Weeks
Everything Is Built and Signed Before We Show Up.
By the time we arrive with tablets, the agreements are signed, the workflows are configured, and the facility's custom processes are operationalized and validated. Nothing is figured out on-site.
Agreements Signed
Pilot agreement + data terms executed. Nothing configured until signed.
CC
Facility Info Gathered
Department structure, stations, equipment, current process, IFUs in use.
CC + Facility
Workflow Selection — "We Pick with You"
Collaborative, adapted to the facility. Endoscopy-heavy → lead with HLD; general SPD → wet pack / BI / load release. Not a fixed menu.
CC + Facility
Success Measure Agreed & Baselined
What "working" looks like, set before go-live, with a starting baseline to compare against at day 90.
CC + Facility
Who's in the Room
Supervisor / EducatorInterchangeable — the process authority. One of the two, whoever owns SOP.
TechnicianThe floor-level user. Confirms the workflow matches how the work actually happens.
ManagerTypically the champion. The one driving it internally.
ProcurementPull them in early — even at $3,500 + $500, free for 90 days. Getting them involved now makes the paid go-live a frictionless transition later, not a new sale.
Infection PreventionNot required by default. Include only if the facility routes it there.
Internal operational playbook · not for external distribution. ClarityComply — Implementation.
1 / 3
CC
ClarityComply
Internal · Operational Playbook
The Core Loop · Phase 1
Custom Workflow Intake & Activation
Every facility asks the same thing: "can you add our process?" The answer is always yes — because that is the engine. This is the loop that turns a facility's required process into a live, guided workflow that's theirs.
Required Workflow → Accessible Workflow → In the System for That Facility
They Don't Build It. They Submit It — We Operationalize, Validate, and Activate.
The facility can't (and shouldn't) build a guided clinical workflow. They submit the process they need; we make it real.
01 · Facility
Submit
The facility submits the workflow they need + the IFU / steps / parties involved (e.g. notify educator for sign-off).
02 · CC
Operationalize
We embed the submitted IFU and steps into a guided workflow — gates, approvals, record.
03 · CC
Validate
Confirmed against the standard and the facility's IFU before it can guide any decision. Required safety checkpoint.
04 · CC
Activate
The workflow goes live for that customer — now part of their configured system.
Validation Is Non-Negotiable: a submitted workflow guides clinical decisions the moment it's active, so it is validated against the standard / IFU before activation — never auto-activated on submission. This is rigor the buyer should hear about, not friction to hide.
Phase 2Go-Live · On-Site · ~1 Hour
Show Up with Tablets in Hand. Live Before We Leave.
Everything's built. This is handoff, training, and lunch — the facility's ~1 hour.
0:00
Hand Off the Tablets
Physical tablets in hand, configured to their workflows. Token session — no account, no password, no PHI.
0:00–0:30
30 Minutes with Key Individuals
Supervisor/educator + tech + champion. Walk the configured workflows, confirm the custom ones, set expectations.
0:30–1:00
In-Service the Department + Lunch
Train the floor so adoption isn't left to two people. Lunch on us — the department is trained and running before we leave.
The Workflow Set
Event ×2
Wet Pack · BI Positive
ST79 · prove value in the high-stakes moments
Recurring
Water Quality · ST108
the weekly touch — mandated, so it never goes idle
Custom
Facility's Submitted Workflow(s)
operationalized + validated + activated (the engine loop)
Optional +1
Second Recurring (e.g. Load Release)
chosen with the team if they want a second weekly touch
Water: CC schedules / gates / guides / trends — the lab or probe measures; ST108 action levels are facility-set & validated. ClarityComply — Implementation.
2 / 3
CC
ClarityComply
Internal · Operational Playbook
First 90 Days & Deployment
Keep It in Use, Prove the Measure, Pre-Wire the Paid Go-Live.
90 DaysRun · Convert
Weekly touch is built in. The recurring water-quality workflow guarantees the product is used every cycle — the pilot can't quietly go idle.
Measure against the baseline. Check the agreed success measure at intervals — exceptions caught, records generated, completion — so the day-90 conversation is a review of results, not a cold sell.
Procurement is already warm. Because they were in the room in Phase 1, the paid go-live ($3,500 + $500/mo) is a transition, not a new procurement cycle.
Decision at pilot end. Continue on a paid tier or walk clean. No obligation, no auto-renew.
What They Receive · Deployment
The Configured System, Not a Login.
Station Tablet(s)
Configured to their workflows. Token session — no account, no password, no PHI. Scan in, get guided, record captures itself.
Department View
Desktop oversight for the supervisor/educator — open workflows, records, the team roll-up, in real time.
Their Workflow Set
The event pair + water quality + their validated custom workflows — guided to their IFU and AAMI ST79 / ST91 / ST108.
Field-informed: Mercy West · Mercy Anderson · UC Health. ClarityComply — Implementation Playbook · Internal.