Technical FAQs

Question

What quality should my images be for processing form data and recognition using FormSuite?

Answer

In all cases, you want to have your images as clear and as clean as possible. For any particular procedure, please consider the following:

OCR and ICR: Capture images in at least 300 DPI resolution. Ideally, working in black and white allows the objects of interest on your image to be better defined and recognized. Free the image form all noise as much as possible. As if a human were reading it, you want the text objects on the image to be as legible as possible. For ICR, ensure that the characters are printed (no cursive text, etc).

Barcode recognition: As with OCR and ICR, capture images in at least 300 DPI and working with black and white content can provide excellent results. Ensure that the bars in the barcodes are clearly defined on the image and are not malformed (for example, the barcodes should have the proper start and stop sequence, etc). Clear as much noise from the image as possible.

Forms matching and registration: As with the prior 2 items above, capture your documents in at least 300 DPI. Ensure that your resolution is consistent between your form templates and incoming batch images. Form templates should only contain data that is common to every image that is being processed (i.e. Form fields, the text that appears on the blank form itself, etc). The template should not have filled-in field information as this will affect the forms matching process.

Question

What quality should my images be for processing form data and recognition using FormSuite?

Answer

In all cases, you want to have your images as clear and as clean as possible. For any particular procedure, please consider the following:

OCR and ICR: Capture images in at least 300 DPI resolution. Ideally, working in black and white allows the objects of interest on your image to be better defined and recognized. Free the image form all noise as much as possible. As if a human were reading it, you want the text objects on the image to be as legible as possible. For ICR, ensure that the characters are printed (no cursive text, etc).

Barcode recognition: As with OCR and ICR, capture images in at least 300 DPI and working with black and white content can provide excellent results. Ensure that the bars in the barcodes are clearly defined on the image and are not malformed (for example, the barcodes should have the proper start and stop sequence, etc). Clear as much noise from the image as possible.

Forms matching and registration: As with the prior 2 items above, capture your documents in at least 300 DPI. Ensure that your resolution is consistent between your form templates and incoming batch images. Form templates should only contain data that is common to every image that is being processed (i.e. Form fields, the text that appears on the blank form itself, etc). The template should not have filled-in field information as this will affect the forms matching process.

insurance claim form automation

 

When it comes to the COVID-19 crisis, the only constant is change. As noted by Insurance Business Magazine, this creates a “growing opportunity” for insurance firms to embrace digital transition and improve their processes — provided they can quickly embrace insurance claim form automation to underpin underwriters’ efficiency.

This is no small task. From legacy systems that were never designed to live on cloud networks to proprietary processing solutions that are struggling with handprinted forms and multiple file formats, health insurance agencies now recognize the need for efficient, accurate, and complete forms processing — but often lack the backend infrastructure to make remote data capture a reality.

Accusoft’s FormSuite for Structured Forms can help bolster digital backends and build out insurance data collection capacity with efficient information capture, reliable structured form field recognition, quick data verification, and multiple form identification to both streamline forms processing and support the “new normal” of health insurance operations.


Managing Healthcare Data Analytics During COVID-19

Crisis conditions are rapidly evolving. From dynamic case variables to emerging equations that govern policy and coverage requirements, it’s critical for insurance companies to have systems in place that allow for capture and routing of this data quickly and accurately, in turn empowering actuaries to create cutting-edge risk models.

This is especially critical as healthcare costs continue to rise. According to a recent data brief, uninsured patients could face medical bills of more than $74,000 if they experience major complications, while the International Travel and Health Insurance Journal (ITIJ) reports a rising demand for more comprehensive employer-sponsored healthcare policies to help offset out-of-pocket COVID-19 costs.

As a result, it’s critical for companies to focus on the certainties of the current claims continuum: the crisis isn’t static, customer satisfaction is paramount, and comprehensive forms capture across four key functions defines the first step toward improved data analysis and risk modeling.

 


1) Efficient Information Capture

On-demand information capture underpins effective analytics, in turn empowering agents with the critical information needed to provide best-fit coverage recommendations and ensure high customer satisfaction. Even prior to the COVID crisis, 61 percent of consumers said they wanted the ability to submit and track claims online. But nine out of ten firms lack the in-house ability to process these forms and capture this data at scale, let alone empower staff to do so at a distance. 

FormSuite for Structured Forms provides a software-driven solution to this challenge with the ability to automatically capture forms data using a combination of OCR, ICR, and OMR technologies, making it possible to quickly and accurately record everything from phone numbers and signatures to hand-printed text fields. For actuaries, agents, and underwriters this reduced reliance on manual processes shortens the distance between data information and insight, allowing staff to better serve customer needs with custom-built health policies.

 

2) Reliable Form Field Recognition

