Before You Begin
You must have a CRM Admin role with access to Settings → Integrations → EMR Settings
Your Alleva account must already be connected to your CRM instance (confirmed by the green check next to the Alleva connection)
A pronoun picklist field must exist on the Intake Opportunity (or related Contact / Account record), already populated with the values you want to support (e.g. She/Her, He/Him, They/Them, She/They, He/They, Other, Prefer not to say)
This feature is available on any instance that already uses the Alleva EMR integration — there is no separate feature flag
Steps
Step 1 — Register the Pronoun Field in EMR Field Mapping
This is a one-time setup step. Before the Pronoun Mapping card can list your CRM pronoun values, the custom pronoun field must be registered against Alleva in EMR Field Mapping.
Open EMR Settings → ALLEVA and click Alleva field mapping
Add a new field mapping row with the following values:
Field | Description | Required Value |
Object | The CRM module that owns your pronoun field |
|
EMR field | Must be the literal string — lowercase — so the CRM can identify it |
|
CRM field | The picklist field you created for pronoun |
|
EMR type | The EMR this mapping applies to |
|
Status | Must be active for the mapping to work |
|
Click Save
The pronoun field can live on Intake Opportunities, Contacts, or Accounts — the CRM resolves the correct table automatically when pushing or pulling values. Register the field once on the module where you actually store the value.
Step 2 — Open the Alleva Pronoun Mapping Card
Navigate to Settings → Integrations → EMR Settings
Click the ALLEVA tab
Scroll down past the existing mapping cards (Document Type, Discharge Types, LOC, Treatment Programs)
At the bottom of the ALLEVA tab, locate the new Alleva Pronoun Mapping card
The card contains the following controls:
Control | Purpose |
Sync from Alleva | Pulls the latest pronoun list from your Alleva account and refreshes the mapping table |
Add | Adds a single pronoun mapping row manually — used when Alleva is unreachable or for ad-hoc entries |
Table rows | Each row shows one Alleva pronoun on the left and the mapped CRM value on the right, with Edit and Remove actions |
Step 3 — Sync the Master Pronoun List from Alleva
Click Sync from Alleva
The CRM calls Alleva, fetches every pronoun currently configured there, and creates or updates one row per pronoun in the mapping table
What to expect:
A green success toast: "Pronoun list synced from Alleva."
Each Alleva pronoun appears as a row with the Alleva name on the left and an empty CRM value on the right — until you map it in the next step
Re-clicking Sync from Alleva is safe — existing rows are updated in place, not duplicated
If Alleva returns no pronouns, you will see the message "Alleva returned no pronouns." instead. Add pronouns inside Alleva first, then click Sync again.
Step 4 — Map Each Alleva Pronoun to a CRM Value
For each row in the mapping table:
Click the blue Edit icon at the right of the row
In the modal, the Match (EMR) column shows the Alleva pronoun name and the Matching (CRM) dropdown lists every value from your CRM pronoun picklist (registered in Step 1)
Select the CRM value that corresponds to this Alleva pronoun
Click Save
The row in the mapping table refreshes to show both sides paired up.
Important: Rows without a CRM value assigned are ignored by the patient sync — they neither push nor pull. Until every Alleva pronoun you care about has a CRM value assigned, the corresponding patients will not be kept in sync.
Verification / Expected Result
Once each Alleva pronoun has a CRM value assigned, the integration runs automatically in the background. There is nothing else to configure.
When a patient is created from the CRM: When you click Create Patient in Alleva on an Intake Opportunity, the CRM:
Reads the pronoun value from the opportunity (or its related Contact / Account)
Looks up which Alleva pronoun it is mapped to
Sends that pronoun to Alleva immediately after the patient is created
If the opportunity's pronoun field is empty or does not match any mapping, the patient is still created — the pronoun is simply skipped.
When a patient is updated in the CRM: The same push runs on update — if the pronoun changes in the CRM, the new value is sent to Alleva automatically.
When a patient's pronoun changes in Alleva: The scheduled Alleva refresh that already updates other patient fields (LOC, discharge type, etc.) now also pulls the patient's current pronoun from Alleva. The CRM looks up the mapped CRM value and writes it to the correct pronoun field on whichever module owns it.
The inbound pull uses the standard CRM save path, so any workflows or save-time hooks you have on the pronoun field will run normally when Alleva updates it.
Troubleshooting / Common Errors
Issue | Likely Cause | Fix |
Alleva Pronoun Mapping card is not visible | Not on the ALLEVA tab, or insufficient role permissions | Confirm you are on the ALLEVA tab of EMR Settings and that your role can view EMR Settings |
CRM pronoun dropdown is empty in the mapping modal | Pronoun field was not registered in EMR Field Mapping | Complete Step 1 — register the pronoun field with EMR field set to |
Sync returns "Alleva returned no pronouns." | No pronouns configured in Alleva | Add pronouns in Alleva first, then click Sync from Alleva again |
Pronoun not pushed to Alleva on patient creation | The mapping row for that pronoun has no CRM value assigned, or the pronoun field on the opportunity is empty | Ensure all relevant Alleva pronouns have a CRM value mapped in the table |
Pronoun not pulling from Alleva back to the CRM | The mapping row exists but has no CRM value, or the scheduled Alleva refresh has not run yet | Assign a CRM value to the mapping row; allow the scheduled refresh to complete its next cycle |
Feature still not visible after confirming tab and role | Instance-level access issue | Contact Dazos Support with examples and information, |