Introduction to Database Purge
The purge function allows pharmacies to schedule a database purge of prescriptions that are more than 2 years old. Purges can only be scheduled by users who have Housekeeping Access set in Security - refer to your pharmacy’s System Administrator (ADM) for permission to schedule purges.
Scheduled purges run overnight, following a successful full nightly backup. The purge will delete prescriptions that were filled on or before the specified Rx Purge Date; the Rx Purge Date must be at least 2 years in the past. The purge will NOT delete the following types of prescriptions:
Prescriptions that are part of a current authorization in the Audit History. For example, if a prescription has been filled within the past 2 years and its authorization date is within the purge period, none of the prescriptions in the current authorization chain will be deleted. Any authorization chains prior to the Rx Purge Date will be deleted.
Prescriptions for active non-retail patients. Therefore prescriptions that are currently on the MAR reports will still be on the MARs following the purge. The purge will delete non-retail prescriptions (last filled on or before the Rx Purge Date) in two situations: if they have an inactive group Rx status (group Rx status I or F); or if the patient’s status is deceased, obsolete or inactive.
Purges can have four different statuses:
| Status | This status means... | The message in Purge Request History indicates... |
|---|---|---|
| Pending | The purge is scheduled to run overnight on the Requested Date. Before starting the purge, PharmaClik Rx checks if a batch or report is scheduled within the next 6 hours - the purge cannot run if either one are scheduled, as they take priority over a database purge. If the purge cannot run on the Requested Date, the purge request rolls over to the next night; the purge request continues to roll over until a successful purge can be performed. | The Message is blank for a new request. If a purge request is rolled over to the next night, the Message indicates why the purge is still Pending - the Message is updated each time the purge request is changed to a new date(i.e., The purge did not run on Jul 20, 2005 due to a scheduled report. The purge request will run on Jul 21, 2005). |
| Complete | The purge was successful. The purged data has been removed from the database and cannot be retrieved. | The Rx Purge Date, the number of prescriptions purged and the number of prescriptions remaining.(i.e., 167782 Rx records purged up to Jan 1, 2003. New Rx count is 130310). |
| Failed | The purge did not run. The purge request has been aborted due to errors or an unsuccessful database backup. The purge request will become temporarily disabled until Programming Support can resolve the issue and manually re-activate the purge request. | The purge was aborted. Contact PharmaClik Rx to re-activate the purge request. |
| Deleted | The purge did not run; the purge request was deleted using the Delete function button in the Purge Request History. Pending and Failed purges can be deleted. | The date and user who deleted the request.(i.e., Purge Request was deleted on Jun 21, 2005 by ABC). |