1. An SEO plugin on 4 million WordPress sites was caught minting itself an admin password — and it doesn't expire

Why it matters for an independent practice: If a client practice runs WordPress — and most do — there is a real chance this credential exists on their site right now, granting a third party's AI agent the ability to publish, edit or delete on a site that carries medical claims and patient-facing content. That is a HIPAA-adjacent governance question even with zero PHI on the box: someone outside your BAA can write in your doctor's name. Two actions this week: audit Application Passwords on every client site, and add "what credentials does this create, and can I revoke them?" to the intake checklist for any plugin or AI tool. This is the same vendor-diligence muscle the ECRI item asked for on Aug 30, applied to the marketing stack instead of the clinical one.

Why it matters for an independent practice: This reframes patient communication from a marketing question into a security control, which is unusually useful for MMR. The practices most vulnerable here are the ones sending bland, templated, unsigned blasts — because their patients have nothing to compare a fake against. The deliverable is concrete: a consistent sender identity and from-address, a real signature, a stated "we will never ask you for payment details by email" line, and a one-page "how to tell a real message from us" page on the site that you can link in every send. That page doubles as an AI-search-citable trust asset. And the pre-written impersonation response belongs in the client's playbook now, not the morning it happens.

Why it matters for an independent practice: Zero medical content, and it maps almost exactly onto a practice. First: the AI assistant that worked was the one built on their own proprietary operating data and pointed at a specific job a specific person does with their hands — the practice equivalent is not a general chatbot but a front-desk or MA assistant grounded in your protocols, your fee schedule, your intake forms. Second: they trained the model on the judgment of their most experienced operators, which is the argument for capturing your best staff member's decision-making before you automate around it. Third, and the one most practices skip — Caterpillar budgeted a training line item and named the role change out loud (doing → supervising). If an MMR client buys an AI receptionist and does not budget for retraining the person who used to answer the phone into the person who now audits it, the deployment fails for workflow reasons, not model reasons. That is also the honest pricing conversation: the implementation and training are the deliverable.

Why it matters for an independent practice: Scheduling is the single highest-friction, highest-leverage automation in a practice, and it is also the one most practices rent — Calendly, the booking widget bundled into the EHR, whatever the last agency installed. A self-hosted booking flow you control means the patient data, the confirmation copy, the reminder cadence and the follow-up trigger all sit inside systems you own, which is both an independence argument and a stewardship one after item 1. Worth a 14-minute watch before the next client asks for booking automation — even if the answer is "we'll buy it instead," you want to know what you're buying.