It may be clear on this ruling, but I would surmise that when a sentinel event happens in a hospital due to some dip$hit running their own rogue AP, the FCC may think a bit different.
Right now they were sending a clear message to the numbskulls doing it for profit.
*hand waffling gesture*
The issue there though is, that is really a medical device manufacturer fault if that can possibly occur. If regular wifi operation withing FCC regulation can cause sufficient interference to cause issues, then the medical device maker/hospital is at fault. Not "some dip$hit" as you put it.
Regular operation of cellular and wifi devices should in no way cause interference with medical equipment. PERIOD.
It is either a design problem from the hospital's network if it can to their network or the medical device manufacturer if it can somehow cause problems with a medical device within the hospital.
There is a bit within the FCCs regulations that require not only non-harmful interference to be generated by FCC certified devices, but also to be able to ACCEPT non-harmful interference from other devices.
The only exceptions I can see to allowing wifi hotspots/cell devices to be operated unobstructed is in the cases of REAL public safety. I'd codify those under things like "blocking cell signals/wifi within top secret facilities" or within prisons (I kind of get why that isn't legal, but at the same time...). Medical equipment and networks absolutely should be able to accept some "dip$hit's" AP operating and cause zero issues.
PS also to be clear, some hospitals tell you no cell/wifi as a for profit thing too. I've been to hospitals where they have no free wifi. Oh, they have wifi you can connect to as a guest/patient...but you also get CHARGED per device you connect. That said, I have also been to some hospitals which just plain have free wifi.