Technical FAQs

Question

For ImageGear .NET, what are the feature differences between an OCR Standard license, an OCR Plus license, and an OCR Asian license?

https://www.accusoft.com/products/imagegear-collection/imagegear-dot-net/#pricing

Answer

ImageGear’s OCR library has three different functionality options that you can choose for your website or application. The primary difference between the three options is the output formats created by the OCR engine. The options for your development are as follows:

  1. OCR Standard:
    The standard edition creates output formats for Western languages such as English. The standard edition outputs text only files and generates a PDF. The file formats it includes are searchable text PDFs and text documents.

  2. OCR Plus:
    The standard plus edition creates formatted outputs for Western languages like English. The formatted output is created with recognition technology that identifies font detail, locates image zones, and recognizes table structure in order to create a representation of the original document. The file formats it includes are Word, Excel, HTML, searchable PDF, and text documents.

  3. OCR Asian:
    The Asian edition creates a formatted output for Asian languages like Chinese, Japanese, and Korean. This formatted output is created with the same recognition technology as the Standard Plus that identifies font detail, locates image zones, and recognizes table structure. It also creates a representation of the original file. Formats include Word, Excel, HTML, searchable PDF, and text documents.

Having the right technology in place is essential for healthcare organizations seeking to deliver better patient outcomes. That’s why medical technology developers are working hard to build the next generation of software tools that will help medical professionals to deliver care more effectively. 

Annotation features provide a number of benefits in these ongoing efforts. Although typically associated with editing and workplace collaboration, medical annotations also have a very different and very specific role when it comes to diagnostic imaging and patient health records.

Enhancing Healthcare Collaboration with Annotations

One of the most straightforward use cases for medical annotation is communicating important information regarding diagnostic images. As images like MRIs and X-rays are passed back and forth between providers, radiologists, technicians, and clinicians, the ability to add comments and point out important details greatly reduces the chance of confusion or of some critical detail being overlooked.

The challenge in these cases, however, is to annotate images and documents without altering the integrity of the original files. This requires healthcare technology developers to build solutions that can retain an unaltered version of the file even as multiple collaborators view and make comments. 

Medical Annotation and Machine Learning

Healthcare solutions are rapidly incorporating sophisticated machine learning tools to analyze large quantities of data and make a quick, accurate diagnosis of conditions. Before these powerful tools can perform that diagnostic work, they need to be properly trained to know what they’re looking for, especially when it comes to very nuanced differences between scanned images and seemingly unrelated details in patient records.

By using annotation tools, medical technology specialists can provide excellent guidance for machine learning development. An MRI scan, for instance, contains so much information that an AI-driven program isn’t going to know what to look for unless the key elements are called out with annotations that indicate certain parts of the image or provide comments about noteworthy aspects.

The DICOM Dilemma

While many software integrations allow developers to incorporate annotation tools for common file formats like PDF and JPEG, the healthcare sector presents a unique challenge in the form of DICOM files. This industry-specific format contains both images and important metadata identifiers that provide information about the image itself and the patient in question. While there are ways to extract images from DICOM files and convert them into a more manageable format, doing so could endanger compliance status or permanently degrade the image quality.

Developers working on healthcare technology solutions need to make sure they can not only deliver annotation tools, but also the ability to add annotations to DICOM files without altering the source file itself. 

Mastering Medical Annotation with ImageGear Medical

ImageGear Medical provides a broad range of XML-based annotation features that allows healthcare software developers to implement UI elements for marking up both images and documents. Since this powerful imaging SDK also gives users the ability to create and view DICOM files, it can quickly enhance the functionality of medical applications to enhance collaboration and ensure diagnostic accuracy.

Once integrated into an application with a viewing UI, ImageGear Medical supports several commonly-utilized annotation marks that makes it easy for users to highlight certain aspects of an image, comment on them, and even cover up some elements using filled-in graphical objects. Annotations can also be grouped in layers to make them easier to manage and distinguish from one another.

