Display Bilingual:

I actually applied immediately. I got 00:00
rejected because I was in high school. 00:01
And then I applied again. I got rejected 00:03
again. And then the third time we came 00:05
armed with a prototype that actually 00:07
worked. The market is a great I mean 00:09
it's just like punch in the face. Like 00:11
it teaches you a lot like very quickly. 00:13
I think our biggest learning is get in 00:15
front of the customer and then just 00:17
solve problems for them and and start 00:19
with one specific problem regardless of 00:20
how small it looks. We went from having 00:23
no revenue to having 3 or 4 million in 00:24
revenue in like a year. And it was like 00:26
well we're done. like we solve all the 00:28
all the problems that are to solve and 00:30
then and you're like well no actually 00:31
the game starts now. 00:33
[Music] 00:35
>> I'm thrilled to be joined today by Tana 00:39
Tanden the CEO of Kamir. We're very 00:41
excited to have him because he's one of 00:44
the leading providers of enterprise 00:45
software to healthcare. Thanks so much 00:46
for joining us. 00:48
>> Thanks for having me. 00:48
>> Why don't we kick things off? Why don't 00:49
you tell me what Athellis is and what 00:50
are you guys working on? 00:51
>> Yeah. Uh, Athellis Camir builds software 00:53
products for providers and so we have 00:55
tools that automate their day-to-day 00:58
workflows like Camircribe which is an 00:59
ambient documentation tool revenue cycle 01:01
which is a payment stack. It's basically 01:04
Stripe for healthcare and doctors. It 01:06
submits their claims, uses LLMs to 01:08
negotiate denials with insurance 01:11
companies, appeal those denials, and 01:12
then really render all of the data viz 01:15
and business intelligence to run your 01:16
practice from a financial standpoint. 01:18
And then also a whole host of clinical 01:20
tools. come engage which does back 01:22
office and front office interactions 01:24
with the patient, explaining their bills 01:27
to them, uh explaining what types of 01:28
tasks they need to do to get prepared 01:32
for a procedure like a colonoscopy, 01:33
sending them appointment reminders, do 01:35
on the order of a couple billion dollars 01:37
worth of payments volume every year. Um, 01:39
help document using our ambient AI tool 01:42
20 million appointments every year and 01:45
then uh probably 150 million touch 01:46
points uh annually on on on our patient 01:49
engagement piece. um spread in large 01:51
health systems and private practices. 01:54
>> And so this is sort of a bundle of 01:56
pieces of software that are each solving 01:57
kind of independent problems for a 01:59
practice and collectively sort of serve 02:01
as the software operating system for 02:03
this entire practice. 02:05
>> That's right. And so you know our 02:06
solutions are used by the physicians and 02:07
the nurses in the practice or the 02:08
hospital and then also by the back 02:10
office. So your accountants, your 02:11
billing team, what we call revenue cycle 02:14
in healthcare. everything from uh you 02:16
know submitting the claim to actually 02:18
you know ledgering everything up for the 02:20
uh CFO's office 02:22
>> and you can actually do all of this with 02:24
technology today. You can have an AI 02:25
model that'll call up an insurance 02:26
company and negotiate with them and that 02:27
actually works 02:29
>> 100%. I mean I think the ability for 02:30
language models to both interact via 02:33
voice and text with humans and we just 02:35
got there a year ago and so we're just 02:37
at the precipice of what it can 02:39
accomplish. Um, and when you walk into a 02:40
health system, there are tens of 02:42
thousands of people whose sole job it is 02:44
to do these types of tasks. And if you 02:46
can free up their time, you can bring 02:48
that productivity back onto what matters 02:50
the most, which is patient care. 02:52
>> And I imagine a lot of those tasks are 02:53
already outsourced to some degree. So, 02:54
you're kind of just slotting in to where 02:56
they've already outsourced it to someone 02:58
else. 02:59
>> Exactly. They they use vendors like R1, 03:00
which is an offshoring RCM provider, 03:02
Axis, Omega. Many of them have their own 03:04
in-house shops where they actually, you 03:07
know, it's effectively outsourced, but 03:09
they actually have the individuals on 03:10
site and the the direction of the 03:12
industry for the last 20 years has been 03:14
offshoring. It works okay for what it's 03:16
worth. I mean, these became big 03:18
businesses, but I think LLM's there's an 03:19
opportunity to reimagine all of that 03:21
where it's it's pure software. 03:23
>> And this ultimately becomes a product 03:24
offering for all types of hospitals, 03:27
both small and large. 03:28
>> Yep. We work with the HCAS of the world 03:30
which is a hundred billion dollar 03:32
hospital empire you know 3,000 sites of 03:33
care 186 hospitals all the way down to 03:36
your private practice owned by a single 03:39
physician and you know they use varying 03:40
parts of the solution but it's provided 03:43
as one platform which is revenue cycle 03:45
workflow automation and patient 03:47
engagement in one 03:48
>> what does that actually mean like for 03:50
someone who's not in healthcare like 03:50
what do these roles actually look like 03:52
in terms of where technology fits into 03:54
them 03:56
>> yeah the way I think about it is the 03:56
physicians dayto-day day is really 03:59
defined as interacting with a patient 04:00
and treating that patient uh and then 04:02
often generating the relevant 04:05
documentation so that their back office 04:07
which is think of it like their 04:09
accounting team their AR team invoicing 04:10
can actually submit those claims to 04:12
insurance. 04:14
>> One of the challenges in healthcare is 04:15
the person paying for the for the 04:16
service is not the person receiving that 04:18
service. So a person paying as like an 04:20
insurance company or Medicare or 04:22
whatever receiving it is the patient 04:23
>> is the patient themselves and that 04:25
individual the beneficiary you know 04:27
their incentives are to get treated to 04:29
get treated fast to get the best 04:30
treatment in the world and often the 04:32
insurance company's incentive is to pay 04:33
out as little as possible and hopefully 04:35
treat as little as possible which is a 04:38
counter incentive to really what the 04:40
patient is trying to accomplish. And so 04:42
when it comes to then building 04:43
technology then you guys build 04:44
technology for all parts of this from 04:46
the patient experience itself as well as 04:48
the kind of front and back office 04:50
accounting and kind of administration of 04:52
that patient experience. We we see it as 04:53
you know there are two key protagonists 04:55
in our story which is the patients and 04:57
the providers and we build software 04:59
solutions and hardware solutions for 05:01
that group of individuals and there's an 05:03
effective enemy that's created as a 05:05
result which is the insurance company 05:07
and all of our tools are pointed at the 05:08
payers in in terms of trying to make 05:10
their lives harder and make the lives of 05:12
our customers easier. 05:14
>> Okay. Very interesting. Okay. I want to 05:15
dive into your technology, but before 05:16
that I'd love to hear a little bit about 05:18
the backstory of so why don't we rewind 05:19
the clock uh to the very early days like 05:22
how did this company come about? Like 05:24
what was the very early days like? Um 05:26
what was your experience in YC like and 05:28
kind of how did you even begin to arrive 05:30
at this idea that you're working on now? 05:32
So I I was very fortunate to have grown 05:33
up in the Bay Area and when you're in 05:35
the Bay Area, Y Cominator is just in the 05:37
ether like people like Casar and Justin 05:40
Khan and Sam Alman were like our heroes 05:43
and the I remember it was like 2013 or 05:45
2014 that we somehow snuck into YC 05:48
startup school because it was happening 05:51
in Certino. Um 05:52
>> I think I was there too actually also 05:53
sort of snuck into it. 05:55
>> It was a great start. I think Zuck came, 05:56
Jeff Dorsey was there. 05:58
>> Yep. Same one. Um, Flexport did their 05:59
interview on stage and I remember I was, 06:00
you know, I was like teenager in high 06:02
school. I was just in awe of of of these 06:03
people that had built such amazing 06:06
technology and YC is this ecosystem that 06:07
had enabled a lot of it uh and was 06:10
starting to enable more and more of it. 06:11
So, you know, fast forward a couple 06:13
years, Y Cominator hosted this hackathon 06:15
called YC hacks and uh I had read a 06:17
couple papers about how you could use 06:20
computer vision to potentially analyze 06:23
blood cells and also use really cheap 06:25
pieces of glass to enhance a smartphone 06:27
camera to basically turn into a 06:30
microscope. 06:31
>> So, this is like in 2016 or 174. 2014. 06:32
So, this is like early computer vision. 06:35
Like the deep learning is like just 06:37
starting to happen to some degree. 06:38
Computer vision is just barely starting. 06:39
the the models that we were using them 06:41
were like even like for for computer 06:42
vision were you know you're using like 06:44
segmentation algorithms like watershed 06:46
and like you know we like random forest 06:48
is what like were like the best models 06:51
for for often NLP and even in some task 06:52
in computer vision. And so armed with 06:55
those two pieces of information, I went 06:57
to YC hacks um and built this little 06:58
really hacked together smartphone camera 07:01
with a random force that had been 07:03
trained to classify malarial cells 07:05
versus non-malarial cells um based off 07:07
of a training set on the internet. And 07:09
it worked like pretty well like you 07:12
could you could segment these two. Um 07:13
and and then you know I was a senior in 07:16
high school at the time but it became my 07:18
science for project that year and I got 07:20
very obsessed with this this idea of man 07:22
we can use computer vision to automate a 07:24
task that someone like a pathologist a 07:26
very trained person is doing in in a in 07:28
a expensive laboratory and bring that 07:30
care directly to the patient um and 07:32
simplify the provider's life and that 07:34
eventually became a which was started as 07:36
a med device diagnostics company. Oh, 07:39
interesting. Okay. So, when you when you 07:40
applied to YC then, so this is shortly 07:42
after that, maybe a year or two after 07:44
you were a freshman in college or 07:45
something like that. 07:47
>> So, I actually applied immediately. I 07:47
got rejected because I was in high 07:48
school and and then I applied again. I 07:50
got rejected again. And then the third 07:53
time we came armed with a prototype that 07:55
actually worked. And it was after Id 07:57
spent about six months at Stanford and 07:59
you know the resources that you have 08:01
access to with the med school and the uh 08:03
you know in the the mechanical 08:05
engineering department like we were able 08:06
to put something pretty serious 08:08
together. Uh and that's when we got in 08:09
for summer 16. 08:11
>> And this was with a med device that was 08:12
doing some type of kind of image based 08:13
analysis of was it was this original 08:15
idea of like blood sample analysis? 08:18
>> That's right. So it was basically taking 08:19
a small volume of blood, turning it into 08:21
a monollayer, so you could see, you 08:23
know, single cells basically like 08:25
they're on a on a smear. Um, and then 08:26
basically a a microscope with an imager 08:29
attached to it, but was hacked in a way 08:31
that it was very uh large field of view 08:33
and still high resolution. And then we 08:35
trained computer vision algorithms to 08:37
recognize and segment those various 08:38
cells. 08:40
>> And so at this point, you know, your 08:40
background is primarily in computer 08:42
science. I assume you had some 08:44
experience in this application area in 08:45
biology in high school and early 08:48
college. You know, what gave you the 08:49
conviction to be like, I'm going to 08:51
presumably drop out of college, start 08:53
this company that is in a regulated 08:55
industry with medical devices. Like how 08:57
did you actually arrive at that 08:58
conviction? I 08:59
>> I would say two key sources. one my 09:00
co-founder Deepka who's also one of my 09:03
closest friends uh we used to compete in 09:04
science spheres against each other and 09:06
her research was always way more uh call 09:08
it med device or bioengineering focused 09:11
and she worked through high school on 09:13
this uh micrfluidic test strip that 09:16
could detect salmonella very quickly 09:18
from you know produce and you know I 09:20
thought it was remarkable that you could 09:23
build something like that in in high 09:24
school because it was you know was 09:26
hardware there was bio involved you have 09:27
to have a good understanding of you know 09:29
how these det protection strips were 09:31
actually fabbed and cut and whatnot. And 09:32
so it was clear that okay, we could 09:34
build things in the real world with uh 09:36
with micrfluidics. And then number two, 09:38
I think the, you know, when you're at 09:40
Stanford, you get to meet these amazing 09:43
professors. For me, Chris Manning was 09:45
was someone who gave me my first shot in 09:47
the Stanford AI lab under Richard 09:48
Socher, um, who started Metammind where 09:50
I was a research intern as well. And I 09:52
think they were just it was really 09:56
motivating because for them it was like 09:57
there's there's no boundaries to what 09:59
machine learning can do. you should go 10:00
after these complex industries. Um, and 10:02
they, you know, Richard was ended up 10:04
being the first check right after Y 10:06
Cominator 50K check and and I think that 10:07
support really encouraged us as well. 10:10
>> Yeah, totally. Okay. So, so let's now 10:11
talk about your time in YC. You know, at 10:13
this point it's just the two of you. Um, 10:15
you're working on this regulated medical 10:17
device. What did you set as kind of your 10:20
demo day goal and like how did you what 10:22
did you accomplish in those few months 10:23
of YC that ultimately then put you on a 10:24
trajectory to build something somewhat 10:27
different now from what you describe 10:28
now? We'll kind of talk about that that 10:30
transition. But yeah, what what did that 10:31
first few months look like? 10:32
>> I I think the first week itself of YC 10:33
was total shock because we came in with 10:35
these traditional timelines for how long 10:37
a med device should take or how long 10:40
anything in healthcare should take, 10:41
>> which is like years or something. 10:42
>> And and that seemed pretty good to me. I 10:44
was like, cool. Like we're going to be 10:46
on this for a long time. It's, you know, 10:47
we're going to go super slow. Remember I 10:49
had a conversation with with Casar, who 10:50
was our group partner and is also now on 10:52
our board. Um, and he, you know, he was 10:54
basically like, he made me walk through 10:58
every assumption on, well, why is that 11:00
months? That that just seems like it's 11:03
like a paperwork. You should be able to 11:04
do it in a week. Why are you waiting for 11:05
Stanford IRB to approve this trial where 11:07
you could go to some local lab and 11:09
probably get it done in a week? Uh, and 11:10
I think because of that, Deep and I sat 11:13
down and just like reimagined how 11:15
quickly you could build this stuff and 11:17
and really went from almost like 11:18
zerobased budgeting, but for a clinical 11:20
trial. And the other piece was, you 11:21
know, if you're a competitive person, in 11:24
our batch, we had companies like, you 11:26
know, Scale AI was in our batch and and 11:28
this was a company that pivoted mid 11:30
batch and got to like millions in 11:32
revenue by the end of the batch. You 11:34
know, for us, we never wanted to just be 11:36
the best healthcare company in the 11:37
batch. We wanted to be the best company 11:38
in the batch. And and so it was it was 11:40
this this pressure that we sort of 11:42
created for ourselves and that group 11:44
partners created that really caused us 11:45
to pace uh more aggressively than if we 11:47
were doing it outside of of of YC. And 11:49
so we set this goal of we will finish a 11:52
clinical trial and have a ready to go 11:54
FDA submission by the end of YC. Um and 11:56
it was crazy but we actually got the 11:58
clinical trial done. We needed to redo 12:00
some of the experiments per the FDA's 12:02
request. So the the approval itself took 12:04
a little longer, but we we we got the 12:06
the core basis of of the clinicals done 12:08
in those 10 weeks. 12:11
>> I mean, that's pretty absurd pace, 12:12
right? I mean, I think like when you 12:13
think about a normal regulated medical 12:14
device, we're talking about many years 12:15
in that process. And yeah, I mean, I 12:17
think this ability to kind of break down 12:18
into its only what the critical 12:21
components of it are, what parts you can 12:23
actually shortcut versus not is it's a 12:24
very challenging head space to get into. 12:27
And then you guys as as 19-year-olds, I 12:28
mean, I can only imagine some number of 12:30
people you talk to are like, "Who are 12:32
these guys to be making a medical 12:34
device?" Like, how do you go up against 12:35
that? Like, how did you get yourself to 12:36
not care? Basically, 12:38
>> we had many conversations where we got a 12:39
quote from Stanford where it was like, 12:42
"We can run this trial and it'll be 12:43
$120,000 and it will take 3 years." 12:44
>> And and I mean, when you see something 12:47
like that, it's almost so absurd that it 12:49
wheels you into action a little bit, 12:52
which is like, if this is the default 12:53
system, I mean, something is broken. and 12:55
and and I think um because of that we 12:57
thought to ourselves it's time to 13:00
rethink first principles and it really 13:01
came down to one identifying a partner 13:03
hospital that was small enough and 13:06
willing to work with us very quickly and 13:08
that ended up being in Huarez Mexico so 13:10
we flew out there mid batch uh ran the 13:12
trial with them number two is really 13:14
deleting as many parts as possible and 13:17
running the simplest form of the trial 13:19
so instead of hiring traditional 13:20
clinical trial operators deep and I ran 13:22
the trial ourselves she took samples in 13:25
the front room. I was in the back room 13:27
running them on the device. Uh, and then 13:29
we had a nurse that we had hired for the 13:31
day who was running them on the 13:32
traditional system called the 13:33
Sysmex5000. 13:35
And we would then compare those results 13:36
and show that they were accurate and and 13:38
equivalent to each other. And the whole 13:40
process from finding the hospital to 13:42
making sure the devices were ready to 13:46
actually running the trial and then 13:48
getting the results end to end was 13:50
probably 6 weeks of the batch. Once we 13:52
hit those milestones, that's when we 13:54
raised our seed round. 13:55
>> Okay. So you started there though. You 13:56
started with this medical device. Today 13:57
you're not a medical device company for 13:59
the most part at least or at all I 14:00
think. What was that arc like? I'm sure 14:02
there was many steps in which the 14:04
company changed. But maybe tell me a 14:06
little bit about how you segment your 14:07
brain into like the few eras of this 14:09
company and how you went from one of 14:11
these to perhaps pivoting to uh kind of 14:13
another version of that company over the 14:15
last few years. you know, we did YC, we 14:17
raised our seed round from Sequoia, 14:19
Alfred, um, over at Sequoia, and the 14:20
next 18 to 24 months just became brutal 14:23
focus on getting an FDA clearance. Um, 14:26
get the device to a state where it can 14:29
replicably run in in in clinical trials, 14:31
uh, where you can, you know, all kinds 14:34
of crazy tests like we have to drop the 14:35
device and kick the device and, you 14:37
know, things break and you have to be 14:39
able to continue to pass the the 14:40
relevant tests. And that was it. We were 14:42
laser focused on this one goal. And I 14:45
think that was very freeing in some ways 14:47
because it was the only thing we had to 14:48
get done. We also only had $3 million to 14:50
do it. Um, and you know, the the other 14:52
piece of it was to start proving out the 14:54
commercials. And that's when I started 14:56
engaging with uh what became our first 14:58
customer, which was actually a 15:00
pharmaceutical company that manufactured 15:01
a drug called Cloopene, which is a 15:03
refractory schizophrenia treatment that 15:05
causes neutropenia, white blood cell 15:08
count reduction as a side effect. And 15:10
you know, they told us, "We've been 15:13
dreaming about a device like this." and 15:14
and they signed that first million-doll 15:16
contract even before we had approval 15:17
just based off of the results of the 15:19
clinical. So, we had that commercial 15:21
proof. We had early clinics that were 15:22
adopting it. We were, you know, seeing 15:24
them use it and then we got the FDA 15:26
clearance and that was really this like 15:28
the first like epoch of the company the 15:29
first like two two and a half years. 15:30
>> Once we got that, you know, the the 15:32
market is a great I mean it's just like 15:34
punch in the face. Like it teaches you a 15:36
lot like very quickly. 15:38
>> You must have felt like you were on 15:39
cloud n then you're like, "Oh, we're 15:40
we're chilling. We we figured this out 15:41
now. Now we're going to go to the moon 15:43
with this." I I mean we got the 15:44
clearance and it was like well we're 15:45
done like we solved all the all the 15:47
problems that are to solve and then and 15:49
you're like well no actually the game 15:50
starts now and the exciting thing was 15:52
that we went from having no revenue to 15:53
having 3 or 4 million in revenue in like 15:55
a year. So as far as traditional series 15:57
A metrics and pacing like we were there. 15:59
The thing that we realized in parallel 16:01
was okay we can probably scale this 16:03
business to tens of millions in revenue 16:05
and build a business that a ro or an 16:07
Abbott or someone will buy for you know 16:09
200 million bucks or whatever that 16:11
number is like a good med device 16:13
outcome. At the same time we had this 16:15
team that we felt could run through 16:18
walls and had built machine learning 16:20
software had gone through regulatory 16:22
done the operations of device 16:24
manufacturing and we were in these 16:25
clinics like our devices were deployed 16:27
and we saw all kinds of problems. 16:29
>> So you got in there by deploying the 16:30
devices we were solving all sorts of 16:32
other problems they were facing and 16:34
along the way you discovered there's 16:35
this massive other set of problems that 16:36
you can solve too. 16:38
>> Yep. We we wanted to go from making 16:38
their lives easier for a percent of 16:40
their patients. So we were serving with 16:42
our athals one device to 100% of their 16:43
patients uh and their whole chronic care 16:46
panel with you know the teleahalth tools 16:48
and the revenue cycle tools. And and I 16:51
think you know my looking back the 16:53
reason this time period was so valuable 16:55
is we would not have had you know a 16:56
valuegiving relationship with these 16:59
customers had it not been for the 17:01
device. They trusted us. They saw us as 17:02
more than just a device company. They 17:04
saw us as those kids that would show up 17:06
in their office, set up the device, 17:08
train them how to use it. And because of 17:10
that, they would tell us about all these 17:11
other problems they had in their 17:13
clinics. Like, hey, when I get the 17:14
result from the device, I have to upload 17:16
it into this portal manually, and then I 17:17
have to call up a pharmacist and tell 17:19
them like, hey, the fax is coming 17:21
through. We would just hear these, you 17:22
know, these complaints like, well, it 17:24
would be amazing if I could, you know, 17:26
upload this automatically or if I could 17:27
fill this claim form out automatically 17:29
to get the next set of medication 17:31
adjudicated. And that's when we started 17:33
building software and it honestly felt 17:35
like playing on easy mode after two 17:36
years of building building hardware and 17:38
dealing with the FDA. 17:40
>> You know, at some point presumably the 17:41
software starts to take off and become a 17:42
pretty significant part of your 17:44
business. At at some point do you you 17:45
what is that process like of leaning in 17:47
on that and perhaps you know abandoning 17:50
the thing that or or at least leaning 17:53
out of the thing that has been your 17:54
initial driver that got you there in the 17:56
first place that has this big pharma 17:57
ideal for example. What does that 17:59
process look like? It was interesting 18:00
because we had two paths in front of us. 18:02
Be the best aellis swan medical device 18:03
company in the world and just you know 18:06
build a great compounding 40 50% 18:09
annualized grower in that in that 18:11
segment. Alternatively it was bet on 18:13
yourself again and expand the TAM and do 18:16
more for these customers um based on the 18:18
learnings we were getting from the 18:20
market. 18:21
>> And also when was this by the way? 18:21
>> This was in 2020. Um 18:23
>> so you've been at this now for like 18:25
fourish years. Like this has been your 18:27
thing. You're a med device company. 18:29
you're growing this thing and now 2020 18:30
is coming. A lot of things are happening 18:32
in the world uh as I'm sure is going to 18:34
be relevant here. And then also you're 18:36
starting to see that there's an 18:37
interesting new opportunity in software. 18:39
>> Yep. And I remember it was I forget was 18:40
it might have been Robin Hood or it 18:43
might have been some company. We had 18:44
this interesting uh fireside that we 18:45
went to and they talked a lot about 18:48
share of wallet and this concept of you 18:49
want to do more and more for your 18:52
consumer and go from just being you know 18:53
with Robin Hood like their toy stock 18:55
couple hundred bucks playing around to 18:57
like no this is like a meaningful 18:59
financial product for your entire 19:00
portfolio. For us, the the analogy was 19:02
was apt because we went we we wanted to 19:04
go from treating 1% of their patients, 19:07
these refractory schizophrenia patients 19:09
that were treatment resistant to 19:11
treating all their patients. And I 19:12
remember Deep, my co-founder, she was in 19:14
one of these clinics. She spent a lot of 19:16
time in these clinics and she was like, 19:17
"It's insane. We are helping them for 1% 19:18
of their patients and they love us so 19:21
much. Imagine if we could build tools 19:22
for all of their patients, their full 19:25
thousand patient panel." And and I think 19:26
that's when we took the bet. We're like, 19:28
we can build a multi-billion dollar 19:30
software business, sensor business in 19:32
this segment by expanding what we do for 19:34
these customers and and grow a lot 19:36
faster than the 100,000 total patients 19:38
that had this one condition. 19:41
>> And then this was before the LLM era was 19:43
really taking off. You were obviously a 19:45
machine learning company and you had a 19:47
lot of experience with building 19:48
software. Um, but like what did that 19:49
initial software look like? Like what 19:51
types of problems could you solve then? 19:52
Presumably now you can solve many more. 19:54
Yeah, we started with the basics which 19:55
is one uh co hit and and as a result our 19:57
providers needed ways to monitor their 20:02
patients in their homes. So we built a 20:04
basic telealth portal and a set of 20:06
remote monitoring devices that connected 20:09
into it and allowed them to interact 20:10
with those patients many of whom also 20:12
used the FLS1 device in the point of 20:14
care or in their homes. The very next 20:17
thing we started playing around with was 20:19
workflow automation as it related to 20:20
claim submission and payments. So 20:23
everything from collecting dollars from 20:25
these patients to uh you know starting 20:27
to submit claims to insurance and first 20:29
we did it just for or you know this 20:31
subset of remote monitoring and cloopine 20:33
patients and then expanded organically 20:36
to more and more of the practice 20:38
>> and and these are problems you basically 20:39
discovered from being in their offices 20:40
like you know you and your co-founder 20:42
are in there and you're noticing and 20:43
hearing from them about whatever other 20:45
problems they're facing and you're kind 20:46
of seeing okay like as exciting as this 20:47
is we sort of have to solve these as we 20:49
go. 20:51
>> Exactly. There is no other way to 20:51
discover these problems than being in 20:53
your customers dayto-day and and and 20:55
just seeing them because there's so much 20:57
nuance to where they get stuck and it's 20:59
not something you can derive you know by 21:01
reading an article or you know watching 21:03
a video online. You you have to be in 21:05
the in the heat of things. 21:07
>> Yeah, totally. I mean I think we see 21:08
this with with companies every day today 21:09
especially in this sort of new 21:11
technological moment is that it's very 21:12
hard to conceive of great startup ideas 21:13
kind of in your home or in a lab. It's 21:15
much more likely to encounter them 21:17
somewhere in the field by being in 21:19
there. And so for you guys that sort of 21:20
was a was a game changer in putting you 21:21
in that place. 21:23
>> 100%. 21:24
>> Well, okay. Well, why don't we, you 21:24
know, kind of move forward now a little 21:25
bit to to today and and get there by 21:27
kind of talking about what the last few 21:30
years has looked like in healthcare 21:32
generally. I mean, there's been an 21:34
incredible amount of changes happening 21:35
in healthcare. To your point, there's 21:37
these massive mega conglomerate style 21:38
hospital businesses. There's 21:41
consolidation in payers and PBMs. for 21:43
you guys as you see this sort of 21:45
changing landscape where do you one 21:47
where do you fit into that landscape and 21:49
then also how does that changing 21:50
landscape affect your business and as 21:52
you think about growing it 21:53
>> I I think it's it's it's really 21:54
interesting is if you go back to the 21:55
'90s uh the life of a physician was 21:57
great they had a tight panel of patients 21:59
they knew them personally they treated 22:02
them and if there was you know chronic 22:04
diseases they were able to talk to the 22:05
patient very quickly idea of a concierge 22:07
doctor was was fairly common you know 22:10
anyone in upper middle middle class had 22:12
a concierge doctor of some kind. And as 22:14
the bloat that came from insurance and 22:18
regulation and and and just what we 22:21
turned healthcare into into this sort of 22:23
like admin state 22:24
>> is what really broke down the 22:26
productivity of a physician where they 22:28
turned into these these, you know, cogs 22:30
and this greater wheel and there's, you 22:32
know, patient productivity numbers they 22:35
have to hit. There's countless tasks 22:36
they have to do. regardless of how 22:38
efficient they are, they always take 22:40
documentation home and they're filling 22:41
out paperwork. And I see it as this 22:43
great misuse of of talent in that we 22:45
have some of the most intelligent, 22:48
well-trained, uh, uh, well-intentioned 22:50
people in the country spending their 22:53
time doing tasks that really software 22:54
should be doing for them. Uh, LLMs are 22:57
not. And what we've seen happen is a lot 22:59
of physicians give up on this dream of 23:01
the private practice or the 23:03
physician-owned practice in change for 23:05
joining a large health system that does 23:07
take on a lot of the overhead that you 23:08
now need to pay in order to just operate 23:11
a health system. 23:13
>> This is like negotiating with insurance 23:14
companies and with PBMs and having uh 23:15
farmer relationships and all that kind 23:18
of stuff, 23:20
>> paying for an EMR, dealing with 23:20
malpractice. And so all of this made it 23:22
harder to practice care and and and 23:25
turned it more into this again like this 23:28
admin business. And and I think now with 23:30
LLMs, there's this generational 23:32
opportunity to free the physician and 23:34
and really bring them back to what they 23:36
love doing the most, which is rendering 23:38
care. And I think our work is in service 23:40
of that. Uh take the work tax and just 23:42
nuke it. take every part of their 23:45
revenue cycle, their back office, their 23:47
documentation, um, and and use software 23:49
to automate, uh, large chunks of that. 23:51
>> And I mean, you guys sell to, you know, 23:53
both this mid-market and larger market 23:54
or or any kind of enterprise market. 23:56
It feels like what you're saying here is 23:59
that this midm market is what you see as 24:01
potentially best suited to take 24:04
advantage of of LLM and especially sort 24:06
of this broader technological adoption 24:09
because it frees them from needing to 24:10
consolidate into these bigger 24:13
enterprises and perhaps the advantage of 24:15
the bigger enterprises won't be as much 24:17
the case in the future. Is that kind of 24:18
how you see it or do you think not so 24:19
much? 24:21
>> I I I think it goes both ways. one I 24:21
think we will see it's sort of the 24:23
analogy we use is like Amazon and 24:25
Shopify where over the last 20 years or 24:26
10 years or whatever time period Amazon 24:30
has grown remarkably um as it's you know 24:31
taken a lot of share from traditional 24:35
retail and also expanded what we order 24:36
online but then Shopify has exploded as 24:38
well as more people are able to start 24:41
their own businesses and I think you 24:42
will have this aspect of the physician 24:44
who practices in a health system but 24:47
then also has their own practice um and 24:49
chooses their hours and because of the 24:51
fact that software is automating more 24:54
and more of their day, they can see more 24:56
patients and do it in in a way that is 24:58
sustainable and gives them energy as 25:00
opposed to drains them out by the end of 25:02
the day. 25:03
>> Yeah. So, let's talk about that a little 25:03
bit in terms of software automating more 25:05
and more of their day. There's been a 25:06
lot of software adoption in healthcare 25:07
over the last 10 years. Most of it 25:09
through electronic health records and, 25:11
you know, kind of payment portals with 25:12
insurance and whatnot. Um, but a lot of 25:14
it has been promised to doctors as 25:16
saving them time or helping patients in 25:19
various ways over the last decade. But 25:21
the critique has often been that well, 25:23
it's not really been about that. It's 25:24
been about getting paid for care. It's 25:25
been about billing mostly and not 25:28
actually about care. How do you see what 25:29
that technological adoption story looks 25:30
like over the last decade and then over 25:32
this next decade? Like what are things 25:34
you think are going to be fundamentally 25:35
different about this technological 25:37
moment? It's it's definitely true 25:38
because a lot of the digitization and 25:40
creation of EMRs came from a place of 25:42
compliance and a place of of billing and 25:45
institutionalizing a lot of regulatory 25:48
requirements as opposed to true you know 25:50
unleashing the doctor. You know do Dr. 25:54
classical who's one of our uh you know 25:56
he used to run Thomas Jefferson 25:58
University the health system um you know 25:59
he calls this the epidemic which is like 26:02
there's just this proliferation of of 26:04
work tax in every organ in the country 26:06
in IT departments in you know in the 26:07
physicians day-to-day and it didn't 26:10
solve the problem it set out to solve 26:12
because the software was built from the 26:13
perspective of the CIO's office and the 26:16
CFO's office 26:17
>> who are optimized around getting paid 26:18
basically. 26:20
>> Exactly. optimized around getting paid 26:20
and not getting sued and and those are 26:22
the you know the two the two drivers you 26:24
know the CLLO's office as well now I 26:26
think you're seeing a lot of 26:28
physician-driven adoption of these tools 26:29
one postco we really stress the system 26:31
out we we burnt we burnt out our 26:34
physicians or burnt out our nurses and 26:36
there's almost no option but for them to 26:39
use these tools uh uh and and and push 26:41
for the adoption of these tools in order 26:44
to just keep up with their with their 26:46
day-to-day patient volumes our loudest 26:48
advocates even in largest health systems 26:50
are physicians. 26:51
>> Well, this is really fascinating. That 26:52
feels like a huge difference, right? I 26:54
imagine in selling the first version of 26:55
EHRs five or six years ago, you're Yeah. 26:57
largely selling to central IT teams, 26:59
CIOS, that type of thing. Here, you're 27:01
saying today when you approach selling 27:03
your recent software, it's an individual 27:05
doctor who's your advocate. 27:07
>> 100%. We have we have a self-s serve 27:08
ambient documentation tool called 27:10
Scribe. And 27:12
>> yeah, how does that work actually? Can 27:13
you tell us a bit about that? 27:14
>> I would say it's one of the explosions 27:15
in software categories recently. You've 27:16
probably had in terms of like really 27:18
fast LLM adoption, I think you've had 27:19
coding tools like the winds surfs and 27:21
the cursors of the world and then you 27:23
you've had ambient documentation tools 27:25
um in the in the healthcare world. And 27:27
ambient documentation listens to the 27:28
conversation that a patient and a 27:30
physician have. It summarizes that and 27:32
then it generates all of the 27:34
documentation based on being trained on 27:36
previous approvals, previous pieces of 27:37
documentation and basically hands it off 27:39
to the revenue cycle teams ready to go. 27:42
>> It's like a perfect problem for LM. This 27:43
thing LM would be really good. 27:45
>> It's a perfect problem for LM. You have 27:46
transcription, you have summarization, 27:47
you have, you know, references and 27:49
citations back to clinical source 27:51
material all in this one, you know, one 27:52
set of models. Uh, and that tool, we 27:55
went from 2023 doing maybe 100,000 27:58
appointments through that tool to this 28:00
year, we'll probably do 20 to 25 million 28:02
appointments through that tool. There's 28:04
a self-s serve motion that has gone from 28:06
last year zero appointments to this year 28:08
5 million appointments. Um, 28:11
>> self-s serve motion as in you don't go 28:13
through the hospital IT team at It's a 28:14
physician finds it online. Uh we 28:15
advertise directly to them. They sign up 28:17
often paying with their own credit card. 28:20
Um 28:21
>> that seems new. 28:22
>> It seems crazy. I mean I was shocked 28:23
when when we saw this working. Uh it was 28:24
this is not behavior you've seen in 28:28
healthcare before. 28:29
>> And from that we you know we then go 28:30
upsell almost like Slack or Dropbox or 28:33
one of these traditional software tools 28:35
the whole enterprise where we pitch the 28:37
integrations into their EMR the whole 28:39
workflow tool. Um, and that's been a 28:41
massive, you know, source of of of 28:44
expansion for us. 28:46
>> If I'm a founder, you know, I might be 28:47
thinking, well, isn't it going to be 28:48
really annoying in terms of HIPPA and in 28:50
terms of all these rules and whatnot in 28:51
terms of actually 28:53
>> getting a doctor to sign up? Like, it's 28:54
not even intuitive to me that a doctor 28:55
is allowed to self-sign up for this type 28:57
of thing. How do you guys think about 28:59
that? Is that has something changed that 29:00
makes it easy or was it never actually 29:02
as hard as people thought? 29:03
>> It's a good question. And I think 29:05
there's definitely a lot of compliance 29:06
departments in hospitals that are very 29:07
much against self- adopted software, but 29:10
the productivity gains are so great that 29:12
it's happening one way or another. Um, 29:14
and the options that a compliance 29:16
department at a hospital has is either, 29:19
you know, sign up and make this part of 29:21
the institution or, you know, tell your 29:24
physicians to continue being burnt out. 29:26
And usually they're picking the one that 29:28
that ends up with happier physicians. 29:30
You know, there are totally ways for 29:32
there to be HIPPA compliant self-s 29:33
served tools. Now, that might defy the 29:35
individual policies of a of a private 29:37
institution like like a hospital itself, 29:39
but from a pure HIPO compliance 29:41
standpoint, right? 29:43
>> It's not actually a legal risk. It's 29:44
just the hospital's own compliance. 29:45
>> It's their own internal policies. 29:46
>> Yeah. And so, what does it actually look 29:47
like in terms of other technological 29:49
problems you face? Like what are some 29:50
>> maybe just diving into some technical 29:52
challenges? Yeah. Um I can imagine for 29:54
something like scribing at least to me 29:56
intuitively that seems relatively 29:58
straightforward as a technical challenge 30:00
but perhaps at that scale actually not 30:02
so much whether in that one or in some 30:04
of the other products you guys have what 30:06
are some of the hardest technical 30:07
problems you guys face in actually 30:08
making software here especially for a 30:10
company that is selling to healthcare as 30:12
opposed to any other enterprise SAS 30:14
company 30:16
>> in just the case of scribing simple at 30:16
first glance but when you scale you know 30:19
you're dealing with millions of hours of 30:21
audio that is often being uploaded over 30:22
shaky networks in the basement of doc in 30:24
you know a hospital in a lab you know 30:26
pharmacy that's a you know freestanding 30:29
part of a freestanding clinic in rural 30:31
America so you have to build great 30:32
offline mode and you know retention and 30:34
and and the ability to you know upload 30:36
these things silently in the background 30:38
and all these like traditional 30:39
challenges that consumer apps have 30:41
solved I think are now being solved in 30:42
healthcare as well. Number two, you 30:44
know, we process billions of dollars 30:47
worth of claims volume every year in our 30:49
revenue cycle business. And as part of a 30:50
revenue cycle is it's stripe for 30:53
healthcare, right? You're the interface 30:54
between the physician and the payer and 30:56
the payers at a 100 blocks that make it 30:58
hard to get paid. Everything from losing 31:00
the claim to, you know, not telling you 31:03
that it was denied for a couple weeks so 31:05
you don't hit your, you know, so you hit 31:07
your timely filing limit and then can't 31:08
get paid anymore. We've built models 31:10
that are constantly checking for all of 31:12
these threats. Uh I almost see it as 31:14
like a like a cyber security problem. 31:16
Every denial is is something broke or 31:18
this is the payer trying to attack the 31:20
physician. We have to debug what went 31:21
wrong and help the physician get paid 31:23
out. A good example is all these payers 31:25
have APIs now, right? 31:28
>> They just work 80% of the time. What 31:29
what that means is is that you might get 31:31
responses that are, you know, missing 31:33
some of the adjudication or there's a 31:35
there's a secondary insurance that needs 31:37
to pay out and then you need to go 31:38
separately hit that secondary insurance 31:40
or these two insurance companies aren't 31:41
talking to each other and they both got 31:43
a medical record but are claiming they 31:45
didn't and you have to show them that 31:46
audit trail. And so the technical 31:47
challenges are are very interesting 31:49
because you're doing this at scale and 31:51
you need to monitor these processes 31:53
constantly. Um but when you solve them, 31:55
physicians win, which is very exciting. 31:58
>> Yeah. And especially today if they are 32:00
your advocates. I mean I think you get 32:02
this even I imagine much faster sales 32:03
motion than probably in the early days 32:06
where if you can show them these 32:08
technical solutions and they can 32:10
actually advocate and like get your 32:11
thing incorporated into their hospital. 32:13
I mean that's huge for you guys. 32:14
>> I mean for our revenue cycle business 32:15
the word of mouth is literally my 32:17
revenue went up by 15%. And that is the 32:19
most potent word of mouth in in the 32:22
world and that's why we're seeing that 32:24
business scale so quickly. Um, I think 32:25
in our ambient business, the word of 32:28
mouth is I save two hours every day and 32:30
I did it with this free tool that I 32:32
found online and if I want to get it 32:33
integrated, it's, you know, like a 32:35
hundred bucks a month or whatever the 32:36
price is. So that that's to me why why 32:37
why I think these tools are spreading so 32:41
quickly now. 32:42
>> And how do you think about yourself in 32:43
terms of a the types of software you 32:45
guys have? You know, you call yourself 32:47
sort of a compound software company, 32:48
sort of a rippling for healthcare as 32:50
we've talked about in the past. 32:51
>> What's the basis for that strategy? you 32:52
know, how do you guys think about growth 32:54
and why grow this way versus doubling 32:55
down on one of these and trying to make 32:57
that be a massive business in itself? I 32:58
>> I think the complexities of healthcare 33:00
and the way that people get paid in 33:02
healthcare and really where the 33:04
operating cash flow lies really make it 33:05
like you can only really build a hundred 33:07
billion dollar business in healthcare as 33:09
a platform company. That being said, you 33:11
have to start as a point solution. We 33:13
started as a med device and then 33:15
eventually turned into this again a 33:16
point solution for a very specific 33:18
subset of claims and then over time 33:19
turned into this platform. Uh but now 33:21
that we're this platform, we also have 33:23
amazing distribution unlocks. We get to 33:25
work with General Catalyst and their 33:27
health assurance framework. They have 40 33:28
health systems that are all signed up. 33:30
HCA is on our board. It's hundred 33:32
billion dollar hospital empire. And so I 33:34
think in the same way that in the 2010s, 33:36
Palunteer solved distribution and 33:40
defense and a lot of call it like 33:42
Fortune 100 uh use cases and then just 33:43
aggregated smart people to go work on 33:46
crazy problems. We're doing that in 33:48
healthcare. The hardest problem in 33:50
healthcare having now spent eight nine 33:51
years in it is distribution and you can 33:54
reinvent the distribution wheel over 33:56
eight nine years for yourself or you can 33:58
go build you know effectively point 34:01
solutions as part of this platform um 34:02
and not worry about the revenue engine 34:05
because the backend revenue cycle has 34:06
that covered 34:08
>> right as long as you ultimately have 34:09
revenue cycle management at some part of 34:11
your platform. Exactly. Kind of works. 34:12
>> Exactly. I mean do you think that 34:14
changes now in this era of kind of 34:15
doctorled advocacy of acquiring software 34:18
you know if if for example it is much 34:21
easier for hospitals to acquire software 34:23
than ever before especially smaller 34:25
clinics does that change the calculus 34:26
there at all or do you think uh 34:28
ultimately the same dynamics lie 34:30
>> what you will see is a lot of these like 34:31
small couple millionaire ARR businesses 34:33
um that might be distributed in this 34:36
somewhat novel way now that physicians 34:38
realize the productivity gains far 34:40
outweigh you know getting wrap on your 34:42
knuckles from compliance. It It's an 34:44
approach. The issue is is that the 34:47
number of companies, there's like 40 34:49
different ambient scribing companies. 34:50
They all hit like 100 200k in revenue 34:52
and then plateau out and then the next 34:54
kind of great wall that they hit is, you 34:56
know, there's probably a dozen of them 34:58
that got to a couple million in revenue 34:59
and then they all plateaued out as well. 35:00
It's not a venture business in my 35:02
opinion. Like a single point solution 35:04
unless you rapidly expand distribution 35:05
or you rapidly expand your platform, 35:07
it's not a venture scale business. I can 35:10
imagine then how you think about 35:11
counterpositioning to what might be many 35:12
new upstart companies thinking about 35:15
this like do you think of it as kind of 35:16
as long as we own revenue cycle 35:18
management you know these folks can 35:19
basically help us innovate on companies 35:21
on on new areas and basically you guys 35:23
would go acquire them 35:25
>> yeah our our strategy has been you know 35:26
bundle as much as possible in terms of 35:29
we think long term 35:31
>> it's kind of the original Microsoft 35:32
business model too 35:34
>> it is 100% the original Microsoft 35:35
business model and a great example is um 35:36
in the 80s there was a software that 35:39
came I'll call Grammatic and it was an a 35:40
word correcting software or like a 35:43
grammar checking software and you know 35:45
it ripped like it it really took off and 35:47
and it looked amazing. I think whatever 35:49
the equivalent of VCs were in the back, 35:52
you know, back then like were super 35:53
excited about the business like I'm sure 35:55
they raised a lot of money from a lot of 35:56
banks or whoever was funding them and 35:58
then Microsoft came out with autocorrect 36:00
as part of Word and this business just 36:04
died and and this will happen 36:06
unfortunately to a lot of these LLM 36:08
rapper businesses today and particularly 36:10
in healthcare. I think there's a whole 36:12
host of vanilla point solution scribing 36:14
companies that have developed and the 36:16
minute Epic turns on their own native 36:18
ambient scribe, those businesses will go 36:19
poof because they have no connection to 36:21
the, you know, revenue cycle, the 36:24
payment stack or anything more 36:25
meaningful than just that one layer. 36:27
>> And actually on on the note of Epic, I 36:28
mean, how do you think about 36:30
counterpositioning to them? I mean, 36:31
they're sort of the kings of 36:32
distribution in terms of healthcare, at 36:33
least for the last decade. 36:35
>> Presumably, you're trying to take their 36:36
crown. Um, but how do you think about 36:38
counterpositioning against their 36:42
existing distribution? 36:44
>> Everything I just said is exactly what 36:45
Epic would say about us. 36:46
>> Yeah, exactly. And so the the way that I 36:47
think about it is one of our core 36:50
company values is speed. And there are a 36:52
group of health systems in this country 36:54
who can't wait for Epic to build these 36:57
solutions for them over a multi-year 36:59
product roadmap. Uh I think the best 37:01
stat that I have here is there you know 37:03
the two best run health systems in the 37:05
country from a four you know from a 37:06
profitability standpoint are HCA which 37:08
is like 12 billion in free cash flow and 37:10
then tenant which is also billions in 37:13
free cash flow. Neither of these 37:14
companies are are on Epic. In fact they 37:16
avoid Epic like the plague. And the 37:18
reason is is that Epic often sucks out 37:20
all of the operating cash flow of the 37:22
academics and businesses that they work 37:24
with. You have these like multiundred 37:26
million dollar implementations. And the 37:28
the way that I see it is if you want to 37:30
be a fastmoving growing business, you 37:33
probably can't be on Epic because the 37:35
CIO's office becomes this captured asset 37:36
and they're just waiting for Epic to 37:39
release stuff or at least Epic can't be 37:40
central to your strategy. Maybe you use 37:42
them for your EMR, but you're you're 37:43
building the system of engagement and 37:45
other tools on top of it and around it. 37:47
Um, and and we aim to be that platform 37:49
for that system of engagement on top of 37:51
the EMR. 37:53
>> And it seems like you're innovating on a 37:53
very different go to market compared to 37:54
them, too. To your point, they're 37:56
probably going to the CIO's office. 37:57
That's right. You guys, it sounds like 37:58
experimenting with ways to go straight 38:00
to doctors and then kind of make your 38:01
way to the CIO's office from doctor 38:03
demand as opposed to from some large 38:04
enterprise deal that's forced on 38:06
everyone. 38:07
>> And ultimately, you have to earn the 38:08
trust of the CIO. There's no doubt about 38:09
that. But you can build a lot of 38:11
momentum and add a lot of value uh 38:13
through this physicianled adoption. You 38:16
know, even at our largest health system 38:17
partners, we have forward deployed 38:19
engineering teams that will sit and, you 38:21
know, just work with the medical 38:23
directors and the leading physicians in 38:25
that facility to try to make their day a 38:27
little easier. And that's it. That's all 38:29
their job is. 38:31
>> I mean, much like you and your 38:32
co-founder in the early days. 38:32
>> Exactly. We try to replicate what worked 38:34
in the in the early days into these 38:37
forward deployed pods and so far it's 38:38
yielded like we a lot of our net new 38:41
products and a lot of our net new 38:42
initiatives have come from that. Maybe 38:44
changing gears a little bit at the end 38:45
here is I'd love to just talk a little 38:47
bit about how you see the future of 38:49
healthcare broadly. I mean you obviously 38:51
have had a front row seat to both 38:52
participating in and shaping what this 38:55
field has looked like for the last 38:56
several years. Now on on the flip side 38:58
from from my perspective as a patient um 39:00
it feels like not a lot has changed from 39:02
my experience as a patient over the last 39:05
let's say 20 years. So, you know, if I 39:06
were to go to a doctor in 2005 versus 39:08
2015 versus today, 39:09
>> sure, more stuff is on a computer, but 39:11
kind of fundamentally I'm kind of 39:13
waiting for the same amount of time and 39:14
talking to more or less the same people 39:16
and maybe there's a couple new things, 39:17
but for the most part, it feels very 39:19
similar. One, do you think that's an 39:20
accurate characterization? And then 39:22
also, how do you think of the next 10 39:23
years? Like, do you think it's going to 39:24
look kind of similar for patients this 39:26
upcoming decade? 39:27
>> I I think for the most part, I I agree, 39:28
which is that the core of the experience 39:30
hasn't changed. I think we're starting 39:32
to see innovation now on the fringes and 39:34
that there's a lot of things that you 39:36
had to go in for that you can now do via 39:38
teleahalth visit. 39:40
>> Co sort of accelerated a lot of this 39:41
>> definitely accelerated a lot of that and 39:43
and that's great. I think 39:44
>> a system that is inherently supply 39:46
constraint the more that you can take 39:47
out of you know having to actually show 39:50
up at this facility and and and you know 39:51
wait for someone to see you the better 39:53
it is both for the system as well as for 39:55
the patient. Where I think we're 39:57
starting to see now uh rapid adoption is 39:59
the physician's life is starting to 40:02
actually become easier in that these 40:03
LLMs are saving them time provably, you 40:05
know, a couple hours every day. And 40:08
because of that, they're either going 40:10
to, you know, their panels will open up, 40:11
they'll be able to see more patients. So 40:13
getting an appointment with a specialist 40:15
hopefully starts feeling a little 40:16
easier, you know, moving forward. But 40:18
then number two, I think on the whole 40:20
these systems are starting to adopt AI 40:22
based solutions for things like their 40:24
front desk to assist with you know call 40:26
automation um the you know patient 40:28
engagement. We have a system that for 40:30
colonoscopy prep it's called engage. It 40:32
will send you a reminder and converse 40:35
with you based on the source material 40:36
and recommendation from the physician 40:38
and it boosts it and improves no-show 40:40
rates by 50%. um because the the prep 40:42
work is done and you know you don't end 40:45
up having to cancel the appointment last 40:46
minute because you messed something up 40:48
and and so those metrics are all moving 40:49
in the right direction. I think where 40:51
what healthcare should become with LLMs 40:53
in the next couple years is, you know, 40:55
you should get your most critical care 40:57
in a hospital or in a, you know, in 41:00
front of a physician where there really 41:02
is something like like, you know, phys 41:04
physiootherapy, like a P like a PT 41:05
actually taking care of you. Um, or 41:07
surgeon operating, 41:09
>> a surgeon or a deep complex diagnosis 41:10
that requires multiple tests in one day. 41:13
Those things should happen in in an 41:15
office. But with LLMs, more and more 41:16
care, I think can transition out of the 41:18
home with sensors that monitor the 41:20
patient, virtual care. Um, and and I 41:22
think that world is finally becoming 41:24
real. 41:25
>> And what do you see the transition in 41:26
that world looking like? I mean, there's 41:27
all these pretty deeply baked incentive 41:29
systems that incentivize bringing people 41:31
into the hospital even for relatively 41:33
small things cuz you have to bill for 41:35
it. To your point, a lot of the revenue 41:36
ultimately comes from RCM. Do you see 41:38
that the those sort of entrenched 41:40
financial motives actually preventing 41:43
that future from happening or do you see 41:45
that it's going to happen inevitably 41:47
just from like kind of this abundant 41:48
intelligence age we're we're entering? 41:50
>> I think it will happen inevitably from 41:51
you know this the abundance of 41:53
intelligence that's emerging. I think a 41:55
lot of your your fringe care will will 41:57
again just be things that patients can 41:59
do entirely on their own. And as a 42:01
result, health systems will be forced to 42:03
really specialize in in doing those high 42:05
margin, high dollar procedures that 42:07
they're uniquely good at. And because of 42:10
that specialization, I think the quality 42:12
of that care will improve as well. And 42:14
you know, you see things like intuitive 42:16
surgical and like robotic care actually 42:17
the fact that it's a thing in in in the 42:19
states is is is pretty remarkable. So I 42:21
think at the at the highest end of our 42:23
spectrum technology has in fact improved 42:24
quality of care meaningfully. There's 42:26
like new imunotherapies cleared every 42:28
year etc. And then at the very lowest 42:29
end of acuity in terms of basic 42:32
tellahalth that's improved as well. And 42:33
it's this kind of middle that's now 42:35
going to massive middle 42:36
>> by both by both sides. And hopefully 42:38
that the rate at which you know that 42:40
that middle gets compressed will be 42:42
fast. I mean one of the areas you see 42:43
the kind of big research labs most 42:45
excited about is you know like Microsoft 42:47
for example put out this thing called 42:49
medical super intelligence on the path 42:51
to medical super intelligence recently 42:53
and there's this sort of excitement 42:54
around the possibility of actually um in 42:56
many ways kind of replacing or or at 42:59
least very heavily augmenting but 43:01
ultimately fundamentally in the long 43:02
term replacing the kind of fundamental 43:04
kind of diagnostic process that a lot of 43:05
doctors do with 43:08
>> super intelligent AI systems you know 43:09
ones that could order tests and then 43:11
respond to feedback back and iteratively 43:13
iteratively work on those. I mean how do 43:14
you think about those? Like do you do do 43:16
you see that being as part of the 43:17
future? And also if that were you know 43:18
what do we need to do now to make that 43:20
future happen? Like what's kind of 43:22
missing in the current world to make 43:23
that happen? 43:25
>> When it comes to ordering or when it 43:25
comes to assessing a test and then 43:27
recommending a plan of care these models 43:29
will probably surpass humans and if they 43:31
have if not like already have have 43:33
surpassed humans. the the idea is that 43:35
just the way that our regulatory system 43:37
is set up from a malpractice standpoint, 43:39
litigation standpoint, a billing 43:41
standpoint, you probably still want a 43:43
responsible party, I think these health 43:45
systems will be the mega adopters of a 43:47
lot of these tools of intelligence 43:49
because it will probably help them from 43:51
a malpractice standpoint. If you can 43:53
point to a model has synthesized 43:55
millions of data points and come to this 43:57
conclusion and we are, you know, 43:59
basically going through its 44:01
recommendations, that's a way better 44:03
world than doctor kind of stuck his 44:05
finger in the air and guessed what was 44:06
happening. And so I I see physicians 44:08
embracing what we call these super 44:10
intelligent co-pilots that synthesize 44:12
information and and take action. You 44:14
will probably still for complex things 44:16
need to see the physician, get that 44:18
final assessment and then the speed and 44:20
accuracy at which you go from not 44:23
knowing what you have to then something 44:25
happening. I think that will get 44:27
compressed which is net good. The 44:28
reimbursement modalities, I'm I'm not 44:29
the world's biggest believer in this 44:31
like value based care world. And you 44:33
know, we've been talking about it for 44:36
like 15 years. I I just think there's 44:37
something about simple capitalism that 44:39
works well in America which is here's a 44:41
service here's a cost and you know we 44:43
will improve the accuracy with which we 44:46
render XYZ services and maybe that you 44:49
know that requires better auditing or 44:52
that requires these super intelligence 44:53
systems not recommending unnecessary or 44:55
incorrect medical procedures but this 44:57
procedure driven healthcare world seems 44:59
to work like America does have good 45:00
healthcare outcomes relative to the rest 45:02
of the world. 45:04
>> Yeah. And and perhaps, you know, if 45:04
there's significantly less unnecessary 45:06
care happening where people are able to 45:08
triage themselves. Yes. In conversation 45:10
with some sort of super intelligent 45:12
>> chat system or whatever that system 45:14
might be in the future with video and 45:16
with sensors and whatnot. 45:18
>> Perhaps that opens up the opportunity 45:20
for medical professionals to focus on 45:22
the cases where you can actually deliver 45:24
really great outcomes versus clogging up 45:25
ERS with people who don't need to be 45:27
there. 45:28
>> What 100%. 45:28
>> What kind of future do you think that 45:30
actually looks like 10 years from now 45:31
then? like do you see yourself do you 45:32
think we're going to go to the doctor 45:35
every year? Do you think we're going to 45:36
um only go when like we actually have a 45:38
catastrophic issue only or something in 45:40
between? 45:41
>> I I think in 10 years you're going to 45:41
have a lot you're going to have sensors 45:43
kind of built into the home. You're 45:45
going to have sensors that are you know 45:46
wearables on patients. The Apple Watch 45:48
and AirPods are becoming medical medical 45:50
devices very quickly. And that's a 45:52
that's a good thing because that passive 45:54
care where you know we can detect things 45:56
like aphib and you know detect spikes in 45:57
certain biomarkers is really good 46:00
because that's that's how you treat them 46:01
very very early. the concept of health 46:03
insurance and the concept of how care is 46:05
rendered is going to look a lot more 46:06
like how our cars are are handled in the 46:08
sense of like auto insurance 46:10
>> catastrophic insurance 46:12
>> catastrophic and and so when something 46:13
bad you break your arm you have cancer 46:15
or you have a you know very complex 46:16
disease there will be an insurance 46:18
mechanism and really your insurance will 46:20
be focused on that kind of care and then 46:22
I think the rest of the care it's 46:23
actually cheaper for it to be out of 46:25
pocket and for it to be you know outside 46:26
of the loop and complexity of the 46:28
insurance system where you can just get 46:30
a direct prescription or you you know 46:31
see a provider on teleahalth or even in 46:34
person for basic therapy um and because 46:35
the system will have shrunk and we have 46:38
deleted parts it will become a more 46:40
efficient system 46:42
>> and do you also see it reverting kind of 46:42
back to that version you said in the 80s 46:44
and 90s it was great to be a doctor so 46:45
>> do you see in many ways the sort of 46:47
consolidation we see happening in this 46:49
field will at least slow down and 46:50
perhaps even revert back to seeing more 46:52
people open private practices 46:53
>> I I really think so I I I would love a 46:54
world where the market cap of United 46:56
Health is you know a fifth 46:59
>> but every doctor is a millionaire Like 47:01
that is a good world for America because 47:03
patients are getting treated better. The 47:05
people that are actually rendering care 47:07
are where value is acrewing. It is 47:09
insane to me that if you think about it, 47:10
the most valuable healthcare company in 47:12
the country, what they effectively do is 47:14
like send you a plastic card in the mail 47:16
once a year. 47:17
>> Yes. There's, you know, it's the straw 47:18
man. There's more that they do, but 47:20
really at its core, that is your 47:21
interaction with Totally. 47:22
>> And and then being denied claims perhaps 47:24
>> and then denying claims and and so it is 47:26
it's an insane system. It needs to 47:28
change. Way too much value is accurate 47:29
that layer. And I think it needs to come 47:31
back to the physician. 47:33
>> D, maybe just to wrap things up, you 47:34
know, now you've you've been at this for 47:36
for quite a while. There's many new 47:37
founders excited about thinking about 47:39
this current technological moment in 47:40
healthcare and AI. You know, what advice 47:42
would you give them in terms of how to 47:43
compete with someone like you guys? Um, 47:45
but also how to build a business that 47:47
can endure and kind of capture this 47:49
current technological moment. I think 47:50
our biggest learning is get in front of 47:52
the customer and then just solve 47:54
problems for them and and start with one 47:56
specific problem even if regardless of 47:58
how small it looks. Our first you know 48:01
our initial TAM was laughable. It was a 48:02
100,000 patients in the entire country 48:05
but people and you know our investors 48:07
and our team and our you know early you 48:09
know founding engineers they took a bet 48:10
on us because they believed that we 48:12
could take the momentum from that to 48:14
build something even bigger. uh and and 48:15
so I would just say don't be afraid of 48:18
starting very small and very specific 48:20
because that is more valuable in the 48:22
long term than you know trying to build 48:24
a platform from right out the gates. The 48:26
other thing that I will say is some of 48:28
the best companies being founded right 48:30
now are folks that came from the palente 48:31
you know did a tour of duty six seven 48:34
years at a palunteer solve didn't have 48:36
to worry so much about distribution and 48:38
just solve problems for customers and 48:39
then saw that scale and learned about 48:41
the distribution um and so you know my 48:43
selfish pitch is like if you're building 48:45
in healthcare one of the fastest ways to 48:47
both become very wealthy is compound at 48:50
a company like Kamir and then also learn 48:52
these skills that you would otherwise 48:54
have to kind of learn denovo you know, 48:55
might take years in in order to amass. 48:58
>> Yeah, I totally agree. I mean, I think 49:00
one of the best ways to think about it 49:01
being becoming a great startup founder 49:03
is to work at another great startup, one 49:04
that's growing and one where you can get 49:06
exposure to customers. I think that kind 49:07
of forward deployed role you described 49:08
feels a lot like the experience of an 49:10
early founder, maybe with perhaps less 49:12
total independence, but a lot of the 49:14
same skill set that you might gain. 49:15
>> 100%. Yeah. 49:17
>> And ultimately focusing on making things 49:18
people want. Makes sense. 49:19
>> Yep. Make things people want. 49:20
>> Awesome. Thanks so much. Thanks for 49:22
joining us. Great. 49:23
>> Appreciate it. 49:24
[Music] 49:30