Poorly-constructed fields represent a real problem for insurance data capture and accuracy. Consider common form characteristics such as comb lines or character boxes. If comb lines are too close together or too short, they will not be recognized. They should be at least half the height of any expected character. Accurate, automated reading may be difficult. When it comes to character boxes, meanwhile, rectangular boxes higher than they are wide can result in compressed characters that are challenging to identify. Even paper thickness and bleed-through can cause form field frustrations, in turn reducing overall claims throughput.

Solving this problem starts with improved form frameworks. Insurers are often best-served by leveraging the latest ACORD standards to ensure claims documentation construction is both current and comprehensive. But in a world driven by socially-distant technology solutions, companies must also account for the expanding volume of new forms used by clients and third-party providers alike. Recent PWC data found that “clunkiness and redundancy” remain common across insurance forms. As a result, it’s critical to deploy SDK solutions capable of streamlining form recognition to ensure staff spend less time checking and re-checking paperwork and more time writing new policies. 

 

3) Confident Data Verification

Data confidence is critical for success, especially when it comes to capturing data from hand printed or scanned insurance forms. Even small errors can cause big problems — if applicant data is incorrectly entered or policy values aren’t accurate, insurance companies lose the information confidence required to drive strategic analytics at scale. 

Confidence values provide the critical connection between OCR assessment and data output. Described on a scale from 0 to 100, higher numbers represent greater likelihood of character accuracy, while lower values indicate a “suspicious” character that may require secondary analysis. FormSuite for Structured Forms allows developers to customize key confidence thresholds that trigger notifications — if characters are deemed suspicious, they can be flagged for further review to ensure data is completely accurate.

 

4) Multiple Forms Identification

According to the World Insurtech Report 2020, the shift from corporate operations to home offices has accelerated digital insurance innovation, with 60 percent of firms launching in-house innovation teams to help embrace the need for technology-first, customer-facing processes. 

The caveat? These initiatives are only successful with backend processes support, specifically in the area of forms recognition. As noted above, while industry-standard forms remain the ideal iteration for claims processes, pandemic priorities have compelled rapid adaptation as both staff working environments and consumer expectations evolve. To meet emerging demand, firms must be prepared to regularly create, vet, and verify new form templates on-demand. 

Advanced optical character recognition is critical to bridge the gap between scanned forms and current templates by ensuring correct formats are quickly identified and efficiently routed. Formsuite for Structured Forms also takes this process a step further with the ability to accurately detect and align form templates even if they’re rotated, skewed, or scaled.

 


Solving for Structural Integrity

Structural integrity is essential for insurance success in the age of COVID-19. To achieve this goal, firms can’t simply focus on front-line functions. Other critical steps include needing to bolster back-end forms processing and bridge functional gaps, empowering staff to capture data, identify form fields, achieve higher character confidence values, and identify document formats on-demand. Ready to streamline claims processing? Download your free trial of FormSuite for Structured Forms.

Although PDFs are one of the most common document types in use today, not every PDF file is identical. A document with multiple layers, annotations, or editable form fields can create significant challenges for an application, especially when it comes to viewing, printing, and OCR reading. One of the most effective ways of dealing with these PDFs is to use powerful digital tools that “flatten” the document to remove unseen or unnecessary information to reduce the overall complexity of the file.

What Is PDF Flattening?

Flattening can be used to refer to a number of different processes, but in principle, they all accomplish the same goal of merging distinct elements of the document. A few example of flattening include:

  • Making interactive form elements non-fillable and static.
  • Burning annotations into the document to make them native text.
  • Combining multiple layers of text or images into a single layer, eliminating any non-visible elements.

3 Reasons to Flatten PDFs

There are numerous reasons why an end user may wish to flatten a PDF document, but they usually fall under one of three broad categories.

1. Better Security

Forms often contain valuable information, especially when it comes to financial, insurance, or government forms. If a PDF with editable forms were to fall into the wrong hands, someone could easily alter the information contained in the form to commit fraud or falsify data. By flattening the forms, the entries become a static element of the document and cannot be altered any further. By building applications with the ability to flatten PDF forms, developers can help organizations protect themselves and their customers from the threat of falsified forms.

2. Faster Viewing

Speed is often crucial when it comes to viewing or processing documents. The more information is contained in a PDF, the longer it takes an application to render and view it. While this is sometimes a byproduct of file size, complex or poorly-designed forms can also make a PDF less responsive. Flattening a multi-layered PDF into a single, flattened layer eliminates hidden elements and makes the document much easier to read. This can also apply to forms, which often contain substantial annotation information. Eliminating forms simplifies the document, allowing it to render more quickly.

3. Easier Printing 

Many PDFs contain hidden data that is not visible on a viewing screen, but turns up on the page when the document is printed. Buttons and dropdown fields, for instance, can make a printed document look cluttered and confusing. When form fields are flattened, hidden annotation data is removed, eliminating any unpleasant surprises when the document hits the printer tray. For PDFs with multiple layers and hidden elements, flattening ensures that only the visible portions of the document will appear on the printed version.

