Where we came from

In July 2015, Accusoft’s SaaS Applications team was tasked with integrating the recently acquired edocr application with our existing Prizm Share community for publishing and sharing documents. While this integration offers numerous challenges with data migration, feature parity, and cohesive branding, we are going to focus on the architectural changes that resulted from the project.

Both projects were initially built as LAMP applications—edocr on Drupal 5 and Prizm Share being built in-house by a fledgling apps development team. Throughout their independent evolutions, they each had the expected increase in features and correlated increase in code base size and technical debt. The decision to merge the two products under a single brand and code base meant choosing a target platform.

Initially, we considered two options:

Migrate Prizm Share data to the existing edocr platform

With edocr being the dominant service for traffic between the two, it made more sense to merge on that base when looked at from a customer-centric perspective. However, edocr was running on a very dated Drupal 5 and in need of an approach that could be supported well into the future. Along these lines, we also considered adopting the Drupal platform and then going through the upgrade process from 5 to the current release, 8. Tests of these upgrades did not have good results, however, as numerous plugins and custom modules in edocr were not available or supported in the latest version.

Migrate edocr data to the existing Prizm Share platform 

With the edocr application being based on the very outdated Drupal 5 platform, the primary contender was to move the application to our existing PHP Prizm Share code base and extend the features that we didn’t currently support in order to serve the existing customers of both products. The problem with this was that the code for Prizm Share was already starting to show signs of rigidity based on a lack of foresight on the initial architecture decisions. New features were increasingly difficult to work in with the existing framework and the team had been looking to move to something more modular.

Our Decision

What the team eventually decided on, however, was a complete overhaul of the whole system, targeting the existing feature sets of both products along with a specific list of MVP requirements for our new consumer document platform.

To ensure flexibility in the future and to keep a positive connotation on the word legacy, we decided to adopt a microservice architecture built on a lightweight application framework we developed in Node. This would handle configuration and dependency management for each of our services. By separating out our functionality into independently managed components and updating our build and deployment system to deploy as docker containers, the team was able to reduce friction with code changes, improve code testability, and drastically reduce the time from commit to production.

Read on in the coming weeks for details on our migration, including failures, successes, and lessons learned.

The world of investment technology moves almost as quickly as the investment markets themselves. Without the right FinTech tools, today’s individual investors are likely to be left behind the latest financial trends. That’s why FinTech investment solutions are once again becoming a major point of emphasis for developers looking to expand access to key financial services.

The History and Impact of FinTech Investment Solutions

As a subset of the FinTech industry, “invest-tech” is sometimes used to refer to a wave of innovative investment management technologies that are helping to connect aspiring investors to the information and financial services they need to capitalize on new opportunities. Like many other FinTech applications, investment software tools have played a pivotal role in expanding access to financial markets and helping consumers take direct control of their investment decisions.

Much of the early FinTech investment market was driven by “robo-advisor” services that used sophisticated algorithms to provide customers with investment guidance. The boom reached its peak in the mid-2010s, with a record 81 new invest-tech solutions hitting the market in 2014. Since then, the number of launches has dwindled as established incumbents in the financial services sector moved in to acquire some of the most promising firms.

In many instances, those acquisitions were made to expand existing digital capabilities or to secure a new base of established investment customers. Since the typical FinTech investment user was younger and possessed fewer assets, the profit margins for many start-ups were simply too low and the costs of customer acquisition too high. This dynamic has gradually shifted the industry’s focus toward the B2B market, although crowdsourced investment platforms remain quite popular among many retail investors. 

The Current State of FinTech Investment Technology

FinTech investment platforms roared back into the public consciousness following the COVID-19 pandemic as the combination of work-from-home mandates and accumulated savings caused a rise in retail investment. Individual investors made up 19.5 percent of stock market activity in the first half of 2020, an increase of nearly five percent from the previous year. On a particularly busy day of trading, individual investors constitute a whopping 25 percent of market activity.

Thanks to mobile FinTech apps from startups and established players in the financial services industry, more people than ever before have access to investment opportunities, which has caused significant disruption to the market. The controversial rush on GameStop stock in early 2021, for instance, demonstrated just how much impact easy-to-access these platforms could have on investment trends.

