Technical FAQs

Question

Can I host multiple PrizmDoc viewers on a single page?

Answer

It is possible to host multiple viewers on a single page. The following example leverages Bootstrap’s tab implementation:

<!DOCTYPE html>

<html lang="en">
<head>
    <!-- Metadata -->
    <meta charset="utf-8" />
    <meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1, user-scalable=no" />
    <meta name="description" content="" />

    <!-- Title -->
    <title>AccuSample</title>

    <!-- Libraries -->
    <link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/normalize/7.0.0/normalize.min.css">
    <link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/4.0.0/css/bootstrap.min.css">

    <!-- PrizmCSS -->
    <link rel="stylesheet" href="https://pcc-demos.accusoft.com/static/viewer-latest/css/viewercontrol.css">
    <link rel="stylesheet" href="https://pcc-demos.accusoft.com/static/viewer-latest/css/viewer.css">

    <!-- Inline Stylesheet -->
    <style>
        body {
            overflow-y: hidden;
        }
        #viewer1, #viewer2 {
            height: calc(100vh - 3em);
            width: 100%;
        }
    </style>

</head>
<body>
    <!-- #main -->
    <main class="container">
        <ul class="nav nav-tabs" role="tablist">
            <li class="nav-item">
                <a class="nav-link active" id="viewer1-tab" data-toggle="tab" href="#viewer1">Viewer 1</a>
            </li>
            <li class="nav-item">
                <a class="nav-link" id="viewer2-tab" data-toggle="tab" href="#viewer2">Viewer 2</a>
            </li>
        </ul>

        <div class="tab-content">
            <div class="tab-pane fade show active" id="viewer1" role="tabpanel">
                <div id="viewer1">
                </div>
            </div>
            <div class="tab-pane fade" id="viewer2" role="tabpanel">
                <div id="viewer2">
                </div>
            </div>
        </div>
    </main>

    <!-- Libraries -->
    <script src="https://cdnjs.cloudflare.com/ajax/libs/jquery/3.2.1/jquery.min.js"></script>
    <script src="https://cdnjs.cloudflare.com/ajax/libs/popper.js/1.14.1/umd/popper.min.js"></script>
    <script src="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/4.0.0/js/bootstrap.min.js"></script>
    <script src="https://cdnjs.cloudflare.com/ajax/libs/underscore.js/1.8.3/underscore-min.js"></script>

    <!-- PrizmJS -->
    <script src="https://api.accusoft.com/v1/docstore/viewer/assets/classic/bundle.js"></script>
    <script src="https://pcc-demos.accusoft.com/static/viewer-latest/js/jquery.hotkeys.min.js"></script>
    <script src="https://pcc-demos.accusoft.com/static/viewer-latest/js/viewercontrol.js"></script>
    <script src="https://pcc-demos.accusoft.com/static/viewer-latest/js/viewer.js"></script>

    <!-- Inline Script -->
    <script>
        var viewingSessionId1;
        var viewerControl1;
        var viewingSessionId2;
        var viewerControl2;

        $(document).ready(function() {
            $.ajax({
                "type": "post",
                "url": "https://api.accusoft.com/PAS/V1/ViewingSession",
                "headers": {
                    "acs-api-key": ""
                },
                "data": JSON.stringify({
                    "source": {
                        "type": "url",
                        "url": ""
                    }
                })
            }).done(function(response) {
                viewingSessionId1 = response["viewingSessionId"];

                // Initialize viewer
                viewerControl1 = $("#viewer1").pccViewer({ 
                    documentID: viewingSessionId1,
                    imageHandlerUrl: "https://api.accusoft.com/v2/viewers/proxy",
                    language: languageItems,
                    template: htmlTemplates
                }).viewerControl;
            });

            $.ajax({
                "type": "post",
                "url": "https://api.accusoft.com/PAS/V1/ViewingSession",
                "headers": {
                    "acs-api-key": ""
                },
                "data": JSON.stringify({
                    "source": {
                        "type": "url",
                        "url": ""
                    }
                })
            }).done(function(response) {
                viewingSessionId2 = response["viewingSessionId"];

                // Initialize viewer
                viewerControl2 = $("#viewer2").pccViewer({ 
                    documentID: viewingSessionId2,
                    imageHandlerUrl: "https://api.accusoft.com/v2/viewers/proxy",
                    language: languageItems,
                    template: htmlTemplates
                }).viewerControl;
            });
        });
    </script>
