Action

A concise procedure that is part of a rule. Together, a rule's action determines how a particular rules-based task is to deal with a specific component of an application's Document Hierarchy...a particular page or field, for example. An action belongs to a category such as Locate, Recognition, Validate, or Export. (These are just a few of the action categories.)

 

Actions Library

The combination of action categories that are available to rules of a specific RuleSet Type. Actions that belong to a particular category - Locate actions, for example - are part of a Rule Runner Actions file (.rra). A RuleSet Actions Library contains one or more files.

 

ADO

Active Data Objects that interface a supplementary task with special-purpose databases.

 

Admin Database

The application database, which contains definitions of workflows, jobs, tasks, users and workstations.

 

Administrative Privileges

Attributes of a User Definition designating the ability of an individual to access Taskmaster Web's administrative pages and data, and to carry out administrative functions.

 

Administrator Page

The primary management page of the Taskmaster Web Site. The secondary pages of the Administrator page define workflows, jobs and tasks - and install and maintain elements of Application Security.

 

Advanced Data Entry Panel

The Data Entry panel of an Advanced Verification Task. The panel's format and content are determined by the structure of an application's Document Hierarchy, and can be easily modified.

 

Advanced Monitor Filter Page

A page with multiple selection parameters that determine the size and scope of listings in the Batch Information Table of the Monitor Batches page.

 

Anchor

An element on a page that Taskmaster uses to determine the position and orientation of fields after the page has been scanned; anchors help Taskmaster compensate for skews that occur during scanning. Anchors are usually formed by the intersection of a horizontal and a vertical line, or by a symbol or a graphic.

 

Application

The principal organizing entity of a Taskmaster configuration. An application's Workflow Hierarchy organizes an application's processing entities at three levels: Workflow, Job and Task.

 

Application Security

Procedures that define and govern the access of individuals and workstations to an application's databases, jobs and tasks; and limit an individual's involvement in administrative activities.

 

Attachment

The image of an item of supporting documentation "attached" to the main document, for example medical test results which accompany a HCFA-1500 or UB-92 health claim. Each image becomes an Attachment page of the document and is stored as a .tif file in the batch containing the document. A document can have multiple Attachments.

 

Attended Task

An operation that involves human interaction. For example, Verification is an attended task, as it requires an operator to verify data.

 

AutoDelete

A Taskmaster utility you can use to identify those batches that meet your selection criteria, then delete some or all of these batches from the application's Batches directory. AutoDelete updates tables of Taskmaster's Engine database with the results of the deletion and retains evidence of the deleted batch, according to guidelines you prescribe.

 

Autofield

The third task in the Main workflow of Taskmaster HCcs. Autofield identifies the relative locations of key fields within the Image file representing a scanned HCFA-1500 (or UB-92) page, generates a Position file (.pos) with this information, and adds the .pos file to the batch containing the page. AutoField is the second of four Dynamic Recognition Client (DRC) tasks which can run without operator participation.

Autoform

A utility that uses the Field components of a Document Hierarchy to automatically assemble a Data Entry panel for an application such as Taskmaster Web.

 

AutoRouter

The fifth task in the Main workflow of a Taskmaster HCcs application, AutoRouter validates much of the data extracted from a HCFA-1500 or UB-92 page by the Recognition task. If all HCFA-1500 (or UB-92) pages in a document meet AutoRouter's requirements, the task splits the document form its batch and forwards the document directly to the QExport child job for processing by an Export task. AutoRouter is the last of four Dynamic Recognition Client (DRC) tasks, which can run without operator participation.

 

Bar Code Recognition

This form of recognition allows documents with pre-printed bar codes and bar-coded labels to be read with very high accuracy.

 

Batch

An application's processing vehicle and container. Usually created by a Scan task, the batch moves from task to task within a job, and is stored in an application's Batches directory. The contents of a batch typically include Image files, Data files, Batch Contents files and (optionally) Log files. Export files typically are not part of a batch; instead, they reside in a separate Export directory.

 

Batch Contents File (aka Page File)

A file generated by a task as it processes a batch. The Batch Contents file (.xml) contains identifying codes and processing statistics about the batch, and about the documents and pages the batch contains. After a task has finished with a batch and compiled the file, the next task in the workflow refers to the Batch Contents file for processing benchmarks.

 

Batch Number

A unique code assigned by the Scan task to identify a batch. Taskmaster supports various Batch Numbering formats. A standard format is YYYYMMDD.nnn. Also known as the Batch ID.

 

Batch Numbering

Alternative procedures to assign numbers to batches. Datacap provides Taskmaster Administrators with a set of Batch Numbering .dll files for 32-bit configurations: the Installation process includes these files in the File Server's Datacap directory: the files reside in the batchnew folder of the dcshared sub-directory.

Batch Pilot

The Taskmaster development workshop. Batch Pilot technology is responsible for the design, testing and implantation of Taskmaster tasks. The Batch Pilot workshop also constructs and maintains Rule Manager and the tools of the Rule Manager Window.

Batch Selection Mode

A property of a Taskmaster Job-Task shortcut.

BDOcs

An application using Datacap's Business Document capture system, which was developed to capture unstructured documents.  It is now known simply as Taskmaster.

Blob

A discernible imprint on the Image file of a scanned page. Soon after the Scan task generates an Image file, the Rule Runner task converts the image to a working fingerprint, locates all blobs on the page, treats each blob as a word and "recognizes" its value, and identifies lines on the page with one or more words.

 

Business Document capture system

See BDOcs.

 

Branching

Routing a batch from the task of a parent job to a task of a child job. Branching occurs in response to a Workflow Rule that is an attribute of the parent job. The Workflow Rule specifies the conditions under which branching occurs.

 

Captured Value

The value of a target word on a working fingerprint after it has been recognized, linked to a Field component of the Document Hierarchy, and added to the Data file of the page represented by the working fingerprint.

 

Character

The representation of a single value in a field of a page. A character can be a letter, a number, a decimal point, a mark in an OMR field or a filled-in radio button.

 

Character Smoothing

A form of image processing that improves the recognition of jagged and broken characters, and of characters printed with dot matrix printers.

 

