Technical FAQs

Question

If I upload an HTML document to PrizmDoc that has image tags in it, will those images be rendered in the Viewer or will only the text be displayed?

What if the image tags are referencing local images?

Answer

When loading an HTML file, PrizmDoc will render image tags that are sourced from publicly accessible URLs. The relative links may not render though, as it’s likely that the source will not be found.

In PrizmDoc 13.2, a server-side configuration option called:

security.htmlRendering.blockExternalContent

was introduced to control whether or not externally-referenced HTML content will be blocked.

See the release notes for more information.

Question

If I upload an HTML document to PrizmDoc that has image tags in it, will those images be rendered in the Viewer or will only the text be displayed?

What if the image tags are referencing local images?

Answer

When loading an HTML file, PrizmDoc will render image tags that are sourced from publicly accessible URLs. The relative links may not render though, as it’s likely that the source will not be found.

In PrizmDoc 13.2, a server-side configuration option called:

security.htmlRendering.blockExternalContent

was introduced to control whether or not externally-referenced HTML content will be blocked.

See the release notes for more information.

Question

If I have a PDF document that only has an embedded image in it (no text objects, etc.), can PrizmDoc Viewer take it and create a searchable PDF file from it?

Answer

Yes. PrizmDoc’s Content Conversion Services can take an image-only PDF and create a searchable PDF file from it. This can be done by modifying the input.dest.pdfOptions.ocr options object; see our documentation here.

If you are attempting to make a searchable PDF from an existing PDF document, please note that the source PDF file should be an image-only PDF. PrizmDoc will not create a searchable file from already-existing vector content.

This feature was introduced in PrizmDoc 13.1, please see our Release Notes for more information.

Tampa Bay Software CEOs Call

TAMPA, Fla. September 9, 2020 – In August, Tampa Bay Tech’s Software CEO Council (TBSC) met to tackle what so many CEOs and founders are experiencing right now as the country continues to reopen. The outlook was optimistic amongst the group as all attendees reported that their businesses were maintaining financial stability and growing headcount.

During this quarterly meeting, TBSC usually gathers to discuss business ideas, philanthropic efforts, and community involvement. This meeting was a little different considering the effects that COVID-19 has had on the market.

“It’s important for TBSC to keep our meetings going, especially during a pandemic,” states Seng Sun, CEO of SunView Software. “We can rely on each other to share feedback and ideas regarding the management of new COVID-19 protocols.”

Prior to the meeting, the members participated in a brief survey about the impact that the pandemic had on their businesses.

“Across the board our CEOs reported challenges in the past several months, but I was encouraged by the optimism for not only ending the year in a positive place, but heading into 2021 with solid strategies to grow,” reported Jill St Thomas, Tampa Bay Tech’s Executive Director. “The commitment of these leaders to support one another absolutely embodies our mission of building a radically connected tech community in Tampa Bay.”

“We need to understand the way the pandemic has influenced not only our own business plans and strategies, but how it will affect the technology landscape in Tampa Bay,” states Jack Berlin, CEO of Accusoft. “We have light-hearted meetings, but we do discuss serious subjects. I took over a page of notes on ideas my peers shared, and I’m interested in implementing them across my teams.”

Members of the group in attendance included: Jack Berlin, CEO of Accusoft, Kevin Coppins, CEO of Spirion, Seng Sun, CEO of SunView Software, Ed Holmes, CEO of FairWarning, Gregory Ross-Munro, CEO of Sourcetoad, Paul Toomey, CEO of Geographic Solutions, Chris Karlo, CEO of Mercury New Media, Jody Haneke, CEO of Haneke Designs, and moderator, Jill St. Thomas, Executive Director of Tampa Bay Tech.

For more information about TBSC, visit the group’s website at https://www.tampasoftwareceos.com/.

About Tampa Bay Tech

Tampa Bay Tech is a 501(c)6 non-profit technology council that has been engaging and uniting the local technology community for 20 years. With over 100 companies representing thousands of tech employees – as well as thousands of students within the area’s colleges and universities – Tampa Bay Tech provides programming and initiatives to support all those in the technology space. Through their membership and partnerships, their mission is to build a radically connected, flourishing tech hub where opportunity is abundant for all. Join the TBTech community at tampabay.tech and follow us on Facebook, Linkedin, Instagram and Twitter.

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.

