Free EMR Newsletter Want to receive the latest news on EMR, Meaningful Use, ARRA and Healthcare IT sent straight to your email? Join thousands of healthcare pros who subscribe to EMR and EHR for FREE!

Cracking Open the Shell on the Personal Health Record

Posted on November 5, 2014 I Written By

Andy Oram is an editor at O'Reilly Media, a highly respected book publisher and technology information provider. An employee of the company since 1992, Andy currently specializes in open source, software engineering, and health IT, but his editorial output has ranged from a legal guide covering intellectual property to a graphic novel about teenage hackers. His articles have appeared often on EMR & EHR and other blogs in the health IT space. Andy also writes often for O'Reilly's Radar site ( and other publications on policy issues related to the Internet and on trends affecting technical innovation and its effects on society. Print publications where his work has appeared include The Economist, Communications of the ACM, Copyright World, the Journal of Information Technology & Politics, Vanguardia Dossier, and Internet Law and Business. Conferences where he has presented talks include O'Reilly's Open Source Convention, FISL (Brazil), FOSDEM, and DebConf.

The concept of maintaining your own health data enjoyed a brief flurry of activity a few years ago with Google Health (now defunct) and Microsoft HealthVault (still active but not popular). It has gotten a second chance with Apple HealthKit, Google Fit, and other corporate offerings explicitly tied in with the convenience of mobile devices. Microsoft itself has galvanized HealthVault with a Microsoft Health initiative similar to Apple’s HealthKit. Recently I’ve been talking to health care reformers about the business and political prospects for personal health records (PHRs).

Patient access to data was enshrined as a right back when HIPAA was passed and is still championed by the US government through Meaningful Use (whose Stage 3 may well focus on it) and other initiatives, and has been endorsed by the industry as well. But this requirement won’t be satisfied by the limited patient portals that hospitals and clinics are hanging out on the Web. Their limitations include:

  • Many provide only viewing data, not downloading or transmitting it (all of these are mandated by Meaningful Use).
  • Data maintained by providers can’t easily be combined into a holistic, comprehensive view, which is what providers need to provide good care.
  • Data on portals is usually a thin sliver of all the data in the record: perhaps prescriptions, appointments, and a few other bare facts without the rich notes maintained by clinicians.
  • You can’t correct errors in your own data through a portal.
  • Clinicians rarely accept data that you want to put in the record, whether personal observations or output from fitness devices and other technical enhancements.

All these problems could be solved by flexible and well-designed personal health records. But how does the health care field navigate the wrenching transition to giving people full control over their own data?

Dr. Adrian Gropper has investigated PHRs for years and even considered building a simple device to store and serve individual’s health data. Now he says, “I can’t recall any physician in my medical society that has ever said they wished their patient had a PHR. Nor do I, after many years on the Society for Participatory Medicine list, ever recall a patient praising the role of their PHR in their care. Today’s PHRs are clinically irrelevant.”

This is not a condemnation of PHRs, but of the environment in which vendors try to deploy them. Many health reformers feel that several aspects of this care environment must evolve for PHRs to be accepted:

  • PHR data must become appealing to doctors. This means that device manufacturers (and perhaps patients themselves) must demonstrate that the data is accurate. Doctors have to recognize value in receiving at least summaries and alerts. Many benefits can also accrue from collecting vital statistics, behavioral data, and other aspects of patients’ daily lives.
  • The doctor’s EHR must seamlessly provide data to the patient, and (we hope) seamlessly accept data from the patient–data that the doctor acts on. Currently, most manufacturers store the data on their own sites and offer access through APIs. Another programming step is required to get the data into the PHR or the doctor’s EHR.
  • Clinicians have to agree on how to mark and collect the provenance of data. “Provenance” deals with assertions such as, “this data was generated by a Fitbit on October 10, 2014” or “this diagnosis was challenged by the patient and changed on August 13, 2010.”
  • Add-on services must make the data interesting and usable to both patients and physicians. For instance, such apps can alert the patient, clinician, or family members when something seems wrong, let them visualize data taken from the PHR and EHR over time, get useful advice by comparing their data to insights from research, and track progress toward the goals they choose.

“A critical force in increasing consumer engagement in digital health is the development of compelling, easy to use tools that make it simple to collect, understand and use health information to reach the goals consumers define for themselves, whether that’s managing a chronic condition, saving money, or fitting into their ‘skinny jeans’,” writes Lygeia Ricciardi, former director of the Office of Consumer e-Health at the ONC. “In an age of ‘one click purchasing,’ it must become incredibly easy for patients to access and share their own health information digitally–if it’s too complex or time consuming, most people probably won’t do it.”

In addition to sheer inertia, a number of disincentives keep PHRs from congealing.

  • Many doctors are afraid of letting patients see clinical notes, either because the patient will ask too many questions or will be upset by the content.
  • Hospitals and clinics want control over records so that patients will return to them for future treatment.
  • Marketing firms live off of rich data lodes on our health data.
  • Other organizations with dubious goals, commercial and governmental, want to track us so they can deny us insurance or control our lives in other ways.

Wait–what about the patients themselves? Why haven’t they risen up over the past several years to demand control over their data? Well, maintaining your health data is intimidating. The data is highly detailed and full of arcane medical concepts and terminology. Most patients don’t care until they really need to–and then they’re too sick and disabled to form an effective movement for patient control.

Still, several leaders in health care believe that a viable business model can be built on PHRs. The spark of hope comes from the success of apps that make people pay for privacy, notably SnapChat and Whatsapp. Although some sloppy privacy practicies render these services imperfect, their widespread use demonstrates that people care about protecting their personal data.

Private storage can be offered both in the cloud and by personal devices, using standardized services such as Direct and Blue Button. These will start out as high-end services for people who are affluent and have particular concerns about storing their own data and choosing how it is shared. It will then become commoditized and come down in price.

What about people who can’t afford even the modest prices for cloud storage? They can turn patient data into a civil rights issue. There’s a potent argument that everyone has the right to determine who can get access to their health data, and a right to have data generated during their daily lives taken into account by doctors.

We don’t need one big central service–that’s insecure and subject to breaches. Multiple services and distributed storage reduce security risks.

We’ll see change when a substantial group of people start to refuse to fill out those convoluted forms handed to them as them enter a clinic, saying instead, “Get it from my web site before you treat me.” Before that protest begins, there’s a lot of work in store for technologists and businesses to offer patients a usable record system open to the wide range of data now available for health.

EHR Adoption Percentage, EHR Story, and Future of EHR

Posted on May 12, 2013 I Written By

John Lynn is the Founder of the blog network which currently consists of 10 blogs containing over 8000 articles with John having written over 4000 of the articles himself. These EMR and Healthcare IT related articles have been viewed over 16 million times. John also manages Healthcare IT Central and Healthcare IT Today, the leading career Health IT job board and blog. John is co-founder of and John is highly involved in social media, and in addition to his blogs can also be found on Twitter: @techguy and @ehrandhit and LinkedIn.

I always love to grab the various EHR adoption numbers. Seems like most are hovering around the 60% number now. This one says 57% EHR adoption.

Of course, this is coming from ONC’s Twitter account, but I’m always happy to read someone’s story. If you’re willing to put your name to it, I’m willing to read it and see what you have to say. Plus, he takes a realistic look at some of the benefits of an EHR in a real matter of fact way.

This is probably the most focused and well written description of the real reasons why EHR software is a disappointment today. Unfortunately, the issues described are a fundamental problem with the healthcare system and something unlikely to change in the near future.

Microsoft and GE Announce Healthcare Joint Venture

Posted on December 12, 2011 I Written By

Priya Ramachandran is a Maryland based freelance writer. In a former life, she wrote software code and managed Sarbanes Oxley related audits for IT departments. She now enjoys writing about healthcare, science and technology.

I got suckered into article-hopping on TechCrunch reading Dave Chase’s opinion piece on Microsoft’s recent joint venture with GE Healthcare, only Chase’s headline reads “Microsoft Ends Another Vertical Market Dalliance—This Time In Healthcare”. Two hours later, here I am with the post I should have written right away.

