Ari Yampolsky, partner at Whistleblower Partners LLP, opened the Friday morning session at RISE West with James M. Taylor, M.D., on Sept. 4 in San Diego. Dr. Taylor is a family practice physician, a certified coder, an EPIC certified physician builder, and a former elected board chair of a large physician group. He is also a relator in a landmark False Claims Act case involving early Medicare Advantage risk adjustment practices, resolved in January with no admission of wrongdoing or liability.
The case gave the session its reason to exist, but it supplied almost none of the hour. Yampolsky pointed the conversation at a harder question for the people in the seats. How does an organization full of people who come to work in good faith, with nobody trying to commit fraud, end up somewhere it never intended to go?
One frame is worth holding through everything below. The operating period Dr. Taylor described runs from the mid-2000s into the early 2010s, the first decade of risk adjusted payment, and the litigation ran for years after that. Nearly everything the industry now treats as table stakes arrived later. Risk adjustment coding credentials, compliance functions built around encounter data, standing internal audit programs, RADV readiness work, and vendor oversight expectations were new or absent. Organizations across the market were assembling the discipline while the program was already running, and most of them have rebuilt it several times since. Read this as a portrait of an era, not a description of any company today.
Drift is gentle, which is what makes it work
Dr. Taylor answered with snorkeling.
He was in Hawaii, watching sea turtles, fully absorbed. The current was mild and steady and gave him nothing to notice. When he finally lifted his head, the boat and the shoreline were a long way off. No single moment took him there.
Organizational drift works the same way. No meeting convenes to cross a line. Alignment loosens by degrees, through decisions each defensible on its own, in an organization no longer curious about where it sits relative to where it started. Vigilance is the thing being lost, and its absence is quiet.
He was generous about the people around him, and he made the point twice. Committed, mission-driven, in the building for the right reasons, and none of them trying to commit fraud. His whole interest is in how capable organizations full of exactly those people end up off course anyway.
A tether does not stop you from moving
The counterweight is unglamorous. Guardrails, checkpoints, second signatures, the audit nobody wants on the calendar. All of it reads as friction to the people working under it.
Dr. Taylor put the reframe in one line the room wrote down. "The tether doesn't stop me from moving. It stops me from drifting."
Ranch houses and skyscrapers
Much of the drift he described traces back to a business model change and the tools available at the time.
Moving from a traditional HMO built on premiums and copays into fee-for-service arrangements and Medicare Advantage is not a change of degree. Risk adjusted revenue arrives with documentation, coding, and audit obligations attached, and the operating muscles are different. His framing: if you are good at building ranch houses and someone asks you for a skyscraper, expect to need different tools.
The industry supplied few of them then, and the gap was general rather than local. Professional associations were slow to treat Medicare Advantage risk adjustment as its own discipline, and the Certified Risk Adjustment Coder credential arrived years after plans were already submitting data. Regulators were learning the mechanics alongside everyone else. Compliance leaders across the market were handed oversight of coding operations without coding backgrounds, and staffing models had no precedent to copy. Technology carried the same inheritance, with systems designed for one payment model taking on documentation questions nobody had built them to answer. The validation layers standard in today's platforms came out of that generation of hard lessons.
The target and the documentation have to be in the same conversation
One sequence he described will sound familiar to anyone who has sat through a budget cycle. Finance sets the revenue expectation, and operations receive the assignment of finding it.
His point is a design point. Revenue targets set without reference to what the documentation supports become a compliance input, whether or not anyone intends them as one. Nothing about the dynamic belongs to a single organization, which is why he keeps describing it to rooms where people recognize it.
The follow-up is the control
The pattern in Dr. Taylor's telling was rarely a missing control. It was a control without a follow-up loop attached.
Corrective action plans get written and filed, and the later audit confirming they worked is the step most likely to go missing. Few organizations had built that loop in the period he described. His two lines on feedback landed as a pair. Feedback is a gift. An answer given to a question nobody asked is noise. Leadership has to go looking for the first one and stop mistaking silence for the second.
Which is where he put accountability, and he put it at the top. Error rates do not belong to a department. They reflect what leadership tolerates. What you permit you promote.
A captain prefers a false alarm to no alarm
Yampolsky steered the back half toward escalation, and Dr. Taylor took it to Master and Commander. A captain wants the lookout shouting. A false alarm costs a few minutes of embarrassment. No alarm costs the ship. He noted the companies whose collapses are now taught in business schools had people who saw it early, and pensions still intact today had anyone treated those voices as an asset.
His own escalation went through the front door first, and he pursued internal resolution for a long time before anything else. There was a year he declined to sign a data attestation because he did not believe the numbers behind it. He raises it as a design question rather than a grievance. Where does a senior objection go in your organization, who is required to answer it, and what happens when the answer is inconvenient? In that era, at that scale, the machinery for routing an objection into a real review had not been built anywhere.
What he wanted the compliance officers in the room to hear was the earlier part. Someone raising a hand is doing the organization a service, and the cheapest moment to hear it is the first time it is offered.
Six years nobody sees
The litigation ran six years under seal, and he described what the seal does to a person. Naming the parties was off limits, which ruled out talking any of it through outside a narrow circle, and the sense of a shoe about to drop never fully left.
What held was the tether again, in its personal form. Family, and two standing weekly groups on the calendar every week for years. His navigational advice for anyone in the middle of something similar was blunt. If you are in trouble, keep your head above the water, because you steer toward what you keep in sight.
What he did with the award
The last stretch of the hour was the part the room did not expect.
A share of the award went to a community initiative grown from an orphanage into an organization building schools, clinics, and hospitals. He anonymously matched funds to complete construction on two hospitals and joined two medical missions to them, seeing patients who had traveled five hours by motorcycle for basic care. His own upgrade, he told the room, was trading a 2007 RAV4 for a 2014 RAV4.