# A Privacy-Preserved Analytical Method for eHealth Database with Minimized Information Loss

Authors: Ya-Ling Chen; Bo-Chao Cheng; Hsueh-Lin Chen; Chia-I Lin; Guo-Tan Liao; Bo-Yu Hou; Shih-Chun Hsu
Journal: Journal of Biomedicine and Biotechnology
 (2012)

---

## Abstract

Digitizing medical information is an emerging trend that employs information and communication technology (ICT) to manage health records, diagnostic reports, and other medical data more effectively, in order to improve the overall quality of medical services. However, medical information is highly confidential and involves private information, even legitimate access to data raises privacy concerns. Medical records provide health information on an as-needed basis for diagnosis and treatment, and the information is also important for medical research and other health management applications. Traditional privacy risk management systems have focused on reducing reidentification risk, and they do not consider information loss. In addition, such systems cannot identify and isolate data that carries high risk of privacy violations. This paper proposes the Hiatus Tailor (HT) system, which ensures low re-identification risk for medical records, while providing more authenticated information to database users and identifying high-risk data in the database for better system management. The experimental results demonstrate that the HT system achieves much lower information loss than traditional risk management methods, with the same risk of re-identification.


---

## Body

## 1. Introduction

Electronic medical records and cloud storage have been introduced in hospitals in recent years. Medical institutions are required to store electronic records in a database and provide access for doctors and researchers. Digital records [1, 2] provide convenience, but such a system also introduces the new challenge of storing personal information securely. The issue of privacy [3] has received much public attention recently. Based on personal information, a specific person can be identified directly or indirectly. Information that can be used to directly identify a particular person is called personally identifiable information (PII). According to the definition given by the United States Office of Management and Budget, full name, Social Security Number, face, fingerprints, and genetic information are all categorized as PII.According to NIST IR7628, personal information privacy means a person has the right to decide when and where to disclose their personal information. It also says that the storage and access of personal information and PII must be secure. Three personal information security measures have been proposed in NIST SP800-122:(1) minimizing the use, collection, and retention of PII, (2) conducting privacy impact assessments, and (3) deidentifying information.Medical institutions save large amounts of personal information in databases whose contents can be divided into three categories: Direct Identifiers (DID), Quasi-identifiers (QID), and Sensitive Information (SI). Information that allows direct identification, such as the Social Security Number, is called DID. Details such as date of birth, level of education, and postcode, which can be combined to identify a person, are QID. Information that is private and confidential, such as medical conditions, is categorized as SI. To provide security of personal information, medical institutions are required to check information before release to prevent any violation of patient privacy.When eHealth practitioners (such as service provider, insurance company and other health researcher) want to access medical records, the hospital can de-identify the database to protect patient privacy. However, when multiple users need to access the database, they would each have unique requirements. The hospital must release several de-identified databases, which are then difficult to manage. In addition, the de-identified database differs from the original database. In other words, the de-identified database will be altered and the degree of alteration is represented by the information loss (IL). As the database provider, the hospital prefers high IL to protect patient privacy and lower the possibility of re-identification of the information. In contrast, researchers prefer databases with low IL for their work. Therefore, the challenge is to strike a balance between the two interests.An information management procedure has been proposed [4] to manage research-oriented electronic medical records. The aim is to minimize the probability of disclosure of personal information. The procedure is as follows.(1)
The information owner must check the legitimacy of the reason for requiring access to the database.(2)
A risk assessment must be conducted based on the user's requirements.(3)
Decide whether de-identification is needed based on the risk associated. Execute various de-identification methods.(4)
Release the database to a user once the risk of re-identification is acceptable.De-identification [5, 6] is the primary method of protecting private information, where the original database is modified to prevent direct identification of a person through their records even if multiple databases are combined. Some common de-identification techniques are data reduction, data modification, data suppression, perturbation, and pseudonymisation [7]. The k-anonymity model [8–10] is commonly used to assess the performance of a de-identification technique in reducing the risk of re-identification. When users search the database after a database is de-identified, one of every k results is authentic. However, the other k-1 results also appear in the search results. Usually, the authenticity of the results cannot be determined, which means the higher the k value is, the lower the risk of re-identification is [11].Currently, numerous privacy-preserving administration tools are commercially available on the market, five of which are markedly popular [12]: the PARAT, μ-Argus, CAT, UTD Toolbox, and sdMicro. Among them, the UTD Toolbox and CAT are based on the k-anonymity algorithm. The UTD Toolbox does not provide active support for its products, despite its functions designed from the developer’s perspective. The CAT suffers from usability difficulties. For example, because the k value of k-anonymity cannot be defined using the CAT, this tool operates unstably. In contrast to the CAT, the sdMicro is unable to process large datasets; furthermore, it crashes frequently. Currently, the tool receiving the most support is the PARAT, which is superior to CAT regarding the k-anonymity algorithm, and outperforms the μ-Argus in resulting precision level.Some previous studies have focused on reducing the risk of re-identification. However, limited research effort has been spent on safeguarding privacy while minimizing data distortion. El Emam et al. [13] proposed a set of programs that balance the risk and the extent of data distortion. If the risk exceeds the preset threshold value, the system tests various de-identification techniques to try and limit data distortion to the required level. However, such a system is unable to identify the data that is responsible for the higher risk effectively; it spends a lot of time on the trial-and-error process.In this study, we propose the Hiatus Tailor (HT) system. By using the Execution Chain Graph (ECG) to progressively de-identify data, people's privacy can be protected. The name Hiatus Tailor refers to the fact that the proposed system is capable of identifying the missing element within the system and fixing it. It uses progressive risk assessment and mitigation, and is able to balance the risk of re-identification and data distortion. Among the scenarios where the re-identification risk requirement is satisfied, the proposed method chooses the one that minimizes the distortion level. The main contributions of this paper are summarized as follows.(i)
In contrast to other de-identification methods that de-identify the entire database once, resulting in high IL, the HT system not only meets the privacy protection requirements, but also categorizes data into QID blocks using ECG. The risk is assessed progressively for each block. Based the re-identification risk estimated by this assessment, an optimal de-identification method is selected. As de-identification is not required at every node, the HT system is capable of reducing IL.(ii)
Tradition risk assessment methods can only indicate whether the risk is high or low. However, for most databases, the source of the risk cannot be identified. Therefore, the process of identifying the source of the increased risk is time consuming. The HT system uses QID and progressively assesses risk for a database. ECG allows an examination of the entire system and assists medical institutions in evaluating whether the target system satisfies privacy safeguard requirements. If the system is found to have a high level of risk, it is easier to identify and handle the QID data block that is responsible for the high-risk level.


