Overview
The LOC Mapping screen in Dazos CRM allows you to match your CRM's Level of Care (LOC) picklist values to the service names that iVerify expects for electronic insurance verification (EIV). This mapping ensures that insurance verifications return accurate results even when a customer has customized their LOC labels.
Why This Matters
iVerify relies on specific, standardized service names to process electronic insurance verifications. When a customer renames or customizes their LOC picklist values in the CRM — for example, changing PHP to Day Program — iVerify no longer recognizes the label. As a result, verification results come back blank or null for that level of care.
The LOC Mapping screen solves this problem by letting you map the custom LOC name back to the standard iVerify service name, so EIV continues to populate correctly.
When to Use LOC Mapping
Standard LOC names (no customization): If the customer's LOC picklist values match the standard iVerify service names exactly (e.g., PHP → PHP), no mapping is needed. Leave it as-is.
Custom LOC names: If the customer has renamed any LOC picklist values, add a mapping row for each customized name so that iVerify can correctly match it to the expected service name.
Example
CRM Level of Care (Custom Name) | iVerify Service Name (Standard) |
Day Program | PHP |
Residential | RTC |
PHP | PHP (no mapping needed) |
Rule of Thumb for Implementation Teams
✅ LOC name matches iVerify exactly → No action required.
⚠️ LOC name has been customized → Add a mapping row for each custom name, pointing it to the correct standard iVerify service name.
When onboarding a new customer, review their LOC picklist values early in the implementation process. If any values differ from iVerify's standard service names, configure the LOC Mapping screen before going live to prevent blank verification results.
Tips & Notes
💡 Tip: Ask the customer to share their full list of Level of Care picklist values during discovery. Compare them against the standard iVerify service names and identify any that need a mapping row.
⚠️ Warning: If a custom LOC name is not mapped, insurance verifications for that level of care will return blank or null results. This can affect the accuracy of benefits information for patients.