January 17, 2024 – Tampa, FL – Accusoft, a software company specializing in industry-leading secure document viewing, processing, and automation technologies for integration into Enterprise Content Management solutions, announced the latest release of PrizmDoc today. The latest version now includes AI for Personally Identifiable Information Detection and Redaction.

“Enhanced data security and improved regulatory compliance are very important to our customers, particularly in the Legal, Insurance, and Financial Services industries,” said Steve Wilson, Accusoft’s Chief Product Officer. “This newest version of PrizmDoc makes meeting these requirements easier.”

AI for Personally Identifiable Information in PrizmDoc: Features and Benefits

The new PrizmDoc AI for Personally Identifiable Information (PII) Detection and Redaction module allows end users to search and detect PII in a document. This provides:

  • The page number where the information is located
  • The ability to see the specific related text
  • What type of PII the AI has identified
  • An identification confidence score for each item

Once reviewed, end users can easily redact the information with a click of a button, or this process can be automated by using APIs.

Software developers can access this functionality using APIs to create workflow automation and enable user interface tools to provide functionality to end users.

PrizmDoc’s newest feature removes the need for end users to manually scan documents trying to identify PII for redaction, reducing bottlenecks and delays, and saving companies a significant amount of time.

Accusoft’s Chief Operating Officer Megan Brooks added: “This release marks a distinct milestone for Accusoft and PrizmDoc. Enhancing PrizmDoc with AI gives our customers a unique capability that allows them to differentiate their ECM solutions from the competition. As we stay close to our partners, the market, and the evolution of AI as it impacts the Document Management industry, we look forward to delivering more innovative feature enhancements to our customers.”

Learn more about PrizmDoc or to schedule a demo of the new PII features

About Accusoft

Founded in 1991, Accusoft is a software development company specializing in document processing, conversion, and automation solutions. From out-of-the-box and configurable applications to APIs built for developers, Accusoft software enables users to solve the 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 Docubee and PrizmDoc 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 releases, and a passion for understanding industry trends that drive consumer demand. Visit us at www.accusoft.com

###

document redaction

Many professionals in highly regulated industries like legal, healthcare, and government handle a myriad of cases, contracts, and forms. However, collaborating on documents comes with a risk. Sharing personally identifiable information (PII) with the wrong person can cause chaos and even result in a lawsuit. That’s why redaction is so paramount to collaboration in so many industries. Where manual paper processes once required a permanent marker, digital solutions now offer redaction capabilities that work even better. 

Redaction removes key pieces of information — including sentences, images, and even entire pages — while leaving the bulk of the document’s text intact. Although many tools now empower organizations to “burn in” data redaction so it can’t be removed, they don’t allow users to indicate multiple reasons for redaction. 

Many solutions offer a coding system that enables users to tag a piece of redacted information with a single reason code that signifies why the data was hidden. However, they lack the ability to add those reasons while you are redacting, which could save time and effort. Just think of how large some of these files could be, and how manually adding comments throughout the document could take hours after you’ve already finished reviewing the content.

This creates additional pressure from viewers to understand the purpose of redaction, and potential reporting issues if the reason for redaction isn’t properly recorded. Solutions that permit the addition of redaction reasons can help defend key data and close this communications gap.


The Freedom of Information Act (FOIA) and Secure Data Sharing

As noted by CNN, government documents are often partially redacted to obscure personal data such as social security numbers or military information related to intelligence data gathering and applications. Consider a U.S. intelligence agency report made public by FOIA request. 

While the Freedom of Information Act forms a critical part of open, effective democracy, data in the report that suddenly becomes public domain — such as the names of confidential sources or the methods used to obtain information about foreign government actions — could jeopardize both the ability of the agency to do its job and put human lives at risk.

Most government redactions expire and are automatically declassified after 50 years, but agencies can also obtain permission for special exemptions which prevent the redaction from being removed. For example, redaction reason 3.3(h)(1)(a) is used to protect the identity of a classified human intelligence source and is exempt from automatic expiration.

