Security incidents make headlines, but many HIPAA complaints come from everyday privacy decisions: a patient who waited months for their records, a disclosure to a family member that went too far, a marketing email sent without authorization. The Privacy Rule governs those decisions, and it applies to PHI in every form — paper, verbal and electronic.
Our Privacy Rule consulting helps covered entities and business associates turn the rule into workflows staff can follow at the front desk, in the billing office and inside a software product.
Key points
- The Privacy Rule covers PHI in all forms, not just electronic data.
- Individual rights carry specific response deadlines that must be tracked.
- Business associates are bound by Privacy Rule limits through their BAAs.
- Legal interpretation questions are handled together with your counsel.
Service overview
Privacy Rule consulting covers the rules for using and disclosing PHI, the rights individuals have over their information, and the administrative requirements in §164.530 that hold the program together. Engagements range from a focused review of one workflow — such as release of information — to a full privacy program build as part of HIPAA compliance consulting.
Who needs Privacy Rule support
- Clinics, practices and hospitals with inconsistent release-of-information or records-request handling.
- Mental health and behavioral health providers balancing psychotherapy notes protections and family involvement — see HIPAA consulting for mental health.
- Digital health and SaaS companies that need to know what their BAAs allow them to do with data, including de-identification and analytics.
- Organizations launching patient communications, marketing or fundraising programs.
- New privacy officials who have inherited a program without documentation.
Regulatory considerations
The core principle is that a covered entity may not use or disclose PHI except as the Privacy Rule permits or requires (§164.502). Uses and disclosures for treatment, payment and health care operations are permitted under §164.506; many others require a written authorization under §164.508, including most marketing and any sale of PHI. When PHI is used or disclosed, the minimum necessary standard (§164.502(b) and §164.514(d)) generally applies, with exceptions such as disclosures for treatment.
| Right | Citation | Response timing |
|---|---|---|
| Access to PHI in a designated record set | §164.524 | Act within 30 calendar days; one 30-day extension with written notice of the reason |
| Amendment | §164.526 | Act within 60 days; one 30-day extension with written notice |
| Accounting of disclosures | §164.528 | Act within 60 days; one 30-day extension with written notice |
| Request restrictions; confidential communications | §164.522 | Must agree to restrict disclosures to a health plan for items paid in full out of pocket (with limited exceptions) |
| Notice of Privacy Practices | §164.520 | Provide, post and make available as the rule specifies |
Common Privacy Rule challenges
- Access requests delayed by unnecessary forms, fee disputes or confusion between patient access and third-party requests.
- Staff sharing more than the minimum necessary in internal email or with vendors.
- Notice of Privacy Practices not updated after changes in practices or regulation.
- No consistent process for verifying identity before disclosure.
- Business associates using PHI for product analytics beyond what the BAA permits.
- Complaints handled informally with no documentation, despite the §164.530(d) requirement for a complaint process.
Our approach
We start with real workflows rather than policy text. We follow a records request from intake to fulfillment, review how disclosures to family members and third parties are handled, and examine how PHI moves to vendors. Then we compare those workflows with the rule and your policies.
Administrative requirements we review
- Designation of a privacy official and a contact person for complaints (§164.530(a)).
- Workforce training on privacy policies (§164.530(b)).
- Administrative, technical and physical safeguards for PHI in all forms (§164.530(c)).
- Complaint process, sanctions, mitigation and non-retaliation (§164.530(d)–(g)).
- Policies, procedures and documentation retained for six years (§164.530(i)–(j)).
Privacy considerations for business associates
A business associate may use and disclose PHI only as its BAA permits or requires, or as required by law. For software and services companies, the practical questions are usually about secondary use: product analytics, model training, benchmarking, support access and subcontractors. We map each of these uses to the BAA language and to §164.504(e), flag where the contract is silent or ambiguous, and recommend that contract interpretation be confirmed with your counsel. Subcontractors that handle PHI on your behalf need their own BAAs with you.
Where privacy meets security
Privacy decisions often depend on technical controls such as role-based access and audit logs. We coordinate with your HIPAA Security Rule consulting work so the two programs stay aligned.
Typical deliverables
- Privacy program assessment against Subpart E and §164.530.
- Updated privacy policies and procedures, including uses and disclosures, minimum necessary and verification.
- Individual rights workflows with request logs and deadline tracking.
- Notice of Privacy Practices review with suggested revisions for counsel’s review.
- Privacy training content tailored to front-desk, clinical, billing or product roles.
- Complaint and sanctions log templates.
Engagement process
- 1
Intake
We identify the workflows and concerns in scope, and whether counsel should be involved from the start.
- 2
Workflow walkthroughs
We observe or walk through records requests, disclosures and vendor data flows with the staff who handle them.
- 3
Gap review
Workflows and documents are compared with Privacy Rule requirements and your BAAs.
- 4
Drafting
We draft or revise policies, procedures, logs and training, with legal questions routed to counsel.
- 5
Rollout support
We help brief managers and staff and set a review schedule for the privacy official.
Cost factors
Scope depends on how many workflows are reviewed, the number of locations and departments, whether you are a covered entity or business associate, the volume of patient-facing documents to update, and whether training development is included. A targeted review of one process is far narrower than a full privacy program build. Our Privacy Rule requirements resource can help you decide which areas to prioritize.
Frequently asked questions
Does the Privacy Rule apply to paper records and conversations?
Yes. The Privacy Rule protects PHI in any form — electronic, paper or oral. The Security Rule, by contrast, applies only to electronic PHI.
How quickly must we respond to a patient’s request for records?
Under the current rule, you must act on an access request within 30 calendar days, with one 30-day extension if you notify the individual in writing of the reason and expected date. Some state laws set shorter deadlines.
Can our company use de-identified data for analytics?
Data de-identified under §164.514 (via the safe harbor or expert determination method) is no longer PHI. Whether and how a business associate may de-identify data depends on its BAA. We review the approach and recommend confirming contract interpretation with counsel.
Do business associates need a Notice of Privacy Practices?
No. The NPP is a covered entity obligation. Business associates must follow the use and disclosure limits in their BAAs and are directly liable for certain Privacy Rule requirements.
Will you write our Notice of Privacy Practices?
We can draft or revise it based on HHS model notices and your actual practices. Because it is a legal notice, we recommend final review by your legal counsel.
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.