MenuClose

Business Associate Agreement

Version 0.1 (draft), November 20, 2026

Draft for the owner's legal review. Not in effect: a lawyer reviews it and the slots marked "owner to fill" are filled before it takes effect.

An agency signs this agreement with IncidentSuite before it puts any protected health information (PHI) into IncidentSuite. It is available from [owner to fill: the date the BAA is available]; until then, agencies use made-up data only, never a real patient's. This page is the agreement's text; the signed copy is the one that binds.

This Business Associate Agreement ("Agreement") is entered into as of [effective date] between [agency's legal name], [agency's address] ("Covered Entity"), and [owner to fill: company legal name], [owner to fill: entity type and state], [owner to fill: company address] ("Business Associate"), which provides the IncidentSuite software service (the "Service").

1. Definitions

Terms used but not defined here have the meanings given in 45 CFR Parts 160 and 164 (the "HIPAA Rules"), including: Breach, Data Aggregation, Designated Record Set, Disclosure, Health Care Operations, Individual, Minimum Necessary, Notice of Privacy Practices, Protected Health Information ("PHI"), Required by Law, Secretary, Security Incident, Subcontractor, Unsecured Protected Health Information, and Use.

2. Obligations of Business Associate

Business Associate shall:

(a) Uses and disclosures. Not use or disclose PHI other than as permitted or required by this Agreement or as Required by Law.

(b) Safeguards. Use appropriate safeguards, and comply with Subpart C of 45 CFR Part 164 for electronic PHI, to prevent use or disclosure other than as this Agreement provides. The safeguards in place are listed in Exhibit B.

(c) Reporting. Report to Covered Entity:

  • any use or disclosure of PHI not provided for by this Agreement of which it becomes aware;
  • any Breach of Unsecured PHI, as required by 45 CFR 164.410, without unreasonable delay and in no case later than [owner to fill: number of calendar days] calendar days after discovery;
  • any Security Incident of which it becomes aware.

The parties agree that this Section is notice of the ongoing, unsuccessful attempts that are routine on the internet (pings, port scans, failed sign-in attempts and similar), and no further notice of those is required.

(d) Breach notice content. Include in a Breach report, to the extent known and as it becomes known, the identification of each Individual whose Unsecured PHI has been, or is reasonably believed to have been, accessed, acquired, used or disclosed, and the other information Covered Entity needs for its own notices under 45 CFR 164.404.

(e) Subcontractors. Under 45 CFR 164.502(e)(1)(ii) and 164.308(b)(2), ensure that any Subcontractor that creates, receives, maintains or transmits PHI on its behalf agrees to the same restrictions, conditions and requirements that apply to Business Associate. The Subcontractors at the Effective Date are listed in Exhibit A. Business Associate will give Covered Entity [owner to fill: number of days] days' notice before adding a Subcontractor that will hold PHI.

(f) Access. Make PHI in a Designated Record Set available to Covered Entity within [owner to fill: number of days] days of its request, so it can meet 45 CFR 164.524. The Service lets Covered Entity's administrators export all of its records directly, at any time (Settings, Export).

(g) Amendment. Make amendments to PHI in a Designated Record Set as directed by Covered Entity under 45 CFR 164.526. The Service keeps the original record and records each amendment as a new, linked version.

(h) Accounting of disclosures. Maintain and make available the information required for Covered Entity to give an accounting of disclosures under 45 CFR 164.528, within [owner to fill: number of days] days of its request.

(i) Covered Entity's obligations. To the extent Business Associate carries out an obligation of Covered Entity under Subpart E of 45 CFR Part 164, comply with the requirements of Subpart E that apply to Covered Entity in performing it.

(j) Books and records. Make its internal practices, books and records available to the Secretary for determining compliance with the HIPAA Rules.

(k) Minimum necessary. Request, use and disclose only the minimum PHI necessary.

3. Permitted uses and disclosures

(a) Business Associate may use and disclose PHI only to provide the Service to Covered Entity, as described in the IncidentSuite Terms of Service, and as Required by Law.

