Suggested Redactions for Documentum, Alfresco or Hadoop using OpenRedact

We have recently seen many of our insurance clients asking what they can do about any PII (Personally identifiable information) and PHI (Protected Health information) that is in the documents they receive from various sources in their ECM repositories. TSG released OpenRedact as a product to help solve this problem by allowing users to manually redact portions of the document to hide some of this sensitive information. This post is going to outline the newest enhancement to OpenRedact to allow for a more automated and “accident proof” redaction process.

As more of our clients start getting electronic copies of documents, the amount of sensitive information in these documents is continuing to expand. We have worked with many of our clients with a variety of eDiscovery and analytic tools to try and completely automate the process of redacting information on all of their documents with limited success. The largest complaint we have heard with these tools is that they often times “over-redact” the document by redacting information within the document that is not PII or PHI data, leading to a loss of fidelity for users attempting to use the now redacted information documents.

We are happy to announce the availability of the “Suggested Redactions” mode for OpenRedact, which provides users a way to redact information on a document without having to manually identify information that should be redacted. OpenRedact allows us to configure any patterns to look for in the content of the document that should be redacted. This allows users to quickly identify what should be redacted in the document, but also allows a human to manually accept/reject any redactions to ensure that the correct information is redacted.

Check out the video below to see how OpenRedact can be used during the upload of a document into your ECM repository to scan the document for sensitive information as it is being ingested.