Reviews

Meet the replacement for .Mac: MobileMe

I mentioned in yesterday’s iPhone 3G announcement that Apple had secretly purchased the domain me.com for an undisclosed sum of money (in the neighborhood of 11 million). It came as no surprise to Apple fans when we found out that MobileMe was the replacement for .Mac. Users had griped for years about .Mac’s lackluster performance and puny space available (1GB for $99/year last I used it).

So, other than the new domain name (personally, I liked the .Mac domain), how’s the new service different?

  • More space: 20GB for the same price ($99/year for individuals and $149/year for a family pack). Additional space is $49/year for another 20GB or $99/year for another 40GB.
  • Push… everything: Apple has upgraded their .Mac email service and calendar and contact syncing to “push” technology. I don’t really see what’s different here when I compare it to .Mac, except the syncing is seamless and faster. And oh, now it works with PCs/Exchange as well.
  • Great web interface: Apple outdid itself here. .Mac had a web interface as well, but it was slow and kludgy. The new web interface behaves like desktop applications and looks really, really nice. Not sure how fast it loads on regular broadband connections, but we’ll find out soon, won’t we?

That’s about it, really. The bulk of the effort went into the better, cross-platform syncing and the innovative, beautifully-designed web interface. The additional space was long overdue.

Existing .Mac members will be upgraded automatically to MobileMe, and their existing subscriptions will be transferred over to the new service when it becomes available on July 11.

What’s the draw to MobileMe? For me, it’s the Back to My Mac service, which was introduced alongside iChat Screen Sharing in Leopard. It wasn’t enough to get me back when .Mac was overpriced and underfeatured, but it may be enough now that MobileMe has more space and is better designed. For iPhone users, it’s the obvious integration and contact/calendar syncing between the phone and the computer(s).

In terms of web storage space, the 20GB isn’t really that big of a deal for me. There are PLENTY of companies out there that offer more space. ADrive, for example, offers 50GB for free, and they’ve worked reliably for the past several months that I’ve used them. Dropbox, although it offers less space for free, has incredibly nice integration between Macs and PCs, and lets me share files seamlessly from computer to computer, or with my friends.

What I have to wonder about is Gmail. Given the partnership between Apple and Google, I’d have hoped that Google products would be better integrated into MobileMe somehow. It seems they’ve still been left by the wayside. They work, but not quite. I still can’t sync my calendar appointments properly from Gmail to iCal, and still can’t sync my contacts properly from Addressbook to Gmail (unless I have an iPhone or iPod Touch). Even Gmail’s IMAP interface in Mail leaves a lot to be desired. After using it for a few months, I switched back to POP3.

That’s annoying. I suppose it may have had something to do with Apple’s desire to keep building on their existing products and to develop an Apple-designed web interface (which is quite different from the spartan design of Google’s products).

Images used courtesy of Apple, Inc. More information about MobileMe can be found in Apple’s original press release, or on the MobileMe website.

Standard
Reviews

Drobo overestimates used space

Here’s what happens. When the Drobo is connected to a computer and the Drobo Dashboard software isn’t running, the Drobo’s capacity meter will overestimate the used space, potentially triggering a low space alert. When the Drobo Dashboard software is started, it does its own used space calculations and corrects the capacity meter, literally turning off one to two or even three of the blue LEDs that indicate how much space is used.

There are 10 blue LEDs, one for each 10% of space used on the Drobo. When I connect one of my Drobos to my computer, the capacity meter lights up 9 of the LEDs, indicating 90% disk space used. When I start up the Drobo Dashboard software, two of the lights are turned off, leaving 7 on, or 70% disk space used. Also, although low space warnings are triggered when the Drobo Dashboard is started, after it calculates the space used, the warning go away, and the Dashboard screen goes from yellow to green.

I made a video which shows this quite clearly. I apologize for its poor quality, but I made it without any prior setup, just to show you that I’m not making this up. This also happens for my other Drobo, where the capacity meter shows 50% disk space used when I connect it, but drops to 30% disk space used when I start up the Drobo Dashboard. If you have a Drobo yourself, try it out and see.

