Category

Why Healthcare PDC Needs
Its Own Software Category.

By Mike Bennett, AIA · 4 min read

If you work in a health system PDC department, you probably run your projects on two pieces of software that weren't built for you. One is a project management platform made for general contractors. The other is a space planning tool made for corporate real estate. We make them work because we have to, but neither one really understands what we do.

That's not a knock on those products. A contractor's PM tool does exactly what a contractor needs: drawings, RFIs, submittals, a schedule, a punch list. If you're building a warehouse, that covers most of the job. Healthcare piles a lot on top of that. FGI Guidelines. State licensing surveys. Infection control. A capital approval process that can have five levels of sign-off before anyone breaks ground. You can't really manage any of that in a Gantt chart built for a GC.

Space planning tools have the opposite problem. They're good at laying out a floor plate, but they don't know what a hospital room needs. They don't know that an OR equipment list is capital equipment with its own procurement timeline and its own clinical sign-off. I've watched good programmers run a department through one of these tools and then rebuild half of it by hand in Excel, because the tool didn't understand what they were trying to do.

Where you actually feel it

You don't notice any of this in a sales demo. You notice it a year and a half into a program. Somebody built a programming spreadsheet that worked pretty well. It got copied for the next project and tweaked. Then tweaked again for the one after that. A few years later there are five or six versions floating around the department, each one trusted by a different person, and nobody is completely sure which assumptions are buried in which file.

I don't think that's anyone's fault. The workarounds people build are usually pretty clever. The trouble is that a spreadsheet only lasts as long as the person who understands it. When that person leaves, you lose more than a coworker. You lose the only real record of how the work got done.

What the software would actually need to do

If someone built software specifically for this work, I think it would have to get a few things right. Space programming would need to know the FGI Guidelines from the start, instead of making you keep the PDF open in another tab while you build the room list by hand. The cost estimate would need to update when the program changes, instead of getting reconciled weeks later. And approvals would need to work the way capital actually moves through a health system: the approval levels, the ICRA tracking, and reporting that works for the CFO and the surveyor. At most places I've seen, those are two more spreadsheets.

I've lived the version without it. A programming cycle that took six weeks when it should have taken a day. A board meeting where two departments showed up with two different budget numbers for the same project. An ICRA permit that ran three weeks late because the tracking lived in one person's inbox. None of that was unusual. That's pretty much what normal looks like when you run a capital program on tools made for another industry.

Why a healthcare add-on usually doesn't fix it

Every so often one of the big PM platforms announces a healthcare template or module, and I always go look at what's in it. Usually it's a few extra fields. A spot to note licensure status, maybe a folder for infection control plans. That's helpful, but a field you can type into is a long way from software that actually tracks your approvals or checks a room list against code.

I get why vendors do it. Their healthcare customers are asking for a better fit, and adding fields is the quickest way to give them one. But the first time a real project runs into something the template didn't plan for, the tool goes right back to acting like the general product it is. That's a big part of why I started building something for this work myself a couple of years ago. But that's a story for another post.

Mike Bennett is a licensed architect and host of the Healthcare Design Podcast, where he talks with PDC directors, project managers, and architects about what actually breaks in a capital program. He also builds Continuum, software for this specific corner of the industry.