Before You Begin
You'll need:
Administrator access to Dazos CRM EMR Settings.
The insurance payer already created in Lightning Step.
The corresponding insurance payer already created in Dazos.
Access to submit a Dazos support ticket.
Overview
For insurance payer information to push correctly to Lightning Step — on both new admissions and re-admissions — the payer must exist in both Lightning Step and Dazos, and be mapped in the Dazos EMR integration settings. If a payer is not mapped, it will be excluded from the payload sent to Lightning Step, resulting in blank or missing Insurance/Payor records that block claims processing.
If you are seeing blank Insurance/Payor records created in Lightning Step on re-admissions, or insurance information that is not populating after a sync, an unmapped payer is the most likely cause.
Steps
Add the insurance policy in Lightning Step. The payer must first exist in your Lightning Step instance before it can be mapped. If it does not already exist, add it in Lightning Step before proceeding.
Add the corresponding insurance policy in Dazos. Navigate to the appropriate area in your Dazos CRM and add the matching insurance policy. The payer must exist in both systems before a mapping can be created.
Submit a Dazos support ticket to complete the mapping. Once the payer exists in both systems, contact Dazos Support and let us know the policy was added. Our team will complete the mapping in the EMR integration settings so the payer is included in payloads sent to Lightning Step.
Verify the mapping is working. After Dazos confirms the mapping is complete, test by pushing an admission or re-admission for a patient with that insurance policy. Confirm that the payer appears correctly in Lightning Step's Payor Information tab with the correct Payor Name, Payor Type, and Plan Priority populated.
How to Check for Unmapped Payers
If insurance is not appearing in Lightning Step after a sync, check whether the payer is mapped in your EMR settings:
In Dazos CRM, navigate to Settings → EMR Settings → Lightning Step.
Review the insurance mapping configuration for your instance.
If the payer is missing from the mapping list, follow the steps above to add it to both systems and submit a support ticket.
⚠️ Important: When selecting insurance options in Dazos, always choose the options that include payer codes, as those are the options currently mapped between the systems.
Selecting an insurance option without a payer code may result in it not syncing correctly.
Result
After completing these steps, the insurance payer will be included in the payload sent to Lightning Step on both new admissions and re-admissions. Payor Name, Payor Type, Funding Source, and Plan Priority will populate correctly in Lightning Step, and claims processing will not be blocked by blank or missing payor records.
Important Notes
Re-admissions and new admissions both require mapped payers. A payer that is not mapped in the Dazos EMR integration settings will be silently excluded from the payload regardless of whether the admission is a first-time admission or a re-admission.
A connector fix has been deployed for policies without a Member ID. Previously, insurance policies with a blank Member ID were sometimes silently skipped if an older payor record on the same client also had a blank Member ID. This was caused by the duplicate-prevention logic treating blank values as a match. This bug has been fixed — policies without a Member ID will now always be pushed to Lightning Step. Logging has also been added to make any skipped policies easier to identify going forward.
Notify Dazos whenever a new insurance policy is added. Because mapping must be completed by the Dazos team, it is important to submit a support ticket each time your team adds a new payer in either system. Without this step, new payers will not sync correctly.
💡 Tip: If your team adds multiple new insurance policies at once, include all of them in a single support ticket so Dazos can map them together.
Still Need Help?
If insurance is still not populating in Lightning Step after confirming the payer is mapped, or if you are unsure whether a specific payer is mapped, contact Dazos Support and provide the name of the insurance policy and the affected patient opportunity. Our team can review the payload sent to Lightning Step and identify any missing or misconfigured mappings.