How Does HIPAA Expert Determination Work in Practice?
HIPAA Expert Determination is a documented process in which a qualified expert evaluates a proposed disclosure of health information, measures the potential for individuals to be identified, applies appropriate data transformations, and determines whether the remaining identification risk is very small. The process is specific to the data and circumstances being assessed rather than a certification that a source database is permanently deidentified. The expert therefore needs to understand the dataset, relevant population, proposed recipient, release environment, external information available for matching, and effect of any controls surrounding the disclosure.
The HIPAA Privacy Rule does not prescribe one statistical methodology that every expert must follow. This allows different methods to be used for different datasets, but it also places responsibility on the expert to document the methods and results supporting the determination.
Expert Determination Starts With the Proposed Disclosure
The analysis needs to begin with the information that the organization intends to disclose. The relevant question is not whether the organization’s entire database can be described as deidentified.
A healthcare organization can maintain identifiable source information and create a transformed version for a particular disclosure. The expert assesses the information that the intended recipient will receive rather than assigning a general status to every record held by the organization.
This distinction allows the same source records to support different disclosures. Different variables can be retained, generalized, suppressed, or modified according to the purpose and environment of each release.
The Relevant Population Affects Identification Risk
Identification risk depends partly on the population from which the records originate. A combination of characteristics that describes thousands of people nationally can describe only a few people within a smaller geographic or demographic population.
The relevant population therefore needs to correspond with the circumstances surrounding the dataset. A record concerning a 75-year-old woman can provide little identifying information in a national dataset but become more distinguishing when the population is restricted to residents of a small community.
Population size also affects decisions about generalization and suppression. Categories that work for a densely populated area might provide insufficient protection for a rural population containing relatively few people with the same characteristics.
Quasi-Identifiers Need to Be Identified
Direct identifiers such as names and medical record numbers provide an obvious route to identification. Expert Determination also needs to examine quasi-identifiers that can contribute to identification when combined.
Age, sex, geography, occupation, dates, diagnoses, procedures, and demographic characteristics can function as quasi-identifiers depending on the dataset. None needs to identify a person independently.
The concern is the combination. Several ordinary characteristics can progressively reduce the number of possible people until a record becomes distinguishable from the surrounding population.
External Information Forms Part of the Assessment
The information available outside the medical dataset affects whether quasi-identifiers can realistically be used to identify somebody. Expert Determination therefore extends beyond examining the fields contained in the healthcare organization’s file.
Public records, commercial databases, social media, news reports, leaked datasets, and other sources can provide identified information for comparison. The relevant sources depend on the information contained in the medical dataset and the anticipated recipient.
The analysis does not require the assumption that every conceivable database exists or is available to every person. The expert considers information that is reasonably available within the circumstances being assessed.
Geography Can Change the External Data Environment
External information is not equally available in every jurisdiction. Public access to voter registration information, property information, vital records, and other government data can differ according to state and local rules.
The same fields can therefore create different practical linkage opportunities depending on where the individuals represented by the data live. A combination that can readily be compared with an identified public dataset in one jurisdiction might be difficult to reproduce elsewhere.
This geographic difference is another reason a deidentification analysis should reflect the actual population and release environment rather than relying solely on a fixed list of fields.
Transformations Should Address the Identified Risk
Data transformations should correspond with the characteristics producing the identification risk. The objective is not to alter information merely because a transformation technique is available.
If exact age creates excessive distinguishability, age can be generalized. If a rare value isolates a small number of records, that value can be suppressed. If exact individual values are unnecessary but population-level statistical properties need to be preserved, perturbation can provide another option.
Several techniques can be applied within the same dataset. Different fields can require different treatment because they contribute differently to identification risk.
Generalization Can Be Adapted to the Population
Generalization does not require every record to use identical category widths established for convenience. Categories can reflect the distribution of the population.
Age provides an example. Narrower age ranges can be appropriate where many people occupy each category. Older ages can require wider ranges when fewer people are represented.
The same principle can apply to geography and other variables. The objective is to retain useful information while preventing precise combinations from making individuals excessively distinguishable.
Transformations Can Create New Disclosure Problems
A transformation can reduce one identification pathway while creating another. Selectively suppressing unusual information can signal that the missing value itself is unusual.
Relationships between variables can also reveal suppressed information. If a diagnosis is removed but a procedure is strongly associated with that diagnosis, the remaining field can allow the recipient to infer what was removed.
Aggregate tables can produce another form of inference. Suppressing one small cell can provide little protection when published totals and neighboring cells allow the missing number to be calculated.
Data Utility Forms Part of the Transformation Decision
A transformation that removes identification risk can also remove information required for the intended analysis. Deidentification therefore involves evaluating what happens to data utility when information is suppressed, generalized, or modified.
Removing precise dates can prevent certain longitudinal analyses. Broad geographic categories can interfere with local population studies. Generalizing age can prevent analysis requiring precise age differences.
The transformations selected for one research purpose can therefore differ from those selected for another purpose using the same source records.
The Expert Can Iterate the Analysis
The first transformed dataset does not need to produce the final result. Expert Determination can operate as an iterative process.
The expert can measure the initial risk, identify the records or characteristics responsible for unacceptable results, specify transformations, and measure the resulting information again. Further changes can be made when the transformed information remains above the selected threshold.
This process allows transformations to be directed at measured risks rather than applying broad changes to every variable before the risk has been assessed.
Verification Needs to Examine the Actual Output
The final assessment needs to correspond with the information that will actually be disclosed. A technically sound transformation specification does not establish that the production dataset was transformed correctly.
Implementation errors can leave fields unchanged, apply incorrect categories, omit records from suppression logic, or introduce information that was not present in the version originally assessed.
Verification therefore connects the expert’s methodology with the actual release. The determination should relate to the transformed output rather than an unimplemented transformation plan.
Changing One Field Can Affect the Complete Risk Profile
Adding or removing a field can change the identification risk created by other fields because distinguishability is based on combinations. A new variable can separate records that previously belonged to larger groups.
This means a healthcare organization should not assume that an approved dataset remains covered by the same analysis after additional information is added. Even a field that appears ordinary can create a new combination when joined with existing variables.
Changes to a data extraction process can create the same problem. A recurring report can retain the same name while its contents change because the underlying software begins populating additional fields.
Continuous Data Accumulation Can Increase Distinguishability
Longitudinal healthcare information can become more distinctive as additional observations accumulate. One diagnosis or procedure can be shared by many patients, while a long sequence of diagnoses, procedures, dates, and encounters can describe a much smaller group.
This creates a particular issue for continuous data feeds. A risk assessment performed when the feed contains a limited history might not represent the risk after substantially more information has accumulated.
Repeated deidentification therefore needs to account for changes in the richness of each patient’s record rather than examining only whether the same fields continue to be transmitted.
New External Data Can Change an Existing Risk Assessment
The healthcare dataset does not need to change for reidentification risk to change. New information can become available outside the organization.
A new public database, commercial dataset, data breach, or online service can create a linkage source that did not exist when the original assessment was performed. Technical developments can also make large-scale matching easier.
This is one reason an Expert Determination can require later review even when the original released fields remain unchanged.
Different Experts Can Reach Different Conclusions
Expert Determination contains professional judgment because HIPAA does not prescribe a single numerical threshold or statistical method. Qualified experts can therefore make different methodological choices while working within the same regulatory standard.
Differences can involve the selected risk threshold, relevant population, assumptions about external information, treatment of particular variables, and weight assigned to contractual or technical controls.
Documentation provides the basis for evaluating these decisions. The record should explain the methodology and results rather than relying solely on the expert’s statement that the information satisfies the HIPAA standard.
Precedent Can Support the Selected Methodology
Prior statistical work can provide context for selecting risk measures, transformations, and thresholds. Statistical disclosure limitation has been used outside healthcare for decades to address the release of useful information about populations without exposing identifiable information about individuals.
Methods developed for census, demographic, and economic data can therefore inform healthcare deidentification. Their application still needs to account for the characteristics and sensitivity of the medical information being assessed.
The methodology should explain why the selected approach is appropriate for the proposed healthcare data release rather than treating a technique used in another context as automatically applicable.
Expert Determination Documentation Has an Operational Purpose
Documentation allows an organization to understand what information was assessed and the circumstances under which the determination was made. This becomes relevant when the organization later changes the dataset or proposes another disclosure.
The documentation can identify the recipient, relevant population, fields assessed, external information assumptions, statistical methods, transformations, controls, measurements, and conclusion. It can also establish the conditions under which reassessment is required.
Without this record, an organization can have difficulty determining whether a later disclosure remains within the circumstances originally evaluated.
AI Creates a Validation Problem for Unstructured Medical Records
Automated tools can process large volumes of clinical narratives that would be difficult to review manually. Natural language processing and AI systems can identify names, dates, locations, organizations, and other identifying information embedded in clinical text.
The compliance problem concerns what happens when the system misses an identifier. Automated deidentification is rarely assessed by asking whether the software can identify obvious names in a small number of examples.
Validation needs to examine the resulting text and the consequences of errors. The HIPAA guidance does not provide a universal acceptable error percentage for automated removal of identifiers from clinical narratives, leaving the organization and expert to establish a defensible method of assessing the resulting risk.
Some Data Types Resist Conventional Transformation
Conventional deidentification techniques work more readily with variables that can be removed, grouped, or modified without destroying their purpose. Some medical information presents a more difficult relationship between identification risk and utility.
Genomic information provides an example because the sequence itself can distinguish an individual. Transforming the sequence sufficiently to eliminate that characteristic can conflict with the scientific reason for using genomic information.
These circumstances can require greater reliance on the release environment, access restrictions, recipient controls, or alternative data-sharing arrangements rather than expecting field transformation alone to resolve the identification risk.
The Release Environment Can Preserve More Detailed Data
Deidentification does not need to produce one universal version of a dataset suitable for every purpose. The release environment can be changed when transforming the information further would remove data required for legitimate analysis.
A restricted research environment can control who receives access and what users can do with the information. Contractual restrictions can prohibit reidentification and external linkage. Technical controls can restrict copying or exporting information.
A separate version intended for broader distribution can contain greater generalization or suppression. Designing the release environment alongside the data transformation allows privacy risk and analytical utility to be addressed together.
Expert Determination Is Specific to the Data Sharing Arrangement
HIPAA Expert Determination is most accurately treated as an assessment of a defined data disclosure rather than a permanent characteristic attached to a database. The analysis depends on what information will be released, who will receive it, which population the records represent, what other information is reasonably available, and what controls govern the recipient.
The process can involve repeated measurement and transformation until the resulting information reaches the selected risk threshold. Verification then establishes that the dataset intended for release corresponds with the information that was assessed.
Later changes can require another analysis. New fields, richer longitudinal records, different recipients, additional external datasets, altered contractual controls, and new methods of linking information can change identification risk even when an earlier release satisfied the HIPAA standard.
