Gradually Changing the Capture Process

Our client is currently scanning lab test requests at their California office. These are prepared by having a PDF417 barcode label affixed to the document, which contains the main metadata value, called the Accession Number. Accessions (i.e., lab tests) are scanned, processed by the PaperVision Capture software to recognize the Accession Number, full-text processing is performed, and then the processed data is uploaded to ImageSilo for access from any office. They would like to begin processing their EOBs and other backup documents as well, so they are included on ImageSilo.

These supporting documents physically arrive at the office at a later date than the lab results, of course. The objective is that a single search of an Accession Number on ImageSilo brings back the lab results and any relevant backup documents, if available. It is important to note that some supporting documents, notably EOBs, contain information about multiple Accessions, and therefore must be duplicated so they appear in more than one Accession search. Ideally, this duplication process will not take additional space on ImageSilo.

Currently backup documents are sent for manual scanning and indexing before processing. Hard copies are then sent for manual hand-key entry into the billing-management system. This hand-key process consists of entering at least one unique reference then hand-keying individual line-item details.

Now, you can see the duplication and labour-intensive issues here, and, as a technologist, it’s easy to make the jump straight to sophisticated forms-recognition functions auto-populating the practice management system in the background, thereby eliminating errors, reducing labour requirements and making everyone’s life a lot easier. But it’s often not so clear cut. The user is already expending the labour, and even when you can show a clear ROI, they may not be ready to make the capital investment in forms recognition software, or they may not think their staff are ready to support the new process, or there may be concern about third-party vendor cooperation or even whether the third-party applications have the capability to back-end volume data imports, and the potential cost implications of those applications, et cetera, et cetera. So we go down a different road, the available road, and we begin to gently transition the process to better, at least, if not best.

Step 1: Immediate Changes to Capture All Supporting Documentation

The first step does not significantly reduce the amount of effort currently being expended, however remember that this wasn’t the primary objective. The main goal is to bring all supporting documents onto ImageSilo, so that lab results and supporting documents can be located with a single search.

In PaperVision Capture we create a new capture Job for scanning supporting documents. This new job has similar index fields as the primary lab results scanning job, with whatever additions are required, if any. The output data will load to the same project as current lab results so all documents are in the same place. (We considered different projects and global search methods, but it’s not really practical on this job, especially with the existing search integration from the web-based practice management application.) The scanning process will differ from the current barcode-breaking mechanism to include manual document breaking (we are investigating other methods, and whether barcodes could be made efficiently at this stage; I don’t think so, but possibly). We also add the document “duplication” process during indexing using PaperVision Capture Detail Sets functionality.

PaperVision Capture Detail Sets define a collection of indexes that allow multiple sets of field data to reference a single document. This will allow the user to create X number of “duplicate” database entries (where X is based on the number of accession references required per supporting document), and where the duplicates are only database entries pointing to the same image file(s) and not physical copies of the image. With the appropriate number of duplicate entries, the user can then begin manually indexing the various accession references that are present on the scanned document. The unique reference field (EOB reference or similar) automatically carries across all documents and is not indexed manually more than once (but will need to be indexed manually each time the detail set changes). Indexed documents are submitted and uploaded to ImageSilo automatically.

And our first objective – getting all the data online and accessible – is met.

Step 2: Automating the Indexing and Merge Process

At this point we will seek to change the process so that keying of data into the practice management system occurs before scanning. In this way, all the data entry has been completed and the indexing data is available for us to run database updates.

In short, this process would allow users to scan each supporting document, index only the unique reference number, and then use database update functionality native to PaperVision Capture to create the appropriate number of items in each detail set, and populate Accession references across all of those items with the data that has already been hand-keyed once.

So, we start getting more efficient on the data-entry at this point – instead of keying into the imaging system and then re-keying into the practice management application, we’re going to hand-key from hard-copy into the practice management and reverse the population of data into the imaging system (whereas normally we would seek for an imaging system to populate the accounting system. Remember, baby steps.).

