Dental and medical offices: what an AI agent can and can't do with your software

• Last verified October 28, 2026
• Updated Oct 28, 2026Published Oct 28, 2026

A small independent practice, whether a general dentist, an orthodontist or a family medicine office, tends to run on a short list of rented systems: practice management software or an EHR that holds the schedule, charts and claims, a patient reminder and texting service, a card processor, QuickBooks for the books, and sometimes a marketing CRM. This guide sorts out which of those Muse, Meta's assistant, or a similar connector-driven agent can get into right now, which front-office jobs are reasonable to give it, and why anything that touches patient information has to clear HIPAA first. It's written for practices with one to a few locations. Hospitals, health systems, pharmacies, labs and health plans are out of scope, and so is choosing clinical software.

Look for the badge beside each claim; it tells you what kind of source supports the statement:

How this page was put together: we went through dental and medical software vendors' developer pages and API terms, the HIPAA, security and privacy pages of the payment, accounting, CRM and automation tools listed here, Meta's Muse terms and privacy policy, HHS's HIPAA regulations on eCFR and one HHS guidance page, the FTC's Health Breach Notification Rule, an FCC rule and its Federal Register amendment, and OSHA's bloodborne pathogens standard. Every source shows the date we read it. No assistant, Muse included, was hooked up to a live practice system, patient list, card account or ledger, didn't send a patient message, and no tool was tested. Vendor documentation describes intended behavior; it can't settle whether your practice may lawfully use a tool that way.

Short version

• Among Muse connectors, Meta's launch post lists HighLevel, Stripe and Intuit QuickBooks and names no practice management, EHR or reminder product; for the complete roster Meta sends readers to the Muse app, which we didn't check. (Confirmed by vendor 1)
• Meta's Muse terms, Muse privacy policy and Muse privacy help page, as we read them on Oct 28, 2026, say nothing about HIPAA, protected health information or a business associate agreement. The privacy policy says the setting that lets Meta use your interactions to improve its AI starts switched on, and that those interactions can include information Muse pulls from Connectors. (Confirmed by vendor 8)
• Under HHS's HIPAA rules, an outside company that creates, receives, maintains or transmits protected health information for a practice is a business associate, and the practice must have written satisfactory assurances, a business associate agreement, before letting it handle that information. (Confirmed by HHS 21 22) HHS's cloud guidance adds that a cloud provider storing such data is a business associate even when the data is encrypted and the provider holds no key. (Confirmed by HHS 20) Don't connect a chart, schedule or patient list to an assistant whose maker hasn't signed one with you.
• Intuit says QuickBooks Online is not HIPAA compliant and advises health care professionals not to enter individually identifiable health information. Zapier says it isn't HIPAA compliant and doesn't sign BAAs. Stripe's services agreement bars sending it protected health information as part of data from your other providers. HighLevel offers a BAA only through a paid HIPAA add-on. (Confirmed by vendor 18 19 17 16)
• The FCC lets a healthcare provider send free-to-the-patient appointment reminders and similar texts to cell phones without the usual consent, but only for listed purposes, with no billing or marketing content, at most one a day and three a week, and with STOP honored immediately. Separate opt-out changes for other consent-based calls and texts take effect Nov 25, 2026. (Confirmed by the FCC 27 28)

Stack map

Swipe the table sideways to see every column →

If you want a custom connector

For anything Meta doesn't list, someone has to build the bridge: an MCP server the vendor runs, a developer integration through the vendor's API program, or a middle layer such as NexHealth. In a practice, the first question isn't technical. HHS's definition of a business associate covers practice management among the services it lists, and it reaches subcontractors that handle the data for a business associate. (Confirmed by HHS 21) So every hop that sees patient data, the vendor, any middle layer and the assistant itself, needs its own agreement. Meta's help center says it doesn't vet custom connectors or how they treat your data, and that what Muse learned can remain in its memory and chat history after you disconnect. (Confirmed by vendor 2) Muse's builder guidelines require a fresh approval for each sensitive write, with no standing permission allowed. (Confirmed by vendor 3) We found no Meta statement offering to sign a BAA for Muse; ask Meta in writing before any patient data goes near it. (Unverified)

