🚀 Meet Us at HIMSS 2026 | March 9–12, 2026 | Las Vegas, NV 🎉
Most conversations about AI in healthcare focus on the technology itself, what it can do, how accurate it is, what it costs. What almost never gets discussed is the work that happens before any of that matters: who inside a healthcare organization drives AI adoption, what they actually do, and why so many rollouts fail without the right people in the right roles.
So we spoke to Amanda McFayden, Director of Clinical Operations at DENT Neurologic Institute, one of the largest outpatient neuroscience centers in the country. Amanda has been at DENT for nearly 20 years, working through almost every part of the organization before reaching her current role. She has seen healthcare technology evolve across two decades, and over the past few quarters, she led the adoption and rollout of Marvix AI at DENT, with 80 of the 100+ providers using Marvix and growing.
In this conversation, we spoke across multiple topics ranging from role of AI in neurology, how does the adoption become a success, role of administration and senior leadership in the successful rollout of AI, and more. Here's her candid take across these topics
AI stopped being optional for organizations like DENT - The administrative burden on providers had reached a point where something had to change. Documentation requirements kept growing, insurance authorizations kept getting harder, and staffing gaps from COVID never fully closed. The senior leadership at DENT recognized that absorbing this through EMR triggers and workarounds was not going to hold for a long time.
Their motivation was clear - Reduce provider burnout driven by documentation overload. AI scribes proved to be the likely answer. They not just saved time on documentation, but better documentation also meant stronger insurance authorization outcomes downstream. However, burnout was the primary problem they were solving for.
If you are evaluating AI for your practice:
Even before speaking to a single vendor, DENT's senior leadership and strategic development team sat down and defined what they actually needed. Amanda highlighted a structured checklist with two non-negotiable must-haves: customization at the provider level and two-way EMR integration.
Customization mattered because outpatient neurology covers a wide range of subspecialties, and each provider has their own clinical voice and note style. A tool that flattened that into a fixed template was never going to get a buy-in. Two-way EMR integration mattered because most neurology visits are follow-ups, and without the ability to pull previous visit summaries into the current note, the AI scribe is doing only half the job.
DENT piloted other solutions before landing on Marvix. The tools that failed did so because providers said the notes did not sound like them. And once that trust breaks, training does not recover it.
If you are building your evaluation criteria:
Signing up with a vendor is where the hard work begins. Amanda started with seven to eight provider champions chosen deliberately across physician types and subspecialties, testing whether the tool could handle the real range of how DENT providers work. Once that pilot group was seeing results, their peers took notice. Providers watching colleagues take lunch and stop post-charting at night did more for adoption than any formal rollout campaign could.
She handled resistant providers by running short optional demos scheduled outside of clinic hours, tracked training completion individually, and followed up with anyone who had not finished their setup. That operational discipline from the client side is what separates a tool that gets adopted from one that stalls.
If you are rolling out AI in your practice:
Amanda's internal playbook started with three questions the team worked through before anything else - Why are we integrating an AI scribe, What is our start point and What is expected of our providers. They also looked hard at the cost, not just the tool cost but the integration cost as well and what the organization would need providers to do differently to make the investment worthwhile.
They ran surveys throughout the pilot to check whether the tool was actually reducing burnout, asking providers directly about fatigue and end-of-day workload. They built in formal sign-off steps so providers acknowledged what the ambient AI scribe was doing in their workflow. Long-term success for DENT meant reduced provider turnover and improved satisfaction over time, and Amanda's view is that the cost of losing an experienced provider to burnout far exceeds the cost of a tool that could have prevented it.
While building your internal playbook:
Neurology is a hard environment for any ambient AI scribe. The clinical language is complex, subspecialty terminology varies, and providers differ significantly in how they speak and how they prefer their notes to read. The tools that failed DENT's evaluation did so because they could not handle that variation.
What worked for Marvix was a combination of clinical quality documentation out of the box and the ability to customize the notes and templates at a provider levvel. Any corrections to names and spellings persist across all future notes, which matters in neurology where medication terminology is often unusual. Note sensitivity and output style can be adjusted at a provider level. And when DENT shared feedback, Marvix built it back into the product. That responsiveness is what Amanda identifies as the real differentiator between an AI company worth working with and one that is not.
What to look for in an AI vendor:
Integration is often treated as a technical checkbox when in reality it determines how much value an ambient AI scribe can actually deliver. DENT started without full integration during the pilot, and even then providers found the tool better than their previous workflow. Once full integration went live, the Marvix summarizer began pulling previous visit summaries into the current note, and that changed the pre-charting and post-charting dynamic significantly for follow-up visits.
The Marvix E/M coding recommendations and ICD-10 suggestions that surface from the visit note also proved useful, particularly for newer providers without formal billing and coding training. Marvix surfaces the rationale alongside the suggestion, making the provider's review faster without replacing their judgment. Amanda describes the integration itself as one of the smoothest DENT has done across any technology layered over their EMR.
Amanda's core point is that AI adoption in a large practice is an operational challenge, not a technical one. It requires sustained hands-on involvement from the administration team and senior leadership that most organizations underestimate. Providers need relationships, not memos. They need someone they can go to when they do not know how to articulate what they need from the tool. They need training that works around their schedule.
This role does not need to be a director. Even a clinic manager managing the day-to-day operations can own it.
For clinical operators starting this process:
The clips above cover some of the most valuable insights from the conversation with Amanda. For the full context, additional stories, and deeper discussion around practice management and leadership, watch the complete podcast below.
Amanda's view is that healthcare organizations in 2026 do not have the luxury of waiting. Payers are not getting easier, the staffing environment has not stabilized, and the administrative load on providers is not going to reduce by itself. Her advice is to re-evaluate your processes and tools at least once a year and be honest about whether what you have is still the right fit.
The gap between a successful AI rollout and a failed one is almost never the technology. It is whether the organization has the right people, with the right relationships, doing the operational work that adoption actually requires. Amanda and her team at DENT are a strong example of what that looks like in practice.
If you are interested in exploring Marvix AI for your practice, book your demo today.
.png)
