Saltar al contenido principal

PII Anonymizer

Deprecated

Use phi-deidentify node instead. It provides NLP-based detection and FHIR-aware processing.

Category: Healthcare Standards
Node id: pii-anonymizer
Maturity: beta
Risk tier: B

Standards: HIPAA, GDPR, SOC2

De-identifies protected health information (PHI/PII) using hashing, redaction, masking, pseudonymization, or generalization methods

What it does​

  • Five de-identification methods: hash, redact, mask, pseudonymize, generalize
  • Object and array data support with recursive field processing
  • Pseudonymization with reversible mapping output
  • Format-preserving anonymization option
  • Configurable field targeting with explicit field list

Use cases​

  • De-identify patient records for HIPAA-compliant research datasets
  • Pseudonymize PHI with mapping for re-identification if authorized
  • Generalize date-of-birth and zip codes for k-anonymity
  • Batch-anonymize FHIR resources before cross-border data transfer

Runtime​

  • Performance tier: fast

Input ports​

NameTypeRequiredDescription
datajsonYesData object or array containing PII fields to anonymize

Output ports​

NameTypeRequiredDescription
resultjsonNoDe-identification output with anonymized data, mapping (pseudonymization only), and fields_anonymized count
successbooleanNoWhether de-identification succeeded

Settings​

Basic​

SettingNameTypeRequiredDefaultAllowed valuesDescription
Anonymization MethodmethodenumYeshashhash, redact, mask, pseudonymize, generalizeMethod used to anonymize PII fields
Fields to AnonymizefieldsarrayYesList of field names to anonymize in the input data
Data Fielddata_fieldstringNodataName of the input key containing data to anonymize

Auth​

SettingNameTypeRequiredDefaultAllowed valuesDescription
Hash SaltsaltsecretNoSalt string for hash-based anonymization

Advanced​

SettingNameTypeRequiredDefaultAllowed valuesDescription
Preserve Formatpreserve_formatbooleanNofalsePreserve the format of values during masking or pseudonymization

Errors​

CodeDescription
INVALID_METHODThe specified anonymization method is not recognized
MISSING_FIELDSFields configuration is required to specify which fields to anonymize
INVALID_DATAInput data is not a valid object or array

Runtime notes​

  • Anonymizes the fields it is given by name; it does not scan for identifiers the caller did not list.
  • Only the fields listed in 'fields' config are anonymized; all other fields pass through unchanged
  • The 'mapping' output is only populated for pseudonymize method (maps pseudonym back to original value)
  • Hash method produces SHA-256 hex strings; salt config strengthens the hash but is not reversible
  • Generalize method converts numeric values to age-range buckets (0-17, 18-34, 35-54, 55-74, 75+)

See Build any workflow for how to put nodes together and Ports, types and data flow for how port types connect.

¿Algo no está claro? Envíe sus comentarios sobre la documentación por correo electrónico..