Skip to main content

Troubleshooting Lightning Step EMR Caller Name Fields Not Mapping via API (CRM)

Overview This guide helps resolve issues where Caller First Name and Caller Last Name fields fail to populate in Lightning Step EMR when pushing patient data from Dazos, even though the API response indicates success.

Symptom / Error

When pushing patient records to Lightning Step EMR, the Caller First Name and Caller Last Name fields remain blank in the Lightning Step Caller Information section, despite the API payload containing the data and returning a successful response.

⚠️ Note: The patient record itself is created successfully — only the caller name fields fail to populate.


Cause

The Caller First Name and Caller Last Name fields are not available for mapping through the Lightning Step API. While these fields appear as mandatory in the Lightning Step interface, the API does not expose them as writable endpoints for external integrations.

This is an API limitation on the Lightning Step side, not a Dazos configuration issue.


Solution

Step 1 — Verify Field Mapping Attempts

Confirm that both field formats have been tested:

  • Standard format: callerfname, callerlname

  • Prefixed format: ice.callerfname, ice.callerlname

Step 2 — Contact Lightning Step Support

Open a support ticket with Lightning Step requesting:

  • Confirmation of API field availability for caller name fields

  • Backend updates to enable API writing to these fields

  • Alternative field mapping options

Step 3 — Implement Workaround

Until API mapping is enabled:

  • Manually enter caller names directly in Lightning Step after record creation

  • Document this limitation for staff workflows

  • Consider alternative data capture methods if caller information is critical

Step 4 — Coordinate Joint Testing

If Lightning Step indicates API support should be available:

  • Schedule a meeting with both Dazos and Lightning Step support teams

  • Conduct live testing with different field key formats

  • Verify backend configuration on Lightning Step's end

Verification / Expected Result

After Lightning Step enables API support for these fields:

  • Caller First Name and Caller Last Name will populate automatically

  • Manual entry will no longer be required

  • The integration will work seamlessly for all future patient records

Escalation

Contact Dazos Support if:

  • Lightning Step confirms API support but fields still don't populate

  • You need assistance coordinating with Lightning Step support

  • Alternative mapping solutions need to be explored

When contacting support, provide:

  • Lightning Step support ticket reference number

  • Screenshots of empty caller name fields

  • API payload examples showing the caller name data

  • Timeline requirements for resolution

Related Resources

  • Lightning Step EMR Field Mapping for Bedboards and Patient Data Sync

  • EMR Integration Field Mapping Overview

  • How to Contact Third-Party EMR Support for API Issues

Did this answer your question?