Article · Governance · October 28, 2026
The least governed queue in a hospital is the one deciding which EHR fix gets built.
A hospital tracks its denial rate, its ED boarding time, and its no-show rate to the decimal point. The queue of requests sitting in the EHR change-management system, the one that decides whether a nurse's workaround ever gets fixed, has no equivalent metric. A June 2026 MedCity News analysis made the point plainly: operations teams track delay everywhere except the queue that decides whether their own workflow problems get solved, so staff route around it with shared spreadsheets and side deals instead of waiting on IT.
The data on how that queue actually runs is thin, and the thinness is itself part of the story. The clearest look comes from a 2023 Applied Clinical Informatics study that interviewed chief medical information officers at 18 U.S. academic medical centers about how each one governs EHR modification requests. The results were not close to uniform. A third of the centers, 33.3 percent, had no scoring system at all for deciding which requests to build first; the rest split between quantitative scoring, 38.9 percent, and qualitative review, 27.8 percent. Request volume was the challenge CMIOs named most often, at 61 percent. At 78 percent of centers, the single slowest step in the entire process was simply clarifying what the requester actually wanted. Only two of the 18 centers formally screened every request for its effect on care equity.
That variability lines up with a broader finding in CHIME and KLAS's 2025 Digital Health Most Wired national trends report. CHIME's own Digital Health Insights, KLAS's report listing, and the trade outlet HealthSystemCIO each covered the same conclusion: governance and integration, not the size of the IT budget, is what separates the health systems reaching the top maturity levels from everyone else. EHR budget as a share of revenue, cybersecurity spending, and total IT spend all failed to predict which organizations scored highest. Governance did.
A hospital that governs its change-request queue loosely is not saving effort by skipping the paperwork. It is trading a visible process for an invisible one, where volume overwhelms the team, the slowest step is guessing what was actually asked for, and whoever escalates loudest gets built first. KLAS's own Arch Collaborative has documented health systems doing the opposite: publishing guiding principles and standards as the starting point for every EHR request, so a requester knows the criteria before submitting rather than only finding out after a long wait with no answer.
The list of things I have watched sit for months is long. Build change requests. The reports people need on the first day of go-live. IT due diligence and the proposed changes for an acquisition.
None of this calls for a bigger IT department. It calls for naming who owns the queue, publishing the criteria a request has to clear, and putting one number, cycle time, volume, or percent formally scored, in front of an executive on a regular basis. Most hospitals already do that for denials. Few do it for the queue that decides what actually gets fixed.
Pull your own change-request backlog this week and ask one question: does every item in it have a published scoring criterion, or just a date it arrived?
Follow along on LinkedIn.
Working through a decision like this one? Let's spend 30 minutes on it →
Leading a rural hospital or clinic? See what your state received, which rounds are open, and whether your project has a path. Rural Health Transformation funding by state →