## 2. HT System Architecture and Operation Method

The two main components of the HT system architecture are the Execution Chain Graph Composer (ECG Composer) and the Privacy Tailor. Based on various user requirements, the ECG composer creates the Execution Chain Graph and sends it to the Privacy Tailor. As the Privacy Tailor receives the Execution Chain Graphs from the ECG Composer at different nodes of execution, it assesses the risk of QID combinations in the database. If the risk is too high, it de-identifies the identifiable information with less information loss in the database.


### 2.1. Architecture

The HT system architecture consists of two major components: ECG Composer and the Privacy Tailor (as shown in Figure1). ECG Composer compiles the information obtained from users’ requirements and generates the Execution Chain Graph, which is sent to the Privacy Tailor for further processing and risk assessment.Figure 1
HT system architecture.The operation of the ECG Composer is based on information from the following elements.(i)
Database schema: defines the properties of the database, such as the type of the tables in the database and the attributes of the table. From the database schema, the data types of the stored data can be identified.(ii)
Application context: includes components related to SQL query statements, which is performed with the SELECT statement to retrieve a list of columns (including QIDs and other regular data) from one or more queried tables with the optional WHERE clause only returning the rows for which the comparison predicate evaluates to True. These SQL query statements are the details relevant to the user application. The order in which the application accesses QIDs determines which QIDs are analyzed by ECG in different nodes.(iii)
Privacy policy: defines the privacy policy associated with the user or company, such as the thresholdk (k-anonymity) for the QID. The privacy policy is modeled as (U, Q, K, G, and F), for different users (U), the administrator can specify the QID(Q) list, the threshold k (K) to be satisfied for k-anonymity, and the de-identification technique (G). The file (F) of the de-id technique contains the de-id policy where we adopt the taxonomy tree approach described in [14]. The de-identification technique (G) may include Data Reduction, Data Modification, Data Suppression, Pseudonymisation, and Generalization. Each de-identification technique has its own specification which is described in the file (F). For instance, Generalization technique will revise the attributes in a hierarchy manner based on the taxonomy tree structure described in file (F). Take the field “country of origin” as a Generalization technique example. USA and Canada are part of North-America. If they are generalized, both USA and Canada will be represented as North America.Based on user requirements, ECG Composer compiles the information obtained from these components and generates the Execution Chain Graph, which is sent to the Privacy Tailor for further processing and risk assessment.Privacy Tailor is analogous to a privacy management department. Its operation can be described as two stages:(1) risk assessment: executes the risk assessment procedure and estimates the re-identification risk of the current assessment phase. (2) Deidentification: on completing the risk assessment, if the re-identification risk is higher than the threshold, Privacy Tailor identifies the tuples that has relatively high risk and needs to be de-identified. The re-identification risk is calculated as described in [15] (as shown in (1)):
(1)R=1Minj(Fj),
where Fj is the size of an equivalence class.An equivalence class is the set of records in the database which have the same values on all quasi-identifier attributes. When an equivalence classes has the smallest value, we have the highest probability of re-identification and use it as our re-identification risk. As such, the Risk Assessment component will scan the database based on various de-identified QID combinations to find the size for each equivalence class and obtain the re-identification risk.ECG Composer uses the contents of the Database schema provided by the user, the operations defined in Application context, and the privacy policy associated with the user, to generate a series of Execution Chain Graphs and forward them to Privacy Tailor. The Execution Chain Graph will be described in the next section. Both Privacy Tailor and Execution Chain Graph node use a node as their unit and are divided based on several levels of re-identification risk of the QID combination in the required database table. When the re-identification risk is below the privacy policy threshold, no operations are required; Privacy Tailor continues to the next node. When the re-identification value is larger than the privacy policy threshold, identification is performed at that level by comparing the re-identification risk value for different combinations of QID to find the most suitable scheme.