There are currently nine FOIA exemptions that are withheld from public release and protected from disclosure. When a portion of a record is withheld from public release, an exemption code may be found listed in the margin. The Federal Bureau of Investigation’s list below showcases what exemption codes are subject to FOIA data withholding:

  • (b)(1) (A) Specifically authorized under criteria by an executive order to be kept secret in the interest of national defense or foreign policy and (B) are in fact properly classified to such Executive Order #12958 (3/25/03).
  • (b)(2) Related solely to the internal personnel rules and practices of an agency.
  • (b)(3) Specifically exempted from disclosure by statute (other than section 552b of this title), provided that such statute (A) requires that the matters be withheld from the public in such a manner as to leave no discretion on issue or (B) establishes particular criteria for withholding or refers to particular types of matters to be withheld.
  • (b)(4) Trade secrets and commercial or financial information obtained from a person and privileged or confidential.
  • (b)(5) Inter-agency or intra-agency memorandums or letters that would not be available by law to a party other than an agency in litigation with the agency.
  • (b)(6) Personnel and medical files and similar files, the disclosure of which would constitute a clearly unwarranted invasion of personal privacy.
  • (b)(7) Records or information compiled for law enforcement purposes, but only to the extent that the production of such law enforcement records or information:
  • A. Could reasonably be expected to interfere with enforcement proceedings;
  • B. Would deprive a person of a right to a fair trial or an impartial adjudication;
  • C. Could reasonably be expected to constitute an unwarranted invasion of personal privacy;
  • D. Could reasonably be expected to disclose the identity of confidential source, including a state, local, or foreign agency or authority or any private institution that furnished information on a confidential basis, and, in the case of a record or information compiled by a criminal law enforcement authority in the course of a criminal investigation or by an agency conducting a lawful national security intelligence investigation, information furnished by a confidential source;
  • E. Would disclose techniques and procedures for law enforcement investigations or prosecutions or would disclose guidelines for law enforcement investigations or prosecutions if such disclosure could reasonably be expected to risk circumvention of the law, or;
  • F. Could reasonably be expected to endanger the life or physical safety or any individual.
  • (b)(8) Contained in or related to examination, operating, or condition reports prepared by, on behalf of, or for the use of an agency responsible for the regulation or supervision of financial institutions.
  • (b)(9) Geological and geophysical information and data, including maps concerning wells.

Given these extensive reasons, we can start to understand how there might be reason to include multiple FOIA exemption codes for one piece of redacted information.


Regulatory Compliance & Document Security

For many organizations, adding redaction reasons to shared or publicly-available documents isn’t mandatory, but it can help reduce the risk of both legal and compliance challenges. 

Consider a redacted court document shared as part of an eDiscovery process. Without a custom redaction reason, other parties may challenge the necessity of your redaction, especially if no contextual evidence indicates its necessity. 

Compliance audits also pose a potential problem. If years or even decades-old documents don’t contain redaction reasons — and the originals aren’t easily located — your organization could face increased regulatory oversight.

Take for example the healthcare industry. There are several clinical studies that require peer review. To keep biases at bay and personal information secure, redaction is critical to the adjudication process. Think about a clinical trial that has specific events related to a test subject. That test subject has participated in a trial for an incentive. 

However, that person did not agree to share his or her personal information with a broad audience. Once the panel of experts reviews the results of a clinical trial, the research goes on public record. It’s crucial to protect the participants involved and their PII to ensure that no harm comes to them.

Many document viewing tools make it possible to add single redaction reasons to released documents, but what happens if your organization is dealing with multiple data types? Look for a solution that enables you to add multiple redaction reasons or codes to clarify your intent and keep data secure.

developer coding in .NET Core

Is .NET or .NET Core the better bet for application development? Both frameworks are designed and supported by Microsoft and offer the ability to create apps capable of using multiple languages, abilities, and libraries, but they’re not the same. .NET Core is rapidly becoming the language of choice. For most app developers, .NET Core comes out ahead of its .NET counterpart. 

