nephrology | | Updated | By Jay Lowrance

HIPAA Compliance Checklist for Nephrology Practices

A comprehensive HIPAA compliance checklist addressing the unique requirements and risks of nephrology practices, including dialysis coordination and lab handling.

A nephrology practice’s HIPAA program needs a documented risk analysis, written policies, trained staff, administrative, physical and technical safeguards, business associate agreements with vendors that handle PHI on its behalf, and a breach response plan. Nephrology adds heavy lab, dialysis and referral data flows that need secure transmission and clear documentation.

HIPAA compliance isn’t optional for nephrology practices—it’s a legal requirement that carries significant penalties for violations. But nephrology faces compliance challenges that general medical practices don’t encounter: constant lab result transmission, complex dialysis center coordination, and extensive sharing of protected health information (PHI) across multiple care settings.

This checklist covers the HIPAA essentials every nephrology practice needs to address, with specific attention to the unique data flows and risks in kidney care.

What Does HIPAA Actually Require?

HIPAA has four main parts that matter to a practice: the Privacy Rule (how PHI is used and shared), the Security Rule (safeguards for electronic PHI), the Breach Notification Rule and the Enforcement Rule.

Before diving into the checklist, let’s review what HIPAA actually requires:

The Privacy Rule governs how PHI can be used and disclosed. It establishes patient rights and limits on information sharing.

The Security Rule requires administrative, physical, and technical safeguards for electronic PHI (ePHI). This includes risk analysis, access controls, and encryption.

The Breach Notification Rule requires notification to patients, HHS, and sometimes media when unsecured PHI is breached.

The Enforcement Rule establishes penalties for violations, which can reach millions of dollars for willful neglect.

Part 1: Risk Analysis and Management

The Security Rule requires an “accurate and thorough assessment of the potential risks and vulnerabilities” to electronic PHI (45 CFR 164.308). Treat it as an ongoing process, not a one-time event.

Initial Risk Analysis

  • Identify all locations where PHI is stored (paper and electronic)
  • Map how PHI flows through your practice (intake → records → labs → referrals)
  • Identify all systems that contain ePHI
  • Document potential threats and vulnerabilities
  • Assess current security measures
  • Prioritize risks based on likelihood and impact
  • Create a risk remediation plan

Ongoing Risk Management

  • Review and update risk analysis annually (minimum)
  • Reassess after significant changes (new systems, new locations, etc.)
  • Document all risk decisions and remediation actions
  • Track remediation progress

Nephrology-Specific Considerations

Your risk analysis should specifically address:

  • Lab result transmission security (incoming and outgoing)
  • Dialysis center data sharing
  • Referral communication with PCPs and other specialists
  • Patient portal security
  • Remote access for physicians (hospital rounds, on-call)

Part 2: Administrative Safeguards

These are the policies, procedures, and practices that govern how your workforce handles PHI.

Policies and Procedures

  • Written HIPAA Privacy Policy
  • Written HIPAA Security Policy
  • Breach notification procedures
  • Sanctions policy for violations
  • Workforce access policy (who can access what)
  • Device and media handling policy
  • Disaster recovery and contingency plan

Security Officer Designation

  • Designated Privacy Officer (can be same person)
  • Designated Security Officer
  • Clear documentation of their responsibilities
  • Adequate authority to implement compliance

Workforce Training

  • Initial HIPAA training for all new employees
  • Annual refresher training for all staff
  • Role-specific training (front desk, clinical, billing)
  • Training documentation and records
  • Training on recognizing phishing and social engineering

Access Management

  • Unique user IDs for all system access
  • Role-based access controls (minimum necessary)
  • Process for granting access to new employees
  • Process for revoking access when employees leave
  • Periodic access reviews (who has access to what?)

Learn more about HIPAA compliance for nephrology

Part 3: Physical Safeguards

Physical security of locations where PHI is accessible matters—especially in busy clinical environments.

Facility Access

  • Secure entry to areas containing PHI
  • Visitor policies and sign-in procedures
  • Workstation positioning (screens not visible to patients)
  • Clean desk policies (no PHI left visible)

Workstation Security

  • Automatic screen lock after inactivity
  • Workstations positioned away from public view
  • Privacy screens where needed
  • No unauthorized software installation

Device and Media Controls

  • Inventory of all devices containing ePHI
  • Encryption on all portable devices (laptops, tablets, phones)
  • Secure disposal procedures for old equipment
  • Secure destruction of media containing PHI
  • Procedures for lost or stolen devices

Paper Records

  • Secure storage for paper records
  • Locked filing cabinets when not in use
  • Secure shredding for PHI disposal
  • Fax machine security (not in public areas)

Part 4: Technical Safeguards

These protect ePHI through technology controls.

Access Controls

  • Unique user identification
  • Automatic logoff
  • Encryption in transit (TLS/SSL)
  • Encryption at rest (stored data)
  • Multi-factor authentication (highly recommended)

