Free EMR Newsletter Want to receive the latest news on EMR, Meaningful Use, ARRA and Healthcare IT sent straight to your email? Join thousands of healthcare pros who subscribe to EMR and EHR for FREE!

Treating a Healthy Patient

Posted on November 21, 2014 I Written By

John Lynn is the Founder of the HealthcareScene.com blog network which currently consists of 15 blogs containing almost 6000 articles with John having written over 3000 of the articles himself. These EMR and Healthcare IT related articles have been viewed over 13 million times. John also manages Healthcare IT Central and Healthcare IT Today, the leading career Health IT job board and blog. John is co-founder of InfluentialNetworks.com and Physia.com. John is highly involved in social media, and in addition to his blogs can also be found on Twitter: @techguy and @ehrandhit and LinkedIn.

I first coined the concept of what I call treating a healthy patient back in 2011. I’ve always loved the concept of a doctor actually treating someone who thinks and feels completely healthy. The challenge is that this type of relationship is very different than what we have in our current health system today.

While our current model is very different, I’m hearing more and more things that get me back to healthcare treating an otherwise healthy patient. Although, someone recently pointed out to me that we’re not really treating a healthy patient, because we’re all sick. We just each have different degrees of sickness. It’s a fine point, but I still argue we’re “healthy” because we feel “healthy.”

This analysis points out one layer of change that I see happening in healthcare. This change is being able to detect and predict sickness. Yes, that still means a doctor is treating a sickness. However, I see a wave of new sensors, genetics, and other technology that’s going to absolutely change what we define as “sick.”

This is a massive change and one that I think is very good. I recently read an article by Joseph Kvedar which commented that we’re very likely to seek medical help when we break our arm, because the pain is a powerful motivating factor to get some help. Can this new wave of sensors and technology help us know the “pain” our bodies are suffering through and thus inspire us to seek medical attention? I think they will do just that.

The problem is that our current health system isn’t ready to receive a patient like this. Doctors are going to have to continue to evolve in what they consider a “disease” and the treatment they provide. Plus, we’ll likely have to include many other professionals in the treatment of patients. Do we really want our highly paid doctors training on exercise and nutrition when they’ve had almost no training in medical school on the subjects? Of course, not. We want the dietitian doing this. We’ll need to go towards a more team based approach to care.

I’ve regularly said, “Treating a healthy patient is more akin to social work than it is medicine.” Our health system is going to have to take this into consideration and change accordingly.

Treating a healthy patient won’t solve all our healthcare problems. In fact, I’ve wondered if in some ways treating a healthy patient isn’t just shifting the costs as opposed to lowering the costs. Regardless of the cost impact, this is where I see healthcare heading. Yes, we’ll still need many doctors to do important procedures. Just because you detect possible heart issues doesn’t mean that patient won’t eventually need a heart bypass surgery some day. In fact, a whole new set of medical procedures will likely be created that treat possible heart issues before they become straight up heart issues.

What other ways do you see the system moving towards or away from “treating healthy patients”?

Ebola and EHR Workflow

Posted on November 20, 2014 I Written By

John Lynn is the Founder of the HealthcareScene.com blog network which currently consists of 15 blogs containing almost 6000 articles with John having written over 3000 of the articles himself. These EMR and Healthcare IT related articles have been viewed over 13 million times. John also manages Healthcare IT Central and Healthcare IT Today, the leading career Health IT job board and blog. John is co-founder of InfluentialNetworks.com and Physia.com. John is highly involved in social media, and in addition to his blogs can also be found on Twitter: @techguy and @ehrandhit and LinkedIn.

Earlier this month, the EHR Workflow fanatic addict expert, Charles Webster, MD, put together a webinar on EHR workflow (imagine that). However, he decided to piggyback the Ebola headline and talk about EHR workflow and a bit about how it applied to the Ebola incident. I love the marketing behind it.

EHR workflow is a topic of interest to me and so this summer I had Charles Webster, MD do an EHR workflow series over on EMR and HIPAA. Turns out, he covers a number of the same EHR workflow topics in the webinar embedded below:
-What it workflow?
-What is workflow technology?
-What is a workflow engine?
-What is a workflow editor?
-What is workflow visibility?

If you have an interest in EHR workflow, here’s Chuck’s webinar:

EHR Requires You to Reconsider Your Workflow

Posted on November 19, 2014 I Written By

