An overview of the OOTB life events processing
Figure 1. OOTB life events processing
- On launch of the IEG Script that is configured for the life event, the pre-population hook that is configured for this life event is called to populate the data store. This implementation should adhere to “curam.citizen.lifeeventbroker.impl.DatastoreBuilder”. The implementation in Health Care Reform pre-populates information from Active Evidence records on the Health Care Reform Integrated Case, about citizen's household, existing jobs, existing ESC, and other information relevant to the life event. Few more information about the citizen's household are also populated in order to determine citizen's new Eligibility and entitlement determination as a result of the changes reported. This implementation is common for all the OOTB Health Care Reform life events. Default Health Care Reform Implementation is ‘curam.healthcare.lifeevents.impl.HealthCareDatastoreBuilderImpl’).
- In order to take the changes that are made to the Data Store and write them back to the IC as In-edit evidence changes, Health Care Reform has implemented a life event submission hook point that is given by Universal Access (curam.citizen.lifeeventbroker.impl.LifeEventUpdater). This implementation takes the changes reported in the life event script and turns them into evidence changes that can be reflected on the Insurance Affordability integrated case. (Default Health Care Reform Implementation name is ‘curam.healthcare.lifeevents.impl.HealthCareLifeEventUpdaterImpl’). The evidence changes here can be categorized into the following,
- Creation of new Evidence – This is done when new jobs, new employer sponsored coverage, or new additional incomes are reported through the life events.
- Correction of existing Evidence – This is done when existing jobs, employer sponsored coverage, or additional incomes are end dated and thus are no longer relevant.
- Change of circumstances – This is done when there is a change in circumstance such as increase/decrease in income.
Pre population of data store and submission hook points are bound by a Life Event Type Name to these default Health Care Reform implementations. These implementations can be extended by custom implementations, if needed.