Live data from Hacker News

What’s Really Killing Digital Health Startups

techcrunch.com

61–70 of 159 posts

Re: What’s Really Killing Digital Health Startups

#61
post #57

I'm in the Health IT space but we took a different approach. Early on we realized most Health IT companies are really pharmaceuticals but they don't realize it. What I mean by this is, you need to have the budget of a pharmaceutical to play in this space: 1 - you need to spend millions to win over consumers and 2 - you need to have an existing network of connections into doctor's offices to convince them of your solu…

Considering that the average new molecular entity requires about $1 billion dollars over 10 years (factoring in cost of refining approximately 10,000 candidates into 1 entity capable of succeeding in Phased trials and receive approval), I'm not so sure these startups are anywhere near the "pharma" level.

It's more the perspective. I.e. you can't just apply tech to healthcare and expect to become successful anymore than you can apply it to ex. the shipping industry.

Some businesses are so intertwined with everything from unions, to legality to human behavior that you need to know what you are getting into before you even start.

Re: What’s Really Killing Digital Health Startups

#62
post #45

Earlier quoted context omitted.

So like Zapier but for that sector?

I have been consistently surprised that Zapier hasn't taken off like a rocket. Can anyone explain this? Zapier integrates an amazingly high number of SaaS's. And aside from the annoying lag due to their frontend being done as a SPA (which doesn't effect their API at all), they seem to be well-built. I do wonder a bit at their pricing, but it's not outrageously overpriced (and underpriced compared to many competitors)…

Zapier is great when you're dealing with REST (or even SOAP) calls.

Problem is, most medical applications don't use REST or SOAP. Chances are they use one of many different variants of HL7, which usually operates through an ETL/data warehousing process. HL7 is one of those data standards that's only widespread because it's barely even a standard -- you'd have to write a different parser for every product or combination of products you integrated with.

And this isn't even touching the hundreds of other proprietary data formats, for everything from medical telemetry (pulse, o2 levels, etc) to imaging (x-rays, MRIs, etc) to billing. Many of these companies don't want you to be able to use their data (because, of course, they offer their own EMR platform or require a hefty licensing fee), so it will be encrypted.

All this is on top of all the deployment problems that SaaS platforms solved in the 2000s -- most offices are still using ancient on-premesis EMR platforms built in the 90s for record keeping purposes. Younger doctors with newer practices are using SaaS systems, but very few young doctors can afford to go into practice for themselves right out of med school. So it's a problem that will eventually be solved, but the time horizon is probably closer to 5-10 years than the 3-5 years we're used to in technology.

As far as Zapier goes, I don't know that it really saves a lot of money for companies. The hardest part of integration isn't coding the integration, it's building out the business requirements -- something you still have to do with Zapier. For anything simple enough to use Zapier for, a junior developer could write the code in an hour or two of his spare time.

Re: What’s Really Killing Digital Health Startups

#63
post #45

Earlier quoted context omitted.

So like Zapier but for that sector?

I have been consistently surprised that Zapier hasn't taken off like a rocket. Can anyone explain this? Zapier integrates an amazingly high number of SaaS's. And aside from the annoying lag due to their frontend being done as a SPA (which doesn't effect their API at all), they seem to be well-built. I do wonder a bit at their pricing, but it's not outrageously overpriced (and underpriced compared to many competitors)…

Are their numbers public? If they are I'd love to see them; if they indeed haven't "taken off" I'd also be surprised.

Re: pricing; I'd argue they're vastly underpriced, when you consider the development costs of writing the integrations yourself. I could pay them $20/month indefinitely and never spend more than the development effort would cost to write and maintain 20 (heck, even 10) integrations.

Re: What’s Really Killing Digital Health Startups

#65
post #24

Having done exactly this type of integration with legacy systems I think a point that gets glossed over is that it's the startups themselves who are full of engineers who think that the whole world has moved on to using NoSQL Node.js RESTful JSON APIs in the cloud (that buzzword soup was intentional) when the reality is that the majority of established businesses are using unsexy and what they would consider to be "l…

What's really killing digital health startups: failure to do due diligence.

I'd say that the potential digital health startups that do their due diligence end up picking another industry. So it's only the guys who failed to do it who end up starting companies.

The VC startup model relies on finding white space and occupying it. Heavily regulated industries (like health care) tend not to have a lot of white space because the boundaries are rigidly defined by law. It's not a good fit for health care.

Re: What’s Really Killing Digital Health Startups

#66
post #65
post #24

Earlier quoted context omitted.

What's really killing digital health startups: failure to do due diligence.

I'd say that the potential digital health startups that do their due diligence end up picking another industry. So it's only the guys who failed to do it who end up starting companies. The VC startup model relies on finding white space and occupying it. Heavily regulated industries (like health care) tend not to have a lot of white space because the boundaries are rigidly defined by law. It's not a good fit for healt…

I guess that depends on how you define it. If by "digital health" companies you mean medical industry companies, you may have a point. But part of what is wrong with American health care is that health care is a polite euphemism for medical care. Grocery stores do not get defined as being in "health care," though eating healthy is clearly a cornerstone of good health.

But I think it is possible to want to do something health related, conclude that the medical industry is a nightmare, and find another approach.

Re: What’s Really Killing Digital Health Startups

#67

I'm in the Health IT space but we took a different approach. Early on we realized most Health IT companies are really pharmaceuticals but they don't realize it. What I mean by this is, you need to have the budget of a pharmaceutical to play in this space: 1 - you need to spend millions to win over consumers and 2 - you need to have an existing network of connections into doctor's offices to convince them of your solu…

This comment and the OP mirror my own experience(s).

Additionally, data interchange between competitors is a non-starter. Possible solutions (work-arounds) will be single payer or continued market consolidation (hospitals merging and then implementing one of the big systems like EPIC).

Not mentioned is that continued churn like HL7 v3, ICD-10, meaningful use, etc. are hugely onerous while adding zero value. A cynic might wonder if its just make work for the consultants.

---

Source: My team designed, implemented, and supported the backend of 5 exchanges. Like this one:

MedPlus to Implement Clinical Portal and Information Exchange for the Brooklyn Health Information Exchange (Jan 11, 2008) http://newsroom.questdiagnostics.com/index.php?s=30649&item=...

Re: What’s Really Killing Digital Health Startups

#69
post #8
post #2

Articles like this make me wonder about Oscar Health.

Oscar Health is actually an insurer. They're trying to win by (a) better marketing and (b) using tech (like free fitness tracker) to reduce their loss ratio. I've heard their innovation was also in pre-paying facilities for services. The collection rate for facilities from insurers is abysmal, so Oscar can negotiate a substantial discount by paying up front. Same idea as if you go to an MRI facility and offer them ca…

What Oscar Is Up Against (http://go.theinformation.com/152dc2)

> After two years in operation, the financial trajectory is becoming clear, both in terms of the growth and the costs. In New York, the company projected a sevenfold increase in premium revenue next year to $399 million from 2014. But it also projects a loss of 12% of premiums, equivalent to $47 million, according to regulatory filings.

...

> Oscar’s losses stem from two sources: higher medical costs as a percentage of premiums than rivals, and higher administrative costs, both of which are traditionally problems of scale in the industry.

> In New York, it projected that 91.5 percent of premium revenues would be eaten up next year by medical claims costs, among the highest projected ratios in the state. That leaves little left over to pay for administrative costs, estimated to be 17 percent of premiums next year, or taxes and fees. Included in administrative costs are the company’s engineering and marketing costs.

> History says insurance companies need at least 200,000 to 300,000 members in a state to be viable, according to Ash Shehata, a partner in KPMG’s health care practice; Oscar had 38,000 members in New York and New Jersey as of June 30, with plans to expand to Texas and California this year.

...

> But Oscar believes it can succeed as a sustainable and profitable business with only 80,000 to 100,000 members per state, according to a person familiar with the company. Though scale is important to contain administrative costs, the person said, Oscar’s plan is to avoid playing the big insurance company game of using size to negotiate lower claims costs with providers. Instead, it will curb claims costs by partnering closely with select providers to exchange data.

'Partnering closely with select providers' is probably the same thing you're referring to - pre-paying facilities for services.

Re: What’s Really Killing Digital Health Startups

#70

Having done exactly this type of integration with legacy systems I think a point that gets glossed over is that it's the startups themselves who are full of engineers who think that the whole world has moved on to using NoSQL Node.js RESTful JSON APIs in the cloud (that buzzword soup was intentional) when the reality is that the majority of established businesses are using unsexy and what they would consider to be "l…

Yes. And on the other side, you have dinosaurs stuck on using MUMPS, Cache (InterSystems), eGate/JCAPS, BizTalk, or some other monstrosity.
Post reply on HN