Platform Partnerships — CicadenceCicadence integrates with the tools specialty pharmacy and clinical care teams already use. Review our partner ecosystem, BAA program, and open API for technology partners.Cicadence has built the operational layer — real-time queue intelligence, RBAC, tenant isolation, audit logging, and a public REST + webhook API. We are seeking EHR/EMR vendors, specialty-pharmacy platforms, and BAA-eligible cloud partners so REMS Operations and Cicadence can ship inside a covered environment.The Integration StoryCicadence is designed to sit inside your existing workflows, not replace them.Your PHI InfrastructureYou own the patient data, the BAA, and the certified hosting layer. Cicadence consumes de-identified or PHI-handled queue signals from your platform.Cicadence Operational LayerWe handle real-time queue intelligence, staff-assignment math, RBAC, audit logging, and tenant isolation. Your clinics see live staffing recommendations.What We NeedA BAA, sandbox EHR/EMR or specialty-pharmacy access to validate the integration, and a technical contact for a 30-minute scoping call.Integration Work in ProgressPre-launch healthcare software earns trust with honest sequencing, not fabricated logos. Here are the integration categories we are actively building against and the partner shapes we are looking for. Nothing on this list is signed; everything is labeled.Specialty Pharmacy Operations (In Active Development)Inbound webhook and CSV/API ingestion patterns to receive prior-authorization queue volume from a specialty pharmacy stack so Cicadence can staff to actual PA backlog rather than an average. Designed to ingest data from dispensing and PA systems like CareTend, PioneerRx, and CoverMyMeds; named vendor connectors are roadmap items, and no commercial relationship with these vendors exists today.Electronic Health Records (Target Partner)Read patient queue and procedure-volume signals from an EHR sandbox to validate the integration end-to-end before any pilot. Designed against the FHIR R4 surface used by Epic and other major EMRs; we need a sandbox tenant from a participating EHR vendor to qualify the pattern. This is a roadmap target, not an existing integration.CRM and Patient Services (Target Partner)Ingest case and enrollment queue volume from CRM-driven hub services workflows via the public REST API and inbound webhooks. Teams running on platforms like Salesforce can push queue counts today using the documented API patterns; a named connector is a roadmap item.HRIS and Workforce (In Active Development)Inbound employee status update webhook to keep Cicadence employee records in sync with the source of truth for hires, role changes, and terminations. Designed against the common HRIS webhook shape; no specific HRIS vendor is integrated yet.Identity and SSO (In Active Development)Replit's OIDC layer is live alongside the username/password flow. SAML and enterprise IdP integrations are scoped to land once a pilot tenant requires them.BAA-Eligible Cloud Hosting (Target Partner)Cicadence cannot self-certify HIPAA. We are seeking a BAA-eligible hosting partner so the operational layer can run inside a covered environment.Public REST API and WebSocketBearer-token authentication, scoped API keys, and real-time queue volume updates via WebSocket. See the API documentation for the full reference.Queue Management APIRead backlog state and push real-time volume updates. Volume changes are broadcast to connected dashboards over WebSocket.Employee Lifecycle APIProvision, update role and skills, and deactivate employees. Designed to be driven from an HRIS.Locations and Assignments APIMap staff to queues at specific locations. Drive live staffing adjustments from an external scheduling system.WebhooksSend and receive events to keep EHRs, POS systems, or pharmacy platforms in sync in real time.Integration Status MatrixWhat actually works today versus what is on the roadmap. If it says Available, you can build on it now; if it says Roadmap, it does not exist yet.

Public REST API — Available. Queues, employees, locations, assignments, dashboard stats. Bearer-token auth with scoped, rate-limited API keys.

Inbound webhooks — Available. POST /api/v1/webhooks/incoming for queue volume, employee status, assignment, and shift events from your systems.

Outbound webhooks — Available. Event subscriptions fired when queues, employees, and assignments change.

Real-time WebSocket updates — Available. Queue volume changes broadcast instantly to connected dashboards.

Middleware script push (API ingestion pattern) — Available. Your script counts rows per work queue and pushes to the REST API on a schedule. Documented pattern with sample code.

Manual queue entry — Available. Shift leads update queue counts in the UI. Day-one capability, no integration required.

OIDC login — Available. OIDC sign-in is live alongside username/password.

Scheduled report drop (CSV / SFTP / mailbox) — Beta. Your reporting tool drops a per-queue-count CSV; Cicadence watches the destination. Configured with each customer during onboarding.

Named pharmacy connectors (CareTend, PioneerRx, etc.) — Roadmap. Turnkey vendor connectors. Today these systems feed Cicadence via the CSV/API ingestion patterns above.

EHR connectors (Epic, Cerner / Oracle Health, etc.) — Roadmap. FHIR R4-based connectors, pending sandbox access from a participating vendor.

CRM / hub-services connectors (e.g. Salesforce) — Roadmap. Named connector for CRM-driven queue volume. The REST API pattern works today.

HRIS connectors — Roadmap. Turnkey employee sync with a named HRIS vendor. The inbound employee.status_update webhook works today.

SAML / enterprise SSO — Roadmap. Scoped to land when a pilot tenant requires it.

What Is Already Shipped

Role-based access control — distinct roles, enforced server-side on every request

Tenant isolation — tenant data isolated per organization, enforced at the storage layer

Encryption at rest — REMS Operations clinical notes are encrypted before persistence

Audit logging — actor-attributed logs on sensitive actions

Scoped API keys — fine-grained permission scopes per integration key, rate-limited per key

Rate limiting — authentication and API endpoints are rate-limited in production

Securely hashed passwords — passwords are securely hashed and salted; plain text is never stored

Security response headers — hardening headers configured across the application

Real-time WebSocket — queue volume changes broadcast instantly to connected dashboards

TOTP MFA — authenticator-app MFA available on every account

Documented threat model — security reviewed against a documented threat model

Automated isolation tests — automated tests verify the tenant-isolation contract on every run

Our Partnership AskWe are not asking for a marketing slot. We are asking for three things: (1) a BAA with an eligible partner so REMS Operations can handle PHI within your platform's certified environment; (2) API or EHR sandbox access to test the integration end-to-end before a joint pilot; (3) a platform partnerships or technical integration lead for a 30-minute scoping call.Contact us at hello@cicadence.com or request a demo. Review our security and HIPAA-readiness documentation or see the full API reference.A note on logos and names: the categories above describe integration shapes, the platform standards we are building against, and the partner profile we are looking for — not signed relationships. Where a third-party product is named, it describes a compatibility pattern or roadmap target only. All third-party names are trademarks of their respective owners; no partnership or endorsement is implied.