Technical FAQs

Question

With a fully-running PrizmDoc environment (version prior to v10.5), I’m noticing times where the system becomes unresponsive. That is, at some point, it no longer processes requests being made to the backend and I have to restart PrizmDoc in order to alleviate it. What could be causing this?

Answer

Prior to version 10.5, PrizmDoc used ProxyServer as its image processing system. Our Development Team eventually began seeing that the ProxyServer exhibited architectural problems that lead to a multitude of issues, such as unresponsiveness.

Starting in version 10.5, the Development Team created the Prizm Content Connect Imaging Service (PCCIS), which is far more stable.

To resolve this issue we suggest upgrading to the latest revision of PrizmDoc. Please see the product page for more information found here: https://www.accusoft.com/products/prizmdoc/overview/

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

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.

developers sitting at computer

Docubee is a great no-code platform for automating your business processes. If you are a developer, we offer several ways to integrate Docubee directly into your site with straightforward APIs, and a few lines of code. If that isn’t your speed, no worries! You can learn more about how you can use Docubee code free here. Otherwise, read on!

You’ve got your perfect website and your customers know and love your unique style. With Docubee, it’s easy to use your own forms to collect data and much more. With additional effort, you could even send documents hosted on your site to Docubee and auto-populate them with data collected in a form.

To demonstrate a very simple use-case, here is a survey form in Docubee which can be used to collect and track response data. The Docubee workflow will be a very simple two step process – a web form and email step. Check out how to create a workflow template here.

 


The Docubee Workflow

Using Docubee’s fast form creator, it was easy to create a simple survey form.

Once created and published, the workflow’s form can be directly linked via URL for collecting survey data, or it can be submitted from your own site by initiating a POST request. This way you don’t need to worry about storing the data. Docubee allows you to track and export all responses.

Each field in the workflow designer has a Field Label and Property Name. The label is what shows up on the Docubee web form, and the Property Name is what the response data corresponds with in the Docubee dashboard.

So far, there are six “Single-Line Text” fields on the form, five of which have a data type of text and one of type e-mail.

(Label / Property Name)

  • What is your favorite product? / Favorite_Product
  • Why did your purchase this product? / Why_Purchase_Product
  • How satisfied are you with this product? / Product_Satisfaction
  • Would you recommend this product to a friend? / Recommend_Product
  • Would you recommend this company to a friend? / Recommend_Company
  • Your Email / Respondent_Email

The property name is also how the data is stored in the POST request body to Docubee that initiates the workflow.


The Docubee API

The workflow can be initiated from your site by having your form post to custom route on your server. The handler behind that route needs to format your forms response data to POST to the workflow instances API endpoint:

POST - https://docubee.app/api/v1/workflowInstances
Content-Type: application/json
Request Body
{
  "wfModelId": "yourModelIdHere",
  "wfData": {
    "Favorite_Product": "yourDataHere",
    "Why_Purchase_Product": "yourDataHere",
    "Product_Satisfaction": "yourDataHere",
    "Recommend_Product": "yourDataHere",
    "Recommend_Company": "yourDataHere",
    "Respondent_Email": "yourDataHere"
  }
}
Response
Content-Type: application/json
{
  "wfInstanceId": "instance-id",
  "redirectUrl": "url-if-there-is-a-next-workflow-step"
}

After a successful POST request, the workflow will be initiated with the data and a thank you email would be automatically sent to the email contained in the “Respondent_Email” property.

The survey responses can be tracked in the Docubee Dashboard under the “COMPLETED” instances tab.

All survey results can also be exported to a CSV file using the “Export Workflows” button.

 

 

Example CSV Export:

Docubee can be used for a wide variety of different use cases, from something as simple as collecting survey data, to more advanced use-cases requiring documents hosted on your site to be automatically populated with data.

Reach out today to schedule a demo, or to get started integrating Docubee’s other powerful APIs into your product. For more advanced use-cases our Professional Services team would be more than happy to assist.

Check out more here.

Landon Lamb

Landon Lamb, Software Engineer III – Docubee Team

Landon started out as a Software Engineer in Support at Accusoft in July 2016. In April of 2017, he transitioned onto the Docubee team initially as a Workflow Developer.

Currently, Landon is a Software Engineer III and works on the front end site, the back end services, and the product’s build pipeline. He enjoys helping deliver new features to Docubee’s growing user base.

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.

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.

Question

What are the best quality images to use when processing form data and recognition?

Answer

In all cases, you’ll 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 will allow 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 was reading it, you’ll want the text objects on the image to be as legible as possible. For ICR, make sure 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. You’ll also want to make sure that the bars in the barcodes are clearly defined on the image and are not mal-formed (for example, the barcodes should have the proper start and stop sequence, etc). As always, 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. Make sure that your resolution is consistent between your form templates and incoming batch images as well. 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.

Organized each year by ALM, LegalTech is one of the most important events for the legal industry. The conference brings together a broad variety of experienced legal professionals and innovative LegalTech providers to highlight the business, regulatory, technology, and talent trends in the market. In previous years, LegalTech was held in New York City and attended by more than 8000 people.

LegalTech 2021 Is Now Legalweek(year)

This year, however, the COVID-19 pandemic has forced the organizers to take a different approach. The first decision involved shifting LegalTech from an in-person conference to a fully virtual event in order to protect the health of both attendees and organizers. While many industry events have made a similar transition, the LegalTech team went a step further by breaking the conference into a series of five interactive virtual events held over the course of 2021. This new virtual series was dubbed Legalweek(year) and aims to provide legal professionals with a powerful resource for working through an unprecedented era.

