LIMRA Data Exchange Standards Community Support Forum

During integration with a new trading partner, the coding supplement is requesting date values as BenefitClassIdentifier and BillGroupIdentifier  where the date values change over time as the employee changes BenefitSubClass or BillSubGroup respectively.

Example:

Bill Sub Class has 2 values, A and B

Employee moves from class A to B due to a location change on 10/1/2024. 

The carrier would like the date of 10/1/2024 as the value in the Benefit Class Identifier.

I've never seen dates set this way in a coding supplement, and I was wondering if this is supported this way within BEM.

The only date I see on the current coding supplement pertains to all the data values on the entire document. I do not at this time see an option to have different dates per data value. Is that what the carrier is asking for?

v

During integration with a new trading partner, the coding supplement is requesting date values as BenefitClassIdentifier and BillGroupIdentifier  where the date values change over time as the employee changes BenefitSubClass or BillSubGroup respectively.

Example:

Bill Sub Class has 2 values, A and B

Employee moves from class A to B due to a location change on 10/1/2024. 

The carrier would like the date of 10/1/2024 as the value in the Benefit Class Identifier.

I've never seen dates set this way in a coding supplement, and I was wondering if this is supported this way within BEM.

After further discussion within the LDEx Community Support team, we have moved this question into the BEM 2.1 future feature request issue (#485) on the LDEx BitBucket page. It will be discussed further for possible inclusion in the next BEM update. I'll update this tread with the results of any further discussions. 

------------------------------
Michael J Grudgings
Business Architect, Data Standards | LL Global, Inc.
300 Day Hill Road, Windsor, CT, 06095
t: (860) 298-3850 | mgrudgings@limra.com

Original Message:
Sent: 10-09-2024 09:12
From: Michael Grudgings
Subject: BenefitClassIdentifier and BillGroupIdentifier - Date Values

The only date I see on the current coding supplement pertains to all the data values on the entire document. I do not at this time see an option to have different dates per data value. Is that what the carrier is asking for?

v

------------------------------
Michael J Grudgings
Business Architect, Data Standards | LL Global, Inc.
300 Day Hill Road, Windsor, CT, 06095
t: (860) 298-3850 | mgrudgings@limra.com

Original Message:
Sent: 10-08-2024 14:58
From: Amanda Lund Anderson
Subject: BenefitClassIdentifier and BillGroupIdentifier - Date Values

During integration with a new trading partner, the coding supplement is requesting date values as BenefitClassIdentifier and BillGroupIdentifier  where the date values change over time as the employee changes BenefitSubClass or BillSubGroup respectively.

Example:

Bill Sub Class has 2 values, A and B

Employee moves from class A to B due to a location change on 10/1/2024. 

The carrier would like the date of 10/1/2024 as the value in the Benefit Class Identifier.

I've never seen dates set this way in a coding supplement, and I was wondering if this is supported this way within BEM.

#LDEx-BEM

------------------------------
Amanda Lund Anderson
Director, Integrations Engineering
Plansource
Salt Lake City UT
8018692781
------------------------------

As of right now, can I put a date value here? I have a request right now to do this, and my concern is making sure it is compliant before we agree to do this.

Elsewhere in the schema, dates are specified as 

------------------------------
Amanda Lund Anderson
Director, Integrations Engineering
Plansource
Salt Lake City UT
8018692781

Original Message:
Sent: 10-09-2024 15:56
From: Michael Grudgings
Subject: BenefitClassIdentifier and BillGroupIdentifier - Date Values

After further discussion within the LDEx Community Support team, we have moved this question into the BEM 2.1 future feature request issue (#485) on the LDEx BitBucket page. It will be discussed further for possible inclusion in the next BEM update. I'll update this tread with the results of any further discussions. 

------------------------------
Michael J Grudgings
Business Architect, Data Standards | LL Global, Inc.
300 Day Hill Road, Windsor, CT, 06095
t: (860) 298-3850 | mgrudgings@limra.com

Original Message:
Sent: 10-09-2024 09:12
From: Michael Grudgings
Subject: BenefitClassIdentifier and BillGroupIdentifier - Date Values

The only date I see on the current coding supplement pertains to all the data values on the entire document. I do not at this time see an option to have different dates per data value. Is that what the carrier is asking for?

v

------------------------------
Michael J Grudgings
Business Architect, Data Standards | LL Global, Inc.
300 Day Hill Road, Windsor, CT, 06095
t: (860) 298-3850 | mgrudgings@limra.com

Original Message:
Sent: 10-08-2024 14:58
From: Amanda Lund Anderson
Subject: BenefitClassIdentifier and BillGroupIdentifier - Date Values

During integration with a new trading partner, the coding supplement is requesting date values as BenefitClassIdentifier and BillGroupIdentifier  where the date values change over time as the employee changes BenefitSubClass or BillSubGroup respectively.

Example:

Bill Sub Class has 2 values, A and B

Employee moves from class A to B due to a location change on 10/1/2024. 

The carrier would like the date of 10/1/2024 as the value in the Benefit Class Identifier.

I've never seen dates set this way in a coding supplement, and I was wondering if this is supported this way within BEM.

#LDEx-BEM

------------------------------
Amanda Lund Anderson
Director, Integrations Engineering
Plansource
Salt Lake City UT
8018692781
------------------------------