Vivek Garipalli:
Yeah, I think as part of that, itll also be helpful for us and Andrew specifically, to kind of give the framing for how we think about buy versus build
versus rent and the framework with which we kind of made the decision on the infrastructure side, but its a very good question.
Andrew Toy:
Yeah. So basically on the backend, theres two sides of the organization here, right? Like for those of you from SJT and from healthcare, like
most plans will have the IT department, thats their technology department. We have our own R and D department, we build products, just like a startup would. So we build a product, thats Clover Assistant. We also have a tech stack which
is belonging to the plan itself. Like which uses InsureTech, claims adjudication, like all those kinds of things. There, we try to be very progressive as well.
So for example, even on all of our plan tech side, we do not have any on-prem infrastructure, right? So nowhere in my entire Clover infra, Clover Assistant,
all the way through to basic plan tech, do we have on-prem, right? I think thats really, really powerful. We are cloud native throughout, right?
What that means is that because were cloud native, most of the technologies we use, if not all, we select them to be forward leaning, even if were
not going to build it, like we dont build our claims adjudication system. We use HealthRules from HealthEdge, right. But we still built a system where we can put this in the cloud and we dont have to run it
on-prem. We get systems which are API native so that we can pull data in and out of those systems because we know well want to, and then Clover Assistants data infrastructure plugs into all of
those areas so that we can pull it centrally into the Clover system data layer, because everything might have signal in terms of how we give care.
So we
definitely do not build everything. Almost everything in Clover Assistant itself is built by us. Thats our tech stack. We have patents, we have IP. Ill go into where we actually rent, or we get from vendors. We always pick something
which has API capability, inter-op capability, the ability to move data in and out, all using fusing standards on all of those dimensions, so that we can pull data into Clover Assistant and manipulate that
data as appropriate.
We also have a big focus on omni channel outreach and things like that. And thats where we are very progressive on the use of
things like Salesforce, where once again, I dont feel the need to build my own CRM, but you know, Im on the Salesforce product advisory council and we push them and we used that platform, to make sure that we are very advanced at how we
are able to do sort of touch points to the CRM side of things. So IP generating, but in all areas we are cloud native and extremely progressive in our tech selection.
Steven Halper:
Right. So when a physician enrolls to be
a provider in your plan, do they enroll right in Clover Assistant?