One CIO's Random Thoughts on Healthcare (Part 3 of 3) | [node:field-byline] | Healthcare Blogs Skip to content Skip to navigation

One CIO's Random Thoughts on Healthcare (Part 3 of 3)

November 4, 2009
by Neal Ganguly
| Reprints

In the first part of this series (over a month ago), I examined the environment driving stimulus and some of the timing challenges that I saw in the various initiatives underway. The second part covered some of the misalignment that exists between the players and the challenges that lack of alignment poses to hospital CIOs.

In this installment I’ll discuss my thoughts on the alignment challenges. To do this, I’m expanding on the challenges covered in Part 2 with the qualifier that this list is still far from complete.

1. Hospital – Physician Alignment

a. Clear agreed upon clinical documentation standards

The latest meaningful use matrix specifies that an up-to-date problem list of current and active diagnoses be maintained using ICD-9 or SNOMED. In the absence of such direction several years ago, we opted to follow nursing standards and build our system on NIC, NOC, and NANDA. Now my team must review the work effort of mapping these nursing standards to SNOMED.

b. HIE / EMR Interoperability

Physicians are clamoring for advice on how to qualify for their piece of the stimulus pie. Our approach has evolved over time. The initial thought was to align with one or two EMR vendors and tight integrate them with our inpatient systems. This approach has several shortcomings, the most serious being the lack of flexibility for the physicians. The current thought involved implementing a local HIE using a commercial application (such as Medicity, MobileMD, Axolotl, etc.) to connect a wide range of EMRs to the hospital’s impatient system. This approach still includes negotiating with a small set of preferred vendors for discounted pricing, but doesn’t close the ‘integration door’ to providers that choose (or require) a different CCHIT compliant system.

c. CPOE

There are so many industry drivers leading us down this path, from Leapfrog all the way through Meaningful Use. This is one is a procrastinator’s dream and has been on the radar for years, but somehow always got deferred for other more pressing matters. Pressing matters defined as something people were more likely to use. The incredible amount of work that CPOE requires – in both build, and (more importantly) culture change, made it daunting. Meaningful use and the deadlines it imposes are forcing this initiative back to the top of the pile. The debate about standardized vs. customized order sets rages on…

d. Quality Measures

Regardless of what we do, and how we do it, it WILL need to be measured. Numerous regulatory bodies want to judge our performance and advertise it to the (often uninformed) public. However, these measures should not be viewed as onerous, rather they should be seen as an opportunity to finally track and improve operations. Key to effective measurement is the electronic capture of necessary data elements. This has a direct impact on how online documentation should be built. A carefully thought out documentation build can reduce the amount of manual work done for reporting dramatically. I am not minimizing the challenges involved in getting a nursing staff to agree to document additional information; it is an uphill climb (barefoot and in the snow). Once the data is captured, make sure it’s being used. Proper analysis and interpretation of this data should give health systems the edge they need to react to changing patient needs, and care delivery models.

e. The Dream

Alignment of the requirements for supporting hospital and physician billing, that would require the physician to document properly for their own reimbursement. No more chasing them to properly document the ejection fraction on a possible CHF case, or specify the lab finding in support of complex pneumonia. For those CIOs who have oversight of HIM, you know my pain.

2. Provider – Patient Alignment

a. Personal Health Record

The PHR is another meaningful use requirement that feels a little ahead of its time. Hospital IT departments will be scrambling to implement or modify applications to ensure that the infrastructure can support the meaningful use of data between the physician and the hospital. That will be daunting enough, without adding the complexities of dealing with the general public right out of the gate.

b. Touchpoints

Today, the patient provider interaction is very physical. As we move down the path of provider-patient alignment the organization must prepare for self service scheduling, remote consultations, and use of modern interaction methods such as social networking. Not sure what that will all ultimately look like, but we’re keeping our eyes open.

3. Government – Provider

a. Reporting Requirements; Regulatory Mandates; Reimbursement Audits

These are all pretty self explanatory – between the reporting discussed above, regulatory issues such as HIPAA 5010 and ICD-10, and RACMAC, etc audits, we’ve got our hands full.

I almost forgot…..

Healthcare Reform

On top of all of the above, let’s not forget that we’re also running a business. Functions such as Business Development, Finance, Payroll, Accounts Payable, HR / Recruitment, Materials Management, Facilities Management, Decision Support, Time & Attendance, Technical Support, Fundraising, Wellness Programs, and more are critical to ‘keeping the lights on’ and require significant IT attention.

All of this and more is done on an average of 2%-4% of a hospital’s revenue compared to 20% plus that is devoted to technology in other industries. The CIO and the IT Team must have their fingers on the pulse of the institution in so many ways. Is it any surprise that the few hairs most CIOs (male or female) have left are gray?

The Health IT Summits gather 250+ healthcare leaders in cities across the U.S. to present important new insights, collaborate on ideas, and to have a little fun - Find a Summit Near You!


/blogs/neal/one-cios-random-thoughts-healthcare-part-3-3

See more on

betebettipobetngsbahis