How to Flatten a PDF Form Field Using ImageGear

With ImageGear, converting interactive form fields into static page content is a simple process that can be accomplished programmatically before documents are read by an OCR or ICR engine. It can also remove XFA form data, which often creates challenges for forms processing software.

ImageGear provides two options for flattening form fields. Although nearly identical in name, they perform somewhat different functions and should be used in different instances.

  • FlattenFormField: Flattens specified fields into the page.
  • FlattenFormFields: Flattens every field contained in the PDF into the page.

During the flattening process, a boolean can be used to indicate which fields should appear during printing, which is useful for hiding interactive elements that have no use on a printed page (such as buttons). Each field contains annotation information that determines how it should be represented on the page. Fields typically features one of three flags to dictate their representation:

  • HIDDEN: Any field with this category will not appear on the page after flattening.
  • NOVIEW: This field will only be visible on the page if “forPrinter” is specified during the flattening process.
  • PRINT: These fields will appear on the page whether or not “forPrinter” is specified. If a field does not have the PRINT flag, it will only appear when “forPrinter” is not specified.

Dealing with XFA Forms

Although officially deprecated by international open PDF standards, Adobe’s proprietary XFA forms are still found in many PDF documents. Opening and editing a PDF that contains XFA data often creates exceptions that make them difficult to manage when it comes to extracting forms information. ImageGear FlattenFormFields function will remove any XFA data from a document during the flattening process.

How to Flatten a PDF for OCR Processing with ImageGear

While flattening forms is an effective way of simplifying a document, it doesn’t change the file format itself. The document itself is still a PDF. So while ImageGear’s form flattening features are an effective solution for managing PDFs securely, another approach is often needed for OCR image processing.

Consider, for instance, an insurance solution that needs to be able to extract data from a wide variety of forms. Some of these documents are interactive PDFs with editable forms, some are static PDFs, and still others are scanned images of a document. Rather than devising multiple strategies for dealing with each document type, the solution can streamline the process by simply rasterizing every PDF it receives into an image file, which effectively flattens any form elements it contains.

Once the PDF is flattened into an image, it can easily be run through an OCR engine to match it to the correct form template and then send it to the appropriate database or extract specific form information. This process ensures that all documents coming through the solution can be handled the same way, which makes for a more streamlined and efficient workflow.

Expand Your Application’s PDF Capabilities with ImageGear

Flattening PDFs is just one of many features developers can incorporate into their applications with Accusoft’s ImageGear SDK. Other core functionality includes the ability to annotate, compress, split, and merge PDF files, as well as convert multiple file types to or from PDF format. ImageGear also provides a broad range of PDF security features like access controls, encryption settings, and digital signatures. Get a hands-on trial of ImageGear today for a closer look at what this powerful SDK can do for your application.

COVID-19 insurtech

 

From large payouts and losses in some segments to rapid growth in others, the insurance industry has experienced seismic shifts due to the COVID-19 global pandemic. To keep some semblance of normalcy during these changes and the aftermath, organizations are turning to InsurTech solutions for help. 

According to Deloitte, InsurTech investments remain strong, with COVID-19 simply shifting priorities to virtual customer engagement and operational efficiency rather than cutting budgets. Data collected by Venture Scanner indicates that the global InsurTech market generated $2.2B in the first half of 2020.


The Challenge of Advancing a Product to Meet Immediate Needs

Tasks once completed manually at insurance companies can bottleneck an entire system in just a few days and prevent insurers from winning much-needed revenue. For this reason, providers are scrambling to make fast efficiency gains while minimizing risks that could lead to unrealized business opportunities due to slow processing. When it’s feast or famine, with customers either signing up or making claims in droves, there’s no time to waste.

As a product developer in the InsurTech space, this puts you in a precarious position. After all, how can you add functionality overnight when it takes time to build those new capabilities? While some organizations may have the available workforce to rally and build new features quickly, most don’t. 

If you’re like most in the development space, finding and retaining talent is a challenge. What’s more, they’re likely already looking at a project backlog spanning many months—if not years. For this reason, augmenting existing solutions with white-label, third-party plug-ins is an attractive option. Now, let’s turn our attention to the type of functionality insurers need to navigate recent shifts.


4 Essential Capabilities for the Insurance Industry in the Wake of COVID-19

Pew Research found that by June of 2020 roughly 3% of Americans had already made a mass exodus from highly populated areas like New York, New York and San Francisco, California due to challenges posed by the COVID-19 global pandemic. This number has likely grown since June and will likely continue to grow as hubs of economic growth continue to shift and settle. 

For each insured individual that moves and retains insurance coverage, there’s paperwork. For many, they’ll even switch providers as their previous provider may not be able to provide competitive rates in their new location. The sheer change-management involved in migrations of this scale is daunting. Without the ability to process requests faster, insurance companies could find themselves struggling to keep up. 