Child Component

A component nested within a component of the same type on the Document Hierarchy.

 

Child Job

A secondary job whose tasks carry out special operations. Under conditions spelled out in a Workflow Rule, a task of the Main workflow can divert a batch or document to a child job for additional attention and possible repair - or sometimes for immediate export.

 

Classifiers

Classifiers are files that enhance recognition accuracy. Classifier files identify typical traits of a character set, thus allowing Taskmaster to more accurately recognize characters. For example, some recognition engines offer classifier files for American hand-print and British hand-print characters. If you were defining a FormSpec for a form that had been distributed in Great Britain, using the British classifier file would probably improve recognition accuracy.

 

Client/Server Mode

A networking configuration that places a supervisory Taskmaster Server between the Taskmaster Clients and the File Server that holds an application's files. Taskmaster Server manages the network as it continuously accesses products and applications on the File Server. The client/server mode is ideal for configurations employing numerous workstations.

 

Comb

Fields designed for hand written entry often use just the bottom halves of boxes to encourage form-fillers to write one character per box. A set of half-boxes is called a comb.

 

Component

An element of a workflow's Document Hierarchy. The hierarchy has components at four levels: Batch, Document, Page and Field. The properties of a component as well as the rules applied to the component determine how rules-based tasks process the component.

 

Condition

An unusual circumstance that a supplementary task might encounter while processing a batch. The process of Task Definition formally identifies any condition(s) associated with the task; the process of Job Definition determine which, if any, will be handled when the task runs as part of a particular job.

 

Condition Index

A zero-based index specifying a supplementary task's special processing conditions.

 

Confidence Level or Confidence Rating 

A value between "0" and "9"stipulating a minimum degree of certainty on the part of a "recognition" task that it has accurately interpreted data in a particular field of a source page, or has accurately recognized the page itself. "0" is the least stringent rating, while "9" means that Rule Runner will accept a field's value only if it has interpreted the value with complete confidence.

Context Recognition

In a given language, the probability that a given letter will precede or follow another letter can be statistically determined. For example, in English, if two consonants occur in sequence, it is probable that the following letter will be a vowel. Some recognition engines allow you to use context recognition.

 

Control

A component of the Datacap Form (dcf) which is a supplementary task's foundation. A control is the instantiation of an object, and has properties and methods. Most methods are subroutines for the control's Event Handlers. The Datacap Form (dcf) comes with two supervisor controls: UserForm and FormDriver. The developer also has access to a full set of User Interface (UI) controls.

 

Core Tasks

Tasks defined according to the specifications of Task Modules in four Taskmaster categories: Scan, Recog, FixUp (in three modes: Fixup, Verify or Rescan), and Export (ExportTX, ExportDB and ExportFS.)

 

Custom Rule

A rule defined to override or supplement the Global Rule that applies to a particular component of the Document Hierarchy. A custom rule is an attribute of a fingerprint.

 

Data Capture

Extracting data from printed documents and storing the data in an electronic format such as a text file or database. Data capture is usually performed by using a scanner in conjunction with character recognition software such as Taskmaster.

 

Data Type

The way a piece of data is represented and stored inside the computer. Taskmaster differentiates between text, floating point numbers, integers, dates and time. The data type of a field is defined in the Data property of the General tab.

 

Data Edit Field

An interactive field of a Verification task's Data Entry panel. A data edit field is linked to a particular field of a source page and may contain its recognized value. After reviewing the field's image, an operator can correct the value in the data edit field if there is an error.

 

Data Entry Panel

An interactive panel with fields that correspond to certain fields on a source page. A panel may present an operator with a field's recognized value alongside the image of the field and its value. After comparing the two values, the operator can make whatever changes are necessary to the value in the interactive data edit field.

 

Data File (.xml)

A file containing values in fields of a source page, and certain supplementary values. After a "recognition" task fully processes a source page, the task adds these values to a Data file it assembles just for that page. If the succeeding Verification task alters a value, the task updates the Data file.

 

Data QA Child Job

An optional Quality Assurance child job that examines the pages of every nth batch, after the batch has been processed by the Main workflow's Verification task.

 

Data Source Name (DSN)

ODBC Specifications define the link between a specific data source, usually a database such as an application's Engine or Admin database - and an Open Database Connectivity (ODBC) "driver". Microsoft's ODBC drivers allow a system using one type of database (an Access database, for example) to import data from a database of a different sort (perhaps a SQL Server database or DB2 database.)

 

Data Verification File (.dvf)

A file containing the Recognition task's interpretation of user-entered values in the fields and settings of a page. After processing is complete, Recognition adds the .dvf file to the batch containing the page's Image file (.tif ). If a succeeding task such as Verification alters an interpreted value, the task updates the .dvf file with the new value.

 

Datacap Form (.dcf)

The container that holds supplementary task's script and controls. The steps a developer takes to assemble and test the task occur within this structure. Running the task links the application to the form and, therefore, the application to the task. The Datacap Form is also a file (.dcf): for most applications, this file resides in the Process Directory.

 

Datacap HCcs

The Datacap Health Claims capture system, now known as Taskmaster HCcs, which is a pre-configured, HIPAA-compliant capture system built especially for payers, TPA's and other health claims processors to capture HCFA 1500 and UB-92 health claims.

 

Datacap Objects

Three objects whose methods and properties link the supplementary task's script to a Taskmaster workflow. The Task Object supplies the task with extensive supervisory data and settings - and returns data to the workflow. The Page Object retrieves, maintains and updates statistics about the current batch. The DVF Object retrieves and updates data in the Data Verification file for a specific page.

 

Design Mode (Task Builder)

The development mode of Task Builder, which permits on-the-spot scripting.

Dictionary; Dictionary File

A set of words used to help a recognition engine more accurately identify the information in a field. A dictionary file contains the words that a field is allowed or expected to contain.

 

DocEdit

A Datacap Taskmaster product for the design and operation of custom Data Entry panels. DocEdit's Data Entry functions and panels display processed data requiring operator review and, if appropriate, modification during the Verification task.

 

