Physicians

Why Doctors Should Stay Out of the Business of Building EHRs

The original Hipoocratic Oath states:

I will not use the knife, not even on sufferers from stone, but will withdraw in favor of such men as are engaged in this work.

One modern version reads:

I will not be ashamed to say “I know not,” nor will I fail to call in my colleagues when the skills of another are needed for a patient’s recovery.

The idea here is that a doctor needs to recognize when another practitioner has a skill that they do not, and that they must refrain from “practice” when another person has demonstrable expertise in that area of practice.

It is now 2013. It is time for doctors to stop “writing their own EHR” from scratch. They need to bow out of this in favor of people who have developed expertise in the area.

I just found out about another doctor who has decided to write his own EHR, because he has not been able to find one that supports his new direct pay business model adequately. In the distant past I encountered a doctor who believed that his “Microsoft Word Templates” qualified as an EHR system. This is a letter to any doctor who feels like they are comfortable starting from-scratch software development for an EHR in 2013 or later.

You might believe yourself to be an EHR expert.

Are you sure about that? Are you sure that you are not just an EHR expert user?

This difference is not unlike your relationship with your favorite thoracic surgeon. Or for that matter, your relationship with the person who built your car. The fact that you are capable of expertly evaluating and using EHR products does not mean you are qualified to build one. Just like the fact that you are qualified to treat a patient who has recently had heart surgery or to discern when a patient might need heart surgery does not make you qualified to perform that heart surgery. Similarly, the fact that you can drive, or even repair your automobile, does not provide you with the expertise you need to build a car from scratch.

The ethical situation that you are putting yourself in by developing your own EHR is fairly tenuous. Performing heart surgery without being a heart surgeon, building and driving your own car without being an automotive engineer and a doctor coding their own EHR system from scratch all have the same fundamental problem: You might be smart enough to pull it off, but if you don’t you can really mess up another person’s life. Make no mistake, you can kill someone with a shoddy EHR just as easily as by performing medical procedures that you are not qualified for or by driving a car that is not road-safe.

It is not that heart surgeons, automotive engineers and EHR developers are not going to kill people with faulty performance. All experts are fallible. But they will kill far fewer people than you would, performing outside your expertise.

I can understand your feelings of frustration. You likely have totally different goals in mind than the average third-party-payer oriented EHR system has. You are right to be frustrated with the shackles that those systems have placed on you. But you are very wrong to presume that it is ethical for you to do “amateur hour” on your own.

You presume that because you can see the problems with EHR developer performance, that this makes you qualified to build a better EHR. You are utterly and unequivocally wrong about this. Sometimes, EHRs have features that are designed for clinical CYA, basically over-documentation for the sake of unethical defensive medicine. Sometimes EHR systems are designed to be glorified practice management systems, designed mostly to ensure that doctors maximize their paycheck at the expense of patient care. Sometimes EHR design decisions have no rational behind them at all… they are frequently the result of original design whims that are hard to correct in subsequent editions of an EHR product.

But sometimes a feature that frustrates you is precisely what makes that EHR safe for patients. I can promise you that you cannot tell the difference between flaws and features without looking carefully at both the internals of the EHR system and all of the clinical workflows it is exercised in. What you think of as a flaw might be a software crumple zone.

Happily, you get to have your cake and eat it too. There are several Open Source EHR systems that are already meaningful use certified. You can use these Open Source EHR systems for nothing, and for very little money you can even get Meaningful Use credit for using these systems. Given this, you have no excuse to continue to develop an new EHR.

Open Source gives you the right to change what you need to, in order to get the functionality that you want.. and more importantly can connect you with experienced health IT developers, who can serve as a gut check for you as you consider how to implement the features that you need for whatever clinical variation you are interested in implementing.

This is very like the person who orders a “kit car” to build in their garage. They get to -feel- like they are building the car, and indeed they get lots of options normal car owners do not. But in the end, they are able to build a car safely because someone else, someone with specific expertise, has made sure that design of the kit car is fundamentally sound.  You can always shoot yourself in the foot with kit cars and Open Source.. but you have the power you need without being in over your head.

The development of mature EHR systems has been very similar to the development of surgical methods. Primitive EHR systems and primitive surgical procedures were both deadly. In both cases, medical science has already sacrificed thousands of people to the “cause” of learning how to do these things right. In 1850, it would have been entirely appropriate for any doctor to “dabble” with creating their own surgical methods. Even as recently as 2000, it would have been appropriate for you to “dabble” with the creation of your own EHR system. (eMDs was started by a doctor dabbling in 1996. eClinicalWorks was started in a similar fashion in 1999). But those days are over.

