Product Concepts Revocations
What Is A Product Concept Revocation
Occasionally, a Drug or Salt is revoked from DrugBank. When this occurs, any Product Concept which included the now-revoked ingredient must also be revoked. Certain situations in which Drugs or Salts are merged to correct or improve chemical structure information may also require a Product Concept to be revoked. When a Product Concept is revoked a snapshot is stored of its data, which may include ingredients which are also revoked. This rare event is a necessary part of ensuring that Product Concepts are meaningful and consistent.
Revocation Historical Data and Metadata
When a product concept is revoked, the accession numbers (like DBPC0017857) are connected to a revocation model. This model contains a snapshot of the information in the product concept at the time of revocation. This includes not only the data from the product concept such as ingredients, strengths, and so on, but also information about when it was revoked, and product codes which can guide users to a suitable replacement product concept.
Unfortunately, because the historical data stored in a product concept revocation is a snapshot from the moment of revocation, it cannot be updated. As such, this means that it may refer to ingredients that no longer exist, or include other outdated data. If any new fields are later added to new product concept revocations, it will not be possible to retroactively add these to older revocations. It is best to rely as little as possible on this data. Instead, prefer using the suggested replacements described below.
Suggested Replacements
The product concept revocation model stores the list of products which were connected to the revoked product concept at the time of revocation. By using this knowledge along with information about which properties of the product concept were set, a list of suggested non-revoked concepts can be generated. In CSV exports, these suggested concepts are provided in the product_concept_revocation_suggested_replacements table, while API users can find them in the JSON structure returned when viewing a product concept revocation.
Product Concept Revocation Structure
Product concept revocations have very little data of their own. Besides the IDs inherited from
the revoked product concepts, they also include a standing (which is always "revoked"
),
as well as the date of revocation (revoked_at
below).
{
"drugbank_pcid": "DBPC0151796",
"alternate_drugbank_pcids": [],
"standing": "revoked",
"revoked_at": "2018-01-11",
"historical_data": {
"name": "Estradiol valerate / Testosterone Enanthate Intramuscular",
"route": "Intramuscular",
"rxnorm_ids": [],
"ingredients": [
{
"drug": {
"name": "Testosterone",
"drugbank_id": "DB00624"
},
"exact_ingredient": {
"name": "Testosterone Enanthate",
"drugbank_id": "DBSALT001030"
}
},
{
"drug": {
"name": "Estradiol",
"drugbank_id": "DB00783"
},
"exact_ingredient": {
"name": "Estradiol valerate",
"drugbank_id": "DBSALT000068"
}
}
]
},
"suggested_replacements": [
{
"name": "Estradiol valerate / Testosterone Enanthate Intramuscular",
"drugbank_pcid": "DBPC0340214",
"regions": {
"us": false,
"canada": true,
"eu": false
}
},
{
"name": "Estradiol valerate 6.5 mg / Testosterone Enanthate 100 mg /1.0 Intramuscular",
"drugbank_pcid": "DBPC0340215",
"regions": {
"us": false,
"canada": true,
"eu": false
}
},
{
"name": "Estradiol valerate / Testosterone Enanthate Intramuscular Solution",
"drugbank_pcid": "DBPC0340218",
"regions": {
"us": false,
"canada": true,
"eu": false
}
},
{
"name": "Estradiol valerate 6.5 mg / Testosterone Enanthate 100 mg /1.0 Intramuscular Solution",
"drugbank_pcid": "DBPC0340219",
"regions": {
"us": false,
"canada": true,
"eu": false
}
}
]
}