Genetic Data Sharing Policy Template for HIPAA-Compliant Hospital Biobank Programs

Kevin Henry

HIPAA

Published Updated

10 minutes read
Share this article
Genetic Data Sharing Policy Template for HIPAA-Compliant Hospital Biobank Programs

What should a hospital biobank genetic data sharing policy include?

A hospital biobank policy should explain what data and specimens the program holds, who may request them, which reviews and permissions are required, and how approved sharing is controlled. Define whether the policy covers genomic data, clinical records, biospecimens, linked datasets, derived information, and data shared with external researchers.

Start by defining the program’s scope and responsibilities. Name the offices or roles responsible for reviewing requests, confirming the applicable legal basis, releasing data or specimens, monitoring recipient compliance, and responding to incidents. Make clear that HIPAA applies to protected health information (PHI) handled by covered entities and business associates, while information that meets HIPAA’s de-identification standard is treated differently under the Privacy Rule. See the HHS guidance on HIPAA and research.

The policy should establish a consistent review process, including the required application materials, review criteria, approval records, permitted data elements, access period, retention or destruction requirements, and procedures for renewal or changes to an approved project. It should also require review of applicable institutional policies and other laws alongside the HIPAA Privacy Rule.

  • Specify permitted research purposes, users, and data-access levels.
  • Identify the documentation needed for authorization, an IRB or Privacy Board waiver, de-identification, or a limited data set data use agreement.
  • Set rules for secure access, onward sharing, incident reporting, and project closeout.
  • Explain how consent limits, withdrawal requests, and requests to return or destroy specimens are handled.

How do HIPAA authorization and IRB or Privacy Board waivers apply to research sharing?

When a hospital covered entity uses or discloses PHI for research, it generally needs a valid HIPAA authorization unless a permitted Privacy Rule pathway applies. The options include an authorization that meets the requirements of the Privacy Rule, an applicable IRB waiver of authorization or Privacy Board waiver, or another permitted route such as disclosure of a limited data set under a data use agreement. The HHS HIPAA and Research guidance describes these research pathways.

An IRB or Privacy Board may approve a waiver or alteration of authorization only when the required criteria are met. These include a finding that the PHI use or disclosure involves no more than minimal privacy risk, that the research could not practicably be conducted without the waiver or alteration, and that it could not practicably be conducted without access to the PHI. The minimal-risk finding also requires an adequate plan to protect identifiers, destroy them at the earliest appropriate opportunity unless retention is justified, and prevent unauthorized reuse or disclosure. The covered entity must keep the required documentation of the approval.

Do not treat an IRB waiver of informed consent under human-subject research rules as automatically satisfying HIPAA’s separate authorization requirements. The two reviews address different requirements; where both apply, the institution must meet both. HHS explains that HIPAA requires documentation of an authorization waiver from either an IRB or a Privacy Board, not both, in its authorizations FAQs.

A policy should require staff to verify that the approval or authorization covers the actual data, recipient, purpose, and proposed sharing. HIPAA authorizations may cover future research when they describe the future research purposes well enough that the individual could reasonably expect the information to be used or disclosed for those purposes, according to HHS research guidance.

How can a biobank distinguish de-identified data from a limited data set?

HIPAA recognizes two methods for determining that health information is de-identified: the Safe Harbor de-identification method and the Expert Determination method. Under Safe Harbor, specified identifiers must be removed, including most geographic subdivisions smaller than a state and all date elements directly related to an individual except the year, subject to the rule’s stated exceptions. Under the Expert Determination method, a qualified person applies generally accepted statistical and scientific methods, determines that the risk of identification is very small for the anticipated recipient, and documents the methods and results. These standards are set out in 45 CFR § 164.514 and explained in HHS de-identification guidance.

A limited data set is different: it remains PHI under HIPAA, but the covered entity removes specified direct identifiers and may retain some information that Safe Harbor does not permit, including dates and certain geographic details. A covered entity may disclose a limited data set for research, public health, or health care operations only with the required data use agreement. The distinction matters because a limited data set is not the same as HIPAA-de-identified information. See 45 CFR § 164.514 and the HHS limited data set FAQs.

For each proposed release, document which category applies and why. Record the de-identification method and its supporting documentation, or confirm that the proposed limited data set excludes the required identifiers and has an executed agreement. Avoid describing a limited data set as “anonymous” or “de-identified.”

Use clear language to describe what the biobank collects and stores, how genetic and associated health information may be used, which types of researchers may receive access, and whether access may occur through a controlled repository or another approved model. Explain whether future studies may include broad areas of genetic or health research, and disclose any limits on the biobank’s ability to predict every future project.

Research consent and HIPAA authorization are related but distinct. A consent form may be combined with a HIPAA research authorization when the authorization meets the Privacy Rule’s requirements; simply obtaining voluntary consent does not, by itself, authorize a PHI disclosure when HIPAA authorization is required. HHS describes this distinction in its guidance on consent and authorization and explains when research documents may be combined in 45 CFR § 164.508.

