🛠️ Method 1: Manual Creation of a New Utility Set
Steps to Create a New Utility Set Manually
-
Navigate to Utility Sets Page:
- Click on the Create Button on the Utility Set view. You will be directed to the Create New Set view.
-
New Utility Set Details:
- Enter the Utility Set Name and set the Creation Method to Manual.
- Click Next to proceed.
-
Edit Fields and Utility Parameters:
- On the next screen, users can enter single or multiple tables they want to anonymize.
- Click on Add Tables:
- A side panel will appear to fill in table details.
- Table ID: Represents the primary key of the table.
- Fields: Specify the columns to anonymize (multiple columns can be added as comma-separated values).
-
Add Conditions (Optional):
- Click Add a Condition to further filter the selected table data.
- The following details are required to add a condition:
Condition Details Table
Input Field | Description | Values | Screenshot |
---|---|---|---|
Condition Name | Input field to define the name of the condition | ||
Tables | Refers to the tables this condition will apply to | All in Utility Set / Particular Table | |
Fields | Column of the table | ||
Function | Specify filtering function | Is, Is Not (Blank Equal, Greater Than, Less Than, Start With, On the List (manual entry), Linked [table].[field]) | ![]() |
Values | Defines the value of the Field in the database | Input field to specify the conditions |
Example:
Condition: Filtering on the table patient
where the value of the column branch
is equal to Mining
.
Managing Table Details in the Utility Set
- Edit Table Details:
- Click on the Table Name or Edit Option in the Utility Set Table.
- View the selected table and its respective columns for anonymization.
- Users can:
- Delete or add a new column for anonymization.
- Define the Utility Parameter, Utility Parameter Conditions, and Privacy Relevance.
Utility Parameters and Conditions
Utility Parameters | Utility Conditions | Description |
---|---|---|
No Change | N/A | Leaves the data unchanged. |
Clear Values | N/A | Clears the data in the selected fields. |
Dummy Domain, Keep Domain, All Caps | Anonymizes email addresses with additional formatting options. | |
Name | First Name, Last Name, All Caps, Full Name | Handles name fields with specific conditions for first name, last name, etc. |
Consistent ID | N/A | Generates a consistent identifier for tracking across records. |
Fixed Value | Input Field | Replaces the field with a fixed value. |
Date | Same Year, Random, Adult, Consistent | Anonymizes date fields while retaining some options for consistency. |
Phone Number | Random, Remove Country Code | Handles phone numbers by formatting them or generating new numbers. |
Number | N/A | Randomizes or anonymizes numerical data. |
Custom Expressions | N/A | Allows custom regular expressions or formats to be applied to the data fields. |
Condition-Specific Details:
-
Email Conditions:
- Dummy Domain: Replaces the email domain (e.g.,
example.com
). - Keep Domain: Retains the original domain while anonymizing the rest of the email.
- All Caps: Anonymizes the original email and converts the entire email to uppercase.
- Dummy Domain: Replaces the email domain (e.g.,
-
Name Conditions:
- First Name: Anonymizes only the first name field.
- Last Name: Anonymizes only the last name field.
- All Caps: Anonymizes the name and converts the name to uppercase.
- Full Name: Anonymizes the entire full name as a single unit.
-
Date Conditions:
- Same Year: Keeps the year consistent across all records.
- Random: Randomizes the entire date.
- Adult: Ensures the date reflects an adult age.
- Consistent: Keeps the date consistent across records.
-
Phone Conditions:
- Random: Randomizes the entire phone number.
- Remove Country Code: Removes the first 4 digits from the original phone number and generates a consistent anonymized value for the remaining number.
-
Custom Expressions:
-
Definition: While creating a utility parameter, you can define the Utility Parameter as
Custom_Expression
. -
SQL Expression: Custom expressions are SQL update queries that are executed once all the anonymizations are done.
-
Steps for Custom Expression:
- Select the Utility Parameter as
Custom_Expression
and enter the expression in the parameter text box. - Ensure that the expression follows correct SQL syntax.
- Select the Utility Parameter as
-
Guidelines for SQL Expression:
- Enclose table column names in hash characters (
#
). - Enclose strings in single quotes (
''
).
- Enclose table column names in hash characters (
-
Example of Custom Expressions:
- Example SQL expression:
UPDATE #table# SET #column# = 'new_value' WHERE #column# = 'old_value'
- Example SQL expression:
-
Restrictions:
- The application doesn't allow you to customize a column with
Custom_Expression
using another column that also has a utility parameter selected asCustom_Expression
.
- The application doesn't allow you to customize a column with
-
Utility Parameter Table
Column | Utility Parameter | Utility Parameter Condition | Description |
---|---|---|---|
CUSTOM_EXPRESSION | normal-string | The email column will be anonymized with the anonymized value of the name column concatenated (symbol ` |
Privacy Parameter Classification
The Privacy Parameter is used to protect sensitive customer information, determining the logging behavior during job runs. It is classified into three categories: Personal, Confidential, and Non-Relevant.
Privacy Types and Logging Policies:
Privacy Type | Example Data | Logging Policy |
---|---|---|
Personal | Name, Address, Email, Phone Number | The original fields are not logged in the audit logs. |
Confidential | Account Number, Financial Details | The original fields are not logged in the audit logs. |
Not Relevant | Non-sensitive data without privacy implications | Log original values in the audit logs. |
Privacy Classification:
- Personal: Data that can directly identify an individual, such as name, address, phone number, or email.
- Confidential: Data that is not directly identifying but is sensitive and private, such as account numbers, financial details, or proprietary business information.
- Not Relevant: Data that does not have privacy implications and does not directly or indirectly identify individuals or contain sensitive business information.
Final Steps:
- After entering the Utility Parameter, Utility Parameter Condition, and Privacy Parameter, click Save to finalize the settings.