– English Lyrics

🎧 Learn and chill with "" – open the app to catch every cool phrase and structure!
By
Viewed
1,735
Language
Learn this song

Lyrics & Translation

[English]
I actually applied immediately. I got
rejected because I was in high school.
And then I applied again. I got rejected
again. And then the third time we came
armed with a prototype that actually
worked. The market is a great I mean
it's just like punch in the face. Like
it teaches you a lot like very quickly.
I think our biggest learning is get in
front of the customer and then just
solve problems for them and and start
with one specific problem regardless of
how small it looks. We went from having
no revenue to having 3 or 4 million in
revenue in like a year. And it was like
well we're done. like we solve all the
all the problems that are to solve and
then and you're like well no actually
the game starts now.
[Music]
>> I'm thrilled to be joined today by Tana
Tanden the CEO of Kamir. We're very
excited to have him because he's one of
the leading providers of enterprise
software to healthcare. Thanks so much
for joining us.
>> Thanks for having me.
>> Why don't we kick things off? Why don't
you tell me what Athellis is and what
are you guys working on?
>> Yeah. Uh, Athellis Camir builds software
products for providers and so we have
tools that automate their day-to-day
workflows like Camircribe which is an
ambient documentation tool revenue cycle
which is a payment stack. It's basically
Stripe for healthcare and doctors. It
submits their claims, uses LLMs to
negotiate denials with insurance
companies, appeal those denials, and
then really render all of the data viz
and business intelligence to run your
practice from a financial standpoint.
And then also a whole host of clinical
tools. come engage which does back
office and front office interactions
with the patient, explaining their bills
to them, uh explaining what types of
tasks they need to do to get prepared
for a procedure like a colonoscopy,
sending them appointment reminders, do
on the order of a couple billion dollars
worth of payments volume every year. Um,
help document using our ambient AI tool
20 million appointments every year and
then uh probably 150 million touch
points uh annually on on on our patient
engagement piece. um spread in large
health systems and private practices.
>> And so this is sort of a bundle of
pieces of software that are each solving
kind of independent problems for a
practice and collectively sort of serve
as the software operating system for
this entire practice.
>> That's right. And so you know our
solutions are used by the physicians and
the nurses in the practice or the
hospital and then also by the back
office. So your accountants, your
billing team, what we call revenue cycle
in healthcare. everything from uh you
know submitting the claim to actually
you know ledgering everything up for the
uh CFO's office
>> and you can actually do all of this with
technology today. You can have an AI
model that'll call up an insurance
company and negotiate with them and that
actually works
>> 100%. I mean I think the ability for
language models to both interact via
voice and text with humans and we just
got there a year ago and so we're just
at the precipice of what it can
accomplish. Um, and when you walk into a
health system, there are tens of
thousands of people whose sole job it is
to do these types of tasks. And if you
can free up their time, you can bring
that productivity back onto what matters
the most, which is patient care.
>> And I imagine a lot of those tasks are
already outsourced to some degree. So,
you're kind of just slotting in to where
they've already outsourced it to someone
else.
>> Exactly. They they use vendors like R1,
which is an offshoring RCM provider,
Axis, Omega. Many of them have their own
in-house shops where they actually, you
know, it's effectively outsourced, but
they actually have the individuals on
site and the the direction of the
industry for the last 20 years has been
offshoring. It works okay for what it's
worth. I mean, these became big
businesses, but I think LLM's there's an
opportunity to reimagine all of that
where it's it's pure software.
>> And this ultimately becomes a product
offering for all types of hospitals,
both small and large.
>> Yep. We work with the HCAS of the world
which is a hundred billion dollar
hospital empire you know 3,000 sites of
care 186 hospitals all the way down to
your private practice owned by a single
physician and you know they use varying
parts of the solution but it's provided
as one platform which is revenue cycle
workflow automation and patient
engagement in one
>> what does that actually mean like for
someone who's not in healthcare like
what do these roles actually look like
in terms of where technology fits into
them
>> yeah the way I think about it is the
physicians dayto-day day is really
defined as interacting with a patient
and treating that patient uh and then
often generating the relevant
documentation so that their back office
which is think of it like their
accounting team their AR team invoicing
can actually submit those claims to
insurance.
>> One of the challenges in healthcare is
the person paying for the for the
service is not the person receiving that
service. So a person paying as like an
insurance company or Medicare or
whatever receiving it is the patient
>> is the patient themselves and that
individual the beneficiary you know
their incentives are to get treated to
get treated fast to get the best
treatment in the world and often the
insurance company's incentive is to pay
out as little as possible and hopefully
treat as little as possible which is a
counter incentive to really what the
patient is trying to accomplish. And so
when it comes to then building
technology then you guys build
technology for all parts of this from
the patient experience itself as well as
the kind of front and back office
accounting and kind of administration of
that patient experience. We we see it as
you know there are two key protagonists
in our story which is the patients and
the providers and we build software
solutions and hardware solutions for
that group of individuals and there's an
effective enemy that's created as a
result which is the insurance company
and all of our tools are pointed at the
payers in in terms of trying to make
their lives harder and make the lives of
our customers easier.
>> Okay. Very interesting. Okay. I want to
dive into your technology, but before
that I'd love to hear a little bit about
the backstory of so why don't we rewind
the clock uh to the very early days like
how did this company come about? Like
what was the very early days like? Um
what was your experience in YC like and
kind of how did you even begin to arrive
at this idea that you're working on now?
So I I was very fortunate to have grown
up in the Bay Area and when you're in
the Bay Area, Y Cominator is just in the
ether like people like Casar and Justin
Khan and Sam Alman were like our heroes
and the I remember it was like 2013 or
2014 that we somehow snuck into YC
startup school because it was happening
in Certino. Um
>> I think I was there too actually also
sort of snuck into it.
>> It was a great start. I think Zuck came,
Jeff Dorsey was there.
>> Yep. Same one. Um, Flexport did their
interview on stage and I remember I was,
you know, I was like teenager in high
school. I was just in awe of of of these
people that had built such amazing
technology and YC is this ecosystem that
had enabled a lot of it uh and was
starting to enable more and more of it.
So, you know, fast forward a couple
years, Y Cominator hosted this hackathon
called YC hacks and uh I had read a
couple papers about how you could use
computer vision to potentially analyze
blood cells and also use really cheap
pieces of glass to enhance a smartphone
camera to basically turn into a
microscope.
>> So, this is like in 2016 or 174. 2014.
So, this is like early computer vision.
Like the deep learning is like just
starting to happen to some degree.
Computer vision is just barely starting.
the the models that we were using them
were like even like for for computer
vision were you know you're using like
segmentation algorithms like watershed
and like you know we like random forest
is what like were like the best models
for for often NLP and even in some task
in computer vision. And so armed with
those two pieces of information, I went
to YC hacks um and built this little
really hacked together smartphone camera
with a random force that had been
trained to classify malarial cells
versus non-malarial cells um based off
of a training set on the internet. And
it worked like pretty well like you
could you could segment these two. Um
and and then you know I was a senior in
high school at the time but it became my
science for project that year and I got
very obsessed with this this idea of man
we can use computer vision to automate a
task that someone like a pathologist a
very trained person is doing in in a in
a expensive laboratory and bring that
care directly to the patient um and
simplify the provider's life and that
eventually became a which was started as
a med device diagnostics company. Oh,
interesting. Okay. So, when you when you
applied to YC then, so this is shortly
after that, maybe a year or two after
you were a freshman in college or
something like that.
>> So, I actually applied immediately. I
got rejected because I was in high
school and and then I applied again. I
got rejected again. And then the third
time we came armed with a prototype that
actually worked. And it was after Id
spent about six months at Stanford and
you know the resources that you have
access to with the med school and the uh
you know in the the mechanical
engineering department like we were able
to put something pretty serious
together. Uh and that's when we got in
for summer 16.
>> And this was with a med device that was
doing some type of kind of image based
analysis of was it was this original
idea of like blood sample analysis?
>> That's right. So it was basically taking
a small volume of blood, turning it into
a monollayer, so you could see, you
know, single cells basically like
they're on a on a smear. Um, and then
basically a a microscope with an imager
attached to it, but was hacked in a way
that it was very uh large field of view
and still high resolution. And then we
trained computer vision algorithms to
recognize and segment those various
cells.
>> And so at this point, you know, your
background is primarily in computer
science. I assume you had some
experience in this application area in
biology in high school and early
college. You know, what gave you the
conviction to be like, I'm going to
presumably drop out of college, start
this company that is in a regulated
industry with medical devices. Like how
did you actually arrive at that
conviction? I
>> I would say two key sources. one my
co-founder Deepka who's also one of my
closest friends uh we used to compete in
science spheres against each other and
her research was always way more uh call
it med device or bioengineering focused
and she worked through high school on
this uh micrfluidic test strip that
could detect salmonella very quickly
from you know produce and you know I
thought it was remarkable that you could
build something like that in in high
school because it was you know was
hardware there was bio involved you have
to have a good understanding of you know
how these det protection strips were
actually fabbed and cut and whatnot. And
so it was clear that okay, we could
build things in the real world with uh
with micrfluidics. And then number two,
I think the, you know, when you're at
Stanford, you get to meet these amazing
professors. For me, Chris Manning was
was someone who gave me my first shot in
the Stanford AI lab under Richard
Socher, um, who started Metammind where
I was a research intern as well. And I
think they were just it was really
motivating because for them it was like
there's there's no boundaries to what
machine learning can do. you should go
after these complex industries. Um, and
they, you know, Richard was ended up
being the first check right after Y
Cominator 50K check and and I think that
support really encouraged us as well.
>> Yeah, totally. Okay. So, so let's now
talk about your time in YC. You know, at
this point it's just the two of you. Um,
you're working on this regulated medical
device. What did you set as kind of your
demo day goal and like how did you what
did you accomplish in those few months
of YC that ultimately then put you on a
trajectory to build something somewhat
different now from what you describe
now? We'll kind of talk about that that
transition. But yeah, what what did that
first few months look like?
>> I I think the first week itself of YC
was total shock because we came in with
these traditional timelines for how long
a med device should take or how long
anything in healthcare should take,
>> which is like years or something.
>> And and that seemed pretty good to me. I
was like, cool. Like we're going to be
on this for a long time. It's, you know,
we're going to go super slow. Remember I
had a conversation with with Casar, who
was our group partner and is also now on
our board. Um, and he, you know, he was
basically like, he made me walk through
every assumption on, well, why is that
months? That that just seems like it's
like a paperwork. You should be able to
do it in a week. Why are you waiting for
Stanford IRB to approve this trial where
you could go to some local lab and
probably get it done in a week? Uh, and
I think because of that, Deep and I sat
down and just like reimagined how
quickly you could build this stuff and
and really went from almost like
zerobased budgeting, but for a clinical
trial. And the other piece was, you
know, if you're a competitive person, in
our batch, we had companies like, you
know, Scale AI was in our batch and and
this was a company that pivoted mid
batch and got to like millions in
revenue by the end of the batch. You
know, for us, we never wanted to just be
the best healthcare company in the
batch. We wanted to be the best company
in the batch. And and so it was it was
this this pressure that we sort of
created for ourselves and that group
partners created that really caused us
to pace uh more aggressively than if we
were doing it outside of of of YC. And
so we set this goal of we will finish a
clinical trial and have a ready to go
FDA submission by the end of YC. Um and
it was crazy but we actually got the
clinical trial done. We needed to redo
some of the experiments per the FDA's
request. So the the approval itself took
a little longer, but we we we got the
the core basis of of the clinicals done
in those 10 weeks.
>> I mean, that's pretty absurd pace,
right? I mean, I think like when you
think about a normal regulated medical
device, we're talking about many years
in that process. And yeah, I mean, I
think this ability to kind of break down
into its only what the critical
components of it are, what parts you can
actually shortcut versus not is it's a
very challenging head space to get into.
And then you guys as as 19-year-olds, I
mean, I can only imagine some number of
people you talk to are like, "Who are
these guys to be making a medical
device?" Like, how do you go up against
that? Like, how did you get yourself to
not care? Basically,
>> we had many conversations where we got a
quote from Stanford where it was like,
"We can run this trial and it'll be
$120,000 and it will take 3 years."
>> And and I mean, when you see something
like that, it's almost so absurd that it
wheels you into action a little bit,
which is like, if this is the default
system, I mean, something is broken. and
and and I think um because of that we
thought to ourselves it's time to
rethink first principles and it really
came down to one identifying a partner
hospital that was small enough and
willing to work with us very quickly and
that ended up being in Huarez Mexico so
we flew out there mid batch uh ran the
trial with them number two is really
deleting as many parts as possible and
running the simplest form of the trial
so instead of hiring traditional
clinical trial operators deep and I ran
the trial ourselves she took samples in
the front room. I was in the back room
running them on the device. Uh, and then
we had a nurse that we had hired for the
day who was running them on the
traditional system called the
Sysmex5000.
And we would then compare those results
and show that they were accurate and and
equivalent to each other. And the whole
process from finding the hospital to
making sure the devices were ready to
actually running the trial and then
getting the results end to end was
probably 6 weeks of the batch. Once we
hit those milestones, that's when we
raised our seed round.
>> Okay. So you started there though. You
started with this medical device. Today
you're not a medical device company for
the most part at least or at all I
think. What was that arc like? I'm sure
there was many steps in which the
company changed. But maybe tell me a
little bit about how you segment your
brain into like the few eras of this
company and how you went from one of
these to perhaps pivoting to uh kind of
another version of that company over the
last few years. you know, we did YC, we
raised our seed round from Sequoia,
Alfred, um, over at Sequoia, and the
next 18 to 24 months just became brutal
focus on getting an FDA clearance. Um,
get the device to a state where it can
replicably run in in in clinical trials,
uh, where you can, you know, all kinds
of crazy tests like we have to drop the
device and kick the device and, you
know, things break and you have to be
able to continue to pass the the
relevant tests. And that was it. We were
laser focused on this one goal. And I
think that was very freeing in some ways
because it was the only thing we had to
get done. We also only had $3 million to
do it. Um, and you know, the the other
piece of it was to start proving out the
commercials. And that's when I started
engaging with uh what became our first
customer, which was actually a
pharmaceutical company that manufactured
a drug called Cloopene, which is a
refractory schizophrenia treatment that
causes neutropenia, white blood cell
count reduction as a side effect. And
you know, they told us, "We've been
dreaming about a device like this." and
and they signed that first million-doll
contract even before we had approval
just based off of the results of the
clinical. So, we had that commercial
proof. We had early clinics that were
adopting it. We were, you know, seeing
them use it and then we got the FDA
clearance and that was really this like
the first like epoch of the company the
first like two two and a half years.
>> Once we got that, you know, the the
market is a great I mean it's just like
punch in the face. Like it teaches you a
lot like very quickly.
>> You must have felt like you were on
cloud n then you're like, "Oh, we're
we're chilling. We we figured this out
now. Now we're going to go to the moon
with this." I I mean we got the
clearance and it was like well we're
done like we solved all the all the
problems that are to solve and then and
you're like well no actually the game
starts now and the exciting thing was
that we went from having no revenue to
having 3 or 4 million in revenue in like
a year. So as far as traditional series
A metrics and pacing like we were there.
The thing that we realized in parallel
was okay we can probably scale this
business to tens of millions in revenue
and build a business that a ro or an
Abbott or someone will buy for you know
200 million bucks or whatever that
number is like a good med device
outcome. At the same time we had this
team that we felt could run through
walls and had built machine learning
software had gone through regulatory
done the operations of device
manufacturing and we were in these
clinics like our devices were deployed
and we saw all kinds of problems.
>> So you got in there by deploying the
devices we were solving all sorts of
other problems they were facing and
along the way you discovered there's
this massive other set of problems that
you can solve too.
>> Yep. We we wanted to go from making
their lives easier for a percent of
their patients. So we were serving with
our athals one device to 100% of their
patients uh and their whole chronic care
panel with you know the teleahalth tools
and the revenue cycle tools. And and I
think you know my looking back the
reason this time period was so valuable
is we would not have had you know a
valuegiving relationship with these
customers had it not been for the
device. They trusted us. They saw us as
more than just a device company. They
saw us as those kids that would show up
in their office, set up the device,
train them how to use it. And because of
that, they would tell us about all these
other problems they had in their
clinics. Like, hey, when I get the
result from the device, I have to upload
it into this portal manually, and then I
have to call up a pharmacist and tell
them like, hey, the fax is coming
through. We would just hear these, you
know, these complaints like, well, it
would be amazing if I could, you know,
upload this automatically or if I could
fill this claim form out automatically
to get the next set of medication
adjudicated. And that's when we started
building software and it honestly felt
like playing on easy mode after two
years of building building hardware and
dealing with the FDA.
>> You know, at some point presumably the
software starts to take off and become a
pretty significant part of your
business. At at some point do you you
what is that process like of leaning in
on that and perhaps you know abandoning
the thing that or or at least leaning
out of the thing that has been your
initial driver that got you there in the
first place that has this big pharma
ideal for example. What does that
process look like? It was interesting
because we had two paths in front of us.
Be the best aellis swan medical device
company in the world and just you know
build a great compounding 40 50%
annualized grower in that in that
segment. Alternatively it was bet on
yourself again and expand the TAM and do
more for these customers um based on the
learnings we were getting from the
market.
>> And also when was this by the way?
>> This was in 2020. Um
>> so you've been at this now for like
fourish years. Like this has been your
thing. You're a med device company.
you're growing this thing and now 2020
is coming. A lot of things are happening
in the world uh as I'm sure is going to
be relevant here. And then also you're
starting to see that there's an
interesting new opportunity in software.
>> Yep. And I remember it was I forget was
it might have been Robin Hood or it
might have been some company. We had
this interesting uh fireside that we
went to and they talked a lot about
share of wallet and this concept of you
want to do more and more for your
consumer and go from just being you know
with Robin Hood like their toy stock
couple hundred bucks playing around to
like no this is like a meaningful
financial product for your entire
portfolio. For us, the the analogy was
was apt because we went we we wanted to
go from treating 1% of their patients,
these refractory schizophrenia patients
that were treatment resistant to
treating all their patients. And I
remember Deep, my co-founder, she was in
one of these clinics. She spent a lot of
time in these clinics and she was like,
"It's insane. We are helping them for 1%
of their patients and they love us so
much. Imagine if we could build tools
for all of their patients, their full
thousand patient panel." And and I think
that's when we took the bet. We're like,
we can build a multi-billion dollar
software business, sensor business in
this segment by expanding what we do for
these customers and and grow a lot
faster than the 100,000 total patients
that had this one condition.
>> And then this was before the LLM era was
really taking off. You were obviously a
machine learning company and you had a
lot of experience with building
software. Um, but like what did that
initial software look like? Like what
types of problems could you solve then?
Presumably now you can solve many more.
Yeah, we started with the basics which
is one uh co hit and and as a result our
providers needed ways to monitor their
patients in their homes. So we built a
basic telealth portal and a set of
remote monitoring devices that connected
into it and allowed them to interact
with those patients many of whom also
used the FLS1 device in the point of
care or in their homes. The very next
thing we started playing around with was
workflow automation as it related to
claim submission and payments. So
everything from collecting dollars from
these patients to uh you know starting
to submit claims to insurance and first
we did it just for or you know this
subset of remote monitoring and cloopine
patients and then expanded organically
to more and more of the practice
>> and and these are problems you basically
discovered from being in their offices
like you know you and your co-founder
are in there and you're noticing and
hearing from them about whatever other
problems they're facing and you're kind
of seeing okay like as exciting as this
is we sort of have to solve these as we
go.
>> Exactly. There is no other way to
discover these problems than being in
your customers dayto-day and and and
just seeing them because there's so much
nuance to where they get stuck and it's
not something you can derive you know by
reading an article or you know watching
a video online. You you have to be in
the in the heat of things.
>> Yeah, totally. I mean I think we see
this with with companies every day today
especially in this sort of new
technological moment is that it's very
hard to conceive of great startup ideas
kind of in your home or in a lab. It's
much more likely to encounter them
somewhere in the field by being in
there. And so for you guys that sort of
was a was a game changer in putting you
in that place.
>> 100%.
>> Well, okay. Well, why don't we, you
know, kind of move forward now a little
bit to to today and and get there by
kind of talking about what the last few
years has looked like in healthcare
generally. I mean, there's been an
incredible amount of changes happening
in healthcare. To your point, there's
these massive mega conglomerate style
hospital businesses. There's
consolidation in payers and PBMs. for
you guys as you see this sort of
changing landscape where do you one
where do you fit into that landscape and
then also how does that changing
landscape affect your business and as
you think about growing it
>> I I think it's it's it's really
interesting is if you go back to the
'90s uh the life of a physician was
great they had a tight panel of patients
they knew them personally they treated
them and if there was you know chronic
diseases they were able to talk to the
patient very quickly idea of a concierge
doctor was was fairly common you know
anyone in upper middle middle class had
a concierge doctor of some kind. And as
the bloat that came from insurance and
regulation and and and just what we
turned healthcare into into this sort of
like admin state
>> is what really broke down the
productivity of a physician where they
turned into these these, you know, cogs
and this greater wheel and there's, you
know, patient productivity numbers they
have to hit. There's countless tasks
they have to do. regardless of how
efficient they are, they always take
documentation home and they're filling
out paperwork. And I see it as this
great misuse of of talent in that we
have some of the most intelligent,
well-trained, uh, uh, well-intentioned
people in the country spending their
time doing tasks that really software
should be doing for them. Uh, LLMs are
not. And what we've seen happen is a lot
of physicians give up on this dream of
the private practice or the
physician-owned practice in change for
joining a large health system that does
take on a lot of the overhead that you
now need to pay in order to just operate
a health system.
>> This is like negotiating with insurance
companies and with PBMs and having uh
farmer relationships and all that kind
of stuff,
>> paying for an EMR, dealing with
malpractice. And so all of this made it
harder to practice care and and and
turned it more into this again like this
admin business. And and I think now with
LLMs, there's this generational
opportunity to free the physician and
and really bring them back to what they
love doing the most, which is rendering
care. And I think our work is in service
of that. Uh take the work tax and just
nuke it. take every part of their
revenue cycle, their back office, their
documentation, um, and and use software
to automate, uh, large chunks of that.
>> And I mean, you guys sell to, you know,
both this mid-market and larger market
or or any kind of enterprise market.
It feels like what you're saying here is
that this midm market is what you see as
potentially best suited to take
advantage of of LLM and especially sort
of this broader technological adoption
because it frees them from needing to
consolidate into these bigger
enterprises and perhaps the advantage of
the bigger enterprises won't be as much
the case in the future. Is that kind of
how you see it or do you think not so
much?
>> I I I think it goes both ways. one I
think we will see it's sort of the
analogy we use is like Amazon and
Shopify where over the last 20 years or
10 years or whatever time period Amazon
has grown remarkably um as it's you know
taken a lot of share from traditional
retail and also expanded what we order
online but then Shopify has exploded as
well as more people are able to start
their own businesses and I think you
will have this aspect of the physician
who practices in a health system but
then also has their own practice um and
chooses their hours and because of the
fact that software is automating more
and more of their day, they can see more
patients and do it in in a way that is
sustainable and gives them energy as
opposed to drains them out by the end of
the day.
>> Yeah. So, let's talk about that a little
bit in terms of software automating more
and more of their day. There's been a
lot of software adoption in healthcare
over the last 10 years. Most of it
through electronic health records and,
you know, kind of payment portals with
insurance and whatnot. Um, but a lot of
it has been promised to doctors as
saving them time or helping patients in
various ways over the last decade. But
the critique has often been that well,
it's not really been about that. It's
been about getting paid for care. It's
been about billing mostly and not
actually about care. How do you see what
that technological adoption story looks
like over the last decade and then over
this next decade? Like what are things
you think are going to be fundamentally
different about this technological
moment? It's it's definitely true
because a lot of the digitization and
creation of EMRs came from a place of
compliance and a place of of billing and
institutionalizing a lot of regulatory
requirements as opposed to true you know
unleashing the doctor. You know do Dr.
classical who's one of our uh you know
he used to run Thomas Jefferson
University the health system um you know
he calls this the epidemic which is like
there's just this proliferation of of
work tax in every organ in the country
in IT departments in you know in the
physicians day-to-day and it didn't
solve the problem it set out to solve
because the software was built from the
perspective of the CIO's office and the
CFO's office
>> who are optimized around getting paid
basically.
>> Exactly. optimized around getting paid
and not getting sued and and those are
the you know the two the two drivers you
know the CLLO's office as well now I
think you're seeing a lot of
physician-driven adoption of these tools
one postco we really stress the system
out we we burnt we burnt out our
physicians or burnt out our nurses and
there's almost no option but for them to
use these tools uh uh and and and push
for the adoption of these tools in order
to just keep up with their with their
day-to-day patient volumes our loudest
advocates even in largest health systems
are physicians.
>> Well, this is really fascinating. That
feels like a huge difference, right? I
imagine in selling the first version of
EHRs five or six years ago, you're Yeah.
largely selling to central IT teams,
CIOS, that type of thing. Here, you're
saying today when you approach selling
your recent software, it's an individual
doctor who's your advocate.
>> 100%. We have we have a self-s serve
ambient documentation tool called
Scribe. And
>> yeah, how does that work actually? Can
you tell us a bit about that?
>> I would say it's one of the explosions
in software categories recently. You've
probably had in terms of like really
fast LLM adoption, I think you've had
coding tools like the winds surfs and
the cursors of the world and then you
you've had ambient documentation tools
um in the in the healthcare world. And
ambient documentation listens to the
conversation that a patient and a
physician have. It summarizes that and
then it generates all of the
documentation based on being trained on
previous approvals, previous pieces of
documentation and basically hands it off
to the revenue cycle teams ready to go.
>> It's like a perfect problem for LM. This
thing LM would be really good.
>> It's a perfect problem for LM. You have
transcription, you have summarization,
you have, you know, references and
citations back to clinical source
material all in this one, you know, one
set of models. Uh, and that tool, we
went from 2023 doing maybe 100,000
appointments through that tool to this
year, we'll probably do 20 to 25 million
appointments through that tool. There's
a self-s serve motion that has gone from
last year zero appointments to this year
5 million appointments. Um,
>> self-s serve motion as in you don't go
through the hospital IT team at It's a
physician finds it online. Uh we
advertise directly to them. They sign up
often paying with their own credit card.
Um
>> that seems new.
>> It seems crazy. I mean I was shocked
when when we saw this working. Uh it was
this is not behavior you've seen in
healthcare before.
>> And from that we you know we then go
upsell almost like Slack or Dropbox or
one of these traditional software tools
the whole enterprise where we pitch the
integrations into their EMR the whole
workflow tool. Um, and that's been a
massive, you know, source of of of
expansion for us.
>> If I'm a founder, you know, I might be
thinking, well, isn't it going to be
really annoying in terms of HIPPA and in
terms of all these rules and whatnot in
terms of actually
>> getting a doctor to sign up? Like, it's
not even intuitive to me that a doctor
is allowed to self-sign up for this type
of thing. How do you guys think about
that? Is that has something changed that
makes it easy or was it never actually
as hard as people thought?
>> It's a good question. And I think
there's definitely a lot of compliance
departments in hospitals that are very
much against self- adopted software, but
the productivity gains are so great that
it's happening one way or another. Um,
and the options that a compliance
department at a hospital has is either,
you know, sign up and make this part of
the institution or, you know, tell your
physicians to continue being burnt out.
And usually they're picking the one that
that ends up with happier physicians.
You know, there are totally ways for
there to be HIPPA compliant self-s
served tools. Now, that might defy the
individual policies of a of a private
institution like like a hospital itself,
but from a pure HIPO compliance
standpoint, right?
>> It's not actually a legal risk. It's
just the hospital's own compliance.
>> It's their own internal policies.
>> Yeah. And so, what does it actually look
like in terms of other technological
problems you face? Like what are some
>> maybe just diving into some technical
challenges? Yeah. Um I can imagine for
something like scribing at least to me
intuitively that seems relatively
straightforward as a technical challenge
but perhaps at that scale actually not
so much whether in that one or in some
of the other products you guys have what
are some of the hardest technical
problems you guys face in actually
making software here especially for a
company that is selling to healthcare as
opposed to any other enterprise SAS
company
>> in just the case of scribing simple at
first glance but when you scale you know
you're dealing with millions of hours of
audio that is often being uploaded over
shaky networks in the basement of doc in
you know a hospital in a lab you know
pharmacy that's a you know freestanding
part of a freestanding clinic in rural
America so you have to build great
offline mode and you know retention and
and and the ability to you know upload
these things silently in the background
and all these like traditional
challenges that consumer apps have
solved I think are now being solved in
healthcare as well. Number two, you
know, we process billions of dollars
worth of claims volume every year in our
revenue cycle business. And as part of a
revenue cycle is it's stripe for
healthcare, right? You're the interface
between the physician and the payer and
the payers at a 100 blocks that make it
hard to get paid. Everything from losing
the claim to, you know, not telling you
that it was denied for a couple weeks so
you don't hit your, you know, so you hit
your timely filing limit and then can't
get paid anymore. We've built models
that are constantly checking for all of
these threats. Uh I almost see it as
like a like a cyber security problem.
Every denial is is something broke or
this is the payer trying to attack the
physician. We have to debug what went
wrong and help the physician get paid
out. A good example is all these payers
have APIs now, right?
>> They just work 80% of the time. What
what that means is is that you might get
responses that are, you know, missing
some of the adjudication or there's a
there's a secondary insurance that needs
to pay out and then you need to go
separately hit that secondary insurance
or these two insurance companies aren't
talking to each other and they both got
a medical record but are claiming they
didn't and you have to show them that
audit trail. And so the technical
challenges are are very interesting
because you're doing this at scale and
you need to monitor these processes
constantly. Um but when you solve them,
physicians win, which is very exciting.
>> Yeah. And especially today if they are
your advocates. I mean I think you get
this even I imagine much faster sales
motion than probably in the early days
where if you can show them these
technical solutions and they can
actually advocate and like get your
thing incorporated into their hospital.
I mean that's huge for you guys.
>> I mean for our revenue cycle business
the word of mouth is literally my
revenue went up by 15%. And that is the
most potent word of mouth in in the
world and that's why we're seeing that
business scale so quickly. Um, I think
in our ambient business, the word of
mouth is I save two hours every day and
I did it with this free tool that I
found online and if I want to get it
integrated, it's, you know, like a
hundred bucks a month or whatever the
price is. So that that's to me why why
why I think these tools are spreading so
quickly now.
>> And how do you think about yourself in
terms of a the types of software you
guys have? You know, you call yourself
sort of a compound software company,
sort of a rippling for healthcare as
we've talked about in the past.
>> What's the basis for that strategy? you
know, how do you guys think about growth
and why grow this way versus doubling
down on one of these and trying to make
that be a massive business in itself? I
>> I think the complexities of healthcare
and the way that people get paid in
healthcare and really where the
operating cash flow lies really make it
like you can only really build a hundred
billion dollar business in healthcare as
a platform company. That being said, you
have to start as a point solution. We
started as a med device and then
eventually turned into this again a
point solution for a very specific
subset of claims and then over time
turned into this platform. Uh but now
that we're this platform, we also have
amazing distribution unlocks. We get to
work with General Catalyst and their
health assurance framework. They have 40
health systems that are all signed up.
HCA is on our board. It's hundred
billion dollar hospital empire. And so I
think in the same way that in the 2010s,
Palunteer solved distribution and
defense and a lot of call it like
Fortune 100 uh use cases and then just
aggregated smart people to go work on
crazy problems. We're doing that in
healthcare. The hardest problem in
healthcare having now spent eight nine
years in it is distribution and you can
reinvent the distribution wheel over
eight nine years for yourself or you can
go build you know effectively point
solutions as part of this platform um
and not worry about the revenue engine
because the backend revenue cycle has
that covered
>> right as long as you ultimately have
revenue cycle management at some part of
your platform. Exactly. Kind of works.
>> Exactly. I mean do you think that
changes now in this era of kind of
doctorled advocacy of acquiring software
you know if if for example it is much
easier for hospitals to acquire software
than ever before especially smaller
clinics does that change the calculus
there at all or do you think uh
ultimately the same dynamics lie
>> what you will see is a lot of these like
small couple millionaire ARR businesses
um that might be distributed in this
somewhat novel way now that physicians
realize the productivity gains far
outweigh you know getting wrap on your
knuckles from compliance. It It's an
approach. The issue is is that the
number of companies, there's like 40
different ambient scribing companies.
They all hit like 100 200k in revenue
and then plateau out and then the next
kind of great wall that they hit is, you
know, there's probably a dozen of them
that got to a couple million in revenue
and then they all plateaued out as well.
It's not a venture business in my
opinion. Like a single point solution
unless you rapidly expand distribution
or you rapidly expand your platform,
it's not a venture scale business. I can
imagine then how you think about
counterpositioning to what might be many
new upstart companies thinking about
this like do you think of it as kind of
as long as we own revenue cycle
management you know these folks can
basically help us innovate on companies
on on new areas and basically you guys
would go acquire them
>> yeah our our strategy has been you know
bundle as much as possible in terms of
we think long term
>> it's kind of the original Microsoft
business model too
>> it is 100% the original Microsoft
business model and a great example is um
in the 80s there was a software that
came I'll call Grammatic and it was an a
word correcting software or like a
grammar checking software and you know
it ripped like it it really took off and
and it looked amazing. I think whatever
the equivalent of VCs were in the back,
you know, back then like were super
excited about the business like I'm sure
they raised a lot of money from a lot of
banks or whoever was funding them and
then Microsoft came out with autocorrect
as part of Word and this business just
died and and this will happen
unfortunately to a lot of these LLM
rapper businesses today and particularly
in healthcare. I think there's a whole
host of vanilla point solution scribing
companies that have developed and the
minute Epic turns on their own native
ambient scribe, those businesses will go
poof because they have no connection to
the, you know, revenue cycle, the
payment stack or anything more
meaningful than just that one layer.
>> And actually on on the note of Epic, I
mean, how do you think about
counterpositioning to them? I mean,
they're sort of the kings of
distribution in terms of healthcare, at
least for the last decade.
>> Presumably, you're trying to take their
crown. Um, but how do you think about
counterpositioning against their
existing distribution?
>> Everything I just said is exactly what
Epic would say about us.
>> Yeah, exactly. And so the the way that I
think about it is one of our core
company values is speed. And there are a
group of health systems in this country
who can't wait for Epic to build these
solutions for them over a multi-year
product roadmap. Uh I think the best
stat that I have here is there you know
the two best run health systems in the
country from a four you know from a
profitability standpoint are HCA which
is like 12 billion in free cash flow and
then tenant which is also billions in
free cash flow. Neither of these
companies are are on Epic. In fact they
avoid Epic like the plague. And the
reason is is that Epic often sucks out
all of the operating cash flow of the
academics and businesses that they work
with. You have these like multiundred
million dollar implementations. And the
the way that I see it is if you want to
be a fastmoving growing business, you
probably can't be on Epic because the
CIO's office becomes this captured asset
and they're just waiting for Epic to
release stuff or at least Epic can't be
central to your strategy. Maybe you use
them for your EMR, but you're you're
building the system of engagement and
other tools on top of it and around it.
Um, and and we aim to be that platform
for that system of engagement on top of
the EMR.
>> And it seems like you're innovating on a
very different go to market compared to
them, too. To your point, they're
probably going to the CIO's office.
That's right. You guys, it sounds like
experimenting with ways to go straight
to doctors and then kind of make your
way to the CIO's office from doctor
demand as opposed to from some large
enterprise deal that's forced on
everyone.
>> And ultimately, you have to earn the
trust of the CIO. There's no doubt about
that. But you can build a lot of
momentum and add a lot of value uh
through this physicianled adoption. You
know, even at our largest health system
partners, we have forward deployed
engineering teams that will sit and, you
know, just work with the medical
directors and the leading physicians in
that facility to try to make their day a
little easier. And that's it. That's all
their job is.
>> I mean, much like you and your
co-founder in the early days.
>> Exactly. We try to replicate what worked
in the in the early days into these
forward deployed pods and so far it's
yielded like we a lot of our net new
products and a lot of our net new
initiatives have come from that. Maybe
changing gears a little bit at the end
here is I'd love to just talk a little
bit about how you see the future of
healthcare broadly. I mean you obviously
have had a front row seat to both
participating in and shaping what this
field has looked like for the last
several years. Now on on the flip side
from from my perspective as a patient um
it feels like not a lot has changed from
my experience as a patient over the last
let's say 20 years. So, you know, if I
were to go to a doctor in 2005 versus
2015 versus today,
>> sure, more stuff is on a computer, but
kind of fundamentally I'm kind of
waiting for the same amount of time and
talking to more or less the same people
and maybe there's a couple new things,
but for the most part, it feels very
similar. One, do you think that's an
accurate characterization? And then
also, how do you think of the next 10
years? Like, do you think it's going to
look kind of similar for patients this
upcoming decade?
>> I I think for the most part, I I agree,
which is that the core of the experience
hasn't changed. I think we're starting
to see innovation now on the fringes and
that there's a lot of things that you
had to go in for that you can now do via
teleahalth visit.
>> Co sort of accelerated a lot of this
>> definitely accelerated a lot of that and
and that's great. I think
>> a system that is inherently supply
constraint the more that you can take
out of you know having to actually show
up at this facility and and and you know
wait for someone to see you the better
it is both for the system as well as for
the patient. Where I think we're
starting to see now uh rapid adoption is
the physician's life is starting to
actually become easier in that these
LLMs are saving them time provably, you
know, a couple hours every day. And
because of that, they're either going
to, you know, their panels will open up,
they'll be able to see more patients. So
getting an appointment with a specialist
hopefully starts feeling a little
easier, you know, moving forward. But
then number two, I think on the whole
these systems are starting to adopt AI
based solutions for things like their
front desk to assist with you know call
automation um the you know patient
engagement. We have a system that for
colonoscopy prep it's called engage. It
will send you a reminder and converse
with you based on the source material
and recommendation from the physician
and it boosts it and improves no-show
rates by 50%. um because the the prep
work is done and you know you don't end
up having to cancel the appointment last
minute because you messed something up
and and so those metrics are all moving
in the right direction. I think where
what healthcare should become with LLMs
in the next couple years is, you know,
you should get your most critical care
in a hospital or in a, you know, in
front of a physician where there really
is something like like, you know, phys
physiootherapy, like a P like a PT
actually taking care of you. Um, or
surgeon operating,
>> a surgeon or a deep complex diagnosis
that requires multiple tests in one day.
Those things should happen in in an
office. But with LLMs, more and more
care, I think can transition out of the
home with sensors that monitor the
patient, virtual care. Um, and and I
think that world is finally becoming
real.
>> And what do you see the transition in
that world looking like? I mean, there's
all these pretty deeply baked incentive
systems that incentivize bringing people
into the hospital even for relatively
small things cuz you have to bill for
it. To your point, a lot of the revenue
ultimately comes from RCM. Do you see
that the those sort of entrenched
financial motives actually preventing
that future from happening or do you see
that it's going to happen inevitably
just from like kind of this abundant
intelligence age we're we're entering?
>> I think it will happen inevitably from
you know this the abundance of
intelligence that's emerging. I think a
lot of your your fringe care will will
again just be things that patients can
do entirely on their own. And as a
result, health systems will be forced to
really specialize in in doing those high
margin, high dollar procedures that
they're uniquely good at. And because of
that specialization, I think the quality
of that care will improve as well. And
you know, you see things like intuitive
surgical and like robotic care actually
the fact that it's a thing in in in the
states is is is pretty remarkable. So I
think at the at the highest end of our
spectrum technology has in fact improved
quality of care meaningfully. There's
like new imunotherapies cleared every
year etc. And then at the very lowest
end of acuity in terms of basic
tellahalth that's improved as well. And
it's this kind of middle that's now
going to massive middle
>> by both by both sides. And hopefully
that the rate at which you know that
that middle gets compressed will be
fast. I mean one of the areas you see
the kind of big research labs most
excited about is you know like Microsoft
for example put out this thing called
medical super intelligence on the path
to medical super intelligence recently
and there's this sort of excitement
around the possibility of actually um in
many ways kind of replacing or or at
least very heavily augmenting but
ultimately fundamentally in the long
term replacing the kind of fundamental
kind of diagnostic process that a lot of
doctors do with
>> super intelligent AI systems you know
ones that could order tests and then
respond to feedback back and iteratively
iteratively work on those. I mean how do
you think about those? Like do you do do
you see that being as part of the
future? And also if that were you know
what do we need to do now to make that
future happen? Like what's kind of
missing in the current world to make
that happen?
>> When it comes to ordering or when it
comes to assessing a test and then
recommending a plan of care these models
will probably surpass humans and if they
have if not like already have have
surpassed humans. the the idea is that
just the way that our regulatory system
is set up from a malpractice standpoint,
litigation standpoint, a billing
standpoint, you probably still want a
responsible party, I think these health
systems will be the mega adopters of a
lot of these tools of intelligence
because it will probably help them from
a malpractice standpoint. If you can
point to a model has synthesized
millions of data points and come to this
conclusion and we are, you know,
basically going through its
recommendations, that's a way better
world than doctor kind of stuck his
finger in the air and guessed what was
happening. And so I I see physicians
embracing what we call these super
intelligent co-pilots that synthesize
information and and take action. You
will probably still for complex things
need to see the physician, get that
final assessment and then the speed and
accuracy at which you go from not
knowing what you have to then something
happening. I think that will get
compressed which is net good. The
reimbursement modalities, I'm I'm not
the world's biggest believer in this
like value based care world. And you
know, we've been talking about it for
like 15 years. I I just think there's
something about simple capitalism that
works well in America which is here's a
service here's a cost and you know we
will improve the accuracy with which we
render XYZ services and maybe that you
know that requires better auditing or
that requires these super intelligence
systems not recommending unnecessary or
incorrect medical procedures but this
procedure driven healthcare world seems
to work like America does have good
healthcare outcomes relative to the rest
of the world.
>> Yeah. And and perhaps, you know, if
there's significantly less unnecessary
care happening where people are able to
triage themselves. Yes. In conversation
with some sort of super intelligent
>> chat system or whatever that system
might be in the future with video and
with sensors and whatnot.
>> Perhaps that opens up the opportunity
for medical professionals to focus on
the cases where you can actually deliver
really great outcomes versus clogging up
ERS with people who don't need to be
there.
>> What 100%.
>> What kind of future do you think that
actually looks like 10 years from now
then? like do you see yourself do you
think we're going to go to the doctor
every year? Do you think we're going to
um only go when like we actually have a
catastrophic issue only or something in
between?
>> I I think in 10 years you're going to
have a lot you're going to have sensors
kind of built into the home. You're
going to have sensors that are you know
wearables on patients. The Apple Watch
and AirPods are becoming medical medical
devices very quickly. And that's a
that's a good thing because that passive
care where you know we can detect things
like aphib and you know detect spikes in
certain biomarkers is really good
because that's that's how you treat them
very very early. the concept of health
insurance and the concept of how care is
rendered is going to look a lot more
like how our cars are are handled in the
sense of like auto insurance
>> catastrophic insurance
>> catastrophic and and so when something
bad you break your arm you have cancer
or you have a you know very complex
disease there will be an insurance
mechanism and really your insurance will
be focused on that kind of care and then
I think the rest of the care it's
actually cheaper for it to be out of
pocket and for it to be you know outside
of the loop and complexity of the
insurance system where you can just get
a direct prescription or you you know
see a provider on teleahalth or even in
person for basic therapy um and because
the system will have shrunk and we have
deleted parts it will become a more
efficient system
>> and do you also see it reverting kind of
back to that version you said in the 80s
and 90s it was great to be a doctor so
>> do you see in many ways the sort of
consolidation we see happening in this
field will at least slow down and
perhaps even revert back to seeing more
people open private practices
>> I I really think so I I I would love a
world where the market cap of United
Health is you know a fifth
>> but every doctor is a millionaire Like
that is a good world for America because
patients are getting treated better. The
people that are actually rendering care
are where value is acrewing. It is
insane to me that if you think about it,
the most valuable healthcare company in
the country, what they effectively do is
like send you a plastic card in the mail
once a year.
>> Yes. There's, you know, it's the straw
man. There's more that they do, but
really at its core, that is your
interaction with Totally.
>> And and then being denied claims perhaps
>> and then denying claims and and so it is
it's an insane system. It needs to
change. Way too much value is accurate
that layer. And I think it needs to come
back to the physician.
>> D, maybe just to wrap things up, you
know, now you've you've been at this for
for quite a while. There's many new
founders excited about thinking about
this current technological moment in
healthcare and AI. You know, what advice
would you give them in terms of how to
compete with someone like you guys? Um,
but also how to build a business that
can endure and kind of capture this
current technological moment. I think
our biggest learning is get in front of
the customer and then just solve
problems for them and and start with one
specific problem even if regardless of
how small it looks. Our first you know
our initial TAM was laughable. It was a
100,000 patients in the entire country
but people and you know our investors
and our team and our you know early you
know founding engineers they took a bet
on us because they believed that we
could take the momentum from that to
build something even bigger. uh and and
so I would just say don't be afraid of
starting very small and very specific
because that is more valuable in the
long term than you know trying to build
a platform from right out the gates. The
other thing that I will say is some of
the best companies being founded right
now are folks that came from the palente
you know did a tour of duty six seven
years at a palunteer solve didn't have
to worry so much about distribution and
just solve problems for customers and
then saw that scale and learned about
the distribution um and so you know my
selfish pitch is like if you're building
in healthcare one of the fastest ways to
both become very wealthy is compound at
a company like Kamir and then also learn
these skills that you would otherwise
have to kind of learn denovo you know,
might take years in in order to amass.
>> Yeah, I totally agree. I mean, I think
one of the best ways to think about it
being becoming a great startup founder
is to work at another great startup, one
that's growing and one where you can get
exposure to customers. I think that kind
of forward deployed role you described
feels a lot like the experience of an
early founder, maybe with perhaps less
total independence, but a lot of the
same skill set that you might gain.
>> 100%. Yeah.
>> And ultimately focusing on making things
people want. Makes sense.
>> Yep. Make things people want.
>> Awesome. Thanks so much. Thanks for
joining us. Great.
>> Appreciate it.
[Music]

