mukul975/privacy-data-protection-skills

hipaa-research-privacy

- Implements HIPAA Privacy Rule requirements for research uses of protected health information under 45 CFR §164.512(i).

Ver código-fonte

Como usar

  1. Copie o comando e verifique o pacote antes de instalar no seu ambiente de agente.
  2. Consulte no original as ferramentas, credenciais e ambientes necessários.
  3. Descreva os dados de entrada e a entrega esperada; confira a saída com as fontes.
npx skills add https://github.com/mukul975/privacy-data-protection-skills --skill hipaa-research-privacy

Antes de começar

  • A instalação não inclui assinatura de modelo, franquia API ou acesso aos seus arquivos.
  • Estrelas e instalações indicam atividade, não um teste independente de qualidade ou segurança.
Documento original do Skill

Renderizado do repositório de origem, preservando títulos, exemplos, código, tabelas, links e imagens.

HIPAA Research Privacy — 45 CFR §164.512(i)

Overview

The HIPAA Privacy Rule permits covered entities to use and disclose PHI for research purposes through several pathways. The primary mechanisms are: (1) individual authorization under §164.508, (2) waiver or alteration of authorization by an IRB or Privacy Board under §164.512(i), (3) use of a limited data set with a data use agreement under §164.514(e), (4) use of de-identified data under §164.514(a)-(b), (5) preparatory to research reviews under §164.512(i)(1)(ii), and (6) research on decedent information under §164.512(i)(1)(iii). Researchers and covered entities must understand the interplay between HIPAA and the Common Rule (45 CFR Part 46) which governs human subjects research independently.

Regulatory Framework

Authorization for Research — §164.508

  • §164.508(a): A covered entity may not use or disclose PHI without an authorization that satisfies §164.508 requirements, except as otherwise permitted
  • §164.508(b)(3): Research-specific authorization elements:
  • May describe the PHI to be used or disclosed in a specific or general manner if adequate to allow the individual to understand the PHI to be used/disclosed
  • May be for use/disclosure of PHI for a specific research study, or for future unspecified research if the authorization adequately describes the purposes
  • No expiration date required if the authorization states "end of the research study" or "none" or similar language

Waiver of Authorization — §164.512(i)(1)(i)

A covered entity may use or disclose PHI for research without authorization if the covered entity obtains documentation that an IRB or Privacy Board has approved a waiver (or alteration) of authorization meeting ALL of the following criteria:

  1. The use or disclosure involves no more than a minimal risk to the privacy of individuals based on:
  • An adequate plan to protect the identifiers from improper use and disclosure
  • An adequate plan to destroy the identifiers at the earliest opportunity consistent with the research (unless there is a health or research justification for retaining them, or retention is required by law)
  • Adequate written assurances that the PHI will not be reused or disclosed to any other person or entity except as required by law, for authorized oversight of the research, or for other research for which the use or disclosure would be permitted
  1. The research could not practicably be conducted without the waiver or alteration
  1. The research could not practicably be conducted without access to and use of the PHI

Limited Data Set — §164.514(e)

A limited data set excludes the 16 direct identifiers listed in §164.514(e)(2) but may include:

  • Dates (admission, discharge, birth, death, service)
  • City, state, five-digit ZIP code
  • Ages (including ages over 89 if not aggregated into a 90+ category)

A data use agreement (DUA) is required specifying:

  • Permitted uses and disclosures
  • Who may use or receive the limited data set
  • Prohibition on re-identification or contacting individuals
  • Adequate safeguards commitments
  • Reporting of violations

Preparatory to Research — §164.512(i)(1)(ii)

A covered entity may use or disclose PHI for reviews preparatory to research if the covered entity obtains representations that:

  1. Use or disclosure is sought solely to review PHI as necessary to prepare a research protocol or for similar purposes preparatory to research
  2. No PHI will be removed from the covered entity during the review
  3. The PHI is necessary for the research purposes