John Lynn is the Founder of the HealthcareScene.com blog network which currently consists of 15 blogs containing almost 6000 articles with John having written over 3000 of the articles himself. These EMR and Healthcare IT related articles have been viewed over 13 million times. John also manages Healthcare IT Central and Healthcare IT Today, the leading career Health IT job board and blog. John is co-founder of InfluentialNetworks.com and Physia.com. John is highly involved in social media, and in addition to his blogs can also be found on Twitter: @techguy and @ehrandhit and LinkedIn.

Despite many EHR vendors best efforts to tell you otherwise, an EHR requires every organization to reconsider their workflow. Sure, many of them can be customized to match your unique clinical needs, but the reality is that implementing an EHR requires change. All of us resist change to different degrees, but I have yet to see an EHR implementation that didn’t require change.

What many people don’t like to admit is that sometimes change can be great. As humans, we seem to focus too much on the down side to change and have a hard time recognizing when things are better too. A change in workflow in your office thanks to an EHR might be the best thing that can happen to you and your organization.

One problem I’ve seen with many EHRs is that they do a one off EHR implementation and then stop there. While the EHR implementation is an important one time event, a quality EHR implementation requires you to reconsider your workflow and how you use your EHR on an ongoing basis. Sometimes this means implementing new features that came through an upgrade to an EHR. Other times, your organization is just in a new place where it’s ready to accept a change that it wasn’t ready to accept before. This ongoing evaluation of your current EHR processes and workflow will provide an opportunity for your organization to see what they can do better. We’re all so busy, it’s amazing how valuable sitting down and talking about improvement can be.

I recently was talking with someone who’d been the EHR expert for her organization. However, her organization had just decided to switch EHR software vendors. Before the switch, she was regularly visited by her colleagues to ask her questions about the EHR software. With the new EHR, she wasn’t getting those calls anymore (might say something good about the new EHR or bad about the old EHR). She then confided in me that she was a little concerned about what this would mean for her career. She’d kind of moved up in the organization on the back of her EHR expertise and now she was afraid she wouldn’t be needed in that capacity.

While this was a somewhat unique position, I assured her that there would still be plenty of need for her, but that she’d have to approach it in a little different manner. Instead of being the EHR configuration guru, she should becoming the EHR optimization guru. This would mean that instead of fighting fires, her new task would be to understand the various EHR updates that came out and then communicate how those updates were going to impact the organization.

Last night I had dinner with an EHR vendor who told me that they thought that users generally only used about 50% of the features of their EHR. That other 50% of EHR features presents an opportunity for every organization to get more value out of their EHR software. Whether you tap into these and newly added EHR features through regular EHR workflow assessments, an in house EHR expert who’s constantly evaluating things, or hiring an outside EHR consultant, every organization needs to find a way to regularly evaluate and optimize their EHR workflow.

Open Source Electronic Health Records: Will They Support Clinical Data Needs of the Future? (Part 2 of 2)

Posted on November 18, 2014 I Written By

Andy Oram is an editor at O'Reilly Media, a highly respected book publisher and technology information provider. An employee of the company since 1992, Andy currently specializes in open source, software engineering, and health IT, but his editorial output has ranged from a legal guide covering intellectual property to a graphic novel about teenage hackers. His articles have appeared often on EMR & EHR and other blogs in the health IT space. Andy also writes often for O'Reilly's Radar site (http://radar.oreilly.com/) and other publications on policy issues related to the Internet and on trends affecting technical innovation and its effects on society. Print publications where his work has appeared include The Economist, Communications of the ACM, Copyright World, the Journal of Information Technology & Politics, Vanguardia Dossier, and Internet Law and Business. Conferences where he has presented talks include O'Reilly's Open Source Convention, FISL (Brazil), FOSDEM, and DebConf.

The first part of this article provided a view of the current data needs in health care and asked whether open source electronic health records could solve those needs. I’ll pick up here with a look at how some open source products deal with the two main requirements I identified: interoperability and analytics.

Interoperability, in health care as in other areas of software, is supported better by open source products than by proprietary ones. The problem with interoperability is that it takes two to tango, and as long as standards remain in a fuzzy state, no one can promise in isolation to be interoperable.

The established standard for exchanging data is the C-CDA, but a careful examination of real-life C-CDA documents showed numerous incompatibilities, some left open by the ambiguous definition of the standard and others introduced by flawed implementations. Blue Button, invented by the Department of Veterans Affairs, is a simpler standard with much promise, but is also imperfectly specified.