DocEdit Project Designer

The person(s) in an organization who defines DocEdit tasks.

 

Document

A key organizational and processing unit, consisting of one or more user-completed pages of specific Page Types. All files representing a document's pages are included in a one batch; one batch, however, may contain files associated with multiple documents. Page files (.pag) generated by each task track results for each document in the batch and for each page in the document.

 

Document Data

Standard identifying information about a document. This data appears in the D Line of a task's Page file - and is included in the Page.DocData property of the Page Object.

 

Document Discrepancy

A procedure that specifies the expected number of documents in a batch; counts the documents in each batch after processing by each task; and reports any discrepancies.

 

Document Identification Number (DIN)

A number the Scan task automatically assigns to a document. If the Custom tab of the Scan Task Setup box contains no overriding criteria, the DIN consists of a Batch ID, a period, and a sequential number identifying the document. Because Taskmaster is a zero-based system, each sequence begins with "0."

 

Document Index

A zero-based index which Taskmaster creates to track all documents in a batch.

 

Document Integrity

Settings that determine the required makeup of the documents in a batch in terms of the number and type of pages in a document. Once defined (usually as part of the Recognition Task) Document Integrity is an application-wide standard.

 

Document Loop

A coding sequence with the script that carries out the same procedure(s) for each document within a batch. Often, Page Loops are nested within a Document Loop.

 

Document QA Child Job

An optional Quality Assurance child job that sets aside every nth batch for the attention of a FixUp operator after Recognition has processed the batch. The Document QA job has four tasks: its interactive FixUp task is followed by Prep, Autofield and Recognition tasks.

 

Document User Data

Additional, user-specified information about a document. This data appears in the H line that follows each D line in a task's Page file.

 

Double Recognition

See multiple recognition.

 

DRC (Dynamic Recognition Client) 

A sequence of four tasks in the Taskmaster HCcs workflow that process a batch without operator intervention. The DRC sequence begins with the Prep task, immediately after the Scan task had set up the batch, and includes the Autofield, Recognition and AutoRouter tasks.

 

Dropout Color

An ink color that won't be recognized by a scanner equipped with the proper bulbs; for example, a scanner with red bulbs won't "see" document elements printed with the appropriate shade of red ink. Document elements such as instructions, field names, and check boxes can be printed in dropout colors, thus preventing these elements from appearing in scanned document images. You can greatly improve recognition performance and accuracy by using forms printed in dropout colors.

 

.dvf file

See Data Verification File.

 

DVF Object

An object Taskmaster can use to retrieve information from the Data Verification file representing a specific page within a batch. The properties of the DVF Object include information about a field and about the value it contains. The object's methods open and close Data Verification files, and extract and update their contents.

 

Endorsements

An identifying code certain scanners can print right on a scanned page.

 

Engine Database

The Taskmaster database, which contains processing results according to task, batch , document and page.

 

End Document Separator Sheet

An optional form placed after the last page in a document to mark the end of the document. These separator sheets are used only with multi-page jobs.

 

Export File

A file (.txt) generated by an ExportTX or ExportFS task at the end of the Main workflow, The file consists of Export records containing verified data from the pages of a fully processed batch. The format and content of the Export record is determined by the field-level specifications of the Export Task Definition.

 

ExportDB Task

An Export task that transfers data from Data Verification files and other sources directly to the tables and rows of an Access or SQL Server database.

 

ExportFS Task

An Export task that matches a field in the FormSpec with a field in the Data Verification file of a particular page. It then transfers the field's DVF data to the Export Record for the page. When the task has processed all FormSpec fields on the page, it closes the Export Record and moves to the next page. After it has processed all pages in the batch, the task places the corresponding Export Records in a text file (.txt) and adds the file to the application's Export directory.

 

ExportTX Task

An Export task that creates an ASCII text file for the batch it is processing. Then, according to the configuration specifications in the Task Definition, the task extracts data from a Data Verification file to assemble the Export Record. The Export Record of an ExportTX task can be short or long - just a few fields, or many. The fields can come from multiple sources...not only the FormSpec but from system and task "variables" as well.

 

Field

An element on a page with values entered by a user or by the system.

 

Field Area

The area of a form in which Taskmaster will look for a field's data during Recognition.

 

Field Name

The unique name assigned to each field of a form.

 

Filters

Settings that limit the scope of the Monitor Batches page's Batch Information Table - or restrict a task's processing to certain batches, documents or pages.

 

Fingerprint

The electronic template of a source page that can be processed by tasks of the Taskmaster workflow.

 

Fixed-Width Boxes

Fields designed for hand written entry often contain boxes to constrain and separate handprinted letters and numbers.  There is usually one box for each character that can be written.

 

FixUp Child Jobs

A child job that rescans faulty images encountered by a Recognition task, Verification operator or Supervisor, or re-structures documents with inaccurate or inadequate page counts and configurations.

 

FixUp Manager

A secondary window that becomes the FixUp operator's workshop and toolbox. The operator uses this window to review the structure of a batch, to select a page requiring attention, and to take corrective action. For the Verification operator, the FixUp Manager has more passive role, but is an essential source of batch information.

 

FixUp Tasks

Tasks that review and correct the recognized data on the pages in a batch; diagnosis and remedy problems with document size and content; or re-scan seriously faulty images. A FixUp task can operate in one of more of the following modes: FixUp, Rescan and Verify.

 

Fluid Value

The temporary value that a form-filler originally assigns to a field on a source page such as an Invoice page. When the Rule Runner task processes the page, it adds this value to the Data file of the working fingerprint which represents the page. At this point, the fluid value is also a captured value.

 

Form

1.) A paper entity consisting of one or more source pages with fields that record hand-printed or machine-printed data. 2.) The electronic interface between a user, and an administrative or operating facet of a Batch Pilot product. A Task Project, for example, consists of a Setup form and a Runtime form.

 

Formatting Task

A special-purpose Export task that formats Export Records according to standards set by the Health Care industry.

 

FormDriver

A standard, supervisory control of the supplementary task's Datacap Form (.dcf). The FormDriver has eight, "empty" Event Handlers ranging from OnInitialize to OnTimer...and four methods.

 

