For me, today’s technical travails started with morning coffee. As in, a piping-hot pint of it dumped on my work laptop keyboard. The nightmare came with the realization that dependency on desktop-based applications almost deep-sixed a high-priority piece of content for SearchHealthIT: a podcast recorded with a National Health IT Week participant who had taken time out of his packed schedule to chat with us from his hotel room in D.C.
With TechTarget’s virtualization efforts and other available tools, it would seem to be pretty straightforward to find alternate paths to accomplishing a podcast. After all, it’s just recording a phone conversation and routing a 70MB audio file to the proper colleagues not even 40 miles away. Piece of cake, right?
Yet, there was no way around connecting that laptop to our VPN because part of the process required to move the audio file from my machine to the network used desktop-based applications tied to the intermittently failing laptop. The only way out of the problem was through that laptop, whose “u” key was stuck down most of the time, as was “page up.” The USB ports would work — but for only a little while at a time.
Some of the podcast-making aspects were cloud-based; for example, I accessed the conference dial-in number and passcode via smartphone. Both email and instant messaging collaboration could be done from other laptops or even my iPad via the Web. Even this blog post was composed in WordPress on a different computer than the one we shall refer to as “the barista.”
In the end, if I couldn’t find a working USB port on the coffee-soaked lapper, it was doomsday for today’s podcast. No way around the bottleneck. All’s well that ends well — the barista held together for four consecutive minutes to upload the audio over the VPN, and coworkers covered a couple Microsoft Word-related processes the cloud alternatives couldn’t.
The talk at the instant-messenger water cooler after the ordeal was mostly over was: if we can’t figure out pure cloud-based workflows for journalism, how can it possibly happen in health care?
From a technology-requirements point of view, journalism is child’s play compared to the heavy lifting of bits and bytes health care practitioners do with their volumes of text and image data and even, for some, video studies. Add to that the fact that many of these data sources are created in proprietary applications that don’t necessarily offer Web-based access, let alone iOS or Android apps. They’re grounded on the desktop. Let’s not mention the proprietary systems that record data from medical devices such as wireless patient monitors into databases, not all of which are cloud-friendly.
Lastly, let’s say I actually could figure out how to port all my journalism-related processes to the cloud. That’d require me clicking “OK” an awful lot along the way, probably giving a bunch of third parties permissions to basically do what they wish with my data — and if I don’t like it, too bad. Eventually, I’d probably indemnify them against data breaches — who reads all the fine print, anyway, at least on deadline? In the HIPAA era, physicians and their CIOs just can’t afford to take such wanton risks.
For all the insanely great iPad advertisements and IBM’s wondrous cloud commercials on network television telling us how smart our planet is, the world still belongs to desktop-based computers. Even if there are many opportunities to port some processes to the cloud, what good is an iPad or thin client if your team falls short of the goal line? Not much. That’s why I refuse to call my iPad an iPad, but rather a “10-inch iPod,” much to the delight of the Apple-haters around me.
Until the iPad can truly replace my work laptop as a terminal to my data in the cloud — and close my personal loop by providing the ability to generate and upload complex documents, created in templates that would make Apple Pages cry, as well as open and upload podcast recordings, interview transcription files, and Livescribe pencasts — it shall remain a 10″ iPod, an expensive Web browser that also can play songs wirelessly over my stereo. Stuff my iPod Touch already does.
Some forward-thinking technologists might suggest I look into Wi-Fi versions of my recording hardware or perhaps an iPhone call-recorder app; those indeed might all but close the loop in my personal workflow. But thinking about the infinitely more complex data workflow that health care practitioners employ with their own kit of proprietary devices, their cloud nirvana would appear to be years away.