I was curious to know more about what Veyo does exactly. Phil explains that
Medicare and Medicaid programs are two fantastic programs that give certain groups of people access to healthcare, people who may not normally be able to afford it.
These groups of people often struggle with getting to their appointments, they may no longer drive or they may not have someone who can take them. This is where Veyo steps in and provides transportation for those people to their medical appointments at no cost to them, Medicare and Medicaid pays the fees for these people.
While it might sound like a gig economy type of service, Phil says it’s a more holistic approach than lyft or uber. People can use public transportation and be reimbursed for it, for example. In Connecticut Veyo mails out the bus token to the person and the person then uses it to get on the bus and go to their appointment.
The point is to not have these people pay for their transportation by pooling federal and state funds to cover the fees. Of course these are non-emergency medical transportation needs only, typically for appointments like follow-ups, dialysis, etc.
Next we get into the actual app experience and more of the “geeky” details. Phil has been the Director of Engineering for about 5 months or so. it was a dot net shop when he got there, much of the code stil is today.
Also on today’s show we talk about which aspects of the Veyo app he has identified as monolithic and what he’s done as a result, Kubernetes, Azure and Google cloud, and why you would do containers or not depending on the situation. Lastly he shares what tech is most exciting for him now – TLA Plus. Join us to hear more about what that is exactly on today’s edition of CTO Studio.