Ashutosh "Ash" Pandey has spent two decades inside the operational machinery of US healthcare — claims floors, billing offices, transformation programs, and now a school-based ESHR he helped design from a blank page. This work finds its true value in the meaningful, quiet mastery of the systems that drive real results.
He began as a claims associate in 2004, adjudicating hospital and physician claims at a large outsourcing operation in India. The work was repetitive and exacting, and it taught him something that has shaped every role since: the answer to most operational problems lives inside the process, not above it. The dashboards summarize, but the queue tells the truth.
From there the path moved in steady steps — quality auditor, trainer (more than 250 people trained and mentored), team lead, assistant manager. By 2010 he was at R1 RCM (then Accretive Health), running revenue cycle operations on GE Centricity and Cerner for large health systems that included Ascension Health and Henry Ford. In 2012 he joined Genpact, where over eleven years he rose to Assistant Vice President, leading a $1B Gross AR portfolio across health systems, pharmacy, PBM, and DME clients — and, along the way, leading the firm's domain practice in revenue cycle.
Today, he serves as Director of Revenue Cycle Operations and Health IT at the Alameda County Office of Education, where he architected a first-of-its-kind school-based ESHR and Medicaid billing program. Developed under California's Children and Youth Behavioral Health Initiative, the system is designed for an initial 120,000+ students across multiple Local Education Agencies. This is an enterprise ecosystem built on Salesforce supported by a robust data warehouse on Azure Cloud that integrates with multiple Student Information Systems. System has matured to process an annual run rate of 24,000 claims.
The through-line that isn't on the resume.
What the resume does not say — and what may matter most — is that Ash trusted basics such as reason, logic, "Why", and "How" to gain knowledge.
Long before the "low-code" paradigm entered the corporate lexicon, his approach to operational strategy relied on advanced functional modeling. Utilizing Excel not merely as a spreadsheet, but as a robust engine for predictive forecasting, capacity planning, and institutional MIS, he engineered sophisticated, multi-layered logical models. This mindset naturally accelerated from complex cell-level logic into automated script architecture (VBA) and custom programmatic solutions — designed first to eliminate operational friction, and ultimately to cultivate a deeper, systems-level data literacy across his teams.
The curiosity naturally expanded into the architecture of data itself: relational database design, schema normalization, master-list separation, and the elegant logic of eliminating redundancy through dedicated tables. The frontend-to-backend contract. The conceptual mechanics of machine learning. How an operating system speaks to silicon in ones and zeros. He has not been formally trained in any of this. He has been formally curious about all of it.
That curiosity made him useful in a way no job description quite captures. As a business analyst and scrum master, he became the translator — the person who could sit with engineers in the morning and finance leaders in the afternoon and speak both languages without losing what mattered to either side.
What he believes about the work.
The frameworks that shaped him.
Early in his career, three ideas left a permanent mark on how he sees operational work. The first was the Input–Output model — the simple discipline of asking, of any process, what goes in, what comes out, and what happens between. The second was Six Sigma, valued less for the credentials than for the underlying conviction that variance is the enemy of operational excellence. It was this discipline that first revealed how data tells a story, sparking a true love for data analytics and a passion for uncovering the operational truths hidden in the numbers. The third was Value Stream Mapping, which taught him to see process not as a sequence of tasks but as a flow of value — and, just as importantly, where that value gets lost.
These three frameworks still sit underneath nearly every diagnosis he runs today, even when they go unnamed.
Why this work, and why still.
Twenty years in, the answer to why still is simpler than it used to be. The work delivers visible impact to a community — a hospital that gets paid for care it actually delivered, a district that can fund a behavioral health counselor because a claim went through clean, a team that learns to trust its own numbers. That impact is unglamorous and easy to overlook from a distance. Up close, it is the work.
The other answer is that the field has never stopped being interesting. Healthcare revenue cycle in 2026 sits at the intersection of finance, technology, regulation, and human behavior — and the AI moment is genuinely re-arranging the furniture. He intends to spend the next decade paying close attention to how that re-arrangement actually happens, in the queue, and to write down what he finds.
This site is part of that writing.
Outside the work.
Ash lives in California, with his family. He likes long walks in nature, learning about old and new, and conversations with people he hasn't met yet — interviews that begin as professional curiosity and usually end somewhere more interesting.
If you are reading this and would like to talk — about the work, or something adjacent to it — the connect column to the right has the means.