ImageGear Medical annotation objects for DICOM include:

  • Text: Adds descriptive text using a variety of fonts, colors, and sizes. Opacity can be adjusted and the text object can appear with or without a border.
  • Point: Places a coordinate point on the image or document, which can be used to support other annotation marks.
  • Polyline: A series of connected straight lines formed by dragging and clicking a mouse or pointer.
  • Curve: Used for creating spline curve marks. Users can select multiple vertices and tensions when creating curves.
  • Ellipse: A circular outline mark that can be used to indicate important elements of an image or document. When filled, it can also cover up areas of the image.
  • Polygon: Like the ellipse, it can be filled or unfilled and is typically deployed to cover or highlight some aspect of an image or document. Polygons are especially useful for medical annotation because they can capture more lines and angles than simple rectangles or circles.

In order to maintain the integrity of the original image, ImageGear Medical stores annotations as a separate file that is overlaid upon the image during display. While annotations can be merged, or “burned in” the file, keeping them separate ensures that the original image itself is not altered directly. This is incredibly important when it comes to DICOM files, which often need to be kept on file for baseline comparisons on a future diagnosis.

Enhance Healthcare Flexibility with ImageGear Medical

Annotations and DICOM viewing support are just the beginning of ImageGear Medical’s expansive feature set. It also provides advanced filtering tools for sharpening and smoothing as well as image cleanup functions like despeckling, noise removal, and deskewing. With support for several dozen medical image and document formats, ImageGear Medical can easily convert files into easy-to-manage formats and compress files for efficient storage.

Available for .NET and C/C++ environments, ImageGear Medical can turn your healthcare application into a powerful annotation platform with full support for DICOM files. Start your free trial of this powerful SDK to discover first-hand how it can empower your medical annotation solution.

TAMPA, Fla. – Accusoft, the leader in document and imaging solutions for developers, is proud to announce its beta release testing program, which provides participants with real-time access to its latest product developments.

Customer input is a key factor in Accusoft’s mission to build better software integrations that deliver functionality like OCR, image cleanup, forms processing, file manipulation, and viewing solutions. Thanks to the new beta program, participants will get early access to brand new products and have the opportunity to provide feedback on the latest features for existing products. Developers can also customize what types of betas they would like to opt into so they can focus on products most relevant to their business.

“Our previous betas for PrizmDoc Editor and PrizmDoc Cells were extremely beneficial for everyone involved, “ says Mark Hansen, Product Manager. “Our team received rapid feedback that helped make our products better, while participants had the opportunity to shape those products to meet their specific requirements.”

By signing up for the beta program now, you can participate in the active beta for PrizmDoc Forms integration, which will allow you to repurpose (or use) your PDF forms to easily create, customize, and deploy as web forms anywhere. You’ll also be the first to know about new product offerings and have the ability to opt into beta releases for Accusoft’s existing products, such as ImageGear, FormSuite for Structured Forms, and PrizmDoc Suite.

To learn more about Accusoft’s exciting new beta program, please visit our website at https://www.accusoft.com/company/customers/beta-release-program.

About Accusoft:

Founded in 1991, Accusoft is a software development company specializing in content processing, conversion, and automation solutions. From out-of-the-box and configurable applications to APIs built for developers, Accusoft software enables users to solve their most complex workflow challenges and gain insights from content in any format, on any device. Backed by 40 patents, the company’s flagship products, including OnTask, PrizmDoc™ Viewer, and ImageGear, are designed to improve productivity, provide actionable data, and deliver results that matter. The Accusoft team is dedicated to continuous innovation through customer-centric product development, new version release, and a passion for understanding industry trends that drive consumer demand. Visit us at www.accusoft.com.

Question

Why do I get a “File Format Unrecognized” exception when trying to load a PDF document in ImageGear .NET?

Answer

You will need to set up your project to include PDF support if you want to work with PDF documents. Add a reference to ImageGear24.Formats.Pdf (if you’re using another version of ImageGear, make sure you’re adding the correct reference). Add the following line of code where you specify other resources:

using ImageGear.Formats.PDF;

Add the following lines of code before you begin working with PDFs:

ImGearFileFormats.Filters.Insert(0, ImGearPDF.CreatePDFFormat());
ImGearPDF.Initialize();

The documentation page linked here shows how to add PDF support to a project.

Question

When using OCR in ImageGear .NET, is there any way to distinguish between a capital/uppercase letter O and the number 0?

