Can an AI Agent Have Its Own Cerbo User Account? HIPAA and the Cerbo Agreement

Is It Allowed to Give an AI Agent Its Own Cerbo User Account?

HIPAA on its own does not forbid giving an AI agent its own Cerbo user account, but your Cerbo agreement does, unless Cerbo says yes in writing. Cerbo's Master Subscription Agreement, last revised October 30, 2026, says clients and their users shall not access or interact with Cerbo using any artificial intelligence agent, automated tool or similar technology, except as expressly permitted by Providi (the contracting company, Cerbo, LLC for Cerbo products) in writing or through features made available within Cerbo. On the HIPAA side, HHS says the Security Rule requires access controls, audit controls and authentication for anyone touching electronic patient data, and any outside vendor whose software handles that data for you is generally a business associate that must sign a BAA. So the honest answer for a physician owner is that a separate AI login in Cerbo needs Cerbo's written permission first, and the agreement exempts features made available within Cerbo, such as its AI Scribe. It also lists the CerboOM API among the services, but no clause names AI use through API credentials. The agreement still applies whichever account a tool uses, so review yours with counsel. Tabflows fits a different route, as a dedicated tech team whose workflows are started by a named person on your team inside that person's own signed-in session, so it never asks for a Cerbo account of its own.

The rest of this guide explains what Cerbo's agreement says line by line, what HIPAA asks of you, what each option costs on Cerbo's own price list, and how to decide. It is a plain reading for practice owners, not legal advice. Every Cerbo fact comes from Cerbo's agreement, pricing page and help center as published on November 2, 2026, and every HIPAA fact comes from HHS.

What Your Cerbo Agreement Says About Users and AI Agents

Cerbo's Master Subscription Agreement covers the EHR, practice management, patient portal, the CerboOM API, the mobile app and its documentation, transcription and workflow tools. Several clauses bear directly on an AI agent with its own login.

• Who counts as a user. Section 2(a) defines Users as employees, contractors or agents the client has authorized to access and use the services.
• One user per subscription. Section 2(b)(i) says the services are accessed through user subscriptions, by no more than the specified number of users, and that subscriptions may not be shared or used by more than one user. Cerbo can agree in writing to a shared account only where the users will not access PHI, or where the client takes full responsibility for detailed access logs for everyone using it.
• New users are billed right away. The same section says you can add users at any time and billing for newly added users is effective immediately.
• No shared credentials. Section 2(g)(ix) bars sharing access credentials, allowing shared use of user logins or exceeding the agreed number of users.
• No AI agents without permission. Section 2(g)(xxiii) bars accessing or interacting with the services using any artificial intelligence agent, automated tool or similar technology, except as Cerbo expressly permits in writing or through features within the services.
• No robots or scrapers. Section 2(g)(xxiv) bars any robot, spider, scraper or other automatic device or process used to access, scrape or mine the services.
• No hidden identity. Section 2(g)(xxv) bars accessing the services in ways that mask, rotate, spoof or otherwise obscure the user's IP address or identity.
• No training on Cerbo data. Section 2(g)(xxii) bars using data or outputs from the services to train, fine-tune or develop any AI model without Cerbo's prior written consent.

Taken together, the agreement treats a new AI login as a permission question first and a billing question second. An agent can't simply be added like a new medical assistant, because Section 2(g)(xxiii) applies whether it uses its own account or someone else's. The clauses also say nothing against the clinic using software in general. They are written to keep access tied to known people and to Cerbo-approved routes, which is a reasonable thing for an EHR holding your patients' records to want.

What HIPAA Requires When Software Touches Patient Data

HIPAA does not name AI agents, but the Security Rule's safeguards apply to whatever touches electronic protected health information. HHS's summary of the Security Rule lists these technical safeguards.

• Access control. Technical policies and procedures that allow only authorized persons to access ePHI.
• Audit controls. Hardware, software or procedural mechanisms that record and examine activity in systems containing ePHI.
• Integrity. Measures to make sure ePHI is not improperly altered or destroyed.
• Authentication. Procedures to verify that a person seeking access to ePHI is who they say they are.
• Transmission security. Measures that guard against unauthorized access to ePHI sent over a network.

HHS also requires a risk analysis and workforce security policies so that people who work with ePHI have appropriate authorization and supervision. An AI login with broad permissions and no clear owner makes each of those harder to show, which is why the questions below focus on who started an action and who can see it afterward.

The business associate rules matter just as much. HHS's business associate guidance says a business associate is generally a person or organization, other than a workforce member, that performs functions or services for a covered entity involving the use or disclosure of PHI, and that a covered entity may share PHI with one only after getting satisfactory assurances in a business associate agreement. HHS notes the "conduit" exception is narrow and covers transmission services only, not vendors that access PHI regularly to perform a service. An AI vendor that reads your Cerbo charts is not a conduit. Cerbo's own agreement makes Cerbo your business associate and incorporates its BAA, but that BAA covers Cerbo, not an outside AI tool. As Aptible's guide to HIPAA-compliant AI puts it, no AI product is inherently HIPAA compliant, and compliance depends on how the organization implements and governs the system.

Comparing Your Options

Here is how the realistic routes compare for a Cerbo practice. Prices are from Cerbo's pricing page, dated in the Sources section below.

