Currently, the API covers ICD codes.
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.
We offer a free tier and competitive paid tier for power users. Read more on the pricing page.
Registering your app is not required, but the amount of calls unregistered apps can make to the API are severely limited. Registration is free and quick!
API "users" (also known as "providers") are individual persons who are end users of your client application, such as doctors, admininstrative staff, medical coders, or healthcare consumers.
Code metadata obtained from API calls made using user access tokens cannot be used for internal processing purposes, analytics/machine learning, or by more than one individual per account. If the usage of the API by a particular user account appears be violating these restrictions, Aqua.io retains the right to, at our sole discretion, block access for that user account and/or the client application that registered the account.
Whatever you want! Current customers of the APIs include EHRs, billing systems, and consumer health apps. If you'd like advice on how to integrate the APIs into an application you are building, please just drop us a line.
We're always happy to give you technical advice on how to do so, as well as give you an engineer's perspective on the advantages/drawbacks of the coding systems available via the APIs.
We currently do not allow client applications to "scrape" the Aqua.io codeset APIs (i.e., download a majority of codes for a codeset and store them on your own server) without explicit prior consent by Aqua.io. Aqua.io reserves the right to ban or blacklist applications that appear to be engaging in scraping.