Component based interface to handle tasks during claim processing

• US 20050149376A1
• Filed: 12/20/2004
• Published: 07/07/2005
• Est. Priority Date: 05/04/1999
• Status: Abandoned Application

• Current Assignee: Accenture LLP (Accenture PLC)
• Original Assignee: Accenture LLP (Accenture PLC)
• Inventors: Guyan, George V., Pish, Robert H.
• Application Number:
  US11/017,086
• Publication Number:
  US 20050149376A1
• Time in Patent Office: Days
• US Class Current: 705/9
• CPC Class Codes: G06Q 10/06311 Scheduling, planning or task assignment for a person or group
• CPC Class Codes: G06Q 10/063114 Status monitoring or status determination for a person or group
• CPC Class Codes: G06Q 10/06316 Sequencing of tasks or work
• CPC Class Codes: G06Q 40/02 Banking, e.g. interest calculation or account maintenance credit or loans G06Q40/03
• CPC Class Codes: G06Q 40/08 Insurance

Abstract

A computer program is provided for developing component based software capable of handling insurance-related tasks. The program includes a data component that stores, retrieves and manipulates data utilizing a plurality of functions. Also provided is a client component that includes an adapter component that transmits and receives data to/from the data component. The client component also includes a business component that serves as a data cache and includes logic for manipulating the data. A controller component is also included which is adapted to handle events generated by a user utilizing the business component to cache data and the adapter component to ultimately persist data to a data repository. In use, the client component is suitable for receiving a plurality of tasks that achieve an insurance-related goal upon completion, allowing users to add new tasks that achieve the goal upon completion, allowing the users to edit the tasks, and generating a historical record of the tasks that are completed.

Claims

1. -21. (canceled)

22. A method for automatically generating tasks to be performed in an insurance organization, said method comprising the steps of:

monitoring a transaction database comprising information relating to an insurance transaction;

identifying an event associated with a change in said information;

retrieving rules stored in a rules database in response to said identified event, said retrieved rules being associated with said identified event; and

determining a task to be completed based on said retrieved rules.

23. The method of claim 22 further comprising a step of assigning said task to a claim handler or group of claim handlers for completion.

24. The method of claim 23 further comprising a step of providing said task to a client component accessible by an assigned claim handler.

25. The method of claim 22 further comprising a step of displaying information associated with said task on a user interface.

26. The method of claim 25 further comprising a step of identifying said task as completed.

27. The method of claim 26 further comprising a step of recording the completion of said task in said transaction database.

28. The method of claim 25 further comprising a step of capturing data entered through the user interface and storing said data in said transaction database.

29. The method of claim 22 further comprising a step of inputting at least one new rule into a library rules interface and storing said at least one new rule in said rules database.

30. The method of claim 22 wherein said step of monitoring a transaction database containing information relating to an insurance transaction comprises monitoring a claim for compensation under an insurance policy.

31. The method of claim 26 further comprising the steps of:

generating a task list of assigned tasks that have not been completed;

displaying said task list on the user interface; and

adding, editing, or deleting a task from the task list in response to a selection by said user.

32. A method for automatically generating tasks to be performed in an insurance organization, said method comprising the steps of:

monitoring a transaction database comprising information related to an insurance transaction;

identifying an event associated with a change in said information;

retrieving rules stored in a rules database in response to an identified event, said retrieved rules being associated with said identified event;

determining a task to be completed based on said retrieved rules;

providing an organizational database containing attributes relating to organizational entities and an organizational structure of the insurance organization, the attributes comprising employee name, employee number, group, office, division, employee relationships, employee reporting hierarchy, employee role, and employee authority level;

said attributes having defined relationships with other attributes to define the organizational structure;

associating a transaction in the transaction database with one or more organizational entities stored in the organizational database;

assigning said task to an employee for completion, the assigned employee having a defined relationship to the associated organizational entity; and

providing said task to a client component accessible by the assigned employee.

33. The method of claim 32 further comprising a step of displaying information associated with said task on a user interface and capturing data entered by way of said user interface.

34. The method of claim 33 further comprising a step of identifying said task as completed and recording the completion of said task in said transaction database.

35. The method of claim 32 further comprising a step of inputting at least one new rule into a library rules interface and storing said at least one new rule in said rules database.

36. The method of claim 32 wherein said step of monitoring a transaction database containing information relating to an insurance transaction comprises monitoring a claim for compensation under an insurance policy.

37. The method of claim 32 further comprising displaying sufficient attributes from the organizational database to track where an employee falls within the organization structure.

38. The method of claim 32 further comprising displaying groups of employees assigned to an insurance transaction.

39. The method of claim 32 further comprising displaying an insurance transaction allocation within the organization structure.

40. The method of claim 32 further comprising storing in the transaction database a role of the one or more organizational entities associated with the transaction.

41. The method of claim 32 wherein the insurance transactions relate to the handling of insurance claims, and the organization is an insurance claims adjusting organization.

42. The method of claim 32 further comprising a code segment stored on computer readable medium for retrieving the authority level attribute of said assigned employee, and granting permission to a second employee to access data authorized for access to the assigned employee where a stored reporting hierarchy of the second employee indicates the assigned employee is a subordinate of the second employee.

43. The method of claim 32 further comprising maintaining current and historical associations between transactions and organizational entities, and displaying all organizational entities currently and historically associated with a transaction.

44. A system for assigning tasks to a claims handler in an insurance organization, said system comprising:

a data component storing information associated with claims handled by said insurance organization and tasks to be performed by said claims handler; and

a client component coupled to said data component, said client component having a user interface adapted to receive a task of said plurality of tasks in response to a change in information.

45. The system of claim 44 wherein said client component further comprises a user interface controller.

46. The system of claim 45 wherein said client component further comprises a user interface form coupled to said user interface controller.

47. The system of claim 44 wherein said client component further comprises a client component adapter.

48. The system of claim 45 wherein said client component further comprises a business object.

49. The system of claim 44 further comprising:

a second data component coupled to said client component, said second data component storing attributes relating to organizational entities and an organizational structure of the insurance organization, the attributes comprising employee name, employee number, group, office, division, employee relationships, employee reporting hierarchy, and employee role;

said attributes having defined relationships with other attributes to define the organizational structure;

said stored attributes including an identification of said claim handler.

50. The system of claim 49 wherein said client component further comprises a second user interface adapted for searching for an entity stored in the second data component based on any stored attribute having a defined relationship with the entity.

51. The system of claim 50 wherein said client component further comprises a third user interface for adding and editing an entity stored in the second data component.

52. The system of claim 51 wherein the stored attributes further comprise an authority level associated with each organizational entity;

and the third user interface is accessible to entities having a predetermined authority level.