### 2.2. Execution Chain Graph (ECG)

Database access task execution is modeled and structured in various stages aimed at clients in several nodes of database retrievals. As described earlier, the ECG Composer compiles the user requirements, consisting of the Database Schema, Application Context, and Privacy Policy, and then generates the Execution Chain Graph in which each node represents a “stored procedure” that accesses database system, and the directed edge denotes execution sequence (or caller to caller relations). Each stage consists of several atomic “stored procedure” nodes which have a set of associated attributes as follows.(i)
Information loss: the magnitude of the difference between the original database and the database after de-identification.(ii)
Re-identification risk: the possibility of identifying a specific entity directly or indirectly with various de-identified QID combinations.(iii)
Table access: the table name where information is stored and accessed.(iv)
QID: quasi-identifier, which is a subset of attributes that can indirectly identify a specific entity in a table.(v)
Condition: the relevant WHERE clause of the SQL statement is used to extract the records which satisfy a specified criterion.These properties can be further classified as Local and Aggregate. The Local value is the result of evaluating the QID combination of the current node. Aggregate value is the result of adding the evaluation of all QID combinations of all previous nodes.


### 2.3. ECG Composer

This section describes the ECG composer process. The ECG composer requires users to provide relevant data as input. When the system receives data from the admin, it will output an Execution Chain Graph according to requirements, and each node will have a form to record relevant data. The input to ECG composer consists of the Database SchemaΩ; Application Context Ψ; and QID List Γ. Algorithm 1 shows the algorithm of ECG composer, which creates a node set S based on the user’s Application Context. Every node has an associated form that records node information. The order in which the application accesses QIDs determines the execution order which represents a direct edge from Si to its successor, Sj. It will retrieve the specified table, attribute list (AL), and conditions for the data from the Application Context. ECG composer compares the AL with the QID list (QL). If there is an intersection, the QIDs in the intersection will be assessed according to the privacy policy, in the order of application access. In each node, node information will be updated to complete ECG generation.Algorithm 1:ECG composer algorithm.
(1) Given: Database schema Ω; Application Context Ψ;
QID List Γ;
(2) AL: Attribute list;
(3) QL: Target QID list;
(4)S: node set;
//Create ECG
(5)S = Construct the node set from Ψ;
(6) Build the direct edge set for each pair of (Si, Si) based on the order of the QID accesses in Ψ;
(7) For each nodeSi{ //Si∈S (i: number of node);
(8)  Extract the corresponding (Table, AL, Condition);
(9)  QL =∩ AL;
(10)  If (QL != Φ) {
(11)   Update (TABLE, QL, Condition) forSi;
(14)  Assess risk forSi;
(15)  }
(16) }Figure2 shows an example for the operations of ECG composer. Supposedly, we have QID List (Γ= age, region, sex, and education) and Application Context Ψ listed as below:SELECT age FROM E_table WHERE age ≥30,SELECT region FROM E_table WHERE age ≥30,SELECT sex FROM E_table WHERE age ≥30.Figure 2
ECG composer operation.Database Schema defines the data types for age, region, and sex as integer, varchar, varchar, respectively. Based on line 5 and 6 in Algorithm1, ECG composer creates a node set S with 3 nodes (S1, S2, and S3) and connects the 3 nodes. Each node has an empty node information form that specifies information loss, re-id risk, and table access. This is the initial ECG. For each node, ECG executes line 08 statement to extract the (Table, AL, Condition) from Ψ. For example, (E_table, age, age≥30) is extracted from the SQL statement “SELECT age FROM E_table WHERE age ≥ 30” for S1. Next, ECG composer will compute the intersection of the attribute list (e.g., AL=age for S1) and the QID List (Γ = age, region, sex, and education). If the intersection (QL) is not empty then ECG performs two steps (line 11 and line 12) as follows: (1) updates node information form (TABLE, QL, Condition) for Si; and (2) assesses risk for the current node Si locally.In our example, according to the order of application access, the system will assess age, region and sex in S1, S2, and S3 one by one. The assessment is based on the threshold k defined in the input privacy policy. For example, in node S1,  according to SQL statement (SELECT age FROM E_table WHERE age≥30), the age data from E_table satisfying age≥30 will be selected and by the definition in database schema, age is an integer value. After risk assessment, the re-id risk is calculated to be 0.03. Initially, as the data has not been processed yet, the value of IL is 0. When node information is updated, IL=0, re-id risk=0.03, Table Access=E_table, QID=age, and Condition=age≥30 will be recorded in the node information. On the other hand, when the intersection (QL) is empty which means this SQL statement has no risk due to no QID access, we will skip the node Si.


### 2.4. Privacy Tailor

