View source for BenSelect:Admin:LDEX

=LDEX API Integration – Getting Started=
The LIMRA Data Exchange (LDEx) Standards are free standards developed in collaboration with a committee of carriers and technology companies, by the industry, for the industry. There are two methods of using these standards to exchange data: using the LDEx BEM Report or using the LDEx API. This document focuses on the LDEX API data exchange method. 
Integrating the LDEx API into your case takes just a few steps:
<li>	Requesting required information, aka Coding Supplement, for setting up the LDEx Integration Provider
<li>	Creating the LDEx Integration Provider Adapter on the case
<li>	Configuring the LDEx Integration Provider Adapter on the case
<li>	Setting up EDI Group Numbers


==STEP 1: REQUEST NEW USER ROLE – API INTEGRATION==
Contact Selerix Technical Support (Support@Selerix.com) and request the API Integration role for your user account. 
This provides access to Integrations via the Data Management menu.  

==STEP 2: CONTACT THE CARRIER FOR REQUIRED INFORMATION==
Before you can connect to the carrier via the LDEx API, you must go through a few administrative steps.

# Contact your Carrier account manager/point of contact and request API integration with Selerix. There may be a fee for activating this service, dependent upon the carrier’s requirements. 
# The carrier will provide you with a Carrier Coding Supplement that provides all the group-specific information you need to complete the setup.


==STEP 3: CREATE THE LDEx API INTEGRATION ADAPTER==

'''To create a LDEx adapter for API integration with BenSelect:'''

#Login to your BenSelect site and select the case that will use the LDEx API Adapter.
#Go to Data Management >> Integrations. The Integrations page displays options for adding a new integration. 
#Click +ADD to create a new integration. The Add Integration dialog box opens. 
#Click the Adapter drop-down list and select LIMRA LDEx Integration Provider. 
#Click Add. The LDEx Adapter Setup page displays options. 
 
Now you can configure the LDEx adapter with the case-specific settings. Use the LDEx Configuration Spreadsheet for each field. 

==STEP 4: CONFIGURE THE LDEx ADAPTER==
Using the information from the carrier, enter the required information in each section of the LDEx Adapter Setup. Note that hovering your mouse over the label for each field provides additional information about the field.

===General Settings===
This section provides access to the following sub-sections:
<li> Basic Settings 
<li> Users
<li>Error Notifications

====Basic Settings====
<li>Name - Enter the name identifying the LDEx configuration in the list of active integrations.  Recommendation:  LDEx Connection for Group_name (# group_number).
<li>Company – Select the payroll company identified on the plans. Note: If you have defined LDEx as a provider, you can set up (in EDI Parameters) deduction codes that are separate from those defined as “Payroll Dept.” 
<li>Contact User – Select the user who is responsible for the setup of the integration. 
<li>Default User  - Select the user that you want to have associated with changes received from LDEx.
<li>Stability Delay – Select the time, in minutes, for the integration to wait in between events for the same employee. Recommended setting is 0.
<li>Deliverable – Associate a deliverable to the integration. This association ensures that any events exchanged via the LDEx integration are tracked on the employee’s EDI tab. Additionally, it ensures any issues associated with the integration are displayed on the Home page Deliverables widget. 
<li>Default Company ID – LDEx provides the value for this field. This can be associated with a location in the Locations section of the adapter. 
<li>Postpone if After – Set the date after which no data exchange should occur. 
<li>Enabled - When you have completed the setup, enable the integration by clicking Yes. Leave this option set to No until the integration setup is complete.
<li>Processing – When all adapter configuration is completed, set Enabled to Yes, then set Processing to Play.
<br>
NOTE: If the Enabled setting is set to Yes, but the Processing setting is set to Pause, BenSelect will receive “payloads” (aka decision information), but will not process them. These will be available for viewing on the Integration Dashboard in the Awaiting Approvals section.
<br> 
Caution: Do not turn off the integration once it has started running. This causes any decision information not to be logged into BenSelect; it would have to be re-sent to the system. However, if the integration is “paused”, the decision information is sent to BenSelect, and can then be processed when the Processing option is set to Play.

====Users Settings====
 
<li>Users – Add users to this list if you wish to allow them to change the configuration.  
<li>A user’s access to events processed by the configuration is controlled by granting the API integration role to the user. Contact Selerix Technical Support for assistance with this task. 

====Error Notification Settings====
This section contains options for notifications regarding the integration. 
 
<li>Send Error Notifications – Select this option to choose to Send error notifications from the case. 
<li>Notification Interval – Select how often error notifications should be sent. 
<li>From – This option is preset, based on the user currently logged into the case, going through setup. 
<li>To – Select the user to receive the notification. 
<li>Add – Click this button to add users to the notification.

===LDEx Parameters Settings ===
This section allows you to configure the source for the payer and the default user.  

<li>Payer - Select the primary payer for the integration. 
<li>Alternative Payer - Select the alternative payer, if more than one payer is identified, for the integration.
<li>Default User - Select the user that you want to have associated with changes received from the carrier 


====Connection Settings====
 Use this section to set the LIMRA settings, which will be provided by the carrier. 

The following fields are used to establish the initial handshake to the server; it’s a complicated setup for username and password to the carrier system. There are several fields that work together to establish a connection; not all fields need to be completed. For example, Client ID and Client Secret may be used together, and would not necessarily need the other fields completed.
<li>OAuth Type 
<li>OAuth URL 
<li>Client ID 
<li>Client Secret
<li>Client ID Header 
<li>Client Secret Header
<li>Username
<li>Password
<li>API Key Header
<li>API Key
<li>Audience 
<li>Scope
<li>Client Certificate
<li>Manual TLS

The following fields are optional, except for BEM Version and RSP Version. These must be set up for the data to be sent. 
<li>File Type
<li>Benefit Administrator
<li>Insurance Carrier
<li>Upload BEM URL  - Include the BEM Url, which may be different from the Oauth URL.
<li>BEM Version - Required field.
<li>Form Options – Select Form GUID. 
<li>Upload Rsp URL – Include the Response URL for the file.  
<li>RSP Version – Required field. 
<li>API Type – Select REST Services (Multipart), unless otherwise indicated by the carrier. 

==STEP 5: SET UP EDI GROUP NUMBERS==
To ensure that the right codes for the products are communicated through the LIMRA LDEx API integration, set up EDI Group Numbers. 
To set up the group numbers:
#Go to Case Setup >> EDI. The Electronic Data Interchange (EDI) screen displays tabs for setting up EDI parameters. 
#Click the Group Numbers  tab. 
#For each plan that you are sending, set up the products, associated payers, and group numbers, as specified in the Carrier Coding Supplement. 
#Click Save after you have set up all options.