</body>
</html>
View Detail >

FormFix forms identification processing

Without accurate forms recognition, developers will have a hard time building effective forms processing applications. The primary advantage of forms processing workflows is the ability to automate the data capture process, but the benefits of automation quickly evaporate if the system continually misidentifies forms or can’t align document images cleanly for accurate data capture. Accusoft’s FormFix SDK ensures that forms processing applications get off to the best start possible by quickly matching and aligning form images to predefined templates.

When to Use FormFix

FormFix works with structured forms that feature a standardized layout with fields located in fixed positions. The SDK has a number of use cases as part of a broader forms processing and data capture workflow. Its primary function is to identify form images and route them to the proper destination. In some instances, this will mean handing the recognized form off to the SmartZone integration, which performs optical character recognition (OCR) and intelligent character recognition (ICR) to extract printed text from form fields. If data capture doesn’t need to be done immediately, the form can instead be routed to a storage location for later reference.

But FormFix can do more than simply identify forms. It also features powerful optical mark recognition (OMR) capabilities, which allows it to detect marks in fillable bubbles or checkboxes that are commonly used on a wide range of forms. Without OMR, a forms processing application will be forced to rely on manual data entry for any form that contains these marks, which typically indicate information like marital status, health history, ethnic background, or a variety of demographic data. Deploying OMR to process these forms automatically helps to minimize the risk of human error and speeds up processing times. In addition to being able to read single or multiple marks, FormFix can also use OMR to detect the presence of a signature on a document. 

 

Creating Master Form Templates for Identification

Before FormFix can start identifying form images, it first needs FormSets to work with. A FormSet consists of several FormDefinitions, each of which represent a document form page. Every FormDefinition object contains compressed image data of a form template and indicates the fields from which data can be extracted. The individual fields can also have specific instructions associated with them that should be performed at the time of processing. This could include despeckling or other forms of image enhancement or clean-up. 

FormSets are created by the FormDirector API, which allows developers to designate what information needs to be extracted and where on a form it should be extracted from. Setting up a FormSet template for a IRS 1040 form, for instance, would involve designating which fields on an unfilled form will be matched and aligned so the information contained in them can be captured accurately. Developers can also create their FormSets using the FormAssist application, which is a graphical interface for FormDirector that allows them to easily upload blank form images and specify how each field should be handled during processing.

How FormFix Identifies Form Images

After a form image is uploaded and cleaned up (usually using the ScanFix Xpress SDK), it can be identified and aligned for data capture. FormFix uses its forms recognition processor to examine the input image and compare it to the available FormSets on file. It does this by looking at the FormDefinitions within the FormSets and matching their embedded template images to the current input image. Once a potential match is identified, FormFix selects the appropriate template and provides a confidence value for all identification candidates.

The FormFix alignment algorithm then takes over, placing the input image on the form template and making a series of adjustments to ensure that the field areas line up as precisely as possible. It can also perform form image drop-out, which removes pre-printed graphical elements, found in the template, like form field boxes and instructional text and leaves only the filled-in information behind. This helps improve recognition accuracy, whether the application is using SmartZone OCR/ICR or deploying FormFix’s OMR capabilities.

Improving FormFix Forms Recognition

Although FormFix is capable of quickly matching form images with the master forms the application has on file, there are a few steps developers can take to streamline the forms recognition process and improve workflow performance. For example, FormFix can be set to only compare images at 90, 180, and 270 degrees, or to only exert certain amounts of effort during forms identification. 

When setting up templates, developers can define what image operations need to be completed for each image input. These parameters can be set at different hierarchies, so some operations may be applied to all forms while others are only applied to specific FormDefinitions or form fields. This eliminates unnecessary image processing operations that may slow down workflows while still ensuring that consistent adjustments are being made where they’re needed.

If possible, barcodes can be affixed to different form types to quickly indicate which template needs to be referenced for the form alignment process. This allows FormFix to bypass the identification process and proceed directly to aligning the form images for dropout and recognition. 