Audit Controls

  • System activity logs
  • Login attempt monitoring
  • Access to PHI logging
  • Regular log review procedures

Integrity Controls

  • Mechanisms to verify ePHI hasn’t been improperly altered
  • Backup verification processes
  • Data integrity checks

Transmission Security

  • Encrypted email for PHI (or secure patient portal)
  • Secure fax transmission (or encrypted fax-to-email)
  • Secure file transfer protocols
  • VPN for remote access

Learn about HIPAA-compliant fax solutions

Part 5: Lab Result Handling

Lab results are the lifeblood of nephrology—and a significant compliance risk area.

Incoming Lab Results

  • Secure transmission from laboratories (encrypted connections)
  • Verification procedures for received results
  • Prompt incorporation into patient records
  • Flagging and workflow for critical values

Outgoing Lab Orders

  • Secure transmission to laboratories
  • Verification of correct patient identification
  • Documentation of orders sent

Do You Need BAAs With Your Labs?

Usually not for treatment. HIPAA’s definition of a business associate excludes a health care provider receiving information from a covered entity about a patient’s treatment (45 CFR 160.103), so sending orders and receiving results generally doesn’t require a BAA. A BAA may still be needed when a lab, or a vendor connected to it, performs a service on your practice’s behalf, such as hosting a results interface or portal for you. Confirm specific arrangements with your compliance officer.

  • List each lab relationship and whether it’s purely treatment or includes services on your behalf
  • BAAs with any lab-related vendor that handles PHI on your behalf
  • Documentation of how each lab connection is secured

Part 6: Dialysis Center Coordination

If your practice coordinates with dialysis centers, this creates significant data sharing that requires compliance attention.

Do You Need BAAs With Dialysis Centers?

Not for treatment coordination itself. Sharing a patient’s information with a dialysis center for their treatment falls under the same treatment exception, so it doesn’t require a BAA. What it does require is secure transmission, verified recipients and good documentation. A BAA can come into play if one organization performs administrative or other services on the other’s behalf; review those arrangements with counsel.

  • Inventory of every dialysis center you coordinate with
  • Agreed, secure method for sharing patient information with each
  • BAAs only where one party performs services on the other’s behalf beyond treatment
  • Annual review of these arrangements

Data Sharing Protocols

  • Defined what information is shared and how
  • Secure transmission methods for patient data
  • Access controls for shared patient information
  • Procedures for addressing discrepancies

For Practices That Own/Operate Dialysis Centers

  • Separate compliance programs if required
  • Clear policies for information flow between practice and dialysis
  • Appropriate access segmentation

Part 7: Referral and Care Coordination

Nephrology involves extensive coordination with other providers—each interaction involves PHI.

Referral Communications

  • Secure methods for receiving referral information
  • Secure methods for sending consult notes back
  • Send only what the recipient needs (good practice, even though HIPAA’s minimum necessary standard doesn’t apply to disclosures to a provider for treatment)
  • Verification of recipient identity before sending PHI

Care Coordination

  • Secure communication with PCPs
  • Secure communication with hospitals
  • Secure communication with transplant centers
  • Documentation of disclosures

Patient Portal

  • Secure patient portal meeting HIPAA requirements
  • Strong authentication for patient access
  • Encryption of portal data
  • Audit logging of portal access

Part 8: Business Associate Management

Any vendor that handles PHI on your behalf requires a Business Associate Agreement.

Common Nephrology Business Associates

  • EHR vendor
  • Practice management system vendor
  • Billing company or clearinghouse
  • IT support provider
  • Cloud storage providers
  • Answering services
  • Shredding company
  • Email service (if PHI is transmitted)

Laboratories and dialysis centers usually aren’t on this list: when they receive PHI for a patient’s treatment, they’re treating providers, not business associates.

BAA Requirements

  • Written BAA in place before PHI is shared
  • BAA includes required HIPAA provisions
  • Annual review of BAA inventory
  • Process for handling BA breaches
  • Documentation of BA compliance verification

Learn about IT services for healthcare

Part 9: Breach Response

Despite best efforts, breaches can happen. Being prepared is essential.

Breach Response Plan

  • Written breach response procedures
  • Clear roles and responsibilities
  • Contact information for response team
  • Templates for required notifications

When a Breach Occurs

  • Incident documentation procedures
  • Risk assessment process (did breach require notification?)
  • Notification procedures (patients, HHS, media if applicable)
  • Timeline compliance: notify affected patients without unreasonable delay and no later than 60 calendar days after discovery
  • Corrective action documentation

Documentation

  • Maintain breach log for 6 years
  • Document all breaches (even those not requiring notification)
  • Document risk assessments and decisions
  • Retain all breach-related communications

Part 10: Documentation and Record Keeping