A doctor developing a new EHR system from scratch, by themselves, without extensive Health IT programming experience is in over their head. If they continue to develop an EHR, even after being warned of the dangers here, then this is hubris.

Ask yourself: Are you absolutely sure that this action is not a fundamental violation of the oath that you took when you became a doctor?

I want to be clear, I have worked on or around the development of EHR systems for more than a decade, and I would not presume to write a new EHR system without a team of programmers and years of funding. Its not that I think that “a doctor” is not qualified to undertake this task. No single person is.

I wrote a book designed to ensure that novice programmers had basic training in complex Health IT principles. Programmers can be guilty of hubris too, and I consistently advocate for a “clinical pair programming” approach. David Uhlman (my co-author) and I wrote the book because too many people assume that Health IT is easy, and they wonder why things in the industry are so “primitive”. The book is intended to teach clinicians and programmers alike humility when approaching clinical information systems, both as users and as developers. FSM knows that I have been dangerously arrogant regarding clinical information systems, and I have and will make serious mistakes. But there comes a point where making the same mistakes that others have made, and written about, becomes unethical. I think we have reached this point with EHR systems.

Some people took offense that I should link to my own book at the end of this article, so instead I have included some of the reference materials that I use frequently. This is a good sampling of the kind of context that really should be required of any modern Health IT developer.

Begin with Information and Medicine by Marsden S Blois. Then move on to Principles of Health Interoperability HL7 and SNOMED by Tim Benson and The CDA Book by Keith Boone. Finally, you should read about what can go wrong in Health IT by studying EHR generated errors with Clinical Information Systems, Overcoming Adverse Consequences by Dean E Sittig and Joan S. Ash.

These are the books that I refer to when I get stuck on something. I wish I could just hold it all in my head, and in many ways my book is just the cliff notes I need for myself. If you know of other books that should be on the “Health IT required reading list” please leave them in the comments…

Fred Trotter is a healthcare data journalist and author. He is a technical blogger for O’Reilly Radar and is the co-author of the first Health IT O’Reilly book Hacking Healthcare. Fred Trotter is deeply involved in the e-patient movement, the quantified selfmovement, the health 2.0 community. In all of those environments, Trotter has focused on building tools that help empower patients to improve their own health. You can follow him at his personal website, where this post first appeared.

Livongo’s Post Ad Banner 728*90

30
Leave a Reply

23 Comment threads
7 Thread replies
0 Followers
 
Most reacted comment
Hottest comment thread
28 Comment authors
Anne Merrittemail marketingSam@doctoraccess.orgChristopher Loyddavid d Recent comment authors
newest oldest most voted
Anne Merritt
Guest
Anne Merritt

While I have already exhausted this issue as I have way more evidence that suggests that PATIENT CARE HAS TAKEN AN EXTREME SLOPE IN A DOWNWARD SPIRAL OF “DOOM” AS THEY HAVE BECOME INCREASINGLY NEGLECTED DUE TO THE IGNORANCE OF : no consistent E.H.R that has long-term value, (unless they are a monopolizing entity-healthcare system) — that is unable to communicate in the health exchange of information, that requires unrealistic expectations of health practitioner’s to be proficient, no consideration for the generations of patients that refuse to buy into the E.HR., the stress of financial burden and /or penalties threatening… Read more »

email marketing
Guest

What’s Taking place i am new to this, I stumbled upon this I have found It absolutely helpful and it has aided me out loads.
I hope to give a contribution & help different customers like its
aided me. Great job.

Take a look at my web blog … email marketing

Sam@doctoraccess.org
Guest

Let the national market place for ACA be a perfect example of why “seasoned” specialists take care of building and implementing an EHR.

Christopher Loyd
Guest
Christopher Loyd

I’m a bit late to the party, with regards to comments and the timing of this article, so forgive me. I find both the article, and a good portion of the comments more than a little unsettling – furthermore, the outright amount of tension between the IT professionals and healthcare professionals in this article shows the lack of understanding for Health IT. Health IT is still, currently, in it’s infancy. Like most other major changes in individuals lives – this has been a bumpy, albeit stressful transition from that of which we’ve been used to as professionals for so many… Read more »

david d
Guest
david d

Fred: was your account hacked?

J. Jones RN BSN CCRN
Guest
J. Jones RN BSN CCRN

I know I am not a doctor, so my use of the EHR is far different than a dr in a private practice. HOWEVER, I do concur that given the user friendliness of the EHR at my hospital, anyone who is driven mad enough times by it would have the motivation to create a better one. I actually think there is a HUGE need for doctors and nurses and pharmacists (end users/customers) to be trained in programming for EHR’s. Too often it is the “I know best” attitude, instead of collaboration that really messes up patient care and outcomes. For… Read more »

Michael Chen, MD
Guest

Although I’m late to the party, I want to say that I’m dismayed and saddened to hear what Fred has to say, given that he has been such a strong, staunch supporter of open source. As a physician and also a software developer (NOSH ChartingSystem) and a staunch supporter of open source myself, the ethos of open source left the building with this post. Yeah, there are hundreds of EHR’s out there, mostly closed source, only a handful of them open source (mine is one of them), I still believe that even with the MU certification fiasco that has crippled… Read more »

DOctorJay
Guest
DOctorJay

Evernote would function as a better EHR than most of the products out there. Why can’t I search with optical character recognition within my EHR (would help tremendously with all the scanned in labs, imaging reports, etc.)? Why do I have to click a million different boxes to get input? Why can’t I amend the templates myself to fix the errors input by some tech who doesn’t understand medical vocabulary? Why can’t you just leave me a bunch of free text boxes that I can dictate into with Dragon (I promise to include your almighty ICD-9 codes)? Why can’t you… Read more »

Raul
Guest
Raul

This piece is so wrong. How the hell do you know that we physician developers have no idea what we’re doing??

Well, I know, because you have no idea what you are talking about.

sribe
Guest
sribe

Yep, I agree wholeheartedly with the MDs bashing this article. And I’m an IT guy. Yes, most MDs who think they could do it themselves are hugely underestimating the difficulty, but many of them are smart enough to get something working, more or less, eventually. And since “something working, more or less, eventually” describes most of the commercially-available EMRs… Also, the assertion that no single person is capable of developing an EMR is patently false. It is true that no single person could develop an EMR to meet the typical goal of “all specialties all sizes” for commercial sale. But… Read more »

Bernard Pegis, MD
Guest

I have to agree with Alan, Rob & Nick and not the author… Both sides of this are woefully inadequate in understanding the needs of the other side. While EMR-X may be a great piece of software abstractly, if it fails to help a doctor *with the flow that works for him* instead of the arbitrary flow the software has (“because it’s safer for the patient” – saith the software engineer) it is useless at best and likely harmful. Those best suited at designing, designing and writing or even advising EMR creation are physicians. Period. All else is hubris and… Read more »

Cristina_EHRvendor
Guest
Cristina_EHRvendor

As a software vendor in the EHR space, we wholeheartedly agree about the complexity of integration. We hear these same issues and find our customers have experienced similar frustrations. However, the difference comes in the relationship you have and the vendor’s knowledge and experience to get you through the speed bumps and curves you will undoubtedly experience when moving a practice to electronic. You will encounter unexpected issues and these are scalable, the larger the business, the more opportunities there are for issues to develop. So ask the EHR vendors about what kind of feedback their customers are giving about… Read more »

Shirie Leng, MD
Guest

Reverse doctor bashing. I love it. I understand what the writer is trying to say. There is nothing more frustrating than a bunch of amateurs flailing about with something they know nothing about in hopes of getting something better that they still know nothing about. We must ask ourselves where the need to flail comes from. Open-Source is a good place to start, but institutionally most of us doctors don’t get anywhere near the decision-making table where which systems to buy are made. People will always hate a one-size-fits-none system that is imposed upon them. Fred, doctors will fight you… Read more »

alan t falkoff, md, faafp
Guest

Having been involved with emrs since 1990, never having written or developed one, having reviewed hundreds, having owned, used and maintained 3 over the past 23 years, having used 6 different ones in hospitals over the same time frame, I have to say this is the most ridiculous piece I have ever read!
How off target and ludicrous can you get?

MG
Guest
MG

I would agree with the general tenant that most physicians think they could do a lot of other things quite easily. My favorite one is that they could easily have become a quant in a private equity or hedge fund by graduating with a PhD in statistics, physics, or applied math. Maybe but I bet an overwhelmingly majority couldn’t have hacked the math. As for building their own EMR, maybe but it would take a pretty special set of skills, expertise, and more importantly desire. Also a huge opportunity cost there in terms of what kind of time requirement it… Read more »

Noah Webster
Guest
Noah Webster

tenant: a person who occupies land or property rented from a landlord.

tenet: a principle or belief, esp. one of the main principles of a religion or philosophy.

I’m guessing you mean the latter, not the former.

Bobby Gladd
Guest

I always love that one. LOL. Also, people who have great ethical “principals.”