Refreshing inherited addresses

AD
DM
DS

Network inherited address information can become out of sync between an address and its object as data is updated and changed by DCR processing and subscription updates.

Use the Refresh Job Schedule to identify out-of-sync addresses and sync them to the parent address again automatically,

This maintenance feature ensures that your data quality is preserved using scheduled updates. If the Refresh Job Schedule is not used, addresses only sync again if the record containing the address is edited by a user.

Prerequisites

The Refresh Job Schedule is available only when the following features are enabled in your instance:

  • Network Address Inheritance

  • Network reporting

Supported addresses

This maintenance job only considers inherited child addresses that have a parent_address_status_v field with the following values: Synced, Re-sync, or Disqualified.

This field value can be found on the address in the profile.

Scheduling updates to refresh addresses

Administrators and Data Managers can run the address refresh job for the country groups configured for Network Address Inheritance.

  1. In the Admin console, click Data Model > Network Address Inheritance.

  2. In the Job Schedule & Triggers section, define the schedule for the job and any subsequent actions that will start when this job finishes.

    • Job Schedule - Run the subscription manually or on a scheduled basis.

      • Scheduled - Jobs can have multiple schedules to run on daily, weekly, monthly, or yearly.

      • Manual - Click Start Refresh Job to start the maintenance job to immediately update out of sync child addresses.

    • Job Triggers - Trigger other actions to start after a job runs. For example, trigger a target subscription to export the updated addresses to a downstream system.

      Available triggers:

      • Send email - Specify users that should be notified for successful and unsuccessful job outcomes.
      • Start a job - Start a subsequent job when this job successfully completes.

      For more information, see Subscription job triggers.

  3. When the job completes, in the Job History section click the ID link to open the Job Details page and view summary information about the job.

    Click View Job Impact Dashboard to navigate to the dashboard and investigate the records that were updated.

Updating addresses

During the job, Network updates child addresses that are out of date with their synced parent address.

The query looks to see if the parent address has been updated more recently than the child address. Network Address Inheritance logic runs on the child address to ensure that it's updated and in sync again. During the process of syncing HCP or HCO addresses, a new address might be found and copied to the child record.

Example

The most recent address update was for the General Hospital (parent address).

When address refresh job runs, the newest address is pushed down to the child entities in the hierarchy. In this example, the address of the surgical department and John Smith are both updated with the hospital's address.

Revision history

When an address is changed to sync to its parent address, the change is tracked in the Revision History.

If a change is made to the record, Network business rules might run; for example, primary affiliation, primary address, or address ordinal sorting. All of these record changes are also included in the Revision History.