To understand why, let’s break down both .NET and .NET Core basics, examine the rise of .NET Core deployments, and dig into some key .NET Core benefits.


What is .NET?

Originally developed in the late 1990s and known as Next Generation Windows Services (NGWS), .NET reached beta release in 2000. As noted by Microsoft, .NET helps streamline application creation by allowing developers to write apps in C#, F#, or Visual Basic. By using a common language runtime (CLR) and class library, .NET manages system resources such as memory, thread execution, code execution, and security validation. This allows apps written in one language to talk with code written in other languages, significantly reducing the potential for interoperability issues.

Despite the benefits offered by .NET and work by Microsoft to standardize the software stack, concerns emerged among developers around the proprietary nature of .NET, especially in the realm of software patents. Microsoft has since changed its development approach to more closely follow open-source development models.

What is .NET Core?

.NET Core is an evolution of .NET that delivers both cross-code and cross-platform support. While Microsoft designed .NET to support Windows-based applications, .NET Core applications run on Windows, Linux, and macOS. It also uses MIT and Apache 2 licenses to deliver true open-source architecture and ensure consistency across operating environments.

While .NET remains the more popular framework by sheer volume of app development, .NET Core is quickly gaining ground. A recent survey found that .NET Core is now one of the “most loved” frameworks by developers.


Why is .NET Core becoming popular?

So, what’s driving the adoption of the .NET Core framework over .NET? Several factors now contribute to this uptake, including:

  1. Linux & Windows Deployment – One of the biggest reasons .NET Core is gaining popularity is due to its ability to deploy in both Linux and Windows. This provides vast cost savings to development teams.
  2. Run-Time and Performance Improvements  Whether your application users are internal employees or external partners and customers, runtime speed and performance concerns are always critical to adoption. Since Core is the future of the .NET platform, all future performance improvements will be implemented there and most will not be present in .NET Framework. .NET Core enables APIs and applications to serve up application interfaces and data faster, regardless of the mobile, IoT, or desktop device which is interacting with it.
  3. CommunityBecause .NET Core follows an open-source development model, there’s a large (and growing) community of devs and designers now supporting its ongoing evolution, allowing IT teams to leverage prebuilt .NET Core code rather than building their own from scratch.

.NET vs. .NET Framework

Beyond increased popularity driven by the shift in software development and standardization, the .NET Core framework also offers key benefits such as:

  • Ongoing ImprovementsIn September 2019, Microsoft released version 3.0 of .NET Core and followed it up with version 3.1 in November of the same year. In addition, the company plans to release a new version every year and remove the “Core” distinction between the two frameworks to deliver increased interoperability.
  • Improved Security From security-specific APIs to Microsoft’s Secret Manager and the Azure Key Vault Provider along with straightforward support for two-factor authentication (2FA), .NET Core improves application security without increasing complexity.
  • Cloud-Based Development SupportWith cloud now the de facto framework for everything from mobile applications, Internet of Things (IoTs), and responsive web applications, .NET Core makes it easy for developers to design cloud-native applications across multiple platforms and devices.
  • Easy Updates .NET Core updates are easily managed and applied, allowing developers to spend more time building great applications instead of dealing with complex and convoluted service upgrades.
  • Cross-Platform Code .NET Core code can run on not only Windows but Linux platforms, which can help greatly reduce your cloud deployment costs. Combined with Docker, developers are able to leverage a greater amount of modularity and flexibility than ever before.

The Accusoft Advantage

To help companies compete on the cutting edge of app development and integration, Accusoft is making .NET Core available for specific products, starting with Barcode Xpress for .NET Core. With just a few lines of code, companies can deploy multi-platform, open-source support for industry-leading barcode recognition. From reading damaged, broken, and incorrect barcodes to scanning multiple barcodes on one document in milliseconds, Barcode Xpress makes it possible to easily integrate cutting-edge barcode functionality into any application across any platform. 

Several of our other SDKs are on deck for .NET Core capabilities. While .NET broke new ground for interoperable frameworks, .NET Core offers the next iteration of interoperable development with cloud-based, cross-platform support for applications at scale. Learn more about our .NET Core plans here.