This resurgence in retail investment could very well spark another wave of interest in FinTech investment apps, especially from established firms looking to expand their digital capabilities and capitalize on the growing market.

Enhancing the FinTech Investment Experience

For developers building the latest iterations of FinTech applications, there are a few key features worth focusing on to deliver a better investment experience. 

Sharing Data and Portfolios

While being able to access investment portfolio data on demand is valuable, customers are understandably concerned about the security of that data. Whether they’re building a retail investment app or a managed digital vault, developers need to provide a way of viewing private information securely. This is especially critical for digital documents. Relying on an external application for viewing or even just using the default browser viewer could potentially expose information to unauthorized users. By integrating secure, native viewing features, developers can ensure that investment portfolio data remains within a protected application environment.

Protecting Proprietary Research

One of the key benefits of working with an investment firm is having access to their market research when making financial decisions. In many cases, financial projections are calculated using proprietary formulas embedded within spreadsheets. Unfortunately, spreadsheets pose a number of security and compatibility problems. Even if a workbook is shared securely, there’s often little to stop someone from copying the proprietary formulas embedded within the cells and using it for other purposes. FinTech developers need ways to make those spreadsheets available without also compromising the valuable formulas developed over years of painstaking research.

Improving Data Capture

Making the right investment is all about having the right information. That data could come from a variety of sources, and in many instances it will need to be collected and analyzed before it can be of any use. Automating the data capture process can help to get that information into a customer’s hands faster. For example, customer information can be updated quickly by automatically extracting data from structured forms like tax filings. Scanned documents can also be converted into searchable PDFs using Optical Character Recognition (OCR), which makes it easier for AI-powered tools to sift through data in search of trends and potential opportunities.

Choosing the Right FinTech Investment Integrations

Building a successful FinTech application requires developers to build innovative tools that set them apart from the competition while also implementing everyday functionality that often lies outside their experience or expertise. Features like document viewing, annotation, and file conversion may be integral components of their platform, but take both time and development resources to build from scratch. By turning to SDKs and APIs, developers can quickly roll out new features without detracting from their primary software development goals.

Accusoft has been working with FinTech investment platforms for many years, helping developers to build powerful InsureTech applications without sacrificing the viewing and image processing technology that customers expect.

• PrizmDoc Viewer: Adds secure HTML5 viewing, annotation, conversion, and redaction capabilities to web-based applications, allowing developers to control every aspect of the viewing experience without compromising privacy.
• PrizmDoc Cells: Provides full XLSX support for applications, making it possible to securely upload and share Excel workbooks without exposing the source file or allowing users to access and copy proprietary formulas.
• FormSuite: A versatile forms SDK that allows developers to add form template identification and data extraction to their application, making it easier than ever to automate and streamline workflows.
• ImageGear: In addition to conversion and compression tools, it also provides full-page OCR for converting scanned documents into searchable text.

Learn more about how Accusoft is helping FinTech developers to drive the next generation of investment technology platforms.

ISVs, corporations, and SaaS solutions all have the same immediate digital transformation needs in common; they all need to bring forth technologies that improve both the customer and employee experience. The challenge is building and launching these technologies quickly, efficiently, and within a scalable, sustainable model. Product managers and development teams are all evaluating options to assist with meeting stakeholder demands for quality, while also meeting the need for speed to market. Enter the hidden value of third-party software integrations.

The secret life of APIs

Digital transformation is an ever-increasing priority for all businesses as well as an initiative that is seeing a surge in funding. In a recent State of the API Economy 2021 report by Google, 56% of enterprise leaders say APIs help them to build better digital experiences and products. Leaders are also finding value in focusing on an API-driven strategy, and 52% say APIs accelerate innovation by enabling partners to leverage digital assets at scale. 

How API Integration Works

At a very simple level, an API consists of code that allows two separate technology systems to communicate and interact with one another. It functions as a translator and messenger; delivering user requests and data from one system to a completely separate system. This effectively allows an application to utilize the features and data of other applications without having to build out that functionality from scratch.

