Filter sensitive information from text

Philter identifies and removes sensitive information such as PHI and PII from natural language text. Philter can be deployed in less than 10 minutes in AWS, Azure, and Google Cloud Compute Engine.



Filter Profile Registry

The Filter Profile Registry is a free companion application for Philter that provides a centralized service for managing and storing filter profiles. A filter profile is a configuration that specifies the types of sensitive information to find in text and how to manipulate the sensitive information.


How Philter identifies and replaces sensitive information such as PHI and PII is defined by a set of files called filter profiles. The Filter Profile Registry provides a centralized service for storing and managing filter profiles. Through its API, filter profiles can be listed, added, retrieved, and deleted. By utilizing the Filter Profile Registry, you can store the filter profiles externally from Philter to enable their use across many instances of Philter. Filter profiles can be stored on the local disk or in an Amazon S3 bucket.

The Filter Profile Registry is useful when you have different types of documents for which you want to handle the sensitive information differently for each type.

See the Filter Profile Registry User’s Guide for examples on how to use the Filter Profile Registry.

Launch Filter Profile Registry

View on DockerHub or pull and run the Filter Profile Registry using the commands below.

docker pull mtnfog/filter-profile-registry
docker run --name fpr -p 8080:8080 mtnfog/filter-profile-registry

Usage Reference

For more detailed instructions see the Filter Profile Registry documentation.

List filter profiles:

curl -k -s https://localhost:8080/api/profiles

Upload a filter profile:

curl -k https://localhost:8080/api/profiles -d @profile.json -H "Content-Type: application/json"

Get a filter profile by name:

curl -k -s https://localhost:8080/api/profiles/{profilename}

Delete a filter profile:

curl -k -s -X DELETE https://localhost:8080/api/profiles/{profilename}

Get the status of Filter Profile Registry:

curl -k -s https://localhost:8080/api/status