January 19, 2010
EMR Research Isn’t Respected
Written by: JohnSign up to receive all the latest EMR and EHR Updates.
At the same meeting where Google’s CEO, Eric Schmidt, commented about healthcare IT, there was another interesting comment by Eric Lander about the state of researching EMR and healthcare IT. Here’s his comment:
“My sense is that we don’t respect this stuff,” said PCAST co-chair Eric Lander. “We respect the cancer genome, but not checklists. What do we need to do to send a signal to the next generation of researchers that this is a high-class, worthy thing to do? What would it take to move the needle?”
I agree. I’ve done the searching through the journals for well done EMR research and found very little. Not that research is the end all be all, but it can provide insight that can’t be found other ways.
Related posts:
One response to "EMR Research Isn’t Respected"
Leave a Reply
Commenting policy: Some comments run the risk of being deleted. These include comments that are spam or cannot be understood or are rude.
» EMR and EHR Sponsors
- » Recent articles
- Pulse EHR Software Gets $13.5 Million Capital Infusion
- Meaningful Use Rule Clarification by John Halamka
- AMA Weighs in on Meaningful Use
- Number of EHR Certifying Bodies Continues to Increase
- Single Point of Contact for EMR Vendor and Consultants
- HP Launches EHReady for Healthcare IT Market
- Meaningful Use Final Rule Links
- Final Meaningful Use Rules Released Tuesday at 10 AM EDT
- Meaningful Use Rule by July 14th
- Lessons Electronic Health Records Learned from Star Trek
- » Archive Calendar
-
Jobs by SimplyHired
Absolutely the point I try and make every day – thanks, John, for calling this out. Here at Electronic Ink we spend our days helping our clients understand not only how to make software usable but, more importantly, what their customers need to be able to accomplish with that software. Taken from that perspective, the design of an application can be accomplished that intuitively supports user goals rather than simply providing sets of features. Additionally, by implementing such a formal design process, we can uncover latent requirements (those that users don’t realize they have) and provide flexible and creative solutions.
Why is this important, you ask? Because sometimes the best solution is more than an electronic version of the currently used solution. Only a good designer can provide that sort of insight.