Algorithm2 represents the Privacy Tailor algorithm. After the ECG composer creates the Execution Chain Graph, Privacy Tailor will calculate the re-identification risk and extent of data alteration at the level of the node and record it in the node data. If the risk value is higher than the threshold, Privacy Tailor will first evaluate and analyze each node to estimate re-identification risk and choose the most appropriate data for identification.Algorithm 2:Privacy Tailor algorithm.
(1) Given ECG & Threshold;
(2) main(){
(3)   while(ok==0){   //Set ok = 1 when finish
(4)     recheck=0;
(5)     Node_information=compute(ECG);
//Compute information loss and Re-ID risk
(6)     Re-id_risk=getRisk(Node_information);
(7)    if(Re-id_risk > Threshold){
(8)       target=Find_De-id_target();
(9)       De-id(target);
(10)     recheck=1;
(11)     node=0;
(12)     }
(13)     if(recheck!=1){
(14)      if(node_number == max){
(15)        ok=1; //Reach the last node and end the process
(16)      }
(17)       else{ node_number++; }
(18) }
(19)   }
(20) } // End of main
(21) Find_De-id_target(){
(22)   Compute aggregate risk for each node at each node;
(23)   Choose the highest risk node;
(24)   return node; }However, after knowing the identification information, the re-identification risk value will change. Therefore, the Privacy Tailor must reanalyze based the new information. If the calculated risk value does not exceed the threshold, it proceeds to the next node for analysis. When the re-identification value at each node is below the threshold, the Privacy Tailor completes execution.Continuing the example from Figure2, the Execution Chain Graph can be divided into three levels, node in terms of nodes S1, S2, and S3 (as shown in Figure 3). Using S1 as an example, re-identification of node information shows no value initially. Next, the Privacy Tailor performs an evaluation and fills in the current node information. In node S1, all QIDs belong to E_table, the Age data. It satisfies the Conditions (comparison predicate) restricting the rows returned by the query (e.g., age≥30), as the re-identification risk is 0.03. Thus, de-identification is no required and data distortion is zero. In addition, if risk value is larger than the user-specified threshold, the user specified de-identification method will be used and privacy model classes will be created according to the de-identification file.Figure 3
Privacy Tailor operation.Assume that a user requires access to information stored in the electronic hospital records database. The information in the database may include patients’ age, region, and gender. Based on the user's requirements, Privacy Tailor performs risk assessment. The detailed processes are described as follows.(i)
At node S1, the Privacy Tailor begins evaluation using the QID combination of the chosen table, which is the re-identification risk of the patients’ age. Assuming that the threshold of the privacy policy equals to 2, the re-identification value calculated is 0.03, which is less than the threshold value 0.5. Thus, the Privacy Tailor decides that age is low risk and de-identification is not needed; the IL value is therefore 0.(ii)
After evaluating S1, node S2 is evaluated, which involves calculating the re-identification risk of the combination of age and region (age×region). Supposedly, the result obtained is 0.73, which exceeds the threshold. Therefore, the Privacy Tailor must proceed with de-identification at this level. There are three possible de-identification ways (age, region, and age×region), each associated with re-identification risk and information loss (as shown in Table 1). After calculating the results for the three different de-identification approaches, the Privacy Tailor will choose to perform de-identification on “region” because it has a relatively low re-identification risk and the lowest data distortion level. After finishing this step, the Local re-identification risk will change from 0.73 to the after de-identification risk value 0.23. The Aggregate risk value will union S1 to S2. In other words, it rescans the QIDs in the union of S1 and S2 to obtain an aggregate risk value of 0.24; Local IL equals 30%, and Aggregate IL equals the sum of IL and that for S1, which is 0% plus 30%, equals 30%.(iii)
After finishing the assessment of S2, it will calculate the re-identification risk of the (age×region×sex) combination at S3, and the result obtained is 0.1, which is lower than the threshold value. After rescanning the union of QIDs in the 3 nodes from S1 to S3, the aggregate risk value becomes 0.3 (less than the threshold 0.5). Therefore, the Privacy Tailor will stop de-identification at this level.Table 1
Different cases in re-indemnification process.
Case
Re-indemnification risk
Information loss
Age
0.55
50%
Region
0.23
30%
Age × Region
0.36
70%This example demonstrates that the Privacy Tailor decides whether to perform de-identification based on the risk level, and then locate the optimal QID information combination from different conditions; de-identification is not performed on all QID information. This multilevel method only needs to deal with local information combinations most of the time and therefore can effectively reduce IL value. In addition, it can also identify the high-risk data in a database and help improve privacy safeguards.


## 2.1. Architecture

