Skip to main content

Troubleshooting Lightning Step EMR Mapping and Multi-Entity Admission Errors (CRM)

Purpose of This Guide

This guide helps resolve two common Lightning Step EMR integration issues: field-mapping errors for specific levels of care (such as residential) and multi-entity admission restrictions that prevent the creation of new episodes.

Symptom/Error 1: Mapping Field Errors for Residential Level of Care

What you'll see: When pushing patients to Lightning Step with a residential level of care selected, you receive an error message stating "the mapping field is not correct."

Workaround: You have to push the patient to the detox level of care, then manually change it to residential within Lightning Step.

Cause

The field mappings for the residential level of care are not properly configured in the Lightning Step integration settings. Each level of care (residential, detox, IOP, etc.) requires separate field mapping configuration.

Solution

Step 1: Navigate to your Lightning Step integration settings in Dazos.

Step 2: Click "Lightning Step Fields Mapping" next to the connection.

Step 3: Check the field mappings specifically for the residential level of care.

Step 4: Ensure all required fields for residential patients are properly mapped between Dazos and Lightning Step.

Step 5: Save the mapping changes and test with a residential patient.

Symptom/Error 2: Multi-Entity Admission Restriction

What you'll see: Error message "Client is currently admitted in this entity. New episodes may not be created while the client remains admitted."

When this happens: Attempting to push an IOP patient to Lightning Step when they are already admitted at another location within the same entity.

Cause

Lightning Step prevents the creation of new episodes when a patient is already admitted to another location within the same entity. This is a built-in restriction in Lightning Step to prevent duplicate active admissions.

Solution

This error indicates the patient has an active admission at another facility within your Lightning Step entity. To resolve:

Step 1: Check Lightning Step to identify where the patient is currently admitted.

Step 2: If the patient should no longer be admitted at the other location:

  • Discharge the patient from the previous location in Lightning Step

  • Then attempt to push the new IOP admission

Step 3: If the patient should remain admitted at both locations:

  • Contact Lightning Step support to understand multi-location admission policies

  • Consider if the locations should be configured as separate entities

Escalation

Contact Dazos Support if:

  • Field mapping configurations don't resolve the residential level of care errors

  • You need assistance identifying which fields should be mapped for different levels of care

  • The Lightning Step Fields Mapping option is not visible in your settings

Contact Lightning Step Support if:

  • You need clarification on their multi-entity admission policies

  • You believe a patient should be allowed concurrent admissions but the system won't permit it

  • You need to restructure your entity configuration

Related Resources

Did this answer your question?