Start the CSSD demonstration with the answer, not the intake screen. Mark one synthetic process record for review and ask: which sets and items are affected, where are they now, and what evidence supports each link?
Then walk every result backward. A recall is the shortest route to the gaps.
Takeaways
- Begin with a recall result and prove every link backward.
- Keep process evidence separate from authorised release.
- Challenge identity, custody, and time at each joint in the trace.
- Reconcile physical location and system state after downtime.
This is a software-procurement test, not infection-prevention, device-reprocessing, clinical, accreditation, or engineering advice. Qualified hospital owners define and validate the process.
Ask for the recall result first
The WHO publication on decontamination and reprocessing of medical devices provides technical guidance for health-care facilities. It is a source for qualified programme owners, not a configuration recipe for a blog or software vendor.
Choose a synthetic process record and mark it for review. Ask the system to identify every linked set, item, storage point, issue, destination, and current state. The output should show source identifiers and event times, not only a list of names.
Record contact attempts, recovery, hold, assessment ownership, and closure evidence. Do not grade by the size of the search result. Grade whether each result can be explained from retained events.
Walk every result backward
Start with one result at its stated location. Trace it backward through the controlled states defined by the hospital’s owners:
CURRENT LOCATION AND STATE
<- issue and destination acceptance
<- storage placement
<- authorised release or hold decision
<- approved cycle evidence association
<- assembly and count
<- processing-stage events
<- receipt, source, identifier, and initial count
At each link, require time, actor, identifier, source, destination, and reason. The software should not invent a successful state when an interface is unavailable.
Break one joint at a time
Create a synthetic set containing ten numbered items. Then run these cases:
- receive nine items and one item with an unreadable mark;
- scan a label that belongs to a different set;
- find the missing item after assembly has started;
- replace one item with an approved substitute;
- split the set for repair and later reunion;
- attempt to issue a set that remains on hold.
Ask how an authorised person resolves each exception and whether the original evidence survives. A corrected count should not erase the mismatch that triggered review.
Stop at the release decision
An integrated system may receive equipment or cycle data. That data is evidence, not a final clinical or technical conclusion by itself. The hospital defines which parameters and checks matter, how exceptions are assessed, and who can release or hold a load.
During the demo, supply one complete synthetic cycle record, one incomplete record, and one record attached to the wrong load. The software should prevent silent association and expose the correction trail. Ask what happens if the equipment clock and application clock disagree.
IISc’s 2026 turnkey CSSD request for quotation includes instrument tracking and data-management software in its stated project scope. That is evidence from one procurement, not a universal specification or endorsement.
Prove the destination and return links
Issue a synthetic set to an invented theatre case. Return it once unopened and once with a recorded missing item. Compare the CSSD state with the theatre record and physical location. If the systems disagree, require an owned exception rather than automatic overwrite.
The operation-theatre software demo tests the receiving lane. Neither module should claim the other’s professional decision.
Compare the software result with a physical-location list prepared for the synthetic test. A mismatch needs an owned exception, not an automatic overwrite. ESIC’s 2025 hospital SOPs describe CSSD staff duties including records, stock, equipment issues, and prescribed registers in that system’s setting. Local owners must map current requirements for their hospital.
Reconcile a downtime trolley
Move two synthetic sets while the application is unavailable. Give each temporary record a unique source, time, custodian, and destination. After restoration, enter the events in original order, detect a duplicate scan, and compare the application with the physical trolley.
Score identity, custody, exception visibility, release separation, recall trace, and reconciliation. A fast scan with a broken chain is not a pass.
Patient Square does not publish a standalone CSSD module. Do not infer instrument-level tracking, barcode or RFID support, equipment integration, cycle validation, labelling, recall, or maintenance from Hospital Copilot. Put every required function, interface, device, acceptance case, and evidence export into the quoted scope.