Personal health records (PHRs) are evolving toward becoming Personal Health Record Systems (PHRSs).
…that’s my key takeaway from attending the Robert Wood Johnson Foundation (RWJF) Project Health Design (PHD) conference in Washington D.C. on September 17. The conference was entitled A ‘Report Out’ from Project HealthDesign and Forum on Next-Generation PHRs .
A PHD Fact Sheet capsulizes the evolution from PHRs to PHRSs:
…next generation PHRs should pair personal health information with powerful technology tools that interpret people’s health data and provide tailored feedback to support their daily health decisions. PHD envisions the PHRs of tomorrow to be part of a broader personal health record system that supports people’s different levels of ability to care for themselves, health literacy, familial supports, technological fluency and other factors….The next generation of PHRs lies in their capacity to be coupled with alerts, reminders and other decision-support tools that help people take action to improve their health or manage their conditions.
“It’s not the record, it’s what you do with it”, summed up RWJF President and CEO Dr. Risa Lavizzo-Mourey.
The content of PHRs is expanding to include Observations of Daily Living (ODLs) — information about your diet, physical activity, pain, sleep patterns, adherence to medication, etc. The diagram below illustrates my sense of how both patients and clinicians tend to view PHRs today relative to Electronic Health Records (EHRs). The basic idea here is that most people think of the PHR as a subset of their medical data — which is only the tip of the iceberg.
The second diagram shows how PHRs are evolving. Tomorrow the PHR will become a much broader concept than an EHR as more and more ODL information is added.
My intuition is that patients will do much better than clinicians in moving toward this expanded view of PHRs. Why? First, clinicians have been taught primarily to value medical data; they will demand proof of value and need education about how to deal with often subjective patient experience. Second, clinicians are already time constrained — we’ve all read about the average 7 minute doctor visit; more information = more information overload.
A final takeaway was the critical need to separate the personal health application from the PHR data platform; for the purposes of this RWJF project, the 9 grantees worked with a common technological platform but built distinct PHR applications to run on the platform. Distinguishing between platform and application lowers barriers to innovation; it enhances opportunities for interoperability and allows for platform components to be reused for multiple applications.
This distinction between application and platform also is a useful way to explain a major difference between Google Health and Microsoft HealthVault. Google Health is both an application and a data platform; Google has provided an integrated PHR through which users can access their information as well as a data repository to store personal health information. HealthVault is solely a platform; Microsoft is engaging 3rd party developers to create many applications, including multiple PHRs that can access the HealthVault data repository.
While attending the event, I had a lot of fun facilitating a panel session including representatives from Google Health, HealthVault, and Dossia. I’ll let you know when conference videos are made available.
This was one of the most innovative and well organized conferences I’ve attended…congratulations and thanks to all!
Related Posts (# comments)
Tags: conference, Dossia, EHR, EHRs/PHRs, Google Health, HealthVault, interoperability, personal health information, platform