We have a few questions on this part, of course, mainly around the best point of entry for accessing the hand-keyed data. Does the commit on the data entry process immediately generate a transmission into a reference database? Or are we waiting until the actual data merge takes place to pull data from the web-based application? We’re looking at methods now and our decision will, as ever, be based on the most efficient method for users.

But we also open up a couple of other areas of potential efficiency gains. Particularly we’d like to eliminate the hand-keying in the imaging system altogether, as well as improving the document break method. So at the data entry point, can we generate a unique 2D barcode reference that applies to the supporting document and kills two birds with one stone: the barcode becomes the automatic document break and populates our unique reference field, enabling automated details sets and bulk updates of accession references. That’s the question we’ll be asking ourselves in weeks to come.

One step at a time. But the sooner we can get to at least this step, the better for the client. At which point they will be a lot more open to re-visiting the ROI on a proper forms-recognition module that eliminates all hand-keying from the process entirely. Especially considering that they are seeing those volumes rise on a weekly basis already.


PaperVision Capture Code: Find Duplicates in Batch

Scanfree develops PaperVision Capture Code and Custom Functions for End-users and Service Providers.

A few Scanfree clients run very large batches through their PaperVision Capture stations. In some cases they’re running PaperVision Capture Automated Import Queues (AutoImport1.xml and AutoImport2.xml) that get created nightly. Others run large manual imports via the PaperVision Capture Operator Console. Whether automatic or manual, a scanning bureau will often find they have duplicates in a batch. Either duplicated images or, at the document level, duplicate metadata (index) field values.

PaperVision Capture maintains the old “Merge Like Documents” from PaperFlow 7.x days, This handy function checks index values and merges documents where all values imatch. But what does a scanning bureau manager do when not all index fields are identical, but certain values need to be checked for duplicates? Browsing the batch in the Operator Console is tedious. It’s not always easy to track down those dupes.

Scanfree has developed a solution. It is available now for any PaperVision Capture user. Service bureaus, in particular, will benefit from this (we use it in our scanning bureau), but so can end-users running PaperVision Capture scan stations.

The process is simple. The PaperVision Capture admin creates a job as normal in the Capture Administration Console. In the appropriate Operator workstep, insert a Custom Code command and import Scanfree’s PaperVision Capture Duplicates Report code. Then it’s just a matter of changing a few settings.

A setting within the code will tell the function which fields should be checked for duplicate values. It looks like this:

private string[] PVC_FIELDS_TO_SEARCH_FOR_DUPLICATES = {“Field1”, “Field2”, “Field3″}

Just change the quoted values to the exact field names of the PaperVision Capture Job. Don’t need to check three fields? Just add the one (or two) you’re after. A second setting in the code will define an output location for the report written by the custom code:

private const string REPORT_ROOT_FOLDER = @”C:\Reports\”

In this example we use a folder named Reports on the local C drive, but it could just as well be any accessible network location.

And that’s really all there is to it. The scan operator logs in to the PaperVision Operator Console and processes their batch as they normally would. When they’re ready they select the Execute Custom Code command within the Operator Console. A message will pop up to say the report has been written (or a message to say no duplicates exist). Open the report (which is time-stamp named) and the following report appears:




These examples show reports with one or two index values being tested, respectively. The final numeric value displays the number of duplicates found for each row item.

To learn more about PaperVision Capture visit our Products section. To learn about Scanfree’s Duplicates Reports go to our Development pages. (INSERT LINKS IN THIS SECTION TO CORRECT PAGES).

And incidentally, you can now run multiple instances of this report wll within the same batch, within the same workstep. For example, first run a duplicates test on Field1/Field2 combined, and then separately run a duplicates test on Field 3. In fact, you can now run as many pieces of custom code as you like all within a single operator workstep. We’ll write more about this one soon, but you can get a tech overview today by visiting the project page for the PaperVision Capture Functions Buttons (INSERT LINK HERE FOR THIS PROJECT).