HIPAA Compliance Guide: Using Collection Agencies Without Violating Patient Privacy

Check out the new compliance progress tracker


Product Pricing Demo Video Free HIPAA Training
LATEST
video thumbnail
Admin Dashboard Walkthrough Jake guides you step-by-step through the process of achieving HIPAA compliance
Ready to get started? Book a demo with our team
Talk to an expert

HIPAA Compliance Guide: Using Collection Agencies Without Violating Patient Privacy

Kevin Henry

HIPAA

March 26, 2024

7 minutes read
Share this article
HIPAA Compliance Guide: Using Collection Agencies Without Violating Patient Privacy

HIPAA and Debt Collection

Where HIPAA fits in medical debt collection

HIPAA permits disclosures of Protected Health Information for “payment” activities, which include using a third‑party to pursue legitimate balances. The key is aligning every disclosure with HIPAA’s Patient Privacy Safeguards and documenting why each data element is needed for payment.

When a provider, health plan, or their revenue cycle vendor engages a collection agency, the agency will typically create, receive, maintain, or transmit PHI. That makes the agency a Business Associate in most placement arrangements, triggering specific contractual and security obligations described below.

Placement vs. sale of accounts

Placing an account for collection usually involves granting the agency limited rights to use PHI for payment on the provider’s behalf. By contrast, an outright sale or assignment of receivables can change roles and responsibilities. Regardless of structure, your disclosure must be permitted by HIPAA and narrowed by the Minimum Necessary Rule.

Minimum Necessary Standard

Apply the Minimum Necessary Rule to every disclosure

Share only the least amount of PHI required for the agency to validate, locate, and collect the debt. Build a field‑level “allowed dataset” so staff and systems consistently withhold extraneous medical details.

Commonly necessary elements

  • Patient identifiers and contact information (name, address, phone, email, date of birth).
  • Account and guarantor numbers, payer status, and amounts owed.
  • Dates of service and provider/facility name.
  • Basic encounter identifiers needed to distinguish multiple balances.

Elements to exclude unless truly required

  • Diagnosis codes, procedure codes that reveal treatment, clinical notes, images, and lab results.
  • Mental health, substance use disorder, reproductive health, HIV/STD, and other specially protected records.
  • Social Security numbers or full medical record numbers where alternatives exist.

Operationalize the Minimum Necessary Standard with role‑based access, automated redaction, data‑mapping checklists, and periodic sampling of outbound files for PHI Disclosure Restrictions breaches.

Business Associate Agreement Requirements

When a Business Associate Agreement is required

If the collection agency performs services on your behalf and will handle PHI, a Business Associate Agreement is required before any disclosure. If a debt buyer is collecting for itself after purchase, a BAA may not apply, but your original disclosure must still be lawful and minimized.

Core BAA provisions to include

  • Permitted uses/disclosures limited to collection for payment and explicit Minimum Necessary obligations.
  • Administrative, physical, and technical safeguards (including encryption in transit and at rest, access controls, and audit logging).
  • Breach and security incident reporting timelines and cooperation requirements.
  • Subcontractor “flow‑down” duties so downstream vendors meet the same protections.
  • Right to audit, workforce training expectations, and sanctions for noncompliance.
  • Return or destruction of PHI at contract end and data retention parameters.

Conduct due diligence on the agency’s security posture, including penetration testing history, SOC reports or equivalent, and evidence of workforce privacy training.

Prohibited Medical Information Sharing

Information you should not send for collections

  • Clinical narratives, progress notes, imaging, lab values, and care plans.
  • Diagnosis or procedure details that reveal the nature of treatment.
  • Psychotherapy notes and specially protected categories (e.g., substance use disorder treatment records subject to heightened federal protections).
  • Any data unrelated to verifying the consumer, the account, or the amount owed.

Adopt a “collections‑safe dataset” that strips attachments and suppresses sensitive fields by default. Use neutral account descriptors and avoid provider specialty names that could reveal a condition on envelopes, call scripts, emails, or voicemail.

Ready to simplify HIPAA compliance?

Join thousands of organizations that trust Accountable to manage their compliance needs.

State Laws Impacting PHI Disclosure

HIPAA is a floor—states can be stricter

