HR-XML 3.0 Standards, 2009 September 23.
Menu: [ Home | Guidelines | BODs | Nouns | Global elements | WSDL | Packages | Code Lists | Master Index ]
Trace back: » pHLevel | ch06s03 | ch07s02 | ch07s03 | ch08 »
Table of Contents
The Indicative Data noun was specifically designed to support the communication of employee data from core HR systems to benefits and payroll service providers. However, because it covers a broad snapshot of human resource data, it is broadly applicable to many HR system integrations.
"Indicative" is defined by the Oxford English Dictionary as that which "points out, states, or declares."" In the context of benefits administration, the term refers to the practice of third-party administrators determining benefits eligibility and other administrative calculations on the basis of employee census data and plan eligibility rules. In other words, the census data points out or indicates eligibility based on plan rules. For example, plan rules may extend benefits to only certain classes of employees, such as those who are scheduled to work more than 35 hours per week or special levels or types of benefits may be available to employees, classified managers, and salaried professionals.
Note
The Indicative Data noun has "swiss-army-knife-like" utility for many HR system integrations. UserAreas make it easy to extend. However, it is not intended to be a complete set of "HR master data."
The IndicativeData specification typically would be used in integrations between a core HR system and the system of a benefit or payroll service outsourcer. However, IndicativeData, provides a broad snapshot of employee data that may be useful in integrations among many types of HR system actors.
Payroll Service. The service provider responsible for processing the payroll of the associated employer. Usually is an external, third-party service, but sometimes may be an internal service provider.
HRIS. An HRIS or "core HR system" combines such functionality as: employee data management, reporting, compliance, benefits administration, recruitment and applicant tracking, talent management, manager and employee self-service modules, and integration services.
Benefits Plan Administrator. A benefits plan administrator (or sometimes "third-party administrator" or "TPA") serves as recordkeeper for a benefits program, administers new enrollments and changes in plan elections, updates participant data to reflect businsess and life events, and administers legal compliance on behalf of an employer. The administrator also may provide on-line facilities for employees/participants to use in making elections, enrollments, and in gaining information with respect to their benefit programs.
Examples of events that could trigger the collaboration, include:
Hire. A "hire event" coincides with the point in time at which a person who has been a candidate becomes associated with an employer as an employee. Sometimes systems are pre-provisioned with information about an individual after he or she has accepted the offer, but before the employee enters-on-duty.
Life Events. This broad category of events covers such happenings in the lives of employees or plan participants as marriage, divorce, legal separation, marriage annulment, birth or adoption of dependent children, gain/loss of guardianship, death, disability, leave of absence, etc.
Personal Data Changes. These include events such as changes in personal information, such as government identifier, person name, home address, direct deposit account, etc.