Recalling on both OnRegistration and OnPresentation Events

Typically you should not generate recalls on both OnRegistration and OnPresentation events, however it can be done successfully if due care and diligence are exercised.

If both OnRegistration and OnPresentation events generate recalls, run a Recall Duplication report periodically to identify and correct duplicate recalls and provide training to the operators who generated the duplicates. Contact Communicare Support if you need assistance with a Recall Duplication report.

Note: Duplicate recalls are generated only by active intervention by the operator.

Example

This issue is most easily understood by considering the following scenario.

An OnRegistration event has generated a Pneumovax recall for a patient's 50th birthday. Later, a diagnosis of Diabetes Mellitus is made some time before the 'age 50' Pneumovax has been given. An OnPresentation event will warn the operator that a recall for Pneumovax already exists for age 50 and will not generate an additional recall unless Confirm is set. This requires diligence from the operator to not set Confirm but instead either:

Adjust the Planned Date for the existing recall. Setting Confirm would result in 2 Pneumovax recalls which might not be properly spaced.
Actually give the immunisation at the time of diagnosis. The outstanding recall is automatically completed and a new recall generated by the OnCompletion event.

Not reading the warning message and setting Confirm regardless could result in a recall on the 50th birthday, which is sooner than desired.

Note: This situation only arises after active intervention by an operator to change the default action and indicates the need for operator training.