The toxiCALL® Migration tool is designed to import existing case information into toxiCALL®. The first iteration will focus on importing data from toxiCALL® 4, but other data sources will be considered in future releases.
We have provided a variety of case selection options for the migration tool. This will allow you to migrate various case groupings for evaluation and data verification.
Recommended Migration Settings
For both testing and moving to production, we recommend using the Case Status to choose which cases to migrate. The solution will be to leave all case statuses selected and enter a starting date for the Closed status. This will ensure all cases are migrated while bringing in only the desired duration of closed cases. We recommend January 1st of the previous year for the Closed cases starting date. This will help keep a manageable set while migrating in other cases later.
Other Settings of Consideration:
- User Name Parsing
- Verify to ensure names are parsed as needed
- Employee Data and User Rights
- Leave this as default. It won’t be necessary to lock users out of toxiCALL® 4.
- Password Options
- Use the Pre-Migration checklist to ensure passwords meet the new password requirements.
- toxiCALL® 5 will update user passwords if needed and generate a log of changes.
- Notes Redaction
- Keep the default Options.
- This will slow the time it takes to perform migration.
- Tracking History/Migrate ToxDelta Table
- This will significantly slow the time it takes to perform migration.
- This can be considered for a future migration pass.
Migration Summary Window #
Before starting migration, you will choose your existing source database, typically toxiCALL® 4, and then the destination database. You will then be presented with a summary screen where you can select special migration options, and filter which cases to be migrated.
The summary window indicates the databases, servers, and features selected for the migration. You will also see the total number of cases to be migrated to provide a general time required for the migration. Each feature and option is detailed in respective sections of this documentation.
IMPORTANT:
The source and destination databases must be hosted on the same server. This will significantly reduce the time required to convert the data.
Testing Environment #
Our support team will work with all poison centers to set up testing environments. The testing environments will be helpful to ensure the migration handles your data correctly and all expected data is migrated accurately.
The testing environment will also aid in evaluating toxiCALL®’s functionality to determine when your poison center is ready to upgrade. You will be able to have specialists utilize toxiCALL® in this controlled testing environment to provide feedback on features, defects, and needed functionality. This will also provide a significant starting point for user training.
IMPORTANT:
Testing environments will be critical to ensure the migration will go smoothly, and that your data are migrated properly, prior to going live. During this testing, we will ask for feedback to address special data capture needs, e.g. DOB captured in a unique field, as well as other potential data inconsistencies.
User Configurable Fields (UCF) #
Our goal is to migrate these data fields into the new Survey module. This will require special review as our team needs to ensure all unique usages have been addressed.
What is not migrated? #
Our immediate goal is to ensure all case data captured is migrated. We are evaluating the ability to migrate configured features such as search criteria, required fields, and other details. However, these may need to be recreated. The current list of items not migrated includes:
- Search Criteria
- Custom Displays
- Batch Reports
- User Configurable Requirements (UCR)
- Application Configurations
- toxiCALL® Data Analysis
- Reports
- Grids
- Pivot Tables
- Graphs
If any of the above details are important to your environment, please contact our support team so we can evaluate it further.
Migration Logs #
After the migration is complete, the Migration Status and Log details will be created. These logs can be exported if further analysis is required.
Migration Verification #
After migration is complete, each poison center must ensure data are being migrated properly. While the toxiCALL® data model should be consistent between poison centers, we want to ensure no problems and that any migration issues are identified early.
Date of Birth and Electronic Medical Record Number #
We understand that various data fields are being used to capture the DOB and EMR in toxiCALL® 4. As we see these data locations, the toxiCALL® team will build data scrubbing tools into toxiCALL® 5. This will allow us to move the DOB and EMR into their new designated fields while attempting to minimize entry requirements.
