HCFA & UB92

     Thuriam processes HCFA 1500, UB92 forms daily by scanning/imaging these documents or accepting them from our clients via ftp and either by OCR or manual double key & verify process. The use of our key from image technology will allow us to route non-readable forms to this system where we will double key from images any unrecognized data. The output data is formatted into electronic claims that are transmitted to our clients in an ASCII comma delimited, flat ASCII, for processing.

     We can process individual HCFA and UB92 claims as well as dental claims. In the mail bin, the claims get opened, removed from their envelopes and sorted into separate piles: single sheet claims, multiple sheet claims, HCFA, UB92, Dental Claims, and miscellaneous other sheets which cannot be processed at quality level of each form. We will not process a document that does not contain a claim form; therefore, any claim or correspondence, whether single or multiple sheet, must always contain a claim form.

     The forms are scanned at 200-300 DPI depending on the quality of the form coming for process. During the time pages are scanned the fields are coded; OCR'd and validated for field content. If acceptable, a bate number is assigned. The pages are then imaged in a tiff format and batched. Critical to our process are two exception handlers. This exception handler allows the system to determine if the claims are good enough to OCR if they are not the claims is routed to our exception program where the claims will be keyed from image.

     We found that it is more effective for an operator to key all the data if more than 20% needs to be corrected. If we found more than one character wrong in a field it is quicker for our operators to key the whole field than try to fix it. Statistically, a more than 20% error rate means that most of the fields will contain more than one error.

     Once the forms are scanned and coded successfully they get assigned a bate number and an image number which is indexed in the final output file associated with that claim. The images get stored on our Server where we will keep them their for our clients to access them through our online search or will be transferred to a CD-ROM or Drive of their choice. The rejected pages are either re-scanned as images or once again routed to our exception key entry operators. While this is going on, our key entry workforces are looking for batches of images that need to be corrected or keyed. The batch is opened on a verification station creating a split screen displaying the image on the top and the zoomed in zone on the bottom and key entry fields below with any unreadable characters displayed by highlighting it in colour.

     Once the batch is complete, and the image record is marked as keyed, the automated job-flow process sends the batch through the output queue into a flat file holding the job in an ASCII or comma delimited format. At the end of the day we generate a transmission report with the file that details each of the batches, which were processed.