Continue reading »]]> For today’s podcast, I did some research at http://www.recovery.gov , looking for recipient reports for “Health IT”.  The results were pretty interesting.  In the show, I talk about some of the information that I found, some trends that I saw, and talk about a few of the more humorous projects (like one for the study of the efficacy of lifestyle changes for obese men with erectile dysfunction).

One of the common themes that I found was that a significant amount of the ARRA money that was supposed to be used to change the face of healthcare IT  is really only being used to augment systems that are already in place.  This means that a lot of the money is being used for tactical purposes in organizations, and not fulfilling strategic needs.

This podcast is being used for my feature at ADVANCE for Health Information Executives for the month of April as well.

To hear the podcast, you can use the plugin here:

If you want to add this feed through iTunes, please click here:

If you want to add this feed to your Google homepage, please use this link:

As always, if you have any questions, you are welcome to contact me directly at spencer@itpodcast.org. I respond to all emails and posts to this blog directly.

If you would like to add me to your Facebook or LinkedIn profiles, you can use these links for that connection.

Spencer Hamons

Continue reading »]]> On today’s show, I talk about alignment of IT initiatives and your organization’s long-term strategic plan and short-term tactical goals.

I also have a talk with Nuance Communication’s Keith Belton about Nuance’s new Dragon Medical product and where Keith feels that speech recognition will continue to be in the future of healthcare IT.

As always, I welcome your comments either here on the blog, or by emailing me directly at spencer@itpodcast.org. If you would like to email Keith, you can reach him at Keith.Belton@Nuance.com. For more information about Dragon Medical, you can click here and a new window will open and you will be taken to their page.

If you want to add this feed through iTunes, please click here:

If you want to add this feed to your Google homepage, please click here:

This week, I did not have any news because the show was getting a little long.

If you would like to comment on this podcast, you can either email me at spencer@itpodcast.org, or you can click on the title of this post and on the new page, scroll down to “comment”.

The next podcast will be available on November 1, 2008.

Continue reading »]]> I posted this response at CIO.com in response to an article surrounding the need for more than one software vendor.  Text of response is below.

READER FEEDBACK

Spencer Hamons Tue, 2008-01-15 17:09

Although I agree with some points made here regarding negotiation position and the relatively small number of large software vendors available, I take issue with just stating that this is the best strategy.

This may well be the best strategy for organizations with mature enought IT departments capable of handling the complexity multiple vendors involves. It is also dependent upon the business of the organization and the risk tolerance and what data integrity means to the specific organization.

For example, I am the CIO of a hospital, and if I encounter a data integration problem that happens to result in some clinical data from one patient being transposed to another patient, I don’t have an upset customer on the end of the support line for an online order they placed. I have the potential for adverse drug interactions, incorrect lab or radiology data, or even death resulting from mistreatment. These are risks that I am not willing to take for the sake of a negotiation advantage. Likewise, if my IT staff were 250 employees capable of monitoring each and every HL7 transaction, my risk tolerance would be different than it is currently with my 10 IT staff members. Additionally, in healthcare, I never have the luxury of taking the entire system down for 24 hours over the weekend…not even a portion of the system. In a 24×7 operation, care must be taken on how do you keep systems active and functioning day and night. If a data integrity problem erupts, for the safety of our patients, we have to take systems off-line. With “one throat to choke”, combined with good contract metrics, the vendor is motivated to resolve our problems quickly rather that point fingers at integration points.

This is a topic that will be discussed on an upcoming podcast at ITPodcast.org for anyone in the healthcare industry (or interested in the healthcare industry) that would like to listen in.