I am working on UHC Medical 834 outbound integration.

Originally replied by Barbara Buchanan on Aug 24, 2026, 1:13 PM.

Hi @Prateek Dwivedi​ - Since you are referencing Employee Election Details (plan Xref) in your mapping, you may need to add a filter to that array that also points to Employee Election Details. I added a filter that identified the Plan Xref codes to be included, and that worked for me (xref in HMO, PPO, etc). Just a possibility.

Originally replied by Brenda Sutton on Aug 24, 2026, 5:11 PM.

@Prateek Dwivedi​  and @Barbara Buchanan​, I believe the filter approach you've suggested is the correct direction. The error indicates the mapper cannot uniquely resolve EmployeeElectionDetails. Since that is a repeating collection, try filtering the collection using PlanXRefCode so that only the applicable plan election(s) are available to the mapping. Your example of filtering to the relevant HMO/PPO/etc. XRef codes is consistent with that approach. Once the collection is narrowed to the intended election, the conditional mapping should have an unambiguous EmployeeElectionDetails path to use for the REF02 value. @Pranaw Sharma​ this may be a good example for Chris to show during our Webinar.

Originally replied by Brenda Sutton on Aug 25, 2026, 5:09 PM.

@Pranaw Sharma​ please take a look at Prateek's question.

Originally replied by Prateek Dwivedi on Aug 25, 2026, 11:58 AM.

Thank you @Brenda Sutton​  @Barbara Buchanan​   I am able to resolve that issue but applying further filter on plan xref based on all four plan option codes. Please see the image. But landed into another error "Condition matched multiple elements in the array" . On further observation i see that in my source data EmployeeElectionDetails array has two entries for same plan (UHC_MEDICAL_HSA_PLUS), and having one option code EMP_UHC_MEDICAL_HSA_PLUS active coverage ending at 08/31 and another option code FAM_UHC_MEDICAL_HSA_PLUS having future start date as 09/01. So, it appears to me that this might be causing the issue. Not sure though. Do i need to further filter the Choose Record condition? Attaching image of condition that i already applied.

Originally replied by Pranaw Sharma on Sep 10, 2026, 1:29 PM.

Hi Prateek,

Yes, I think you’ve identified the issue correctly. Since the same employee has multiple EmployeeElectionDetails records for the same plan, the current Choose Record condition is likely matching more than one record, resulting in the “Condition matched multiple elements in the array” error.

My guess is: one record is the previous election and the other is the newer election. You could try refining the Choose Record condition to select the latest applicable record based on the effective start date. That should narrow the result to a single record and resolve the error.

Hope that helps! Please let us know how it goes.