Overview
This guide explains why a patient discharged in Alleva EMR may still show an Admitted Status of In Treatment in Dazos CRM, and what steps are required to resolve it. There are two common causes: missing discharge type mapping and incorrect readmission workflow.
Symptom / Error
A patient has been discharged in Alleva EMR, but their Admitted Status in Dazos CRM continues to display as In Treatment. The discharge date may appear further down in the CRM record, but the Admitted Status field at the top of the chart does not update.
Cause
There are two reasons this can occur:
Discharge Type Mapping is missing or incorrect: The discharge types used in Alleva EMR must be mapped to the corresponding Admitted Status and Discharge Type picklist values in Dazos CRM. If this mapping is not configured — or if discharge types in Alleva were changed after initial setup — the CRM will not receive or apply the discharge status correctly.
Readmission was processed without a new Intake Opportunity: If a patient was readmitted in Alleva EMR before a new Intake Opportunity was created in Dazos CRM, the sync will not work correctly. The CRM requires a new opportunity to exist first in order to associate the readmission data properly.
Solution
Issue 1 — Discharge Type Mapping Not Configured or Out of Date
Compile a list of all discharge types currently used in your Alleva EMR. Spell them exactly as they appear in Alleva — spelling and formatting must match precisely.
Contact Dazos Support and provide this list so the team can verify or update the discharge type mappings in your CRM configuration.
Each Alleva discharge type must be mapped to the correct Admitted Status and Discharge Type picklist values in Dazos CRM.
Once mappings are confirmed, Dazos Support will push test patients through the EMR to validate that the status updates correctly.
⚠️ Note: If discharge types in Alleva are renamed, added, or restructured after the initial integration setup, the mappings in Dazos must be manually updated to match. This does not happen automatically.
⚠️ Note: Mapping changes only affect future discharge syncs. Previously discharged patients showing an incorrect status may need to be reviewed and updated manually or by Dazos Support.
Issue 2 — Readmission Processed in Alleva Before a New Opportunity Was Created in Dazos
In Dazos CRM, create a new Intake Opportunity for the patient before processing the readmission in Alleva EMR.
Once the new opportunity exists in Dazos, proceed with the readmission in Alleva EMR.
Manually link the patient's Alleva record to the new Intake Opportunity in Dazos if required.
💡 Tip: Always create the new Intake Opportunity in Dazos CRM first, before admitting the patient in Alleva. Reversing this order will break the sync for that record.
⚠️ Note: Automated readmission sync between Alleva and Dazos is currently in development. Until this feature is available, the manual process above must be followed for all readmissions.
Verification / Expected Result
After discharge type mappings are correctly configured and the proper workflow is followed for readmissions, the Admitted Status field at the top of the patient's CRM record should update automatically to reflect the correct discharged status when a discharge is recorded in Alleva EMR.
When to Contact Support
Contact Dazos Support if:
You need help identifying or updating discharge type mappings in your CRM configuration
Admitted Status is still not updating after mappings have been reviewed
A patient record was affected by an out-of-order readmission and needs to be corrected
You are unsure which discharge types are currently mapped or need to provide an updated list from Alleva