LIMRA Data Exchange Standards Community Support Forum

 View Only
  • 1.  How is dependent coverage mapped in LDExBEM_2.0.JSON?

    Posted 02-07-2025 11:07
      |   view attached

    I understand how coverage is mapped to "employee" by way of Employer > employee > Employee > coverage.  How is coverage mapped to "dependent"?  Dependent is mapped Employer > employee > Employee > dependent > Dependent > {properties}.  However there is no "coverage" included in the Dependent?  Will some please help me think this through since I have a need to receive dependent coverages.  Thanks!


    #LDEx-API
    #LDEx-BEM
    #LDEx-JSON

    ------------------------------
    PAUL EHRSAM
    Quality Engineering (QE) Consultant
    Securian Financial Group
    ST PAUL MN
    651-665-4564
    ------------------------------

    Attachment(s)



  • 2.  RE: How is dependent coverage mapped in LDExBEM_2.0.JSON?

    Posted 02-10-2025 10:17
      |   view attached

    Dependents are built in the Dependent object then linked to any Coverage by using the CoverageInsured object, in the Coverage Object. You use the dependentPartyID as the InsuredPartyID in CoverageInsured to link a dependent to a coverage.

    Herer is a brief snippet of how CoverageInsured works. Attached is a larger example including the dependent object.

                                                                                    "Coverage": {
                                                                                                    "CoverageID": "O001",
                                                                                                    "GroupPolicyNumber": "R1234567",
                                                                                                    "ProductTypeCode": "Accident",
                                                                                                    "BenefitPlanIdentifier": "815",
                                                                                                    "CoverageEffectiveDate": "2024-07-01",
                                                                                                    "CoverageTierCode": "EmployeeFamily",
                                                                                                    "EmployeeContributionCode": "EmployeePaid",
                                                                                                    "EmployeePremiumContributionAmount": "32.53",
                                                                                                    "TotalPlanPremiumAmount": "32.53",
                                                                                                    "PaymentMethodCode": "PayrollDeduction",
                                                                                                    "PremiumModeQuantity": "12",
                                                                                                    "CarrierID": "MYCARRIER_ID",
                                                                                                    "CoverageInsured": [
                                                                                                                    {
                                                                                                                                    "InsuredPartyID": "916063",
                                                                                                                                    "PrimaryInsuredIndicator": "true",
                                                                                                                                    "InsuredCoverageEffectiveDate": "2024-07-01"
                                                                                                                    },
                                                                                                                    {
                                                                                                                                    "InsuredPartyID": "111111111",
                                                                                                                                    "PrimaryInsuredIndicator": "false",
                                                                                                                                    "InsuredCoverageEffectiveDate": "2024-07-01"
                                                                                                                    },
                                                                                                                    {
                                                                                                                                    "InsuredPartyID": "111121111",
                                                                                                                                    "PrimaryInsuredIndicator": "false",
                                                                                                                                    "InsuredCoverageEffectiveDate": "2024-07-01"
                                                                                                                    },
                                                                                                                    {
                                                                                                                                    "InsuredPartyID": "111131111",
                                                                                                                                    "PrimaryInsuredIndicator": "false",
                                                                                                                                    "InsuredCoverageEffectiveDate": "2024-07-01"
                                                                                                                    }
                                                                                                    ],



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

    Attachment(s)

    pdf
    Dependent.pdf   72 KB 1 version


  • 3.  RE: How is dependent coverage mapped in LDExBEM_2.0.JSON?

    Posted 02-10-2025 15:52

    Hello Michael -

    Thank you for explaining how to map dependent coverages in the JSON for LDEx BEM2.0.  Your explanation is easy to follow!



    ------------------------------
    PAUL EHRSAM
    Quality Engineering (QE) Consultant
    Securian Financial Group
    ST PAUL MN
    651-665-4564
    ------------------------------