ehealth

Defining the PHR – take II

Following on from my April post regarding thoughts about Person Health Records, I've been working with Professor Dipak Kalra to clarify the definitions and purpose of PHRs. This work is intended to be part of a much larger document which describes PHRs and provides examples. It is not an easy task - PHRs are difficult critters to pin down and most definitions are more a description, but here is my next take on trying to do so...

Personal Health Records are by their very nature hard to define and in order to tease out the breadth and depth of PHRs, it may be helpful to consider PHRs and clinical EHRs being positioned at two opposing ends of a spectrum of health records (see diagram). We could attempt to define a PHR as the direct counterpoint to an Electronic Health Record, but in practice the lines of demarcation are most often not clear nor desirable, except when viewed in terms of who has control over the health record and the content within.

While EHRs have traditionally been defined as “logical representations of information regarding or relevant to the health of a subject of care”, they have existed primarily for the purposes of the healthcare provider providing care to an individual. Information from EHRs may be made available to the subject of care or their authorised representative, upon request to the clinician who is acting as a steward of the health information. In some countries this is supported by specific legislation.

PHRs are also “logical representation of information regarding or relevant to the health of a subject of care”, however in the strictest sense these health records are primarily managed and controlled by the individual who is subject of care, or their authorised representative. The individual has rights over the clinical content held within a PHR, including the ability to delegate those rights to others, especially in the case of minors, the elderly or the disabled. The individual, or their authorised representative, is the key stake-holder determining that the content of the PHR is relevant and appropriate. Simplest examples include self-contained mobile phone applications that track a personal diet or exercise history – individual controlled and accessed only by the individual themselves.

However, in between these two strictest views of an EHR and a PHR is a continuum of person-centric health records with varying degrees of control, access and participation by the individual and their healthcare providers. Toward the EHR end of the spectrum, some EHRs provide viewing access or annotation by the individual to some or all of the clinician’s EHR notes. Conversely, at the other end of the continuum, some PHRs enable individuals to allow varying degrees of participation by authorised clinicians to their health information – from simple viewing of data through to write access to part or all of the PHR.

In the middle range of this continuum exist a growing plethora of person-centric health records that operate under collaborative models, combining content from individuals and healthcare providers under agreed terms and conditions depending on the purpose of the health record. Control of the record may be shared, or parts controlled primarily by either the individual or the healthcare provider with specified permissions being granted to the other party.  For example a shared antenatal record may be either primarily a PHR, under auspice of the individual, permitting authorised health care providers to contribute content or directly edit part of all of the record itself, or it may be an extension of an organisations EHR, permitting the individual to view or directly contribute content to some or all of the record. The exact nature of the sharing of responsibilities and participations by each party needs to be specified in the terms and conditions of the health record.

Intent of health information with a PHR may be purely for use by the individual themselves or it may be used to share with healthcare providers and others, such as family members.

Ownership of the PHR can be complicated – requiring differentiation between moral ownership of the health information content and technical/legal stewardship for storing and securing the data. Storage of health information upon a PHR platform that is managed by a third party requires a formal relationship between the two parties so that individuals can assert their rights, as must the third party uphold their responsibilities.

The content scope for a PHR varies according to purpose, and is broader than most conventional EHRs. In the maximal scope a PHR may have a breadth that encompasses health, wellness, development, welfare and concerns; plus a chronological depth which embraces history of past events, actions and services; tracking and monitoring of current health or activities; and goals and plans for the future. Some PHRs will have a very general, summary focus; others may be activity-driven eg a diabetes management record within a Diabetes community portal or an personal fitness and exercise record. An individual may choose to have one single summary PHR or multiple activity driven PHRs, or a combination of both.

Acknowledgement: Prof Dipak Kalra, CHIME, University College London

PHRs: still a powerful grassroots approach to eHealth

