toxiCALL® Application Specifications
The specifications below are general guidelines for toxiCALL® 5 deployments. Actual requirements will vary based on case volume, database size, number of concurrent specialists, network architecture, integrations, and other site-specific factors.
Database Server
| Component | Minimum | Recommended |
| Processor | 2.0 GHz or higher | Modern multicore 3.0 GHz or higher |
| Memory | 32 GB RAM | 64 GB RAM or higher |
| Storage | Sufficient space for Windows, SQL Server, database, backups, and growth | Sized according to current database size, backup retention, and anticipated growth |
| Operating System | Windows Server 2019 or later | A currently Microsoft-supported Windows Server release compatible with the selected SQL Server version |
The following SQL Server guidance applies to both toxiCALL® 4 and toxiCALL® 5.
| Item | Minimum | Recommended / Supported |
| SQL Server Version | SQL Server 2019 | SQL Server 2019 or later, including SQL Server 2022 and SQL Server 2025 |
| Edition | SQL Server Express* | SQL Server Standard or Enterprise for production environments |
| Database Compatibility Level | No special toxiCALL-specific compatibility level is required | Use the compatibility level appropriate for the installed SQL Server version and your organization’s database standards |
| Connectivity | Standard Microsoft SQL Server connectivity | TCP/IP recommended |
| Encryption | TLS 1.2 supported | Use current Microsoft-supported security settings appropriate for your environment |
* SQL Server Express can be appropriate for smaller databases and limited workloads, but Microsoft-imposed Express edition resource and database-size limitations should be considered when selecting an edition.
SQL Server Features and Services
toxiCALL® uses standard Microsoft SQL Server database functionality and standard T-SQL. It does not require SQL Server Reporting Services (SSRS), Analysis Services (SSAS), Integration Services (SSIS), or other optional SQL Server services for normal application operation.
No proprietary database engine, external database service, or specialized SQL Server feature set is required. Standard SQL Server database administration, backup, recovery, and maintenance practices may be used.
SQL Connectivity, Authentication, and Network Configuration
toxiCALL® uses standard Microsoft SQL Server connectivity. A separately managed third-party SQL database driver is not required for normal operation.
toxiCALL® supports both Windows Authentication and SQL Server Authentication. The authentication method can be configured at the workstation level, allowing organizations to use the approach that best fits their SQL Server security policies.
- TCP/IP should be enabled for the SQL Server instance.
- The SQL Server instance must be reachable from toxiCALL® workstations or application servers.
- Required SQL Server ports must be permitted through applicable firewalls.
- Named Pipes may be enabled if required by the organization’s SQL configuration, but it is not a toxiCALL®-specific requirement.
toxiCALL® 5 Client Workstation
| Component | Minimum | Recommended |
| Processor | 1.4 GHz or higher | Modern multicore 2.5 GHz or higher |
| Memory | 8 GB RAM | 16 GB RAM or higher |
| Storage | 256 GB available storage | 512 GB or greater |
| Operating System | Windows 10 or later | Windows 11 or a currently Microsoft-supported Windows desktop release |
| .NET | .NET 10 | Current CAS-supported .NET 10 servicing release |
toxiWEB® IIS Server Specifications
| Component | Minimum | Recommended |
| IIS | IIS 10 | Current Microsoft-supported IIS release |
| Processor | 2.0 GHz or higher | Modern multicore 3.0 GHz or higher |
| Memory | 8 GB RAM | 16 GB RAM or higher |
| Storage | 256 GB available storage | 512 GB or greater, based on usage |
| Operating System | Windows Server 2019 or later | A currently Microsoft-supported Windows Server release |
| .NET Hosting Bundle | Current CAS-supported version | Current CAS-supported version |
toxiWEB® Browser-Based Client
toxiWEB® is designed for modern web browsers. Browser and platform support continues to expand as the product is developed and validated.
For production deployments, CAS will provide current browser and platform guidance appropriate to the installed toxiWEB® release.
Performance Optimization
Application performance is influenced primarily by workstation processing speed and network performance.
- Workstation performance: Faster modern processors can significantly improve case load and application response times.
- Network performance: Low bandwidth, high latency, VPN connections, and wide-area network connections can increase case load, save, upload, and download times.
Remote toxiCALL® 5 installation performance depends on the quality of the connection between the specialist workstation and the central SQL Server. Low bandwidth, slower network speeds—including upload speed—high latency, VPN overhead, connection variability, and local or home network conditions can all affect case load, save, upload, and download times.
A high advertised Internet download speed alone does not necessarily indicate how well a database application will perform remotely. Upload capacity, latency, connection stability, Wi-Fi quality, and other local network conditions can also be important.
For optimal remote performance with toxiCALL® 5, poison centers should consider a virtual desktop, hosted desktop, or similar solution that keeps the toxiCALL® application and SQL Server database together on a low-latency network. This minimizes the amount of database communication that must travel across the specialist’s remote connection.
toxiWEB® provides another powerful remote-access option as an add-on to toxiCALL® 5. toxiWEB® complements toxiCALL® 5 by providing browser-based access while sharing many of the features and workflows available in toxiCALL® 5. It is not intended to replace toxiCALL® 5; rather, it extends the overall solution with browser-based capabilities while toxiCALL® 5 remains available for functions and workflows not yet included in toxiWEB®.
For poison centers using toxiCALL® 5 directly over remote, lower-bandwidth, slower, or less consistent network connections, toxiCALL® 5 also includes features designed to improve responsiveness and allow specialists to return to case-entry work more quickly:
- Local Database: A Local Database can be used on the workstation so case entry and local saves occur locally rather than waiting on each transaction to complete across the connection to the central SQL Server. This can significantly improve case-entry and save performance in remote environments.
- Background Upload and Download: Case transfers between the Local Database and Network Database can continue in the background, allowing specialists to return to case-entry work while synchronization completes.
- Network Case Preview: When a network case has not been downloaded to the Local Database, specialists can preview the case and enter notes without waiting for the complete case to download. This provides quicker access to important case information when network performance is limited.
Together, these options give poison centers flexibility to support remote specialists using the architecture that best fits their infrastructure, workflow, and budget.
Database Migration / Server Replacement
toxiCALL® does not require a proprietary database migration process when moving an existing database to a replacement SQL Server.
A typical migration can be performed using standard Microsoft SQL Server administration procedures:
- Back up the existing toxiCALL® database using SQL Server tools.
- Restore or migrate the database to the replacement SQL Server instance using the organization’s normal DBA procedures.
- Re-create or transfer required SQL logins, users, and database permissions as appropriate.
- Verify the database is online and accessible from the new SQL Server instance.
- Update the toxiCALL® database connection configuration to reference the replacement server or instance.
- Test connectivity and normal application operation before retiring the previous SQL Server.
For major environment changes, CAS recommends retaining a recoverable backup of the existing database and validating the migrated database before the prior server is decommissioned.
A SQL Server change will cause the toxiCALL® license to enter Emergency Mode because the licensed server environment has changed. Emergency Mode is designed to allow specialists to continue capturing cases after an environment change while the license is refreshed. A new license request should be submitted to CAS following the server migration. Some secondary applications or automated services may have limited functionality until the refreshed license is applied.
License Request Instructions:
General Notes
All specifications are guidelines and may change as toxiCALL® and toxiWEB® continue to evolve. Actual requirements can vary significantly based on database size, case volume, concurrent specialists, integrations, reporting requirements, network conditions, and client-specific data collection.
Database storage requirements should be planned with sufficient capacity for database growth, backups, maintenance operations, and retention requirements. toxiCALL® 5 may store additional data compared with a comparable toxiCALL® 4 implementation.