To help your insurance industry clients effectively navigate the road ahead, your applications need to include greater data-capture, data-conversion, and optical character recognition technologies that reduce the need for manual intervention in document processing. 

1. Data Capture Efficiency  

As the number of file formats increases, insurance organizations need the ability to quickly capture and process hundreds of different image formats. Beyond simply capturing them, they often also need to aggregate and convert those multiple formats into a single, secure, and digitally accessible PDF.

Rather than trying to build everything from scratch, sometimes partnering with a third-party software developer can give you a leg up on all the delivery time associated with expanding feature sets for the insurance industry.  

Essential Capabilities Should Include:

  • Support for multiple file formats
  • Automated image-correction and optical character recognition technology
  • Clean integration that maintains or improves processing speed 

Once data is captured, it then needs to be managed. To explore document management capabilities to consider when expanding your feature set for the insurance industry, click here

2. Identify Form Fields

Whether potential buyers are requesting new policies or current customers are evaluating existing policies, precise and efficient data-capture technologies can improve the ability of insurers to access important data and analyze policies. Adding these capabilities requires quite a bit of strategy. First, one must consider the core challenges involved in effective data capture: 

  • Poor inputs that aren’t easy to correct and capture 
  • Poorly designed forms that reduce image recognition success  
  • Imaging technology that can’t recognize a robust number of file formats and fonts 

When contemplating the structure of boxes for character collection, our experts found that using a square shape rather than a rectangle results in less data loss. While rectangles may, at first, appear to save space and therefore be a more effective option, research showed that they typically don’t provide the average user enough space to clearly write letters or characters without interfacing with the boundary lines. Thus, square boxes improve data transfer success. 

Figure 1: Examples of ineffective rectangular boxes versus effective square boxes for character capture. 

This is just one factor to consider when streamlining form processing within an insurance technology application. To explore more research on this topic, download the Best Practices: Improving ICR Accuracy with Better Form Design whitepaper.  

3. Confidence Value Reporting for Data Recognition

Not all optical character recognition technology is created equal. That’s why it’s important to make sure any solution you either create internally or partner with a third party to integrate provides ongoing confidence value reporting for data recognition. Having this capability in place can alert you to problems before they lead to costly issues — like duplicated efforts, a poor customer experience, or incomplete data hindering contract processing. 

4. Use OCR to Identify Different Documents

Optical character recognition (OCR) can help insurance companies cut down on manual effort by identifying different forms automatically, which equips application developers like you to create automation within your company’s product that routes identified forms through predefined workflows. 

Without OCR, significant manual effort is required to process forms required to execute insurance contracts. When evaluating OCR capabilities to add to applications, keep in mind these essentials:

  • Successful Character Recognition Rates – Given the highly regulated nature of insurance along with high fines for shortcomings, it’s often well worth the extra investment to get a solution with 99% accuracy versus 95%. 

 

  • Multi-Document Recognition with High Confidence Values– Given the broad number of file types insurance organizations receive, having a software package in place that cleans up documents before running them through optical character recognition tools improves the likelihood of extracted data being usable. With cleaner data in hand, insurance agents are empowered to make better recommendations to customers, ensuring they’re not over or under insured.

These are just a few items to consider when adding document viewing and forms processing features to your application. While automated workflows may have given organizations heartburn in the past, the reality is that high-volume, fast-changing environments can’t survive without them. Markets are changing so quickly that without automation to help bring order to the chaos, the tidal wave of requests will overtake the underprepared. 

Help your clients better respond to not only COVID-19, but also future-proof their ability to streamline claims by expanding document viewing and form processing capabilities. To learn more about our insurtech capabilities, explore our content solutions for insurance companies.      

Today’s organizations gather information from a variety of sources. Structured forms remain one of the most popular tools for collecting and processing data, and anyone who has filled out such a form recently has likely encountered the familiar bubbles or squares used to indicate some form of information. Whether these marks are used to identify marital status, health conditions, education level, or some other parameter, optical mark recognition plays an important role in streamlining forms processing and data capture.

What is Optical Mark Recognition?

Optical mark recognition (OMR) reads and captures data marked on a special type of document form. In most instances, this form consists of a bubble or a square that is filled in as part of a test or survey. After the form is marked, it can either be read by dedicated OMR software or fed into a physical scanner device that shines a beam of light onto the paper and then detects answers based on how much light is reflected back to an optical sensor. Older OMR scanners detected answers by measuring how much light passed through the paper itself using phototubes on the other side. Since the phototubes were very sensitive, #2 pencils often had to be used when filling out forms to ensure an accurate reading.

Today’s OMR scanners are much more accurate and versatile, capable of reading marks regardless of how they’re filled out (although they struggle if the mark is made with the same color as the printed form). More importantly, OMR software has made it possible to capture data from OMR forms without the need for any special equipment. This is especially helpful for processing forms information that exists in digital format, such as PDF files or JPEG images. 

The History of Optical Mark Recognition

