Factual Makes a House Call with Improved Healthcare Provider Data

In the U.S., we have many choices when considering healthcare providers for ourselves or loved ones. Unfortunately, much of this information is scattered, disjointed, and unreliable.  If you’re shopping around for a specific type of doctor or specialist based on the insurance you have, that information is not easily available via the big search engines or major health web portal or apps.  Insurance companies have made it fairly difficult for both consumers and application developers to get data on the doctors they reimburse.

The Data Stack: A Structured Approach

At Factual, we think about data day and night. Our goal is not just to create products, but to create new data economies that draw people to participate because we offer a better data experience. Because of this mission, we organize our work using what I call the data stack.

Keep on Driving

You may have noticed that we’ve built up a pretty extensive array of software drivers to access our API. I’d like to take a few moments to provide insight into our driver strategy and the lessons that have informed it.

Factual’s API: A Good Fit for Node

Most people have heard the buzz surrounding Node. Words like “fast”, “scalable”, “concurrency” come to mind. At Factual, we pride ourselves on using (and finding) the right tool for the job. We use everything from jquery to hadoop, postgresql to mongodb and fortunately our engineering culture gives us the leeway to experiment a little.  However, any technology that we deploy has to be measured and justified.  Qualities such as agility, performance, stability and cost are all part of the equation.