De-Identify Sensitive PHI and SSN Fields. Auditable, Data Deidentification for PCI, HIPAA, etc.

Home » Solutions » Field Protection » De Re-Identification

Field-Level De/Re-Identification

» Solutions

Field Protection

Encryption/Decryption

Encode Sensitive Data (Recoverable Protection)

Challenges:

Do you need to change the individualizing characteristics of data so that a person or item stored in the original field cannot be identified, but nonetheless remain individualized? This way, files can flow safely de-identified through different departments, and where necessary, be re-identified.

Sensitive field data must also be replaced with altered (but reversible) output but maintain the characteristics of the original field (like the length, data type, or even a real-looking but different value). Field-level encryption does not accomplish this goal because the ciphertext result is usually longer than the original field and will not look recognizable.

Solutions:

The CoSort product's SortCL tool gives you many ways to de-identify PHI and other sensitive field data (like a social security or cell phone number) in your files. At the same time, the de-identified field can look more realistic and still be recovered.

With CoSort, you can de-identify private fields in these ways:

Specify lookup (set) files to substitute sensitive field values with a pseudonym
Use the built-in de-identification function to encode fields with ASCII characters
Transform the field with one or more data manipulations
De-identify or encode the data with your own field-level transformation function

Example of the function-based de-identification option offered in CoSort's Graphical User Interface - to - Sort Control Language (gui2scl) Java client application. In this example, the SSN field in a file is de-identified.

These field-level de-identification methods can help you comply with certain privacy regulations, leave your non-sensitive data and files available for further processing, and produce an XML audit trail to help you verify compliance. However, de-ID functions may not provide the robust levels of security and recoverability which SortCL's built-in AES-256 encryption function affords. Please see the Next Steps for more details.

IRI, The CoSort Company