Despite its reputation for being slow to adapt and held back by outdated, legacy technology, the insurance industry is undergoing a tremendous period of digital transformation. A new generation of InsurTech applications are helping insurers respond more quickly to a dynamic market and empowering customers to become more engaged with their policies. InsurTech digital collaboration is a key industry trend.

Digital collaboration tools are critical to this dramatic shift, which has created a unique opportunity for InsurTech developers. By deploying features that allow insurers to streamline workflows and improve communication both with internal stakeholders and customers, developers can capitalize on an emerging need and establish their applications as the “new standard” for digital collaboration in the insurance industry.

Creating Better Digital Collaboration Tools for InsurTech Software

Accessible Viewing

The ability to easily access and view insurance documents is increasingly important to insurance agents and customers alike. When assembling a policy bundle, insurance agents must reference multiple pieces of information about customers as well as detailed actuarial data from a variety of sources. By building HTML5 viewing capabilities into InsurTech applications, developers can help underwriters reference all relevant information within their existing workflow. Rather than ponderously requesting documents from other departments and receiving them via email, and opening them with an external program, they can simply request, search for, receive, or view files without ever exiting their secure application.  

Customers, meanwhile, expect to be able to access their insurance records quickly and easily. Whether it’s a detailed description of their policy or a copy of their proof of insurance, they want the ability to log into a web-based application that allows them to locate and view records related to their account. This can greatly improve communication with their insurer since they’re able to quickly reference different aspects of their policy and identify their needs more clearly. Developers can build viewing features into an InsurTech application so customers can access their essential documents without having to download anything or take any additional steps. Insurers can also use the same features to easily provide updates about policies or rates. 

Annotations

Building an insurance policy or evaluating claims can be a lengthy and confusing process without the right digital collaboration tools in place. Documents often need to be reviewed by people in different departments before bundled services and rates can be finalized. If an InsurTech application lacks collaboration features, insurers may need to resort to emailing documents back and forth along with their comments. There is ample space for miscommunication in this scenario, with vital comments potentially going unnoticed or the wrong document being sent as an attachment.

Built-in annotation tools allow insurers to leave comments, highlight areas of concern, and provide helpful notes directly on the files themselves. Developers can also make it possible to share and view those documents entirely within the application environment, which reduces the risk that someone will overlook important comments or compromise privacy by opening a file with poorly secured software. Annotation markups are stored separately from the original file until they need to be burned into a new copy. This protects the integrity of the source document throughout the collaboration process.

Version Control

One of the biggest challenges with digital collaboration is maintaining version control over documents. When multiple people are working on a file, it’s important to make sure that everyone is using the most up-to-date version of it. This is especially true of insurance documents because rates and risk adjustments can sometimes change quite rapidly. The last thing an organization (or their customers) want is to have inconsistencies spread across several documents due to poor version control.

Developers can combat version confusion by keeping every stage of document workflows within their InsurTech applications. Version problems are usually caused by people downloading documents, working on them in isolation with a separate program, and then uploading their changed versions back into the application. By making it possible to view and annotate content within the application, developers can help ensure that everyone is working from the most up-to-date version of every file. 

Conversion

InsurTech applications must be able to handle a wide range of file types if they’re going to effectively facilitate digital collaboration. Customers often need to upload images as part of their insurance claims and will often provide documents as scanned images that can’t be searched for key text. Without the ability to convert files into more manageable formats, collaboration can quickly become an exercise in frustration and confusion.

Conversion tools not only make files more accessible, but also make it easier to manage content. Several small documents, for instance, could be combined into a single file for faster access, review, and markup. Developers can also incorporate Optical Character Recognition (OCR) into their InsurTech application to extract the text from a document image and use it to create a searchable PDF for more convenient reference. These conversion tools provide a great deal of workflow customization that allows their customers to set up efficient processes that help them deliver better services.

Boost InsurTech Digital Collaboration with PrizmDoc Viewer

Accusoft’s PrizmDoc Viewer is an HTML5 that integrates smoothly into your InsurTech application to deliver a powerful array of digital collaboration tools. Using a sophisticated collection of REST APIs, PrizmDoc Viewer provides support for multiple file types and can easily convert between formats to simplify insurance workflows. It also features a full range of annotation and redaction tools as well as OCR text extraction and electronic signature features.

