Talk to our team

Tell us about your organisation and we will reply within one business day.

Thank you. Your submission has been received!

Our team will be in touch shortly.

Oops! Something went wrong while submitting the form.
Vee Healthtek Horizontal Color logo
Clinical and Revenue Cycle Partnership

Care and Revenue Cycle, Connected.

What Jason Raidbard and Mamoon Nawabi revealed about shared data, closer collaboration and purposeful AI. 

Care and Revenue Cycle, Connected.

November 23, 2026

Blog

8 minutes

On this page

TL;DR

  • Jason Raidbard connected front-end accuracy with stronger revenue cycle performance.
  • Mamoon Nawabi showed how shared data and regular collaboration help teams resolve issues earlier.
  • Both emphasized starting with the operational problem before introducing AI.
  • Their partnership combines clinical context with revenue cycle expertise, creating clearer accountability and less rework.

Operations and revenue cycle cannot stay in separate rooms. | One Workflow, Shared Outcomes

A scheduling decision can become a billing issue. A documentation gap can become a denial. A physician who begins delivering care before payer enrollment is complete can create work that takes months to unwind. Clinical operations and revenue cycle may sit in different parts of an organization, but their outcomes are inseparable.

That was the central theme of my recent Reworked conversation with Jason Raidbard, Executive Administrator for Ophthalmology and Visual Science at UChicago, and Mamoon Nawabi, Executive Director of Physician Services at UChicago. Jason leads a clinical department. Mamoon leads the physician revenue cycle that supports it. Their partnership shows what becomes possible when both sides treat the work as one connected system.

 

The front end shapes everything that follows.

Jason described the principle simply: if the patient is not registered correctly, the claim will not be right. Accurate registration, prior authorization, documentation and credentialing are not isolated administrative steps. Each one influences whether the organization can submit a clean claim and receive appropriate payment.

The complexity increases in an academic health system, where novel procedures and services may be considered experimental or use unlisted codes. Mamoon’s team works with clinical departments to understand emerging services, improve documentation and identify payer patterns that could lead to denials.

“If you don’t register the patient correctly, the claim will never get done.”
Jason Raidbard, UChicago

The practical lesson is that revenue cycle involvement must begin before a new provider, location or service goes live. When UChicago expands into a new market or brings a physician on board, payer enrollment and credentialing need to move alongside the operational plan, not behind it.

 

Partnership works better than handoffs. | Partnership Before Escalation

One of the most useful practices Jason and Mamoon described is also one of the simplest: their teams meet every month. The discussion covers overall performance, denial and payment trends, new providers, services and locations, and any issue that requires a deeper review.

Mamoon’s team approaches the clinical departments as internal clients. The goal is not only to submit claims and post payments, but to demonstrate quality, communicate payer issues and ensure the department is not surprised when reimbursement is at risk. Jason, in turn, brings the operational context needed to interpret the numbers and challenge assumptions.

“We see the clinical departments as our clients.”
Mamoon Nawabi, UChicago

This rhythm turns revenue cycle from a back-office function into an operating partner. It gives both teams a regular place to surface risks before they become larger problems, connect strategic decisions with their financial consequences and create open accountability for what happens next.

 

Question the data to understand, not to assign blame. | Question Data to Understand

Jason made an important distinction about reviewing performance data. The first step is not to declare that a report is wrong. It is to ask questions that clarify how the result was produced and what the other person is seeing.

“You’re not questioning the person. You’re questioning the data.”
Jason Raidbard, UChicago

That approach protects the relationship while improving the analysis. It also creates room for the revenue cycle team to explain the detail behind a trend. Once both sides understand the same facts, they can examine whether the issue comes from coding, authorization, payer behavior, workflow design or the underlying data itself.

Mamoon noted that engaged department leaders can identify gaps the central billing office may not see. A problem found in one department may also exist elsewhere, turning one careful question into an organization-wide improvement opportunity.

 

Useful dashboards require data literacy. | Make Metrics Actionable

Mamoon’s team has built dashboards that connect high-level revenue cycle measures with the detail required to act. Leaders can begin with denial rates, days in accounts receivable or revenue per work RVU and then drill into payer, CPT and provider-level patterns.

