The other day I had the chance to get a demo of Avado‘s PRM (Patient Relationship Management) system from Dave Chase. I’d seen a lot of the writings of Dave Chase throughout the internet. He’s been really smart to go after a number of really high profile tech blogs to get some good exposure for Avado. This isn’t a good strategy for a lot of healthcare IT companies, but it can work really well for the right ones. Either way, I was fascinated by many of Dave Chase’s writings and so I knew it would be an interesting experience.
Needless to say, Dave Chase and Avado are looking at the physician patient relationship quite different from many others. At some point, I may do a full write up of the Avado service, but I think this slide that Dave Chase showed me summed up the comprehensive way that Avado looks at the physician patient relationship. Take a look at the comparison of Avado with a patient portal (I wish PHR was included in the chart as well):
I love companies that look at situations in a really comprehensive manner. Avado seems to be a company that does that. I think it’s still early to know if Avado will be able to execute on this comprehensive approach, but I think it’s a good starting point. Many who have looked at patient portals and PHR software in the past probably wondered why many of the things listed in the chart above weren’t features of the portal or PHR.
I must admit, my next idea for this list is to take it and see how the various PHR and portals handle each of the items on the list. Considering the new emphasis on the patient portal thanks to meaningful use stage 2, physicians might want to give a little extra thought into what the patient portal they adopt is able to do.