Every hospital I walk into has spent millions on clinical information systems. And in every single one, case managers are still tracking discharge tasks on sticky notes, saving facility phone numbers in their personal cell phones, and using secure messaging as a makeshift task management system.

That’s not a training problem or a compliance problem. It’s a design problem: the technology was built for clinical documentation. Discharge coordination is a fundamentally different workflow, and almost nobody has built for it.

Over the past two years, I’ve done more than 200 interviews with case managers, discharge planners, social workers, and the directors who lead them, not through surveys but through real conversations, often in the middle of their workday, between calls to SNFs and arguments with payers. What I’ve learned has shaped everything we’re building at Caremaze. Here’s what they actually told me.

What They Tell You vs. What They Mean

When vendors do discovery calls with case management leaders, they hear things like “we need better documentation tools” or “we need more visibility into discharge status.” Those are real requests. But they’re shorthand for something more specific.

What case managers actually mean is: stop making me enter the same patient information into five different systems. Stop making me compile the same clinical packet - face sheet, H&P, progress notes, PT eval - and reformat it for every facility, every insurance appeal, every transportation request.

One discharge planner I spoke with described her routine as “asking my twelve questions that I ask every time” to every facility she calls. Twelve questions, repeated across five, ten, sometimes twenty facilities for a single patient. Not because she doesn’t know the answers she needs, but because there’s no system that holds them in one place and checks them in parallel.

The frustration isn’t about documentation, it’s about re-work. The information exists, but it’s scattered across systems that don’t talk to each other, in formats that aren’t portable, and behind workflows that require a human to manually bridge every gap.

The Real Job That Most Technology Ignores

If you’ve never shadowed a case manager through a full shift, you might assume the work is primarily clinical, but it isn’t. The clinical assessment is a meaningful but relatively small portion of the day. Evaluating the patient’s functional status, determining the appropriate level of post-acute care, reviewing the clinical picture, and that’s maybe 30% of their time.

The rest is logistics and relationship management. Tracking down a payer authorization. Calling the fourth SNF to check bed availability because the first three couldn’t take the patient’s medication regimen. Waiting on a callback that may never come. Chasing a transportation company to confirm a pickup time. Following up on a prior authorization denial. Coordinating with the hospitalist on discharge orders that haven’t been signed yet.

One case manager at a large urban hospital described her caseload: 5 to 10 admissions and 3 to 8 discharges on any given day. Each discharge with its own constellation of dependencies, all managed through a combination of the EHR, phone calls, faxes, and secure messages. Every one of those channels requires her to be the one doing the work, one task at a time, in sequence.

That serial nature is the core problem. A complex discharge can require 20 or more phone calls to post-acute providers. Most of those calls are just verifying basic information: does the facility have a bed, do they accept this insurance, can they handle the patient’s clinical needs. And each call happens one at a time, with a wait for a callback in between. You can lose entire days this way. At $2,500 to $3,500 per inpatient day depending on the state, those days add up fast. The California Hospital Association estimated that discharge delays alone cost California hospitals $3.25 billion per year in unnecessary inpatient days.

Technology that doesn’t address the logistics and coordination layer isn’t addressing the actual job.

What Frustrates Them About Current Tools

I’ve heard the same frustrations in every hospital I’ve visited. The specifics vary by system, but the patterns are consistent.

The EHR does what it was designed to do, and discharge coordination isn’t it. Most electronic health records are built for clinical documentation, orders, and billing. When case managers try to use them for discharge tracking, they end up with workarounds: open text fields serving as task lists, progress notes used to communicate discharge status, and documentation that’s thorough for compliance purposes but useless for real-time coordination. As one director put it, the system is great for clinical documentation, but it wasn’t built to orchestrate the discharge workflow.