Answer

Not without context or a font that makes the difference clear (such as one with a slashed 0). ImageGear will properly recognize Oliver and 1530 as containing O and 0, respectively, but cannot reliably distinguish it when letters and numbers are mixed. That is, ImageGear may not reliably distinguish between 1ABO0F3 and 1AB0OF3.

Question

The logging for ImageGear C & C++ Deployment Packaging Wizard (DPW) is showing different output for some components since v19.3, why is this?

In ImageGear C & C++ v19.2 and prior, the DPW had additional logging information for the ARTX component in its deployment.log:

Deploying an application that uses the ARTXGUI library of ImageGear
ARTX Component requires the following merge modules to be installed:

Microsoft_VC90_CRT_x86_x64.msm

Microsoft_VC90_MFC_x86_x64.msm

But since v19.3, the logs are no longer telling me to install these modules. Is this a mistake, or are they no longer necessary?

Answer

This was an intentional change on our end, and the Deployment Packaging Wizard (DPW) is working as intended. We made some updates to the DPW in the latest release; one update is that the CRM requirements for CORE (which is required in every project) now also covers the ARTX component. If the DPW is not saying you need additional components to use the ARTX component, then you’ll be fine.

Question

Why do I get a “File Format Unrecognized” exception when trying to load a PDF document in ImageGear .NET?

Answer

You will need to set up your project to include PDF support if you want to work with PDF documents. Add a reference to ImageGear24.Formats.Pdf (if you’re using another version of ImageGear, make sure you’re adding the correct reference). Add the following line of code where you specify other resources:

using ImageGear.Formats.PDF;

Add the following lines of code before you begin working with PDFs:

ImGearFileFormats.Filters.Insert(0, ImGearPDF.CreatePDFFormat());
ImGearPDF.Initialize();

The documentation page linked here shows how to add PDF support to a project.

Question

How do I use a Network Drive path for Image and ART storage in my ImageGear .NET web application?

Answer

In an ImageGear .NET web application, you have to define the location of the images and annotations directory in the storageRootPath and artStorageRootPath configuration property.
In the current version of ImageGear .NET, the storageRootPath and artStorageRootPath do not work with a network drive path \\SERVER-NAME\sharefilename.

The workaround for this would be to create a Symbolic link from a local directory to the network drive directory.

  • To create a symbolic link: Open “Command Prompt” as Administrator and type in > mklink /d "local path" \\SERVER-NAME\sharefilename
  • Pass in the path of the symbolic link as image or art storage root path in your web.config: storageRootPath="local path" artStorageRootPath="local path"

Image compression has become such a ubiquitous aspect of the digital world that the average person doesn’t give it much thought. Even when they encounter textbook compression problems, such as running out of space for photos on their phones, waiting on a slow-loading webpage, or working with an overly pixelated image, they may not consider how effective compression techniques could resolve these issues.

Today’s software developers, by contrast, spend a lot of time thinking about how to incorporate better compression solutions into their applications. That’s why they frequently turn to image compression SDKs to help their end users better manage large and highly-detailed image files.

The Enduring Need for Image Compression

Although advancements in hard drive technology and easily scalable cloud storage have reduced many traditional data management concerns, large image files can still pose significant challenges. Many organizations that can’t utilize cloud storage options for compliance reasons or find the cost of those platforms prohibitively high. 

While they may be able to add more on-premises storage easily enough, this option can also quickly become quite costly. Companies often need to procure much more storage than they may need on a day-to-day basis in order to meet redundancy requirements. Scaling physical storage also locks firms into burdensome equipment refresh cycles.

But simply storing images is only part of the challenge of data management. Large files are more difficult to move, even if an organization has a customized solution in place. If images can’t be shared quickly and easily through a secure platform, users may turn to riskier third-party applications.

Image compression alleviates these problems by reducing the overall size of image files. By compressing image files, organizations can maximize their storage potential and share files more easily. Image compression can also improve website and application performance by reducing the time it takes to load images. 

Although there are many different methods of compressing images, they all involve algorithms that use a variety of shortcuts to reduce the overall size of pixel data. In some instances, compression involves the elimination of image data, which can degrade the image quality and make it impossible to return to its original size (lossy or irreversible compression). Other techniques retain the original image data, but can’t achieve the same level of compression (lossless or reversible compression). 

