Business Associate Agreement: What Ona Health Signs and What It Covers
Ona Health signs a BAA with every practice before patient data is entered. What a BAA is, who the parties are, what 45 CFR requires it to cover.
Ona Health signs a business associate agreement with every practice before patient data is entered. The BAA is signed when the workspace is created, and Ona keeps who signed it and when. Owners and admins can see who opened, searched, exported, signed or changed a record for the last 7, 30 or 90 days in team roles and security.
Quick answer:
- Yes, Ona signs a BAA, at workspace creation rather than on request. There is no form to file, no fee and no seat minimum.
- The contents are not up to the vendor. 45 CFR 164.504(e)(2) lists what the agreement must say, and 45 CFR 164.410(b) gives the vendor no more than 60 calendar days from discovering a breach to tell you about it.
- Ona claims no certification. A BAA is a contract, not a certificate, and the rule names no certifying body.
Ona's facts below were read from ona.health on November 18, 2026, the competitor pages the same day, and the rule text is quoted from 45 CFR as published on ecfr.gov.
Ona Health is a general ambulatory EHR and practice management platform, from a solo clinician to an enterprise group, excluding inpatient and hospital settings. That matters here only because the agreement is the same either way: there is no compliance tier.
What a business associate agreement is
A BAA is a written contract that lets a provider hand PHI to a company outside its own workforce.
The definition is set in 45 CFR 160.103. A business associate is a person or company that, on behalf of a covered entity and "other than in the capacity of a member of the workforce", "creates, receives, maintains, or transmits protected health information for a function or activity regulated by this subchapter". The rule then lists the functions by name, and two of them describe practice software exactly: "billing" and "practice management".
So a practice management platform is a business associate by definition, not by choice. The question is never whether your EHR vendor is one, but whether the paperwork actually exists.
45 CFR 164.502(e) is the obligation on your side: a covered entity may disclose PHI to a business associate only with satisfactory assurances, in writing, that the information will be protected. 45 CFR 164.504(e) says what those assurances must contain. A vendor that will not sign is one you cannot legally give a chart to.
Who the two parties are when you use Ona Health
There are exactly two signatories, and buyers mix them up often enough to state it flatly.
Your practice is the covered entity. You treat the patients and bill for it. The obligation is yours, and no contract moves it.
Ona Health is the business associate. Ona receives, stores and transmits PHI on your behalf, so it signs the vendor side.
The mechanism is published on team roles and security: every practice signs Ona's BAA when the workspace is created, and Ona keeps a record of who signed it and when. That last clause is the one to check at any vendor: an agreement that takes effect silently leaves you nothing to show an auditor about who accepted it.
What it costs: nothing. The BAA is not an add-on and is not priced. Seats are $130 per practitioner per month and $45 per staff seat, and the agreement is identical at one seat and at fifty.
What the agreement has to cover
45 CFR 164.504(e)(2) sets the contents, and it is short enough to read against any vendor's draft. The contract must establish the permitted and required uses and disclosures of PHI, and may not let the vendor use or disclose it in a way that would breach the rule if your practice did. Then it commits the business associate to the following.
- Not use or disclose PHI beyond the contract, or beyond what law requires.
- Use appropriate safeguards, and comply with the Security Rule for electronic PHI.
- Report any use or disclosure not provided for by the contract, including breaches of unsecured PHI under 45 CFR 164.410.
- Bind its own subcontractors to the same restrictions and conditions.
- Make PHI available to the patient under 45 CFR 164.524.
- Make PHI available for amendment, and incorporate amendments, under 45 CFR 164.526.
- Provide the information for an accounting of disclosures under 45 CFR 164.528.
- Carry out any of your obligations it has taken on, under the same rules that bind you.
- Open its internal practices, books and records relating to PHI to the Secretary.
- Return or destroy the PHI at termination if that is feasible, keeping no copies, and if it is not feasible, keep the protections running on whatever it still holds.
The agreement must also let you terminate if the vendor breaks a material term. And 45 CFR 164.504(e)(1)(ii) adds a duty most buyers never read: if you know of a pattern of activity that breaches it, you must take reasonable steps to cure it, and terminate if you cannot. Signing is not the end of the obligation.
One number from that list is worth memorising. Under 45 CFR 164.410(b) a business associate must notify you of a breach of unsecured PHI "without unreasonable delay and in no case later than 60 calendar days after discovery". The clock starts on the first day the breach is known, or would have been known by reasonable diligence, to anyone working for them other than the person who caused it.
What a BAA is not
Three substitutions come up in procurement, and all leave a gap.
It is not a certification. No certificate replaces it. 45 CFR 164.504(e) tells a covered entity what the contract must say and names no certifying body. Ona claims no certification, and a compliance badge on any vendor's site is marketing rather than evidence. What you can verify is the signed agreement, the roles that decide who can open a record, and the log that shows who did.
It is not a patient consent. A Notice of Privacy Practices and a HIPAA authorization sit between the practice and the patient. A BAA sits between the practice and a vendor. Ona ships those documents in its consent library, and each signed consent records the time, the IP address, the browser and device, the exact wording, which boxes were ticked and a SHA-256 hash of the document. A strong audit trail for consents, and not a BAA.
It is not a substitute for your own controls. The agreement obliges the vendor to use appropriate safeguards. It says nothing about how your team behaves in the product. Ona gives you 5 roles - owner, admin, clinician, staff and student - to decide that, with Student granting no access on its own and needing a verified .edu address. Two-step sign-in is per person via an authenticator app, passwords run to a 12-character minimum, and sessions sign out after 60 idle minutes.
Subcontractors, which is where the chain usually breaks
A business associate rarely does everything itself, and the rule follows the data downstream.
45 CFR 160.103 puts a subcontractor that creates, receives, maintains or transmits PHI on a business associate's behalf inside the definition of business associate. 45 CFR 164.504(e)(5) then applies the whole of the contract requirement to the agreement between a business associate and that subcontractor, "in the same manner" as between a covered entity and a business associate. The obligations travel the chain, and each link signs with the one above it, not with you.
In practice, know which parts of your platform somebody else runs. Ona publishes one: eligibility and claims run through Ona Clearing House, which runs on Stedi, with no separate clearinghouse account to open and no separate contract to sign, and the volume is metered on a Clearing House plan from $69 a month for 100 claims, 100 ERAs and 200 eligibility checks. Because Stedi is Ona's subcontractor for that work, the paperwork under 164.504(e)(5) is Ona's to hold.
One case moves the line back to you. Ona lets a practice connect its own Claim.MD account with an API key instead of using Ona Clearing House. Then Claim.MD is your vendor and that BAA is yours to sign. Catch it before go-live, not during an audit.
How four platforms execute the agreement
One axis: how the BAA is put in place and what each vendor publishes about it. Not a quality ranking, and every row here does sign one. All four pages read live on November 18, 2026.
| Platform | How the agreement is put in place | When it takes effect | Date shown on the agreement | Fees stated for it |
|---|---|---|---|---|
| Ona Health | Signed by the practice inside the product, and Ona keeps a record of who signed it and when | At workspace creation, before patient data is entered | No standalone agreement page is published; the commitment is stated on /features/team-security | None stated |
| SimplePractice | Published agreement that amends and is made part of the Terms of Service, naming you as Covered Entity and SimplePractice LLC as Business Associate | "at the date and time your SimplePractice account is created" | No effective or last-updated date shown on the page | None stated |
| Healthie | Published agreement, made and entered into when the account is created | "at the date and time your Healthie account is created" | "Effective as of May 25, 2018" | None stated |
| Tebra | Incorporated into the Terms of Service for customers that are covered entities and give Tebra PHI | From the Activation Date, which the agreement references but does not define | "Last Updated: March 17, 2025" | Time-and-materials fees possible under section 2.12 for accounting-of-disclosures work and for carrying out your Privacy Rule obligations (sections 2.8 to 2.11), after an estimate and mutual agreement; patient access and amendment are delivered through the product with no fee stated |
Two columns carry the weight. Whether a signature is recorded against a named person is what you produce when somebody asks who agreed and on what date. And the Tebra row shows that a BAA free to have can still carry a charge for the work the rule makes the vendor do: its fee clause reaches the accounting of disclosures and any of your Privacy Rule obligations it takes on, while patient access and amendment come through the product at no stated fee. Read the fee clause, not the headline.
What to check during the trial
The 14-day free trial needs no credit card, so you can inspect the compliance surface before a patient exists in the system. Four checks, all on published behaviour.
Confirm the signature was recorded. The BAA is signed at workspace creation and Ona keeps who signed it and when. Find that record and screenshot it.
Open the activity log. Owners and admins see who opened, searched, exported, signed or changed a record across the last 7, 30 or 90 days, and each patient chart has its own Record activity panel, where admins see who opened or changed that chart. This is the evidence behind an accounting request, so look while the stakes are zero.
Set the roles the way you will actually run. Give the front desk a Staff seat and confirm it works without Settings access, then that a Clinician seat sees its own patients. Permissions are fixed per role.
Delete something on purpose. A recording deleted permanently loses its audio and its transcript. The return-or-destroy obligation in 164.504(e)(2)(ii)(J) is easier to reason about once you have watched deletion behave.
Three honest limits, because finding them after signing is worse. The activity log cannot be exported today. Two-step sign-in cannot be required across the whole practice, only switched on per person. There is no SAML single sign-on and no custom roles. If any of the three is a hard requirement from your security reviewer, raise it on the call, not after the migration.
Related reading: HIPAA-compliant platforms for solo and group practices for the shortlist question, HIPAA-compliant practice software for the shortlist-and-checklist question of which safeguards to verify with any vendor, and team roles and security for roles, sign-in and the activity log.
Frequently asked questions
Will Ona Health sign a BAA?
Yes. Ona Health signs a business associate agreement with every practice before patient data is entered. The agreement is signed when the workspace is created, and Ona keeps a record of who signed it and when. There is no separate request to file, no approval queue and no fee for it, and it does not depend on how many seats you buy.
What does a business associate agreement actually cover?
45 CFR 164.504(e)(2) sets the contents. The agreement establishes the permitted and required uses and disclosures of PHI, and commits the vendor to use appropriate safeguards, to report any use or disclosure not provided for by the contract, to bind its own subcontractors to the same restrictions, to make PHI available for patient access, amendment and an accounting of disclosures, to open its books to the Secretary, and at termination to return or destroy the PHI it still holds if that is feasible. It must also let the practice terminate for a material breach.
Is Ona Health HIPAA certified?
No, and Ona Health claims no certification of any kind. What the rule asks for is a contract, not a certificate: 45 CFR 164.504(e) sets out what the agreement must say and names no certifying body. Treat a compliance badge on any vendor's website as marketing. The signed agreement, the roles that decide who can open a record and the log of who did open it are the things you can actually check.
Do I need a separate BAA with Stedi or the clearinghouse?
Not for Ona Clearing House. It runs on Stedi, and Ona publishes that there is no separate clearinghouse account to open and no separate contract to sign, and the volume is metered on a Clearing House plan from $69 a month. Under 45 CFR 164.504(e)(5) a subcontractor that handles PHI on a business associate's behalf has to agree to the same restrictions, so that link in the chain sits between Ona and Stedi rather than on your desk. The exception is a clearinghouse you bring yourself: Ona lets a practice connect its own Claim.MD account with an API key, and that is your vendor relationship and your BAA to sign.
Is a signed Notice of Privacy Practices the same as a BAA?
No. A Notice of Privacy Practices and a HIPAA authorization are documents between the practice and the patient. A BAA is a contract between the practice and a vendor. Ona ships both documents in its consent library and records the time, the IP address, the browser and device, the exact wording, which boxes were ticked and a SHA-256 hash of the document for each one signed. None of that is a BAA, and a chart full of signed notices does not give you one.
Can I see the BAA before I enter patient data?
Yes. The agreement is signed when the workspace is created, which happens at the start of the 14-day free trial, and the trial needs no credit card. Ona does not publish the text of the agreement at a public URL today, so if your counsel wants to read it before anyone signs, ask for a copy at [email protected] and review it outside the product.
Next step
Bring your security reviewer to the call and work down their list with the product open. Book a 15-minute demo, or start the 14-day free trial with full access to every feature and no credit card. If the activity log export or practice-wide two-step sign-in is a requirement you cannot waive, say so first and we will tell you straight where Ona stands today.

Written by
Ona Health team