Queue counts come in from the systems you already run. Cicadence turns them into staffing answers. Dashboards, alerts, and reports come out — all isolated per organization and secured end to end.
Four ways to feed queue volume into Cicadence: scheduled CSV report drops from your existing reporting tools, a small script pushing counts to the public REST API, inbound webhooks from external systems, or manual entry by a shift lead. For the core queue use case, only aggregate counts per work queue leave your environment — no patient or customer records are required.
The staffing engine calculates how many people each queue actually needs from live volume and target throughput. AI predictions forecast upcoming queue volume and suggest schedules. Fatigue monitoring tracks consecutive shifts and workload to flag burnout risk early.
Live dashboards updated in real time over WebSockets, alerts for staffing gaps and credential expirations, reports and analytics with one-click exports, and signed outbound webhooks back to your systems.
Tenant isolation scopes every read and write to your organization on the server. Traffic is protected with TLS and sensitive data is encrypted at rest with AES-256. Role-based access control and multi-factor authentication govern who can do what, and API keys carry narrow scopes with rate limits. Sensitive actions are audit logged with who did what and when.