Referral management platforms don’t solve the coordination problem. One case manager told me she uses the dominant referral platform for about 90% of her referrals. But the other 10%? “Those organizations are not integrated into that platform. It’s calls or emails.” And even for the 90% that are in the system, the data is often stale. Facilities listed as accepting referrals have actually stopped. Bed availability is out of date. Insurance acceptance information is wrong. So case managers call anyway to verify, which means the platform added a step without removing one. Another described sending referrals “into sometimes what feels like the ether that you don’t necessarily know clearly - was it received?”

Secure messaging became a firehose. What was supposed to streamline communication turned into another channel to monitor. Case managers now check the EHR, their email, secure messages, and their phone. The cognitive load of switching between these systems, and making sure nothing falls through the cracks across them, is itself a source of exhaustion, because the tools are all working but they’re not working together.

Insurance creates compounding delays that no tool addresses. The payer process is sequential, and each step resets the clock. A facility accepts the patient, the insurer reviews and denies, the case manager appeals, and the appeal takes 48 to 72 hours. One case manager I interviewed responded to the phrase “fast appeal” with a dry laugh: “It is not fast at all.”

None of these are edge cases; this is the daily experience of case management across the country. And the consequences are predictable. The national hospital turnover rate sits at 18.3%, and case managers have been specifically called out as a role with high churn. When the work is this grinding, people leave. Positions stay open for months. The remaining team absorbs the load, which makes the problem worse, which drives more turnover. No amount of hiring solves it if the underlying work doesn’t change.

What They Actually Want

In 200-plus interviews, not a single case manager has asked me for “AI.” That word has never come up unprompted. What they describe wanting is far more concrete.

Know where a patient stands without asking five people. Case managers want a single view that shows which tasks are blocking a discharge, who owns each task, and what’s actually been completed. Not a dashboard they have to go check. Something that surfaces the information proactively, so they’re not spending the first hour of every shift reconstructing each patient’s status from fragmented sources.

Have someone, or something, make the calls. The most consistent request, across every hospital and every role: take the phone work off my plate. Not the decision-making or the clinical judgment, but the transactional calls: the 20 calls to SNFs verifying the same basic information. The follow-up to a facility that never responded to a referral. The hour of back-and-forth with a transportation company to confirm a pickup time. Case managers want to stay in control of the decisions. They just don’t want to be the ones sitting on hold.

Get flagged early, not after the problem has compounded. By the time a case manager discovers a placement has fallen through or a payer denial has stalled a discharge, the patient may have already spent an extra day or two in a bed. What they want is to know about problems as they develop. A facility that hasn’t responded in 12 hours. An authorization about to expire. A patient whose discharge plan has three unresolved dependencies with two days until expected discharge. They want early signals, not late alarms.

Weekend and shift continuity. There’s no real handoff when someone is out sick or when the weekend team takes over. The context about each patient, who was called, what was said, what’s pending, lives in the case manager’s head or in scattered notes. Every Monday morning is a reconstruction project. Case managers want continuity that doesn’t depend on a single person’s memory.

One thing that surprised me in these conversations: the emotional dimension. The case managers who have been doing this for years love the hard cases. Getting a complex patient placed, the one with behavioral health needs and Medicaid and a wound vac, that’s a win they carry with them. As one veteran case manager told me, “I really like a good discharge. Like a good win.” Another, with 20 years in the role, said simply: “I pride myself, I mean, I love my job.” The frustration isn’t with the work itself but with the volume of low-value tasks that crowd out the work they find meaningful.

What It Means to Build for Them, Not at Them

There’s a meaningful difference between talking to case managers and building with them. Most health tech vendors talk to a few case managers during a discovery phase, then go build what their product team already wanted to build. The result is technology that looks good in a demo and falls apart on the floor.

Building with case managers means spending time in the room while they work. Watching a discharge planner make the same call to five facilities in a row. Sitting through a multidisciplinary round and seeing what information the case manager actually uses versus what the documentation says they should use. Understanding that no two discharges are the same, and that any tool rigid enough to require “the right way” of doing things will get abandoned within a week.

If you’re thinking about how to better support your case management team, we’d welcome the conversation. Request a conversation →

Frequently Asked Questions