In 1999 four clinicians and an ex-CIO gathered around my kitchen table and week by week we hatched a plan for a Personal Health Record (PHR) which we hoped could revolutionise healthcare. At that time a PHR was not at all mainstream. Very few clinicians we spoke to thought it was a good idea at all. Many held a very paternalistic view that patients were not capable to handle their health information, and that a PHR would not ever be trusted as a useful resource (- for some reason a verbal a history was acceptable but a patient entered record of some sort was not)! Patients were also pretty passive and had to be convinced that they could be supported to manage their health information in a similar way that they managed their finances! In January 2000, those last heady days of the dot-com era we started development in earnest, then rode the rollercoaster and navigated the fallout of the dot-com crash. HotHealth was launched in November 2000. My clinical colleagues were still not very enthusiastic about the concept. The business model was not easy. Large companies, health insurers, hospitals, pharmaceutical companies - everyone could see how a PHR would be 'useful', but none would commit. The funding dried up and it/we were acquired by listed company in 2002.

In the US, there were a fair number of PHRs in 2000, maybe even as many as 50. DrKoop.com (now apparently HealthCentral) was the clear leader at the time; WebMD is probably the only significant one remaining. Our annual market research for competitors showed a huge turnover - PHRs were appearing and disappearing at a great rate!

But the evidence was starting to come in and support the concept - Kate Lorig's work at Stanford on supported self-management in arthritis was working well on paper and face-to-face. We applied some of these principles to HotHealth plus health summaries, prevention plans, wellness promotion, quality health information etc - the kinds of features we are used to seeing in PHRs now.

Well, HotHealth still exists and has had some modest success, mostly in the spin off of a PHR for older children and teenagers with insulin dependent diabetes which ran between 2003 and 2005 - Betterdiabetes - but it never blossomed as I had hoped. Was it the timing? Was it the business model? Was Australia too small a market. Yes to all of these, and much more - it was harder than we anticipated.

In 2005 I was asked to write a commentary in Australian Health Review - "The patient’s memory stick may complement electronic health records"(PDF of full text). Re-reading it now, I can't help but be disappointed that not a lot has really changed in terms of integration and data exchange between clinicians and patients. We have made some small progress, but I thought the revolution would have happened by now.

Amusingly I think that my final paragraph in that commentary, written back in September 2005, still stands true.

"A grassroots push by consumers wishing to hold, own and manage their own health information has the potential to make relatively quick, inexpensive and significant changes to the way healthcare is delivered, to support and encourage consumer input to their own health information record, and kick-start electronic health record development in Australia. And eventually when our individual PHRs evolve to amalgamate and integrate with the HealthConnect* implementation, we will all be beneficiaries of an integrated and interoperable health system, meeting the needs of all participants in a timely manner, and most importantly enhancing health outcomes, and minimising risk."

It's just been a longer journey that I first thought!

Reflecting today, I think that those four words in bold - "grassroots push by consumers" - are important. Health care consumers are now better educated and equipped than ever before to decide what it is that they want from eHealth. Let's complement the top-down national program approach with a powerful, bottom-up, consumer-driven kickstart to eHealth!

More than just requesting our data in a readable format, more than collecting a heap of printed pages or folders of pdfs, we should be requesting our data be in a format that we can do something with, data that we can actually re-use. Think of all the little bits of health information that have been created and left behind after each consultation with your family doctor and at each hospital visit. And of course don't forget your dentist and physio, your naturopath who also prescribes for you nor the doctor you saw only once while on holiday in some far off place. Think of what we could do with all that data; if we could only aggregate all of these snippets of information together. The PHR is the most likely place for our fragmented data to come together; the result being a broader, deeper and richer record than could be achieved by any one provider!

I still firmly believe that Personal Health Records have the potential to transform the way we deliver health care. It may take longer than we all anticipate but the PHR is a very powerful grassroots approach to eHealth. Be patient;-)

*HealthConnect was Australia's eHealth program at the time - now totally MIA and no evidence of it exists online!

Waving in eHealth

I’m excited and optimistic about Google Wave. In my mind, its key strength is as a brilliant hybrid medium for complex, small group conversations:

  • allowing tightly focused, tree-like threads, through contextual inline replies;
  • synchronous & asynchronous collaboration, wherever useful or most appropriate; and
  • inclusion of shared resource files.

So, Google Wave in eHealth - how could it be used?

A few thoughts...

1. Health Conversations

  • For private use...

