Skip to main content

Required Fields for Pushing Clients to Alleva EMR (CRM)

Overview When pushing a client from Dazos CRM to Alleva EMR, specific fields must be completed to ensure successful data transfer. Alleva has unique requirements that differ from other EMR integrations.

Required Fields for Alleva Integration

Based on our integration experience, the following fields are required when pushing clients to Alleva:

  • Gender - Must be populated in the client's demographic information

  • Date of Birth (DOB) - Required for patient identification

  • Treatment Program - Must be selected before initiating the push

  • Admission Date - Required for the admission process

  • Email Address - Critical requirement as Alleva uses email as a unique identifier

Additional Requirements

In addition to the specific fields above, you must also ensure:

  • All red-asterisk mandatory fields in the CRM are completed

  • Lead details and patient demographics are filled out comprehensively

  • Insurance policies are properly configured if applicable

Why These Fields Matter

Each required field serves a specific purpose in the Alleva system:

  • Email - Acts as the unique identifier for patient records

  • Gender and DOB - Essential demographic data for patient matching

  • Treatment Program and Admission Date - Required for proper program enrollment and scheduling

Verification Steps

Before attempting to push a client to Alleva:

  1. Review the client record for any red-asterisk fields that need completion

  2. Confirm that Gender, DOB, and Email are populated

  3. Verify that Treatment Program and Admission Date are selected

  4. Check that insurance information is complete if applicable

โš ๏ธ Note: While we don't maintain comprehensive field requirement lists for every EMR, these requirements are specific to Alleva based on their system's unique identifier structure and integration specifications.


Related Resources

For assistance with EMR integrations or field mapping, contact Dazos Support for guidance specific to your implementation.

Did this answer your question?