인터페이스는 현지화되어 있으며, Skill 소개와 설명 문서는 선택한 언어로 AI가 자동 번역합니다. 코드·명령어·경로·전문 용어는 원문을 유지하며 원작자 문서가 우선합니다.
Skills 둘러보기
문서 및 사무 · SKILL.md

hipaa-release-authorization

hipaa-release-authorization

Drafts HIPAA-compliant PHI release authorizations for estate-planning workflows under 45 CFR §164.508. Use when drafting release forms, healthcare POA support documents, or record-access instruments. Triggers: HIPAA release, PHI authorization, healthcare agent access, advance directive support, medical record release.

Independent GitHub snapshot · Automated classification · Original documentation governs

Skill 문서

GitHub

name: hipaa-release-authorization language: en description: >- Drafts HIPAA-compliant PHI release authorizations for estate-planning workflows under 45 CFR §164.508. Use when drafting release forms, healthcare POA support documents, or record-access instruments. Triggers: HIPAA release, PHI authorization, healthcare agent access, advance directive support, medical record release.

HIPAA Release Authorization

Generates a 45 CFR §164.508-compliant authorization permitting designated recipients to access a patient's protected health information (PHI) from covered entities, typically in an estate-planning context.

Quick Start

Gather before drafting:

  1. Jurisdiction — state governs signature and witness/notary formalities
  2. Patient identity — legal name, DOB, contact details
  3. Recipients — healthcare agent, successor agent(s), other representatives
  4. Disclosing entities — providers, hospitals, labs, pharmacies, health plans
  5. PHI scope — all records or limited categories
  6. Purpose and duration — expiration date, event, or condition
  7. Representative authority (if applicable) — POA, guardianship order, court appointment
  8. Related documents — healthcare proxy, advance directive for terminology alignment

Required Sections

Every authorization must include these elements per §164.508:

SectionKey requirement
Patient identificationName, DOB, contact
Authorization statementVoluntary, specific written consent
Authorized recipientsAgent names, roles, relationships — no ambiguity
Disclosing entitiesCovered entities / record holders
PHI scopeExplicit categories; do not mix "all records" with narrow limits
PurposeSpecific estate-planning healthcare decision-making purpose
ExpirationExplicit end date, event, or condition
Required noticesRe-disclosure warning, treatment non-conditioning, right to refuse
RevocationHow and where written revocation is sent; prospective-only effect
Execution blockPatient signature first, then representative if applicable
Witness/notaryOnly where state law requires [VERIFY]

Draft Workflow

  1. Confirm inputs against the Quick Start checklist; flag any gaps.
  2. Select PHI scope — if client wants full-record access, state it unambiguously; otherwise enumerate categories. Sensitive categories (substance use, mental health, genetic, HIV/AIDS) require explicit inclusion [VERIFY].
  3. Draft the form using this structure:
    • Title citing 45 CFR §164.508
    • Patient identification block
    • Authorization statement
    • Disclosers list
    • Recipients list (match names/roles to healthcare POA document)
    • PHI scope with checkbox-style selection
    • Purpose statement tied to healthcare directives
    • Duration clause (date, revocation, or death — whichever first)
    • Patient rights / required statements (all six §164.508 notices)
    • Execution block (patient, then representative if signing on behalf)
    • Witness/notary block if state law applies
  4. Validate — all placeholders visible, recipients consistent across sections, terminology aligns with governing POA/directive.
  5. Add state-specific addendum only when confirmed for target jurisdiction.

Pitfalls

  • Never authorize broader disclosure than needed unless client explicitly requests full-record access.
  • Never leave recipient or discloser fields unidentified.
  • Never leave representative signature fields blank without authority documentation.
  • Federal law is not exclusive — state mandates may impose additional form requirements [VERIFY].
  • Estate-planning variants must match healthcare POA terminology in the core delegation document [VERIFY].
  • Include attorney-review language in cover memo if template is client-facing.
저장한 Skills