For Patient to Patient or Clinician to Clinician conversations, Wave is a great way for individuals to share thoughts and information on any topic, health included, and no matter what the personal or professional purpose. However if the topic IS health, then there also should be a caveat that the Wave doesn’t contain any private health information. It is not unreasonable to assume that sharing health information in Wave is similar to that of using insecure emails – so just don’t do it!

  • For use in healthcare provision...

As a vehicle for a dialogue between Clinician and Patient, Wave is great but it is important to keep in mind that this is not just your average chat, but another format of an online consultation, and all the complications that this brings. If Wave is embedded in an appropriately secure environment, such as an existing EHR/PHR platform with appropriate privacy provisions/authorizations etc. and where versioning of the Wave could be recorded to support the medico-legal record, then Wave could be a great tool in eHealth.  Remember that this is a preview and it is a new technology, so there will be hiccups as we all learn to use Wave - there is a significant overhead to using Wave effectively.

One of my first thoughts re the potential clinical use of Wave was how it could have enhanced a Personal Health Record (PHR) that was developed for use by older children and teenagers with Insulin Dependent Diabetes at Royal Children’s Hospital, Melbourne – BetterDiabetes. There is a component within this PHR where the teens can request online assistance and advice from their Diabetes Nurse Educators (DNEs) for management of their diabetes. Armed with appropriate authorization and access permissions, the DNEs can view selected parts of the BetterDiabetes record, including glucose measurements uploaded only minutes beforehand, making informed and making real-time responses back to the teens regarding proposed changes to their care. In the online version of BetterDiabetes the secure messages flowing back and forth are similar to email, but embedded in the PHR – asynchronous, fragmented and clunky. If this was able to be transcended by a Wave-like tool for communication it could be a very useful vehicle for collaborative healthcare provision. The provision of timely information flow in both directions, and including addition of external files to the ‘Wave’ could be extremely valuable.

2. EHRs & EMRs

Wave is NOT appropriate for an EHR/EMR platform. Formal health records should be based on standards such as ISO 18308 – ‘Requirements for an Electronic Health Record Reference Architecture’ and ISO/DTR 20514 – ‘Electronic Health Record Definition, Scope and Context’. Now Wave may be very useful as an interface for communications within that EHR framework, form or structure, but it is definitely not the basis for "…a set of clinical and technical requirements for a record architecture that supports using, sharing, and exchanging electronic health records across different health sectors, different countries, and different models of healthcare delivery." Of some concern, there are some public Waves that are promoting Google Wave as the newest medium for EMRs. One public Wave as an example is: Electronic Medical Records (EMR) and Medical Information Systems: Is Wave the future of electronic medical records? which includes an EMR example.

By all means let's embed the innovative Wave interface for use within a formal EHR/EMR but we need to be careful if we are expecting more from it.

3. Clinical Decision Support

Phil Baumann’s ‘A Clinical Infusion of Google Wave’ blog, featuring Clinybot, is a fascinating, futuristic view of Clinical Decision Support provided for clinicians. Phil states that he assumes all privacy and security aspects are OK when proposing Clinybot - agreed. However, the missing ingredient in Phil’s proposal is not unique to Clinybot but the reason why we have so little Clinical Decision Support in practice. In order for Clinybot to function as described it would have to have a clear semantic handle on the data structure underlying it. Clinical Decision Support can be and is developed on a per EHR/EMR basis, however standardization of clinical content would enable universal applicability of Clinybot across all EHRs and EMRs. The combination of Clinybot and standardised content could be a very powerful potential partnership.

_____

I’m a pragmatist; definitely not a futurist. I’ve seen some predictions and anticipated uses for Wave that I think are very optimistic, maybe even a little far-fetched. Perhaps these things might happen... probably not.

And of course there are issues and drawbacks to Wave. Tech Crunch's Why Google Wave Sucks, And Why You Will Use It Anyway is a pretty good heads up to the reality of Wave at present.

For the moment I'm more than happy to explore how the benefits of the complex, small group conversations can be leveraged in healthcare, and particularly my clinical modeling work with openEHR. I will keep an open mind to see how Waving in health develops.

Riding the Google Wave

This morning I posted two tweets: "I'm having some great 'robust' discussions on #GoogleWave. I'm now able to finish @ianmcnicoll's sentences for him... in person & online;-)"

