LIMRA Data Exchange Standards Community Support Forum

From @Jaqui Payne

My query: <u5:p></u5:p>

Currently, I do not see that the committee has not offered guidance or a limit to the maximum number of iterations for the <EmploymentInformationUserDefinedCategory> complex element to populate the file for each employee. While I understand that a limit may be outside the scope of the mission of the committee, I am curious about feedback about what a reasonable expectation of a maximum number of iterations might be. The generic Coding Supplement layout is currently defaulted to 5 lines. While we can, in theory, accommodate an infinite number of iterations, it's causing technical concerns on our side, and would be a better experience if we set a max number instead. I'm currently toying with 5 to match the Coding Supplement. <u5:p></u5:p>

Current LDEx Standards implementers: What are your thoughts on limiting the number of repetitions of the EmploymentInformationUserDefinedCategory field? I currently tell organizations to avoid using this field at all costs, so limiting it to 5 repetitions is something I would at least consider. I am fairly certain we can do this by appending a maxOccurs="5" tag to the element. 

I agree, a limit would be ideal, and a better overall implementation experience for customers. If the variables in the EmploymentInformationUserDefinedCategory add up to more than 5 consistently, it might mean we're missing something that should be accounted for with common elements available in a coding supplement or additional attributes in the EmploymentInformation complex type. 

From @Jaqui Payne

My query: <u5:p></u5:p>

Currently, I do not see that the committee has not offered guidance or a limit to the maximum number of iterations for the <EmploymentInformationUserDefinedCategory> complex element to populate the file for each employee. While I understand that a limit may be outside the scope of the mission of the committee, I am curious about feedback about what a reasonable expectation of a maximum number of iterations might be. The generic Coding Supplement layout is currently defaulted to 5 lines. While we can, in theory, accommodate an infinite number of iterations, it's causing technical concerns on our side, and would be a better experience if we set a max number instead. I'm currently toying with 5 to match the Coding Supplement. <u5:p></u5:p>

Current LDEx Standards implementers: What are your thoughts on limiting the number of repetitions of the EmploymentInformationUserDefinedCategory field? I currently tell organizations to avoid using this field at all costs, so limiting it to 5 repetitions is something I would at least consider. I am fairly certain we can do this by appending a maxOccurs="5" tag to the element. 

From @Jaqui Payne

My query: 

Currently, I do not see that the committee has not offered guidance or a limit to the maximum number of iterations for the <EmploymentInformationUserDefinedCategory> complex element to populate the file for each employee. While I understand that a limit may be outside the scope of the mission of the committee, I am curious about feedback about what a reasonable expectation of a maximum number of iterations might be. The generic Coding Supplement layout is currently defaulted to 5 lines. While we can, in theory, accommodate an infinite number of iterations, it's causing technical concerns on our side, and would be a better experience if we set a max number instead. I'm currently toying with 5 to match the Coding Supplement. 

Current LDEx Standards implementers: What are your thoughts on limiting the number of repetitions of the EmploymentInformationUserDefinedCategory field? I currently tell organizations to avoid using this field at all costs, so limiting it to 5 repetitions is something I would at least consider. I am fairly certain we can do this by appending a maxOccurs="5" tag to the element.