The HT system architecture consists of two major components: ECG Composer and the Privacy Tailor (as shown in Figure1). ECG Composer compiles the information obtained from users’ requirements and generates the Execution Chain Graph, which is sent to the Privacy Tailor for further processing and risk assessment.Figure 1
HT system architecture.The operation of the ECG Composer is based on information from the following elements.(i)
Database schema: defines the properties of the database, such as the type of the tables in the database and the attributes of the table. From the database schema, the data types of the stored data can be identified.(ii)
Application context: includes components related to SQL query statements, which is performed with the SELECT statement to retrieve a list of columns (including QIDs and other regular data) from one or more queried tables with the optional WHERE clause only returning the rows for which the comparison predicate evaluates to True. These SQL query statements are the details relevant to the user application. The order in which the application accesses QIDs determines which QIDs are analyzed by ECG in different nodes.(iii)
Privacy policy: defines the privacy policy associated with the user or company, such as the thresholdk (k-anonymity) for the QID. The privacy policy is modeled as (U, Q, K, G, and F), for different users (U), the administrator can specify the QID(Q) list, the threshold k (K) to be satisfied for k-anonymity, and the de-identification technique (G). The file (F) of the de-id technique contains the de-id policy where we adopt the taxonomy tree approach described in [14]. The de-identification technique (G) may include Data Reduction, Data Modification, Data Suppression, Pseudonymisation, and Generalization. Each de-identification technique has its own specification which is described in the file (F). For instance, Generalization technique will revise the attributes in a hierarchy manner based on the taxonomy tree structure described in file (F). Take the field “country of origin” as a Generalization technique example. USA and Canada are part of North-America. If they are generalized, both USA and Canada will be represented as North America.Based on user requirements, ECG Composer compiles the information obtained from these components and generates the Execution Chain Graph, which is sent to the Privacy Tailor for further processing and risk assessment.Privacy Tailor is analogous to a privacy management department. Its operation can be described as two stages:(1) risk assessment: executes the risk assessment procedure and estimates the re-identification risk of the current assessment phase. (2) Deidentification: on completing the risk assessment, if the re-identification risk is higher than the threshold, Privacy Tailor identifies the tuples that has relatively high risk and needs to be de-identified. The re-identification risk is calculated as described in [15] (as shown in (1)):
(1)R=1Minj(Fj),
where Fj is the size of an equivalence class.An equivalence class is the set of records in the database which have the same values on all quasi-identifier attributes. When an equivalence classes has the smallest value, we have the highest probability of re-identification and use it as our re-identification risk. As such, the Risk Assessment component will scan the database based on various de-identified QID combinations to find the size for each equivalence class and obtain the re-identification risk.ECG Composer uses the contents of the Database schema provided by the user, the operations defined in Application context, and the privacy policy associated with the user, to generate a series of Execution Chain Graphs and forward them to Privacy Tailor. The Execution Chain Graph will be described in the next section. Both Privacy Tailor and Execution Chain Graph node use a node as their unit and are divided based on several levels of re-identification risk of the QID combination in the required database table. When the re-identification risk is below the privacy policy threshold, no operations are required; Privacy Tailor continues to the next node. When the re-identification value is larger than the privacy policy threshold, identification is performed at that level by comparing the re-identification risk value for different combinations of QID to find the most suitable scheme.


## 2.2. Execution Chain Graph (ECG)

Database access task execution is modeled and structured in various stages aimed at clients in several nodes of database retrievals. As described earlier, the ECG Composer compiles the user requirements, consisting of the Database Schema, Application Context, and Privacy Policy, and then generates the Execution Chain Graph in which each node represents a “stored procedure” that accesses database system, and the directed edge denotes execution sequence (or caller to caller relations). Each stage consists of several atomic “stored procedure” nodes which have a set of associated attributes as follows.(i)
Information loss: the magnitude of the difference between the original database and the database after de-identification.(ii)
Re-identification risk: the possibility of identifying a specific entity directly or indirectly with various de-identified QID combinations.(iii)
Table access: the table name where information is stored and accessed.(iv)
QID: quasi-identifier, which is a subset of attributes that can indirectly identify a specific entity in a table.(v)
Condition: the relevant WHERE clause of the SQL statement is used to extract the records which satisfy a specified criterion.These properties can be further classified as Local and Aggregate. The Local value is the result of evaluating the QID combination of the current node. Aggregate value is the result of adding the evaluation of all QID combinations of all previous nodes.


## 2.3. ECG Composer

