Joseph Kvedar, M.D. at the Center for Connected Health wrote recently about embedding the basic tools of persuasion into automated interchanges for better health. Messages that take advantage of reciprocation, consistency with personal commitments, expert authority, access to scarce resources, liking the source, and social norming are more likely to be persuasive. Marketers and sales people have long known this. I also agree with him that increased demand for health care as will require some sort of efficiency gains to maintain any semblance of access and equity.
In fact, the gains had by engaging patients in their own care, combined with the efficiencies of automation, are the "secret sauce" behind the success of the Vermedx Diabetes Information System in reducing the need for hospital and Emergency Room care as well as in reducing total costs of care.
His column got me thinking about our own automated messages within the Vermedx system. The letters to patients clearly take advantage of personal commitments and expert authority, but they could make better use of social norming and access to scarce resources. However, we take advantage or another technique that wasn't mentioned: specificity. Vermedx messages include information that is timely, specific, and actionable. Rather than say "You ought to get blood tests regularly," Vermedx tells the patient exactly when the test was due and what to do about it now.
We're going to be working on better ways to incorporate all the positive aspects of the Psychology of Persuasion (or Behavioral Economics, if you prefer) to make even greater gains in health outcomes.
Wednesday, February 23, 2011
Monday, February 14, 2011
How big a chunk of information do we want to exchange?
John Halamka and Wes Rishel have a very interesting approach to the recent debates on just what it is we might be exchanging in Health Information Exchanges. The problem arises from a tension among the need to care for the individual patient in front of you right now, to put that patient's care in the context of their history over time, and to take a broader view of a population of patients.
The provider with an individual case in the here and now traditionally generates a progress note - a document with whatever he or she thinks is required for the purposes of care. Much of professional education is transmitting the law and lore of what must/may/mustn't go into these documents and how to organize them for their various audiences. In general, they are free text, minimally organized with perhaps a few headings (Chief Complaint, Past Medical History, Assessment, etc.) and highly variable both across and within practitioners. (Some ten years ago, when Medicare mandated the presence of a Review of Systems for most office and hospital visits, the push-back from providers was huge and some actually left the profession rather than comply with this minimal nod towards standardization.)
Caring for patients in context requires the assembly of data across time and space and is the first place that electronic health records really shine. Knowing that the patient has an abnormal cardiogram now is valuable. Knowing that it is unchanged from one taken a year ago by another physician is gold. Sharing documents across settings and providers accomplishes much of this, although it can certainly be improved upon with a little more granular organization.
At the population level, however, unstructured documents are not all that useful. Searching for the incidence of diabetic foot examination in our institution required natural language processing of many thousands of documents and failed to produce a reliable estimate [Kost, Chen, Littenberg et al. AMIA 2009]. Rather, we need standardized components of documents that can be extracted, transmitted, understood both as stand-alone entities and in the context they arose from, and analyzed for population as well as individual purposes.
Clinical laboratory data have long had these characteristics. A more-or-less complete documentation of a clinical chemistry test will consist of patient identifiers, specimen source (blood, urine, etc.), date and time of acquisition, analytic method, result, and units. However, even these simple concepts are represented by a bewildering array of formats and definitions. To make matters worse, clinical labs routinely change their analytic methods, units, test names and any of these details, sometimes without even warning the users! A huge amount of effort goes into maintaining the clinical laboratory interfaces at Vermedx to ensure that these data continue to be useful over time.
More complex and less structured data such as pathology reports, operative notes, and discharge summaries are going to require a very large amount of work to make them transmissible and useful at this level. The first steps seem to be to agree upon what the smaller, irreducible units of information should be. This will undoubtedly be the battlefield of yet another IS standards war, but the outcome will have very big implications for how, and even whether, we can exchange health information into the future.
The provider with an individual case in the here and now traditionally generates a progress note - a document with whatever he or she thinks is required for the purposes of care. Much of professional education is transmitting the law and lore of what must/may/mustn't go into these documents and how to organize them for their various audiences. In general, they are free text, minimally organized with perhaps a few headings (Chief Complaint, Past Medical History, Assessment, etc.) and highly variable both across and within practitioners. (Some ten years ago, when Medicare mandated the presence of a Review of Systems for most office and hospital visits, the push-back from providers was huge and some actually left the profession rather than comply with this minimal nod towards standardization.)
Caring for patients in context requires the assembly of data across time and space and is the first place that electronic health records really shine. Knowing that the patient has an abnormal cardiogram now is valuable. Knowing that it is unchanged from one taken a year ago by another physician is gold. Sharing documents across settings and providers accomplishes much of this, although it can certainly be improved upon with a little more granular organization.
At the population level, however, unstructured documents are not all that useful. Searching for the incidence of diabetic foot examination in our institution required natural language processing of many thousands of documents and failed to produce a reliable estimate [Kost, Chen, Littenberg et al. AMIA 2009]. Rather, we need standardized components of documents that can be extracted, transmitted, understood both as stand-alone entities and in the context they arose from, and analyzed for population as well as individual purposes.
Clinical laboratory data have long had these characteristics. A more-or-less complete documentation of a clinical chemistry test will consist of patient identifiers, specimen source (blood, urine, etc.), date and time of acquisition, analytic method, result, and units. However, even these simple concepts are represented by a bewildering array of formats and definitions. To make matters worse, clinical labs routinely change their analytic methods, units, test names and any of these details, sometimes without even warning the users! A huge amount of effort goes into maintaining the clinical laboratory interfaces at Vermedx to ensure that these data continue to be useful over time.
More complex and less structured data such as pathology reports, operative notes, and discharge summaries are going to require a very large amount of work to make them transmissible and useful at this level. The first steps seem to be to agree upon what the smaller, irreducible units of information should be. This will undoubtedly be the battlefield of yet another IS standards war, but the outcome will have very big implications for how, and even whether, we can exchange health information into the future.
Subscribe to:
Posts (Atom)