Technical FAQs

Question

How do I remove XMP Data from my image using ImageGear .NET?

Answer

When removing XMP data in ImageGear, the simplest way to do this is to set the XMP Metadata node to null, like so:

ImGearSimplifiedMetadata.Initialize(); 
doc.Metadata.XMP = new ImGearXMPMetadataRoot();

Or, you can traverse through the metadata tree and remove each node from the tree:

// Example code. Not thoroughly tested
private static void RemoveXmp(ImGearMetadataTree tree)
{
ArrayList toRemove = new ArrayList();
foreach (ImGearMetadataNode node in tree.Children)
{
    if (node is ImGearMetadataTree)
        RemoveXmp((ImGearMetadataTree)node);

    if (node.Format != ImGearMetadataFormats.XMP)
        continue;

    toRemove.Add(node);
}

foreach (ImGearMetadataNode node in toRemove)
    tree.Children.Remove(node);
}
View Detail >
Question

I encounter an Unhandled Exception error, as shown below, in ImageGear when trying to load a page into the recognition engine.

Error Message: An unhandled exception of type
‘ImageGear.Core.ImGearException’ occurred in ImageGear22.Core.dll

Additional information: IMG_DPI_WARN (0x4C711): Non-supported
resolution. Value1:0x4C711

What is causing this and how can I fix it?

Answer

This is probably because the original image used to create the page didn’t have a Resolution Unit set.

Resolution unit not set in original image

To fix this, check if the page has a Resolution Unit set. If it does not, set it to inches. You should also set the DPI of the image as those values were probably not carried over from the original image since the Resolution Unit wasn’t set. The following code demonstrates how to do this.

// Open file and load page.
using (var inStream = new FileStream(@"C:\Path\To\InputImage.jpg", FileMode.Open, FileAccess.Read, FileShare.Read))
{
    // Load first page.
    ImGearPage igPage = ImGearFileFormats.LoadPage(inStream, firstPage);

    if (igPage.DIB.ImageResolution.Units == ImGearResolutionUnits.NO_ABS)
    {
        igPage.DIB.ImageResolution.Units = ImGearResolutionUnits.INCHES;
        igPage.DIB.ImageResolution.XNumerator = 300;
        igPage.DIB.ImageResolution.XDenominator = 1;
        igPage.DIB.ImageResolution.YNumerator = 300;
        igPage.DIB.ImageResolution.YDenominator = 1;
    }

    using (var outStream = new FileStream(@"C:\Path\To\OutputImage.jpg", FileMode.OpenOrCreate, FileAccess.ReadWrite))
    {
        // Import the page into the recognition engine.
        using (ImGearRecPage recognitionPage = recognitionEngine.ImportPage((ImGearRasterPage)igPage))
        {
            // Preprocess the page.
            recognitionPage.Image.Preprocess();

            // Perform recognition.
            recognitionPage.Recognize();

            // Write the page to the output file.
            recognitionEngine.OutputManager.DirectTextFormat = ImGearRecDirectTextFormat.SimpleText;
            recognitionEngine.OutputManager.WriteDirectText(recognitionPage, outStream);
        }
    }
}
View Detail >

 

PrizmDoc Cloud API

Powerful patient portals are now essential for healthcare organizations to deliver high-quality care, even at a distance. Despite advancements around functionality, however, challenges remain. As noted by Healthcare Info Security, many healthcare providers still struggle with providing solutions to patients in an easily accessible portal that provides the security they require by law.

Here, HIPAA compliance is critical. Healthcare organizations need portal solutions that deliver valuable information without undermining regulatory requirements around data security and handling. Creating innovative, secure patient portals demands HIPAA-compliant tools that deliver advanced viewing and redaction tools while keeping privacy in practice.

The State of Healthcare Security

Security remains a problem for healthcare organizations as attackers ramp up efforts to access private patient and operational information. The healthcare industry saw more than 41 million records breached in 2019 and new attack vectors are now emerging as hackers look to leverage pandemic pressures and breach corporate security. It’s no surprise, then, that last year saw 28,261 HIPAA complaints, the highest number ever recorded, as organizations deployed more user-friendly technology and attackers looked to capitalize on potential weaknesses.

