Method and apparatus for monitoring events concerning record subjects on behalf of third parties

• US 20040039586A1
• Filed: 03/12/2003
• Published: 02/26/2004
• Est. Priority Date: 03/13/2002
• Status: Abandoned Application

• Current Assignee: Dharmendra Etwaru, Michael A. Garvey
• Original Assignee: Dharmendra Etwaru, Michael A. Garvey
• Inventors: Etwaru, Dharmendra, Garvey, Michael A.
• Application Number:
  US10/387,229
• Publication Number:
  US 20040039586A1
• Time in Patent Office: Days
• US Class Current: 705/1
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: G06Q 10/105 Human resources
• CPC Class Codes: G06Q 40/08 Insurance

Abstract

An event notification and risk monitoring system (10), for providing to an interested third party (15) (such as an employer) notification of events newly made part of public records of individuals, records related to the performance of tasks by the individuals, and for also providing values for metrics used in assessing risks associated with the tasks. One application is to provide event notification and risk monitoring for an employer for risks associated with drivers employed by the employer. The system (10) includes a database management and reporting system (11) and a record database (12), with the former populating the latter with information obtained from a source (14) of the public records (a source such as a state department of motor vehicles), information often in a non-standard format and so requiring that it be parsed and converted to a format suitable for business-to-business communications, a format such as XML.

Claims

1. A system (10) for use in connection with monitoring records of one or more subjects on behalf of a third party (15), the records of subjects being maintained by a monitoring party (14), the system characterized by:

a database management and reporting system (11), for providing a request for event information for the subjects, responsive to the event information, for determining event notifications based on parsing the event information, and for providing to the interested third party (15) the event notifications in a form predetermined to be intelligible to the interested third party according to predetermined routing instructions; and

a record database (12), for storing the predetermined routing instructions.

2. The system of claim 1, wherein the record database (12) is used by the database management and reporting system (11) to store event information so as to allow querying the event information to provide reports of event information for different time periods.

3. The system of claim 1, wherein event information is provided to the database management and reporting system (11) by the monitoring party (14) based upon an earlier request that the monitoring party (14) provide event notifications concerning the record subjects at or near the time when the monitoring party itself receives information on events concerning the record subjects.

4. The system of claim 1, wherein the predetermined routing instructions include information relating the record subjects to the interested third party, and also include instructions as to where event information is to be communicated.

5. The system of claim 1, wherein the records are driver records maintained by a state department of motor vehicles, the monitoring party (14) is the state department of motor vehicles, the subjects are employees of a company who drive vehicles as at least part of the work the employee is required to perform for the company, and the interested third party (15) is either the company or a related entity having in any case authorization to obtain and review the driver records of the employees.

6. The system of claim 1, wherein the records are credit reports of employees of a company and are maintained by a credit reporting agency, the monitoring party (14) is the reporting agency, the subjects are the employees, and the interested third party (15) is either the company or a related entity having in any case authorization to obtain and review the credit reports of the employees.

7. The system as in claim 1, further characterized in that the monitoring party (14) providing the event concerning the record subject is an automated event notification system for automatically providing event notifications according to coded registration information, and the system is further characterized in that it is responsive to uncoded registration information provided by the one or more associated interested third parties, the uncoded registration information being input using a form and an interface that error checks entries made to the form as the entries are being made, and in response to the uncoded registration information provides to the monitoring party (14) coded registration information, the coded registration information being in a form specified by the monitoring party (14).

8. The system as in claim 1, wherein after parsing the event information received from the monitoring party (14), the database management and reporting system (11) creates an extensible markup language (XML) document including the event information.

9. The system as in claim 8, wherein, in providing event notification to the interested third party (15), the database management and reporting system (11) communicates the XML document or a corresponding other XML-type document to the interested third party (15).

10. The system as in claim 9, wherein the corresponding other XML-type document is an HTML document or a WML document.

11. The system as in claim 8, wherein the database management and reporting system (11) populates the record database (12) using the XML document.

12. The system as in claim 11, wherein the database management and reporting system (11) retrieves event information from the record database (12) using a query, compares it with event information newly obtained from the monitoring party (14), prepares another XML-type document based on the comparison providing any changes to records of subjects since last obtaining event information from the monitoring party (14), and communicates the other XML-type document to the interested third party (15) by way of event notification.

13. The system as in claim 1, wherein the database management and reporting system (11) retrieves event information from the record database (12) and constructs a value for a predetermined metric representing risk indicated by the records of the subjects.

14. The system as in claim 13, wherein the risk metric is given by:

15. The system as in claim 1, wherein the database management and reporting system (11) performs event notification according to a proactive notification protocol (122) that refers to nodes of a reporting tree (121) for indicating to whom to report to in an organization of the interested third party (15), and how to respond in case of failing to receive an acknowledgment from the interested third party (15).

16. The system as in claim 1, wherein the proactive notification protocol (122) also indicates how often to obtain records of subjects being maintained by the monitoring party (14) on behalf of the interested third party (15).

17. A method for use in connection with monitoring records of subjects on behalf of a third party (15), the records of subjects being maintained by a monitoring party (14), the method characterized by:

a step (111) of obtaining updates to event information from the monitoring party (14); and

a step (112) of parsing the event information to create an XML-type document containing the event information for use in providing event notification to the third party (15).

18. The method of claim 17, further characterized by:

a step (114) of communicating the event information to the third party as an XML-type of document according to a proactive notification protocol (122).

19. The method of claim 17, further characterized by:

a step (115) of storing the event information in a record database (12); and

a step (116) of querying the record database (12) to provide reports of event information for different time periods.

20. The method of claim 17, further characterized by:

a step (117) of calculating values for a risk metric for each of the periods of time; and

a step (118) of communicating the risk metric values to the third party (15) as an XML-type document.