Establishing secure connection…Loading editor…Preparing document…

HITRUST Healthcare Addendum

This template is fully customizable. Edit the text, fill out the fields, and send it for signature. Give it a try!

HITRUST HEALTHCARE ADDENDUM

This HITRUST Healthcare Addendum (the Addendum) is entered into by and between Covered Entity Name: and Business Associate Name: . Effective Date:

RECITALS

WHEREAS, Covered Entity and Business Associate are parties to an agreement governing the handling of protected health information; and

WHEREAS, the parties desire to impose additional information security and privacy obligations consistent with HITRUST requirements and applicable law to protect the confidentiality, integrity and availability of Protected Health Information (PHI).

DEFINITIONS

For purposes of this Addendum, terms shall have the meanings set forth in the underlying agreement. In addition:

"HITRUST" means the HITRUST Common Security Framework and associated certification requirements. "PHI" means protected health information as defined by applicable law.

SCOPE OF ADDENDUM

This Addendum supplements the parties' underlying agreement and applies to all PHI accessed, created, received, maintained, transmitted, or stored by Business Associate on behalf of Covered Entity in connection with services provided under the underlying agreement.

PATIENT INFORMATION (IF APPLICABLE)

Date of Birth:

Gender:

Phone:

Relationship:

Phone:

INSURANCE INFORMATION

Policy Number:

Group Number:

MEDICAL HISTORY

DATA SECURITY AND HITRUST REQUIREMENTS

Business Associate shall implement and maintain administrative, physical and technical safeguards consistent with HITRUST requirements and applicable law to protect PHI. Business Associate shall, at minimum:

  • Maintain risk assessments and remediation plans, including regular vulnerability scanning and penetration testing;
  • Implement role-based access controls, multifactor authentication for privileged access, and logging sufficient to support incident investigations;
  • Encrypt PHI in transit and at rest where technically feasible;
  • Maintain an incident response program that includes notification procedures to Covered Entity;
  • Apply secure change management and patching practices to systems that store or process PHI.

Business Associate attests to the following (select applicable option and provide details):

Business Associate currently holds HITRUST certification for the services covered by this Addendum.

If Business Associate is not currently certified, Business Associate shall achieve certification within of the Effective Date.

BREACH NOTIFICATION AND REMEDIATION

Business Associate shall notify Covered Entity of any actual, suspected, or reasonably suspected breach or security incident affecting PHI without unreasonable delay and in no event later than 72 hours after discovery of the incident. Notification shall include available information regarding scope, affected data elements, remediation steps taken, and corrective actions planned.

Phone:

Email:

Business Associate shall cooperate in investigations and regulatory reporting and shall implement remediation measures to prevent recurrence. Covered Entity retains the right to require forensic review and independent assessment at Business Associate's expense where Business Associate's controls are found deficient.

SUBCONTRACTORS AND FLOW-DOWN

Business Associate shall require any subcontractor creating, receiving, maintaining, or transmitting PHI on its behalf to agree in writing to the same restrictions and obligations that apply to Business Associate under this Addendum, including HITRUST-related obligations where applicable.

Business Associate must provide Covered Entity with a list of subcontractors processing PHI upon request and shall remain liable for the acts and omissions of such subcontractors.

AUDIT RIGHTS AND REPORTING

Covered Entity or its authorized representative shall have the right to assess Business Associate's compliance with this Addendum, including review of relevant policies, procedures and audit reports, subject to reasonable notice and protection of Business Associate's confidential information. Business Associate shall promptly provide evidence of HITRUST status and relevant audit reports upon request.

TERMINATION; RETURN AND DESTRUCTION OF PHI

Upon termination or expiration of the underlying agreement, Business Associate shall return or destroy PHI in accordance with Covered Entity's written instructions. If return or destruction is infeasible, Business Associate shall continue to protect PHI and shall limit further uses and disclosures to those purposes that make the return infeasible.

MISCELLANEOUS

This Addendum shall be governed by the laws selected in the underlying agreement. In the event of any conflict between this Addendum and the underlying agreement, the provisions that are more protective of PHI and consistent with applicable law shall govern.

HIPAA / PRIVACY ACKNOWLEDGMENT

Both parties acknowledge their respective obligations under HIPAA and agree to comply with applicable privacy and security rules. Covered Entity acknowledges that Business Associate's safeguards are described in this Addendum and that Covered Entity shall limit disclosures of PHI to the minimum necessary for the permitted purpose.

Covered Entity and Business Associate each acknowledge they are subject to HIPAA obligations and have read and accept the obligations set forth in this Addendum.

ADDITIONAL PROVISIONS

Covered Entity

Printed Name:

By:

Date:

Title:

Business Associate

Printed Name:

By:

Date:

Title:

Enter text✕

What the HITRUST Healthcare Addendum Is

The HITRUST Healthcare Addendum is a contract attachment that documents specific information security and privacy obligations aligned with the HITRUST Common Security Framework (CSF) for arrangements involving protected health information. It supplements core agreements—such as business associate agreements (BAAs) or vendor contracts—by mapping controls, reporting expectations, breach notification timelines, and audit access rights to HITRUST requirements. Organizations use this addendum to show how a vendor’s program meets or will remediate against HITRUST control categories relevant to the relationship, and to establish measurable obligations for handling electronic protected health information (ePHI).

Why a HITRUST Healthcare Addendum Matters

A HITRUST Healthcare Addendum clarifies security responsibilities, reduces compliance gaps with HITRUST CSF and HIPAA expectations, and provides purchasers a documented baseline for vendor assessment and audit rights.

