Home
Encounters
Open a service recording for patient interactions and add clinical items, record progress notes, prescribe medications, review investigations, write referrals and manage recalls.
Clinical Support
Recalls
Recalls are the elements that make up a care plan. Recalls can be either generated automatically by Communicare or manually created by the user.
Automated recalls
Communicare can automatically create one or more recalls when particular events occur.
Automated Recall Events
Recalls are automatically generated when these events occur.
Recalling on both On Registration and On Presentation Events
Typically you should not generate recalls on both On Registration and On Presentation events. However, it can be done successfully if due care and diligence are exercised.

Encounters
Open a service recording for patient interactions and add clinical items, record progress notes, prescribe medications, review investigations, write referrals and manage recalls.
- Encounters
  Record patient encounters in Communicare using any one of the following methods.
- Medications
  This topic covers all Medications Management functionality within Communicare.
- Clinical Support
  - Investigations and documents
    Communicare receives pathology and imaging results, letters and other documents electronically and sends documents and letters electronically using HL7 messages.
  - Referral Management
    Manage incoming internal and external referrals from a single list.
  - Birth Notifications
    For customers who belong to the Western Australian Country Health Service, use the Birth Notifications module to manage notifications related to births from a single list.
  - Recalls
    Recalls are the elements that make up a care plan. Recalls can be either generated automatically by Communicare or manually created by the user.
    - Automated recalls
      Communicare can automatically create one or more recalls when particular events occur.
      - Automated Recall Types
        Automated recall types control the automatic generation of recalls. They can be edited by the Communicare Administrator.
      - Automated Recall Events
        Recalls are automatically generated when these events occur.
        On Registration
        The On Registration event occurs when a patient's date of birth is first added to the Biographics record.
        On Presentation
        The On Presentation event occurs when a condition is entered into a patient's clinical record.
        On Completion
        The On Completion event occurs when a recall is completed, or when a recallable clinical item is entered into a patient's clinical record.
        On Qualifier
        When an automated recall is triggered by a qualifier you must define the qualifier and the response.
        Recalling on both On Registration and On Presentation Events
        Typically you should not generate recalls on both On Registration and On Presentation events. However, it can be done successfully if due care and diligence are exercised.
      - Automated Recall Confirmation
        Before an On Completion or On Presentation recall is generated, the Confirm Automated Recall window is displayed.
      - Recalls Generated by Multiple Events
        Some automated recalls are generated by multiple events.
      - Effect of Patient Date Of Birth on Recall Generation
        Automated recall creation can be controlled by the age of the patient. An automated recall type can be designated as specific to a patient older than or younger than defined ages or within an age range.
      - Effect of Patient Sex on Recall Generation
        Automated recall creation can be controlled by the sex of the patient, that is an automated recall type can be designated as specific to a patient of a certain birth sex.
      - Effect of Aboriginality on Recall Generation
        Automated recalls can be restricted to those who identify as Aboriginal or Torres Strait Islander.
    - Manual Recall Creation
      You can create recalls manually for clinical item types that have automated recalls and for certain other Clinical Item Types that do not have automated recalls.
    - Regenerating recalls
      Every time a recall type is edited, the system attempts to rebuild all the automated recalls of that particular type.
    - Completing recalls
      Complete a recall either directly or indirectly.
    - Removing outstanding recalls
      Occasionally, you may want to remove recalls that are no longer relevant from patient records. Before you attempt to remove recalls, or request that Communicare does this for you, check the following information.
    - Immunisation Reviews
      Immunisation Reviews are reminders at set ages to review which immunisations each patient has had, and what immunisations they are due.
    - 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.
    - Cancer recalls
      Additional clinical items were added in V21 following advice and consultation with the GP Review of Clinical Software for compliance with the National Cancer Screening Guidelines.
  - Datasets
    Datasets are a user-friendly coding system, giving health professionals a standardised way to record data and report on data entered in a patient’s clinical record.

Recalling on both On Registration and On Presentation Events

Typically you should not generate recalls on both On Registration and On Presentation events. However, it can be done successfully if due care and diligence are exercised.

If both On Registration and On Presentation 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 On Registration 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 On Presentation 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 On Completion 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.

14 November 2023