Recall migration

If the recall policies for your site or for clinical items change, your site can migrate your recalls using one of the following approaches.

Note: Ensure that you speak to Communicare Support before migrating recalls.
Table 1. Example recall migration strategies
What Who Clean up
Disable the original recall rule and enable the new recall rule Migration managed by your Communicare Administrator at your site Manage recalls that are not automatically removed manually as patients present or run Recalls Due report and manually convert disabled recalls to new recall
Original recalls are progressively updated Migration managed by your Communicare Administrator at your site If the correct sequence is followed, Communicare will create a new On Registration recall with the same due date as the original recall
New recalls preserving the due date of the original recall are added, duplicating the original recall Migration facilitated by Communicare Support using a custom SQL script to replace the original recall with the new recall

On registration recalls will be created for all patients, including those who have already declined the recall.

The original recalls will remain in the clinical record and will need to be completed or cancelled.

New recalls preserving the due date of the original recall replace the original recalls Migration completed by Communicare Support using a stored procedure in addition to an SQL script to reconcile recalls None