Jobs you could hand off today

These keep patient information out of the assistant.

Swipe the table sideways to see every column →

None of these has been tried by us. Plans, staff permissions and connector settings all change the outcome, so begin with a handful of records and check each result by hand.

Keep these out

• Charts, schedules, patient lists and claims. Until every party that will see the data, including the assistant's maker, has signed a BAA with you, don't connect your practice management system or EHR to an AI assistant, and don't paste patient details into a chat.
• Clinical calls. Muse's terms forbid using it to decide, without meaningful human review, whether someone gets or keeps healthcare, or in ways that amount to unlicensed medical activity, and state that Muse doesn't give medical advice. (Confirmed by vendor 8) Diagnosis, treatment plans, prescriptions and triage stay with licensed staff.
• Patient texting at scale. Muse's terms also bar bulk calls or messages sent without the consent telecommunications laws such as the TCPA require. (Confirmed by vendor 8) Use your reminder vendor, under its BAA, and the rules below.
• Refunds and patient balances. Stripe makes a person click through and confirm a refund or outbound payment before its MCP completes it. (Confirmed by vendor 7) Billing questions belong with your front desk.
• Breach decisions. Whether a lost laptop or a misrouted message is a reportable breach is a judgment for the owner and the practice's privacy officer, not an agent.
• State law. We didn't check state health privacy, dental board or medical board rules, or state texting laws, for this page. (Unverified)

Risks to keep a person on

Patient data and business associate agreements

HIPAA covers a health care provider who sends health information electronically in connection with a transaction HHS's rules cover. (Confirmed by HHS 21) That is how most practices that bill insurance electronically become covered entities. A covered entity may let a business associate handle protected health information only after getting satisfactory assurance, documented in a written contract, that it will safeguard it. That contract has to limit what the business associate may do with the information, require it to use appropriate safeguards and follow the Security Rule for electronic data, report breaches of unsecured information, bind its subcontractors to the same terms, and return or destroy the information when the contract ends where that's feasible. (Confirmed by HHS 22) HHS says a practice that uses a cloud provider for electronic patient data without a BAA is violating the HIPAA Rules, that its Office for Civil Rights doesn't endorse or certify any product, and that the narrow conduit exception covers only services that do nothing but transmit data. (Confirmed by HHS 20)

Outside of treatment and a few other listed cases, a practice and its business associates must make reasonable efforts to limit protected health information to the minimum needed for the purpose. (Confirmed by HHS 22) Even with every agreement in place, give an agent only the fields a task needs.

Security Rule safeguards

The Security Rule requires an accurate and thorough risk analysis and measures that bring risks to electronic patient data down to a reasonable level, a regular review of system activity records such as audit logs and access reports, and technical controls covering access, unique user IDs, audit records, confirming who is signing in, and protecting data in transit. (Confirmed by HHS 23) Adding an AI assistant, connector or middle layer changes your risk analysis, so update it first. A shared login used by an agent defeats the unique user ID point.

When something goes wrong

An improper use or disclosure of protected health information is presumed to be a breach unless a risk assessment of at least four listed factors shows a low probability that the information was compromised. Affected patients must be told without unreasonable delay and within 60 calendar days of discovery. A breach involving more than 500 residents of a state or jurisdiction also requires notice to prominent media there, and HHS must be told at the same time for 500 or more people, or in a yearly log within 60 days after the calendar year ends for fewer. A business associate has to tell the practice within 60 days of discovering one. (Confirmed by HHS 24) If an agent sends patient data somewhere it shouldn't, that clock may already be running.

Patient marketing

Using patient information for marketing generally needs the patient's written authorization, but HHS's definition of marketing leaves out, among other things, communications about the patient's own treatment and about the practice's own health-related services when nobody pays the practice to send them. (Confirmed by HHS 25) A recall reminder is different from a promotion for teeth whitening sent on a vendor's dime, and an agent shouldn't decide which side of that line a message falls on.