For example, the Uber ride-sharing app connects customers to available drivers within a specific area. It does this with a combination of smartphone geolocation and accurate maps, but the Uber app doesn’t have mapping capabilities. To get those features, it connects to Google Maps by way of an API that allows the Uber app to access the relevant navigational data and use it to connect customers to drivers.

Another key function of APIs is their ability to automate key processes and connect legacy infrastructure to newer technology systems. Data can be collected in one system, for instance, and “pushed” into another system automatically. This not only eliminates the complicated (and error-prone) task of manually transferring data between different systems, but also allows users to build a workflow in an application they’re already accustomed to, without having to learn an entirely new system. 

More importantly, since APIs allow newer technologies, devices, and legacy applications to talk to each other, they provide firms with substantial flexibility when it comes to adding new platforms. Purchasing new software doesn’t mean throwing out existing tools, which significantly reduces the risks associated with technology investments and upgrades.

The cost savings with API Integrations

When you purchase a third-party API integration you’re gaining more than additional functionality for your application. You also gain access to a team of developers and support specialists who are here to assist you from POC to deployment and beyond.  Leaning on the specialization of a third-party vendor allows your developers to focus on application enhancements and release your product to market faster. Ultimately saving your company valuable development time and realizing product revenue faster.

Interested in learning more?

Could your business benefit from an API led digital transformation strategy? Schedule a consultation today, to learn more about the document management API integration options available from Accusoft.

The healthcare industry has undergone a profound change in the 21st century. A combination of technological advancements and regulatory pressures has encouraged providers to adopt new software platforms and update their existing IT stack. Gone are the days of physical file archives and cramped server rooms; today’s healthcare organizations are instead embracing innovative Internet of Things (IoT) devices, cloud-based file systems, and colocated server deployments that enhance their service capabilities and efficiency.

Unfortunately, not every provider is implementing new technology at the same pace. As science fiction author William Gibson famously observed, “The future is already here. It’s just not evenly distributed yet.” Today’s healthcare organizations must navigate a complex landscape of software solutions and overcome compatibility challenges in order to provide better service and care patients deserve.

The Drive for Interoperability

One of the key components of the 2010 Affordable Care Act was the push to promote interoperability among healthcare providers. The logic was fairly simple: for a healthcare marketplace to work effectively, patient information needs to be able to move freely between providers. That meant the myriad healthcare technology platforms being adopted by different organizations needed to be able to communicate with one another and share a common set of file formats.

The combined pressures of digital transformation and interoperability have led most hospitals and specialized health providers to implement picture archiving and communication systems (PACS). These digital archives and file management platforms allow providers to easily, store, retrieve, distribute, and present a variety of medical images, such as CT, MRI, and DR scans. They have largely replaced the expensive and complex manual filing systems used to store physical film and provided a far more secure means of protecting patient data.

Healthcare Image Processing

One of the advantages of shifting to digital scan formats is the ability to compress images while maintaining the ability to decompress them back to their original images. Poorly optimized compression tools can deteriorate the integrity of a high-resolution image, potentially obscuring key diagnostic indicators. In order to overcome these challenges, healthcare systems need image processing features capable of supporting rapid data compression, lossless transmission, and image cleanup.

Software developers working on PACS platforms and medical applications can turn to image processing SDKs like PICTools Medical to incorporate extensive compression and decompression capabilities into their solutions. These SDK tools can help overcome a variety of diagnostic imaging challenges, ensuring that complex medical files can be processed without any degradation of quality for easy viewing and management across multiple PACS platforms.

The Role of EHR Systems

Part of the push for interoperability included the adoption of electronic health records (EHR) systems, which digitized patient files to make them easier to share between healthcare providers. One of the challenges that came along with this adoption, however, was the handling of high-resolution medical images. While most healthcare providers have implemented some form of an EHR system, many of them do not have a PACS solution, especially if they don’t do any kind of medical scanning on-site. That means their ability to view certain types of medical images is quite limited. 

In theory, the medical industry has already solved this challenge with the development of the DICOM standard. Short for “digital imaging and communications in medicine,” DICOM was originally developed in a joint venture between the American College of Radiology (ACR) and National Electrical Manufacturers Association (NEMA) to ensure that healthcare providers would be able to view medical images no matter which vendor’s modality originally created them.