With three decades of experience developing imaging and document management technology, Accusoft offers a variety of software integrations that can support digital collaboration efforts. From document assembly to secure spreadsheet support, our collection of SDKs and APIs can provide the features your InsurTech application needs to meet the evolving demands of the insurance industry. Check out our InsurTech fact sheet to learn how you can turn our capabilities into your capabilities.

As part of our ongoing commitment to supporting the LegalTech industry in its effort to transform the processes used by law firms and legal departments, Accusoft recently sponsored an educational webinar in conjunction with Law.com entitled “Build or Buy? Learning Which Is Best for Your Firm or Department.” Hosted by Zach Warren, editor-in-chief of Legaltech News, the webinar featured Neeraj Rajpal, CIO of Stroock & Stroock & Lavan, and Kelly Wehbi, Head of Product at Gravity Stack, a subsidiary of the Reed Smith law firm. 

Together, the panelists brought two unique perspectives to the ongoing “build vs buy” debate, both from the software vendors who provide LegalTech solutions and the decision makers working at the legal firms who make difficult decisions regarding technology solutions.

Build vs Buy: The Choices Before the Decision

Both Rajpal and Wehbi agree that any decision involving building or buying technology solutions has to begin with defining the problem a firm needs to solve. Regardless of whether you’re working with an independent legal firm or a legal department within a larger organization, it’s critical to understand the business problem, existing pain points, and potential value of a solution.

“When you start asking the right questions,” Raijpal notes, “you sometimes come across a situation where the requirements are not very clearly defined and that is a big red flag to me because when requirements are not defined, you’re not solving anything.”

Wehbi shares that concern about the requirements gathering process, pointing out that things tend to go wrong when firms fail to consider both the scope and magnitude of the challenge they’re trying to overcome. “Organizations can struggle a lot when they jump a little too quickly to a solution or to thinking about just what the return would be on a potential new product or service offered.”

It’s also critical to make sure that the firm is willing to accept some degree of change. If existing business processes are unclear or if no one is willing to consider changing how they work, then no amount of technology is going to make a difference. Understanding the culture of the firm and securing the buy-in from leadership is absolutely critical to making any technology integration succeed whether you’re buying a solution or building one from scratch. 

The Pros and Cons of Building LegalTech Solutions

For an organization that has the resources, methodologies, and skill sets necessary to develop a solution that’s specifically designed to meet its unique requirements, building can be a great decision. The key advantage here is that it focuses specifically on the firm’s processes and user pain points, allowing developers to design a solution that is much more targeted than an “off-the-shelf” product.

Benefits of Building

  • Applications can be customized to your exact specifications, allowing them to better address your specific business needs.
  • Since you manage the solution from end to end, you retain much more control in terms of application features and functionality, how data is managed, and access security.
  • Developing a specialized solution creates room for innovative technology that can provide a competitive edge.
  • A custom-built solution presents fewer integration challenges, especially when it comes to interfacing with legacy systems used by many legal organizations.

Risks of Building

  • Building a new solution from the ground up requires a great deal of time and resources that might be better spent elsewhere.
  • Investing in custom software creates substantial technical debt that must be maintained over time and could create integration problems in the future when additional upgrades are required.
  • If the new solution doesn’t contribute enough to the bottom line to justify the cost of operations, it could lead to negative economies of scale that make it difficult for the firm to grow its business.

The Pros and Cons of Buying LegalTech Solutions

Not every organization has the development resources to build a customized solution from the ground up. If they’re not ready to make that capital investment, a cloud-based offering may be better suited to their needs. Leveraging a proven, ready-to-launch SaaS solution offers a number of advantages, but could impact how the company makes technology decisions in the future.

Benefits of Buying

  • Since SaaS services are usually cheaper and easier to implement, they are often the best option for companies with limited IT resources.
  • Cloud solutions are good for solving common technology problems that smaller firms face.
  • Already-live functionality means SaaS solutions can be implemented on a faster time frame.
  • The cloud vendor handles all building and maintenance costs associated with the platform.
  • Since the vendor sets up workflows and integrations as well as troubleshooting, your internal team is freed up to focus on other tasks.

