HealthTech · Data made useful

Ask the government's healthcare data anything.

The government publishes an enormous amount of public healthcare data, and almost none of it is usable. Getting one real answer meant hiring analysts and waiting weeks, so most questions never got asked. I fixed that. Now you ask a question the way you'd say it out loud, and you get a clear answer back in seconds.

One place for all of itAsk in plain EnglishAnswers in secondsNo data team needed
Oshri Cohen, CMS healthcare data made useful
Oshri CohenDigital products delivered
The problem

The data is public. The answers weren't.

All the information is right there, free, for anyone. Actually getting an answer out of it is where everyone gets stuck.

Scattered everywhere

The piece you need is split across hundreds of separate places that were never meant to work together. Answering one question first means hunting down and lining up half a dozen of them.

Nothing lines up

The same hospital, doctor or drug is labeled three different ways in three different places. Before you can compare anything, someone has to make it all agree, and that someone is usually expensive.

Every question started from zero

Want to compare quality against cost across a region? That was a project: scope it, staff it, wait weeks, pay for it, for a single answer. So most questions simply never got asked.

The solution

Gather it once, then just ask.

All of it in one place

I brought the whole sprawling collection together into one place, with the same hospital, doctor and drug finally lined up so they can be compared instead of just collected.

Always current

It keeps itself up to date on its own. When the government publishes something new, it's there, so you're always working from today's picture, not a snapshot someone pulled a year ago.

Ask in plain English

No special skills, no query language, no ticket to a data team. You ask the question the way you'd say it in a meeting, and the answer comes back.

Answers, not raw data

You get the finished answer, the ranking, the comparison, the number you were after, rather than a giant file you'd still have to make sense of yourself.

Built for the questions people actually ask

It's tuned around the real questions clients bring, quality versus cost, who's growing, where the outliers are, so the answers land on the decision, not a chart nobody reads.

Powers your own dashboards

Teams plug it into their own dashboards and tools, turning a pile of public data they could never use into a living source of answers they own. See 50 questions it answers for the kinds of things it unlocks.

Before & after

What changed about getting an answer.

Before

A project per question

  • , Track down the right sources by hand
  • , Pay specialists to make them line up
  • , Build something custom for this one question
  • , Wait weeks and pay for the analyst time
  • , Most questions never get asked at all
After

Ask, and get an answer

  • Everything is already gathered and lined up
  • It stays current on its own
  • Ask in plain English, the way you'd say it
  • Get a clear answer in seconds, not weeks
  • Cheap enough to ask the questions you used to skip
The result

Questions that were once too expensive to ask.

Allof it
The whole public healthcare data collection, gathered and lined up in one place
PlainEnglish
Ask the way you'd say it out loud, no specialists or special skills required
Days→sec
Answers that took weeks of analyst time now come back on demand

The data was always public. What changed is the cost of asking a question of it. When the answer drops from a three-week project to a sentence, people finally ask the questions that move the business.

Oshri Cohen · On making data useful
Common questions

What people ask about this.

What can clients actually do with it?

They ask questions and get answers, without a data team in the loop. Instead of commissioning an analysis and waiting, someone types the question the way they'd say it in a meeting and gets a clear answer back, a ranking, a comparison, the number they needed. That's what makes the dashboards and reports possible: the hard part is handled once, up front, so every question after that is quick and cheap.

How do you keep it current?

It updates itself. When the government publishes new information, it gets pulled in automatically, so you're always working from the latest picture rather than a stale extract someone downloaded once and forgot. Nobody has to babysit a download folder.

Why is this so much cheaper than before?

Before, every question was its own project: find the sources, make them line up, build something custom, wait weeks, pay for the time. Most questions never got asked because it wasn't worth it. Here all of that hard work is done once, up front. After that, asking a brand-new question costs almost nothing, so the answers people used to skip are suddenly within reach.

Sitting on public data
you can't actually use?

Whether it's this healthcare data, another government data dump, or your own scattered systems, I build the thing that turns it into answers anyone can ask for.