FormSpec

An ASCII file which assigns properties to an application's form, pages and fields and defines the properties of the electronic version of an application's paper form. Certain of these properties are accompanied by scripts. Workflow's script-based tasks refer continuously to a FormSpec as they process the contents of a batch.

 

FormSpec-level Property

Some properties can be set as a default for a FormSpec; these default properties can be overridden in corresponding properties of fields.

 

Form-Filler

The individual or mechanism responsible for entering fluid values in the fields of a source page (such as an Invoice page.) Taskmaster attempts to read and interpret these hand-printed or machine-generated values and the Verification task confirms the accuracy of these interpretations.

 

Global Rules

A set of default rules in each RuleSet Type that apply to specific components of the Document Hierarchy. Global Rules direct a task's involvement with the components of a working fingerprint unless the corresponding permanent fingerprint includes custom rules that intercede.

 

Global Template

The permanent "Fingerprint" for a standard, application-wide source page. The Global Template's format, fields and values are representative rather than real - and are used to define the application's Global Rules.

 

Groups

Sets of users responsible for identical jobs and tasks. Attributes of a User Group include the User ID's that designate its members, and the Job-Task Permissions assigned to the group and, by extension, to each member.

 

HCFA-1500 Form

The paper version of a Health Claims form submitted by doctors and health care agencies for reimbursement from insurance providers. The HCFA-1500 form has two sides: users of the form enter data on Side 1, while Side 2 has pre-printed instructions.

 

Hand-print

Data that is hand-written by a form-filler. Hand-print data is recognized by an Intelligent Character Recognition (ICR) engine.

 

High Confidence Value

A value in a field of a scanned page which the Rule Runner task interprets with a degree of confidence that equals or exceeds the application's requirements.

 

HIPAA

In 1996, the U.S. legislature passed into law the Health Insurance Portability and Accountability Act, which regulates the handling of health claim data, including formats, code sets and individuals with access to claims. 

 

History

An area at the top of the Taskmaster Web Site which lists the pages you've visited recently. Clicking on a Page ID returns you to that page.

 

Home Page

The opening page of the Taskmaster Web Site. The Home page welcomes you to Taskmaster Web, and provides instant access to the Web Site's other primary pages: Operations, Monitor and Administrator.

 

Intelligent Character Recognition (ICR)

Intelligent Character Recognition is a technique designed to read letters and numbers using a neural network recognizer that can distinguish characters even when they are written by different people with different writing implements.

 

Image File

An electronic representation a scanned page. The Image file is a digital picture of the actual page, usually stored as a .tif file.

 

ImageFix Task

A core task of Taskmaster's workflow, responsible for de-skewing and cleaning Image files before they are submitted to the scrutiny of recognition.

 

Index

A one-dimensional array, usually with two columns. The cells in one column are zero-based subscripts; the cells in the second column contain values to which the subscripts refer.

 

Interactive Editing

A synonym for Verification. The term "interactive editing" is sometimes used because Verification is turned on and off with the Interactive Edit checkbox in the Preferences tab. Job A set of interrelated Taskmaster tasks that operate together to accomplish a specific goal. Usually, the purpose of a job is to convert paper documents to captured data. Some special purpose jobs - a FixUp job, for example - handle problems with unsatisfactory images or document content. A job is a component of a workflow.

 

Job Monitor

A secondary window used by Administrators and Supervisors to track the workflow's activity at the batch level. The Job Monitor's Batch Information Table lists batches awaiting processing by specific Job/Task combinations; batches with a temporary Hold or Waiting status; and batches, which have completed a job's processing cycle.

 

Job Monitor Page

A secondary page of the Web Site's Monitor page, with extensive batch listings.

 

Job Rule

A rule in a Job Definition that lays out the conditions under which a task can divert a batch to a child job for special processing.

 

Job/Task Combination

The workflow's fundamental processing unit, forged by the assignment of a specific task to a specific job. Taskmaster's workflow prototype consists of four tasks assigned to a Main job: Main.Scan, Main.Recognition, Main.Verify and Main.Export.

 

Job-Task Permissions

Authorizations permitting individuals to carry out an application's Job/Task combinations. An application's Security Program includes these authorizations in its User, User Group, Station and Shortcut Definitions.

 

Job-Task Shortcut

An icon in Taskmaster Web's Operations page that initiates one or more Job/Task combinations. A shortcut is an element of Application Security: it is available only to authorized operators, Supervisors and Administrators working from a station with comparable Job-Task permissions.

 

Keyword

A title, phrase or other alphanumeric combination, which is reasonably likely to appear on a working fingerprint. Related keywords are stored in a keyword file: invnum.key, for example, lists the many variations of "Invoice Number." Certain actions of a Locate rule attempt to match values in a keyword list with keywords in the working fingerprint. Subsequent actions locate the target word that is associated with the keyword and retrieve its recognized value. KScan Task The standard task that opens the workflow by scanning the pages of paper forms, generating an Image file for each page, and assigning the pages to the processing batch it creates.

 

Local Station

See Station.

 

Log Files

Files that record events that occur when a task processes a batch.

 

Lookup Database

The database used by Validation rules of the Rule Runner and Verification task to confirm the fluid values in certain fields of a working fingerprint..

 

Looping Index

An index which provides processing parameters to a scripting sequence such as a Document Loop or nested Page Loop. Often, a Looping Index derives some or all of its values from an associated Property Index such as the Document Index.

 

Low Confidence Field

A field containing data about which the Recognition task is uncertain.

 

Low Confidence Page

A page that the Rule Runner task determines has one or more Low Confidence fields. A Low Confidence field contains one or more characters that are below the application's recognition threshold.

 

Machine-print

Any data that is printed on a page with a typewriter, a computer printer, or a typesetting machine. Machine-print data is recognized by an Optical Character Recognition (OCR) engine.

 

Main Job

A workflow's primary job, usually consisting of tasks in at least four categories: Scan, Recognition, Verification and Export.

 

Mark Sense

See Optical Mark Recognition.

 

Method

