I have to start off by admitting some bias here – I love user communities. I grew up with video game user communities supporting my video game modding habit, and I’ve translated that into my professional life by ruthlessly mining user communities for the hoard of knowledge that they contain. So when I managed to get Conversations Connect 2016 in my budget last year, it was less for the HIT conference and more for the users. Those who have met me (or read the Nuance Healthcare Listserv), know that I’m a little outspoken, and while I’m comfortable with message boards and email threads, there are some conversations that just aren’t going to happen in that medium. Sometimes you have to meet people face to face.
But what I found at my first Nuance user conference was not what I was expecting. There were the normal roadmap sessions and user presentations supporting the added value of features like PowerShare and Montage (now mPower). But there was also an open and in-depth discussion with the heads of development and support about the future of PowerScribe 360 – where it was going and where we’d like it to go. We talked at length following presentations, at dinner, and in transit about features that we’d like to see added, how they’d be accomplished, and the level of user support for the requests. I’d expected that sort of discussion with some users, but that’s not a common thing to get from a vendor. I came away from all this with a much better understanding of where Nuance sees its diagnostic solutions going, and it gave me the opportunity to look at where the features I’d like to see can fit into that vision.
And this year I’d like to take that one step further by presenting a report building session at Conversations Connect, which will give users a reason to dive into their own data to get a better feel for how PowerScribe operates under the hood. I’ll be talking about some of the SQL reports and scripts I’ve written to solve the needs of my environment, and discuss how users can leverage the Nuance Healthcare community to tackle problems in their own environment. For example, I’ve used feedback and requests from the user community as a huge driver in developing my PowerScribe toolset, and I’d like to see that work for everyone else.
I hope to see you at Conversations Connect, and don’t forget to bring plenty of questions.