Resolving duplicate primaries

AD
DM

When primary type fields are configured, one object can be primary for different fields. For example, Global Primary Address and Primary Address for Cardiology can be set to Yes/True for the same address. But, a primary field can be set to Yes/True for only one set of objects. For example, an HCP cannot have the Primary Address for Cardiology field set to Yes/True for two different addresses.

Duplicate primaries in the Network UI

To ensure that there are no duplicate primaries, Network changes the primary value if the field is set to Yes/True multiple times across an object.

Example

All users can edit primary fields on record profiles. If the primary field is updated, a data change request is created and sent to local data stewards to accept or reject the change.

To ensure that a field is set to primary on only one object, Network changes the primary value if a field is set to Yes/True multiple times on a record.

Example

On an HCP record, the Primary Address for Cardiology field is set to Yes/True for 6941 W Archer Ave.

A user edits the record and sets the same primary field to Yes/True for 1180 W Wilson St Ste E.

To ensure that there's only one Primary Address for Cardiology defined on the record, Network automatically toggles the field value to No/False on the 6941 W Archer Ave address.

The same behavior occurs on data change requests.

Multiple primaries on entity merge, unmerge, and Change Request API

If multiple primaries are defined on an object (for example, the Primary for Cardiology field is set to Yes/True on more than one address), the primary will be determined by Network for one object only using the following criteria:

  • Source rank
  • Last updated time
  • Network entity ID

Review the following diagram to understand how primary is determined on merge, unmerge, and changes submitted using the Change Request API.

OpenData address merge behavior on the same entity

If OpenData merges addresses on the same entity, the primary address will be retained on the winning address and no primary re-calculation occurs.

Multiple primaries on source subscriptions

When multiple primaries are available in a source file, all of the primary values are read and the source file changes are compared with the data that is already in the Network instance.

Merging and unmerging records

When records are merged, a primary custom field might be set to Yes/True multiple times across one set of objects. For example, both records that are being merged might have the Primary Address for Cardiology field set to Yes/True for an address. Network ensures that the surviving record has only one primary for that field.

Primary rules for merging records:

  • If an object is primary on the winning record, the winning record's primary object remains primary on the merged record.

  • If an object is primary on the losing record, and the winning record has no primary specified, the losing record's primary object will be primary on the merged record.

  • If OpenData or third party managed records are merged with customer records and an OpenData or third party managed address is primary, it always wins.

Unmerging records

When records are unmerged from each other, any fields that were set as primary on the original records are recovered.