Health apps outside HIPAA

The FTC's Health Breach Notification Rule doesn't apply to HIPAA-covered entities or to a business associate acting as one. It covers vendors of personal health records, related entities and their service providers, where a personal health record is an electronic record able to draw on multiple sources and managed, shared and controlled by or mainly for the individual. A covered breach requires notice to the people affected, the FTC and, in some cases, the media, and violations are treated as violations of an FTC rule. (Confirmed by the FTC 26) For a typical practice that bills insurance, HIPAA is the rule that applies. This one matters if you also run a cash-only wellness or health app outside your HIPAA practice.

Reminder and recall texts

The FCC's robocall rule normally requires prior express consent before autodialed or prerecorded calls and texts to a cell phone. Its healthcare exemption allows them when the patient isn't charged and every condition is met: sent only to the number the patient gave, naming the provider and its contact details, limited to purposes such as appointment confirmations and reminders, wellness checkups, lab results, prescription notifications and post-discharge follow-up, with no telemarketing or billing content, compliant with HIPAA's privacy rules, no longer than 160 characters for a text, no more than one a day and three a week per patient, and with a reply of STOP honored immediately. (Confirmed by the FCC 27) Prerecorded or autodialed advertising calls to cell phones need written consent, but the rule exempts a call delivering a health care message from a covered entity or its business associate, as HIPAA defines them. (Confirmed by the FCC 27)

For calls and texts that rely on consent, the FCC's amended opt-out rules apply from Nov 25, 2026. A caller may designate a single exclusive method for withdrawing consent, such as a reply word, a key press or a website or number it names, provided its calls and texts disclose that method; a caller that names nothing has to honor any reasonable request. Each revocation gets ten business days to take effect, a stop reply to an informational message may be limited to that type of message, and a one-time confirmation of the opt-out is allowed if it contains nothing promotional. (Confirmed by the FCC 28) The amendment leaves the healthcare exemption's own STOP rule untouched. (Confirmed by the FCC 28) Don't let an agent edit your reminder vendor's opt-out keywords, add billing lines to reminders or move patients onto a promotional list.

Bloodborne pathogens records

OSHA's bloodborne pathogens standard requires a written exposure control plan for employers with occupational exposure, kept confidential employee medical records that can't be disclosed without the employee's express written consent and must be kept for at least the length of employment plus 30 years, training records kept for 3 years, and, where required, a sharps injury log kept in a way that protects the injured employee's confidentiality. (Confirmed by OSHA 29) An assistant can remind you of deadlines. It shouldn't hold or summarize those records.

Treat this page as a summary of published sources, not as legal, medical, privacy or compliance advice. Your state, your licensing board, your payer contracts and your own software agreements may impose more than what's covered here, so talk to a healthcare privacy lawyer before connecting any system that holds patient information.

FAQ

Can Muse connect to Open Dental or Dentrix?

Meta's launch post doesn't name either one. Open Dental publishes a REST API that offices enable with keys, and Dentrix opens its API only to developers who join Henry Schein One's program and sign its agreement. (Confirmed by vendor 1 9 10) Whether either should be connected comes down to the BAA question above.

Isn't encryption enough?

Does turning off AI training make Muse safe for patient data?

Muse's privacy policy says the Data controls setting decides whether your interactions are used to improve Meta's AI, and the terms say Meta may access and keep logs of actions Muse takes. (Confirmed by vendor 8) Turning training off doesn't stand in for a business associate agreement.

What does Zapier cost here?

Every successful MCP tool call through Zapier counts as two tasks on your plan. (Confirmed by vendor 5) Zapier also tells healthcare users not to automate anything that involves protected health information with it. (Confirmed by vendor 19)

Changes to this page

Swipe the table sideways to see every column →

Found a mistake or a newer source? Send it through Corrections, with a link to the source, and we'll recheck the claim and record the change here.