Download Drobo overestimates used space (640×480, MP4, 35MB)

I notified Drobo Support of this issue a couple of days ago, but I have not yet received a reply from them. I will be glad to include any feedback/clarification from them right here, and will update this post with further information as I receive it.

I should also point out that there’s still no fix for the other two issues I outlined in my original Drobo review recently, where I pointed out that:

  • The transfer speed slows down significantly (and somewhat inversely proportional) to the amount of disk space remaining on the Drobo after the 70% mark is reached. In other words, the less space there is (in terms of the percentage, not GB remaining), the slower it’s going to be to access and transfer data to the Drobo.
  • The Drobo becomes excessively noisy when the fourth hard drive is inserted, and the fan will go into high gear when the Drobo isn’t even used. It seems this is loosely tied to the ambient room temperature, and once it goes over 75 degrees Fahrenheit, the fan kicks on and stays on for a long time. But again, you’ll only see this issue when the 4th hard drive is inserted. Given that the Drobo is a consumer device which is meant to operate at room temperatures, not in a climate-controlled server room, this is not appropriate behavior and should be corrected.
Standard
Reviews

Google Health is a good thing

When it launched a few weeks ago, Google Health received fairly lackluster reviews. Privacy issues and lack of features were the main complaints. Well, I’m here to tell you those initial views are wrong.

Even if you’re a long-time reader of my site, you may not know what qualifies me to make that statement, so let me tell you a bit about myself.

My background

A few years ago, I was Director of Health Information Systems at a South Florida hospital, where I implemented an electronic medical records system. My job was fairly unique, because I not only wrote the policies and procedures for the system and oversaw its implementation, but I also rolled up my sleeves and built the various screens and forms that made it up. I, along with my staff, also built and maintained the servers and databases that housed it.

As far as my education is concerned, I hold a Master’s Degree in Health Services Administration (basically, hospital administration). I was also admitted to two medical schools. I ended up attending one for almost a year until I realized being a doctor wasn’t for me, and withdrew.

For plenty of years, I’ve been a patient of various doctors and hospitals, as have most, if not all of you, for one reason or another.

Furthermore, my father is a doctor: a psychiatrist. He has a private practice, and also holds a staff job at a hospital. My mother handles his records and files his claims with the insurance companies, using an electronic medical records system. I get to hear plenty of stories about insurance companies, billing ordeals, hospitals and the like.

So you see, I’ve seen what’s involved with medical records and access to said records from pretty much all sides of the equation. Again, I say to you, Google Health is a good thing, and I hope you now find me qualified to make that statement.

The benefit of aggregation

Just why is it such a good thing? Because I wish I could show you your medical records — or rather, their various pieces — but I can’t. That’s because they exist in fragments, on paper and inside computer hard drives, spread around in locked medical records facilities or in your doctors’ offices, all over the place. If you endeavored to assemble your complete medical history, from birth until the present time, I dare say you’d have a very difficult time getting together all of the pieces of paper that make it up — and it might not even be possible. That’s not to mention the cost involved in putting it together.

A few of the problems with healthcare data sharing

Do you know what my doctor’s office charges me per page? 65 cents, plus a 15 cent service fee. For a 32 year old male (that’s me) it would take a lot of pages (provided I could get a hold of all of them) and a lot of money to put my medical record together.

The sad part is that this is MY medical information we’re talking about. It’s information that health services workers obtained from MY body. It’s MY life and MY record, yet I can’t have access to it unless I fill in a special form at every doctor’s office I’ve ever visited, and pay for the privilege. Is that fair? NO. Can something be done about it? YES, and so far, Google Health is the only service I’ve seen that is trying to pull together all of the various pieces that make up my medical record, for my benefit and no one else’s. Sure, the system is in its infancy, and there’s a lot of work to be done to get it up to speed, but that’s not Google’s fault.

I’ve been inside the healthcare system, remember? I know how things work. I know how slowly they work, to put it mildly. I know how much resistance to change is inherent in the system. Just to get medical staff to use an electronic medical records system is still a huge deal. The idea of giving the patient access to the records, even if it involves no effort on the part of the medical staff (but it does, as you’ll see shortly) is yet another big leap.