State privacy statutes can impose tighter PHI Disclosure Restrictions than HIPAA, and you must comply with the stricter rule. Many states add special protections for mental health, HIV/STD, genetic data, reproductive health, and minor consent services, and they may require additional authorization or specific notice language.

Practical steps for multi‑state operations

  • Maintain a 50‑state matrix highlighting stricter consent, content, and retention rules for medical debt collection compliance.
  • Build state logic into letter templates, credit reporting decisions, and call scripts.
  • Flow state‑specific obligations into your Business Associate Agreement and SOWs.
  • Track state breach‑notification timelines and definitions that may differ from HIPAA.

Because state rules evolve, schedule annual legal reviews and update your datasets and scripts accordingly.

Fair Debt Collection Practices Act Compliance

The Fair Debt Collection Practices Act governs how third‑party collectors communicate with consumers. Align scripts, letters, and digital outreach so they never disclose medical details to third parties and always honor cease‑communication and dispute rights. Use limited‑content messages for voicemail and neutral business names on caller ID, envelopes, and emails.

Key FDCPA‑aligned practices

  • Send a timely validation notice that itemizes the debt and explains dispute rights.
  • Respect time‑of‑day and workplace contact restrictions and cease‑communication requests.
  • Avoid any false, deceptive, or harassing conduct; document call frequency controls consistent with Regulation F.
  • Ensure all communications reveal only what is necessary to identify the account holder—never a medical condition or treatment.

Train both revenue cycle and agency staff on the intersection of HIPAA and FDCPA to prevent privacy breaches through everyday collection activities.

Best Practices for HIPAA Compliance in Collections

Operational checklist

  • Define a HIPAA Compliance Guide for collections that maps lawful purposes, data fields, and Patient Privacy Safeguards.
  • Use a standard, “minimum‑necessary” placement file; exclude diagnoses, clinical notes, and sensitive categories by design.
  • Execute and maintain a robust Business Associate Agreement with security exhibits and audit rights.
  • Secure data transfers with encryption, MFA, IP allow‑listing, and immutable audit logs.
  • Adopt neutral branding and limited‑content messaging for letters, emails, texts, and voicemail.
  • Audit samples monthly for leakage of restricted PHI; remediate and retrain promptly.
  • Coordinate dispute, identity theft, and bankruptcy workflows to halt communications and preserve privacy.
  • Define retention and destruction schedules; require confirmation of deletion at contract end.

Bottom line: You can use collection agencies without violating patient privacy by narrowing disclosures to the Minimum Necessary Rule, contracting through a strong Business Associate Agreement, obeying PHI Disclosure Restrictions, and aligning all communications with the Fair Debt Collection Practices Act. Done together, these controls deliver medical debt collection compliance while maintaining trust.

FAQs

Is selling medical bills to collections a HIPAA violation?

Not by itself. HIPAA allows disclosures for payment, but the structure matters. Placing accounts with an agency that acts on your behalf typically requires a Business Associate Agreement. An outright sale or assignment may change roles and can raise “sale of PHI” concerns. If remuneration is for the PHI itself rather than services, patient authorization may be required unless a narrow exception applies. Consult counsel before selling receivables and minimize the PHI disclosed.

What information can be shared with collection agencies under HIPAA?

Share only what is necessary to identify the consumer and collect the balance: name, contact details, dates of service, provider name, account/guarantor numbers, and amounts owed. Do not include diagnoses, treatment details, clinical notes, or specially protected categories. Avoid Social Security numbers unless essential and justified.

Are Business Associate Agreements mandatory for collection agencies?

Yes, when the agency performs collection work on your behalf and will access PHI, a Business Associate Agreement is required. If a debt buyer is collecting for itself after purchase, a BAA may not apply, but your initial disclosure must still be permitted by HIPAA and limited to the minimum necessary. In all cases, contract for strong privacy and security controls.

How do state laws affect HIPAA compliance in medical debt collection?

State laws can be stricter than HIPAA and will control where they offer greater protection. Many states impose extra consent or content rules for sensitive categories and have distinct breach‑notification requirements. Build state‑specific logic into your datasets, notices, and scripts, and review your framework annually to stay aligned with evolving state privacy regimes.

Share this article

Ready to simplify HIPAA compliance?

Join thousands of organizations that trust Accountable to manage their compliance needs.

Related Articles