Selling or Assigning Medical Debt: HIPAA Compliance Checklist and Best Practices

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

Selling or Assigning Medical Debt: HIPAA Compliance Checklist and Best Practices

Kevin Henry

HIPAA

April 06, 2024

7 minutes read
Share this article
Selling or Assigning Medical Debt: HIPAA Compliance Checklist and Best Practices

When you sell or assign medical debt, you handle Protected Health Information (PHI) in ways that trigger HIPAA obligations. The key is aligning payment and collection activities with the HIPAA Privacy, Security, and Breach Notification Rules while honoring consumer protection laws that govern Medical Debt Collection Regulations.

This guide translates the rules into practical steps. It distinguishes assigning debt to a collection agency (you remain creditor; agency is typically a Business Associate) from selling the debt outright (buyer becomes creditor). In both scenarios, you must apply the Minimum Necessary Standard, secure PHI, and document every decision.

HIPAA Compliance in Medical Debt Collection

Core principles

  • Identify your role and the collector’s role: covered entity, business associate, subcontractor, or debt buyer. Your obligations and contracts flow from these roles.
  • Confirm a lawful basis to disclose PHI: collection falls under “payment” and certain “health care operations.” Only disclose what is necessary for that purpose.
  • Differentiate assigning vs. selling: assignment generally uses a Business Associate Agreement (BAA); a sale changes ownership and requires heightened due diligence and stricter data minimization.
  • Map PHI flows end to end: intake, transmission, storage, access, and disposal. Maintain a current data map tied to Medical Debt Collection Regulations.
  • Designate privacy and security leads, perform risk analyses, and maintain written policies that cover disclosures, safeguards, and HIPAA Breach Notification.

Permitted disclosures for collection

For collection, permissible PHI may include patient identifiers, contact details, dates of service, payer status, and amounts owed. Avoid clinical notes, images, and detailed diagnoses unless strictly required to resolve a coverage or coding dispute.

Business Associate Agreement Requirements

When a BAA is required

If a third party collects on your behalf, it is typically a Business Associate and must sign a Business Associate Agreement (BAA). A debt buyer that owns the account may not be your Business Associate, but disclosures supporting the transfer must still meet HIPAA’s requirements.

What a strong BAA includes

  • Permitted uses/disclosures: narrowly define collection and payment activities and prohibit any unrelated use of PHI.
  • Safeguards: require administrative, physical, and technical controls aligned to HIPAA’s Security Rule.
  • Breach and incident reporting: prompt notice, investigation duties, cooperation, and allocation of notification responsibilities under the HIPAA Breach Notification Rule.
  • Subcontractor flow-down: ensure downstream collectors or letter vendors sign BAAs with equivalent obligations.
  • Access, amendment, and accounting support: obligate the collector to assist with individual rights requests and disclosure logs.
  • Return or destruction: specify secure return or destruction of PHI at contract end and define exceptions where retention is legally required.
  • Monitoring and termination rights: allow audits, require remediation plans, and permit termination for material breach.

Applying the Minimum Necessary Rule

Operationalizing the Minimum Necessary Standard

  • Limit data elements: usually name, date of birth or last four SSN, account number, balance, service dates, provider, payer status, and basic procedural codes only if needed to validate coverage.
  • Exclude where possible: full medical records, psychotherapy notes, detailed diagnoses, images, labs, and clinician narratives.
  • Use role-based access: collectors see only the fields required for their task; supervisors see just enough for oversight.
  • Apply redaction and field-level masking: hide nonessential fields by default; unmask via controlled workflow when justified.
  • Document decisions: record why each data element is necessary for payment or operations.

Special situations

For disputed claims or medical-necessity appeals, share the narrowest codes or documentation needed to resolve the dispute, and only with parties authorized to receive them. Reassess necessity before each disclosure.

Ready to simplify HIPAA compliance?

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

Secure Communication and Data Handling

Transmission and storage

  • Encrypt PHI in transit (e.g., TLS) and at rest; use secure file transfer or vetted portals instead of unencrypted email attachments.
  • Enforce multi-factor authentication, strong passwords, device encryption, and automatic logoff on all collector systems.
  • Adopt least-privilege access, audit logs, and anomaly detection; review access logs routinely.

Channels and content controls

  • Email and messaging: avoid PHI in subject lines or voicemails; keep messages generic and direct patients to secure channels.
  • Paper mail: limit details to what is necessary to identify the account and balance; avoid revealing medical conditions.
  • Calls and texts: verify identity before discussing any PHI; use scripts that prevent unnecessary disclosures.