Decedent Research — §164.512(i)(1)(iii)

A covered entity may use or disclose PHI of a decedent for research if:

  1. The covered entity obtains representation that use/disclosure is solely for research on the PHI of decedents
  2. The PHI sought is necessary for the research
  3. Documentation of the death (upon request) is provided

HIPAA vs. Common Rule

RequirementHIPAA Privacy RuleCommon Rule (45 CFR Part 46)
GovernsUses/disclosures of PHI by covered entities and BAsProtection of human research subjects
Enforced byOCR (HHS)OHRP (HHS) and institutional IRBs
Authorization/ConsentHIPAA authorization (§164.508)Informed consent (§46.116)
WaiverIRB/Privacy Board waiver of authorization (§164.512(i))IRB waiver of informed consent (§46.116(f))
De-identification18-identifier Safe Harbor or Expert DeterminationNot a substitute for IRB review
Applies toPHI held by covered entities and BAsAll human subjects research at institutions receiving federal funding
OverlapBoth may apply to same study — dual compliance requiredBoth may apply to same study — dual compliance required

Enforcement Examples

  • Lurie Children's Hospital (2024, $3.45M): Although primarily a cybersecurity settlement, OCR noted that research data containing PHI was among the compromised records, underscoring the obligation to secure research PHI
  • Memorial Sloan Kettering (NYS AG, 2023): State enforcement for insufficient research consent practices related to genetic data sharing with third parties
  • University of Mississippi Medical Center (2016, $2.75M): OCR found systemic failure in risk analysis and access controls affecting research data repositories

Integration Points

  • hipaa-privacy-rule: Research uses and disclosures are governed by the Privacy Rule
  • hipaa-deidentification: De-identification eliminates HIPAA restrictions on research use
  • hipaa-minimum-necessary: Minimum necessary applies to research disclosures under waiver (not to individual access or authorized disclosures)
  • hipaa-baa-management: Research collaborators may be BAs if they create, receive, maintain, or transmit PHI
  • hipaa-breach-notification: Research data breaches trigger the same notification obligations

Relacionados por tarefa

do mesmo repositório

Mais Skills

Todos os Skills
mukul975
Comunidade

applying-privacy-design-patterns

- Systematic application of the eight privacy design patterns per Hoepman: minimize, hide, separate, abstract, inform, control, enforce, and demonstrate. Covers pattern selection methodology per processing activity, mapping to GDPR principles, and practical implementation guidance for privacy-by-design system architecture.

instalações
1
GitHub Stars
315
Atualizado
16 de mar.
mukul975
Comunidade

brazil-lgpd

- Guides compliance with Brazil's Lei Geral de Proteção de Dados (LGPD, Lei 13.709/2018). Covers the 10 lawful bases under Art. 7, DPO appointment, ANPD enforcement, data subject rights under Arts. 17-22, and international transfer mechanisms. Keywords: LGPD, Brazil data protection, ANPD, lawful bases, data subject rights, international transfers.

instalações
1
GitHub Stars
315
Atualizado
16 de mar.
mukul975
Comunidade

adequacy-assessment

- Guides assessment of third-country adequacy decisions under GDPR Article 45 for international data transfers. Covers the current EC adequacy decisions list, adequacy assessment criteria, partial adequacy handling, and monitoring of adequacy decision reviews. Keywords: adequacy decision, Article 45, third country, adequate protection, EC adequacy list.

instalações
1
GitHub Stars
295
Atualizado
16 de mar.
mukul975
Comunidade

age-gating-services

- Implements age-gating mechanisms for online services to restrict access based on user age. Covers hard gates versus soft gates, neutral age prompts, re-verification triggers, circumvention prevention, and regulatory requirements under GDPR, COPPA, UK Online Safety Act, and DSA. Keywords: age gate, age restriction, neutral prompt, children, online services, access control.

instalações
1
GitHub Stars
295
Atualizado
16 de mar.