Deanne Clark, vxVistA Program Manager at DSS, Inc., told me that VistA supports the C-CDA. The open source Mirth HIE software, which I have covered before, is used by vxVistA, OpenVista (the MedSphere VistA offering), and Tolven. Proprietary health exchange products are also used by many VistA customers.

Things may get better if vendors adopt an emerging HL7 standard called FHIR, as I suggested in an earlier article, which may also enable the incorporation of patient-generated data into EHRs. OpenMRS is one open source EHR that has started work on FHIR support.

Tolven illustrates how open source enables interoperability. According to lead developer Tom Jones, Tolven was always designed around care coordination, which is not the focus of proprietary EHRs. He sees no distinction between electronic health records and health information exchange (HIE), which most of the health IT field views as separate functions and products.

From its very start in 2006, Tolven was designed around helping to form a caring community. This proved useful four years later with the release of Meaningful Use requirements, which featured interoperability. APIs allow the easy development of third-party applications. Tovlen was also designed with the rights of the patient to control information flow in mind, although not all implementations respect this decision by putting data directly in the hands of the patient.

In addition to formats that other EHRs can recognize, data exchange is necessary for interoperability. One solution is an API such as FHIR. Another is a protocol for sending and receiving documents. Direct is the leading standard, and has been embraced by open source projects such as OpenEMR.

The second requirement I looked at, support for analytics, is best met by opening a platform to third parties. This assumes interoperability. To combine analytics from different organizations, a program must be able to access data through application programming interfaces (APIs). The open API is the natural complement of open source, handing power over data to outsiders who write programs accessing that data. (Normal access precautions can still be preserved through security keys.)

VistA appears to be the EHR with the most support for analytics, at least in the open source space. Edmund Billings, MD, CMO of MedSphere, pointed out that VistA’s internal interfaces (known as remote procedure calls, a slightly old-fashioned but common computer term for distributed programming) are totally exposed to other developers because the code is open source. VistA’s remote procedure calls are the basis for numerous current projects to create APIs for various languages. Some are RESTful, which supports the most popular current form of distributed programming, while others support older standards widely known as service-oriented architectures (SOA).

An example of the innovation provided by this software evolution is the mobile apps being built by Agilex on VistA. Seong K. Mun, President and CEO of OSEHRA, says that it now supports hundreds of mobile apps.

MedSphere builds commercial applications that plug into its version of Vista. These include multidisciplinary treatment planning tools, flow sheets, and mobile rounding tools so doctor can access information on the floor. MedSphere is also working with analytic groups to access both structured and unstructured information from the EHR.

DSS also adds value to VistA. Clark said that VistA’s native tools are useful for basic statistics, such as how many progress notes have not been signed in a timely fashion. An SQL interface has been in VistA for a long time, DSS’s enhancements include a graphical interface, a hook for Jaspersoft, which is an open source business intelligence tool, and a real-time search tool that spiders through text data throughout all elements of a patient’s chart and brings to the surface conditions that might otherwise be overlooked.

MedSphere and DSS also joined the historical OSEHRA effort to unify the code base across all VistA offerings, from both Veterans Affairs and commercial vendors. MedSphere has added major contributions to Fileman, a central part of VistA. DSS has contributed all its VistA changes to OSEHRA, including the search tool mentioned earlier.

OpenMRS contributor Suranga Kasthurirathne told me that an OpenMRS module exposes its data to DHIS 2, an open source analytics tool supporting visualizations and other powerful features.

I would suggest to the developers of open source health tools that they increase their emphasis on the information tools that industry observers predict are going to be central to healthcare. An open architecture can make it easy to solicit community contributions, and the advances made in these areas can be selling points along with the low cost and easy customizability of the software.

