# US 2025/0094932 A1 · Enterprise real-time absence information portal

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2025/0094932 A1
- Document ID: US20250094932A1
- Status: Published application
- Kind: A1
- Application number: 18/467,010
- Filed: 2023-09-14
- Published: 2025-03-20
- Earliest claimed: 2023-09-14
- Assignees: Hartford Fire Insurance Company
- Inventors: Darren Michael Fayard; Laura Lirio; Dennis D. Pannella, JR.
- Web page: https://patentgrep.com/patent/US20250094932A1

## CPC

- G06Q 10/1091: Recording time for administrative or management purposes
- G06Q 10/0635: Risk analysis of enterprise or organisation activities
- G06Q 40/08: Insurance
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR

## Abstract

An absence data store contains electronic records associated with absence identifiers. For each absence identifier, the data store includes an employee identifier, an absence type, and absence parameters. An employee data store contains electronic records for accounts having risk relationships with an enterprise. A back-end application computer server may associate a selected absence identifier in the absence data store with an account having a risk relationship with the enterprise. The computer server may then retrieve absence parameters from the absence data store and risk relationship parameters from the employee data store and aggregate absence parameters associated with a plurality of absence types for the selected employee identifier. The computer server may also facilitate an exchange of data with a remote device to support interactive user interface displays that include information about the aggregated absence parameters.

## Claims

### Claim 1

An absence tracking system implemented via a back-end application computer server of an enterprise, comprising:
(a) an absence data store that contains electronic records associated with a plurality of absence identifiers, and, for each absence identifier, an employee identifier, an absence type, and absence parameters;
(b) an employee data store that contains electronic records associated with a plurality of accounts having risk relationships with the enterprise, and, for each account, employee identifiers and risk relationship parameters;
(c) the back-end application computer server, coupled to the absence data store and the employee data store, including:
a computer processor, and
a computer memory coupled to the computer processor and storing instructions that, when executed by the computer processor, cause the back-end application computer server to:
associate a selected employee identifier in the absence data store with an account having a risk relationship with the enterprise,
based on the selected employee identifier, retrieve absence parameters from the absence data store and risk relationship parameters from the employee data store, and
aggregate absence parameters associated with a plurality of absence types for the selected employee identifier; and
(d) a communication port coupled to the back-end application computer server to facilitate an exchange of data with a remote device to support interactive user interface displays that include information about the aggregated absence parameters.

### Claim 2 (depends on 1)

The system of claim 1, wherein the interactive user interface displays include at least one of: (i) an absence portal dashboard, (ii) an absence overview, (iii) absence filters, (iv) a return to work overview, (v) a new claim overview, and (vi) a claims denied overview.

### Claim 3 (depends on 1)

The system of claim 1, wherein the interactive user interface displays include at least one of: (i) an employee view, (ii) an employee intermittent absence view, and (iii) an employee continuous absence view.

### Claim 4 (depends on 1)

The system of claim 1, wherein the absence parameters include an absence status associated with at least one of: (i) approved, (ii) pending, (iii) denied, and (iv) closed.

### Claim 5 (depends on 1)

The system of claim 1, wherein the absence types include at least one of: (i) Short Term Disability (“STD”), (ii) Long Term Disability (“LTD”), and (iii) paid family leave.

### Claim 6 (depends on 1)

The system of claim 1, wherein the absence parameters include at least one of: (i) absence dates, (ii) an employee name, (iii) an employee gender, (iv) a date of birth, (v) a date of hire, (vi) an employee status, (vii) an expected return to work date, (viii) an intake method, (ix) a work state, (x) a date reported, (xi) a date of disability, (xii) a modified duty flag, and (xiii) a percent of benefit used value.

### Claim 7 (depends on 1)

The system of claim 1, wherein the enterprise is an insurer, the accounts are associated with businesses, and the risk relationships are associated with insurance policies.

### Claim 8 (depends on 7)

The system of claim 7, wherein the back-end application computer server is further to aggregate absence parameters associated with a plurality of employee identifiers.

### Claim 9 (depends on 1)

