Courts everywhere use specialized software to manage their core business functions, not unlike any standard business process in any organization. ImageSource has worked with many courts to promote their paperless initiatives and integrate with their case management systems (CMS), whether they have proprietary systems or they are using popular software like Tyler, JTI, Justice Systems, or Thomas Reuters.
The reasons to utilize electronic forms in the courtroom are obvious. Eforms can enable an end-to-end paperless process, eliminate inked signatures, manual approval stamping, scanning and filing. They can also require that complete and accurate data is submitted.
Some case management systems include electronic forms modules, but they have real limitations. Because they are commonly static PDF documents that lack many of the benefits listed above, progressive courts choose to integrate a more robust eForms software for several reasons:
With these advantages in mind, let’s take a look at a real-world application to show the difference specialized, robust eForms software can make.
In the case of some California Superior Courts, eForms are revolutionizing traditional processes. In the past, attorneys and their supporting staff would have to sift through inapplicable fields to fill a paper form. Some of the fields had to be hastily filled during a hearing and then handed to the judge for a signature. The paper would then be delivered to court clerks, who would review and time stamp the document, scan and manually enter pertinent data into the case management system. The document would then be uploaded to a repository or the CMS, sometimes requiring more keying of index fields.
When advanced electronic software is integrated with a CMS, an eForm can automatically pull information from that database to pre-fill pertinent fields, verifying data, saving time and ensuring accuracy. Responsive form technology automatically only shows applicable fields, revealing more of the form only when certain actions are taken, like checking a box. Additional functionality enables the process to be completely paperless to provide additional efficiencies to the process. They include:
This eForm functionality is not just impressive, but exponentially valuable when integrated with existing case management systems, like Tyler, JTI, Justice Systems, and Thomas Reuters. The good news is that integrating some products, like our ILINX eForms, doesn’t have to be difficult or complicated.
Using ILINX eForms as an example, let me outline an example of the synergistic relationship between the two platforms for both the push and pull of data. As mentioned above, the eForm is able to pull data from the CMS to pre-fill and validate data in the form fields.
Upon completion and of an electronic form during a hearing, the same workflow used for submittal and approval can begin a number of essential processes to push data. First, it can update the case management system with the data collected. Second, the data can be transformed into a digital document that looks like an official paper document that can be stored in the CMS, stored in a repository, shared or printed.
This image automatically retains relevant metadata so it can be easily searched for, making retrieval a breeze. Lastly, the data collected can be pushed to standardized forms, like the ones provided by the Judicial Council of California for Superior Courts to use, fully automating that process.
Data collected on eForm can be automatically pushed to a standardized PDF form, including signature
Imagine the possible applications across your organization for any process that needs to gather information and deliver it in a specifically structured document, or as raw data. Using the right form builder, your IT team can generate a wide variety of eForms internally, enabling granular control over function and the flow of information.
Using the courts as an example, a flexible eForms product like ILINX, can be extended to integrate with any number of business systems for better access and automation. Forms can be integrated with accounting systems for online invoice submission, status and resolution, procurement and expense reporting. Forms can be utilized by HR for onboarding, time-off requests and address/name changes. Public requests for court documents can be made through a web form. Payments for requested documents or fines can also be collected through a form. All this using one flexible platform.
These points highlight just how powerful the integration of a robust electronic forms platform can be, demonstrating the value that they add not just to a court system, but to virtually any organization.
For more information on ILINX eForms, visit our website, email us at info@imagesourceinc.com, or call (360)943-9273.
To learn more about ImageSource, and all of the content management services we provide, visit us here.
One message we consistently hear from government customers is how they need better solutions around records requests. With content growing at exponential rates, and huge implications around potential litigation, many organizations don’t feel that they have a good handle on it.
The ability to comply with public records request laws in any jurisdiction starts with good record-keeping, including disposition. Keeping a record past it’s retention period can be as big a problem as not keeping it long enough.
Here are some steps you can take to move toward better records practices:
If you’ve done the prep work correctly—analysis, inventory and technology partner and system selection—then what you’ve put in place will help you retain records exactly as long as required. If you’d like to learn more about ImageSource, our history, retention management and public records request solutions, please contact us today.
ImageSource has been successfully executing migrations, large and small, to and from content repositories since 1994. Recently, we completed a mammoth project for a global financial information services company in which we migrated 85 million documents from a deprecated Oracle 10g IPM system to ILINX Content Store in 9 months with 99.99995% accuracy. That’s zero loss of data, except a few hundred docs that were already corrupt in the source system!
The speed and accuracy of this project can be attributed to 3 important factors that made the content migration successful:
We’ve used a similar services formula for migration execution large and small—your migration doesn’t have to be massive like the one mentioned above to give you great ROI. That, and the right software mix, will eliminate headaches from the equation the next time you have to migrate content.
If schedules or other factors outside your control don’t allow time for a full migration prior to going live with your new system, we have a feature in ILINX Content Store that will allow customers to turn off their normal end user access to your legacy system on day one of using the new system and still pull content from the legacy system through the ILINX interface, read more about that here. This enables significant benefits that include smarter resource allocation within your operating constraints and migration flexibility. Contact us for more information.
Gene Eckhart, PMP
Project Manager
ImageSource, Inc
Two years ago, we helped one of the largest credit union in Alaska (17th in the nation at the time) automate their consumer loan processing operations. With a growing number of their 78 locations looking to processing auto dealership loan requests, Alaska USA Federal Credit Union needed to replace their manual, paper-based process to meet current and future demands.
As is the case with many lenders who haven’t yet gone electronic, paper loan requests packets were being submitted via multiple avenues from dealerships. These packets consisted of anywhere from 20 to 25 pages per packet with a variety of page sizes, file sizes and quality. Some documents were even printed from DOT Matrix printers at some of the dealerships. Packets came in primarily through fax and email, and local dealers in Anchorage would even hand deliver loan packets. Once received, faxes and emails were printed out and paper documents were used to process the loan request. The documents had to go through various people for review and approval creating a lot of manual movement of paper. Having these documents in paper format also created a need for document storage in file cabinets consuming significant floor space in the building.
In order to rise above the limitations that paper processing placed on loan approval volume, Alaska USA went digital, with 6 major automation improvements to shave valuable time off the process:
Having automated their Consumer Loan process, Alaska USA has greatly improved their service to auto dealers and can be more competitive on winning new business. On the cost savings side, they can process more loans without increasing headcount and have eliminated hard copy document storage.
For more information on ILINX eForms, visit our website, email us at info@imagesourceinc.com, or call (360)943-9273.
To learn more about ImageSource, and all of the content management services we provide, visit us here.
Migrations from systems like IBPM to ILINX can be fraught with issues that can bite the unwary in very bad places. However, if you are aware of such problems, you can plan ways to mitigate them and have a successful migration in the end.
One issue we run into is documents that have a page or two with corrupt images. Perhaps when the page was first contributed to IBPM, a system or other type of issue caused the image to be corrupt or cease to exist. Either physical hardware or a software bug can be the culprit. The product we use for migration, ILINX Export, will flag this document as an error, skip it and move on to the next document in RECID order. Once the export is completed, these flagged documents have to be re-visited. Once a determination is made that an image is indeed corrupt, and the chance to recover it from backups is extremely remote, the document can be deleted or manually exported from IBPM without the corrupt image.
Another matter we’ve dealt with is related to non-tiff images. This category is “universal” type images, and includes PDF, DOC, XLS, MSG and a host of other file types that IBPM supports. There are options within the ILINX Export tool that will allow the export of these files types in their native format through the IBPM SDK. Or the export can be done through database manipulation that can directly access the image file and then “unzip” the universal file into its native format.
The issue that can be encountered here is twofold, and manifests itself when migrating to another repository. One, IBPM stores the native file zipped up with another file that contains metadata and has no file extension. When the document is unzipped there are two files, one with a valid file type and one without. Typically, backend repositories require file extensions, which are useful for performance, like displaying file type icon on the user interface, and a variety of other reasons. During the migration, importing to the backend may be impeded due to a lack of extensions on the metadata files. Secondly, if the extension of the universal file has been altered or damaged in storage, the file type may not be a standard that the new repository will accept. In any case, having your migration come to a screeching halt is something to avoid.
Awareness is the key. By proactively incorporating a response into your migration plan, you can eliminate much heartburn and anxiety. That is where the expertise and knowledge of a seasoned Optika / Stellent / Oracle integrator, like ImageSource, comes into play. We have helped many customers build migration plans that take these and other items into account, so the migrations are as smooth and worry-free as possible.
Chris Hillenburg
Sr. Systems Engineer
ImageSource, Inc.
