Here are some tips to get you started |
Information about the document that can be used for retrieval and rules processing. The information attached to the document should be as unique as possible for easy document searching. Examples of indexes include; client number, social security number, member ID, dollar amount, date, client name, etc. Indexes are the key data elements you can use to identify which member/applicant/client/account each document belongs to that enters the IWS system.
The act of data entering a user defined index (above) to go along with a new document when it is brought into IWS.
A general categorization to assign to a document in the system. Examples; Enrollment Form, HCFA form, Proposal, Contract, Payables Form, etc. Document types are defined and customized by each department in IWS.
These are the digital “inboxes” of IWS. Think of them as the “in basket” on someone’s desk, or their mailbox in the mail room. Queues can be setup for individual access, or for multiple staff to work from. You can name a queue anything you want. Like Document Types, Queues are customized and defined by each department.
A rule, or set of "if" conditions (Queue Logic), defined in the system by a user. A rule tells the system to what queue(s) (Queue Flow) the new document should be routed. The rule is based on the index data attached to the document.
"If statements" used on a Queue Rule to evaluate document indexes. Example: If the Index field EMPLOYEE_STATE equals "TX" then route the Document to the TEXAS DATA ENTRY Queue.
A list of Queues attached to a Queue Rule to which a document gets routed through when the Queue Logic rule is found to be true.