Unfortunately, the size and complexity of DICOM files often make them difficult for providers to manage. For instance, most EHR systems can transmit DICOM files (through a DICOM out or DICOM send functionality), but they often cannot view or annotate them. That’s because Windows doesn’t recognize DICOM files as image files. More importantly, large DICOM files often exceed the digital transfer limits of common communication channels like email. That leads to DICOM images being transferred on physical mediums, like discs or flash drives, that include viewer software.

Unlocking the Potential of DICOM 

Healthcare technology developers can help expand EHR functionality and realize the potential of DICOM by building viewing, conversion, and compression capabilities into their applications. Medical imaging SDKs like ImageGear Medical can not only convert DICOM files into a variety of easily viewable formats, but also perform essential cleanup functions to ensure that images maintain the highest integrity possible. High-level APIs can abstract or redact the details of a DICOM file to ensure the anonymity of the patent data as well as to compress it without degrading the image, making it easy to transfer files over secure channels rather than resorting to physical mediums or non-compliant public cloud platforms.

The ability to convert DICOM files into more easily managed formats also helps providers to share more information with patients. Diagnostic scans, for instance, can be quickly opened on IoT devices like a tablet and viewed entirely within the local application without having to use special equipment. Images can even be transferred directly to patients, allowing them to conveniently view them on their own devices. And thanks to lossless compression, medical offices can transmit the source DICOM files to other organizations when referring a patient to an outside provider.

Accusoft Medical Imaging Toolkits

With more than two decades of experience working with the imaging needs of the healthcare industry, Accusoft offers a variety of medical imaging toolkits to help software developers enhance their healthcare applications. Whether you’re developing a standalone imaging solution or adding viewing, compression, and cleanup features to your EHR system, our collection of SDKs and APIs can provide core medical image functionality so you can focus on building a better user experience and get to market faster. Learn more about how our medical imaging toolkits are improving outcomes in the healthcare industry and accelerating digital transformation trends.

Barcodes continue to be an essential tool for today’s organizations, whether they’re using them for managing supply chains or sorting documents within a complex digital workflow. Since the early 1990s, however, the potential use cases of barcodes have expanded tremendously. That’s largely due to the invention of the quick response barcode, better known as the QR Code. Developed by the Japanese manufacturer Denso Wave in 1994, this two-dimensional barcode revolutionized the way data was encoded and scanned. Today, QR Codes can be found practically everywhere, along with their smaller cousins, the Micro QR Code.

What Is a Micro QR Code?

Although the standard QR Code could hold a tremendous amount of information, that ability occasionally created challenges for specialized use cases where space was at a premium. Small components like circuit boards or machinery parts, for example, often couldn’t accommodate a QR Code. Even when they could, much of the QR Code’s storage capacity wasn’t being used to its full potential. For use cases where space was at a premium and only a small amount of data needed to be encoded, a more compact version of the QR Code was needed.

The Micro QR Code was designed to solve this specific challenge. Roughly half the size of the conventional QR Code, this smaller version still provided many of the benefits of its bigger cousin, including finder patterns to orient the image properly, multiple levels of error correction, and support for Japanese Kanji, Kana, and Hiragana characters.

The Anatomy of a Micro QR Code

A Micro QR Code consists of four elements that allow it to encode data and provide a barcode reader with instructions for how to read the contents.

Data Modules

Like any other QR Code, Micro QR Codes store binary data in square modules. While the human eye only registers the black modules, a computer scanner also registers white modules when reading the code. A black square represents a binary 1 while white squares are read as a binary 0. The amount of information that can be encoded into these modules changes depending upon the size of the barcode. Micro QR Codes can be written in four different sizes (more on that in a moment), allowing them to store up to 35 numeric digits, 21 alphanumeric characters, or 128 data bits.

Finder Pattern

The finder pattern is the square “bull’s eye” that appears in the upper-left hand corner of a Micro QR Code. This pattern ensures that the barcode is oriented and scanned correctly when read by an application. Since Micro QR Codes contain less complex data, they only require a single pattern finder while a conventional QR Code uses three. While many QR Codes also require an alignment pattern to correct for crookedness or distortion, Micro QR Codes are not large enough for these problems to create much of an issue during scanning.