A function or subroutine of a Datacap Object, or of a control included in a task's Datacap Form (.dcf). Monitor Page A primary page of the Taskmaster Web Site that provides administrators and supervisors with current and historical information about batches, users and workstations. The Monitor page has four secondary pages: Job Monitor, Station Monitor, Web Monitor and Reports.

 

Multi-Page Job

An HCCS Main job which processes claims consisting of one or more HCFA-1500 (or UB-92) pages. There are two multi-page jobs: HCFA Main Sep and UB92 Main Sep. Multi-page jobs require the use of End Document separator sheets after each document in a batch except the last.

 

Multiple Recognition

The technique of using more than one recognition engine on a field and comparing the results; this is sometimes also called voting. Paper Keyboard's scripting language allows you to perform multiple recognition.

 

MultiTask

Datacap 2000 software that offers a developer both tools and a workshop to design, test and implement of an application's supplementary tasks.

 

MultiTask Builder's Kit (MBK)

The workshop within which a developer assembles a supplementary task. The MultiTask Builder's Kit has two components: the Task Builder constructs the task's Datacap Form (.dcf); the Task Definer gives the task a formal identity and workflow attributes.

 

Noise

When a document is scanned, some stray marks often appear in the scanned image. Most of these marks are in the original background of the document, or are inadvertently made by the form-filler. In addition, other stray marks come from flecks in the paper, smudges, folds, staple marks and other such imperfections. These latter marks are called noise. Paper Keyboard's image processing features allow you to remove or ignore these marks; the careful use of these features can greatly improve recognition accuracy.

 

OCR Field

An Optical Character Recognition field containing typed or computer-printed values.

 

OMR Field

An Optical Mark Recognition field containing one or more check boxes to be filled in by a user.

 

Operations Page

A primary page of the Taskmaster Web Site, with two secondary pages. The Select Shortcut to Run page lists the Job-Task Shortcuts an authorized operator uses to launch the Job/Task combination(s) assigned to the shortcut. The Run Batches for Selected Steps in Workflow page lets the operator select and run individual Job-Task combinations.

 

Operations Window

A secondary window within the Taskmaster Window. The Operations window displays shortcut icons an authorized operator, Supervisor or Administrator uses to initiate Job-Task activity.

 

Operator

An individual authorized by an application's Administrator to run one more tasks: Scan and Verification tasks usually require direct operator participation. Application Security procedures require a unique User ID and Password for each operator, and formal permission to carry out a specific Job/Task combination.

 

Operator-filled Field

A field representing a sector of source field on a processed page. Values in Operator-filled fields are often entered directly by Verification task operators and are always subject to operator review.

 

Options File

This file controls certain aspects of how Taskmaster will appear and operate; for example, the Options file determines the colors that Taskmaster uses to highlight various types of characters when operators verify data.

 

Page

The image of one side of a scanned form and the information it contains. The primary characteristics of a page are its Page Type and Page Status, and its position within a document. In the early stages of the Main workflow, a page is represented by an Image file (.tif). Later, a page is represented by the Image file, a Data Verification file (dvf) and an Export file (.txt).

 

Page Data

A Page file's standard information about a processed page in a batch. The Page file's P line contains this data.

 

Page Discrepancy

The difference between the expected number of pages in a batch, and the actual number. Standard tasks in all categories except Export will check for Page or Document Discrepancy if the Task Definition provides the applicable parameters.

 

Page File

A file generated by a task as it processes a batch. The Page file contains identifying codes and processing statistics about the batch, and about the documents and pages the batch contains. After a task has finished with a batch and compiled the Page file, the next task in the workflow refers to the Page file for processing benchmarks.

 

Page Group

A combination of pages representing different Page Types. The nature and number of Page Types in the Page Group forms the basis for a Document Integrity Rule that determines the acceptable makeup of documents within a batch.

 

Page ID Field

A field that identifies the page that is being processed. Used in multi-page documents, Page ID fields will contain document elements that uniquely identify the pages in a document.

 

Page Loop

A coding sequence within the script that carries out the same procedure(s) for each page. Often, Page Loops are nested within a Document Loop.

 

Page Object

A Datacap Object which is the interface between the Page file generated by the previous task in the workflow - and the current Page file, generated by the supplementary task. The Page Object's methods retrieve data from existing Page files and create new files; the Page Object's numerous properties ensure that each item of data is available.

 

Page Status

A value indicating the processing status of a page. The Page.GetStrPageStatus ( ) method of the Page Object retrieves this value from a Page file, and the Page.PageStatus property stores the value. In addition, the Page.GetPageNumberwith Status ( ) returns the number of pages in a batch with a specified status.

 

Page Type

A designation representing a specific kind of page. A form consists of pages of one or more Page Types.

 

Page User Data

A Page file's optional information about a processed page in a batch. Settings in the Scan Task Definition determine the content and format of the data, which appears in the I line of the Page file.

 

Panel

See Data Entry Panels.

 

Panel Modes

One of the three modes of a DocEdit Data Entry panel. The Design mode identifies the FormSpec Field IDs of the panel's fields and settings, and allows an Administrator to review the properties of the panel's objects.(fields, buttons, etc.). The Test mode displays the panel as it appears to a Verification task operator, adding sample data to its fields and settings. The Operating mode presents actual data to Verification operators, and governs the ways in which they review and modify values.

 

Paper Keyboard

Datacap's original forms processing product, which enabled scanning, recognition, verification and upload. The majority of Paper Keyboard's functions have been incorporated into Taskmaster.

 

PCX

A popular image file format.  Although the PCX format is not as efficient in terms of compression as the TIFF format, PCX is widely supported by many programs.

 

Permanent Fingerprint

The electronic template of a source page that can be processed by tasks of the Taskmaster workflow. A permanent fingerprint contains a complete set of rules that locate the fields on a corresponding working fingerprint; read, interpret and validate their data; and export the data to files or databases.

 

Picture Character

A character that represents the set of allowable values for a character position in a field. A picture string consists of picture characters.

 

Picture String

