STORIES & SOLUTIONS FOR THE MODERN BUSINESS USER

Healthcare IT is such a foreign language to people who don’t think about the intersection of health and technology every day. Before I entered the field, similar to other healthcare newcomers, I thought nothing of the nurses’ or doctors’ notes, aside from whether the blood pressure number they told me was normal. We are not too far removed from the days of paper everything, but I now find it interesting to see the magic behind the technology curtain.

As many of my readers know, I used to work for a software company which is based near Madison, WI that makes a popular electronic health record (EHR). I won’t name the company to help protect their privacy. I practiced primary care pediatrics for many years before moving over the vendor side, so the ways of a large corporation were foreign to me in many aspects. While this might sound odd, what follows is a true story.

Historically, community, critical access, and rural hospitals didn’t have many options when it came to their enterprise systems. Tight margins and limited technical support have held smaller hospitals back from being able to invest in enterprise-scale ERP systems. Often, disconnected systems and paper-based processes were often put in place for materials management, financials, human resources, etc.

I recently read an article in Wired magazine about what sound design is with respect to information technology (IT) and why sound design is so important. I admit that I’ve rarely thought about this field of software development, but it really is important. What exactly is sound design? The author introduces the concept this way: “How do you know whether Siri heard you? Just as in human interaction, good communication is about the flow of conversation, the ongoing exchange of information.” Sound designers try to ensure that the two-way communication between humans and technology works, intuitively and naturally.

The electronic health record (EHR) problem list is . . . well, it’s a problem. I’ve worked with many of the leading EHR vendors and their tools, and no one has solved this quandary. While I haven’t met a physician (or any clinician for that matter) who doesn’t want a well-maintained and curated longitudinal problem list for their patients, I have met many doctors who don’t want to take on the responsibility. “I’m just the specialist” or “I’m in the ED” are common statements, but one might argue (I might argue) that these are the very folks who benefit the most from an up-to-date list of patient issues and concerns.

Anyone who has been part of an ERP implementation knows the importance of having the right people on the project team. While emphasis is typically put on the technology itself, in the end, it is the people of the organization who are using the system. They are the ones who need to know the ins and outs of the software. Dedicating the right resources who know the business, the vision for the future and how the system will be used can drive a more seamless implementation.

Two weeks ago, I had the pleasure of attending the 2019 Cerner CommunityWorks Summit in Kansas City, MO. Avaap was honored to be included as one of a few select vendors to exhibit at the summit. It was a whirlwind week full of education, networking, and happy hours hosted by Cerner. We had great conversations with hospital executives, clinicians, operations leaders, and IT liaisons about the challenges rural, community, and critical access hospitals face. At the same time of the summit, Avaap announced the Columbus Regional Health System go-live with Cerner CommunityWorks after a year-and-a-half long partnership, beginning with system selection through go-live. Seeing their journey and comparing it with stories from other sites in their same domain, whether currently implementing or live for several years, led me to a few key takeaways from the week:

There hasn’t been a sense of urgency to update ERP until recently. Now, digital transformation is atop many CIO’s agendas and with many older solutions ready for retirement, it is time to start thinking about what’s next.

I recently attended the second annual KLAS Arch Collaborative meeting in Salt Lake City. If you’re not aware of the Arch Collaborative, it’s a group of hospitals, healthcare systems, and clinics which survey their clinical users about the technology they use to do their jobs. The Collaborative members then benchmark against peer institutions to see how they’re doing. Some crazy Arch Collaborative findings: