News

05:36 PM
Connect Directly
RSS
E-Mail
50%
50%

Google Launches Its Own PHR

Why insurance carriers might ultimately be the key to success for Google's newly launch PHR initiative.

On Monday, Google announced that it has started to offer online personal health records to the public. The Google PHR, which provides users with tools to collect manage and store their personal health information online, was previously only available to patients at the Cleveland Clinic as part of a pilot program.

From InformationWeek:

For years, the Cleveland Clinic has provided its patients with electronic access to their health information via the clinic's MyChart initiative. But back in February, the clinic and Google announced that 1,600 MyChart patients were involved with a pilot in which they could add information online about their medical histories and conditions.

That's because like most Americans who get their health care from multiple providers -- specialists, family physicians, dentists, eye doctors, and so on -- many Cleveland Clinic patients also receive their care from multiple providers, many of whom may not be part of the clinic.

By having a Google Health account, Cleveland Clinic patients who were part of the pilot -- and now any patient anywhere -- have the ability to enter medical information into their Google PHR, whether it be about treatments they're receiving from other doctors, medical history, allergies, or the drugs doctors have prescribed to them.

InformationWeek also says that third-party alliances -- such as those with pharmacy chains, testing labs and prescription drug management companies -- will be key to Google's initiative. However, it's my opinion that biggest outside player to the ultimate success of Google's PHR or similar programs such as one launched by Microsoft last fall will be the insurance industry.

Certainly, PHRs can help improve patients' quality of health care by providing physicians and other healthcare providers with a more holistic clinical record. Still, PHRs are only as valuable as the information they contain.

What if a patient forgets to add a new drug they're taking to their PHR? What if they aren't vigilant enough in updating their PHR with their most recent medical history? In some cases, PHR integrations with physician or third-party data feeds can help catch what falls through the cracks.

Health insurers, though, with their claims data are best equipped to fill-in those gaps. Just about any patient is going to receive healthcare from multiple sources in a given year or over the course of a few years. What will remain relatively consistent will be the health insurer handling all those disparate claims.

It seems to me that the best way to keep PHRs up-to-date (and thus, actually useful) isn't to rely on patients to populate the records with data. It's to create a central depository for a patients medical data by integrating with disparate data sources . Then, allow the patient to control it. Let them choose how to use that information and which health care providers they want to have access to it. In that scenario, claims data would be key.

If Google or Microsoft are looking to improve the usefulness of their respective online health management efforts, they'd be well served to partner with as many insurers as possible. Of course, then the questions becomes: will insurers, many of which have PHR offerings of their own, be willing to cooperate?Why insurance carriers might ultimately be the key to success for Google's newly launch PHR initiative.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: This is a secure windows pc.
Current Issue
Security Operations and IT Operations: Finding the Path to Collaboration
A wide gulf has emerged between SOC and NOC teams that's keeping both of them from assuring the confidentiality, integrity, and availability of IT systems. Here's how experts think it should be bridged.
Flash Poll
New Best Practices for Secure App Development
New Best Practices for Secure App Development
The transition from DevOps to SecDevOps is combining with the move toward cloud computing to create new challenges - and new opportunities - for the information security team. Download this report, to learn about the new best practices for secure application development.
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2017-0290
Published: 2017-05-09
NScript in mpengine in Microsoft Malware Protection Engine with Engine Version before 1.1.13704.0, as used in Windows Defender and other products, allows remote attackers to execute arbitrary code or cause a denial of service (type confusion and application crash) via crafted JavaScript code within ...

CVE-2016-10369
Published: 2017-05-08
unixsocket.c in lxterminal through 0.3.0 insecurely uses /tmp for a socket file, allowing a local user to cause a denial of service (preventing terminal launch), or possibly have other impact (bypassing terminal access control).

CVE-2016-8202
Published: 2017-05-08
A privilege escalation vulnerability in Brocade Fibre Channel SAN products running Brocade Fabric OS (FOS) releases earlier than v7.4.1d and v8.0.1b could allow an authenticated attacker to elevate the privileges of user accounts accessing the system via command line interface. With affected version...

CVE-2016-8209
Published: 2017-05-08
Improper checks for unusual or exceptional conditions in Brocade NetIron 05.8.00 and later releases up to and including 06.1.00, when the Management Module is continuously scanned on port 22, may allow attackers to cause a denial of service (crash and reload) of the management module.

CVE-2017-0890
Published: 2017-05-08
Nextcloud Server before 11.0.3 is vulnerable to an inadequate escaping leading to a XSS vulnerability in the search module. To be exploitable a user has to write or paste malicious content into the search dialogue.

Dark Reading Radio
Archived Dark Reading Radio
In past years, security researchers have discovered ways to hack cars, medical devices, automated teller machines, and many other targets. Dark Reading Executive Editor Kelly Jackson Higgins hosts researcher Samy Kamkar and Levi Gundert, vice president of threat intelligence at Recorded Future, to discuss some of 2016's most unusual and creative hacks by white hats, and what these new vulnerabilities might mean for the coming year.