ATTENTION RADIOLOGISTS: AI Is Not Going To Replace You Anytime Soon

I read this article in IoT World about connected health trends to keep an eye on for 2019. It talks about use cases for AI such as wearables, patient dashboards, surgical robots. It talks about some VS guy who a few years ago said that AI can do 80% of what doctors can do and that radiologists would be obsolete by 2022!

The overall progress of AI adoption in healthcare has been really slow. It seems to me that so many companies are trying to develop AI solutions for applications and use cases that are just too complicated or rely on an ecosystem of other technologies to make them happen.

We need to stick to the basics. No tech project or initiative will be successful unless there’s a business case to drive it. And in healthcare, the obvious business case for AI starts where IoT did: service and support.

Companies trying to deploy an IoT technology so they can remotely support their devices in the field are certainly still facing challenges today. More and more of their end users, particularly overseas, are resisting their attempts to connect to their devices on their network because of security concerns. But the business case for remote service and support still is strong.  Reducing downtime, reducing 2nd service calls, improving MTTR and FTF rates still translate right to the bottom line for OEM’s and their customers.

Continue reading “ATTENTION RADIOLOGISTS: AI Is Not Going To Replace You Anytime Soon”

How to Get Organized to Evaluate RevTwo AI

So you’re thinking about trying out RevTwo’s AI technology? We are currently working with several potential customers on proving out our technology for them and would love to work with you.

IDENTIFY KEY ISSUES

To get started, talk to your service and support teams and identify 3-5 common service/support use cases that usually result in having to send a technician onsite to resolve it.

Sometimes our customers may struggle to come up with the right issues they want to address.  One way to get your team thinking is to consider issues with one of these characteristics:

-An issue that happens often

-Something that was expensive when it happened

-Something that everyone in the organization would know about

It also doesn’t have to be something cut and dried like “the water pump failed”. Most complex issues are not that straight forward and usually have multiple root causes and symptoms. For example, it could be “my system is running slowly”.

Continue reading “How to Get Organized to Evaluate RevTwo AI”