Incident response and HIPAA Breach Notification

  • Maintain a tested incident response plan with clear triage, containment, forensics, and documentation steps.
  • Assess risk factors for impermissible disclosures; if a breach is confirmed, execute HIPAA Breach Notification obligations and remediate root causes.
  • Coordinate with collectors and any subcontractors to ensure timely, accurate notifications and mitigation.

Staff Training and Compliance Audits

Training essentials

  • Provide initial and annual HIPAA training tailored to collection workflows, scripts, and systems.
  • Emphasize the Minimum Necessary Standard, identity verification, and handling of sensitive data elements.
  • Include phishing awareness and secure handling of removable media, printouts, and screenshots.

Auditing and oversight

  • Conduct periodic risk analyses, call monitoring, and access-log reviews; correct issues with documented remediation.
  • Test vendor compliance through questionnaires, evidence reviews, and on-site or virtual audits.
  • Track and enforce sanctions for policy violations; record corrective actions and outcomes.

Compliance with FDCPA and TCPA

FDCPA and Regulation F alignment

  • Provide timely validation notices with required disclosures; honor disputes and cease-communication requests.
  • Avoid unfair, deceptive, or harassing practices; follow call-frequency and time-of-day limits applicable to debt collectors.
  • Substantiate balances and itemizations; keep chain-of-title documentation when debt is sold.
  • Obtain and document appropriate consent for autodialed or prerecorded calls/texts to cell phones; honor revocations promptly.
  • Scrub numbers against do-not-call lists as applicable; classify numbers (cell, landline, VoIP) and choose compliant dialing modes.
  • Keep text content generic, free of PHI; include clear opt-out instructions and suppress upon opt-out.

Remember that state Medical Debt Collection Regulations may impose stricter requirements on disclosures, communication practices, interest, fees, and credit reporting. Build state-specific rules into your workflows and letters.

Documentation and Record-Keeping Practices

What to maintain

  • BAA inventory and vendor due-diligence files, including risk assessments and remediation plans.
  • Policies and procedures covering Privacy, Security, Minimum Necessary Standard, and HIPAA Breach Notification.
  • Training records, attestations, and sanctions logs.
  • Access logs, disclosure logs, incident/breach logs, and corrective-action records.
  • Account-level documentation: assignment or sale agreements, chain of title, balance itemization, consent records, and dispute handling.

Retention and disposition

  • Retain HIPAA-required documentation for at least six years from creation or last effective date; longer if state law or payer contracts require.
  • Apply legal holds when litigation or investigations are reasonably anticipated.
  • Use secure destruction methods (e.g., shredding, wiping, or cryptographic erasure) and record certificates of destruction.

Conclusion

Whether you assign or sell medical debt, you can stay compliant by limiting PHI to the Minimum Necessary, contracting smartly with a robust BAA where applicable, securing every communication channel, training and auditing continually, aligning with FDCPA and TCPA, and documenting each step. Done together, these best practices minimize risk while enabling effective, patient-respectful collections.

FAQs.

Is selling medical debt a HIPAA violation?

No. Selling medical debt is not inherently a HIPAA violation if disclosures of PHI are permissible for payment or health care operations, limited to the Minimum Necessary, and safeguarded appropriately. You must also ensure the transfer documents and data files exclude unnecessary clinical details and that the buyer commits to protecting any PHI received.

What are the HIPAA requirements for sharing PHI with debt collectors?

If a collector works on your behalf, treat it as a Business Associate and execute a BAA that defines permitted uses, safeguards, breach reporting, subcontractor controls, and end-of-term data handling. Disclose only what is necessary for collection, maintain security controls, log disclosures, and support individual rights requests.

How does the minimum necessary rule apply to medical debt collection?

The Minimum Necessary Standard requires you to share only the smallest set of PHI needed to collect the debt—typically identifiers, dates of service, balance, payer status, and limited billing codes when strictly required. Exclude diagnoses, narratives, and full medical records unless essential to resolve a specific payment dispute.

What security measures must debt collectors implement to protect PHI?

Collectors should encrypt PHI in transit and at rest, enforce multi-factor authentication and least-privilege access, maintain audit logs and monitoring, use secure file transfer or portals, verify identity before disclosures, train staff on HIPAA, and implement an incident response plan that supports HIPAA Breach Notification.

Share this article

Ready to simplify HIPAA compliance?

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

Related Articles