Timing Pattern

A series of alternating black and white modules running vertically along the left side and horizontally along top of the barcode, the timing pattern is used to configure the rest of the data grid for the scanner. By reading the timing pattern, the scanner software can quickly determine the size of the barcode’s data matrix, as well as the symbol and version density.

Quiet Zone

A clear margin space surrounding the rest of the barcode elements, the quiet zone makes the boundaries easy for scanning software to detect and identify. While a conventional QR Code requires four or more modules of empty space, a Micro QR Code only needs a two module-wide space. This helps to keep the barcode compact regardless of how much data is encoded within it.

Micro QR Code Sizes and Error Correction

Depending upon the amount of data encoded, Micro QR Codes can be written in one of four sizes. The smallest version, M1, consists of 11×11 modules, while the largest, M4, is 17×17 modules. Each size above M1 can support different levels of error correction, although the more thorough the error correction, the less data can be encoded.

Error correction is based on the Reed-Solomon algorithm and allows scanning software to recover lost, poorly printed, or damaged barcode data. Versions M2 and M3 offer two levels of error correction:

• Level L (Low): Capable of recovering up to seven percent of encoded data.
• Level M (Medium): Capable of recovering up to 15 percent of encoded data.

As mentioned above, higher levels of error correction impact the amount of data that can be encoded into Micro QR Code modules. That’s because the redundancies necessary to support error correction algorithms take up available space. Increasing an M3 barcode’s error correction from level L to Level M, for instance, would reduce the number of numeric characters that could be supported from 23 to 18.

An M4 Micro QR Code contains enough modules to support a third level of error correction:

• Level Q (Quartile): Capable of recovering up to 25 percent of encoded data.

Although level Q provides excellent durability, it leaves much less space for encoding data. An M4 barcode with this level of error correction actually holds less data than an M3 barcode with level L error correction. When writing a Micro QR Code, it’s important to determine what level of error correction is actually necessary for the use case at hand rather than simply defaulting to the most robust option.

Differences Between Micro QR Codes and Conventional QR Codes

While Micro QR Codes use many of the same 2d barcode principles as traditional QR Codes, it’s not quite accurate to think of them as a condensed version. They have some notable differences that make them more or less suited to specific use cases.

Micro QR Codes

• Provide up to three levels of error correction.
• Needs only a single finder pattern for orientation.
• Can encode up to 128 bits.

Conventional QR Codes

• Provide up to four levels of error correction.
• Requires three finder patterns for orientation.
• Can encode up to 23,658 bits.

Enhance Your Barcode Capabilities with Barcode Xpress

Adding barcode recognition capabilities to an application can help to streamline document management workflows and allow organizations to route files more efficiently. Developers can easily integrate the ability to read and write barcodes into their platforms using a barcode SDK like Accusoft’s Barcode Xpress. With support for more than 30 unique barcode types, including Micro QR Barcodes, this versatile SDK provides the tools to support a wide range of use cases that call for fast, accurate barcode recognition.

For a hands-on evaluation of how Barcode Xpress will perform in your development environment, download a free trial today or start a conversation with one of our SDK specialists.

Printers, scanners, and other imaging devices have long been a source of headaches and frustration for developers and users alike. All too often, multiple software tools are required to connect an application to a device and acquire image files from them. This not only slows down workflows, but also creates opportunities for human error. Files can easily be misplaced or imported using the wrong parameters under these conditions.

Thanks to ImageGear’s TWAIN scanning support, however, developers can ensure that their application makes acquiring images from compatible devices both straightforward and mistake free. 

What Is TWAIN?

Developed in 1992 by a consortium of software developers and hardware manufacturers, the TWAIN standard is a standard software protocol and API that facilitates communication between imaging devices and software applications running on a computer. The word itself refers to a famous line in the Rudyard Kipling poem “The Ballad of East and West” that reads “never the twain shall meet.” Although sometimes alleged to stand for “Technology Without An Interesting Name,” the term is not actually an acronym despite being capitalized.