This section describes the ECG composer process. The ECG composer requires users to provide relevant data as input. When the system receives data from the admin, it will output an Execution Chain Graph according to requirements, and each node will have a form to record relevant data. The input to ECG composer consists of the Database SchemaΩ; Application Context Ψ; and QID List Γ. Algorithm 1 shows the algorithm of ECG composer, which creates a node set S based on the user’s Application Context. Every node has an associated form that records node information. The order in which the application accesses QIDs determines the execution order which represents a direct edge from Si to its successor, Sj. It will retrieve the specified table, attribute list (AL), and conditions for the data from the Application Context. ECG composer compares the AL with the QID list (QL). If there is an intersection, the QIDs in the intersection will be assessed according to the privacy policy, in the order of application access. In each node, node information will be updated to complete ECG generation.Algorithm 1:ECG composer algorithm.
(1) Given: Database schema Ω; Application Context Ψ;
QID List Γ;
(2) AL: Attribute list;
(3) QL: Target QID list;
(4)S: node set;
//Create ECG
(5)S = Construct the node set from Ψ;
(6) Build the direct edge set for each pair of (Si, Si) based on the order of the QID accesses in Ψ;
(7) For each nodeSi{ //Si∈S (i: number of node);
(8)  Extract the corresponding (Table, AL, Condition);
(9)  QL =∩ AL;
(10)  If (QL != Φ) {
(11)   Update (TABLE, QL, Condition) forSi;
(14)  Assess risk forSi;
(15)  }
(16) }Figure2 shows an example for the operations of ECG composer. Supposedly, we have QID List (Γ= age, region, sex, and education) and Application Context Ψ listed as below:SELECT age FROM E_table WHERE age ≥30,SELECT region FROM E_table WHERE age ≥30,SELECT sex FROM E_table WHERE age ≥30.Figure 2
ECG composer operation.Database Schema defines the data types for age, region, and sex as integer, varchar, varchar, respectively. Based on line 5 and 6 in Algorithm1, ECG composer creates a node set S with 3 nodes (S1, S2, and S3) and connects the 3 nodes. Each node has an empty node information form that specifies information loss, re-id risk, and table access. This is the initial ECG. For each node, ECG executes line 08 statement to extract the (Table, AL, Condition) from Ψ. For example, (E_table, age, age≥30) is extracted from the SQL statement “SELECT age FROM E_table WHERE age ≥ 30” for S1. Next, ECG composer will compute the intersection of the attribute list (e.g., AL=age for S1) and the QID List (Γ = age, region, sex, and education). If the intersection (QL) is not empty then ECG performs two steps (line 11 and line 12) as follows: (1) updates node information form (TABLE, QL, Condition) for Si; and (2) assesses risk for the current node Si locally.In our example, according to the order of application access, the system will assess age, region and sex in S1, S2, and S3 one by one. The assessment is based on the threshold k defined in the input privacy policy. For example, in node S1,  according to SQL statement (SELECT age FROM E_table WHERE age≥30), the age data from E_table satisfying age≥30 will be selected and by the definition in database schema, age is an integer value. After risk assessment, the re-id risk is calculated to be 0.03. Initially, as the data has not been processed yet, the value of IL is 0. When node information is updated, IL=0, re-id risk=0.03, Table Access=E_table, QID=age, and Condition=age≥30 will be recorded in the node information. On the other hand, when the intersection (QL) is empty which means this SQL statement has no risk due to no QID access, we will skip the node Si.


## 2.4. Privacy Tailor

Algorithm2 represents the Privacy Tailor algorithm. After the ECG composer creates the Execution Chain Graph, Privacy Tailor will calculate the re-identification risk and extent of data alteration at the level of the node and record it in the node data. If the risk value is higher than the threshold, Privacy Tailor will first evaluate and analyze each node to estimate re-identification risk and choose the most appropriate data for identification.Algorithm 2:Privacy Tailor algorithm.
(1) Given ECG & Threshold;
(2) main(){
(3)   while(ok==0){   //Set ok = 1 when finish
(4)     recheck=0;
(5)     Node_information=compute(ECG);
//Compute information loss and Re-ID risk
(6)     Re-id_risk=getRisk(Node_information);
(7)    if(Re-id_risk > Threshold){
(8)       target=Find_De-id_target();
(9)       De-id(target);
(10)     recheck=1;
(11)     node=0;
(12)     }
(13)     if(recheck!=1){
(14)      if(node_number == max){
(15)        ok=1; //Reach the last node and end the process
(16)      }
(17)       else{ node_number++; }
(18) }
(19)   }
(20) } // End of main
(21) Find_De-id_target(){
(22)   Compute aggregate risk for each node at each node;
(23)   Choose the highest risk node;
(24)   return node; }However, after knowing the identification information, the re-identification risk value will change. Therefore, the Privacy Tailor must reanalyze based the new information. If the calculated risk value does not exceed the threshold, it proceeds to the next node for analysis. When the re-identification value at each node is below the threshold, the Privacy Tailor completes execution.Continuing the example from Figure2, the Execution Chain Graph can be divided into three levels, node in terms of nodes S1, S2, and S3 (as shown in Figure 3). Using S1 as an example, re-identification of node information shows no value initially. Next, the Privacy Tailor performs an evaluation and fills in the current node information. In node S1, all QIDs belong to E_table, the Age data. It satisfies the Conditions (comparison predicate) restricting the rows returned by the query (e.g., age≥30), as the re-identification risk is 0.03. Thus, de-identification is no required and data distortion is zero. In addition, if risk value is larger than the user-specified threshold, the user specified de-identification method will be used and privacy model classes will be created according to the de-identification file.Figure 3
Privacy Tailor operation.Assume that a user requires access to information stored in the electronic hospital records database. The information in the database may include patients’ age, region, and gender. Based on the user's requirements, Privacy Tailor performs risk assessment. The detailed processes are described as follows.(i)
At node S1, the Privacy Tailor begins evaluation using the QID combination of the chosen table, which is the re-identification risk of the patients’ age. Assuming that the threshold of the privacy policy equals to 2, the re-identification value calculated is 0.03, which is less than the threshold value 0.5. Thus, the Privacy Tailor decides that age is low risk and de-identification is not needed; the IL value is therefore 0.(ii)
After evaluating S1, node S2 is evaluated, which involves calculating the re-identification risk of the combination of age and region (age×region). Supposedly, the result obtained is 0.73, which exceeds the threshold. Therefore, the Privacy Tailor must proceed with de-identification at this level. There are three possible de-identification ways (age, region, and age×region), each associated with re-identification risk and information loss (as shown in Table 1). After calculating the results for the three different de-identification approaches, the Privacy Tailor will choose to perform de-identification on “region” because it has a relatively low re-identification risk and the lowest data distortion level. After finishing this step, the Local re-identification risk will change from 0.73 to the after de-identification risk value 0.23. The Aggregate risk value will union S1 to S2. In other words, it rescans the QIDs in the union of S1 and S2 to obtain an aggregate risk value of 0.24; Local IL equals 30%, and Aggregate IL equals the sum of IL and that for S1, which is 0% plus 30%, equals 30%.(iii)
After finishing the assessment of S2, it will calculate the re-identification risk of the (age×region×sex) combination at S3, and the result obtained is 0.1, which is lower than the threshold value. After rescanning the union of QIDs in the 3 nodes from S1 to S3, the aggregate risk value becomes 0.3 (less than the threshold 0.5). Therefore, the Privacy Tailor will stop de-identification at this level.Table 1
Different cases in re-indemnification process.
Case
Re-indemnification risk
Information loss
Age
0.55
50%
Region
0.23
30%
Age × Region
0.36
70%This example demonstrates that the Privacy Tailor decides whether to perform de-identification based on the risk level, and then locate the optimal QID information combination from different conditions; de-identification is not performed on all QID information. This multilevel method only needs to deal with local information combinations most of the time and therefore can effectively reduce IL value. In addition, it can also identify the high-risk data in a database and help improve privacy safeguards.


