As we grow, so do our products. We’ve been working hard to bring big improvements to our Clinical API for the Spring feature release. From therapeutic alternatives to completed Health Canada mapping and new authorised products, we’re able to offer you more.
Check out what we’ve been working on.
Table of Contents
- Therapeutic Alternatives
- Completed Mapping to Canadian Clinical Drug Data Set
- Authorised Products Now Available
- Top 5 Ways to Leverage the API
- Deprecation Notices
Starting now, all Clinical API users will be able to view therapeutic alternatives for a drug based on therapeutic categories. This new feature will also enable users to see drug alternatives for a product and a product concept. Among its many uses we see it being helpful for prescribing clinicians who are looking for alternative medications for a patient.
Completed Mapping to Canadian Clinical Drug Data Set
We’re thrilled to announce that we’ve completed mapping to Health Canada’s Canadian Clinical Drug Data Set (CCDD), a database that enables interoperability for e-prescribing. If you’re building e-prescribing functionality in Canada, we would love to talk to you!
Authorised Products Now Available
In addition to approved drug products, products that have received emergency use authorization (EUA) across all supported regions are now included in the API search results. While uncommon, these EUA products have proven to be clinically-relevant, as we’ve seen with the COVID-19 vaccines.
Top 5 Ways to Leverage the API
Our Clinical API is a dynamic and powerful tool. No matter how you’re using it, there are even more capabilities to try. Check out our top five ways to leverage the API:
- Search drug products
- Check for possible drug interactions
- Understand what a drug product is indicated to treat
- Review a drug product’s possible adverse effects
- Learn how a drug allergy might present itself
- As of March 31, 2022, we will no longer support vo of the API.
- As of April 30, 2022, we will no longer support the “Find DDI with Product Names” endpoint.
We’ve already reached out to affected customers individually to help them transition and are here for any questions you may have.
These latest features are available for all our Clinical API users. If you have thoughts on how the API could better suit your needs we’d love to hear from you.