CenterFuze Business Associate Agreement
Publication date: January 1, 2026
Effective date between the parties: The date Customer accepts the Customer Subscription Agreement or first uses the Healthcare Module to create, receive, maintain, or transmit PHI, whichever occurs first.
Version: 1.0
This Business Associate Agreement (“BAA”) is between the customer accepting it (“Covered Entity”) and CenterFuze, LLC (“Business Associate”). It supplements the CenterFuze Customer Subscription Agreement (“Service Agreement”). If Customer is itself a Business Associate, references to Covered Entity include Customer in that capacity and CenterFuze acts as its subcontractor Business Associate.
By checking the acceptance box for the Service Agreement or using the Healthcare Module for PHI, Covered Entity accepts this BAA and represents that the accepting person has authority to bind it. This BAA applies only to PHI processed through the Healthcare Module and approved healthcare workflows.
1. Definitions
Terms including Breach, Business Associate, Covered Entity, Designated Record Set, Disclosure, Electronic PHI, Health Care Operations, Individual, Minimum Necessary, PHI, Required by Law, Secretary, Security Incident, Subcontractor, Unsecured PHI, and Use have the meanings in HIPAA. “HIPAA” means the Health Insurance Portability and Accountability Act, HITECH Act, and Privacy, Security, Breach Notification, and Enforcement Rules at 45 C.F.R. Parts 160 and 164, as amended. “Healthcare Module” means the CenterFuze service functions expressly approved for PHI, including supported eligibility, claims, remittance, benefits, appeals, insurance, and related workflows.
2. Permitted uses and disclosures
Business Associate may Use and Disclose PHI only to provide, secure, support, maintain, and administer the Healthcare Module under the Service Agreement; as authorized by Covered Entity; and as Required by Law. Business Associate will not Use or Disclose PHI in a manner that would violate the Privacy Rule if done by Covered Entity, except for uses and disclosures expressly permitted below.
Business Associate may Use PHI for its proper management and administration or to carry out its legal responsibilities. It may Disclose PHI for those purposes only if Required by Law or after obtaining reasonable assurances that the recipient will keep it confidential, use it only for the stated purpose or as Required by Law, and report any known breach of confidentiality. Business Associate may provide Data Aggregation services relating to Covered Entity's Health Care Operations only as authorized by Covered Entity. Business Associate may de-identify PHI in accordance with 45 C.F.R. § 164.514 and may use properly de-identified information as permitted by law and the Service Agreement.
Business Associate will make Uses, Disclosures, and requests consistent with the Minimum Necessary requirement and Covered Entity's notified restrictions to the extent applicable to Business Associate.
3. Safeguards
Business Associate will use appropriate safeguards to prevent Use or Disclosure other than as permitted and will comply with the applicable requirements of the Security Rule for Electronic PHI. Safeguards include supported encryption, multi-factor authentication, role-based access controls, audit logging, monitoring, incident response, daily backups, secure development and release practices, and AWS-hosted multi-tenant logical separation.
4. Reporting
Business Associate will report to Covered Entity any Use or Disclosure not permitted by this BAA, a Breach of Unsecured PHI, and a Security Incident of which it becomes aware. Business Associate will notify Covered Entity of a Breach of Unsecured PHI without unreasonable delay and no later than 10 business days after discovery.
Notice will include, to the extent known, the individuals affected; types of information; date and discovery date; description; mitigation; and other information reasonably required for Covered Entity's notifications. Information may be delivered in phases as investigation continues.
The parties acknowledge that routine unsuccessful events—such as pings, blocked attacks, port scans, unsuccessful logins, and firewall events that do not result in unauthorized access, Use, Disclosure, modification, or destruction—occur and need not be individually reported.
5. Subcontractors
Business Associate will ensure that Subcontractors that create, receive, maintain, or transmit PHI on its behalf agree in writing to restrictions, conditions, and Security Rule requirements that apply to Business Associate. Business Associate will remain responsible as required by the Service Agreement and law.
6. Individual rights and Covered Entity assistance
To the extent Business Associate maintains PHI in a Designated Record Set, it will make PHI available to Covered Entity as reasonably necessary for Covered Entity to respond under 45 C.F.R. § 164.524. At Covered Entity's direction, Business Associate will make amendments or incorporate amendments under § 164.526 and provide information required for an accounting under § 164.528. Unless otherwise agreed, Covered Entity remains responsible for communicating with Individuals and determining whether a request must be granted.
If Business Associate performs an obligation of Covered Entity under the Privacy Rule, Business Associate will comply with the requirements applicable to Covered Entity in performing that obligation.
7. HHS access
Business Associate will make its internal practices, books, and records relating to Use and Disclosure of PHI available to the Secretary for purposes of determining Covered Entity's compliance with HIPAA, subject to applicable legal protections.
8. Covered Entity obligations
Covered Entity will notify Business Associate of limitations in its Notice of Privacy Practices, changes or revocations of Individual permissions, and agreed or legally required restrictions, to the extent they affect Business Associate. Covered Entity will not request a Use or Disclosure that would violate HIPAA if made by Covered Entity, except where HIPAA permits a Business Associate to perform the activity.
Covered Entity is responsible for its HIPAA status; lawful authority; policies; workforce training; Minimum Necessary determinations; user access; endpoints; configuration; integrations; and use of only approved Healthcare Module workflows. Covered Entity will not submit PHI to public forms, general support, AI features, or modules not approved for PHI.
9. Term and termination
This BAA continues while Business Associate creates, receives, maintains, or transmits PHI for Covered Entity. Covered Entity may terminate the affected Healthcare Module if Business Associate materially violates this BAA and fails to cure within 30 days after notice, or immediately if cure is not possible. If termination is infeasible and a material violation continues, Covered Entity may report the matter to the Secretary as required by HIPAA.
On termination, Business Associate will return or destroy PHI where feasible. PHI in active systems will remain available for export for 90 days unless Covered Entity requests earlier deletion supported by the Service. If return or destruction is infeasible for protected backups or required legal records, Business Associate will extend this BAA's protections and limit further Use and Disclosure to the purpose making return or destruction infeasible until deletion under its lifecycle.
10. Interpretation, liability, and conflict
This BAA will be interpreted to permit compliance with HIPAA. References to HIPAA provisions include amendments. No third-party beneficiary rights are created. Liability is governed by the Service Agreement. If this BAA conflicts with the Service Agreement or DPA concerning PHI, this BAA controls.
11. Electronic acceptance and notices
Electronic acceptance is the parties' signature. CenterFuze will retain the accepted version and acceptance record. Notices to Business Associate must be sent to legal@centerfuze.com and security@centerfuze.com and to CenterFuze, LLC, 433 Plaza Real, Ste 275, Boca Raton, FL 33432. Notices to Covered Entity will be sent to the legal, privacy, or security contact in its account.