(b) 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 the disclosure is Required by Law, or if Business Associate obtains reasonable assurances from the recipient that the PHI will be held confidentially, used or further disclosed only as Required by Law or for the purpose for which it was disclosed, and that the recipient will notify Business Associate of any breach of its confidentiality.

(c) Business Associate may provide Data Aggregation services relating to Covered Entity's Health Care Operations [owner to fill: only if the parties agree in writing, or never].

(d) Business Associate may de-identify PHI under 45 CFR 164.514(b) [owner to fill: only with Covered Entity's written consent, or never].

(e) Business Associate will not sell PHI. It will not use PHI for marketing, or for training any model or product other than the Service provided to Covered Entity.

(f) Business Associate's staff access Covered Entity's data only to provide support Covered Entity asks for, or to keep the Service secure and working, and only through the Service's staff tools, which record every view and action.

4. Obligations of Covered Entity

Covered Entity shall:

(a) Notify Business Associate of any limitation in its Notice of Privacy Practices, any change in or revocation of an Individual's permission, and any restriction it has agreed to under 45 CFR 164.522, to the extent the item may affect Business Associate's use or disclosure of PHI.

(b) Not ask Business Associate to use or disclose PHI in any manner not permitted under Subpart E of 45 CFR Part 164 if done by Covered Entity.

(c) Be responsible for its users (whom it invites, their roles, and removing them when they leave), the devices it enrolls, and the security of its own workstations and phones, including a screen lock on every phone that signs in. The Service requires two-step sign-in for every web sign-in.

(d) Send to the Service only the dispatch fields needed for fire and EMS response, and configure its dispatch system or feed accordingly.

(e) Not send Criminal Justice Information (as defined in the FBI CJIS Security Policy) to the Service: NCIC or III returns, criminal history, or law-enforcement case information. The Service is not built or authorized to hold it.

5. Term and termination

(a) Term. This Agreement starts on the Effective Date and lasts until the subscription ends and all PHI has been returned or destroyed under Section 5(c).

(b) Termination for cause. If either party learns of a material breach by the other, it shall give the other party written notice and [owner to fill: number of days] days to cure. If the breach is not cured, it may terminate this Agreement and the subscription.

(c) Return or destruction. On termination, Business Associate shall, at Covered Entity's choice, return all PHI in a format the Service can export, or destroy it. Database backups expire after 14 days. [owner to fill: deleted files' earlier versions are kept until a lifecycle rule is set]. Where return or destruction is infeasible, Business Associate shall extend this Agreement's protections to the remaining PHI and limit further use and disclosure to the purposes that make return or destruction infeasible.

(d) Survival. Section 5(c) survives termination.

6. Miscellaneous

(a) Amendment. The parties shall amend this Agreement as needed to comply with changes to the HIPAA Rules.

(b) Interpretation. Any ambiguity shall be resolved to permit compliance with the HIPAA Rules.

(c) No third-party beneficiaries.

(d) Order of precedence. If this Agreement conflicts with the Terms of Service, this Agreement controls as to PHI.

(e) Governing law. [owner to fill: governing-law state].

(f) Notices. Business Associate's security contact: [owner to fill: security officer's name, title, email and phone]. Covered Entity's privacy officer: [name, email, phone].

Exhibit A: Subcontractors that hold PHI at the Effective Date

SubcontractorServiceAgreement
Google LLC (Google Cloud)Hosting, database, files, sign-in, functions, logsGoogle Cloud HIPAA Business Associate Addendum, accepted [owner to fill: date accepted]
Google LLC (Google Workspace: Gmail)The mailbox that receives dispatch email. Listed only if email intake is on, and the Workspace agreement accepted, by the Effective DateGoogle Workspace HIPAA Business Associate Addendum, accepted [owner to fill: date accepted]

Not Subcontractors, because they receive no PHI: Twilio SendGrid (email, which carries no patient detail), Stripe (billing) and Cloudflare (domain name service only).

Exhibit B: Safeguards

[owner to fill: the safeguards in place on the Effective Date, from compliance's confirmed list]

Signatures

Covered Entity: ______________________ Name and title: ______________ Date: ________

Business Associate: ______________________ Name and title: ______________ Date: ________