and

"I have a love/hate relationship with #GoogleWave. Getting sick of the "Everything's shiny, Cap'n." message, when clearly everything is NOT".

These two statements posted about an hour apart reflect some of my journey into the world of Google Wave.

My day-to-day work is all about collaboration - relying heavily on Skype and GoToMeeting as online tools to communicate with colleagues and clients distributed around Australia, and overseas; and working with groups of clinicians who are using an online application, the openEHR Clinical Knowledge Manager (CKM) for designing, reviewing and agreeing computable clinical content definitions, known as archetypes, for use in Electronic Health Records.

CKM is a relatively new and unique online application. Powered only by volunteers, it is harnessing the "collective intelligence" of clinicians and informaticians from all over the world to create open source archetypes, which underpin the European and international EHR standard, ISO13606.  Since its April launch, CKM is gaining momentum and has attracted 388 registered users from 49 countries, with 130 individuals actively involved in reviewing and agreeing the current 200+ archetypes - some modest success methinks.

The biggest challenge for me this year has been exploring how to productively engage with these busy clinicians and informaticians who are volunteering their time and expertise.  As a result, it was only early this year that I opened a Facebook account (after swearing I would never do it), and only this week I passed my 1000 tweet mark!  Learning to engage with these social networking tools and communities has certainly given me enormous insight re how we might be able to take CKM forward.

The core CKM team comprises Ian McNicoll (@ianmcnicoll) in Glasgow, Sebastian Garde (@gardes) in Dusseldorf and myself in Melbourne and we meet formally using Skype and GoToMeeting twice a week, which is not always the easiest way to collaborate.  One of the next challenges for CKM  is to nurture the design and initial creation of the archetypes collaboratively - effectively a sandpit or archetype 'nursery'.  Our main question is how to provide an online environment where interested international clinicians could share their time and resources effectively... and then we heard that Google Wave was coming!

Receiving that invitation was very exciting.  This was immediately followed by the let-down phase because, of course, you have to wave with someone!  And then the dilemma of "What to do with it?" I found a number of public waves where there were multitudes of people joining and then... well, nothing.  No-one seemed to have a clue what to do with it!  And the few Waves that were very active seemed to become quite chaotic very quickly, resulting in confusion rather than collaboration.

Once Ian, Sebastian and I all had our Wave accounts, we had an opportunity to play - sending asynchronous messages, using the Piratify and Flippy bots to do silly things to the blips and co-writing in real-time - hence my ability to finish off Ian's sentences for him;-).  More recently, we started to find some real uses for Wave which our usual email, Skype and GoToMeeting couldn't do.  We created a number of separate Waves, each related to a particular CKM requirement that we were trying to thrash out.  In fact, only this morning we managed to come to an agreement on a particularly curly one - an issue that we hadn't been able to resolve through a number of verbal discussions.  The ability to focus on one comment (blip) to get a common understanding has been very useful.

And then there was a recent twitter discussion that I had with @psweetman and @JFahrni about allergies - 3 strangers from UK, US & Australia using Twitter to try to come to a common understanding!  Jerry took the initial tweets (-what is the collective noun for a group of tweets?) and combined them in his blog.  While we could now see them all together, instead of fragmented 140 character snippets, it was still difficult to engage with each other.  So I took the blog and 'Waved' it - created a private Wave in which all 3 of us could participate.  The discussion that ensued was much more effective, building on previous comments and thrashing out specific points. It worked pretty well, including some bonus tips on where to visit next time I go to Las Vegas!

It is this collaborative aspect of Google Wave I'm beginning to love - it is really quite compelling.  Other tools, even used in combination don't cut it. Yet the down side is that Wave is still pretty clunky and I feel that I have seen more than my fair share of the "Everything's Shiny Cap'n" messages as the Wave crashes - hence the frustration evident in my second tweet.

The reality is that you just can't collaborate like this in other media.  Google Wave has enormous potential as it is refined and is extended. I look forward to exploring if and how we can incorporate Wave into our archetype development, especially now with the opportunity to federate Wave servers.  Perhaps it will work, perhaps not - but I have a glass half full kind of view at present.  Will keep you posted...