How does the Object and Description table and JSON Output of Drugbank drug products API function?
In this article, I will clarify the object table and JSON output specifically of the Drugbank drug products API. As a programmer, it's essential to have a clear understanding of the data format you're working with, and the Drugbank API provides data in the JSON format. JSON (JavaScript Object Notation) is a lightweight data interchange format that is easy for humans to read and write and easy for machines to parse and generate. The object table, on the other hand, is a tabular representation of the data in the API, which can be helpful in organizing and analyzing large sets of information. By the end of this article, you will have a clear understanding of the object table and JSON output of the Drugbank drug products API, which will make it easier for you to work with and manipulate the data.
Table
| Objects | Description |
| name | The proprietary name(s) provided by the manufacturer for any commercially available products containing this drug. |
| ndc_product_code | The National Drug Code (NDC) product code from the FDA National Drug Code directory. |
| dpd_id | Drug Product Database (DPD) identification number from the Canadian Drug Product Database. Only present for drugs that are marketed in Canada. |
| started_marketing_on | The starting date for market approval. |
| ended_marketing_on | The ending date for market approval. |
| dosage_form | The pharmaceutical formulation by which the drug is introduced into the body. |
| strength | The amount of active drug ingredient provided in the dosage. |
| route | The path by which the drug or product is taken into the body. |
| fda_application_number | The New Drug Application [NDA] number assigned to this drug by the FDA. |
| country | The country where this commercially available drug has been approved. |
| over_the_counter | A list of Over The Counter (OTC) forms of the drug. |
| generic | Whether this product is a generic drug. |
| approved | Indicates whether this drug has been approved by the regulating government. |
| source | Source of this product information. For example, a value of DPD indicates this information was retrieved from the Canadian Drug Product Database. |
| ema_product_code | |
| ema_ma_number | |
| labeller | |
| prescribable_name | |
| standing | |
| etc | etc |
name: The proprietary name(s) provided by the manufacturer for any commercially available products containing this drug.
ndc_product_code: The National Drug Code (NDC) product code from the FDA National Drug Code directory.
dpd_id: Drug Product Database (DPD) identification number from the Canadian Drug Product Database. Only present for drugs that are marketed in Canada.
started_marketing_on: The starting date for market approval.
ended_marketing_on: The ending date for market approval.
dosage_form: The pharmaceutical formulation by which the drug is introduced into the body.
strength: The amount of active drug ingredient provided in the dosage.
route: The path by which the drug or product is taken into the body.
fda_application_number: The New Drug Application [NDA] number assigned to this drug by the FDA.
country: The country where this commercially available drug has been approved.
over_the_counter: A list of Over The Counter (OTC) forms of the drug.
generic: Whether this product is a generic drug.
approved: Indicates whether this drug has been approved by the regulating government.
source: Source of this product information. For example, a value of DPD indicates this information was retrieved from the Canadian Drug Product Database.
ema_product_code: The product code assigned to this drug by the European Medicines Agency (EMA).
ema_ma_number: Marketing authorization number assigned by the European Medicines Agency (EMA).
labeller: The company responsible for labeling and packaging the drug.
prescribable_name: The name used when prescribing the drug.
standing: The standing of the drug in relation to its availability, such as prescription-only or over-the-counter.
The information presented in the table provides a comprehensive overview of the key properties of a drug product. Each object in the table represents an important aspect of the drug, such as its name, dosage form, strength, and route of administration, as well as information about regulatory approval and availability. Understanding these properties can be crucial for healthcare professionals, researchers, and patients alike. For example, knowing the dosage form and route of administration can help healthcare professionals determine the best way to administer the drug to patients, while information about regulatory approval and availability can help researchers understand the legal and practical limitations of studying the drug in different regions. Overall, having access to this information can help improve healthcare decision-making and contribute to better patient outcomes.
JSON Output
The JSON output provided is an example of data for a single product called Kaletra. The product has several properties, including the name of the drug, the identification number in the Canadian Drug Product Database (DPD), the date the drug was first marketed, the dosage form, the route of administration, the labeller, the name of the product that is prescribable, the standing, and other properties. In addition, the product contains information about the ingredients and their respective strengths, along with other details. This data can be useful for understanding the properties of the drug and how it can be used. The data is formatted in JSON, a commonly used data interchange format in web development.
{
"products": [
{
"name": "Kaletra",
"ndc_product_code": null,
"dpd_id": "02285533",
"started_marketing_on": "2006-09-08",
"ended_marketing_on": null,
"dosage_form": "Tablet",
"strength": "",
"route": "Oral",
"fda_application_number": null,
"country": "Canada",
"over_the_counter": false,
"generic": false,
"approved": true,
"source": "DPD",
"ema_product_code": null,
"ema_ma_number": null,
"labeller": {
"name": "Abbvie"
},
"prescribable_name": "Kaletra 200 mg / 50 mg Oral Tablet",
"standing": "good",
"jurisdiction_marketing_category": "MARKETED",
"branded": true,
"prescription": true,
"unapproved": false,
"vaccine": false,
"allergenic": false,
"cosmetic": false,
"kit": false,
"solo": false,
"available": true,
"ingredients": [
{
"name": "Lopinavir",
"drugbank_id": "DB01601",
"strength": {
"number": "200",
"unit": "mg"
}
},
{
"name": "Ritonavir",
"drugbank_id": "DB00503",
"strength": {
"number": "50",
"unit": "mg"
}
}
],
"supplemental_ingredients" [
],
"images": []
}
]
}
Finishing
Today, we discussed the object table and JSON output of the Drugbank drug products API. The object table lists the key properties of a drug product and provides a comprehensive overview of the drug's properties, including its name, dosage form, strength, and regulatory approval. The JSON output is a data format used to exchange information and is commonly used in web development. Understanding this information can be helpful for healthcare professionals, researchers, and patients in making informed decisions about the drug product. Ultimately, this information can contribute to better healthcare outcomes for patients.
Reference
Access to the Drugbank drug products API is available through the third-party data marketplace of Worldindata. Worldindata provides access to a range of high-quality, curated datasets that can be used for research, analysis, and other applications. To access the Drugbank drug products API, interested parties can visit the Worldindata website and sign up for an account. From there, users can browse the available datasets, including the Drugbank drug products API, and request access. Worldindata will then provide users with the necessary credentials and documentation to start using the API. This provides a streamlined and convenient way to access the Drugbank drug products API, making it easier for researchers, healthcare professionals, and other interested parties to access this important data.