We e-mail the editable toolkit files to the address you gave, usually within 2 to 3 business days.
Data Privacy

What Documents You Need for HIPAA Implementation

What Documents You Need for HIPAA Implementation
In short

A practical checklist of the policies, procedures, records and agreements needed for HIPAA implementation, and how to organise and maintain them.

In this article
  1. Start with the rules your documents must support
  2. Governance and accountability documents
  3. Privacy Rule documents
  4. Security Rule documents
  5. Breach notification and third-party documents
  6. Quick reference: documents and evidence
  7. Common mistakes to avoid
  8. Frequently asked questions

HIPAA does not have a certification scheme, so there is no certificate to aim for. What you do have is a regulator, and in an investigation or audit the first question is usually: "Show me your documentation." If a policy, risk decision or training session is not written down, it is hard to prove it happened.

This article lists the documents most organisations need when implementing HIPAA, whether you are a covered entity or a business associate. Treat it as a working checklist, not legal advice. Your exact set will depend on your size, services and the data you handle.

Start with the rules your documents must support#

HIPAA documentation is organised around three rules:

  • Privacy Rule: how protected health information (PHI) may be used and disclosed, and what rights individuals have.
  • Security Rule: the administrative, physical and technical safeguards for electronic PHI.
  • Breach Notification Rule: how you assess and report incidents involving unsecured PHI.

The rules also require you to keep your policies, procedures and related records in written or electronic form, and to retain them for six years from the date of creation or the date they were last in effect, whichever is later. That retention expectation affects how you version and archive everything below.

Governance and accountability documents#

These show who is responsible and how the programme is run.

  • Privacy and security official designations: a written appointment of the person responsible for each, with their responsibilities.
  • HIPAA compliance policy or programme overview: scope, roles, and how the policies fit together.
  • Sanction policy: consequences for workforce members who violate policies, applied consistently.
  • Complaints procedure: how individuals can raise privacy concerns, and how you record and resolve them.
  • Document control procedure: how policies are approved, versioned, reviewed and retained.

Privacy Rule documents#

These cover how PHI is used and what you owe to patients or members.

  • Notice of Privacy Practices (for covered entities), plus a process for providing it and recording acknowledgment where required.
  • Uses and disclosures policy, including the minimum necessary standard and role-based access to PHI.
  • Authorization forms for disclosures that need patient permission.
  • Individual rights procedures: access to records, amendment requests, restriction requests, confidential communications and accounting of disclosures. Each needs a clear owner, a response process and a log.
  • Marketing, fundraising and research handling rules, if relevant to your activities.
  • Verification and de-identification procedures, if you release or share data in those ways.

Security Rule documents#

This is usually the largest set, and the one where evidence matters most.

Risk analysis and risk management#

  • Risk analysis: an accurate, thorough assessment of risks to the confidentiality, integrity and availability of ePHI. It should cover systems, locations, vendors and data flows.
  • Risk management plan: the decisions and actions taken to reduce those risks, with owners and timelines.
  • Information system activity review procedure: how logs, access reports and incident trails are reviewed, and how often.

Administrative safeguards#

  • Workforce security, onboarding and termination procedures
  • Access authorisation and access management procedures
  • Security awareness and training programme, with training records
  • Security incident response procedure and incident log
  • Contingency plan: data backup, disaster recovery, emergency mode operation, and testing records
  • Periodic evaluation procedure to check that policies still match operations

Physical safeguards#

  • Facility access controls and visitor handling
  • Workstation use and workstation security rules
  • Device and media controls: disposal, re-use, movement and accountability for hardware that holds ePHI

Technical safeguards#

  • Access control policy: unique user IDs, emergency access, automatic logoff
  • Audit controls: what is logged and how logs are protected
  • Integrity controls for ePHI
  • Authentication and transmission security, including encryption decisions

Some Security Rule specifications are "addressable". That does not mean optional. If you do not implement one as written, document why and what equivalent measure you used instead.

Breach notification and third-party documents#

  • Breach assessment and notification procedure: how you decide whether an incident is a reportable breach, who must be notified and within what timeframes.
  • Breach risk assessment template and breach log: a consistent record of each assessment and its outcome.
  • Business associate agreements (BAAs): signed agreements with every vendor that creates, receives, maintains or transmits PHI for you. Business associates also need agreements with their own subcontractors that handle PHI.
  • Vendor inventory and due diligence records: a list of who has PHI, what they do with it, and what you checked before engaging them.

Quick reference: documents and evidence#

AreaCore documentsTypical evidence
GovernanceOfficial designations, sanction policy, complaints procedureAppointment letters, sanction records, complaint log
PrivacyNotice of Privacy Practices, rights procedures, authorization formsRequest logs, signed forms, disclosure accounting
SecurityRisk analysis, risk management plan, safeguard policiesReview reports, access logs, test results
TrainingAwareness programme, role-specific contentAttendance records, completion dates
BreachNotification procedure, assessment templateBreach log, assessments, notifications sent
VendorsBAA template, vendor inventorySigned BAAs, due diligence files

Common mistakes to avoid#

  • Copying generic policies without adapting them. A policy that describes controls you do not operate is a liability, not protection.
  • Treating the risk analysis as a one-off. Update it when systems, vendors, locations or threats change.
  • Missing BAAs. Cloud hosts, billing services, IT support and shredding vendors are often overlooked.
  • No evidence trail. Training happened, but nobody kept the attendance record.
  • Poor version control. You need to show which policy was in force at a given time, for the full retention period.

Frequently asked questions#

Is there a HIPAA certification I can get?#

No. There is no official HIPAA certification. Compliance is shown through your documented programme, your risk analysis, your safeguards in practice and your records. Any third-party assessment is a way to test your readiness, not a government-recognised certificate.

Do business associates need the same documents as covered entities?#

Business associates must comply with the Security Rule and with the parts of the Privacy and Breach Notification Rules that apply to them. They typically do not need a Notice of Privacy Practices, but they do need risk analysis, security policies, training, incident and breach procedures, and BAAs with their own subcontractors.

How long do we need to keep HIPAA documentation?#

Required documentation must be retained for six years from the date it was created or the date it was last in effect, whichever is later. Note that state law or contractual terms may require longer retention for some records, so check your own obligations.

Building this document set from scratch takes time, and a structured starting point helps. The HIPAA Toolkit is a ready-to-use documentation toolkit you can adapt to your own environment. If you want to discuss where to begin, you can contact the AdWiser team. For a comparison with another privacy regime, see What Documents You Need for GDPR Implementation.

Share this guide

Ready to put this into practice?

Start with the HIPAA Toolkit and adapt it to your organisation, or talk to us about implementation support.

Chat on WhatsApp