One of the oldest versions of forms processing technology, OMR dates back to the use of punch cards, which were first developed in the late 1800s for use with crude “tabulating” machines. The cards typically provided simple “yes/no” information based on whether or not a hole was punched out. When fed through the tabulating machine, a hole would be registered and counted. This same basic principle would allow more complex machines to perform basic arithmetic in the early 1900s before serving as the foundation for early computer programming by mid-century. Entire computer programs were stored on stacks of punch cards, which would remain in use until well into the 1970s when more powerful machines made them obsolete.

Although OMR operates on the same principle as a punch card, it instead uses scanning technology to detect the presence of a mark made by a pencil or a pen. This form of identification was first popularized by IBM’s electrographic “mark sense” technology in the 1930s and 1940s. The concept itself was first developed by a schoolteacher named Reynold Johnson, who wanted to streamline test grading. He designed a machine that could read pencil marks on a special test paper and then tabulate the marks to generate a final score. After joining IBM in 1934, Johnson spearheaded the development of the Type 805 Test Scoring Machine, which debuted in 1938 and revolutionized test scoring in the education sector. In production until 1963, the 805 could score 800 sheets per hour when run by an experienced operator.

The 805 registered marks by using metal brushes to sense the electrical conductivity of graphite from the pencil lead. While effective, it had limitations in terms of reading speed and flexibility. When Everett Franklin Lindquist, best known as the creator of the ACT, needed a machine that could keep up with Iowa’s widespread adoption of standardized testing in the 1950s, he developed the first true optical mark reader. Patented in 1962, Lindquist’s machine detected marks by measuring how much light passed through a scoring sheet and was capable of scoring 4,000 tests per hour.

Throughout the 1960s, OMR scanning technology continued to improve and spread to a variety of industries looking for ways to rapidly process data. In education, however, the OMR market would soon be dominated by the Scantron Corporation, which was founded in 1972 to market smaller, less expensive scanners to K-12 schools and universities. After placing the scanners in educational institutions, Scantron then sold large quantities of proprietary test sheets that could be used for a variety of testing purposes. Scantron was so successful that their distinctive green and white sheets have become synonymous with OMR scanning for generations of US college students.

The next major innovation in OMR technology arrived in the early 1990s with dedicated OMR software that could replicate the drop-out capabilities of commercial scanners. Part of the reason why scanners used proprietary, pre-printed forms was so they could use colors and watermarks that would not register during scanning for more accurate reading. Thanks to OMR software, it became possible to create templated forms and then remove the form image during the reading process to ensure that only marked information remained.

Take Control of OMR Forms with Accusoft SDKs

Accusoft’s FormFix forms processing SDK features powerful production-level OMR capabilities. It not only detects the presence of check or bubble marks, but can also detect markings in form fields, which is particularly useful for determining whether or not a signature is present on a document. Capable of reading single or multiple marks at 0, 90, 180, and 270 degree orientations, FormFix can also recognize checkboxes and be programmed to accommodate a variety of bubble shapes. Its form drop-out and image cleanup features also help to ensure the highest level of accuracy during OMR reading.

For expanded forms functionality, including optical character recognition (OCR) and intelligent character recognition (ICR), developers can also turn to FormSuite for Structured Forms. Featuring a comprehensive set of forms template creation tools and data capture capabilities, FormSuite can streamline forms processing workflows and significantly reduce the costs and errors associated with manual data entry and extraction.

Find out what flexible OMR functionality can do for your application with a fully-featured trial of the FormSuite SDK. Get started with some functional sample code and explore FormFix’s features to start planning your integration.

Although often considered a bit old fashioned, the insurance industry has made great strides in recent years to adapt to the changing needs of its customers. The latest generation of insurance customers expects faster service, better support, and more options from providers. Given these pressures, it’s no surprise that InsurTech developers have found ample opportunities to deliver solutions that help insurance firms better manage their workflows and create better customer experiences.

Despite the successes of this digital transformation, however, there are still a number of challenges that InsurTech developers face when building new applications. Investing heavily in creating powerful AI and big data tools might help those platforms stand out from the crowd, but they won’t find much success with firms if they don’t also provide the core functionality organizations need to service their customers. 

That’s why many InsurTech developers are turning to versatile SDK and API integrations to expand their feature sets without compromising their development timelines.

4 Major Challenges of InsurTech Applications

1. Security and Privacy

As the insurance industry continues to shift toward digital processes and platforms, it’s become more important than ever for InsurTech applications to keep sensitive data secure. While most organizations do invest in cybersecurity protections, they often don’t realize how their own practices could potentially pose a risk to customer information. This is especially true of insurers that rely on third-party programs for various tasks like document viewing and editing. Take, for instance, the case of Folksam Group, which inadvertently shared client data from as many as one million customers with Google, Facebook, LinkedIn, Microsoft, and Adobe in late 2020. 

2. File Management

