deidentify | Protected Health Information according to HIPAA Privacy Rule

Misread the question at first..

You can import the csv and change only the identities in field Two like this:

This issue was reported at Google Public Issue Tracker, such requests aren't indexed, but it's a good way to report issues or request new features. Please follow this case to be updated.

There's a workaround suggested by Google:

This is a case where we have some undefined behavior when findings overlap. The person comes from the user's configuration to replace people name with person.

They can omit the overlaps.

For more information, please have a look at the documentation Modifying infoType detectors to refine scan results section Omit matches on PERSON_NAME detector if also matched by EMAIL_ADDRESS detector:

The following JSON snippet and code in several languages illustrate how to indicate to Cloud DLP using an InspectConfig that it should only return one match in the case that matches for the PERSON_NAME detector overlap with matches for the EMAIL_ADDRESS detector. Doing this is to avoid the situation where an email address such as "james@example.com" matches on both the PERSON_NAME and EMAIL_ADDRESS detectors.

The issue had nothing to do with DLP.

I was sending invalid JSON:

I get an error if I don't set a crosswalk first, but this is fairly trivial:

Most likely, the key is not wrapped correctly. Can you please try the following commands to see that the decryption of the wrapped key generates the right output?

The error: “google.api_core.exceptions.InvalidArgument: 400 Could not de-identify all content due to transformation errors. See the error details for an overview of all the transformation errors encountered.”

This is a generic error when free-form text de-identification fails due to some transformation errors. Unfortunately, it seems like the python library is not exposing the error details.

As per the service documentation [1], the detected tokens must be at least two characters long: