Bring a small, consistent test pack
Prepare fictitious HCFs, several collection events, a duplicate upload, a receipt difference and one rejected submission. Ask the supplier to show each item through the relevant workflow. Use anonymized or sample records so a demonstration does not disclose patient, employee or customer information. Score observed behavior rather than promises about future releases.
Test offline work and permissions
Disconnect a collection device, capture sample events, reconnect it and inspect the resulting server records. Check whether staff can see pending and failed uploads. Test what happens if the device clock is wrong. Ask a restricted user to edit a closed record, export data and reprint a label. The system should apply the permissions you agreed and record authorized changes.
Examine integration and exit options
Ask for the applicable integration specification, onboarding requirements and a demonstration of acknowledgement handling. Separate successful transmission from acceptance by the receiving system. Request an export containing identifiers, event history and attachments where relevant. Ask how you would retrieve data at contract end and how much assistance costs.
Compare the whole operating cost
Include implementation, migration, devices, printing, connectivity, training, renewals, support and future changes. Record which party owns each dependency. Seek written acceptance criteria and response arrangements before committing. This site is published by e-Planet, developer of CBWTF SmartCare; the checklist is an evaluation aid, not an independent vendor ranking.
Take this to your team review
A working prompt, not a compliance score. Selections last only while this page is open.
Have a correction or a question about this workflow? Contact the publisher.