Today’s insurers are receiving all kinds of documents, files, and images from their customers, which creates something of a document dilemma. A single auto accident claim, for instance, might have valuable information spread across multiple PDFs, Word documents, spreadsheet files, scanned images of hand-written forms, and image files. In order to process claims quickly and effectively, firms need InsurTech solutions that provide an all-in-one solution that can handle a broad array of file formats. Without these file management tools, insurers will be forced to use multiple programs to meet their needs, which creates inefficient dependencies and increases security risks.

3. Data Collection

Insurance companies gather quite a bit of information from form applications, both in physical and digital formats. Unfortunately, transferring that information from a form document into an InsurTech system is often a laborious manual process. Not only is manual data collection time consuming, it also increases the likelihood of human error. Even when firms do implement an InsurTech solution with forms processing capabilities, however, they often lack the capability to read certain types of form fields, especially those completed by hand. The ability to adapt to new form templates is also critical for organizations that want to invest in automation. 

4. Remote Collaboration

The COVID-19 pandemic may have forced insurance offices to rapidly embrace a remote work strategy, but many firms had already been investing in some form of hybrid work model for years. Nationwide was able to transition 98 percent of its workforce to remote status precisely because the company already had the technology solutions in place to allow insurance agents to work from home. Without some way of facilitating remote collaboration directly through InsurTech applications, organizations end up relying on email, which poses serious security concerns. Furthermore, with multiple copies of a document being distributed and downloaded, it quickly becomes difficult to know which version incorporates the most up-to-date changes.

SDK and API InsurTech Solutions

Building new functionality into an application always involves a tradeoff. When developers choose to code something from scratch, that means pulling team members away from another project or extending the product’s release timeline. In a fast-moving industry where InsurTech developers are racing competitors to be the first to market, it doesn’t make sense to design and build every aspect of an application in-house. 

Rather than pulling valuable development resources away from their innovative InsurTech features, developers can solve common insurance challenges much faster with SDK toolkits and API integrations. 

Secure File Viewing

The easiest way for InsurTech solutions to keep documents secure is to integrate HTML5 viewing capabilities directly into the application. Rather than being forced to download or open a file for viewing in a third-party application, employees can view multiple document formats natively. This is critical because it means no data will be shared with third-party programs.  Since the files remain safely within the secure InsurTech environment, firms can also control the level of access to any document, which prevents unauthorized individuals from downloading or viewing the contents. Thanks to API-based integrations like Accusoft’s PrizmDoc Viewer, InsurTech developers can help their applications safely view more than 100 unique file types without any third-party dependencies.

Data Capture

By integrating forms processing capabilities into their applications, InsurTech developers can provide their clients with powerful tools that allow them to gather essential data quickly and accurately. As the essential connective tissue between customers and insurance databases, form field recognition integrations use OCR technology to intelligently identify form data and extract it for processing. They can also be set up to identify a wide range of insurance forms to quickly identify and scan documents to streamline processing workflows. Accusoft’s FormSuite for Structured Forms even goes a step further by incorporating powerful image cleanup functionality to ensure that data will be extracted as accurately as possible.

File Conversion

In order to meet the file management challenges of today’s insurance providers, InsurTech developers need document and image processing integrations that can read and write multiple file formats. Information spread across multiple documents, emails, or even texts can be processed using OCR technology, and then consolidated and converted into a variety of formats for easy reference and collaboration. Rather than juggling several files with different dependencies, an SDK integration like Accusoft’s ImageGear can easily output processed files in PDF, RTF, XML, or DOCX format for viewing and editing within a single application.

Editing and Annotation

Providing secure document viewing capabilities solves only one half of the insurance collaboration challenge. InsurTech applications also need to provide both internal and external stakeholders with the ability to edit and markup documents throughout the application and claims process. Content processing integrations can allow authorized users to make changes to documents completely within their InsurTech solution and review markups and comments from other collaborators. 

Since all editing occurs within the application itself, there’s no need to worry about anyone downloading a document to make changes locally and creating confusion over which version is the most up-to-date. Redactions may also be necessary to hide private or confidential information from unauthorized viewers. As an added benefit, PrizmDoc Viewer’s editing features allow users to make a variety of markups and redactions while preserving the integrity of the original file.

Accelerate Your InsurTech Application Development with Accusoft

Accusoft’s collection of powerful SDK toolkits and API integrations provide innovative InsurTech developers with the resources they need to solve core insurance industry challenges. By implementing proven functionality into their applications, project managers can streamline the development process and dedicate more resources to the innovative features that will set their platform apart from the competition.

Whether you’re looking to incorporate versatile document viewing and editing or need a more accurate forms processing solution, Accusoft’s family of InsurTech SDKs and APIs can help your development team get to market faster. Learn more about what our products can do for your application in our InsurTech fact sheet.

 

OCR form