Ramping up security in patient portals and meeting emerging patient needs is a priority for organizations. Accusoft’s PrizmDoc Cloud, a HIPAA compliant solution, is capable of offering user-friendly portal capabilities inside your own secure application. The right combination of existing technology and cloud-based application programming interfaces (APIs) can take your patient portal to the next level. Let’s break down five key cloud-based APIs that can help patient portals deliver on practical potential.

Robust Document Viewing with PrizmDoc Cloud API

Effective medical care depends on documents. From patient consent forms to test results and referrals from other healthcare practices, documents form the core of custom-built treatment plans. While the transition to electronic health records (EHRs) has helped reduce the complexity and confusion that comes with paper-based processes, this digital transition has introduced the challenge of document diversity. 

From typical Word documents to Excel spreadsheets and scanned images of handwritten forms, patients need the ability to access documents on-demand, while healthcare organizations must ensure that patient access options are both secure and HIPAA-compliant.

The PrizmDoc HTML5 Document Viewing API offers document and image viewing while also streamlining the process with key features including:

  • Responsive Web UI — Patients and staff can easily view documents and images that are scaled to fit their tablet, laptop, or mobile phone.
  • Configurable Controls — Organizations can easily enable or disable tabs, localization, rendering options, and encryption within their patient portal.
  • Microsoft Office (MSO) Conversion — Healthcare agencies can integrate true native viewing of Word, Excel, and PowerPoint documents.

Reliable PII Redaction

Data privacy is paramount for HIPAA compliance. As noted by Managed Healthcare Executive, this is especially critical in the world of COVID-19. With telehealth now the “new normal” — and likely to continue long after the pandemic subsides — organizations must ensure that protection of personally identifiable information (PII) remains intact.

While robust encryption and identity access management (IAM) tools form part of this function, redaction is another critical aspect. Consider the case of children. As noted by the Health Info Security piece, although parents typically have complete access to the medical records of children under 12, PII for those between the ages of 13 and 18 — such as mental health records — may be restricted. For healthcare agencies, this requires patient portal solutions that allow parents access to some data while also protecting specific PII. Here, robust redaction APIs that allow organizations to obfuscate key information are critical to meet regulatory requirements without compromising ease-of-access.

Regulated Image Compression

Images form a critical component of effective patient prognosis and treatment plans, and while DICOM files used in high-fidelity imaging are often a priority for medical agencies, there’s also a need for image compression solutions that enable the portability of more common image types such as JPEGs.

Consider the simple case of patient identification. By attaching high-quality photos to patient records, medical staff are better equipped to ensure the individual they’re assisting — virtually or in-person — is the patient linked to the account. High-quality JPEG photos are also useful to record and track the progress of specific physical ailments over time. Cloud-based image compression APIs streamline this process with the ability to compress individual or multiple files, set desired quality, remove metadata, and set JPEG mode output.

Rapid File Conversion

Complexity remains a challenge for healthcare records management. As patients visit general practitioners (GPs) and specialists, data volumes rapidly increase, in turn making it difficult for doctors to find specific information and create comprehensive treatment plans.

Multi-file combination and conversion to popular formats such as PDF helps solve this problem — not only can healthcare staff create files that are easily viewed by doctors and patients alike but administrators can also set key permissions around editing, annotating, and printing to ensure information remains secure. File format conversion with PrizmDoc Cloud APIs can help enhance patient portals with key features including:

  • Easy combination of multiple files into single PDFs
  • Data security with optional password protection
  • Specific section or entire file conversion
  • Searchable output formats

Relevant Watermarking

Last on our list of patient portal APIs is watermarking. By labeling key documents with unique healthcare watermarks, organizations can both improve front-line security and enhance HIPAA compliance. By training staff to only accept and process watermarked images and documents, companies can reduce the risk of potential compromise. If attackers attempt to spoof or modify key documents they can be easily detected because they won’t carry corporate watermarks. These marks also form a key component of auditing and data tracking if healthcare agencies are evaluated for HIPAA compliance by providing a visible chain of custody around document creation, storage, and access. 

