Skip to main content

How HCGH justifies their $240 cable bill

So I wrote about how HCGH charges $240 per month for basic cable and local phone services last week. Today, I returned their call and here's their justification for putting the burden of cancellation on the (sick) patient:
  • the charges for the phone and cable is spelled out in the consent form that new patients fill out upon admission to the hospital. This is the same consent form that grants the hospital the right to treat you. So if you don't consent to cable+phone charges and treatment, the doctors can't treat you. How nice!
I asked why not make it two forms: one for cable tv and one for treatment. God knows patients have to sign enough forms during the admission process. Their answer:

"Our patients have requested that the admission process be streamlined". Oh yeah, streamlined my foot. Wouldn't it make more sense to not turn on the service until a patient requests it? Instead, they waste their employees' time reversing silly charges. Or perhaps, not enough patients call in to complain and thus HCGH makes a nice little sum of money each month.

Either way, when planning to use HCGH (an otherwise excellent hospital) be sure to
  • call the hospital and have them turn off the basic cable non-flat-screen tv
  • call 1-800-775-8352 to ensure you are not billed upon discharge

Comments

Popular posts from this blog

InfoPath & SharePoint (Part 1)

A departure from sports and politics. This one is about technology.

InfoPath sucks and SharePoint is the most expensive piece of crap ever. InfoPath, as a development environment, has absolutely no redeeming value. It's worthless and if your boss ever thinks of using it, you have three options:

convince him not to (not easy once he's been brainwashed by the Microsoft marketing presentations)use one of Al Gore's lockboxes to store away your sanity 'cos you'll lose it. Also, pad your estimates very generously. You'll need every bit of time you can get.
quit immediately while you still have your sanityFirst, InfoPath:

To me InfoPath is like programming in assembly language. Sure it makes it easy (too easy in fact) to bind data to controls. But it doesn't provide you with easy access to your controls. Why is this important? Say you want to disable a button:

in most technology: buttonA.enabled = false (or something similar).

In InfoPath, you simply can't do this.…

Technical Certifications are worthless

Technical certifications, especially in the IT field, are totally worthless. Why? All a technical certification prove is that you were able to buy a couple of exam prep books, cram them in a week or two and take an exam. My monkey (if I had one) could do that. I can't tell you how many times I have interviewed certification-carrying candidates for open positions at my company only to find them severely lacking in thorough understanding of computer science. I don't care that you have an MSCD or MCP or whatever it's called these days if you don't know foundational concepts in computer science and database design.
For example, I don't want someone who just knows that you store things in a hashtable using keys. I need you to know why a hashtable is better than an array in some cases. I need you to know when an interface is better than an abstract class; when to use recursion; the different kinds of joins and when to use each one; I need you to understand how crucial sou…

Does InfoPath (still) suck?

A couple of years ago, I wrote a blog post titled "InfoPath & SharePoint (Part 1)". Back then I had just started working on a project using InfoPath 2007. So, expectedly, the post wasn't very complimentary to InfoPath (or SharePoint). In fact, I said:
InfoPath sucks and SharePoint is the most expensive piece of crap ever. InfoPath, as a development environment, has absolutely no redeeming value. It's worthless.... (more)Since then my opinion of InfoPath has changed slightly. It still suffers from all the flaws I pointed out in that post. However, I think when used right, InfoPath can be an OK tool. I think it's well suited for designing one off forms and not for anything that requires complex logic or multiple iterations (like most software development requires). Alas, most CTOs fall in love with its point & click simplicity and integration with SharePoint that they try to use it to replace more developed technologies like ASP.NET. What do you get? A horri…