BAA (Business Associate Agreement)

A HIPAA-required contract between a covered entity (typically a healthcare organization) and a business associate (a vendor that handles protected health information on behalf of the covered entity). For interpreter services, a BAA is required whenever the interpretation vendor stores, processes, or transmits PHI, including session recordings, transcripts, or scheduling data with patient identifiers.

The BAA is the contract that extends HIPAA’s confidentiality and security obligations to your interpretation vendor. Without a BAA in place, sharing PHI with an interpretation vendor is itself a HIPAA violation, regardless of what the vendor does with the data.

For most healthcare buyers, the BAA-or-no-BAA question is a threshold filter on vendor selection. Vendors that won’t sign a BAA are non-starters for hospital, clinic, and health-plan procurement. Vendors that will sign one are still subject to your due diligence on actual security practices.

A well-drafted interpretation BAA addresses:

  • What PHI the vendor may receive (typically: patient name and DOB for scheduling, session notes for some contracts)
  • How long PHI may be retained (typically: minimum necessary)
  • Who may access PHI on the vendor side (typically: assigned interpreters, dispatch staff, billing, explicitly named or role-defined)
  • Subcontractor restrictions (typically: same protections apply to subcontracted interpreters)
  • Breach notification requirements (60-day federal floor; many buyers require shorter)
  • Right to audit and termination provisions

Best practice: receive vendor’s standard BAA, run it through legal, push back on any clauses that don’t match your compliance baseline. Most reputable interpretation vendors negotiate willingly.