Overview #
APC Notification and Availability
The Association Board passed a motion to add three new Therapies and a new substance formulation. These additions will be effective on January 1, 2026. The announcement indicated “these changes will be available in BETA for testing by November 15th and in Production by December 15th.”
The changes are currently available for toxiCALL® and can be implemented as soon as you are ready.
This documentation page also includes the updates to Generic Codes and TDA Definitions. These definitions can be updated separately, as long as you do not update all system tables.
toxiCALL® Requirement
Please ensure IT Support assistance is available to ensure all steps can be completed.
The new changes will be available through the system tables with a database update, as performed in 2025. However, the addition of the new substance formulation requires an upgrade to toxiCALL® 4 released as version 4.7.45 or later. The formulation can still be used in current versions; however, you won’t be able to close the case until upgrading.
toxiCALL® 4.7.40 will work with the new system tables and therapies. However, you will not be able to save a case with the Closed status due to the validation rules. This validation error is corrected with the latest version of toxiCALL® 4.
toxiCALL® 5 users can receive the update through System Tables. Data table scripts and version changes are not required for these updates.
This document outlines the new data elements required for compliance with NPDS data submission. Understanding the order of implementation is crucial, as it can lead to errors. The System Table release for FieldCodeValue should be performed last to ensure no errors in saving case information.
Estimated Time
The estimated time for this process is 60 to 90 minutes. The system table updates are quick. The most time-consuming process may be updating all the local databases.
Users can continue to work within toxiCALL® during this process. Once the user restarts toxiCALL®, they will receive the new system tables and can begin using the new therapy. If you are using ByPass local mode, you can delay the update of the local database.
Please feel free to schedule a time with our support team if you would like assistance through this process.
Checklist #
- Update the Generic Codes
- Low impact, can be done anytime.
- Update RADARS Definitions
- Low impact, can be done anytime.
- Therapy Update for two new Antivenom and Honey
- Moderate impact requires an update to the local database on all workstations.
- Update or Copy Local Database
- Moderate Impact will distribute an updated local database for each user.
- Update the System Tables
- Low impact must be achieved after step 3, Therapy Update.
Generic Codes and RADARS Update #
Release Anytime
The following will update the Generic Codes and RADARS Definitions. This can be released without the Therapies and Substance Formulation Update.
- Generic Tables
- TCN_Definitions
- SearchList Tables
Generic Codes and RADARS ONLY
Warning: Do not update all the System Tables until instructed to do so below. Updating the FieldCodeValue and SearchViewList tables prematurely will cause errors in toxiCALL®.
One new generic code has been added, and one has been retired.
Click here for details on the generic code release. To access toxiCALL® and the discussion forums, you need a username and password.
Click here for more details in the toxiCALL® discussion forums.
Only update the Generic Codes during this step.
Updating other system tables prematurely may cause problems.
Ensure the Generic Tables indicate “Updated” status when complete.
File Downloads #
The latest toxiCALL® 4 files can be downloaded by clicking here. There are two new files of importance for this NPDS update.
Toxicall.exe #
The file Toxicall.exe is intended as a patch replacement for the existing Toxicall.exe file. This version is v4.7.45 and will allow the new substance formulation to pass validation. Without this update, you will still be able to code a case with the new Gummy formulation, but it just won’t pass validation. Cases with Gummy formulation cannot be closed until the new Toxicall.exe file is in place.
DB_Update_NPDS2026.sql #
The file DB_Update_NPDS2026.sql contains the script used to update the Network, Local, and Archive database structures.
Therapy Update #
NPDS has introduced two new antivenoms and one honey therapy. These new therapies are easily added to toxiCALL® 4. We are excited to announce that toxiCALL® 4 has been designed to support additional therapies without requiring an application update. The following steps will outline how a simple data structure and System Table Update enable toxiCALL® to capture the new Therapy. It is also important to note that AutoUpload has been designed to automatically accommodate this change without needing a special version update.
toxiCALL® 5 and Therapies
toxiCALL® 5 has been designed to simplify this process even further! The data model update requirement has been removed, allowing Therapies, Clinical Effects, Routes, and Scenarios to be updated with only a System Table update.
To properly implement the change, a toxiCALL® supervisor will run an SQL Script against the Network database and all archive databases. The script can also be run against the local database if cases exist.
Therapies Search Tab #
The toxiCALL® 4 Therapies search tab is limited to the current number of therapies. As a result, the new therapies are included in the tab “8) Outcome / Scenario” as shown in the image.
All toxiCALL 4 File Downloads #
We have centralized all of the toxiCALL® 4 file downloads. Click here to access the latest download page.
SQL and MS Access Update Script #
- One script is used for the Network, Local, and archive databases. The script file name is DB_Update_NPDS2026.sql
NOT in ByPass Local Mode #
Caution when Not in ByPass Local Mode
When SPIs a using their local database, they can continue to manage cases on their local database. However, they cannot update/download once the Network Database has been updated.
Once a workstation’s local database has been updated, the SPI can continue to manage cases normally.
ByPass Local Mode #
If you are running Bypass Local Mode, you can update the local database later. Please note that you cannot download cases to the local database until it has been updated.
Update your Network Database #
Warning
Users cannot upload, download, move, or copy cases until the source and destination databases are updated. For example, uploading and downloading cases between the Network and Local databases requires updating both the Network and Local databases.
Users can continue to work on cases locally if they are not using Bypass Local Mode. The cases can be uploaded after the local database has been updated using the MS Access Script.
If both databases are not updated, you will receive an error similar to the one on the right.
To run the update script, log into toxiCALL® with Supervisor rights and ensure all Case and Search Windows are closed.
From the Tools menu, select Data Migration–>Check for Structure Updates…
Using the 3-dot lookup, select the script file “DB_Update_NPDS2026.sql”
Next, select the Network Database or the archive database to be updated.
This step must be performed once for the Network and each Archive database.
Select Yes after confirming you want to update the correct database.
If you attempt to run the script a second time will present an error indicating the column already exists.
After the script has been completed, you will see a success message.
Other messages may indicate that you do not have the appropriate database rights to perform the change or that the database has already been updated.
Update your Local Database #
When using this script update, cases CAN remain on the local database.
Alternative Solution Options
- Update one local database and copy it to each workstation.
- Copy the provided ToxiLoc.mdb to each workstation.
- This requires the local database to have no cases downloaded.
Click here for more details on copying to other workstations.
Using the 3-dot lookup, select the script file “DB_Update_NPDS2026.sql”
Next, select the Local Database or the “Access mdb” archive database to be updated.
This step must be performed for every local database.
Choose Yes to compact the database.
After the local database has been successfully updated and tested, it can be copied to other workstations to save time on distribution.
Copy your Local Database to other Workstations #
MDB Files #
The links below make the empty database files available. These files should be distributed to the application directory of all toxiCALL® workstations. Please note the additional details below for virtual environments, as each user or virtual machine will have an individual copy of the local database.
CAUTION
Do NOT use the ToxiLoc.mdb from this download if you have UCF (User Configurable Forms/Fields) in your database. Please update your existing Local Database, which can then be distributed to other workstations.
After you have tested your local database, it may be more convenient to copy the local database ToxiLoc.mdb and ToxiBlnk.mdb files to other workstations.
The local database is typically stored in the toxiCALL® application folder, typically:
C:\Program Files (x86)\CAS\Toxicall
If toxiCALL® is configured in a virtual environment, and each user has their own copy of a local database, you must update their local databases.
Virtual Environments #
If you are running toxiCALL® in a virtual environment, you must take extra care to ensure all the local databases are updated. Each user may have a local database distributed into their local file share or some other isolation method.
Virtual Environments
One indicator is if your user starts toxiCALL® using the StartToxicall.bat file.
Please reach out to support for questions and further clarification.
New Workstation Installation #
New Workstation Installation
If installing toxiCALL® on other workstations, the ToxiLoc.mdb and ToxiBlnk.mdb files in the local database must be updated.
Update System Tables #
There are two sections that require updating for this part of the process:
Release Anytime
The following will update the Generic Codes and RADARS Definitions. This can be released without the Therapies and Substance Formulation Update.
- Generic Tables
- TCN_Definitions
- SearchList Tables
New Gummies Substance Formulation
The following table should be released with caution. You CAN release the table and start using the new Gummies formulation immediately. However, you will not be able to close the case until you have updated the workstations to Toxicall v4.7.45 or later.
- CodeValue
Requires Therapies DB Script Update
Do NOT release the following tables until you have completed the Database Script Updates
- FieldCodeValue
- SearchView Tables
Before proceeding with these tables, please ensure the above database update steps have been completed. Once the system tables are updated, the databases MUST be updated for toxiCALL® to work correctly.
These updates provide details to toxiCALL® on the new system tables. Once these system tables are released, all databases must be updated. Failure to update the databases using the script can result in errors when saving cases, uploading/downloading cases, or moving cases to an archive database.
Confirm the FieldCodeValue table to be updated with a version date of December 1, 2025 or later.
Double-click to change the Installed Status to Install, and click the Release button.
Click here for details on updating system tables. As shown in the screenshot above, be sure to update the FieldCodeValue system table specifically.
Testing #
The final step is to ensure you can choose the Rivastigmine Therapy within a toxiCALL® case. Please start toxiCALL®, create a new case, click on the Therapies section, and ensure the new Rivastigmine therapy is presented as shown in the image below. Ensure the case can be saved properly and there are no errors present.
Check the Case List Advanced Search Tab 7 #
- After starting toxiCALL®, load the “Case List – Advanced” display.
- Select Tab “7) Therapy”
- Scroll down to confirm that Rigastigmine is available.
Check the Therapy Entry #
Testing Download/Upload Cases #
If you are not using ByPass Local, save a case to the network and download a case from the network. This will confirm that the Data Model updates are correctly in place.
Work Local Only Mode #
Work Local Only mode can be activated to minimize downtime, allowing specialists to continue capturing and managing cases before their local database is updated. Once the network database script is updated in the Update Network Database section, cases can no longer be uploaded/downloaded until their local database is updated, as outlined in the Per Workstation Step-By-StepSteps section.
This will be required if specialists currently download/upload cases with the neOnce the local database is updated, specialists can then upload their cases to the network database.
We suggest that specialists download the cases they want to manage before entering Work Local Only mode.
Enable Work Local Only Mode.
Confirm Work Local Only Mode.
Work Local Only mode enabled. Notice the Network Database Icon shows the Network is Offline.
After your workstation has been updated, you will start toxiCALL® normally. Work Local Only mode will no longer be activated, and you can continue uploading and downloading cases as usual.
Per Workstation Step-By-Step #
This section provides a summary overview of the steps that should be performed at each workstation. To complete these steps successfully, users will need access to a common folder where the following files are stored, as shown below. They will also need the ability to overwrite the existing toxicall.exe file, which may be limited in some IT departments.
Please be sure the person performing these steps has the Supervisor right in toxiCALL®.
Navigate to the common file folder.
Copy the new Toxicall executable file.
Navigate to the Toxicall Program Files location using the shortcut.
Copy the new Toxicall Application file.
Paste the new Toxicall file into the application folder.
Select Replace file to overwrite the old application file.
Start Toxicall using your normal method.
After starting toxiCALL® with a login that has Supervisor rights, select the Check for Structure Updates.
Select the DB Script.
Select the destination of Local Database and Start the update.
This will only take a couple of seconds.
Confirm the Local Database and select Yes.
Confirm Yes to perform a compact database.
Confirm the script is complete.
Exit and restart toxiCALL® normally.
The updates are complete!
