Killer NPI API – BloomAPI

The foundation of many mobile physician applications is some sort of NPI lookup. In many ways, the NPI is the social security number for clinicians. It’s a unique identifier for a clinician and pretty much all of them have one. The good part is that the NPI data is downloadable for those who want to use it. Here’s Michael Wasser’s description of the NPI data:

The NPI is downloadable and is made up of basic demographics (name, sex), location information (business address, practice address), affiliations, and details of their practice (taxonomy codes). It is maintained by Cognosante for the federal government. Weekly disseminations are available at http://nppes.viva-it.com/NPI_Files.html. The total size of the NPI is about 4.5 Gigabytes.

The problem: The data isn’t huge, but its too big for excel or to just casually include in an application.

Like any good hacker, Michael Wasser saw this problem and decided to create a solution. That solution is called the BloomAPI (see also the github repository). I think this NPI lookup tool is a really great offering to the healthcare IT community. I’m sure we’ll see many applications use this going forward.

About the author

John Lynn

John Lynn

John Lynn is the Founder of the HealthcareScene.com, a network of leading Healthcare IT resources. The flagship blog, Healthcare IT Today, contains over 13,000 articles with over half of the articles written by John. These EMR and Healthcare IT related articles have been viewed over 20 million times.

John manages Healthcare IT Central, the leading career Health IT job board. He also organizes the first of its kind conference and community focused on healthcare marketing, Healthcare and IT Marketing Conference, and a healthcare IT conference, EXPO.health, focused on practical healthcare IT innovation. John is an advisor to multiple healthcare IT companies. John is highly involved in social media, and in addition to his blogs can be found on Twitter: @techguy.

2 Comments

  • Thanks for the kind words! I hope that with the launch of BloomAPI developers will never again skip over clinician lookup functionality because its too much work to build or because they have to pay for better access to this open data. In the last week since the launch, several companies have let me know they’ve already implemented functionality on top of bloomAPI!

    I also hope we will see more open projects in the future. The more accessible the data, the more organizations will be able to focus on their core values.

Click here to post a comment
   

Categories