SMORES HEALTH. COMMUNITY HEALTH WORKER SOFTWARE SCORECARD
Reviewed October 9, 2026

Smores Health publishes this buyer worksheet. Apply the same evidence standards to all vendors. Scores are planning aids, not independent ratings. Use fictional data in demonstrations.

Organization and service model:
Decision owner and evaluators:
Team size, programs, locations:
Problem to solve:
Critical requirements that cannot be averaged away:

REQUIREMENT CARD (COPY FOR EACH REQUIREMENT)
Requirement and why it matters:
Acceptance scenario:
Vendor:
Evidence shown:
Configuration or workaround:
Unresolved question and owner:
Score: 0 not demonstrated; 1 workaround; 2 agreed configuration; 3 directly demonstrated.
Critical requirement decision: met / unresolved / not met.

SCENARIOS
[ ] Create a fictional referral and handle duplicate information.
[ ] Assign support and cover a worker absence.
[ ] Record an encounter and follow the correction process.
[ ] Keep referral sent and service received distinct.
[ ] Reconcile a report total to underlying records.
[ ] Demonstrate staff roles and access restrictions.
[ ] Complete everyday work on actual staff devices.
[ ] Explain interrupted work and connectivity limits.
[ ] Export usable example records and related information.

COSTS
Subscription, included roles/modules, and limits:
Setup and migration:
Training and ongoing support:
Interfaces, usage, and storage:
Configuration changes:
Exit/export costs:
First-year total and assumptions:
Renewal total and assumptions:

IMPLEMENTATION
Owners:
Data mapping and cleanup:
Pilot scope:
Acceptance checks:
Training:
Open dependencies:
Written commitments to confirm:
Decision and rationale:

Guide: https://smoreshealth.com/peer-support-software/choose-community-health-worker-software
Demo: https://cal.com/team/smoreshealth/demo