A Little Digital Health Conference (#DHC14) Twitter Roundup

Posted on November 17, 2014 I Written By

John Lynn is the Founder of the HealthcareScene.com blog network which currently consists of 15 blogs containing almost 6000 articles with John having written over 3000 of the articles himself. These EMR and Healthcare IT related articles have been viewed over 13 million times. John also manages Healthcare IT Central and Healthcare IT Today, the leading career Health IT job board and blog. John is co-founder of InfluentialNetworks.com and Physia.com. John is highly involved in social media, and in addition to his blogs can also be found on Twitter: @techguy and @ehrandhit and LinkedIn.

I’m at the Digital Health Conference in NYC and the Twitter stream has been going strong (search #dhc14 on Twitter to see what I mean). Sometimes I forget how much more satisfying a conference is when there’s an active Twitter stream. It enhances a conference for me in so many ways. I thought it would be fun to point out a few of the tweets that struck me today (and there were a lot to choose from).


I do think New York has made a lot of progress with their HIE. Pretty amazing that they got $30 million of state funding for it. Do you know of other states that are making good progress on their state HIE?


Topol’s comment about cigarettes is interesting. I had to throw in the CVS reference. Right now it doesn’t seem that crazy, but I wonder if 10 years from now it will be just as crazy as Cleveland Clinic giving out cigarette pack holders.


I love imagery and this is great imagery that could inspire a lot of people. What I don’t think many tech people realize is that they’re going to need to work collaboratively with scientists, chemists and doctors to do surveillance on the blood stream. Talk about an area that needs multidisciplinary efforts.


The common error that we compare the new way against perfection as opposed to comparing the new way against the alternative (or the previous model). I’ve been seeing this problem come up over and over in healthcare IT.

Mobile EHR Use

Posted on November 14, 2014 I Written By

John Lynn is the Founder of the HealthcareScene.com blog network which currently consists of 15 blogs containing almost 6000 articles with John having written over 3000 of the articles himself. These EMR and Healthcare IT related articles have been viewed over 13 million times. John also manages Healthcare IT Central and Healthcare IT Today, the leading career Health IT job board and blog. John is co-founder of InfluentialNetworks.com and Physia.com. John is highly involved in social media, and in addition to his blogs can also be found on Twitter: @techguy and @ehrandhit and LinkedIn.

One of the most fascinating sessions I attended recently was by Mihai Fonoage talking about the “Future of Mobile” at EMA Nation (Modernizing Medicine’s EHR user conference where I was keynote). At the start of the presentation, Mihai provided a bunch of really interesting data points about the EMA EHR use on mobiles:

  • 3,500,000 Screens Viewed Daily
  • 50,000 New Visits Each Day
  • 35,000 Photos Taken Daily
  • 12,000 New Consents Each Day
  • 8,000 Rx Prescribed Daily

The most shocking number there is the 35,000 photos taken daily. That’s a lot of photos being stored in the EHR. It is worth noting that Modernizing Medicine has a huge footprint in dermatology where photos are very common and useful. Even so, that’s a lot of photos being taken and inputted into an EHR.

The other stats are nearly as astounding when you think that Modernizing Medicine is only in a small set of specialities. 3.5 million screens (similar to pageviews on a website) viewed daily is a lot of mobile EHR use. In fact, I asked Modernizing Medicine what percentage of their users used their desktop client and what percentage used their iPad interface. Modernizing Medicine estimated that 80% of their EHR use is on iPads. This is a hard number to verify, but I can’t tell you the number of people at EMA Nation I saw pull out their iPads and log into their EMA EHR during the user conference. You could tell that the EMA iPad app was their native screen.

I still remember when I first saw the ClearPractice iPad EHR called Nimble in 2010. It was the first time I’d seen someone really make a deep effort to do an EHR on the iPad. DrChrono has always made a big iPad EHR effort as well. I’d love to see how their iPad EHR use compares to the Modernizing Medicine EMA EHR numbers above. Can any other EHR vendor get even close to 80% EHR use on an iPad application or any of the numbers above?

I’d love to hear what you’re seeing and experiencing with EHR iPad and other mobile EHR use. Is Modernizing Medicine leading the pack here or are their other EHR competitors that are seeing similar adoption patterns with their mobile EHR product lines?

Full Disclosure: Modernizing Medicine is an advertiser on this site.

Generation Who Doesn’t Know Paper Chart World – EHR Natives

Posted on November 13, 2014 I Written By

John Lynn is the Founder of the HealthcareScene.com blog network which currently consists of 15 blogs containing almost 6000 articles with John having written over 3000 of the articles himself. These EMR and Healthcare IT related articles have been viewed over 13 million times. John also manages Healthcare IT Central and Healthcare IT Today, the leading career Health IT job board and blog. John is co-founder of InfluentialNetworks.com and Physia.com. John is highly involved in social media, and in addition to his blogs can also be found on Twitter: @techguy and @ehrandhit and LinkedIn.

I loved this insight from a doctor at EMA Nation, Modernizing Medicine’s EHR user conference. When making the comment, he was talking about how many MAs in his office don’t know how to keep the clinic going in a non-EHR world (ie. the EHR is down). Obviously, that’s an example of where dependence on EHR goes too far. However, I’ve found that a great leader in a practice can easily quell and comfort these MAs (and other clinical staff) when the EHR is down or otherwise unavailable. It’s never a fun experience, but it can be managed.

While dependence on EHR has its challenges, it also illustrates where the industry is headed. Very quickly not just the MAs, but the RNs, doctors and all of your staff will be EHR natives. What’s an EHR native? It’s someone who has only practiced medicine or worked in a clinic where an EHR was present.

The number of EHR natives is still rather small, but it’s starting to grow very quickly. Soon, we won’t even be having a discussion of going back to paper charts, because a large majority of users won’t even know what it was like to practice on a paper chart. In fact, they’ll likely not even understand how someone could practice medicine on a paper chart.

This is a dramatic cultural shift that is happening right before our eyes. However, the shift is slow and gradual, so many people don’t even realize that it’s happening. While it currently is important to talk about EHR acceptance, this will be gone forever with EHR natives. Many of the paper chart culture will just disappear from healthcare.

I personally look forward to this day. That’s not to say that many of the paper chart natives can’t learn EHR as well. They can and do. Although, I know the cost of learning something new and it’s high. Trust me. I just added snapchat to my cell phone. All I longed for was to go back to SMS, Facebook, and Twitter. It’s definitely hard to teach an old dog new tricks. It’s possible, but possible doesn’t mean it’s easy.

Darth Vader Diagnosis

Posted on November 12, 2014 I Written By

John Lynn is the Founder of the HealthcareScene.com blog network which currently consists of 15 blogs containing almost 6000 articles with John having written over 3000 of the articles himself. These EMR and Healthcare IT related articles have been viewed over 13 million times. John also manages Healthcare IT Central and Healthcare IT Today, the leading career Health IT job board and blog. John is co-founder of InfluentialNetworks.com and Physia.com. John is highly involved in social media, and in addition to his blogs can also be found on Twitter: @techguy and @ehrandhit and LinkedIn.

The creativity of humans will never cease to amaze me. Here’s a good example from a tweet from the Exponential Medicine conference:

I think I’ve seen ZDoggMD reference some of the clinical issues of Darth Vader before as well. I’m honestly not sure what value this has to your work, but it gave me a good laugh, so I thought you might enjoy a laugh too.

Healthcare Unbound Conference in San Diego

Posted on November 11, 2014 I Written By

John Lynn is the Founder of the HealthcareScene.com blog network which currently consists of 15 blogs containing almost 6000 articles with John having written over 3000 of the articles himself. These EMR and Healthcare IT related articles have been viewed over 13 million times. John also manages Healthcare IT Central and Healthcare IT Today, the leading career Health IT job board and blog. John is co-founder of InfluentialNetworks.com and Physia.com. John is highly involved in social media, and in addition to his blogs can also be found on Twitter: @techguy and @ehrandhit and LinkedIn.

This December in beautiful San Diego, CA (seriously, who wouldn’t want to be in San Diego in December?), they’re holding the 11th Healthcare Unbound conference. It’s impressive for a conference to reach a second year, let alone an 11th year.

Here’s a summary of the conference and what you can expect to find if you attend:

In 2002, Forrester Research coined the term “Healthcare Unbound” to encompass the trends toward self-care, mobile care, and home care. More specifically, Forrester describes Healthcare Unbound as “technology in, on and around the body that frees care from formal institutions.”

The Healthcare Unbound Conference will focus on technology-enabled consumer engagement and behavior change. Technologies to be discussed include wearables, mHealth, remote monitoring, eHealth and social media.

Moving beyond just a “cool technology” focus, this event will offer practical approaches for healthcare stakeholders and digital health companies. The program will address the reasons that the sustained adoption of digital health technology is below expectations and what can be done to change that, showing examples of successes and also highlighting lessons learned from failures. The conference is based on the premise that technology by itself is not the solution; the solution must be a combination of process (services), technology and business model (be it all combined in one company or via a network of partners) providing the end-to-end solution.

You can see the full agenda for the event, but all you really need to know is that Vince Kuraitis, JD, MBA, Principal, Better Health Technologies, and Patricia Salber, MD, MBA, CEO, Health Tech Hatch & Founder & Host, The Doctor Weighs In are the two chair people for the event, so you can be sure you’re going to get some great content. They are both people that are deeply and personally interested in the future of healthcare IT and are both people I respect greatly. Plus, I’m interested to hear how Gregg Masters’ session on Healthcare CEOs who Tweet or Won’t goes. Sounds like an interesting session.

If you want to get the early bird registration price for the event, you’ll need to register by Nov 17, 2014. Looks like it’s going to be a great event.

Open Source Electronic Health Records: Will They Support the Clinical Data Needs of the Future? (Part 1 of 2)

Posted on November 10, 2014 I Written By

Andy Oram is an editor at O'Reilly Media, a highly respected book publisher and technology information provider. An employee of the company since 1992, Andy currently specializes in open source, software engineering, and health IT, but his editorial output has ranged from a legal guide covering intellectual property to a graphic novel about teenage hackers. His articles have appeared often on EMR & EHR and other blogs in the health IT space. Andy also writes often for O'Reilly's Radar site (http://radar.oreilly.com/) and other publications on policy issues related to the Internet and on trends affecting technical innovation and its effects on society. Print publications where his work has appeared include The Economist, Communications of the ACM, Copyright World, the Journal of Information Technology & Politics, Vanguardia Dossier, and Internet Law and Business. Conferences where he has presented talks include O'Reilly's Open Source Convention, FISL (Brazil), FOSDEM, and DebConf.

Open source software missed out on making a major advance into health care when it was bypassed during hospitals’ recent stampede toward electronic health records, triggered over the past few years by Meaningful Use incentives. Some people blame the neglect of open source alternatives on a lack of marketing (few open source projects are set up to woo non-technical adoptors), some on conservative thinking among clinicians and their administrators, and some on the readiness of the software. I decided to put aside the past and look toward the next stage of EHRs. As Meaningful Use ramps down and clinicians have to look for value in EHRs, can the open source options provide what they need?

The oncoming end of Meaningful Use payments (which never came close to covering the costs of proprietary EHRs, but nudged many hospitals and doctors to buy them) may open a new avenue to open source. Deanne Clark of DSS, which markets a VistA-based product called vxVistA, believes open source EHRs are already being discovered by institutions with tight budgets, and that as Meaningful Use reimbursements go away, open source will be even more appealing.

My question in this article, though, is whether open source EHRs will meet the sophisticated information needs of emerging medical institutions, such as Accountable Care Organizations (ACOs). Shahid Shah has suggested some of the EHR requirements of ACOs. To survive in an environment of shrinking reimbursement and pay-for-value, more hospitals and clinics will have to beef up their uses of patient data, leading to some very non-traditional uses for EHRs.

EHRs will be asked to identify high-risk patients, alert physicians to recommended treatments (the core of evidence-based medicine), support more efficient use of clinical resources, contribute to population health measures, support coordinated care, and generally facilitate new relationships among caretakers and with the patient. A host of tools can be demanded by users as part of the EHR role, but I find that they reduce to two basic requirements:

  • The ability to interchange data seamlessly, a requirement for coordinated care and therefore accountable care. Developers could also hook into the data to create mobile apps that enhance the value of the EHR.

  • Support for analytics, which will support all the data-rich applications modern institutions need.

Eventually, I would also hope that EHRs accept patient-generated data, which may be stored in types and formats not recognized by existing EHRs. But the clinical application of patient-generated data is far off. Fred Trotter, a big advocate for open source software, says, “I’m dubious at best about the notion that Quantified Self data (which can be very valuable to the patients themselves) is valuable to a doctor. The data doctors want will not come from popular commercial QS devices, but from FDA-approved medical devices, which are more expensive and cumbersome.”

Some health reformers also cast doubt on the value of analytics. One developer on an open source EHR labeled the whole use of analytics to drive ACO decisions as “bull” (he actually used a stronger version of the word). He aired an opinion many clinicians hold, that good medicine comes from the old-fashioned doctor/patient relationship and giving the patient plenty of attention. In this philosophy, the doctor doesn’t need analytics to tell him or her how many patients have diabetes with complications. He or she needs the time to help the diabetic with complications keep to a treatment plan.

I find this attitude short-sighted. Analytics are proving their value now that clinicians are getting serious about using them–most notably since Medicare penalizes hospital readmissions with 30 days of discharge. Open source EHRs should be the best of breed in this area so they can compete with the better-funded but clumsy proprietary offerings, and so that they can make a lasting contribution to better health care.

The next installment of this article will look at current support for interoperability and analytics in open-source EHRs.