An automated forms processing solution can significantly improve accuracy and efficiency when it comes to managing large quantities of documents containing structured content. Whether an organization needs to digitize existing records or is continuously processing new documents within application workflows, having a versatile optical character recognition (OCR) component working to identify and extract text from multiple languages allows them to capture data more effectively.  Solid OCR form capture is critical.

Although a good OCR engine operates quickly and efficiently, the process of recognizing and extracting text is a highly complex undertaking that can be impacted by a variety of factors. Under optimal conditions, for example, the OCR component within Accusoft’s FormSuite can generate results quickly and accurately, with the ability to read several languages from around the world. However, if an application’s forms processing workflow is not set up efficiently or overlooks a few important considerations, recognition performance may suffer in terms of speed and accuracy.

6 Ways to Achieve the Best Results with the Accusoft OCR Component in FormSuite

 

1. Pay Attention to Image Resolution

As a general rule, OCR components should be provided with high resolution images so the recognition engine is able to distinguish the details that would otherwise be missed on low resolution images. This helps them to recognize the differences between “l” and “i” or “O” and “0” (zero), which results in better, more accurate results.

However, there could be a problem if the image resolution is too high. These images require much more time to process without delivering any benefits since the required letter properties are clearly distinguishable in a lower resolution.

To strike a balance between speed and accuracy, it’s better to scan all images in a 150-400 dots-per-pixel range. This allows the recognition engine to identify all possible letter properties and avoid being bogged down with analyzing a lot of data at the same time.

2. Don’t Lose Image Properties While Preparing to Recognize

To achieve the best results, it’s important to provide the recognition engine with a few helpful hints. In some cases, resolution properties may be lost while an image is being prepared for recognition, leading to worse than expected results. This happens most frequently when working with System.Drawing.Image or SystemDrawing.Bitmap classes directly during operations like clipping, merging, or reducing the bit depth. 

In this case, the best solution is to make sure that HorizontalResolution and VerticalResolution properties are set correctly and reflect initial image resolution values. The ScanFix component within FormSuite can perform this task automatically and is designed to be compatible with the OCR component to help achieve better recognition results.

3. Clean Up Underlined Text Before Recognition

Specks, dirt, and other imperfections within the source image can significantly reduce recognition quality. Sometimes, however, even a seemingly good image can be recognized incorrectly when there are underlined words like URLs, emails, or specifically formatted generic text. 

From the software’s point of view, this kind of text isn’t very different from other types of image distortion. ScanFix’s LineRemovalOptions can clean up the text by eliminating lines that could interfere with recognition. The API also features special parameters that ensures characters with low hanging elements (such as “j” or “y”) will be restored after line removal to avoid another potential recognition problem.

4. Use Long-Living Objects to Avoid Recognition Performance Drop

Creating a new instance requires OCR engine initialization and loading neural network data suitable for specific recognition parameters. This process is not resource free because of the data complexity and may cause delays from ~200 msec to 2 sec depending on the hardware and recognition properties. 

Existing Accusoft OCR instances may be reused to recognize other images with different properties. This will speed up the overall process because initialization will be done only once during the first AnalyzeField call and subsequent calls will be much cheaper in terms of computing resources.

5. Assign Instances to Their Own Worker Threads

Objects are thread safe and can be called from different threads. However, assigning an object to its own thread can avoid extra locking. One of the simplest ways to do this is to use C# Parallel.ForEach loop and create ConcurrentQueue with the pre-allocated objects. 

This ensures that the number of threads will not exceed the number of available CPUs. Any available instance can then be automatically assigned to recognize the images in their own thread while extra possible threads will wait until busy instances will be free to acquire.

Other common patterns are producer-consumer and map-reduce, which are more complex to implement but provide better flexibility when managing input data.

6. Dispose Objects to Avoid Memory High Memory Consumption

This is a generic rule for the C# to call a Dispose for the objects which use non-managed resources. FormSuite’s OCR component uses an external recognition engine, so it is highly recommended to call Dispose when the instance will not be required anymore. This can avoid a situation where the memory will not be available for different parts of the application, especially when a high amount of data exists for post-processing or the amount of available memory is low because of the different processes running in parallel.

Get Accurate OCR Data Capture Results with FormSuite

When properly configured and incorporated into a forms processing workflow, the FormSuite OCR component can accelerate automated data capture and reduce manual errors. Its zonal field recognition capabilities allow it to hone in on predefined field types to improve processing speed and accuracy. Developers can also adjust confidence values for recognition results to determine how frequently manual review is necessary. 

To get a hands-on look at how FormSuite incorporates OCR seamlessly into its collection of forms processing tools, schedule a free trial today.

prizmdoc cells finance

 

Spreadsheets are to finance what cranes are to construction. As a result, financial services organizations including traditional banks, tax companies, insurance agencies, and fintech firms opt for software-driven spreadsheet solutions as standard operating procedures. The problem? Ubiquitous spreadsheet software introduces a host of cybersecurity, compliance, and collaboration challenges, especially as regulatory and operational requirements evolve around the use, storage, and sharing of clients’ financial data.  Enter PrizmDoc Cells for finance. 

