Ted Eytan, MD

e-Health. Patient empowerment. Washington, DC.

While at Massachusetts General Hospital last week, as a guest of The Stoeckle Center for Primary Care Improvement, I was invited to meet the team at the Laboratory of Computer Science based at MGH. The Lab of Computer Science produces the OnCall series of clinical web portals, which are a front end to the Computer Stored Ambulatory Record medical record system.

The reason it is a “series” and not “a front end” is because this system actually has brands that are specific to the specialties and care that it supports. Here’s a picture from a computer screen that shows them:

OnCall Brands


Why is this interesting? Because it’s doable - this ambulatory record system communicates using an XML platform, and has been doing so since 1996. XML, as I mentioned in a previous post, is an uber-industry standard for moving data across systems outside of health care, and is now getting traction in health care. Having it as a foundation for an electronic health record system back to 1996 has some advantages, like the one you can see above. Different types of care can access the same data differently.


In my usual LEAN way, I asked if I could see OnCall in action, and so I shadowed Henry Chueh, MD during his clinic day (with each patient being asked for their consent before I entered the room). I found the interface to be very user centric, with lots of modern AJAX-y touches, as one would expect for an EHR that is being continually improved by a team of physicians that practice medicine regularly. Back to the XML though, the happiness is not that the user experience is good, it’s that it can be improved perhaps easier than another system because the data is moved around in standard ways. It’s almost like the team could create a patient version of the same record using a style sheet - which is something of a holy grail in patient access, in my opinion.


OnCall is going to be used as the basis for the Ambulatory Practice of the Future, also being designed at MGH. The idea is that a practice that can continuously improve will do best with an electronic system that can do the same, quickly.


There isn’t yet a patient portal attached to OnCall, but one is being worked on under the leadership of Henry and JeanHee Chung, MD, MS, a practicing internist and member of the LCS team. They showed me an early prototype of a patient front end and system named “ACCORD” (Ambulatory Care Compact to Organize Risk and Decision-making) which takes a personal health record one step farther than I have seen, by connecting patients and physicians to agreements around treatment plans. There’s a short summary of the project here at the AHRQ Web Site. I think this would be an exciting development for an electronic system and I was delighted to meet the parents of the OnCall system and get a glimpse into the future of a personal health record that uses data to model patient-centeredness.


Thanks to MGH and the Lab of Computer Science team for the warm welcome. LCS is sort of legendary in Informatics circles in terms of the vision it brought to medicine around the use of computers, and it was good to see in the flesh.

1 Comment | Add Yours

What I learned about CCR, Part I

This is a bit overdue for me given that I learned what I learned about CCR at the ASTM Workshop in May, 2008, conducted by David Kibbe, MD, MBA, and Steven Waldren, MD. I think what I learned is important for supporting patient-centered HIT, so I’m putting my summary here. A reminder that the beauty of Web 2.0 is that nothing is ever finished - feel free to clarify or correct anything I’ve gotten wrong.

The seminar itself was very enjoyable, nicely paced, and I learned as much from the students (including fellow blogger Vince Kuraitis and Sam Faus from Sujansky and Associates) as from the teachers - that’s always the right combination.

Why was CCR created?

CCR stands for “Continuity of Care Record. (link to official site here) ” I think the “why?” of anything is the most important - knowing where things come from tells us where they’re going…

In 2003, there was a desire to figure out a way to take the “green form,” which health care providers used to transmit a patient’s medical record summary to the nursing home, digital.

(In the clinical arena, the transfer to a nursing home is one of the most delicate times for a patient and their family. Inaccurate or missing information can have an enormous impact when the receiving institution is not staffed to reconcile and adjust therapy the same way a hospital is.)

In their discussions, David told us, they began asking about making this XML-based standard “a record for the patient” that could be used for all kinds of care transitions, not just to the nursing home. And so, CCR was born.

(Comment from me - (a) yet another innovation from those in our profession who care for our geriatric peers (b) CCR is fairly new on the scene, 2003 is recent in Informatics history)

CCR was vetted through ASTM International, which from my understanding, is atypical for this organization, which now has a very small focus on Health Informatics. There are other standards bodies, most notably HL7, that have traditionally working in health information.

What exactly is CCR?

Note: The paragraph below is superceded by the comment attached to this post by David Kibbe, MD, which more accurately explains the content and licensing of CCR. Thanks, David!

CCR is two basic things - a “Schema Definition” that resides an a fairly easy to read spreadsheet. And an implementation guide, which provides the “how to” of every element. Both are licensed under the Apache GNU License. This is not 100% the same as open source - but I think it does mean anyone writing software can use this standard to move data around.

CCR uses eXtensible Markup Language, or XML. XML is very standard in modern Web applications. For example, the piece of software that I am writing this blog post on is going to send my words via XML to my blog, and my blog doesn’t really care what software I used to send it my words from, as long as it uses the right XML code to contain it in. This is important in a standard - it’s connected in a logical way to standards already used by other industries to move data (getting us away from the “health care is different” model).

Is CCR supposed to help with portability and interoperability?

As David explained to us. These are two different things. Portability means you can move the information to another place, via paper, fax, or digitally. Interoperability is the ability of “XHR” software (”X” can mean “P” or “E” for EHR or PHR - get it?) to communicate and exchange data so it can be used for its intended purpose, for example to trend with data like it, or to be used to support population health.

CCR is supposed to help with both, using an approach that is not based on a paper chart - it is concerned with vendor-neutral, human and machine-readable structured data.

Why isn’t CCR based on the concept of a medical chart?

I have worked in large systems that computerize medical charts using state of the art software. This part took me some time to understand. A medical chart is divided into various sections, organized a certain way (depending the doctor/hospital where it’s used unfortunately), and serves various clinical and legal functions. It’s a lot of things to a lot of people.

CCR on the other hand, is more like, “What do I need to know about you (and what do you, the patient need to know about you) for you and I to take care of you right now.” It’s a summary of the most important things, but not necessarily everything. At the same time, it can have multiple observations, like a list of past blood pressures for example. It can be a summary of just one outpatient visit, or of 10 years in a healthcare system. It’s flexible that way. We learned that MinuteClinic, Inc. uses it in the former way, to “summarize” one visit to a practitioner and transmit it as needed by the patient.

Part II coming soon: More of What I Learned about CCR

1 Comment | Add Yours
No Comments yet | Add Yours
No Comments yet | Add Yours

The members of Personal Health Records PHR Work Group Members - CCHIT Certification Commission for Healthcare Information Technology were announced today, click on the link to see the list.

It’s a pretty impressive group, myself excluded :), and I look forward to participating. Because CCHIT handles proprietary information, I won’t be blogging about my volunteer position with this group here.

CCHIT operates its own web site which includes opportunities for public commentary, and it also operates the EHRDecisions Blog, which I subscribe to.

10 Comments | Add Yours
No Comments yet | Add Yours
No Comments yet | Add Yours
No Comments yet | Add Yours

Colleague in patient empowerment Susannah Fox e-mailed me this question and so we thought we’d start one.

Jay Parkinson, MD, linked to a discussion happening on Digg in his blog. E-patients is also hosting an informed discussion on their blog.

Is it cliche to say that this is evolutionary, not revolutionary? I think it’s of benefit to patients and our profession that a dialogue has started around moving health care data in a standardized way to a place where people can aggregate and do things with it to improve their health. A year or two ago, it was hard to think about a standardized extract of a medical record that you could send from an EHR system except in very specialized situations. Now you can do with several partners, Google being the most recently announced option.

I didn’t even think about writing a special post about it, even though I thought, “Cool, this work will support the ideas I am exploring with the California Healthcare Foundation, that patients can be involved and active in their care, across health environments (health system, work, play).” So rather than writing about it, I just incorporated the possibility into the work we’re already doing, which is great.

I think of privacy as a state of being that allows a person to feel comfortable seeking health care regardless of the issue. This is a good place to be, and when that state of being doesn’t exist, people will seek it out, even if it means not seeking needed care, which could be devastating both to patient and health system. At the same time they seek comfort, they also want to build confidence in their ability to manage their health by having as much information their care as possible. In systems where patients have good access and trust, the care is better, and it feels great (and is great) to provide and receive care in that setting. Both things are important, we should not sacrifice one for the other; every patient deserves to achieve their life goals through optimal health.

3 Comments | Add Yours

I learned about this at the CCR workshop. The CCR accomodates elements of this, but CMS has not endorsed it yet as a standard.

AMCP.org - Comments on Standard SIG - The NCPDP was working on the standard for Med Sigs - a little background

No Comments yet | Add Yours
« Previous Entries  
Random header image... Refresh for more!

Recent Comments

Calendar

July 2008
S M T W T F S
« Jun   Aug »
 12345
6789101112
13141516171819
20212223242526
2728293031  

Photographing Now

Reading Now

Doing Now