Hi,
We had one question regarding the use of eventDate.
We are struggling with one partner in particular who is sending us both prior, current and future eventDates for a given employee payload. Even though the definition of the eventDate is an event that has already taken place.
The date on which a specific occurrence took place. Needed for Coverage. Change use case. Added in Version: 1.0.2020.01.14
Here are the scenarios (assuming current date is 05-21-2024)
- Some events given for active plan year that are backdated Ex. 05-18-2024
- Some events given for active plan year on current day 05-21-2024
- Some event given for active plan year in future days 05-22-2024
- Some event given for active plan year in future months 06-21-2024
- Some events given for next plan year 01-01-2025
They seem to be using the eventDate as a payload effective date – rather than the date on which an occurrence has taken place (below definition).
We are struggling to work with the backdated and future event dates as we cannot process them though the API at the time they are given since they are not yet 'effective' - or the fact that they might be outdated (if backdated)
This is causing us to come up with some 'not so API friendly' practices of maintaining/batching/holding events to be sent throughout internally at a later time – or even marking some as throwaway/outdated.
Limra Reference for EventDate
<xsd:element name="EventDate" type="xsd:date">
<xsd:annotation>
<xsd:documentation>The date on which a specific occurrence took place. Needed for Coverage
Change use case. Added in Version: 1.0.2020.01.14</xsd:documentation>
</xsd:annotation>
</xsd:element>
How should this eventDate be utlized and should a partner be sending future dated / backdated transactions with the use of the eventDate ?
#LDEx-General
#LDEx-API
#LDEx-BEM
------------------------------
Stephen Cocuzza
Tech Lead, Software Developer
Prudential
Newark NJ
+1 732 482 8920
------------------------------