Regarding the joint venture, here’s what the Microsoft spin machine put out, and here’s the original New York Times blogpost that first broke the news.

To summarize: Microsoft and GE will be joining forces in a healthcare joint venture, if and when the deal gets regulatory approval. Some of Microsoft’s healthcare projects like Amalga, Vergence, and expreSSO will now form part of the joint venture. The new company has not been named, but there are plans to hire 750 people, sourced from Microsoft, GE and elsewhere.

– HealthVault still remains with Microsoft.

I’m not a Microsoft fan by any standards but I’m not so sure it’s a bad idea for Microsoft to want to join forces with GE, and keep HealthVault inhouse. And I’m also not sure I’d term the process an end to Microsoft’s healthcare plans. It seems more of a shift in gears. However, Chase, who worked with Microsoft for 12 years, believes it is a sign of an exit given Microsoft’s old exit patterns. (Chase’s list of all the verticals Microsoft has exited from makes for interesting reading. Did you know Expedia used to be a Microsoft company? Me neither.) Posting in the discussion following the Tech Crunch article, Chase also insinuates that there have been layoffs among Amalga employees, though he doesn’t give any numbers.

The NYT post states that the aim for the new company is to provide a Windows like platform which developers can then use to create healthcare related apps and services on. It also rightly points out that EMR vendors like Epic and Cerner are not going to be falling head over heels building products for the new platform.

One of the most trenchant comments (to me at least) on the NYT post comes from a commenter called Manuel Albarracin:

“Also, beyond Epic or Cerner, there will be others who will resist change along these lines, for this resistance comes not only from (legitimately) wanting to protect market positions and commercial interests; it also comes from a subtle but entrenched (and not so legitimate) mentality to reinvent the wheel at every healthcare organization, to ‘control things our way’, thus creating ‘walled-gardens’ in each of them.”

Which is probably what Microsoft has in mind – to provide the framework that the apps are built on. If the Windows experience is anything to go by, we should be in for an interesting ride.

Mayo Clinic Launches PHR Available to Anyone

Posted on May 14, 2009 I Written By

John Lynn is the Founder of the blog network which currently consists of 10 blogs containing over 8000 articles with John having written over 4000 of the articles himself. These EMR and Healthcare IT related articles have been viewed over 16 million times. John also manages Healthcare IT Central and Healthcare IT Today, the leading career Health IT job board and blog. John is co-founder of and John is highly involved in social media, and in addition to his blogs can also be found on Twitter: @techguy and @ehrandhit and LinkedIn.

Here’s the story from the American Medical News:

The Mayo Clinic announced the launch of a new personal health record system that will be available to anyone, including those who are not Mayo patients. Those involved with the project say the system, powered by Microsoft HealthVault, could also carry benefits for non-Mayo physicians.

Is it just me, or is my headline (which is theirs also) really misleading? When I saw the headline I was really interested to see the type of PHR that Mayo Clinic had created. Instead, all they’re doing is adopting Microsoft HealthVault. That’s a big win for Microsoft HealthVault, but that’s been publicly available for a while. I’m not sure why Mayo Clinic joining HealthVault makes it any more available to those outside of Mayo.

The more interesting part of the article is when they talk about Mayo Clinic moving forward despite Beth Israel Deaconess Medical Center in Boston stopping claims data from being sent to Google Health:

The launch of Mayo’s system came days after Beth Israel Deaconess Medical Center in Boston announced it would stop sending claims data to patients’ Google Health accounts due to the possibility that the data contain errors. The move reignited the debate over whether PHRs can contain too much data that is not useful to physicians, or dangerous for them to rely on.

Mayo’s system will allow the import of claims data through Health Vault, but Mayo’s physicians will likely not use it, the organization said. Other patients and their physicians can choose whether the information is relevant enough to be kept.

I’d still like to see better support for PHR in various EMR and EHR products. However, until there’s a good standard I don’t expect that to happen anytime soon.