Data Masking Components: Date Of Birth

{TOC}

Date Of Birth

API Reference, CLR Reference

Usage Instructions:

Purpose

The purpose of the component is to mask values of date and datetime data types, especially date of birth. The component makes necessary allowance for the k-anonymity requirement in terms of sparsity of centenarians or people close to centenarians in age in general population. Tch allowance is a requirement in HIPAA 18 elements

Algorithm

Date Variance

Description

The Masking Date of Birth component provides generic date handling. It expects a string in the date format (‘MM/DD/YYYY) and can be used to mask any date.The component also allows selection of the interval of confidence in days that defines interval of variation for the date. The date itself is in the middle, interval values add both positive and negative numbers of days to the date. Example: if May, 1st 2000 is the date, defining an interval of confidence as two days will produce April 29th, April 30th, May 1st, May 2nd, and May 3rd as values.

API Reference, CLR Reference

Usage Instructions:

1. Configure a source that contains the column with alphabeticalDate andtype numericvalue characters. The data in the column may also includeor any other characterdate that will be treated as a separator. type.
2. Drag and Drop GenericDate AlhaNumericof Dynamic Birth data masking component, connect the source and the genericDate alphaof numericBirth component with the source's precedence constraint:
3. Now, the precedence constraint (the blue arrow) passes proper meta-data to the GenericDate AlphaNumericof Birth component. If you click on the constraint, you will see:
4. Now that the metadata for the GANDOB exists, and values are passed into the data masking component, please open the component editor:
5. In the second tab, there are input columns. Please check-mark only one column, the one that you will be masking with GenericDate Alphaof NumericBirth algorithm:
6. This will create an extra column with the prefix “Masked_”.
7. Create a connection manager for the destination and configure source component for the destination. In the connection manager, in the tab “Mappings”, specify that you want newly created Field_Masked to be a field replacing the original value. For that, just click on the available input columns, choose the masked value, and map to the “Available Destination Columns”
8. Now, all the configurations are complete for the valid values. You can run the package with the GenericDate AlphaNumericof DynamicBirth Data Masking component, and see the results of data masking:

Error Handling

9. If, however, there are invalid values in the package's source, one would need to configure error handling. Invalid values are those that are not conforming to the rules of the entity. To handle invalid values, each data masking component has error handling precedence constraint. One needs to create error destination connection and connect red arrow (error handling constraint) with this destination. As the connection is made, one needs to configure the state of failure: “Fail”,”Ignore” or “Redirect”.
10. It is recommended that one re-directs the output into the error destination, so that later one be able to analyze and process data for quality purposes. The GenericDate Alphaof NumericBirth components errors are the only ones not recommended for further processing as it is truly hard to break their format.
11. It is our suggestion that with GenericDate Alphaof NumericBirth component one should not process erroneous data without further analysis at all.

Download Example ###**