Risks of Buying

  • Off-the-shelf solutions offer less customization and control over infrastructure and data.
  • Even industry-specific SaaS solutions are built for a general market in mind, so their features may not solve your firm’s unique requirements.
  • Since the vendor manages security, customers have less oversight over how their sensitive data is managed.
  • Working with a SaaS provider exposes firms to market risk. If the vendor goes out of business or sunsets a product, it may be difficult to repatriate data or transition to another provider.

When to Build

For firms with the development resources that are already using in-house document management solutions to streamline processes, SDK and API integrations are often the best way to enhance functionality. Accusoft’s PrizmDoc Suite leverages REST APIs and advanced HTML controls to provide powerful document viewing, conversion, editing, and assembly capabilities to web-based applications. Our SDK integrations also allow developers to build the functionality they need directly into their software at the code level.

Document Assembly

Law firms need automation solutions that allow them to easily create and manage multi-part, multi-stage contracts. Thanks to Accusoft’s PrizmDoc Editor, legal teams can rapidly identify and assemble sections of pre-existing text into new content that is both editable and searchable. PrizmDoc Editor integrates securely into existing applications and delivers in-browser support to help lawyers assemble assets without resorting to risky external dependencies.

Case Management

LegalTech applications can manage and review cases much more efficiently by integrating data capture, file conversion, and optical character recognition (OCR) capabilities. The ImageGear SDK helps legal teams access case data in a variety of formats without the need for downloading additional files or relying on third-party viewing applications. It can also convert multiple file types into secure and searchable PDF/A documents, making it easy to tag files with client numbers, names, and other identifiable information. Thanks to PDF/A functionality, ImageGear ensures that firms can stay on the right side of federal regulations.

eDiscovery

The rapid transition to predominantly digital documents has fundamentally altered the way legal organizations approach the discovery process. Innovative eDiscovery processes can streamline case management while also protecting client interests. In order to implement these strategies effectively, firms need applications that provide extensive file format support and search functionality as well as redaction and digital rights management (DRM) tools capable of protecting client privacy. PrizmDoc Viewer delivers these features along with scalable annotation capabilities that make it easier for collaborators to proofread, review, and make comments to case files without creating version confusion. As an end-to-end eDiscovery toolkit, our HTML5 viewer also includes whitelabeling support so it can be fully integrated into your application’s branding.

When to Buy

For smaller legal teams looking for broad functionality without development hassles or a new firm taking its first steps toward document automation, it often makes more sense to implement a bundled, buy-in solution like Accusoft’s Docubee SaaS platform.

Document Completion

Docubee makes document management easy with drag and drop data routing. Users can quickly create legal contracts, route the appropriate data to documents, deliver contracts for approval, and facilitate signing with secure eSignature technology. 

Customized Templates

With Docubee, legal teams can create customized document templates and manage them on a section-by-section basis. Individual clauses can be added or removed as needed, allowing attorneys to repurpose document templates instead of creating them from scratch for every client. 

End-to-End Support

Two-way communication support helps firms to build better dockets and negotiate more effectively. Documents can be updated automatically and version controls ensure that everyone is always looking at the most up-to-date version of a contract. Docubee also allows users to prioritize key tasks with collaborative redlining and notification tools.

Long-Term Storage and Security

Docubee stores data for up to six years to meet eDiscovery requirements. To better protect client privacy and meet changing compliance requirements, firms can also set destruction dates for contracts, templates, and case files. Docubee is SOC2 compliant, featuring multi-layer encryption to keep data under tight lock and key.

Hear the Full Conversation

To hear the full webinar and learn more about how legal firms make the difficult choice between building or buying their next technology solution, sign up now to get access to an on-demand recording of the event. If you’re ready to learn more about how Accusoft technology is helping to power innovation in the legal industry by delivering the latest in content processing, conversion, and automation solutions, visit our legal industry solutions page or contact us today to speak to one of our product experts.