Why a HITRUST Healthcare Addendum Matters

Who Typically Prepares and Signs This Addendum

The addendum is used by parties that exchange or process ePHI and need to align contract terms with HITRUST controls and HIPAA obligations.

  • Health systems and hospitals assessing vendor security posture in procurement and vendor risk management workflows.
  • Healthcare technology vendors delivering SaaS or cloud-hosted services that store or transmit ePHI.
  • Third-party service providers (billing, RCM, analytics) that act as business associates under HIPAA.

Common signers include security or compliance officers, legal counsel, and authorized executives for both covered entities and business associates.

Core Elements to Include in a Professional HITRUST Healthcare Addendum

A well-structured addendum lists the scope of covered data, specific HITRUST control families applied, evidence and audit rights, incident response and breach notification procedures, remediation timelines, and acceptance criteria for assessments or continuous monitoring.

Scope

Define roles (covered entity, business associate), systems, and data types (ePHI) that fall under the addendum.

Mapped Controls

Specify applicable HITRUST CSF control objectives and how they are implemented or planned to be implemented.

Audit & Evidence

Detail evidence deliverables (attestations, audit reports, HITRUST certification level) and frequency of access.

Breach Response

Set notification windows, forensic access, remediation obligations, and coordination procedures for incidents affecting ePHI.

Remediation Milestones

Agree timelines for corrective actions, testing, and validation where gaps are identified during assessments.

Liability & Limits

Clarify indemnities, limitation of liability, insurance expectations, and data return or destruction at termination.

Essential Information Fields to Include

Parties: Full legal names
Effective Date: MM/DD/YYYY
Scope Description: Systems and data
HITRUST Status: Certification level or remediation plan
Breach Timeline: Hours to notify
Audit Rights: Frequency and format

Step-by-Step: Completing the HITRUST Healthcare Addendum

Follow these four practical steps to prepare and finalize the addendum with clarity and compliance.

  • 01
    Gather Info: Collect legal names, system inventory, and current HITRUST evidence.
  • 02
    Map Controls: Identify applicable HITRUST CSF categories and note implementation status.
  • 03
    Agree Terms: Negotiate notification windows, audit access, and remediation schedules.
  • 04
    Execute: Obtain authorized signatures and store executed copies securely.

How to Configure an Online HITRUST Addendum Workflow

An electronic workflow improves traceability; configure fields and authentication consistent with legal and healthcare requirements.

Field Configuration
Signature Fields Require name, title, date
Authentication Email + SMS OTP or organization SSO
Audit Trail Capture IP, timestamp, and events
Document Storage Encrypted at rest with access logging

Digital Signing and Submission Considerations

Use an eSignature platform that meets HIPAA and HITRUST-related technical controls, supports secure storage, and preserves an auditable trail.

  • Authentication Options: Email link, SMS OTP, KBA, or SSO
  • Document Formats: PDF, DOCX supported
  • Integrations: CRM and cloud storage connectors

Where to Send and How to Submit the Executed Addendum

Common submission paths include vendor contract repositories, procurement portals, and secure email or SFTP to the counterparty designated compliance mailbox.

  • Contract Repository: Upload executed addendum to central contract management system.
  • Vendor Portal: Submit through vendor onboarding or vendor risk portal.
  • Secure Transmission: Use encrypted email or SFTP when direct upload is unavailable.
  • Record Retention: Store signed copy with audit metadata for future review.

Common Preparation Mistakes to Avoid

  • Leaving scope vague rather than enumerating systems and data types.
  • Failing to align timelines for remediation with contractual milestones.
  • Skipping a review of the vendor’s current HITRUST or SOC attestation evidence.
  • Not specifying the format and frequency of audit evidence delivery.

Risks and Consequences of an Inadequate Addendum

Regulatory Exposure: HIPAA enforcement and potential corrective action
Financial Loss: Breach-related costs and liability
Contract Dispute: Ambiguous obligations leading to litigation
Certification Impact: Failure to meet HITRUST audit expectations
Operational Downtime: Service interruption during remediation
Reputational Harm: Loss of customer trust and market impact

Real-World Examples of the Addendum in Use

The following case summaries illustrate how healthcare organizations and vendors document HITRUST-related commitments in contracts.

Fertility Centers Example

A regional healthcare provider required vendors to deliver quarterly evidence of control implementation.

  • The vendor provided a consolidated report.
  • This allowed the provider to meet internal audit requirements and reduce ad hoc evidence requests while maintaining documented accountability and breach coordination procedures.

NetSuite Integration Example

An enterprise vendor integrated contract metadata with its ERP for tracking.

  • The integration flagged expired attestations.
  • That process improved renewal timelines and ensured procurement teams had current HITRUST status before approving continued access to ePHI systems.

eSignature Pricing Snapshot (signNow first)

Compare common commercial eSignature plans focusing on starting price, trial availability, bulk send, audit trail, HIPAA compliance, and envelope or usage caps.

signNow DocuSign Adobe Sign PandaDoc HelloSign
Starting Price $8/user/mo $15/user/mo $14/user/mo $19/user/mo $15/user/mo
Free Trial 7-day free trial, no credit card Varies by vendor Varies by vendor Varies by vendor Varies by vendor
Bulk Send Yes Yes Yes Yes No
Audit Trail Yes Yes Yes Yes Yes
HIPAA Compliant Yes Yes Yes No No

Frequently Asked Questions About the HITRUST Healthcare Addendum

Answers to common questions about applicability, signatures, and evidence help avoid delays and ensure enforceability.


Need help? Contact support

be ready to get more
Join over 28 million airSlate SignNow users