Accelerate Your Forms Processing Workflow with FormFix

Accusoft’s FormFix SDK helps your forms processing application to quickly identify form images, prepare documents for zonal and full page OCR/ICR, and extract information with OMR functionality. Fully customizable to meet the needs of your forms workflow, FormFix also includes a variety of image cleanup tools that can remove imperfections and noise to improve recognition accuracy.

To learn more about the capabilities of the FormFix SDK and see how it fits into a broader forms processing solution, download our FormFix Fact Sheet today or contact one of our integration experts for more information.

View Detail >
Question

In PrizmDoc, my document appears to be small on the page relative to the viewer. How can I fix this?

enter image description here

Answer

By default, PrizmDoc renders a PDF file according to the MediaBox, which is normally the same as CropBox, though sometimes this is not the case. The larger area you see in the PrizmDoc Viewer is the size of the MediaBox. Please note that the product provides the fileTypes.pdf.pageBoundaries control option (or useCropBox in the older versions) to change the default behavior. Try setting the option to cropBox in the Central Configuration File in order to get the PDF content rendered according to the CropBox. You can read more about configuring image frame rendering in our documentation here.

For additional reading, see 7.7.3.3 on “User Space” of Adobe’s PDF 1.7 specification:

https://www.adobe.com/content/dam/acom/en/devnet/pdf/pdfs/PDF32000_2008.pdf

Note: In some older versions of PrizmDoc, there exists an issue where setting the pageBoundaries field to cropBox can cause light blurring/distorting on the page. This issue was addressed in version 13.4.

View Detail >
Question

In PrizmDoc, my document appears to be small on the page relative to the viewer. How can I fix this?

enter image description here

Answer

By default, PrizmDoc renders a PDF file according to the MediaBox, which is normally the same as CropBox, though sometimes this is not the case. The larger area you see in the PrizmDoc Viewer is the size of the MediaBox. Please note that the product provides the fileTypes.pdf.pageBoundaries control option (or useCropBox in the older versions) to change the default behavior. Try setting the option to cropBox in the Central Configuration File in order to get the PDF content rendered according to the CropBox. You can read more about configuring image frame rendering in our documentation here.

For additional reading, see 7.7.3.3 on “User Space” of Adobe’s PDF 1.7 specification:

https://www.adobe.com/content/dam/acom/en/devnet/pdf/pdfs/PDF32000_2008.pdf

Note: In some older versions of PrizmDoc, there exists an issue where setting the pageBoundaries field to cropBox can cause light blurring/distorting on the page. This issue was addressed in version 13.4.

View Detail >
Question

With PrizmDoc Viewer, can I have more than a single viewer on the same page?

Answer

Yes, just initialize a second viewer on another <div> in the page. You can use the initialization code here more than once within the same page.

View Detail >
Question

With PrizmDoc Viewer, can I have more than a single viewer on the same page?

Answer

Yes, just initialize a second viewer on another <div> in the page. You can use the initialization code here more than once within the same page.

View Detail >

PDFs HTML embed

As digital processes become more commonplace, it’s more important than ever for organizations to have the tools in place to manage electronic documents effectively. The evolution of PDF viewing technology continues to provide new levels of flexibility for software applications. Now that HTML5 is capable of rendering PDF data within a conventional browser, developers are looking for new ways to make the viewing experience even more seamless. By embedding PDFs in HTML, they can continue to streamline document viewing and reduce the need for external software.

Why Embed a PDF in HTML?

Sharing a PDF online is far easier to do today than it was just a decade ago. For many years, the two most commonly used options were providing a link to download the file directly from a server or sending it as an attachment in an email. Once the file was downloaded, it could be opened and viewed with PDF reader software installed on a computer. This, of course, introduced numerous security risks that are associated with downloadable files and email attachments.

The widespread adoption of cloud storage has made it very convenient to share a PDF file and even manage who has access to it. And since most modern browsers can view PDFs without needing to download the file, providing a link is typically all that’s necessary to pass the file along.

