Technical FAQs

Question

I have EML and MSG files that contain attachments. I want to combine the original EML/MSG document with each of its attachments into a single PDF. How can I do this?

Answer

To do this you are going to need to create a viewing session for the EML or MSG file. Once you’ve created the viewing session you can get the viewingSessionIds of the attachments. Once you have the viewingSessionIds you can get the workFile ID associated with each viewing session. With the workfile IDs you can use the Content Conversion Service (CCS) to combine the email with its attachments into a single PDF.

Use the following API requests to do this:

Create a new viewing session with:

POST {server_base_url}/PCCIS/V1/ViewingSession 

This will give you a viewingSessionId which will be used in future requests.

The body for this request will be JSON:

    {
        "render": {
            "html5": {
                "alwaysUseRaster": false
            }
        }
    }

Upload the document with:

PUT {server_base_url}/PCCIS/V1/ViewingSession/u{viewingSessionId}/SourceFile?FileExtension={extension} 

The request body must be bytes of the source document. Make sure to include the FileExtension or PrizmDoc won’t be able to detect the file as an EML or MSG file.

Poll for and get the viewingSessionIds of the attachments with:

GET {server_base_url}/PCCIS/V1/ViewingSession/u{viewingSessionId}/Attachments

This will return the viewingSessionIds for each of the attachments.

Get the workfile ID for each of the viewing sessions with:

GET {server_base_url}/PCCIS/V1/ViewingSession/u{viewingSessionId}/FileId 

You’ll need to get a fileId for each attachment’s viewingSession and the email’s viewingSession.

With those workfile IDs, you can use the Content Conversion Service (CCS) to combine each of the workfiles with:

POST {server_base_url}v2/contentConverters

The body for this request will be JSON and need to include the workfileId for each of the attachments and the email itself. The body would look like this:

    {
        "input": {
            "sources": [
                { 
                    "fileId": "{EmailWorkFileId}"
                },
                { 
                    "fileId": "{Attachment1WorkFileId}"
                },
                { 
                    "fileId": "{Attachment2WorkFileId}"
                }
                
            ],
            "dest": {
                "format": "pdf"
            }
        }
    }

This will return a processId that you can poll using:

GET /v2/contentConverters/{processId}

Once the process is complete, the request will return a results array that will contain the fileId of the final document.

You can get the final document that contains all the attachments and original EML/MSG file combined into a single PDF with:

GET /PCCIS/V1/WorkFile/{fileId}

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.

Question

When using the PrizmDoc samples, the sample documents included are taking close to 1 minute to load in the viewer. The same also happens when uploading files into the sample.

The server processes are showing minimal impact on CPU and memory. However, the hard drive was spiking to 100% utilization sporadically.

Answer

We have found that Windows Defender with enabled Real-Time scanning can significantly impact performance. Once Real-Time scanning was disabled, we found this issue to be immediately resolved.

To disable Windows Defender, you can do the following:

  1. Right-click on the Windows Logo in the lower left-hand corner and select Control Panel.
  2. Select Windows Defender and then select Settings.
  3. Under the Real-Time protection section, slide the switch to Off.
Question

When viewing .csv files in PrizmDoc Viewer, the dates in the CSV file are in UK format (DD/MM/YYYY). However, if the DD is lower than 13 it is converted to US date format (MM/DD/YYYY).

Answer

Workaround:

The suggested workaround is to use Excel files instead of CSV to avoid this situation. Excel file format stores date/time format in the file.

Issue:

This is a bug in the MS Excel COM Interop that is being used by the product (MsOfficeConverter). Here is the related Excel bug: https://social.msdn.microsoft.com/Forums/vstudio/en-US/82248560-dabd-4c90-b1e2-793b2f32b257/excel-bug-handling-dates-in-csv-files-using-microsoftofficeinteropexcel?forum=exceldev

Problem description:

When using MS Excel Interop to open CSV files, all date/times there are being interpreted with “en-US” locale, regardless of actual system locale. Here is the description from the bug link above:

Excel interpreting dates when its reads csv files via .NET Interop. It is not a excel formatting issue per say. When excel accesses information such as dates (which are stored as numbers in memory to support arithmetic operations) from text files, it has to convert the date from textual representation (within the csv file, such as 2012-09-12) to the equivalent number in Excel memory (e.g. 41164 which represents 2012-09-12). When we use Interop to access this number in memory, many are interpreted incorrectly – swapping days with months and vice versa. This is a bug, as Excel is not abiding by the system culture on interpreting local date formats.

Question

When viewing .csv files in PrizmDoc Viewer, the dates in the CSV file are in UK format (DD/MM/YYYY). However, if the DD is lower than 13 it is converted to US date format (MM/DD/YYYY).

Answer

Workaround:

The suggested workaround is to use Excel files instead of CSV to avoid this situation. Excel file format stores date/time format in the file.

Issue:

This is a bug in the MS Excel COM Interop that is being used by the product (MsOfficeConverter). Here is the related Excel bug: https://social.msdn.microsoft.com/Forums/vstudio/en-US/82248560-dabd-4c90-b1e2-793b2f32b257/excel-bug-handling-dates-in-csv-files-using-microsoftofficeinteropexcel?forum=exceldev

