LIMRA Data Exchange Standards Community Support Forum

Hello,

Our teams and I are struggling to understand the LDEx RSP field definitions in JSON

Currently the glossary has definitions but are all based in XML where language like 'element' and 'complex type' do not directly translate in JSON terms.

Specifically these fields are a bit ambiguous/confusing

here are the ldex glossary definitions

referenceElement

Element within the payload identifying the record location of the Entity Code referenced in the Transaction Remark.

is this the parent object of the entityCode?

referenceElementID

Unique identifier from the payload for the Reference Element specified in the Transaction Detail.

so like employeeIdentifier for employee, coverageID for coverage, dependentIdentifer for dependent , employerPartyId for employer?

what identifiers are supposed to be used? 

entityCode

Complex type element in which the element identified in the Field Name is located.

does this mean the parent object name to the fieldName? like if its an error inside 'employer', 'employee', 'coverage' then these are the possible entityCodes  

entityReferenceValue

Populated value of the element being referenced in the payload.

Not sure how to interpret this one, isn the element being referenced the fieldName and theres already fieldReferenceValue for that?

and this is also required which makes it troublesome

fieldReferenceValue

Populated value of the element being referenced by the FieldName.

this makes sense for invalid population of given fields being referenced 

fieldName

Field Name is the actual element being referenced in the payload.

This one makes sense - its whatever field is causing the error 

example for missing or invalid employeeIdentifier , employeeIdentifier is your fieldName

There are also no populated samples in JSON for LDEx RSP

the current - LDExRSP_2.0.2024.09.13.instance.json - has fake populated values like below - which isnt too helpful

{
    "transmissionResponse": {
        "transmissionGUID": "YltbNduJPZAHvGUU",
        "sourceTransmissionGUID": "VBBfszFRlWVCQL",
        "transmissionStatusCode": "Success",
        "creationDateTime": "2024-09-13T12:50:23Z",
        "transactionDetail": [
            {
                "referenceElement": "OfferID",
                "referenceElementID": "hLdXECUrJoUpeyYCR",
                "transactionRemark": [
                    {
                        "entityCode": "RxRzJelkdtaQd",
                        "entityReferenceValue": "dnipaLNwfKiDiEQ",
                        "fieldName": "HlZDSpHHWN",
                        "fieldReferenceValue": "jD",
                        "remarkStatusCode": "Warning",
                        "messageTypeCode": "Duplicate",
                        "messageText": "ZEgwyONRBsuvZUENOnR"
                    },
                    {
                        "entityCode": "KxtCRpPyflOXknYFK",
                        "entityReferenceValue": "aCWmS",
                        "fieldName": "tFWtNai",
                        "fieldReferenceValue": "ZyG",
                        "remarkStatusCode": "OK",
                        "messageTypeCode": "Duplicate",
                        "messageText": "pPfi"
                    },
                    {
                        "entityCode": "yMGGsQm",
                        "entityReferenceValue": "ZKcdJaKqAMlXYaxd",
                        "fieldName": "eSGFjJbnjwHemPmqJa",
                        "fieldReferenceValue": "LasgbzCwLiWwaxAnEXyX",
                        "remarkStatusCode": "Warning",
                        "messageTypeCode": "Missing",
                        "messageText": "WCYvpDrUVE"
                    },
                    {
                        "entityCode": "uPeeMGd",
                        "entityReferenceValue": "YxvAk",
                        "fieldName": "cOyvCihIAQs",
                        "fieldReferenceValue": "WJjqsZR",
                        "remarkStatusCode": "Warning",
                        "messageTypeCode": "Invalid",
                        "messageText": "DlspbVFlmze"
                    }
                ]
            },
            {
                "referenceElement": "BenefitPlanID",
                "referenceElementID": "XAvgMpUUXF",
                "transactionRemark": []
            },
            {
                "referenceElement": "BenefitPlanID",
                "referenceElementID": "YZItftff",
                "transactionRemark": []
            }
        ],
        "transmissionRemark": [],
        "audit": {
            "auditID": "ggeJRFAOrc",
            "auditRecord": [
                {
                    "recordFieldName": "ykYzFSenfzbsytd",
                    "recordQuantity": 75
                },
                {
                    "recordFieldName": "PgLqMRv",
                    "recordQuantity": 65
                },
                {
                    "recordFieldName": "imDxcnXpqGYBVCHSjo",
                    "recordQuantity": 57
                },
                {
                    "recordFieldName": "luyDFLHhJTNO",
                    "recordQuantity": 54
                },
                {
                    "recordFieldName": "v",
                    "recordQuantity": 15
                }
            ]
        }
    }
}

#LDEx-BEM
#LDEx-JSON

------------------------------
Stephen Cocuzza
Tech Lead
Prudential
Newark NJ
9083770862
------------------------------

This should probably be a call. I'll reach out via email to schedule some time with you. 

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

I would recommend using XSD to familarize yourself with the schema.

For example using your json example and understanding the schema, i would follow this thought:

let's look at TransactionRemark object. annotation  has a very good explanation of what this object is for. I also see the type="rsp:Remark". having this information i would search in XSD further this "type":

as you mentioned - it's a complex type and cosist of multiple elements inside. EntityReferenceId, EntityCode, FieldName, etc.

For example "EntityReferenceID" that you asked about - is a simple type now, just a sting and annotation says that this identifier generated by requestor.

"EntityCode" on the other hand is another complex type of "Entity". I would to the same action and search for it in the document:

i can see it's ENUM and i know now all set of values i can expect in RSP for EntityCode.

Hope that helps with reading the schema!

------------------------------
Max Ignatov
CTO
BenefitScape
Natick MA
5086553307
------------------------------