A string of one or more picture characters, entered in the Picture property of the General tab. A picture string acts as a filter, allowing certain characters to appear in a field and blocking out other characters.

 

Pixel

Each individual dot in an image file is called a picture element, or pixel for short. The number of pixels in a document depends on the scanning resolution, which is generally measured in dots per inch (DPI). Most document scanning is performed at 200 or 300 DPI.

 

Position Files

Some forms consist of multiple versions in which the fields are located in different positions. Position files store the physical positions of fields on a form's various versions.

 

Prep Task

The second task in the workflow, following immediately after the Scan task. The Prep task cleans and deskews the image of the scanned page. The Prep task is an unattended task: it does not require operator intervention.

 

Privileges

See Administrative Privileges.

 

Processing Mode

Settings files configure Taskmaster to perform Scan, Recognize, Verify, and Export operations consecutively or separately, and to have operations launched manually or automatically. These configurations are Taskmaster's processing modes. For example, one possible processing mode would configure Taskmaster to automatically batch-scan pages without performing Recognition or Verification.

 

Property

An attribute of an object or control. This attribute is defined in terms of its generic role and of an immediate value assigned to it.

 

QA Page

The secondary Manage QA Jobs page of the Administrator page that lists the elements of any special-purpose Quality Assurance jobs you've defined using the QA Job Properties sub-page. The properties of a QA Job Definition determine which batches will be diverted to the attention of Quality Assurance operators and supervisors.

 

Quality Assurance Child Jobs

Optional child jobs whose tasks regularly audit the results of the Main workflow's tasks.

 

Recognition

The extraction of data from scanned images. During Recognition, Taskmaster interprets the markings on a scanned image into letters, numbers, and other characters such as punctuation marks. Taskmaster also recognizes bar codes and check boxes.

 

Recognition Engine

Software a "recognition" task uses to read and interpret the values in the fields of a source page Usually, an application uses different engines to read machine-printed and hand-printed text, and to "vote" on values in certain fields.

 

Recognition Task

A standard task, which identifies each page in a batch, and each field on a page. The Recognition task interprets the values in those fields, then generates a Data Verification file (.dvf) for the page, and adds the interpreted values to the file. Recognition often re-structures the processing batch by creating documents and assigning pages to those documents.

 

Recognized Value

The interpreted value of a word on a page.

 

Remote Station

See Station.

 

Report Viewer

A Taskmaster utility that retrieves, organizes and displays an application's task statistics. These statistics track the performance of a task as it assembles and processes the contents of a batch - moving the batch from one task to the next until the data on every page has been read and recognized, verified and exported. Report Viewer can present results electronically or on paper. Coverage can be complete, or "filtered" according to parameters you provide. You can call upon Report Viewer for spur-of-the-moment details, or for a stream of information generated according to a schedule you define.

 

Reports Page

A secondary page of the Taskmaster Web Site's Monitor page. The Reports page generates Detail and Summary reports covering task activity.

 

Rescan

An option Taskmaster provides to an operator after a batch has been processed. The procedure re-processes the image of a hard-to-read page.

 

Rescan Tasks

A FixUp task in the Rescan mode. This task re-processes the image of a hard-to-read page. Rescanning occurs when a Verification operator or Supervisor sets aside a problem page for the attention of the FixUp operator. Typically, a task in this mode also operates in a FixUp mode.

 

Roll-backs

A procedure that takes a batch that has been "successfully" processed by a task and returns it to that task for a second round. A roll-back typically occurs when an operator or Administrator receives information that should have been included in a page within the batch before the page was processed. Note: Techniques for carrying out a roll-back differ from task to task.

 

Rule

A set of instructions that determines how a task is to carry out a narrowly-defined activity involving a single component of the Document Hierarchy. A rule consists of one or more actions. Rules are categorized according to their RuleSet Type: Locate rules, for example, find fields and their values; Export rules extract values from a Data file and add them to an Export file or database. Multiple rules of the same type that present alternative ways to deal with the same component form a RuleSet.

 

Rule Manager

Development technology responsible for definitions of an application's Document Hierarchy, Global Template, permanent fingerprints, rules, RuleSets and RuleSet Types. Rule Manager activities take place within the Rule Manager Window.

 

Rules-based Tasks

Tasks that operate in response to rules prepared exclusively for the application. These rules are applied directly to components of a Document Hierarchy that has also been constructed exclusively for the application.

 

Rule Runner Task

A core task of the Taskmaster Workflow Hierarchy, and the "brains" of the workflow's Main job. In response to its Task Project specifications, Rule Runner first identifies the page represented by the current working fingerprint.

 

Rules-based Application

A Datacap application with tasks that operate in response to rules prepared exclusively for the application. These rules are applied directly to components of a Document Hierarchy that has also been constructed exclusively for the application. The Document Hierarchy has components at four levels: Batch, Document, Page and Field. Rules are categorized according to RuleSet Type: Pre-Recognition, Recognition, Create Documents, Locate, Clean, Filter, Validation, Export and ExportClose. A rules-based application's Rule Runner, Verification and Export tasks run according to rules in one or more categories.

 

Rules Database

The database with complete information about an application's rules, actions and RuleSets - and their association with working fingerprints, permanent fingerprints and individual components of the Document Hierarchy.

 

RuleSet

A group of rules of the same RuleSet Type that apply to same component of the Document Hierarchy. As an example, the Locate rules that look for the Date field on a working fingerprint belong to the same RuleSet.

 

RuleSet Type

A category that defines the purpose of a particular RuleSet. BDOcs specifies nine default RuleSet Types: Pre-Recognition, Recognition, CreateDocuments, Locate, Filter, Clean, Validate, Export and Export Close.

 

Scan Task

A standard task that opens the workflow by scanning the pages of paper forms, generating an Image file for each page, and assigning the pages to a processing batch. Scan String An optional set of values specified in the Scan Task Definition. A portion of the Scan String, or the entire string, can be imprinted on a scanned page and appended to the Image file representing the page.

 

Scripts

Custom code that expands a FormSpec's scope and capabilities. A script can affect the overall form, or individual fields. An application may include scripts to customize the behavior of a verification panel or a special task.

 

