News for hackers. Stuff that matters.
Re:Clover Health, an insurance startup trying to use data to... by ubernostrum on Wednesday December 14, 2016 @03:58PM (#13179587)
(I work at Clover)

As a 23 year old I'm not sure if this is any different than what big insurance co's do for their Medicare enrollees.

The difference is most insurers would say something like "OK, out of X thousand Medicare-age people, Y of them will have this expensive health problem over the next year, are we profitable when that happens?". We say "OK, how can we identify the people most at risk of that and use preventive care to head it off?" So while most insurers just take the statistics as a given and budget for it, we're trying to change the statistics.

storage and management of this tangential customer data

I think you vastly underestimate how much low-hanging fruit there is in this field, and how difficult getting and maintaining good data (so you can find the things you can do) really is :)

Re:Clover Health, an insurance startup trying to use data to... by Justin_K on Wednesday December 14, 2016 @04:22PM (#13179779)
Every health plan has been doing this for years. They too have treasure troves of data... they have care coordinators, patient centered medical homes, etc. So, how are you actually trying to change the statistics?
Re:Clover Health, an insurance startup trying to use data to... by exelius on Wednesday December 14, 2016 @10:26PM (#13182141)
Ehhh... not so much.

Some of the mid-size companies are okay at this; but the low-end guys are very, very unsophisticated (there are a lot of local / state plans as mandated by various state laws) and the super-big guys just have so much stuff they have no idea how to integrate it all. Think 15-20 different, incompatible claims systems with overlapping numbering schemes, different versions of schema, different versions of underlying DB required, etc. Then do the same with provider management systems, contracting systems, etc. You get the point.

By the time you get halfway through scoping out a project, the architecture will be obsolete. Oh and also the federal government keeps changing the rules about ICD-10, ACA, Medicare reimbursement, and a whole bunch of other stuff, so make sure you add in that capability to all existing systems and don't get sanctioned. A lot of companies are having a hard time keeping their heads above water.

The big guys are going to eat the data-hungry guys. Or rather, the big guys will buy the best of the new data-first health plans (Clover, Oscar, etc.) for their platforms and migrate everything onto them.

Re:Clover Health, an insurance startup trying to use data to... by Mz on Wednesday December 14, 2016 @05:09PM (#13180108)
Every health plan has been doing this for years.

I processed insurance claims for over five years and that was not my observation. Granted, it was one company, I processed accident claims and it was supplemental coverage. But when I was there, I was initially encouraged by the trend towards adding "wellness benefits" because I had naïve fantasies this meant they were working towards getting people healthier.

Nope. It was entirely about "If we offer specific tests and call them wellness benefits, we have higher retention."

That was it. There was zero interest in actually making customers healthier. And I was horrified and I am pretty cynical these days.

So, I guess, I am wondering if you have supporting evidence? (Links to articles, stats, etc?)

Re:Clover Health, an insurance startup trying to use data to... by ubernostrum on Wednesday December 14, 2016 @07:46PM (#13181268)
This isn't my first insurance company. The typical experience in insurance is that those tools mostly only come out once someone already has the expensive problem, and are used to manage the cost of it after the fact, rather than prevent it from happening in the first place.

Also most insurance companies aren't really set up to do preventive work to the extent we do (which involves home visits from nurses and other clinical staff, staying in touch and proactively reaching out when there seem to be problems, etc. etc.), largely because they consist of essentially competing divisions which each own a subset of the data and responsibilities and jealously guard against every other division. I worked in a company like that, once upon a time -- everyone had very clearly-defined limits to their responsibilities (well beyond what privacy rules required) and even just contacting someone in a different department to make them aware of a problem or pass along a suggestion would trigger turf-war consequences.

I'm very happy to now be working with the opposite of that.

Finally, it's worth noting that although there are a lot of dismissive comments about tech in this thread (and some of it I can understand -- most of what we do is internal-facing and harder to promote as a result), the perspective inside is pretty different. It's true there's not a ton we're doing that's cutting edge and "sexy" tech (though we have open-sourced some neat tools for temporalizing SQLAlchemy's ORM), but that's because health care hasn't yet caught up to just the boring everyday things we take for granted.

There's an example that really drove it home for me, from about six months ago. Claims are obviously a big part of what we're about, and so we have an internal team that reviews processed claims for accuracy. They have to check against a pretty complex set of Medicare claim-processing rules, part of which involves rules about combinations of medical procedures (i.e., Procedure A might be allowed but only if alongside Procedure B, or A might only be allowed without B, or A and B might just be independent and can both appear or not appear). The canonical source for that data is... gigantic Excel spreadsheets of all the procedure codes and rules. And so the claims-review team would open up Excel, type in a code, wait five minutes while it churned to find the code, then repeat for the next code, etc.

An engineer saw this and spun up a two-day project to ingest those spreadsheets (on an ongoing basis, since they change over time) into a database and wrap a search interface around them which allowed punching in all the codes and getting back a list of rules and an indicator of whether they'd been violated.

To tech people that's so mundane it almost puts you to sleep, and makes you say "wait, that's it?". But to healthcare people, it was a gigantic step forward. So many people from health backgrounds came from places that never let them work side-by-side with tech staff and figure out what was possible (or where all tech was outsourced to vendors with opaque planning and feature-request processes), which is why so much of healthcare tech feels decades out of date.

So just having tech and medical/insurance people in the same room, working and talking together every day, acts as a pretty impressive multiplier compared to traditional insurance companies.

Re:Clover Health, an insurance startup trying to use data to... by coldcode on Wednesday December 14, 2016 @08:54PM (#13181687)
Also worked at a Healthcare (claims processing) company owned by multiple giant insurance companies. I never thought of it as healthcare but just health plumbing, all we did is push HIPAA data from point A to point B. And we also had horrible turf wars and insanely stupid projects that did no one any good.

What you are doing is far more interesting. It was pretty obvious that there is a lot one can do with data, assuming you can deal with the HIPAA limitations. One ill person is hard to get much from, but 10000 is different story.

Re:Clover Health, an insurance startup trying to use data to... by roymurdock on Wednesday December 14, 2016 @10:35PM (#13182171)
Thanks for taking the time to write up your experiences here. Much more informative than the Bloomberg article. I agree that culture/what management knows and focuses on can make a huge difference, especially in a field like medicine where there are so many rules and regulations around data and expensive industrial equipment that the market can take a while to catch up to consumer/enterprise tech.

I wouldn't be surprised to see you guys getting acquired by a Bigco insurance. I'm guessing that's an exit your investors are hoping for and part of a reason for the Bloomberg article, to start getting the company on the biz radar.

Re:Clover Health, an insurance startup trying to use data to... by exelius on Wednesday December 14, 2016 @10:37PM (#13182175)
> I think you vastly underestimate how much low-hanging fruit there is in this field, and how difficult getting and maintaining good data (so you can find the things you can do) really is :)

100% agree. Health insurance data is about as garbage of data as you can get.

Many providers still fill out claims by hand and fax them in. A good many more have an EMR system that just automatically faxes it for them. All this faxing and handwriting and manual data entry means numbers get transposed and data is wrong all the time. Add to this the fact that the people at the doctor's offices filing the claims often have no idea what they're doing and will often file things completely incorrectly (i.e. under a provider code instead of a facility code), leading to a rejection.

I cannot overstate how shitty this data is. Across the board. EMR systems are getting better, but generally only younger doctors in independent practices use the more cloud-based/big data ones. Big hospitals and the like are still generally on proprietary EMR systems (and that doesn't mean it's any better; different departments can have different billing practices that still screw things up).

It will take AI to clean up this mess. It's just too complex for humans to tackle.

Re:Clover Health, an insurance startup trying to use data to... by qwrusz on Wednesday December 14, 2016 @09:17PM (#13181792)
Thanks for coming on here and giving some insight. Not always easy to do as HN comments can sometimes get a bit brutal.

I agree there needs to be better health care data science going on towards improving wellness and health care (assuming data is collected, stored and analyzed honestly and appropriately - whatever that means these days is whole other debate).

But I think it would be helpful to everyone if there was a bit more transparency and clarity from health care related startups about their plans and what they are doing. For example:

It sounds like a couple very separate things are going on here:

1) You are a health insurance company

2) You are an organization doing medical patient data collection and data analyses and pushing real-world actions based on this analyses to try to improve wellness and prevent/reduce expensive medical problems.

The first is relatively straightforward, the insurance business is really just a math equation with a marketing department. Health insurance and Medicare are a bit of a special case because the government has said health insurance companies must pay out most of the premiums to medical care costs or give the money back. Though this government contract component creates a numbers game with a single digit profit % built in once you scale (you can also do a decent back of the envelope valuation just discount your member growth as other inputs and comps are ~standardized).

The second thing, medical data science is where it gets complicated. This is serious work that needs to involve doctors and medical research professionals and studies before anything major can happen. I think it's great if an insurance company wants to take some of its revenue and put it towards data science focused on researching better wellness and health care. (Let's ignore for a moment that the incentives from a business model and profit potential are not clearly aligned by doing this, eg you don't get to keep medical care cost savings, you give it back).

More of an issue is the ambiguity around stuff like the "promise of using technology to solve such a large and socially significant problem as health care is one of Clover’s most powerful recruiting tools" and then goes on to say a guy from Yammer and engineers from FB and Google are mining health data to "suggest ways to prevent them before they happen." What is that suggesting process and who is involved? Recommendations of brown rice and gym memberships to a couple of octogenerians is funny and relatively mild (and kinda pathetic tbh). But it's a risky slippery slope when potentially unqualified and premature medical data analyses conclusions start to be implemented in the real world, it could be even dangerous to people's health, the opposite effect, even with the best of intentions. The example from the article could go bad: have you studied a potential rise in injuries when you recommend gym memberships to 83 year olds? If this has been properly studied and implemented make it public.

Re:Clover Health, an insurance startup trying to use data to... by ubernostrum on Wednesday December 14, 2016 @10:15PM (#13182102)
I think it's interesting you assumed there must be zero credentialed medical professionals involved in the company or the things we're trying, or that random engineers are making care decisions. So allow me to immediately disabuse you of that notion.

We are not a tech-led company: we're a company that makes tech -- in the form of tools, data science, etc. -- available in service to our clinical, operations, and insurance staff. My project right now involves building out a social-work assessment app, for example; I don't decide what goes in it or what actions to take based on the responses entered. No engineer does. The LCSW who's in charge of the assessment tells us what goes in it and what the workflow rules for it are and how data from it should propagate into our systems and be used. My job is to bring technology to bear to make it A) easier for the social workers to use than their current paper forms, B) easier to process the data so that they can use data-science frameworks on top of it to inform their decisions about how to care for someone.

Re:Clover Health, an insurance startup trying to use data to... by qwrusz on Thursday December 15, 2016 @12:54AM (#13182748)
I didn't assume zero credentialed medical professionals are involved in the company. The article clearly states you have 12 nurse practitioners serving your 19,000 members. I looked at your website too and saw some of the other clinical operations roles.

I also didn't assume random engineers are making care decisions. I said this is ambiguous and I asked a question: What is that suggesting process and who is involved?

The article says you are "developing software to organize the trove of data coming from workers on the ground in New Jersey, mine it for likely health problems and suggest ways to prevent them before they happen." Your website says "we’re also partners in care, using patient-centered analytics and a dedicated care management team to identify potential risks and directly provide preventive care."

Well nurses generally don't know much about data science software and data scientists generally don't know much about practicing medicine or preventive care.

And of course you are not a tech-led company. You are a marketing company and government contracted middle man connecting health care services to patients and handling some of their paperwork and payments. Still this is an industry entirely living off regulatory capture.

I'm not accusing you of denying someone's valid insurance claims because they didn't take your eat brown rice suggestion.

But you yourself claim to be an insurer "trying to change the statistics". I get the preventive care and data science shtick looks good when marketing to potential members and to potential investors. But it's not clear how you are taking on the "change the statistics" part you claim to be, which is the most interesting and important part of all this to the extent it is real as improving peoples' health and wellness, and preventing serious health problems would be amazing!

So I asked a question about how the process works and who is involved as getting data and actionable data analyses to and from health care professionals in the field is not straightforward, nor is it trivial, nor is it explained anywhere.

Re:Clover Health, an insurance startup trying to use data to... by ubernostrum on Friday December 16, 2016 @02:32AM (#13191712)
I've left some longer comments elsewhere in this thread about the problems with typical insurers. There's a lot of low-hanging fruit out there, which many of them aren't equipped to take advantage of because of how they're structured, and don't particularly desire to take advantage of anyway. Like I said originally, a lot of insurers are content to look at the average risk, figure out a way to be profitable in spite of it, and call it a day, because the economics of Medicare Advantage have allegedly been "solved" in that sense.

The way I see it, the premise of Clover is asking what would happen if you removed the corporate-organization barriers and the organizational disinclination to do much beyond just processing claims. All those easy preventive-care wins suddenly become real options, for example. And as the insurer you have all the data to identify gaps and potential problems. For example: you know someone has a prescription because you see the pharmacy claims. And you know if they stop filling it because you stop getting claims. That's a potential problem that's easy to identify, and you have the staff to get in touch and find out what happened; maybe it's as simple as finding a pharmacy that's easier for them to get to, or a service that will pick up and deliver without requiring regular trips to the pharmacy. Sometimes it's the complexity of a particular medication regime (especially since often it just comes in the form of written instructions with little context), and clinical staff or pharmacists pharmacists take a look and come up with better explanations and adherence plans.

And really, just the easy obvious stuff is so copious that I suspect it's going to be years before we run out of it and have to worry about trying to come up with new ideas -- it's just that most insurers are not structured to take advantage even of stuff that's known to be helpful for people, so nobody's ever seen what happens when you try.

Still this is an industry entirely living off regulatory capture.

I'm not really sure what you mean by this. I'm not privy to exactly why Clover's in the Medicare space, but my inclination is that it's because Medicare provides a stable, existing and relatively well-known space to operate in, and precisely because of how it's structured and regulated it provides a few things already packaged up that you don't have to bootstrap or which aren't quite as hard to bootstrap. And although it is heavily regulated, I've seen no evidence that the regulatory structure is designed to exclude competitors or preserve existing players; for example, in January of this year, Cigna (hardly a disruptive new player) was hit with sanctions that temporarily remove their ability to enroll new members into their Medicare Advantage plans. Everything I've seen of the regulatory environment is that it's designed to ensure the safety of Medicare enrollees and to push Medicare Advantage insurers to take good care of them.