Accusoft’s newest addition to the PrizmDoc Suite — PrizmDoc Cells — offers both form(ula) and functional advantages for financial data entry and integrity.


Managing Market Forces

As noted by Forbes, the finance market is changing. Recent survey data found that 69 percent pointed to fintech firms as a “lifeline” during the current crisis. And these shifts are ongoing. Even once pandemic pressures begin to ease, there’s no going back from the speed and convenience offered to users when brick-and-mortar locations were locked down. 

Financial firms across multiple markets that made the move online application processing, claims evaluation, and loan approvals must now support these initiatives at scale — but many are now finding themselves frustrated by the limitations of current spreadsheet solutions.


Addressing Operational Challenges

Familiar spreadsheet software offers straightforward function: Staff can enter relevant data and derive actionable output through formulas. But these tools also pose problems for finance firms, including:

    • Operational errorsAs noted by CFO, 88 percent of spreadsheets contain some type of error. These include errors in formulas, human data entry issues that create impossible data ranges, and even hidden fonts that can impact the outcome of calculations. This is no small issue — for one financial firm, a missing negative sign caused a 2.6 billion dollar mistake in reporting net capital losses, forcing the company to cancel year-end dividend distributions.

 

    • Version consistencyThe more people handle and modify a spreadsheet, the harder it is to identify the “right” version. This becomes especially problematic as spreadsheets are saved to desktops or mobile devices, then modified and sent back into corporate email environments.

 

    • Data securityWhile email presents a significant spreadsheet security risk, the same is true of any solution — cloud-based, on-premises or a mix of both — that allows users to download, copy, and share spreadsheets. Consider the case of a well-meaning user who downloads a financial spreadsheet from a cloud app and then sends it to his personal email so he can work on them remotely. If this email account is compromised, so too are any supposedly secure spreadsheets, putting financial firms at risk of regulatory compromise.

 

    • Ongoing Time and effortFrom the time needed to track down and verify the most recent and accurate version of key spreadsheets to the effort required if data is entered incorrectly and requires remediation, current software tools often see staff focused on putting out formula and framework fires instead of moving financial firms forward.

 


Gaining Control with PrizmDoc Cells for Finance

PrizmDoc Cells changes the spreadsheet paradigm by shifting data out of proprietary software and into the application of your choice. As a web-based spreadsheet viewer and editor designed to natively support XLSX files, PrizmDoc Cells provides the ability to securely embed spreadsheet data into any website, intranet, portal or CMS application without compromising security. This makes it possible for independent software vendors (ISVs) and other fintech providers to deliver the best of both worlds: Familiar functions in a user-friendly, online form that’s separated from the critical formulas and proprietary business logic behind-the-scenes.

Key benefits of PrizmDoc Cells for finance include:

  • Solve for proprietary dependenciesExcel remains the de facto spreadsheet standard for many organizations but also locks financial firms into a cycle of software dependency — and if legacy applications or in-house tools don’t work well with Excel, firms face extra operational steps to ensure reliable data access. PrizmDoc Cells solves this proprietary problem by allowing any application to import, edit, and export XLSX files without Excel dependencies.

 

  • Safeguard source dataIn many cases, end-users need to view spreadsheets and make minor edits but can’t be granted access to original files. With PrizmDoc Cells, fintech providers can secure intellectual property by removing end-user access to proprietary source files, encrypting the data, and hosting it securely in their own environments.

 

  • Separate underlying logic and UIWhile proprietary business logic, formulas, and calculations form the basis of spreadsheet value and actionable insight, users don’t need the ability to see — or modify — these functions. PrizmDoc Cells lets administrators control what’s visible, what’s accessible, and what’s changeable to ensure spreadsheet consistency.

 

  • Streamline version controlBy removing the need for client-side software installs and downloads, PrizmDoc Cells sets the stage for enhanced version control. While users can view and edit spreadsheets with the right permissions, these spreadsheets are continually updated with the most recent changes to ensure version consistency. 

 

  • Start ASAPPrizmDoc Cells makes it easy for companies to get started and get building their best-fit spreadsheet solution by using the simplicity and speed of Docker containers. Instead of worrying about potential conflicts with other software or issues with specific operating system requirements, companies can start up a PrizmDoc Cells container in a matter of seconds.

Securely Embed Your Data Now

Even as the value proposition evolves, the volume of spreadsheets processed by financial firms continues to grow. For industry operators, this presents a challenge: How do they align evolving client expectations with current spreadsheet limitations? 

For ISVs, this offers an opportunity. Empowered by PrizmDoc Cells, vendors can offer a new take on spreadsheet form and function that delivers ease of integration and on-demand customization without breaking the bank — or increasing regulatory risk.

Unlock the PrizmDoc Cells potential — try the online demo today and experience the future of formula and function.