The technology matters, but the operating capability matters more. Managers, supervisors and directors are trained to use the reporting tools, and the broader team receives regular updates on current performance and payer issues. The insight does not remain with a small analytics group.

“Data literacy is very important. It does not fall on one or two people; it sits on the shoulders of all.”
Mamoon Nawabi, UChicago 

This creates shared accountability. When people understand the reason behind a change in performance, they are better equipped to correct it and less likely to treat the dashboard as a scorecard that belongs to someone else. That visibility is central to open accountability: the teams closest to the work can see the issue, understand its operational context and agree on who will act.

 

A speak-up culture keeps improvement moving.

Data can reveal a broken process, but people must be able to say that something is wrong. Jason connected this to his experience with high-reliability patient safety. Leaders need to be approachable, open to critique and willing to hear when a decision or workflow is not working as intended.

A low number of reported problems does not always indicate a healthy system. It may mean people do not feel safe raising them. In revenue cycle, the same dynamic can allow documentation gaps, authorization failures and inefficient workarounds to continue unnoticed.

 

Govern AI around the problem being solved. | Govern AI Around the Problem

The conversation eventually turned to AI. Mamoon described current uses in coding, predictive denials and appeal-letter generation. He also emphasized the need to verify AI output, preserve the team’s ability to identify trends and distinguish genuine AI from rules-based automation presented under the same label.

Jason added a broader governance point: organizations should identify the problem first, conduct due diligence and establish how a product and vendor will be managed before scaling. A compelling demonstration is not a substitute for operational fit.

“What are you solving for? You have to understand your own organization and what the needs are first.”
Jason Raidbard, UChicago

That sequence matters. A strong governance model connects technology decisions to a defined need, tests the output and assigns responsibility after implementation. Without it, organizations risk adding cost, workload and frustration instead of removing rework.

 

Better revenue cycle performance begins with partnership.

Jason and Mamoon came to healthcare from different directions, but their work converges around the same outcome. Clinical departments need revenue cycle expertise, and revenue cycle teams need operational context. Neither side can build a complete view alone.

Their conversation reinforced a practical model: meet consistently, share usable data, question it constructively, create a culture where people can speak up and govern technology around a clearly defined problem. That combination of first-pass performance and open accountability helps teams prevent avoidable defects, see where ownership sits and move from disconnected handoffs to a more resilient revenue cycle.

‍

About Reworked.

Reworked brings together healthcare leaders who refuse to accept avoidable revenue cycle rework as simply “how things work.” In each concise episode, I speak with healthcare leaders about a specific operational problem, where work was being done, undone and redone, and what it took to create a more resilient process.

The conversations move beyond broad claims about AI and transformation. Guests share the processes they re-engineered, the technology they introduced, the team behaviors they changed and the measures that showed whether the work improved. The goal is simple: every listener should leave with at least one practical idea they can take back to their own revenue cycle team.

 

Continue the conversation.

Watch my full conversation with Jason Raidbard and Mamoon Nawabi for practical insights on clinical-revenue cycle partnership, data literacy, speak-up culture and AI governance.

Read the Blog
Use your business email to access the page
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Where are disconnected handoffs creating rework in your revenue cycle?

Talk with our team about how first-pass performance can bring clinical operations, data and revenue cycle teams together around the work that needs to be right the first time.

Thank you. Your Submission Has Been Received!

Continue exploring expert perspectives, industry trends, and practical strategies for improving revenue cycle performance.

Explore Points Of View
Oops! Something went wrong while submitting the form.

Frequently Asked Questions

Why should clinical operations and revenue cycle work together?

White plus sign symbol on a transparent background.

How does front-end accuracy affect revenue cycle performance?

White plus sign symbol on a transparent background.

How can monthly clinical and revenue cycle meetings reduce rework?

White plus sign symbol on a transparent background.

Why is data literacy important in revenue cycle management?

White plus sign symbol on a transparent background.

How should healthcare organizations evaluate AI for revenue cycle use cases?

White plus sign symbol on a transparent background.

What does first-pass performance mean for clinical and revenue cycle teams?

White plus sign symbol on a transparent background.