Skip to content
HIPAA ComplianceConsulting

Documentation Service

HIPAA Policies and Procedures

Policies and procedures that match your real systems and workflows, mapped to HIPAA requirements, with version history and a review cycle built in.

Reviewed Request a HIPAA Consultation

Almost every organization handling PHI has HIPAA policies. Far fewer have policies that describe what they actually do. A template downloaded years ago may reference systems you no longer use, roles that do not exist and procedures nobody follows — and in an investigation, a policy you do not follow can be worse than no policy at all.

We write and revise HIPAA policies and procedures so they reflect your actual environment, satisfy the documentation requirements of the Privacy and Security Rules, and stay maintainable after we leave.

Key points

  • HIPAA requires written policies and procedures under both §164.316 and §164.530(i).
  • Policies must be retained for six years and updated as needed.
  • Procedures should name roles, systems and records — not just restate the rule.
  • Templates are a starting point, never the finished product.

Service overview

This service produces a complete, coherent set of HIPAA policies and procedures, or a revision of the set you already have. Policies state what the organization commits to; procedures describe who does what, in which system, and what record is kept. We write both, mapped to the regulatory requirements they support.

Policy work is most effective when it follows an assessment. A HIPAA gap analysis or security risk analysis tells us which documents are missing and which decisions — particularly on addressable specifications — need to be captured.

Who needs this service

  • Organizations using generic templates that have never been tailored.
  • Startups and SaaS companies writing their first HIPAA documentation for customer due diligence — see HIPAA compliance for startups.
  • Dental, specialty and multi-site practices whose policies predate cloud systems or telehealth.
  • Business associates whose customers require policies consistent with BAA obligations.
  • Organizations that have changed systems, merged or restructured and need a single policy set.

Regulatory considerations

Both core rules require documented policies. The Security Rule (§164.316) requires reasonable and appropriate policies and procedures to comply with the Security Rule, written documentation of required actions and assessments, retention for six years from creation or last effective date, availability to those responsible for implementing them, and periodic review and update. The Privacy Rule (§164.530(i)–(j)) has parallel requirements, including changing policies promptly when the law changes.

Core policy set and related requirements (illustrative, not exhaustive)
Policy areaPrimary citation(s)
Security management, risk analysis and risk management§164.308(a)(1)
Workforce security, access management and sanctions§164.308(a)(1)(ii)(C), (a)(3), (a)(4)
Security awareness and training§164.308(a)(5); §164.530(b)
Security incident procedures and contingency planning§164.308(a)(6), (a)(7)
Facility, workstation and device and media controls§164.310
Access control, audit controls, integrity, authentication, transmission security§164.312
Business associate management§164.308(b), §164.314, §164.504(e)
Uses and disclosures, minimum necessary, verification§164.502, §164.506, §164.508, §164.514
Individual rights§§164.520–164.528
Breach risk assessment and notification§§164.400–164.414
Documentation and retention§164.316; §164.530(j)

Common policy challenges

  • Templates naming systems, roles or locations that do not exist in your organization.
  • Policies that restate the regulation but never say who does what.
  • No version history, so prior versions cannot be produced for the six-year retention period.
  • Separate privacy and security documents that contradict each other.
  • Breach procedures that omit business associate notification timing or HHS reporting thresholds.
  • No annual or event-driven review, so documents fall out of date after system changes.

Our drafting approach

  • Map before writing: we inventory existing documents against requirements and your actual systems.
  • Separate policy from procedure: short policy statements, with operational procedures that name roles, tools and records.
  • Reflect your decisions: addressable specification decisions and risk acceptance are captured in the documents.
  • Plain language: written for the staff who use them, with defined terms used consistently.
  • Build in maintenance: version control, owners, review dates and a change log in every document.
  • Counsel review where needed: documents with legal implications, such as the Notice of Privacy Practices or BAA templates, are flagged for your attorney.

Policy versus procedure: an example

A policy might say: “Access to ePHI is granted based on job role and removed promptly when no longer needed.” The matching procedure says who submits an access request, who approves it, which systems it covers, how quickly accounts are disabled at termination, where the record of each step is kept, and how often access lists are reviewed. The policy states the commitment; the procedure is what makes it happen and produces the evidence.

Keeping documents maintainable

We keep the set as small as the requirements allow. Fewer, well-structured documents are easier to review, train on and keep consistent. Each document carries an owner, an effective date, a review date and a short change log, so the next review — whether done by your team or with our ongoing HIPAA compliance support — starts from a clear record.

Typical deliverables

  • Policy and procedure set covering the Privacy, Security and Breach Notification Rules, scoped to your role.
  • Requirement cross-reference showing which document addresses each standard.
  • Supporting forms and logs: access request log, breach risk assessment form, sanctions log, BAA tracker.
  • Version history and review calendar.
  • Staff summary or acknowledgment form to support HIPAA compliance training.

Engagement process

  1. 1

    Document inventory

    We collect your existing policies, procedures and forms and map them against HIPAA requirements.

  2. 2

    Discovery interviews

    Short interviews with system and process owners confirm how work actually gets done.

  3. 3

    Drafting

    We draft or revise documents in priority order, starting with the highest-risk or missing items.

  4. 4

    Review cycles

    Your owners review drafts; legal questions are routed to your counsel; we finalize revisions.

  5. 5

    Approval and rollout

    Documents are approved, versioned and distributed, with acknowledgment tracking and a review schedule.

Cost factors

Costs depend on the number of documents needed, whether we are revising usable material or starting fresh, whether you are a covered entity, business associate or both, the number of entities and locations the documents must cover, and how many review rounds your approval process requires. Supporting forms and training materials add scope. The HIPAA compliance cost resource explains how documentation fits into overall program cost.

Frequently asked questions

Can we just buy a HIPAA policy template?

Templates can be a useful starting structure, but they must be tailored to your systems, roles and decisions. A policy that does not reflect actual practice can create risk in an investigation. Many clients bring templates to us to adapt rather than starting over.

How often should HIPAA policies be reviewed?

HIPAA requires periodic review and updates in response to environmental or operational changes, and prompt updates when the law changes. It does not set a fixed interval; many organizations review annually and after significant changes.

How long do we need to keep old versions?

Six years from the date of creation or the date the policy was last in effect, whichever is later, under §164.316(b)(2) and §164.530(j)(2).

Do business associates need HIPAA policies?

Yes. Business associates must maintain Security Rule policies and procedures and follow the use and disclosure terms of their BAAs. The scope differs from a covered entity’s, and we tailor the set accordingly.

Will these policies make us compliant?

Policies are necessary but not sufficient. Compliance depends on following them, training staff, managing risk and keeping documentation current. No consultant can promise a compliant outcome.

Authoritative sources

This page is general information, not legal advice. Regulations and guidance change; confirm current requirements with the official sources above and, where needed, qualified legal counsel.

Talk through your HIPAA obligations with a consultant

Tell us about your organization, how you handle patient information, and what’s prompting the review. We’ll suggest a practical scope — and tell you if you don’t need us.