• Share a staff login with an AI tool. Cerbo agreement: barred by 2(g)(ix) and 2(g)(xxiii). HIPAA angle: breaks the one-person audit trail. Cerbo cost: none extra.
• Dedicated Cerbo user for the AI. Cerbo agreement: needs Cerbo's written OK. HIPAA angle: needs a vendor BAA and a clear owner. Cerbo cost: $63 per month for an Additional Staff user, or the one-time Restricted Access User fee below.
• Cerbo API user for a vendor. Cerbo agreement: still applies, whichever account it uses; review yours with counsel. HIPAA angle: the Superadmin answers for the vendor. Cerbo cost: not listed on the pricing page.
• Cerbo AI Scribe. Cerbo agreement: a built-in Cerbo feature. HIPAA angle: covered by Cerbo's BAA. Cerbo cost: $29 or $59 per provider per month.
• Tool a named person starts in their own session. Cerbo agreement: still applies, whichever account it uses; review yours with counsel and ask the vendor how it works. HIPAA angle: needs a vendor BAA. Cerbo cost: none extra.

Sharing an existing login

This is the quickest shortcut and the one the agreement closes most clearly. It also leaves your audit log showing a person doing work they didn't do, which is the opposite of what HHS's audit control and authentication safeguards are for.

A dedicated Cerbo user for the agent

A separate account is better for your logs, and on Cerbo's price list a full-time Additional Staff user is $63 per month ($39 part-time, in multi-provider clinics), while a Restricted Access User is a $15 one-time fee with options for scheduling and billing and no access to charting. Some visits to that page also show a one-time setup fee of $1,195, or $595 for a new part-time solo or micro practice (seen November 4, 2026), and others show none. The agreement still requires Cerbo's written permission before an AI agent uses that account, so ask Cerbo first and keep the answer on file.

Cerbo's open API

Cerbo's API User Management help article says a Superadmin creates API credentials under Admin, Manage, Integrations, gives each set a nickname and description, and picks a permission profile that limits which endpoints it can reach, with Cerbo recommending the most restricted profile that still does the job. The same article says the Superadmin is responsible for ensuring the third party complies with Cerbo policies and HIPAA, and for any breach by that third party. That is a real responsibility to weigh before you hand API keys to an AI vendor. Cerbo's agreement lists the CerboOM API among the services and exempts features made available within the services, but no clause names AI use through API credentials. The agreement still applies whichever account a tool uses, so review yours with counsel.

Cerbo AI Scribe

If what you need is help with notes, Cerbo's own AI Scribe add-on is listed at $29 per provider per month for up to 60 notes, or $59 per provider per month with no monthly note limit, with a consent prompt in the workflow and notes in the chart for provider review. It is a feature inside Cerbo, so it does not raise the outside-agent question.

A tool that runs inside a real person's session

The last route never creates a new identity in Cerbo. A named person on your team starts each workflow from their own signed-in session, and the tool helps with the work between screens. Ask any vendor in this category whether it stores your Cerbo password, whether it ever acts without a person starting it, whether it masks who did what, and whether it trains models on your data, because those map directly onto Sections 2(g)(ix), (xxii), (xxiii) and (xxv).

A Checklist Before Any AI Touches Your Cerbo Charts

1. Ask Cerbo in writing. If the plan gives an AI agent its own Cerbo account, email Cerbo, cite Section 2(g)(xxiii), describe what the tool will do, and keep the reply. For an API user or a tool a named person starts in their own session, the agreement still applies whichever account it uses, so review yours with counsel.
2. Sign a BAA with the AI vendor. Do this before any patient data moves, separately from your Cerbo BAA.
3. Use the narrowest access. For API work, pick the most restricted permission profile, and for any user account, the lowest role that does the job.
4. Keep one person per action. Make sure every action can be traced to a named person or a named integration, never a shared login.
5. Add it to your risk analysis. Note the tool, what data it reaches and how you would turn it off, as HHS's risk analysis requirement expects. Our HIPAA Security Rule guide covers that process.

Where Tabflows Fits

Tabflows is a dedicated tech team and smart admin infrastructure for DPC, concierge, functional and integrative medicine clinics. It is not an EHR and does not replace Cerbo. It works across the tools you already use, such as Cerbo, Spruce, Hint and Google Workspace, and turns the work between them into tracked tasks and automations that the team sets up and runs for you.

On the account question, Tabflows does not log into Cerbo as its own user. Its workflows are initiated by an authorized person on your team and run inside that person's own signed-in session, Tabflows does not store Cerbo or other EHR credentials, it does not independently start access to Cerbo, its activity is tied back to the named person who started it, and it does not train AI models on patient data or bulk scrape EHR records. Tabflows signs a BAA by default. The full product facts, written for owners, vendors and counsel, are on our user-initiated EHR workflow page. Those facts describe how the product works rather than interpret your contract, so review your own Cerbo agreement with counsel.

You can see how Tabflows works alongside Cerbo on the Cerbo integration page, read how integrative practices use it in our Cerbo workflow guide, or check the compliance page for security details.

A Natural Next Step

If you are weighing an AI tool against your Cerbo agreement, start with the work you want off your plate rather than the login it would need. Tell us about your practice and we will show you which of those jobs can be handled with your team's own access, a signed BAA and no new Cerbo account.

Sources

Checked on November 4, 2026: cer.bo/pricing. Spot a wrong fact? Email a correction.