## 3. Simulation and Results

This section presents a discussion of the experiments performed. The environment developed in C language is used to simulate the workflow of the HT system. We used two datasets in the experiment. The first dataset is sourced from the Microdata (demodata.asl) and Macrodata (demodata.rda) ofμ-Argus [16], and is called Dataset 1 (shown with solid lines). The second dataset is sourced from the adult data set of the UCI Machine Learning Repository [17], and is called Dataset 2 (shown using dashed lines). Under the considerations of the re-identification risk threshold between k=2 and k=15, the target attributes are age, address, and income.Based on assumptions above, the ECG composer outputs an Execution Chain Graph with accessing three QID attributes: age, address, and income. In each node, the Privacy Tailor assesses whether the re-identification risk is higher than the threshold. If the risk is within an acceptable range, the information will be passed to the next node without de-identifying the attribute. In our experiment, the risk values assessed in node one and node two are lower than the threshold, while the node three assessment result is higher than the threshold. Therefore, an appropriate de-identification method combination is required.Firstly, the risk of each de-identification combination of the attributes needs to be assessed. There are seven possible de-identification combinations: address, age, income,address×age, age×income, address×income, and address×age×income. When the risk values of all nodes are lower than the threshold, we perform data de-identification with only some of the attributes, which result in low information distortion. The following paragraphs present the results plotted from the experiments. The HT system uses the same de-identification techniques as μ-Argus. With the same re-identification risk threshold (k), we compared the distortion levels between de-identifying with the optimal combination of HT and de-identifying with the entire dataset of μ-Argus. The distortion level is represented by Modification Rate (MR) and Extended Bias In Mean (EBIM).


### 3.1. Modification Rate

MR represents the distortion level based on the amount of data being modified. The idea here is that when executing a de-identification procedure, a portion of the data is modified, which causes data distortion. Equation (2) is to calculate the ratio between the numbers of modified attributes and the total attribute numbers.
(2)MR=NANT,
where NA is the number of modified attributes of a dataset, and NT is the total number of attributes in the dataset.Figure4 demonstrates the MR of both the HT system and the μ-Argus system. The x-axis represents the re-identification risk k, and the y-axis represents the MR of the de-identified dataset. As shown in the figure, for Dataset 1, the amount of data that needs to be modified is 65% and 95% for the HT system and μ-Argus system, respectively. According to (2), the distortion level is determined by the amount of data that is modified. Thus, the distortion level of the HT system is 30% lower than that of the μ-Argus system. For Dataset 2, we find that when k=2, the amount of data that needs to be modified is 28% and 70% for the HT system and μ-Argus system, respectively. As the threshold increases, a larger part of dataset needs to be modified, and our system maintains a relatively low-distortion level. Even when k=4, the MR of HT system increases, but remains lower than μ-Argus. Therefore, in terms of MR, the HT system is superior.Figure 4
Data distortion analysis on Modification rate.


### 3.2. Extended Bias in Mean

