Symptom/Error

When patients with compound last names (two surnames) are synced to Alleva EMR, only the first surname appears in the last name field. The second surname incorrectly appears in the middle name field instead of being included with the full last name.

Example: A patient named "Dazos Aliba Test" appears in Alleva as:

First Name: "Dazos"
Last Name: "Test" (only first surname)
Middle Name: "Aliba" (second surname incorrectly placed here)

This issue is particularly common with Hispanic naming conventions where compound surnames are standard.

"In the JSON payload, notice how the middle name field is incorrectly populated with the second surname ("Alleva") instead of the patient's actual middle name."

Cause

This occurs due to backend parsing logic in the Dazos-Alleva integration that incorrectly splits name components. The system mistakenly routes the second surname to the middle name field instead of keeping the full compound name in the last name field when building the API payload sent to Alleva.

The field mapping in Alleva is correctly configured - the issue originates from how Dazos constructs the name data before transmission.

Solution

This issue requires a backend fix from the Dazos development team to correct the name parsing logic in the EMR integration. This is not something that can be resolved through CRM settings or field mapping changes.

Steps for resolution:

Contact Dazos Support - Report the specific patients affected and provide examples
Development team investigation - Our developers will review the backend parsing logic
Backend fix deployment - The name parsing logic will be updated to properly handle compound surnames
Testing verification - Test with a new patient record after the fix is deployed

Expected Result After Fix

Once the backend fix is deployed:

Patients with compound last names will sync correctly to Alleva
The full compound surname will appear in the last name field (e.g., "Aliba Test")
The middle name field will only contain actual middle names
Both new patients and re-synced existing patients will display correctly

When to Contact Support

Contact Dazos support immediately if you encounter this issue, as it requires backend development work and cannot be resolved through configuration changes. Please provide: