ASO Reporting: What the Practices You Serve Need to See

An ambulatory surgery organization has two sets of customers and only talks to one of them regularly. Patients come through once. The referring practices send cases every week, judge you constantly, and almost never get told anything, which is why ASO reporting is a retention problem before it is an analytics problem.

Ask a surgeon’s office manager why they favor one surgery center over another and volume rarely comes up. What comes up is friction. Whether their patient got a date quickly. Whether somebody chased the paperwork or they had to. Whether they found out the case was cancelled from the center or from the patient calling them, upset.

That last one is the most damaging and the most preventable. A referring office that learns about a problem from its own patient concludes, correctly, that it has no visibility into what happens after it sends a case.

Most surgery organizations do have the data. It is sitting in the case queue, the schedule, and the document workflow, and nobody has made it into something a referring practice receives on a schedule. Building that is not a data science project. It is deciding what the other side needs to see and then sending it.

The rest of this is about what belongs in that report, and where each piece already exists.

The referring office is already tracking you, badly

Whatever you send them, they are keeping their own version of it, and their version is worse than the one you could produce.

An MGMA Stat poll found that more than three medical groups in four, 76%, manage patient referrals in their EHR at 66% or in referral management software at 10%, while about one in five, 21%, still rely on manual tracking. That manual fifth is the group calling your front desk to ask where a patient stands, and even the systematized majority is tracking what they sent rather than what happened to it.

The asymmetry is the opportunity. They know the case left. You know whether it was scheduled, whether the paperwork arrived, whether the date moved, and whether it happened. Sending that back closes a loop that costs them staff time to chase manually.

And it is cheap to do well, because the same information that answers their question is the information your own coordinators are already assembling one phone call at a time.

Case close reasons are the report you already have

Every question that arrives about a case becomes a record somewhere. In athenaOne that record is a patient case, and cases close with a reason drawn from a list your organization configures.

Those close reasons are the most under-used measurement asset in a surgery organization. Read across a month they describe what your front office actually spends its hours on, which is almost never what people assume. Practices that look at this for the first time usually find one or two reasons dominating a queue that everyone believed was evenly distributed.

The operational requirement is that the list has to be specific enough to be useful and short enough that staff pick accurately. A close reason list with a large catch-all bucket produces a report that says most of your work is other. Reviewing which cases changed and how they closed, on a regular cadence rather than during a crisis, is what keeps the list honest.

What goes to the referring practice is the derived version, not the raw list. How many of their cases were scheduled on first contact, how many needed a second attempt to reach the patient, and what the common reason was when a case stalled. That is a report an office manager will actually read.

Paperwork deadlines are the cancellation you can predict

The most useful number an ambulatory surgery organization can send a referring practice is the one that gives them time to act.

Medicare conditions for coverage require an ASC to maintain a policy identifying which patients need a history and physical completed before surgery, including the timeframe for completing it. That timeframe is the whole front-office game. A case with a missing document three days out is a cancellation that has not happened yet, and it is visible days before it becomes one.

So the report to the referring office should be forward looking rather than historical. Here are your cases in the next two weeks, here is what is outstanding on each, here is who we have already contacted. Sending that on a Monday converts a cancellation into a phone call the referring practice can make while it still matters.

Automation fits this cleanly because it is document chasing, not decision making. The system knows which documents are on file against a scheduled case, calls or messages the responsible office, records the attempt, and escalates to a coordinator when the deadline gets close. What it never does is decide whether a patient is ready for surgery. That determination belongs to clinicians on both sides, and the front-office layer exists only to make sure the paperwork reaches them in time.

Report block utilization, not just case counts

The second report has a different audience inside the same building, and it is the one that changes what gets offered.

A surgery organization’s capacity is block time, and block time is wasted in ways that case counts hide. Utilization by surgeon and by day, booked cases across every location rather than one, and the gap between block released and block refilled. Turnover is what sets the real cutoff for the last case of the day, not the posted closing time, so a report built on operating hours will overstate available capacity every single day.

There is a scheduling consequence worth naming. Missed appointments were the top patient access concern for practice leaders in 2026 at 27% of responses, ahead of online scheduling at 24%. In a setting where a single cancelled case leaves a block that cannot be resold on short notice, the recovery window is measured in hours.

Which argues for the same discipline as the paperwork report. Watch the leading indicator, act while there is time, and tell the referring practice what you are seeing rather than explaining it afterwards.

What to leave out

A report that a referring office does not read is worse than no report, because it consumes the goodwill you were trying to build.

Leave out anything they cannot act on. Total case volume, average satisfaction, and internal efficiency metrics belong in your own management review, not in the packet you send to a surgeon’s office manager. Every line in an external report should answer one of two questions: what is happening with my patients, and is there something I need to do.

Keep it short and keep it on a schedule. A predictable weekly note that is accurate beats a comprehensive monthly one that arrives late, because the value is operational rather than analytical.

And measure whether it worked the same way you would measure anything else. If the report is doing its job, inbound status calls from that office should drop. That decline is the cleanest evidence available that the visibility gap has closed.

Key Takeaways

Treat referring practices as the customer that repeats, and build reporting for them before building internal dashboards.
Keep the patient case close-reason list specific and short, then read it monthly to see what the front office actually spends hours on.
Send a forward-looking report of upcoming cases and outstanding documents, so the referring office can act before a cancellation happens.
Base capacity reporting on block utilization and turnover-driven cutoffs rather than posted operating hours.
Keep document chasing in automation and every readiness determination with clinicians on both sides.
Judge the report by whether inbound status calls from that office drop, not by how comprehensive it looks.

Referring practices choose a surgery organization on how little work it creates for them. Reporting is the cheapest way to reduce that work, and most of what belongs in it is already sitting in the case queue waiting to be sent.

Sources