While this solution is usually sufficient for the personal needs of an individual user, it’s not a practical option for even a small-scale business when it comes to public-facing document management. Organizations want to retain control over their files with respect to how they’re accessed and displayed. By embedding PDFs in HTML, they can keep their documents within their secure application environment where they have full control over how they’re managed, shared, and viewed. For developers looking to provide a seamless user experience, building options for embedded PDFs into their software is critically important.

The Value of an Integrated PDF Viewer

Since most modern browsers can utilize HTML5 to render PDF files, developers could lean on those capabilities without building a dedicated PDF viewer for their application. That decision will very quickly lead to some unpleasant complications, however. In the first place, they are leaving a lot to chance in terms of the viewing experience. Not every browser renders PDF files the same way, so it’s very possible that two different users could have two very different experiences when viewing a document. In some cases, that could mean nothing more than a missing font that’s replaced with an alternative. But in other cases, it could mean that the document doesn’t open at all or is missing important graphical elements.

This approach also forces users to make do with whatever PDF functionality is incorporated into their browser’s viewer. In most cases, that will mean subpar search performance, a lack of responsive mobile controls, and no annotation features. The browser may also have trouble with some of the less common PDF specifications, making it impossible for some users to even view a document.

By embedding a JavaScript-based PDF viewer into their application, developers can ensure that documents will display the correct way every time. Since the viewing is handled through a viewer embedded into the web application by default, it will be the same no matter what kind of browser or operating system is being used. A customizable viewer also allows developers to adjust the interface to permit or hide certain features, such as downloading or markup tools.

The open-source PDF.js library is a popular choice for many web applications, but it comes with a number of well-documented shortcomings. In addition to lacking key features like annotation, it also doesn’t support the entire PDF standard and does not provide a responsive UI for mobile devices. For developers looking to add more robust features, working with PDF.js often entails quite a bit of additional coding and engineering to build those capabilities from the ground up.

Embed PDFs in HTML with Accusoft PDF Viewer

Accusoft PDF Viewer takes the foundation of PDF.js and provides robust enhancements to meet the viewing needs of today’s applications. In addition to incredibly fast text search, expanded PDF standard support, and optimization for high-resolution displays, this lightweight SDK is also equipped with a responsive UI that adapts automatically to mobile screens. Developers can integrate essential mobile features like pinch to zoom quickly and easy, with no additional integrations or engineering required.

With no external dependencies or complicated server configurations, Accusoft PDF Viewer integrates into a web-based application with less than 10 lines of code. Once the viewer is in place, developers can embed PDFs in HTML and easily render them to provide a state-of-the-art PDF viewing experience regardless of the browser or device users have at their disposal. And since the UI can be customized to your application’s needs, there’s no reason to sacrifice control for the sake of viewing convenience.

Accusoft PDF Viewer is a JavaScript SDK that you can incorporate into your application environment quickly and easily to provide much greater viewing control and functionality than is possible with a standard browser viewer or base PDF.js library. If you’re planning to embed PDFs in HTML as part of your software solution, taking just a few moments to integrate versatile and responsive viewing tools can ensure a high-quality viewing experience. Download Accusoft PDF Viewer Standard Version today at no cost to see how easily it can transform your application’s HTML5 viewing potential.

For additional features like annotation, eSignature, and UI customization, contact one of our solutions experts to upgrade to Professional Version.

View Detail >

For today’s healthcare organizations, having a versatile electronic health records (EHR) system is essential for running an efficient practice and connecting to other medical providers. Thanks to EHRs, practices can ensure that they’re getting a complete picture of a patient’s health and treatment history, which allows them to deliver much better care outcomes. As developers continue to refine the usability of these systems, they need to consider how they can improve core features like healthcare electronic document management and medical imaging support.

Managing Medical Documents

A typical EHR system has to be able to handle quite a lot of document types. Anyone who has visited a healthcare provider is quite familiar with the myriad forms used to gather patient information. Many of those forms end up being converted into digital formats that need to be managed within the EHR system. Then there are digital versions of lab reports, physician notes, invoices, and financial documents. 

While EHR systems may utilize databases to store much of the information they need, healthcare providers still need to be able to produce physical documents and view digital files in many situations. This could include communicating information to patients, complying with regulatory requests, or filing a financial claim of some kind. More importantly, they also rely on digital documents to enter data into the EHR system. The push toward interoperability between EHR systems has improved information sharing, but there are still many instances where medical records are delivered in the form of a document that needs to be managed securely.