HIPAA requires extensive documentation, retained for 6 years.

Required Documentation

  • All HIPAA policies and procedures
  • Risk analysis and management documentation
  • Training records
  • BAAs
  • Breach documentation
  • Complaints and resolution
  • Sanctions applied for violations

Documentation Best Practices

  • Consistent dating and versioning of policies
  • Clear indication of when policies were reviewed/updated
  • Organized, accessible storage of compliance documents
  • Regular audits of documentation completeness

Part 11: Patient Rights

HIPAA grants patients specific rights that your practice must honor.

Required Capabilities

  • Process for patients to access their records
  • Process for patients to request amendments
  • Process for patients to request restrictions
  • Process for patients to request alternative communications
  • Accounting of disclosures capability
  • Notice of Privacy Practices distribution

Notice of Privacy Practices

  • Current NPP compliant with HIPAA
  • NPP provided to all patients
  • Good faith effort to obtain acknowledgment
  • NPP posted in office
  • NPP available on website

How Often Should a Nephrology Practice Review HIPAA Compliance?

At least once a year, plus after any significant change such as a new EHR, a new location or a security incident.

HIPAA compliance isn’t one-and-done. Schedule annual reviews:

  • Risk analysis update
  • Policy review and updates
  • Training completion verification
  • BAA inventory review
  • Access review (terminated employees removed?)
  • Technical safeguard testing
  • Documentation audit
  • Breach log review

What Are the Most Common HIPAA Gaps in Nephrology Practices?

Unsecured lab and dialysis communications, vendors without BAAs, insecure remote access and outdated patient portals.

Watch for these common compliance gaps in nephrology practices:

  1. Lab results via unsecured email — Use encrypted email or portal only
  2. Dialysis coordination over unsecured fax or email — A BAA isn’t required for treatment coordination, but secure, verified transmission is
  3. Dictation services without BAA — Transcription services are business associates
  4. Remote access without VPN — Physicians accessing records from home or hospital need secure connections
  5. Missing BAA with IT support — Your IT provider likely accesses ePHI
  6. Outdated patient portal security — Ensure your portal meets current security standards

Need Help with HIPAA Compliance?

HIPAA compliance is complex, and nephrology adds layers of complexity. At MedTech Consulting, we help nephrology practices implement and maintain HIPAA compliance programs.

Our services include risk assessments, policy development, staff training, and technical safeguard implementation.

Contact us to discuss your compliance needs.


Related reading: Cybersecurity for Medical Practices | HIPAA-Compliant Cloud Fax | Social Media Compliance for Healthcare

Frequently Asked Questions

What does HIPAA require of a nephrology practice?

Every nephrology practice needs a documented, regularly updated risk analysis; written privacy and security policies; designated privacy and security officers; workforce training; access controls, encryption and audit logging for electronic records; business associate agreements with vendors that handle PHI on its behalf; a breach response plan; and processes for patient rights such as record access. Documentation must be kept for six years.

Does a nephrology practice need a BAA with dialysis centers and labs?

Generally not for treatment. Under HIPAA, a health care provider isn't a business associate when another covered entity shares information with it about a patient's treatment, so coordinating care with dialysis centers or sending orders to labs usually doesn't require a BAA. A BAA may be needed if one organization performs services on the other's behalf beyond treatment. Confirm specific arrangements with your compliance officer.

How often should a medical practice do a HIPAA risk analysis?

HIPAA requires an accurate and thorough risk analysis but doesn't set a fixed schedule. Most practices update it at least annually and again after any significant change, such as a new EHR, a new location, a new remote access setup or a security incident. Document each review, the risks found and what you did about them.

How long does a practice have to notify patients of a HIPAA breach?

Affected individuals must be notified without unreasonable delay and no later than 60 calendar days after the breach is discovered. Every breach must also be reported to HHS: at the same time for breaches affecting 500 or more people, or in an annual log for smaller ones. Large breaches in a single state also require media notice. Keep records of every incident and your risk assessment, including incidents you decide don't require notification.

What are the most common HIPAA gaps in nephrology practices?

The gaps we see most are lab results sent by unsecured email, dialysis coordination over unsecured fax or email, transcription and IT vendors with no BAA, physicians reaching records remotely without a secure connection, missing multi-factor login, and patient portals running on outdated security. Most are fixable with configuration changes and a vendor BAA review.

HIPAA compliance nephrology healthcare security patient privacy dialysis compliance
Jay Lowrance, Founder of MedTech Consulting

Jay Lowrance

Founder & Principal Consultant

Jay has spent 25+ years in technology and 15+ years in healthcare. He runs MedTech Consulting, a local tech partner for businesses in Gwinnett, Barrow and Walton counties covering IT, business phones, websites, marketing, and AI. He works hands-on with every client.

Ready to Grow Your Practice?

15+ years helping medical practices with marketing, AI, and technology.