Emulation process for making changes and revisions to computer data files

• US 20030037023A1
• Filed: 08/07/2001
• Published: 02/20/2003
• Est. Priority Date: 08/07/2001
• Status: Abandoned Application

• Current Assignee: IntelliClaim, Inc. (McKesson Corp.)
• Original Assignee: IntelliClaim, Inc. (McKesson Corp.)
• Inventors: Polyakov, Sergey, Lyakovetsky, Daniel
• Application Number:
  US09/924,259
• Publication Number:
  US 20030037023A1
• Time in Patent Office: Days
• US Class Current: 707/1
• CPC Class Codes: G06Q 10/10 Office automation; Time management

Abstract

The process of the present invention is an emulation process for automatically making changes and/or revisions to computer data files from a database of file records stored in a computer. The process includes the steps of identifying the events that occur while accomplishing a given task, recording in memory the operation of a human operator interacting with a graphical user interface of a computer to form one or more emulated responses to each event representing event handlers for performing the task, forming a collection of events for such task and a collection of the recorded emulated event handlers corresponding to each event for such task, selecting a batch of file records that require changes and/or revisions from the database of file records, loading a specified task and the recorded collection of events and emulated event handlers for such task into a computer; and executing the task on each selected file record by matching each emulated event handler in memory to a given event.

Claims

1. A process for automatically changing and/or revising data in a database of file records stored in a computer comprising the steps of:

identifying the events that occur while accomplishing a given task;

recording in memory the operation of a human operator interacting with a graphical user interface of a computer to form one or more emulated responses to each event representing event handlers for performing the task;

forming a collection of events for such task and a collection of the recorded emulated event handlers corresponding to each event in such task;

selecting a batch of file records that require the task to be performed to execute changes and/or revisions from a database of file records;

loading a specified task and the collection of events and emulated event handlers for such task into a computer; and

executing the task on the selected file record by matching each emulated event handler in memory to a given event.

2. A process as defined in claim 1 wherein the events loaded into the computer are randomly executed with each event being matched to an event handler until the last event occurs at which time the task is deemed successful and another task is loaded for execution.

3. A process as defined in claim 2 wherein if no response is found that matches an event the task is deemed unsuccessful followed by the step of either loading another file for modification or another task.

4. A process as defined in claim 3 further comprising updating file records when a task is deemed unsuccessfully executed followed by providing a printout of the unsuccessful claim file.

5. A process as defined in claim 3 wherein the file records are selected consecutively for implementing a given task.

6. A process as defined in claim 2 further comprising the step of minimizing the interactions in the emulation procedure to optimize the selection of event handlers for each event so as to reduce or eliminate unnecessary steps.

7. A process as defined in claim 6 wherein each emulated task is parameterized to include variables as a substitute for fixed values entered by the operator in response to an event.

8. A process as defined in claim 2 wherein the recording of each event for each task is analyzed to determine that all possible events needed to accomplish a specified task have been performed and if not the emulation procedure is repeated.

9. A process as defined in claim 1 further comprising the step of rerunning the task until the recorded emulated event handlers successfully reproduce the actions of the claims processor.