Let’s also not forget to consider that medical records systems are monsters. Each is built in its own way. There are certain lax standards in place. Certain pieces of information need to be collected on specific forms. The documentation needs to meet certain coding standards as well, or the hospitals or doctors’ offices or pharmacies won’t get reimbursed. There are also certain standards for data sharing between systems, and the newer systems are designed a little better than older ones.

Yet the innards of most medical health systems are ugly, nasty places. If you took the time to look at the tables and field names and views and other such “glamorous” bits inside the databases that store the data, you’d not only find huge variations, but you’d also find that some systems still use archaic, legacy databases that need special software called middleware just so you can take a peek inside them, or form basic data links between them and newer systems. It’s a bewildering patchwork of data, and somehow it all needs to work together to achieve this goal of data sharing.

The government is sort of, kind of, pushing for data sharing. There’s NHIN and the RHIOs. There are people out there who want to see this happen and are working toward it. Unfortunately, they’re bumping up against financial and other barriers every day. Not only are they poorly funded, but most healthcare organizations either do not want or cannot assign more money to either getting good record systems or improving their existing ones to allow data sharing.

Add to this gloriously optimistic mix the lack of educated data management decisions made in various places — you know the kind of decisions that bring in crappy systems that cost lots of money, so now people have to use them just because they were bought — and you have a true mess.

Oh, let’s also not forget HIPAA, the acronym that no one can properly spell out: Health Insurance Portability and Accountability Act. The significant words here are Insurance and Accountability. That’s government-speak for “CYA, health organizations, or else!” There’s not much Portability involved with HIPAA. In most places, HIPAA compliance is reduced to signing a small sticker assigned to a medical records folder, then promptly forgetting that you did so. Your records will still be unavailable to you unless you pay to get them. Portability my foot…

Benefits trump privacy concerns

Alright, so if you haven’t fallen asleep by now, I think you’ve gotten a good overview of what’s out there, and of what’s involved when you want to put together a system like Google Health, whose aim is to pull together all the disparate bits of information that you want to pull together about yourself. Personally, I do not have privacy concerns when it comes to Google Health. There are more interesting things you could find about me by rummaging through my email archives than you could if you went through my health records. If I’m going to trust them with my email, then I have no problems trusting them with my health information, especially if they’re going to help me keep it all together.

Not sure if you’ve used Google Analytics (it’s a stats tool for websites). Not only is it incredibly detailed, but it’s also free, and it makes it incredibly easy to share that information with others — should you want to do it. You simply type in someone’s email address in there, and you grant them reader or admin privileges to your stats accounts. Instantly, they can examine your stats. Should you prefer not to do that, you can quickly export your stats data in PDF or spreadsheet format, so you can attach it to an email or print it out, and share the information that way.

I envision Google Health working the same way. Once you’ve got your information together, you can quickly grant a new doctor access to your record, so they can look at all your medical history or lab results. You’ll be able to easily print out immunization records for your children, or just email them to their school so they can enroll in classes. A system like this is priceless in my opinion, because it’ll make it easy to keep track of one’s health information. Remember, it’s YOUR information, and it should NOT stay locked away in some hospital’s records room somewhere. You should have ready access to it at any time.

Notice I said “whose aim is to pull together all the disparate bits of information you WANT to pull together” a couple of paragraphs above. That’s because you can readily delete any conditions, medications or procedures you’d rather keep completely private from Google Health. Should you import certain things into it that you don’t feel safe storing online, just delete that specific thing, and keep only the information you’d be comfortable sharing with others. It’s easy; try it and see.

Lots of work has already been done

Another concern voiced by others is that there isn’t much to do with Google Health at the moment — there isn’t much functionality, they say. I disagree with this as well. Knowing how hard it is to get health systems talking to each others, and knowing how hard it is to forge the partnerships that allow data sharing to occur, I appreciate the significant efforts that went on behind the scenes at Google Health to bring about the ability to import medical data from the current 8 systems (Beth Israel Deaconess, Cleveland Clinic, Longs, Medco, CVS MinuteClinic, Quest, RxAmerica and Walgreens).