The system of claim 1, wherein the absence parameters include a communication address and the back-end application computer server is further to automatically create and transmit a notification to the communication address.

### Claim 10 (depends on 9)

The system of claim 9, wherein the communication address is associated with at least one of: (i) an email address, (ii) a telephone number, (iii) a user name and password, and (iv) a postal address.

### Claim 11

An absence tracking method implemented via a back-end application computer server of an enterprise, comprising:
associating, by a computer processor of a back-end application computer server, a selected employee identifier in an absence data store with an account having a risk relationship with the enterprise, wherein the absence data store contains electronic records associated with a plurality of absence identifiers, and, for each absence identifier, an employee identifier, an absence type, and absence parameters;
based on the selected employee identifier, retrieving absence parameters from the absence data store and risk relationship parameters from an employee data store, wherein the employee data store contains electronic records associated with a plurality of accounts having risk relationships with the enterprise, and, for each account, employee identifiers and risk relationship parameters;
aggregating absence parameters associated with a plurality of absence types for the selected employee identifier; and
exchanging data with a remote device to support interactive user interface displays that include information about the aggregated absence parameters.

### Claim 12 (depends on 11)

The method of claim 11, wherein the interactive user interface displays include at least one of: (i) an absence portal dashboard, (ii) an absence overview, (iii) absence filters, (iv) a return to work overview, (v) a new claim overview, and (vi) a claims denied overview.

### Claim 13 (depends on 11)

The method of claim 11, wherein the interactive user interface displays include at least one of: (i) an employee view, (ii) an employee intermittent absence view, and (iii) an employee continuous absence view.

### Claim 14 (depends on 11)

The method of claim 11, wherein the absence parameters include an absence status associated with at least one of: (i) approved, (ii) pending, (iii) denied, and (iv) closed.

### Claim 15 (depends on 11)

The method of claim 11, wherein the absence types include at least one of: (i) Short Term Disability (“STD”), (ii) Long Term Disability (“LTD”), and (iii) paid family leave.

### Claim 16 (depends on 11)

The method of claim 11, wherein the absence parameters include at least one of: (i) absence dates, (ii) an employee name, (iii) an employee gender, (iv) a date of birth, (v) a date of hire, (vi) an employee status, (vii) an expected return to work date, (viii) an intake method, (ix) a work state, (x) a date reported, (xi) a date of disability, (xii) a modified duty flag, and (xiii) a percent of benefit used value.

### Claim 17

A non-transitory, computer-readable medium storing instructions, that, when executed by a processor, cause the processor to perform an absence tracking method implemented via a back-end application computer server of an enterprise, the method comprising:
associating, by a computer processor of a back-end application computer server, a selected employee identifier in an absence data store with an account having a risk relationship with the enterprise, wherein the absence data store contains electronic records associated with a plurality of absence identifiers, and, for each absence identifier, an employee identifier, an absence type, and absence parameters;
based on the selected employee identifier, retrieving absence parameters from the absence data store and risk relationship parameters from an employee data store, wherein the employee data store contains electronic records associated with a plurality of accounts having risk relationships with the enterprise, and, for each account, employee identifiers and risk relationship parameters;
aggregating absence parameters associated with a plurality of absence types for the selected employee identifier; and
exchanging data with a remote device to support interactive user interface displays that include information about the aggregated absence parameters.

### Claim 18 (depends on 17)

The medium of claim 17, wherein the enterprise is an insurer, the accounts are associated with businesses, and the risk relationships are associated with insurance policies.

### Claim 19 (depends on 18)

The medium of claim 18, wherein the back-end application computer server is further to aggregate absence parameters associated with a plurality of employee identifiers.

### Claim 20 (depends on 17)

The medium of claim 17, wherein the absence parameters include a communication address and the back-end application computer server is further to automatically create and transmit a notification to the communication address.

### Claim 21 (depends on 20)

The medium of claim 20, wherein the communication address is associated with at least one of: (i) an email address, (ii) a telephone number, (iii) a user name and password, and (iv) a postal address.