User-friendly patient portals are critical for healthcare companies to survive in the “new normal” — and embrace what comes next. But speedy access requires a robust security balance; document viewing, redaction, compression, conversion, and watermarking APIs from Accusoft can deliver privacy in practice and capitalize on patient portal potential.  Try PrizmDoc Cloud API.

View Detail >

InsurTech SDK

The insurance market is booming. As noted by research firm Deloitte, the property and casualty (P&C) sector saw a massive income uptick in 2018 and steady growth last year that’s predicted to carry forward through 2020. To help manage the influx of new clients and handle more claims, many firms are spending on insurance technology (insurtech) — digital services and solutions that make it possible to reduce error rates and enhance operational efficiency. InsurTech SDKs are important components of this transformation.

Both in-house insurtech solutions and third-party platforms often excel in specific areas but come up short in others, putting insurance firms at risk of writing off potential gains. While solution switching and ground-floor rebuilds offer one route to success, there’s another option that’s more custom to your business needs: software development kits (SDKs). Here’s a look at three top SDKs that offer customized functionality potential.

FormSuite for Structured Forms: Solving for Data Capture

Time is money. The faster insurance companies accurately complete and file documents, the greater their revenue potential. And as noted by KPMG, the need for speed is more pressing than ever. Many insurance sectors have seen substantial increases in both claims and new applications as the COVID-19 crisis evolves. 

As a result, accurate and agile forms processing is critical to keep up with demand. If current insurance software can’t quickly capture forms data, recognize standard form fields, and let users easily create standard form libraries, policy processing falls behind.

FormSuite for Structured Forms makes it easy for developers to build in form identification and data capture that includes comprehensive form field detection with OCR, ICR, and OMR functionality and the ability to automatically identify scanned forms and match them to existing templates.

ImageGear for .NET and C/C++: Simplifying Conversion

Conversion is critical for insurance firms. Depending on the type and complexity of insurance claims, companies are often dealing with everything from Word documents for initial client assessments and .GIF or .JPG images of existing damage to contractor-specific PDFs or spreadsheets that detail necessary materials, time, and labor costs. The result? A mash-up of multiple file types that forces adjusters to spend valuable time searching for specific data instead of helping clients get their claims process up and running. This makes it difficult to recognize value from emerging digital initiatives. 

Accusoft’s ImageGear for .NET and ImageGear for C/C++ empower developers to integrate enterprise-class file viewing, annotation, conversion, and image processing functions into existing applications, allowing staff to both quickly collaborate on key tasks and find essential data across a single, easy-to-search document.

 

ImageGear: Streamlining PDF Capabilities

While insurance technology offers substantive opportunities for end-users to capture, convert, and retain data, this technology can also come with the challenge of increased complexity. According to recent research from PWC, for example, firms looking to capitalize on insurtech potential must be prepared to rapidly develop new product offerings and embrace the expectations. 

As a result, companies need applications that streamline current functions and allow them to focus on creating cutting-edge solutions. For example, PDF is a file format that is still used by enterprises worldwide to maintain document format consistency and maximize security. When it comes to converting multiple files into a PDF, software can be expensive and introduce data security issues. 

This can all be solved with an SDK like ImageGear, which makes it possible to integrate the total PDF package into any document management application, both reducing overall complexity and freeing up time for staff to work on new insurance initiatives.

Insurtech forms the framework of functional futures in policy applications, claims processing, and compliance reporting, but existing software systems may not provide the complete capability set companies need to make the most of digital deployments. These top SDKs offer insurance IT teams the ability to integrate key services, improve speed, and boost security at scale. Learn more about Accusoft’s SDKs at www.accusoft.com/products. 

View Detail >
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.

View Detail >
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.

View Detail >
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.

View Detail >
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.

View Detail >