Key Vocabulary

Start Practicing
Vocabulary Meanings

prototype

/ˈprəʊtətaɪp/

B2
  • noun
  • - an early sample or model of a product used to test a concept

revenue

/ˈrevənjuː/

B2
  • noun
  • - income generated from normal business activities

automation

/ˌɔːtəˈmeɪʃən/

C1
  • noun
  • - use of technology to perform tasks without human intervention

clinical

/ˈklɪnɪkəl/

B2
  • adjective
  • - relating to the observation and treatment of actual patients

diagnosis

/ˌdaɪəɡˈnoʊsɪs/

B2
  • noun
  • - identification of the nature of an illness or problem

technology

/tekˈnɒlədʒi/

B2
  • noun
  • - the application of scientific knowledge for practical purposes

model

/ˈmɒdəl/

B2
  • noun
  • - a simplified representation used to explain or predict something

claims

/kleɪmz/

B2
  • noun
  • - requests for payment submitted to an insurer

billing

/ˈbɪlɪŋ/

B2
  • noun
  • - the process of preparing and sending invoices

workflow

/ˈwɜːrkfloʊ/

C1
  • noun
  • - a sequence of steps needed to complete a task

engagement

/ɪnˈɡeɪdʒmənt/

C1
  • noun
  • - active participation or involvement, especially of users or customers