Script-based Tasks

Tasks that process documents in response to the specifications of a FormSpec. Although the set up of individual tasks permits limited customization, an application's versatility results primarily from scripts that expand (or limit) a task's role as it processes a particular page, or a field within a page.

 

Script-based Application

A Datacap application that employs standard tasks to process documents in response to the specifications of a FormSpec. Although the set up of individual tasks permits limited customization, an application's versatility results primarily from scripts that expand (or limit) a task's role as it processes a particular page, or a field within a page.

 

Script Editor

The multi-faceted window used by the developer to prepare and test elements of a supplementary task's script, as well as the overall script. Security Procedures that define and govern the access of individuals and workstations to an application's databases, jobs and tasks; and limit an individual's involvement in administrative activities.

 

Separator Sheet

A form placed after the last HCFA-1500 or UB-92 page in a document to mark the end of the document (End Document), or after the last HCFA-1500 or UB-92 page in a claim (End Claim). Multi-page jobs require the use of End Document separator sheets.

 

Server

See Taskmaster Server, Taskmaster Web Server

 

Serverless Mode

The networking mode connecting Taskmaster Clients directly to the File Server that holds an application's resources instead of through a Taskmaster Server.

 

Settings File (.ini)

A file whose specifications govern certain aspects of the ways in which a task works, or determine the content of the Rule Manager Window.

 

Shortcuts

Items in the secondary Select Short to Run page of the primary Operations page. Clicking on a shortcut initiates the activities of a Job/Task combination that selects and processes a batch. An application's Security Program assigns properties to a shortcut and determines who can use the icon.

 

Shortcut Icon

An icon in the secondary Operations window of the Taskmaster window; double-clicking on the icon initiates task activities that select and process a batch. An application's Security Program assigns properties to an icon and determines who can use the icon.

 

Single-page Job

A Taskmaster HCcs job which processes claims consisting of a single HCFA-1500 (or UB-92) page. HCFA Main and UB92 Main are single-page jobs.

 

Snippet

An item in a DocEdit Data Entry panel that shows the image of data written or typed in a field. Operators compare the data displayed in snippets with the interpreted data in fields to determine the accuracy of data in documents.

 

Source Page

A scanned page containing values that are to be located, read, interpreted, verified and exported.

 

Special Tasks

Tasks to carry out exceptional processing or storage functions.

 

Split

A process that identifies a document within a batch that meets certain conditions, splits the document from the batch, and assigns the document to a sub-batch for further processing.

 

Standard Tasks

Tasks defined according to the specifications of Task Modules in four Taskmaster 2000 categories: Scan2k, Recog2k, FixUp2k (in three modes: Fixup, Verify or Rescan), and Export (ExportTX, ExportDB and ExportFS.)

 

StartBatch Data Panel

A panel that appears when a Scan task begins to ask the operator for specifics about the contents of the new batch. The panel's Pages in Batch amount becomes the workflow's expected number of pages in the batch.

 

Station Monitor

An administrative window with details about each workstation in an application's Taskmaster network.

 

Static Value

The constant value of a field on a working fingerprint - often, a pre-printed title or number that does not change from fingerprint to fingerprint. A field's fluid value, on the other hand, changes from one fingerprint to the next.

 

Station

A computer running Taskmaster Client software and authorized to carry out one or more Job/Task combinations. Also known as workstations, Taskmaster security assigns each an access code; an operator can use this computer to run a task only if it has a valid Station ID (and the operator has a valid User ID and Password).

 

Station Monitor

An administrative window with details about each workstation in an application's Taskmaster network.

 

Station Monitor Page

A secondary page of the Web Site's Monitor page. The Station Monitor page lists all workstations which are currently using the Task Master Web configuration to process batches. The page identifies each active station; its operator; the Job/Task combination it's running right now; and the number of batches in the task's queue.

 

Super Snippet

A type of snippet. The difference between a regular snippet and a super snippet is that a Verification task's operator can view a super snippet for a data entry field even though the panel does not contain a snippet for that field.

 

Supplementary Task

A task designed to augment the tasks of standard workflow by carrying out special or unusual steps.

 

Tagged Image File Format (TIFF)

Taskmaster's default image file format. Most scanners come with software that allows you to create TIFF files; you can also create TIFF files when scanning with Taskmaster. Taskmaster can read and write TIFF files in the uncompressed, Group 3 and Group 4 formats.

 

Target Directory

A folder on the File Server containing the Datacap files that have been copied from the Installation CD-ROM during the opening phase of the Installation process. During installation's second phase, this directory becomes the unambiguous target to which the Taskmaster Server will point as it searches for applications and data, if Taskmaster is running in a client/server mode. Similarly, Stage 3 will provide any client running in a serverless mode with a straight path to the target files.

 

Target Word

A word on a working fingerprint with a recognized value that is the target of a Locate rule's actions. A target word is associated with a keyword, and both are linked to a Field component of the Document Hierarchy. For example, on an invoice with these two values - Invoice Number MW31222 - the word on the left ("Invoice Number") is the keyword and the word on the right ("MW31222") is the target word - and both are associated with the Number Field component.

 

Task

The processing component of a Workflow Hierarchy. A task must be part of a job; a job must be part of a workflow. The task's identity is defined in Taskmaster when it is added to the Workflow Hierarchy. However, a rules-based task that is a product of the Batch Pilot workshop requires setup specifications and detailed settings from the underlying Task Project.

 

Task Definition

A specialized set of specifications resulting in a single-purpose task that can be assigned to a Main or child job. The Task Definition provides the task with its identity; designates a Task Module to serve as the task's design and operating template; and selects numerous options from a Task Setup dialog to customize the task's performance. Task Identity Elements of the unique identity that is a required component of a Task Definition.

 

Taskmaster

The administrative engine of an application. Taskmaster defines and manages the workflow-beginning with the physical scanning of a page, and ending when the values in the fields of a source page have been verified and exported.

 

Taskmaster Administrator

A secondary window of the Taskmaster Window, used to define an application's Workflow Hierarchy and Security Program. In a Taskmaster Web environment, the Administrator page is responsible for these procedures.

 

