OR Informatics Replaced Month-End Blind Spots With Real-Time Surgical Capacity
At San Juan Regional Medical Center, a community hospital in Farmington, N.M., the distance to the nearest large tertiary center is roughly 180 miles. In that setting, surgical access is not a convenience metric; it determines whether patients receive care locally or face a long, burdensome transfer across the Four Corners region. The hospital’s old Excel-based operating room workflow could not keep pace with that responsibility. It created bottlenecks, obscured true capacity and forced leaders to manage surgery scheduling with stale information.
The shift to LeanTaaS’ iQueue for Operating Rooms changed that picture in 90 days. The hospital said it opened up surgical access, reached 88% user adoption and recorded a two-fold return on investment in the first quarter after implementation. For a 10-room OR that performs about 7,500 surgeries annually, the operational change carried direct patient consequences: fewer blind spots, faster scheduling decisions and better use of time that had previously sat hidden in spreadsheets.
One sentence captured the old reality plainly: “We were addressing problems 30 days after they happened.”
Manual Scheduling Left Leaders Managing Yesterday’s Problems
Before the platform went live, scheduling and tracking ran through disconnected manual processes. Admissions nurses called floors to find clean rooms. Physicians signed paper forms to book cases. Leaders could not see block utilization, turnover times or first-case on-time starts in real time, and extracting data from the EHR required workarounds that made monthly governance meetings feel detached from day-to-day operations.
That data lag mattered because OR capacity is a living system. If turnover times are longer than expected, if a room is idle between cases, or if block time is underused by one service line and overbooked by another, the hospital loses throughput and patients wait longer. In a rural referral environment, those delays can ripple outward quickly. A community hospital cannot afford to discover weeks later that surgical access was narrower than the schedule implied.
Strong governance alone did not fix the problem. The hospital already had external consultants and an OR capacity structure in place. What it lacked was timely, trustworthy data that could drive action while the operating day was still unfolding.
Executive Sponsorship Gave the Project Clinical Weight
John Gaede, the hospital’s CIO, carried the technology case to the board from the start and framed it around the institution’s mission as the premier regional medical center. He also brought unusual operational fluency to the role, having spent nine years as a medical technologist before moving into IT. That background made the project less like a software install and more like a clinical operations intervention.
Carlo Hallak, MD, physician informatics executive at the hospital, described the effort in the same terms. Physician and IT leaders worked side by side, validating surgeon concerns and keeping the project anchored in bedside reality. In a setting where skepticism about data is predictable, leadership alignment mattered. The platform could not succeed as an abstract efficiency tool. It had to prove it could reflect what clinicians already knew about the OR and then improve it.
Trust arrived through verification, not slogans. The LeanTaaS team spent weeks working with the hospital’s nurse informaticist to ensure the platform matched the EHR. The medical director of anesthesiology, who had long maintained the OR’s Excel spreadsheets, became a crucial validator. When some providers questioned the numbers at the first governance meeting, he was there to confirm them. In a workflow built on long-standing habits, that endorsement carried more weight than any sales pitch.
Small Workflow Changes Unlocked Adoption
Adoption was not automatic, and the team did not treat resistance as a nuisance to be overcome with more software. The on-site implementation team listened, documented feedback and adjusted the system to fit the hospital’s practice patterns. One early issue involved turnover time. The platform defaulted to 30 minutes, but surgeons said San Juan Regional needed 45 minutes. The team changed it.
That adjustment removed scheduling gray zones and showed clinicians that the system could bend to the reality of the operating room rather than force the OR to conform to a generic template. The response from the hospital side reinforced the same message. The nurse informaticist, a former OR circulator, provided at-the-elbow support to schedulers and nurses who had spent hours each week assembling spreadsheets. With the new platform, they could pull turnover and block utilization reports in a few clicks.
A general surgeon helped drive uptake among peers by modeling point-of-care scheduling. In clinic, she logged in, created the case and booked OR time immediately instead of relying on paper forms and follow-up calls. That behavior mattered because physician habits often determine whether operational software becomes a true workflow tool or just another screen in the background. Here, the scheduling path became shorter and more visible at the exact moment when clinical decisions were being made.
Capacity Gains Became Visible Within 90 Days
The first-quarter results were concrete. San Juan Regional reported 88% user adoption, 71 active users across schedulers, staff and physicians, and 498 approved requests for booked or open OR time slots. Under the prior system, some of those cases likely would have been delayed or never scheduled at all. The average lead time for case requests is now 10 days, which gives teams more time to prepare patients and organize the OR around actual demand instead of reactive guesswork.
The hospital also calculated a two-fold return on investment, using a conservative contribution margin estimate that is still being refined with LeanTaaS and the hospital’s CFO. If that margin proves higher, the return will rise further. Financial gain, though, is only part of the story. The more immediate clinical consequence is that surgeons can see open time at the point of care and book cases immediately, reducing the lag between evaluation and surgery.
At the most recent throughput governance committee meeting, the OR director presented data from the platform rather than Excel sheets. That single shift signaled a new operating norm: one source of truth, visible to leaders and clinicians alike. The hospital can now track room use, equipment utilization and surgical robot deployment with far more clarity than it had before.
The Next Layer Will Push the Data Closer to the Bedside
The hospital is not stopping at basic visibility. It plans to give six surgeons personalized dashboards showing how they use OR time and how they schedule cases. It is also adding a same-day view of OR activity so leaders can act on problems as they happen, not after the day is over. New tools will allow OR time to shift between surgeons as demand changes, which could tighten alignment between block allocation and real utilization.
Longer term, the hospital is evaluating similar capacity tools for inpatient and infusion care. The broader lesson, as Hallak described it, is that adoption depended less on the software than on the bridge built between IT and operations. Without that partnership, the project could easily have become another unused rollout. With it, the hospital turned a manual scheduling system into a live clinical operations platform, while still facing the next question that always follows early gains: how far can real-time capacity management extend beyond the OR, and how durable will those improvements remain once the novelty of the new system fades?