We need more granular control over contact de-duplication, specifically for users syncing data from clinical platforms via API (I use Nookal, but I'm sure many health care PMS would have a similar problem). Relying solely on Email/Phone leads to corrupted data when family members share contact info (e.g. parent and child = often same last name and same email or mobile).

Requested Logic Requirements:

The "Strict Match" Rule: Only auto-merge if Email + Last Name + Birth Date are identical.

A "Review" Trigger: If Email and Last Name match, but First Name or Birth Date differ, the system must pause the sync for that contact - send it for a "pending merge" option which a human can confirm or reject.

Proposed UI Element: A "Conflict Resolution" tab within the Contact section where users can see "Incoming Data" vs "Existing Data" and choose to Merge, Keep Separate, or Overwrite.

In healthcare, merging two different people into one record based on a shared email is a data integrity risk. Adding Birth Date as a mandatory validation field for merging would help solve this.

Kind regards,

Sam