EBIM extends the Bias In Mean (BIM) method, proposed by Li and Sarkar [18], to calculate the difference between the modified dataset and the original dataset. As BIM is only suitable for calculating the difference of single attribute between the modified dataset and the original dataset, the EBIM improved the BIM method to calculate the average of the difference for all attribute fields, before and after modification. To clearly indicate the information loss, we used an extended BIM (EBIM) to accommodate for the generalization strategy. Assuming the interval where the attribute (X) resides is known, the range R≤L, X, U> where U is the upper bound value; L is the lower bound value; X is the original value. The EBIM formula is given in (3) where j represents the index of the attributes and i represents the index of data entry.
(3)EBIM=1NT∑i=1NT∑j=1NA(U-LXi,j),
where NA is the total attribute numbers of a dataset; NT is the total number of data entries.As shown in Figure5, it shows the comparison of the distortion level by EBIM between the HT system and μ-Argus system. The x-axis is the re-identification risk threshold (k). The y-axis represents the EBIM distortion level. Figure 5, presents that the HT system outperforms the μ-Argus system in all scenarios. In Dataset 1, the distortion rate increases as the threshold increases. When k=4, the distortion increases due to the higher level of de-identification required. However, the HT system still manages a lower-distortion level than μ-Argus does. After the previous de-identification is processed, no additional de-identification is required between k=4 and k=12 in Dataset 1 (i.e., remaining the same EBIM results). When k=13 in Dataset 1, both systems should further de-identify data and yielded higher distortion levels. Moreover, in Dataset 2, HT system is able to maintain a lower-distortion level than μ-Argus. Further, no additional de-identification is required beyond k=4 in Dataset 2. Based on both datasets, the HT system produced a comparatively lower-distortion level.Figure 5
Data distortion on Extended Bias in Mean.


## 3.1. Modification Rate

MR represents the distortion level based on the amount of data being modified. The idea here is that when executing a de-identification procedure, a portion of the data is modified, which causes data distortion. Equation (2) is to calculate the ratio between the numbers of modified attributes and the total attribute numbers.
(2)MR=NANT,
where NA is the number of modified attributes of a dataset, and NT is the total number of attributes in the dataset.Figure4 demonstrates the MR of both the HT system and the μ-Argus system. The x-axis represents the re-identification risk k, and the y-axis represents the MR of the de-identified dataset. As shown in the figure, for Dataset 1, the amount of data that needs to be modified is 65% and 95% for the HT system and μ-Argus system, respectively. According to (2), the distortion level is determined by the amount of data that is modified. Thus, the distortion level of the HT system is 30% lower than that of the μ-Argus system. For Dataset 2, we find that when k=2, the amount of data that needs to be modified is 28% and 70% for the HT system and μ-Argus system, respectively. As the threshold increases, a larger part of dataset needs to be modified, and our system maintains a relatively low-distortion level. Even when k=4, the MR of HT system increases, but remains lower than μ-Argus. Therefore, in terms of MR, the HT system is superior.Figure 4
Data distortion analysis on Modification rate.


## 3.2. Extended Bias in Mean

EBIM extends the Bias In Mean (BIM) method, proposed by Li and Sarkar [18], to calculate the difference between the modified dataset and the original dataset. As BIM is only suitable for calculating the difference of single attribute between the modified dataset and the original dataset, the EBIM improved the BIM method to calculate the average of the difference for all attribute fields, before and after modification. To clearly indicate the information loss, we used an extended BIM (EBIM) to accommodate for the generalization strategy. Assuming the interval where the attribute (X) resides is known, the range R≤L, X, U> where U is the upper bound value; L is the lower bound value; X is the original value. The EBIM formula is given in (3) where j represents the index of the attributes and i represents the index of data entry.
(3)EBIM=1NT∑i=1NT∑j=1NA(U-LXi,j),
where NA is the total attribute numbers of a dataset; NT is the total number of data entries.As shown in Figure5, it shows the comparison of the distortion level by EBIM between the HT system and μ-Argus system. The x-axis is the re-identification risk threshold (k). The y-axis represents the EBIM distortion level. Figure 5, presents that the HT system outperforms the μ-Argus system in all scenarios. In Dataset 1, the distortion rate increases as the threshold increases. When k=4, the distortion increases due to the higher level of de-identification required. However, the HT system still manages a lower-distortion level than μ-Argus does. After the previous de-identification is processed, no additional de-identification is required between k=4 and k=12 in Dataset 1 (i.e., remaining the same EBIM results). When k=13 in Dataset 1, both systems should further de-identify data and yielded higher distortion levels. Moreover, in Dataset 2, HT system is able to maintain a lower-distortion level than μ-Argus. Further, no additional de-identification is required beyond k=4 in Dataset 2. Based on both datasets, the HT system produced a comparatively lower-distortion level.Figure 5
Data distortion on Extended Bias in Mean.


## 4. Conclusion and Future Work

Safeguarding privacy has received increased attention from the public. Using personal information, we may be able to identify a particular person directly or indirectly. Traditional methods, which perform de-identification on the entire database, can reduce the re-identification risk and protect private information, but they cannot provide authentic information to researchers. Based on experimental results, this paper proposes the HT system, which maintains a low re-identification risk in the required area, but is still able to effectively reduce the level of information loss and satisfy the needs of medical and research groups, and identify the information with high risk. HT system enables administrators to completely customize a privacy-preserved database system for eHealth applications and ensure that all service requests are managed in a consistent and reliable manner. In future work, we will satisfy l-diversity requirement [19] to ensure that sensitive attribute values in each equivalence class are sufficiently diverse in order to make the HT system have more practical privacy protection.



---

*Source: 521267-2012-08-30.xml*