The name is well chosen because the TWAIN standard helped to solve the enduring problem of getting imaging devices and computers to connect and send data between one another. Most commonly used for scanners and digital cameras, TWAIN made it possible to request an image file to be imported into an application without having to utilize additional software or input commands using the physical device.

Implementing TWAIN Scanning with ImageGear

As a versatile image processing SDK, ImageGear fully supports the TWAIN specification, which allows developers to support any TWAIN-capable device directly into their applications. In most instances, this will involve adding a “Scan” button or option somewhere in the platform’s interface so that users can quickly and easily instruct their scanner to capture an image and pass it along to the application’s storage or workflow. Developers can also use the integration to adjust device settings directly from their application, such as changing the scanning area, modifying brightness and contrast, or increasing/decreasing dots-per-inch (resolution). 

ImageGear’s TWAIN scanning feature works with three external elements to facilitate image file transfers:

• The Device: Usually a scanner or digital camera, this is the primary imaging source. The device must be compliant with TWAIN protocol.This is typically indicated by the manufacturer.
• Data Source: Although ImageGear’s TWAIN scanning features can connect an application to a scanner, the device still needs a software driver that allows it to communicate with the computer’s operating system.
• Data Source Manager: The TWAIN manager software provides a universal mechanism for managing and using data sources from different device manufacturers. Developed by the TWAIN consortium, it can be downloaded for free and installed wherever the application is running.

(Both the device’s data source driver and TWAIN data source manager should be included with its installation software. They are not provided by the ImageGear SDK).

Acquiring an Image Using TWAIN Scanning

ImageGear can configure an application to gather an image or set of images from a connected device with a few simple steps.

Step 1: Open the Data Source

Developers can set the application to automatically open a default Data Source. This is typically the best choice when only one scanner is available, as is often the case in a small workplace. They can also use the Data Source Manager to provide a list of all available Data Sources and let the user select the one they need.

Step 2: Adjust Settings

ImageGear’s TWAIN scanning features allow image acquisition parameters to be set through the application. Parameters such as page count and image size can be set to a common default, but developers can also give the option to obtain the various capabilities (listed as “ScanCaps”) and display them for users to select from. ImageGear supports a wide range of TWAIN-related capabilities.

Step 3: Acquire Image

After all settings are configured, the image can be scanned and loaded into an ImGearPage Class object. When acquiring a multi-page image, ImGearPages are loaded into an ImGearDocument Class object instead.

How ImageGear TWAIN Scanning Looks in Code

As an example, here’s what the C# code may look like when using ImageGear to help an application import an image from a TWAIN Data Source:

using System;
using ImageGear.Core;
using ImageGear.TWAIN;

public ImGearPage AcquireImage(IntPtr Handle)
{
    ImGearPage igPage = null;
    ImGearTWAIN igTWAIN = new ImGearTWAIN();

    igTWAIN.WindowHandle = Handle;
    igTWAIN.UseUI = true;

    try
    {
        // Open the data source selection dialog
        igTWAIN.OpenSource(String.Empty);

        // Initialize the scanning
        igPage = igTWAIN.AcquireToPage();
    } 

    catch(ImGearException e)
    {
        // Handle the exception ...
    }

    finally
    {
        if(igTWAIN.DataSourceManagerOpen == true)
        {
            igTWAIN.CloseSource();
        }
    }

    return igPage;
}

Expand Your Application’s TWAIN Support with ImageGear

Accusoft’s ImageGear SDK provides comprehensive support for a broad range of TWAIN devices, which makes it easier than ever for developers to control the scanning process directly from their applications. Integrating TWAIN scanning can streamline workflows and significantly improve the software user experience by completely eliminating the need to turn to external programs for image acquisition. ImageGear is fully compatible with multiple generations of the TWAIN standard, including TWAIN v1.6, v1.7, v1.8, v1.9, and v2.4.

In addition to TWAIN scanning support, ImageGear provides powerful image and document processing capabilities that can transform your application workflows. With extensive file conversion and compression features, it’s the best way to quickly integrate content management features into your platform. To get a glimpse of what ImageGear can do for your .NET application, download a free trial today and start building.