Problem description:

When using MS Excel Interop to open CSV files, all date/times there are being interpreted with “en-US” locale, regardless of actual system locale. Here is the description from the bug link above:

Excel interpreting dates when its reads csv files via .NET Interop. It is not a excel formatting issue per say. When excel accesses information such as dates (which are stored as numbers in memory to support arithmetic operations) from text files, it has to convert the date from textual representation (within the csv file, such as 2012-09-12) to the equivalent number in Excel memory (e.g. 41164 which represents 2012-09-12). When we use Interop to access this number in memory, many are interpreted incorrectly – swapping days with months and vice versa. This is a bug, as Excel is not abiding by the system culture on interpreting local date formats.

Question

I would like to remove the mark selection handles from the marks (annotations and redactions) in the viewer so that my users can’t resize marks, but so they can still move the marks around. How can I do this?

Answer

The easiest way to achieve the functionality you’re looking for would be to simply change the CSS for the mark handles to set their display to none !important. The CSS for the mark handles can be found in viewercontrol.css. See the following code for an example:

/* mark selection handles */
.pccMarkHandleTopLeft,
.pccMarkHandleTopCenter,
.pccMarkHandleTopRight,
.pccMarkHandleMidLeft,
.pccMarkHandleMidRight,
.pccMarkHandleBottomLeft,
.pccMarkHandleBottomCenter,
.pccMarkHandleBottomRight,
.pccMarkHandlePoint,
.pccMarkHandleTextSelectionStart,
.pccMarkHandleTextSelectionEnd {
    position: absolute;
    width: 40px;
    height: 40px;
    display: none !important;
    background-image: url(data:image/png;base64,iVBORw...);
}

@media screen and (-webkit-min-device-pixel-ratio: 2), 
       screen and (min-resolution: 2dppx),
       screen and (min-resolution: 192dpi) {
    .pccMarkHandleTopLeft, 
    .pccMarkHandleTopCenter, 
    .pccMarkHandleTopRight, 
    .pccMarkHandleMidLeft, 
    .pccMarkHandleMidRight, 
    .pccMarkHandleBottomLeft, 
    .pccMarkHandleBottomCenter, 
    .pccMarkHandleBottomRight, 
    .pccMarkHandlePoint, 
    .pccMarkHandleTextSelectionStart, 
    .pccMarkHandleTextSelectionEnd {
        -webkit-background-size: 40px 40px;
                background-size: 40px;
        display: none !important;
        background-image: url(data:image/png;base64,iVBORw...);
    }
}

You will want to set the !important flag so that the functions inside viewercontrol don’t set the display back to block.

One thing you may want to do is separate out pccMarkHandleTextSelectionStart and pccMarkHandleTextSelectionEnd to not include display: none. This way, the text selection annotations are able to be edited, since they are reliant on the handles for "movement" because they select a portion of the text signified by the handles. 

Question

Is there a way to modify the colors used in PrizmDoc Viewer’s search results? In particular, the currently selected search result has a very similar color to the other results from the same term. Is there a way to increase the contrast?

Answer

Currently, we don’t support the ability to set anything other than the highlight color through the search API.

There is a feature request to enable such modifications:

https://ideas.accusoft.com/ideas/PDV-I-531

Question

Why is the viewer not rendering my PDF?

Answer

Please check the developer console of your web browser to troubleshoot issues with documents not rendering, our product will report all errors and debugging information there.

Question

Where can I find the documentation for Accusoft PDF Viewer?

Answer

Our product documentation is located here.

Question

When using the PrizmDoc samples, the sample documents included are taking close to 1 minute to load in the viewer. The same also happens when uploading files into the sample.

The server processes are showing minimal impact on CPU and memory. However, the hard drive was spiking to 100% utilization sporadically.

Answer

We have found that Windows Defender with enabled Real-Time scanning can significantly impact performance. Once Real-Time scanning was disabled, we found this issue to be immediately resolved.

To disable Windows Defender, you can do the following:

  1. Right-click on the Windows Logo in the lower left-hand corner and select Control Panel.
  2. Select Windows Defender and then select Settings.
  3. Under the Real-Time protection section, slide the switch to Off.
Question

In the PrizmDoc Viewer, what are the two different ways to load annotation layers?

Answer

PrizmDoc has two options for loading annotations, the “My Annotations” pane and the “Annotations for Review” pane.

The “My Annotations” pane is used to load a single annotation layer for editing. You can add, delete, or make changes to annotations and then save those changes using the “My Annotations” pane.

The “Annotations for Review” pane is used for viewing annotations. You can load as many annotation layers for viewing as you would like. You cannot interact with annotations loaded in this way, but you are able to make comments on them. You can toggle between any of these layers to hide them. You can also merge these annotations to the currently loaded annotation layer from “My Annotations”.

For more information see our documentation here: https://help.accusoft.com/PrizmDoc/latest/HTML/Annotation_Layers.html

Question

What browsers are supported by Accusoft PDF Viewer?

Answer
  • Windows: All chromium based browsers such as Microsoft Edge and Google Chrome.
  • Mac: Safari
  • iOS: Native Safari Browser
  • Android: Native Chrome Browser