platform

/ˈplætˌfɔːrm/

B2
  • noun
  • - a base of technologies that allows other applications to run

innovation

/ˌɪnəˈveɪʃən/

C1
  • noun
  • - the introduction of new ideas, methods or products

scaling

/ˈskeɪlɪŋ/

C1
  • noun
  • - the process of increasing a system’s capacity to handle more work

distribution

/ˌdɪstrɪˈbjuːʃən/

C1
  • noun
  • - the act of delivering products or services to users

adoption

/əˈdɒpʃən/

C1
  • noun
  • - the act of starting to use a new technology or practice

iteration

/ˌɪtərˈeɪʃən/

C1
  • noun
  • - repeating a process in order to improve a product or result

deployment

/dɪˈplɔɪmənt/

C1
  • noun
  • - the act of putting a system or software into active use

analytics

/ˌænəˈlɪtɪks/

C1
  • noun
  • - the systematic analysis of data or statistics

compliance

/kəmˈplaɪəns/

C1
  • noun
  • - conforming to rules, standards, or laws

Do you remember what “prototype” or “revenue” means in ""?

Hop into the app to practice now – quizzes, flashcards, and native-like pronunciation are waiting!

Key Grammar Structures

  • I actually applied immediately. I got rejected because I was in high school.

    ➔ Past Simple (Passive Voice)

    ➔ Use of the past simple passive voice to indicate that the subject (I) was the recipient of the action (rejected). "I **got rejected**" shows that something was done *to* the subject.

  • The market is a great I mean it's just like punch in the face. Like it teaches you a lot like very quickly.

    ➔ Simile

    ➔ Use of the simile "**like a punch in the face**" to vividly describe the harsh and impactful nature of the market's lessons.

  • I think our biggest learning is get in front of the customer and then just solve problems for them and and start with one specific problem regardless of how small it looks.

    ➔ Imperative Mood

    ➔ Use of the imperative mood to give direct advice or instructions. "**Get** in front of the customer," "**solve** problems," "**start** with one specific problem" are all direct commands.

  • We went from having no revenue to having 3 or 4 million in revenue in like a year.

    ➔ Gerunds

    ➔ Use of gerunds ("**having** no revenue" and "**having** 3 or 4 million") as objects of the preposition "from" and "to" respectively. This indicates a transition between two states.

  • It's basically Stripe for healthcare and doctors.

    ➔ Metaphor

    ➔ Use of the metaphor "**Stripe for healthcare**" to provide a concise and understandable comparison, indicating that the service is analogous to Stripe in its function within the healthcare industry.

  • They saw us as more than just a device company.

    ➔ Comparative Adjective

    ➔ Use of the comparative adjective "**more** than" to show a higher degree of value or perception compared to being "just a device company."

Related Songs