Document Conversion

If an EHR application lacks the right file conversion capabilities, viewing and extracting data from those documents could prove difficult. The last thing a practice wants to do is actually remove them from the secure EHR system to open and convert the files using separate software that may not be compliant when it comes to handling healthcare information. Even if the external application is secure, transferring files over, converting them, and then transferring them back is both inefficient and creates unnecessary risk (especially if someone forgets to delete the original file or move it back into the EHR environment).

ImageGear Medical has a document conversion feature that supports a wide range of file types, allowing developers to build EHR applications capable of quickly converting incoming documents. They can even set up their solution to perform conversion tasks programmatically to help streamline workflows and minimize human error. This helps practices to get a better handle on document management, ensuring that they will be able to do everything they need with files completely within the EHR application.

Other Essential Document Features

But ImageGear Medical’s document capabilities go far beyond just conversion. With full annotation support, developers can provide markup tools within the EHR system that allow physicians to make notes and comments on various documents. This allows them to share information much more easily. If a physician has a question about a diagnosis or a prescription, for instance, they can simply leave an annotation note directly on the document rather than referring to it in a separate message.

ImageGear Medical also allows applications to perform full-page optical character recognition (OCR), which can quickly read and extract text from document and image files. This feature is especially useful for capturing text from scanned images of documents, which can then be used to create a searchable PDF or fill form fields within the EHR system. The OCR engine not only reads most Western languages, but also detects and reads several Eastern language characters.

Managing DICOM Files

One of the biggest challenges healthcare organizations face is with managing medical imaging files. When providers need to send X-Rays, MRIs, or CT Scans, they use a standardized file format known as Digital Imaging and Communications in Medicine (DICOM) files. These files are more than just image files, however. They contain extensive datasets that provide a patient’s information along with image pixel data for multi-dimensional medical scans. A DICOM file can be quite large due to the high-resolution image data used by most medical imaging equipment.

Although most EHR systems are capable of transmitting DICOM files (via a DICOM out or DICOM send feature), they usually can’t actually view them in their native format. Since Windows doesn’t recognize them as image files, additional viewing software is typically needed to open and view them. This is why physical storage, like discs and flash drives, are often used to transfer DICOM files along with the necessary viewing software.

ImageGear Medical helps to solve the DICOM dilemma thanks to its extensive conversion and compression capabilities. By decoding the complex data contained within the file, ImageGear Medical can convert DICOM files into image formats that are much easier to view and manage. This is especially useful for smaller practices that don’t have a picture archiving and communication system (PACS) capable of storing, retrieving, distributing, and viewing high-quality medical images. 

Converting DICOM files makes it possible for healthcare professionals to view them on any device connected with their EHR system. That could include tablets or other IoT devices that healthcare technology companies are rolling out to put critical medical data on the front lines of everyday care. Developers can also use ImageGear Medical’s conversion tools to allow their EHR system to share viewable versions of diagnostic scans with patients, allowing practices to make good on the promise of providing patients access to their essential health data at all times. 

The sheer size of DICOM files makes them difficult for many practices to manage. Simply compressing them tends to degrade the image data, which can create significant problems when files are unpacked and opened for viewing. Losing even a small degree of image quality can make it much harder to render an accurate diagnosis. In some cases, poorly designed compression can even make it nearly impossible to uncompress again at all. Thanks to powerful lossless compression technology, ImageGear Medical makes it easier to share medical images between providers without damaging the integrity of the original data.

Expand EHR Capabilities with ImageGear Medical

Accusoft’s imaging, conversion, and compression technology has been supporting the needs of the healthcare industry for decades. As developers work to expand the capabilities of their EHR applications, our engineers are busy improving the medical SDKs that will provide them with the features they need to stand out in a competitive market. 

ImageGear Medical utilizes a combination of efficient code and elegant APIs to deliver the document and image processing tools EHR systems require. For a closer look at this dynamic SDKs capabilities, check out our extensive developer resources today or download a free trial to get started.

View Detail >