Taskmaster Clients

Components of a Taskmaster configuration responsible for initiating and monitoring tasks - and for accessing the application's databases and supporting files - through Taskmaster Server. The application's Security Program defines the scope of a client's activity: Administrative clients can carry out a full range of tasks and supplementary procedures.

 

Taskmaster Server

The component of a Taskmaster configuration responsible for linking the system's Engine and Admin database with Taskmaster Clients if Taskmaster has been set up in a client/server mode.

 

Taskmaster Web

A processing environment that uses a Taskmaster Web Site to link remote Taskmaster Web Clients to an application's administrative and operating functions. Taskmaster Web Client The component of a Taskmaster Web configuration that initiates and monitor tasks - and accesses an application's databases and supporting files - over the Internet through Taskmaster Web Server to the Taskmaster Web Site.

 

Taskmaster Web Server

The Internet Server which is host to the Taskmaster Web Site. The Taskmaster Web Server connects to a Datacap configuration's Taskmaster Server which, in turn, links clients to the configuration's File Server.

 

Taskmaster Web Site

Taskmaster Web's administrative and operating Internet Control Center. The Web Site features four primary pages: Home, Operations, Monitor and Administrator. Each primary page has a full set of secondary pages. Individual Help files explain the content and use of every page.

 

Task Module

Specifications that link a Task Definition to its setup and operating code, and to the Taskmaster Web environment. The Task Module also determines if a task will create batches, and if it can divert batches to special-purpose, child jobs if it encounters unusual processing conditions.

 

Task Monitor

A secondary, display-only window that appears as soon as a task selects a batch for processing, then provides up-to-the-second data as it tracks the task's progress.

 

Task Object

The Datacap Object that provides an interface between the supplementary task's script and the supervisory aspects of the Taskmaster operation. The object's "children" properties help define and manage a task's responses to exceptional processing conditions.

 

Task Specifications

The custom attributes of a particular task. An Administrator uses the Task Setup dialog to assign Task Specifications, in the third and closing phase of the Task Definition process.

 

Test Mode (Task Builder)

The mode of the Task Builder Window which allows a developer to test a script's new or revised code without delay. Tests Procedures that evaluate connections between a Taskmaster Web Client and the Taskmaster Web Server.

 

Threshold Percent

The amount of a check box that must be filled, expressed as a percent of the total area, before Taskmaster will consider the check box as being marked by a form-filler.

 

UB-92 Form

The paper version of a Health Claims form submitted by hospitals and clinics for reimbursement from insurance providers. The UB-92 form has two sides: users of the form enter data on Side 1, while Side 2 has pre-printed instructions.

 

UB-92 Page

The image of, and data in, a completed UB-92 form. Taskmaster HCcs uses the page's image to extract and verify the data it contains.

 

Unattended Task

An operation that does not require human interaction. For example, Taskmaster's Recog task allows you to define a workflow in which Recognition is an unattended task-scanned images will automatically be forwarded to the Recognition workstation, which will automatically process the images and then automatically forward the recognized data to the next workstation in the workflow.

User

1. An individual who fills out the fields of a paper copy of a form. 2. An individual who has access to a Taskmaster application and its databases. The application's Security Program provides each user with a User ID and Password, and specify the limits of a user's processing and database access "privileges."

 

User Interface (UI)

The interactive and passive controls that are part of a UserForm, and accessible to a user - operator, Supervisor or Administrator - when the task runs.

 

Validation

The process of making sure that a field's value meets specified criteria. For example, the criteria for a field might be that the field can only contain a number within a range of numbers. Validation is a useful way of assuring that all data meets certain requirements and is ready for useful reporting.

 

VBScript

A powerful scripting language that uses the Windows Script Host to run within the Windows operating system. Scripts for a supplementary task can be written in VBScript (our recommendation) or in PerlScript or JScript.

 

Verification

The review and correction of data that has been previously recognized. By default, Taskmaster will present only low-confidence fields to operators for Verification. However, you can also configure Taskmaster to present all fields to Verification operators.

 

Verification Task

A FixUp task in the Verify mode. This task retrieves information from the Image (.tif) and Data Verification (.dvf) files of a "problem" page. The Verification task presents the operator with the Low Confidence characters in "Low Confidence" fields throughout the page, then moves to the next problem page until the batch is verified. A Verification task often comes right after a Recognition task as part of the workflow's Main job.

 

Voting

Internal procedures of a Recognition task that use multiple Recognition engines to read and interpret the value in a field. These procedures include an algorithm that settles on the most satisfactory interpretation of the value.

 

Web Monitor Page

A secondary page of the Web Site's Monitor page. The Web Monitor page provides network information about all Taskmaster Web Client workstations currently linked to Taskmaster Web.

 

White Space

An area on a printed document in which nothing is printed. For best results, Paper Keyboard requires some white space around anchors and fields in order to distinguish them on the page.

 

Workflow

The top level of a Taskmaster application's Workflow Hierarchy. A workflow includes jobs, the tasks assigned to a job, any child jobs that branch from the job, and the tasks of these child jobs.

 

Workflow Development Rules

Sixteen rules that govern the design, development and implementation of a Workflow Hierarchy and its components - workflow, job and task.

 

Workflow Hierarchy

The formal structure, which an application employs to retrieve, interpret, verify and store the data on a scanned page. A Workflow Hierarchy has three tiers. At the top is the workflow itself, which focuses on a particular form or operates within a particular environment. Jobs are components of a workflow and occupy the second tier: a workflow usually has a Main job, and may have child jobs to handle special functions. Tasks are components of a job, and occupy the hierarchy's third tier.

 

Workflow Rule

A rule in a Job Definition that lays out the conditions under which a task can divert a batch to a child job for special processing.

 

Zone

A tightly-defined area that surrounds a Field component of a permanent fingerprint. The area's parameters - its size and location - are properties of the component, and are transmitted to working fingerprints that rely on this permanent fingerprint for guidance. The zoning mechanism's tools are in the Zone Hierarchy sector of the Rule Manager Window's Fingerprints panel.