Data Use Agreement

Specifies the exact data fields covered by the agreement and the required de-identification methodology. This section defines whether the dataset meets the HIPAA Safe Harbor method (removal of 18 specific identifiers) or the Expert Determination standard. It explicitly lists permitted data elements such as structured diagnosis codes, laboratory results, and imaging metadata while prohibiting the inclusion of direct identifiers like names, medical record numbers, and full ZIP codes.

Defines the specific research purposes for which the data can be utilized, prohibiting repurposing without amendment. This clause binds the recipient to a precise protocol, such as federated cohort discovery for a specific disease phenotype or federated survival analysis for a defined treatment pathway. Any attempt to re-identify individuals, link the data to other datasets without authorization, or use it for commercial product development outside the agreed scope constitutes a material breach.

Mandates the technical safeguards required to protect the dataset from unauthorized access, use, or disclosure. Requirements typically include:

• Encryption at rest and in transit using FIPS 140-2 validated modules
• Role-based access controls limiting data visibility to named investigators
• Audit logging of all data access events
• Prohibition of storage on personally owned devices or unsecured cloud environments

Establishes the terms for disseminating research findings derived from the data. This section balances the provider's interest in confidentiality review with the recipient's academic freedom to publish. It typically grants the data provider a period (e.g., 30 days) to review manuscripts for inadvertent disclosure of proprietary information or potential re-identification risks before submission, while explicitly preventing the provider from blocking publication of unfavorable results.

Defines the agreement's duration and the legally required actions upon expiration or termination. The recipient must certify the irreversible destruction or secure return of the dataset and all derivative copies. This clause often requires a formal written confirmation from the recipient's institutional official, and may specify that the provider retains the right to audit compliance with data disposition obligations.

Allocates risk between the parties in the event of a data security incident or unauthorized use. The recipient assumes liability for its own violations and must agree to immediate notification (often within 24-48 hours) of any suspected breach. This section requires the recipient to cooperate fully with the provider's incident response, forensic analysis, and mandatory reporting obligations to regulatory bodies such as the Office for Civil Rights (OCR).

A stripped-down clinical dataset defined by the HIPAA Privacy Rule that excludes 16 specific direct identifiers of the patient, relatives, employers, or household members. Key characteristics include:

• Retains: Dates of admission, discharge, birth, and death; city, state, and 5-digit ZIP code.
• Excludes: Names, street addresses, phone numbers, social security numbers, and full-face photographs.
• Purpose: An LDS is the specific data object governed by a Data Use Agreement, allowing research without individual authorization.

A neutral intermediary software architecture that de-identifies clinical data before it is released to researchers or federated networks. The honest broker:

• Strips direct identifiers to create a Limited Data Set or fully de-identified data.
• Maintains a secure mapping key to re-identify data if clinically necessary.
• Enforces the terms of the Data Use Agreement by acting as a technical gatekeeper, ensuring only permitted data elements leave the institution's firewall.

An administrative body established to protect the rights and welfare of human research subjects. The IRB reviews research protocols to ensure ethical compliance. In the context of a Data Use Agreement, the IRB often determines whether the proposed use of a Limited Data Set qualifies for an exemption or requires a waiver of authorization, directly influencing the permitted uses specified in the DUA.

A precise de-identification standard requiring the removal of 18 specific identifiers from health data. Unlike a Limited Data Set, Safe Harbor data contains no dates or geographic subdivisions smaller than a state. Data de-identified via this method is no longer considered PHI and is not subject to a Data Use Agreement or HIPAA regulations, making it a preferred format for purely statistical federated queries where temporal precision is not required.

The documented lineage of a dataset that records its origin, transformations, and chain of custody. In federated clinical analytics, robust data provenance is critical for enforcing a Data Use Agreement because it:

• Audits that only approved algorithms touched the data.
• Verifies that data was not re-identified or cross-linked.
• Provides an immutable record for regulatory compliance reporting.