In addition to providing names and explanations for each code, the API also provides Wikipedia links (for ICD codes only, coming soon for LOINC), two-way ICD9/10 equivalency mapping, LOINC lookup by property, method, system, or related term, and collected metadata from various drug coding sets. Searching by code name and explanation is also available. Everything comes across in simple, beautiful JSON.
We are currently in the process of testing other medical and healthcare related APIs we have developed for release. If you would like to suggest a useful API you would like to see, shoot us an e-mail.
Really, that's it! We will always keep the APIs launched and documented here free to use and available to all developers. Healthcare IT standards and coded values ought to be easy and free for developers to understand, use, and deploy, so these APIs are intended to make that into reality.
Nothing. Nada. Zip.
Mostly, two things:
You may find some data is poorly formatted or incomplete. We're working on it. Shooting us an e-mail outlining an error or omission you've discovered in the data is the fastest way to get it fixed.
We may add new fields to the JSON outputs for some objects, as we continue to improve and expand our data resources and push the limits of how much we can output without affecting performance. The documentation pages for each call will be updated immediately, if any changes are made.
We will not remove or alter the names of any fields already documented, however, so don't worry--any future changes should not break your current implemenations of the API.
At the moment, no.
We do appreciate knowing who is using the app, however, and encourage you to sign up for our mailing list (at the bottom of the page, or to follow us on Twitter.
Whatever you want. If you want to tell us what you've created, we'd be happy to link to it on this page.
The API is made available under a slightly modified form of the MIT License so all the usual legal disclaimers about how you use the API at your own risk and indemnify us against errors or omissions in the data apply. Other than that, no.
Here's the license:
Copyright (c) 2013 Aqua.io
Permission is hereby granted, free of charge, to any person using application programing interface and associated documentation files (the "API"), to deal in the API without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the API, and to permit persons to whom the API is furnished to do so, subject to the following conditions:
THE API IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.