Image Compression SDKs and Your Applications

While there are many compression options available in commercial imaging software, organizations often need the ability to compress image files within their core business applications without any external dependencies. Opening an image file with another program not only takes additional time and disrupts efficient workflow, but it also creates the potential for security risks and version confusion.

Consider, for instance, a medical provider that needs to send a high-resolution MRI scan to another provider. If the file is too large to deliver electronically, someone may try to get around the problem by using another program to compress the scan and then send it as an attachment over email or share it through a cloud platform. Suddenly, the confidential image file has been accessed by potentially vulnerable third-party applications, which creates a serious compliance issue. To make matters worse, the compressed image may not be associated with the patient’s file in the EHR system. And that’s not even getting in the question of whether or not the compression technique used damaged the image integrity!

An image compression SDK like ImageGear allows developers to integrate the ability to compress and convert image files into their applications without compromising security, efficiency, or quality. Optimized, standards-based compression libraries with support of formats like TIFF, PDF, PDF/A, JPEG 2000, JPEG, and DICOM deliver fast compression/decompression capabilities while ensuring that images remain high quality. 

The primary advantage of integrating image compression capabilities directly into an application is the lack of third-party dependencies. This is crucial for software that is gathering and managing image files because it doesn’t cause any workflow disruptions. With an image compression SDK integration, image files can be shrunk down to more manageable sizes programmatically, which aids significantly in automated processes. Since the images are being compressed entirely within the application, it’s also easier to maintain strict version and access control throughout the life cycle of the file.

Image Compression SDKs vs Open Source Solutions

Many developers turn to open source compression libraries when looking to integrate image compression features into their applications. While this often seems like an easy, low cost solution, open source codecs can lead to unforeseen problems over time. Since many of them are not actively maintained, troublesome bugs can go unresolved and security gaps can create serious privacy risks.

One infamous example of this problem involved the widely used “Cornell Codec,” one of the first open source libraries that supported lossless JPEG compression. Developed in 1994, it was quickly adopted by many healthcare applications that needed to compress high-resolution medical images like MIRIs, CT scans, and X-Rays. 

Unfortunately, the codec had a problem. When it compressed images into DICOM files (the industry standard used in medical imaging applications), it produced an error that made them unreadable when they were decompressed. Since the Cornell Codec was an open source solution embedded into numerous applications, the problem went unresolved for many years until Accusoft developed a code based workaround for our customers.

By choosing a well-supported image compression SDK like ImageGear for their application’s compression needs, developers can rest easier knowing that they’re deploying a tried and true solution that won’t create unexpected problems for their customers. Another benefit of a comprehensive image compression SDK is that it will provide a variety of compression libraries that can accommodate almost any file type and use case. ImageGear, for example, supports more than a dozen unique image compression types, including JPEG (lossy/lossless/progressive), RAW, ASCII, and Deflate.

ImageGear: More Than an Image Compression SDK

Image compression is just one of ImageGear’s many powerful document and image processing features. A versatile code-based solution, ImageGear allows developers to quickly integrate image conversion and cleanup features to their application along with editing, annotation, viewing, scanning, and printing capabilities. With support for a huge number of today’s leading document and image file formats as well as medical imaging support with ImageGear Medical, this SDK toolkit delivers the functionality developers need to get their applications to market faster. See what ImageGear can do for your application today by downloading a free trial.

Question

How do I use a Network Drive path for Image and ART storage in my ImageGear .NET web application?

Answer

In an ImageGear .NET web application, you have to define the location of the images and annotations directory in the storageRootPath and artStorageRootPath configuration property.
In the current version of ImageGear .NET, the storageRootPath and artStorageRootPath do not work with a network drive path \\SERVER-NAME\sharefilename.

The workaround for this would be to create a Symbolic link from a local directory to the network drive directory.

  • To create a symbolic link: Open “Command Prompt” as Administrator and type in > mklink /d "local path" \\SERVER-NAME\sharefilename
  • Pass in the path of the symbolic link as image or art storage root path in your web.config: storageRootPath="local path" artStorageRootPath="local path"