Overview
When the Alleva EMR integration is configured correctly, demographic changes made directly in Alleva — such as adding an email address to a linked patient chart — will sync back into Dazos CRM automatically, without any manual intervention. You do not need to click Pull Updates from EMR for these updates to appear.
This article explains the two conditions required for automatic sync, how the sync mechanism works, and what timing to expect.
Key Concepts
Bidirectional sync: The Alleva integration supports two-way data flow. Changes made in Dazos can be pushed to Alleva, and changes made in Alleva are pulled back into Dazos.
Field mapping: Only fields that have been mapped in the Alleva field mapping screen will be synced. Unmapped fields are ignored.
Pull EHR updates for existing records — Demographics: This setting must be enabled in your Global EMR Settings for demographic changes in Alleva to automatically update already-linked CRM records.
Webhooks: Alleva sends real-time notifications to Dazos whenever a patient record is changed. Dazos processes these immediately upon receipt.
Scheduled sync: A fallback sync runs at least once per hour to catch any updates that may have been missed by a webhook.
How It Works
When both required conditions are met — the demographic field is mapped and Pull EHR updates for existing records → Demographics is enabled — the following process occurs automatically:
A change is made to a patient record in Alleva (for example, an email address is added to a linked chart).
Alleva sends a real-time CLIENT_UPDATE webhook notification to Dazos.
Dazos receives the webhook, looks up the linked CRM record, and writes the updated demographic value to the mapped CRM field — typically within seconds.
If the webhook notification is missed for any reason, a scheduled sync runs at least every hour as a fallback and picks up the change then.
In practice, most demographic updates appear in Dazos almost immediately after you make the change in Alleva. The worst-case delay — if the webhook is missed and the fallback sync must run — is approximately one hour.
Important Notes
The manual "Pull Updates from EMR" button is not required. When the integration is configured as described above, the sync happens automatically in the background. The manual button is available only if you need to force an immediate refresh on demand — for example, if you cannot wait for the next scheduled sync cycle.
Both conditions must be in place for automatic sync to work:
The demographic field (e.g. email) must be mapped in Settings → EMR Settings → Alleva → Field Mapping.
Pull EHR updates for existing records → Demographics must be enabled in your Global EMR Settings.
If either condition is not met, demographic changes in Alleva will not automatically sync back into Dazos. Contact your CRM Administrator to verify these settings are configured correctly.
For information on setting up or verifying the webhook configuration, see Set Up Real-Time Alleva EMR Webhook Integration (CRM).