Submit your article of up to 500 words in length, subject to editing for clarity and brevity. I’ll use a phony name for you unless you tell me otherwise. Thanks for sharing!
CIOs: Sell Your Board and Executives on the Big Picture
By Ivo Nelson
If you think your IT staff and budget will decline in the next five years, think again. By 2010-2013, hospitals will be in full-scale EMR implementation mode. At the same time, they will be reengineering their revenue cycle processes and systems to accommodate some level of healthcare reform, while preparing for conversion to ICD-10.
All of this activity will be on the same scale as converting to DRGs (1983) AND converting to Y2K (1999) AND implementing HIPAA (2003) times two (or more). And keep in mind, because these changes are mandated by the government, ALL hospitals and physicians will have to comply at the same time.
If you think your vendor contracts will cover all this, think again. If you think you’re at the top of their priority list, think again. If you think you’re going to get a break when you wind down your EMR implementation, think again.
I’ve met with over 60 CIOs in the last couple of months, looking for insights into their strategies, concerns, and challenges.
The ARRA HIT stimulus bill is on everyone’s mind. Most CIOs have done more PowerPoints in the last couple of months than in the last five years due to inquiries from their CEOs and boards who smell money. The focus is the stimulus money and how their hospital is positioned to receive the maximum amount from the government. They allude to an END, when the EMR is implemented and demonstrates “meaningful use”, some minimal level of interoperability all within the boundaries of HIPAA security and privacy regulatory changes.
The ARRA HIT stimulus is just the start. Healthcare reform will change reimbursement to true pay-for-performance, requiring billing systems to be based on outcomes and quality. Additionally, if bundled payment is adopted, it will require unparalleled coordination to bring the hospital, physician charges, and other services into a single rate. Any emphasis on coordination of care requires a level of interoperability that doesn’t exist today.
On top of all that, the impending ICD-10 coding conversions requires the number of diagnostic codes to swell from 13,500 to 120,000. For inpatient procedures, the number jumps from 4,000 codes to 200,000 codes. The IT implications are huge. The impact on the hospital operations process and analytics will be even greater.
Quality is the new battleground. Once we are required to produce consistent quality reporting as a requirement for incentive payments (and eventually to avoid penalties), the game changes. Quality comparisons among competitors will be posted on the sides of buses, billboards, magazine ads, and on the TV. Quality care will be the first thing patients look for when it comes to the well-being of themselves, their family, and their community.
The usual Press-Ganey patient satisfaction measure will become almost irrelevant. Patients will endure long lines, rude staff, and will sit on the floor if they believe they will receive higher quality of care.
For the CIO, there will be immense pressure to be agile in producing reports to manage and report quality. Many are already coming to the sad reality that, after spending tens of millions of dollars on their EMR, all they have is a transaction system that doesn’t produce information. An entirely new genre of HIT now emerges around healthcare analytics. Remember, reimbursement will likely be tied to this information. Losing revenue because IT can’t produce reports, systems aren’t integrated, or vendors aren’t responsive isn’t going to be a conversation any CIO wants to have with his/her CEO or board.
Interoperability/Community Connectivity? Obama’s view of community connectivity is the sharing of patient information between heathcare organizations regardless of their competitive stance and strategy with each other. Our president greatly underestimates the power of local political will. Connectivity is contemplated, in the short term, only when organizations use it to capture a greater share of referring physicians – damn the community good. Elaborate arguments will justify the self-serving, digital capture of community (e.g. referring) physicians. There is a good chance ‘connectivity’, in the Obama sense, will eventually be defined in the courts.
Most CIOs are aware of the issues around interoperability. Most are participating on some committee on the state or local level as per their boss’s direction. Most roll their eyes at the naïve, non-healthcare participants who see the healthcare exchanges and interoperability as the holy grail.
Most realize they are being required to respond to some government mandate that doesn’t completely comprehend the data complexities that exist within the walls of most organizations. One organization has 92 different definitions for glucose and another has 16 different ways to define death. And they’re going to talk to each other? It’s a good thing there are some smart people on the ARRA HIT Standards Committee.
Of course, all of this is going on while we’re in a recession and CFOs are ratcheting back on capital and asking CIOs when their staff will downsize post-EMR implementation. It is not just that the CFOs are asking for reductions, it’s that the credit markets have tanked and the money simply isn’t there. It’s one thing for a CFO to say we need to reduce expenses; it’s another thing for a hospital to find out they have no credit because the bond market has tanked.
If I were a CIO, I’d be adding a few slides to my PowerPoint presentation to include ALL of the potential changes coming down the pipe, not just the stimulus incentives. I wouldn’t do a full-scale strategic plan, but I would dig deeper into a staffing analysis and make sure I didn’t prematurely reduce or redeploy staff. I’d create some what-if scenarios on the high and low end of change. I’d also take more advantage of the current access to my board and executives to educate and "sell" them on the bigger picture. Yep, and all this needs to be done while you’re trying to get the printer to format labels for the lab accurately.
The budget cycles are starting now for 2010. Make sure you get all of your cards on the table. I know it’s not all defined yet, legislation isn’t passed, and some changes may be a moving target. Like it or not, this is a government that makes decisions. The stakes are high. Now is not a time to be timid.
In the words of the great Wayne Gretzky, “A good hockey player plays where the puck is. A great hockey player plays where the puck is going to be.” Let’s keep the puck on the ice. Go Red Wings!
Ivo Nelson is chairman of Encore Health Resources, a healthcare IT consulting organization.
From DVR-Challenged to an EHR?
By Gregg Alexander
Bringing real change to healthcare information integration will never happen until the focus is off of the “technology” and onto the training, education, implementation, and ongoing usage support of such complicated tools. Period.
Of course you can force the horse, but he he’ll die of dehydration if he can’t figure out how to drink. Geeks docs get it, but most clinicians are not geeks and couldn’t care less about technology if it doesn’t:
1. Make their lives easier;
2. Strengthen their profit margins;
3. Help them be better doctors, AND;
4. Come with ongoing, easy-to-access, stupid-simple support.
Number 4 is probably the most important, yet most often shortchanged component of these quadrangular conditions. Both the technology and the issues it is trying to support (healthcare issues) are far too complex for the general masses of providers to wrap their brains around all together. Just being a clinician is hard enough. Giant new learning curves for techno-tools which – let’s face it – don’t really hold much fascination for most normal folks are off-putting, even repulsive.
Here’s what I hear: “With pen and paper, I can be a decent doctor (#3), get by financially (#2), and I already, almost innately, know how to use them (#1). Sure, paper has a ton of associated problems, but until there are sufficient helpmates (#4) to hump me over that technological learning curve mountain, I’ll do what I know and spend my extra time trying to get the hang of my DVR. By the way, speaking of computers, what’s this Twitter thing? Is it … (hushed) … sexual?”
Dr. Gregg Alexander is a grunt-in-the-trenches pediatrician and geek. His personal manifesto home page…er..blog…yeh, that’s it, his blog – and he – can be reached through http://madisonpediatric.com or firstname.lastname@example.org. He writes regularly for HIStalk Practice, but we decided to put him on HIStalk this time just for fun.
Blade Server Review – Main Features and Values
By The PACS Designer
There has been a lot of press lately about blade server architectures, so TPD thought it would be a good idea to highlight some of the main features of this type of architecture.
A blade is a plug-in device that is installed in a chassis. Its Wikipedia description reads, "The name blade server appeared when a card included the processor, memory, I/O and non-volatile program storage (flash memory or small hard disk(s)). This allowed manufacturers to package a complete server, with its operating system and applications, on a single card / board / blade. These blades could then operate independently within a common chassis, doing the work of multiple separate server boxes more efficiently. In addition to the most obvious benefit of this packaging (less space-consumption), additional efficiency benefits have become clear in power, cooling, management, and networking due to the pooling or sharing of common infrastructure to supports the entire chassis, rather than providing each of these on a per server box basis."
Blade servers and storage systems generally consume 50% less energy than traditional servers. They also occupy much less floor space, so valuable real estate can be put to better use. They also require fewer cables, have smaller power needs, and fit into 19" slots in a chassis.
Blade servers won’t replace mainframes any time soon, but they will be deployed for Web solutions and cloud computing. An effort to move mainframe software to external users through conversion to SOA and REST solutions would typically be good for installation on blade server/storage systems, provided adequate security methods have been installed.
IBM’s partnership with Sentry Data Systems, which serves pharmacies and hospitals in over 20 states, is an example of a cloud solution that was deployed to reduce power consumption and meet the growing needs for servers in a smaller operating space with less cabling.
Since the genie is out of the bottle, so to speak, for Web 2.0 and cloud computing, we will be seeing more need for blade systems solutions in the years ahead.