Disclosures should also address privacy limits specific to genetic information. Explain that sharing genomic data may carry a risk of re-identification, including through linkage with other information, and that safeguards reduce but cannot promise to eliminate that risk. The National Human Genome Research Institute’s privacy guidance discusses these concerns and the use of access controls for sensitive genomic data.

Ready to simplify HIPAA compliance?

Join thousands of organizations that trust Accountable to manage their compliance needs.

Get Started Free Today

How should access requests, honest brokers, and data use agreements be governed?

Require researchers to submit a defined project purpose, requested data and specimens, proposed analyses, access duration, data security plan, and any applicable ethics or regulatory approvals. A designated review group should check whether the request fits the participant’s permissions, the approved research purpose, and the data-sharing pathway. Document the decision and release only the approved information.

An honest-broker system can separate identifying information from research data: a designated broker holds or manages the linkage key and releases coded or otherwise approved data to researchers. Define the broker’s authority, access restrictions, documentation duties, and rules for any re-linking. An honest broker is an internal governance safeguard, not a substitute for HIPAA authorization, a waiver, de-identification, or another valid disclosure pathway.

When sharing a limited data set, the limited data set data use agreement must define permitted uses and recipients, require appropriate safeguards, prohibit uses or disclosures outside the agreement or otherwise permitted by law, require reporting of impermissible uses or disclosures, bind agents and subcontractors to the same restrictions, and prohibit identifying or contacting individuals. These requirements appear in 45 CFR § 164.514(e). The policy should also set a process for responding to violations, including suspending access or ending the agreement when warranted.

What safeguards reduce genetic data re-identification risks?

Do not assume that removing names alone eliminates genetic privacy risk. Genomic information can create re-identification concerns, particularly when combined with other available information. The National Human Genome Research Institute’s overview of privacy in genomics explains why genomic data sharing requires attention to both privacy risk and access controls.

Use safeguards that match the data and the release model. Consider role-based access, secure computing environments, identity verification, audit logs, controls on downloading or onward sharing, and review of potentially identifying combinations of data elements. For electronic PHI, the HIPAA Security Rule requires appropriate administrative, physical, and technical safeguards; covered entities should select and assess measures through their security program and risk analysis. See the HHS summary of the Security Rule.

Require recipients to use data only for approved purposes and not to attempt re-identification or contact participants, except where a specific, lawful and approved process permits it. Review releases for rare conditions, small populations, detailed dates or locations, and combinations of genetic and clinical variables that could increase risk. The HHS de-identification guidance notes that identification risk depends on the information, the anticipated recipient, and other reasonably available information.

What limitations should the policy disclose about withdrawal and downstream sharing?

Explain how participants can withdraw from future participation or revoke a HIPAA authorization, who should receive the request, and what changes the biobank can make after receiving it. Under HIPAA, revocation of an authorization must be in writing and does not undo actions already taken in reliance on a valid authorization. HHS describes these limits in its guidance on revoking authorization.

Clarify that withdrawal may stop future collection or new disclosures but may not make it possible to retrieve information already distributed to researchers or incorporated into analyses. For PHI already obtained under an authorization, continued use or disclosure may be permitted to the extent necessary to preserve research integrity under the applicable reliance exception. Explain separately how the program handles stored specimens, coded data, and information that has already been included in completed or ongoing research. See the HHS FAQ on research after authorization is revoked.

Set expectations for downstream sharing: identify whether approved recipients may share data with collaborators, what additional review or agreements are required, and whether previously shared material can be recalled or destroyed. State that withdrawal cannot guarantee retrieval of data already shared or complete removal of information from research results. A clear policy links each sharing decision to the relevant permission, review, and safeguard, while candidly explaining the limits of withdrawal and de-identification.

FAQs

Does sharing genetic data for research always require HIPAA authorization?

No. Authorization is not always required. Depending on the facts, a covered entity may use or disclose HIPAA-de-identified information, share a limited data set under a compliant data use agreement, or rely on a documented IRB or Privacy Board waiver or another permitted Privacy Rule pathway. The biobank should determine and document which pathway applies before sharing. See HHS HIPAA and Research guidance.

Can a hospital biobank share a limited data set without removing all dates?

Yes. A limited data set may retain dates, unlike Safe Harbor de-identification, provided the covered entity removes the identifiers required for a limited data set and obtains a compliant data use agreement. A limited data set remains PHI. See 45 CFR § 164.514.

Does HIPAA de-identification eliminate genetic re-identification risk?

No. HIPAA de-identification establishes a regulatory standard for treating health information as not individually identifiable under the Privacy Rule; it does not guarantee that genetic information carries no re-identification risk. A biobank should use appropriate safeguards and explain the residual privacy risk to participants. See the HHS de-identification guidance and the NHGRI privacy guidance.

What should a biobank data use agreement prohibit?

For a limited data set, the agreement must prohibit uses or disclosures outside the agreed purposes or those otherwise permitted by law, and it must prohibit recipients from identifying or contacting individuals. It should also require safeguards, reporting of impermissible uses or disclosures, and equivalent restrictions for agents or subcontractors. See 45 CFR § 164.514(e).

Share this article

Ready to simplify HIPAA compliance?

Join thousands of organizations that trust Accountable to manage their compliance needs.

Get Started Free Today

Related Articles