“This decision was made to address the needs of our legal community during these trying times of COVID-19 and to provide the type of innovative education, solutions, and connections that is so crucial to legal leaders,” said ALM’s Mark Fried. “The 2021 series will set the stage for a resurgence in the legal sector and a big ‘Welcome Back’ to attendees for our in-person Legalweek event (in 2022).”

The first virtual Legalweek(year) event is scheduled for February 2-4, 2021 and will feature bestselling author and political leader Stacey Abrams, legal AI expert Josua Walker, and former New Jersey governor and federal prosecutor Chris Christie as keynote speakers. Attendees will not only be able to participate remotely, but they will also have an additional six months worth of on-demand access to virtual content following each event.

Visit the Accusoft Legalweek(year) Virtual Booth

As a longtime sponsor of LegalTech, Accusoft is proud to participate in this groundbreaking series of virtual events. The conference has historically been a great opportunity for us to speak directly with the independent software vendors and legal IT professionals about the latest industry trends and LegalTech applications. 

This year, we’ll be hosting a “virtual booth” through the Legalweek(year) event site. Whether you’re a developer looking to solve a particular software challenge or a project manager building an in-house solution for your firm, you’ll find plenty of resources and support at the Accusoft booth. Read through our numerous case studies and LegalTech whitepapers or schedule a meeting with one of our product specialists to learn more about our SDK and API integrations for legal software. You can even chat with someone in real time if you need a quick answer!

After completing registration, Legalweek(year) attendees can access the Accusoft virtual booth during the event simply by logging into their account.

Visit the Accusoft Virtual Booth

Our LegalTech Solutions

Accusoft’s combination of content processing and conversion integrations help today’s innovative LegalTech applications reach their full potential. As law firms and legal departments incorporate more technology into their everyday operations, they need software tools capable of automating workflows, simplifying eDiscovery, and facilitating secure collaboration.

PrizmDoc Viewer

Our feature-rich HTML5 document viewer allows users to seamlessly view a variety of document and image files within their secure web application. Thanks to PrizmDoc Viewer’s powerful REST APIs, developers can provide additional functionality, such as annotations and redactions, that is essential for legal organizations.

PrizmDoc Editor

In addition to allowing users to edit DOCX files within the secure confines of their LegalTech applications, PrizmDoc Editor’s automated document assembly features streamlines the contract creation process to improve efficiency and accuracy. Documents can be assembled programmatically, incorporating commonly used or specific clauses, special language, and client data to eliminate “cut and paste” errors. Once documents are assembled, PrizmDoc Editor’s sharing tools allow firms to control access and ensure that everyone is working from the same up-to-date version.

ImageGear

With the ability to read, convert, and compress a wide range of files, our ImageGear SDK integration provides LegalTech applications with the tools they need to manage almost any type of file collected during the eDiscovery process. Powerful optical character recognition (OCR) capabilities allow ImageGear to read a wide variety of languages from around the world and convert scanned documents into searchable plain text or PDF files.

LegalTech in 2021 and Beyond

As legal organizations continue to make strides toward achieving true digital transformation, they will need versatile LegalTech applications capable of adapting along with them. Accusoft’s family of SDK and API integrations can help developers leverage the power of their innovative software tools and free up resources to focus on improving their core capabilities.

We hope you’ll join us at Legalweek(year) on February 2-4, 2021. Our booth will be available throughout the virtual event, so stop by to find out how Accusoft can help you realize the potential of your LegalTech applications.

barcode xpress pricing

 

When you’re looking to integrate a toolkit into your application, your first priority is assessing the capabilities. Once you’ve found the right fit, you need to make sure that the pricing matches your budget and makes sense for your needs.

Historically, Accusoft has offered a variety of different licensing options for our clients. Products were always licensed by core or number of installs, depending on which runtime fits best. 

These practices have been great for our clients so far, but we realized a missing piece that could help bridge the gap for new clients with smaller projects that dynamically scale based on workload.


Introducing a New Way to License

Barcode Xpress is the first product on the Accusoft line to offer metered licensing based on transaction. Metered licensing helps a variety of different clients scale up or down, when they need to. While our traditional licensing plan is great for projects with defined scope, smaller projects that have potential to grow need more flexible pricing options.

“The main reason we wanted to introduce metered licensing is to address SDKs used in scalable environments,” says Mark Hansen, Product Manager of SDKs. “Clients can use metered licensing to spin up their projects based on the traffic they’re getting, without the need to obtain additional licenses. While many companies opt for an ongoing usage, this new model allows for estimating a specific amount of use, so they only pay for what they need.”


The Benefit of Metered Licensing

Why would a company choose to specify the usage from the start? Metered licensing is great for short-term projects with a limited lifespan, as clients only pay for what they use. It’s also great for clients who don’t know the scale of their project and need to be cautious with how much they spend. 

Metered licensing is based on a pay-per-transaction model. A transaction is defined by the page. For example, if Barcode Xpress reads 30 pages with five barcodes on each page, the transaction total is 30 instead of 150.

This transaction-based model makes for a very low cost of entry, and a no-stress agreement. With this value in mind, clients don’t have to worry about how much they will use the integration after a specific project is complete. In addition, if the project grows, metered licensing allows the client to scale up.


Reliability of Metered Licensing

Accusoft understands that our customers are building mission-critical apps with our SDKs and has carefully architected the system to be extremely reliable. Our server-side authorization and reporting system runs in Amazon AWS and is split into online and offline parts. 

The online portion is built on AWS CloudFront and S3, two of the most reliable systems available on the Internet. All of Accusoft’s backend code is in the offline portion of the system and an outage in that portion of the system will have no effect whatsoever on our customers, even if it were down for several days. Nevertheless, we have 24/7 alerting in place so we will be notified soon after an outage occurs and will quickly get it back up.

barcode xpress pricing

Metered licensing is now available for Barcode Xpress 13.1 and following versions.