Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Care Management - Deploying the Alert Processor

Updated on September 25, 2019

The Care Management Framework contains a Data-Admin-Queue instance in the PegaClinical RuleSet called Alert Processor that is derived from a Rule-Agent-Queue instance of the same name/class.

It is this data queue that processes all active alerts on a recurring schedule each day.

Out of the box, the queue is set to process alerts at 1:00 AM every day when the status of the work item is PENDING.

When the agent processes an alert in the queue, it:

  1. Evaluates scheduling information to determine if the alert is scheduled to run. If it is not, it evaluates the next alert in the queue.
  2. Evaluates the data source information to find claim criteria and create a result set. If there is none, it evaluates the next alert in the queue.
  3. Matches the codes against the data source result set.
  4. Stores all events on the alert work item in case of a matching event.
  5. Processes all dormant work items if the alert is looking for the presence of a claim.

The following diagram shows this chain of processing events by the agent.

Deployment Options

To deploy the Alert Processor, consider the following configuration changes:

Changing the Schedule of the Alert Processor

  • Copy the Alert Processor queue rule to your RuleSet
  • Update the parameters located on the Scheduled Activities tab

Implementing Error Reporting

    • Copy the activities listed in the table below to your RuleSet
    • Add your reporting requirements


Activity Name

Called by




Activity ProcessSingleAlert


Activity ProcessSingleTask


Activity ProcessSingleGoal


Configuration Tip: Configure your clipboard pagesto capture processing information in the activity ReportAlertProcessorProblem. Then, use the activity CreateAlertProcessorReport to handle the collection of data for each daily run of the alert processor agent.

Return to About the Care Management Framework





Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us