What’s important to consider is that Google needed to have the infrastructure in place (servers, databases) ready to receive all of the data from these systems. That means Google Health is ready to grow as more partnerships are forged with more health systems.

In order to illustrate how hard it is to get other companies to share data with Google Health, and why it’s important to get their staff on board with this new development in medical records maintenance, I want to tell you about my experience linking Quest Diagnostics with Google Health.

Quest is one of the companies listed at Google Health as having the ability to export/share their data with my Google Health account. What’s needed is a PIN, a last name and a date of birth. The latter two are easy. The PIN is the hard part. While the Quest Diagnostics websites has a page dedicated to Google Health, where they describe the various benefits and how to get started, they ask people to contact their doctors in order to obtain a PIN. I tried doing that. My doctor knew nothing about it. Apparently it’s not the same PIN given to me when I had my blood drawn — by the way, that one didn’t work on Quest’s own phone system when I wanted to check my lab results that way…

Quest Diagnostics lists various phone numbers on their site, including a number for the local office where I went to get my bloodwork done, but all of the phone numbers lead to automated phone systems that have no human contact whatsoever. So Quest makes it nearly impossible to get in touch with a human employee and get the PIN. Several days later, in spite of the fact that I’ve written to them using a web form they provided, I still don’t have my PIN and can’t import my Quest Diagnostics lab results into my Google Health account.

Updated 5/27/08: Make sure to read Jack’s comment below, where he explains why things have to work this way with Quest — for now at least.

That is just one example of how maddening it is to try and interact with healthcare organizations, so let me tell you, it’s a real feat that Google managed to get eight of them to sign up for data sharing with Google Health. It’s also a real computer engineering feat to write the code needed to interact with all those various systems. I’m sure Google is working on more data sharing alliances as I write this, so Google Health will soon prove itself even more useful.

More work lies ahead

I do hope that Google is in it for the long run though, because they’ll need to lead data sharing advocacy efforts for the next decade or so in order to truly get the word out to patients, healthcare organizations and providers about the benefits of data sharing and Google Health.

For now, Google Health is a great starting point, with the infrastructure already in place and ready to receive more data. I’m sure that as the system grows, Google will build more reporting and data export capabilities from Google Health to various formats like PDF, as mentioned several paragraphs above, and then the system will really begin to shine. I can’t stress enough what a good thing this is, because just like with web search, it puts our own medical information at our fingertips, and that’s an invaluable benefit for all.

Join me for a short screencast where I show you Google Health. You can download it below.

Download Google Health Screencast

(6 min 28 sec, 720p HD, MOV, 39.8MB)

Standard
Thoughts

Where are the Condensed Knowledge posts?

Good question. Some of you have gotten quite accustomed to those daily Condensed Knowledge posts, and they’ve gone AWOL since last week. On the other hand, others have told me they were distracting, and detracted from the substance of my site.

I’d been giving the matter some thought myself, and in the end, sided with the folks who said I should stick to writing original content. You see, while I enjoy sharing the information with you, and while I also believe that it’s important to highlight valuable content on the Internet, those posts were distracting me from writing. Since I had something to post every day, other than my own writing, I tended to do less of it, and that was not good.

So, for the time being, no more Condensed Knowledge posts. That’s not to say you can’t access them anymore. You still can, but in a separate feed: feeds.feedburner.com/FavoriteBlogPosts. Subscribe to it if you’d like. The feed is actually more reliable than the method I used with the Condensed Knowledge posts, which was to share items from Google Reader, publish them to Twitter, then use the Twitter Tools plugin to collect them in a daily summary. That method was highly dependent on Twitter’s uptime/downtime, and that meant you weren’t getting the full link list every day. With the feed, you are getting everything I share from Google Reader.

I can’t deny I’d rather have the same link summaries present in my site feed, just like with my daily del.icio.us links, and perhaps at some point in the future that’ll be possible, but until then, the separate feed will do just fine.

If you have any questions, let me know in the comments and I’ll see if I can answer them.

Standard
Lists

Condensed knowledge for 2008-03-14

Standard