This is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |
Archive 15 | Archive 16 | Archive 17 | Archive 18 | Archive 19 |
What is GoodRx and why should we add it to the drugbox?
| ||
---|---|---|
As for what GoodRx is, their support page probably explains it best:
As for why we should add it to the drugbox:
See this Google search for the string 'insulin cost United States death' and just pick any article (e.g., [1], [2] [3]) In a nutshell, they all say the same thing: the rising prices of insulin analogs in the United States has made it prohibitively costly for some people to fill a prescription for one of those drugs. The clinical efficacy of insulin analogs for diabetes is completely irrelevant if people can't afford to buy them. The news articles from the google search and the examples I provided all say that insulin analogs (nearly all of which cost >$300 out of pocket per the news articles and from checking every link in GoodRx's insulins drug category page; NB: the prices listed next to the drugs on that page are "GoodRx fair prices", not the lowest price with their coupons) are prohibitively costly for diabetics without health insurance; some ration their insulin and/or don't fill prescriptions, and in some cases doing that has led to diabetic ketoacidosis and resulted in death, as stated in those sources. The majority of those articles specifically mention prices for various dosage forms of brand name or generic Humalog (insulin lispro), which is the cheapest short-acting insulin analog (NB: none of those articles mention GoodRx or online drug coupons). If you compare the prices for brand name Humalog/generic insulin lispro mentioned in the sources to the retail prices on GoodRx's generic Humalog page, you'll notice they're more-or-less the same as what's listed there, but GoodRx's Coupons for generic Humalog discount the retail price by ~60% for all three dosage forms (i.e., the kwikpen, carton, and vial). In other words, if someone with diabetes lacks insurance and can only afford to pay a certain $ amount out of pocket for generic Humalog each month due to financial constraints, using GoodRx Coupons will more than double their purchasing power of insulin lispro at that $ amount (i.e., with GoodRx coupons, a consumer with a limited/fixed budget can buy approximately 2.5 times as much insulin lispro for the same total cost as they could without those coupons). That increase in purchasing power could very well obviate the need for a person to ration insulin or forego their prescriptions, thereby mitigating the ketoacidosis risk.
This is a study of prescription drug economics/cost-minimization conducted by USC that used GoodRx data+coupons; I've quoted all of the relevant content from this source on GoodRx below. [1] It's not the only pubmed-indexed article that used GoodRx data for research purposes (e.g., PMID 28895827, 30796990), but it's the only one I've come across that analyzed the utility of GoodRx for prescription drug cost minimization in the United States. It's worth reading the excerpts below IMO.
|
Following up on Talk:Epinephrine (medication)#Cost information in the United States, what do others think of placing a GoodRx link in the drugbox template? We could use a left-hand side field as "US consumer prices" and the RHS could just link directly to the corresponding GoodRx webpage(s) listed on Wikidata for an article (that'd require creating an identifier property for GoodRx). I'd be willing to add the corresponding identifiers to all of the Wikidata entries on prescription drugs listed on the GoodRx website with a bot if there's consensus to do add it to the drugbox. Seppi333 ( Insert 2¢) 18:49, 11 August 2019 (UTC)
Chemical and physical data | |
---|---|
Formula | C9H13NO |
Molar mass | 151.209 g·mol−1 |
[GoodRx_url Pagename_of_Drug_product]
; e.g.,
Amphetamine Salt Combo,
Amphetamine Salt Combo XR,
Mydayis,
Adzenys XR-ODT,
Dyanavel XR,
Amphetamine Sulfate,
Dexedrine Spansule,
Zenzedi,
Lisdexamfetamine. Those products and links are the same ones from this table:
Amphetamine#Pharmaceutical products.
Seppi333 (
Insert 2¢)
07:33, 12 August 2019 (UTC)The first is that I imagine a lot of readers will have no clue what happened to every drugbox on Wikipedia if we suddenly cut them in half without providing some kind of indication of what we did with the other half of the drugbox data (it's not like they're going to know we've moved it to an EL section and I doubt most of them will scroll all the way to the bottom of the article to try to find what we did with it). The second is that all of those links are still very much pertitent to the Drugbox even after being split out, so there should be a means of navigating to them quickly within the Drugbox (this is analogous to the "Supplementary data page" link in the chembox)." – I meant it at face value. We're going to cut the drugbox in two and keep the appearance identical; and, that's why that there's going to be a link from the drugbox at the top of the page to the External data half at the bottom. Seppi333 ( Insert 2¢) 22:58, 14 August 2019 (UTC)
Clinical data | |
---|---|
License data | |
../licence/sandbox | |
License data |
@ Bluerasberry and DePiep: I've added a lengthy explanation about what GoodRx is, the services it provides, the motivation for adding this link to the drugbox, and clearly illustrated the utility of GoodRx to consumers with 2 examples. I strongly suggest reading all of it; but, at the very least, just read the quoted excerpts from the journal citation.
Clinical data and identifiers parameters
|
---|
<!-- Clinical data --> | Drugs.com = | MedlinePlus = | licence_CA = <!-- Health Canada may use generic or brand name (generic name preferred) --> | licence_EU = <!-- EMA uses INN (or special INN_EMA) --> | DailyMedID = <!-- DailyMed may use generic or brand name (generic name preferred) --> | licence_US = <!-- FDA may use generic or brand name (generic name preferred) --> | ATC_prefix = <!-- 'none' if uncategorised --> | ATC_suffix = <!--Identifiers--> | CAS_number = | PubChem = | PubChemSubstance = | IUPHAR_ligand = | DrugBank = | ChemSpiderID = | UNII = | KEGG = | ChEBI = | ChEMBL = | NIAID_ChemDB = | PDB_ligand = |
oppose. I'd agree if the price was listed, with GoodRx as the reference but not with a straight up link. While I agree this is in the public good for US citizens (as already pointed out) I see a lot of dangers. (1) I can't find precedent for including a for-profit link in the infobox (I equate this (from a philosophical point of view) to having the IMDB or Rotten Tomato link in the infobox of a movie), but I think much of the general community would oppose. (2) Their profit model could change, without disclosure, and we could be giving bad and unverifiable information. (3) Their methods seem to be bit of a black box; we can't independently verify accuracy or that they're unbiased (4) There may be bias in the way information is presented (e.g. the referral fees or advertising that is not well marked as such) (5) very specific to the US. Overall; I like the idea as a public service but oppose it because it's easily corruptible by the company and it gives them a significant, and unfair advantage over anyone else that may be providing the same or similar services. Ian Furst ( talk) 19:06, 20 August 2019 (UTC)
{{External links list|GoodRx= [https://www.goodrx.com/amphetamine-salt-combo Adderall], [https://www.goodrx.com/amphetamine-salt-combo-xr Adderall XR], [https://www.goodrx.com/amphetamine-sulfate Evekeo]| MedlinePlus = a616004 | license_US = amphetamine | licence_EU = yes | INN_EMA = amphetamine | Drugs.com = {{Drugs.com|parent|amphetamine}}| ATC_prefix = N06| ATC_suffix = BA01| CAS_number_Ref = {{cascite|correct|CAS}} | CAS_number = 300-62-9 | PubChem = 3007 | IUPHAR_ligand = 4804 | DrugBank_Ref = {{drugbankcite|correct|drugbank}} | DrugBank = DB00182 | ChemSpiderID_Ref = {{chemspidercite|correct|chemspider}} | ChemSpiderID = 13852819 | UNII_Ref = {{fdacite|correct|FDA}} | UNII = CK833KGX7E | KEGG_Ref = {{keggcite|correct|kegg}} | KEGG = D07445 | ChEBI_Ref = {{ebicite|correct|EBI}} | ChEBI = 2679 | ChEMBL_Ref = {{ebicite|correct|EBI}} | ChEMBL = 405 | NIAID_ChemDB = 018564 | PDB_ligand = 1WE| smiles = NC(CC1=CC=CC=C1)C}}
[[#External links|External data]]
or [[#External data|External data]]
provided that I add {{
Anchor|External data}}
to the heading of the new template) at the bottom of the Drugbox for two reasons. The first is that I imagine a lot of readers will have no clue what happened to every drugbox on Wikipedia if we suddenly cut them in half without providing some kind of indication of what we did with the other half of the drugbox data (it's not like they're going to know we've moved it to an EL section and I doubt most of them will scroll all the way to the bottom of the article to try to find what we did with it). The second is that all of those links are still very much pertitent to the Drugbox even after being split out, so there should be a means of navigating to them quickly within the Drugbox (this is analogous to the "Supplementary data page" link in the chembox).In the end result, we should not use meta {{ Infobox}}.And why is that, exactly? I made it clear earlier that I still consider all of these external links to be part of the drugbox even after splitting them out, hence the use of an infobox with an identical appearance; we're simply moving them to the EL section since it's just as appropriate to place them there as it is in Drugbox template itself. Seppi333 ( Insert 2¢) 06:37, 16 August 2019 (UTC)
{{
Infobox}}
to style its contents does not make it an infobox. E.g., {{
Glossary infobox}}
is a back-end template for {{
Addiction glossary}}
and {{
Transcription factor glossary}}
, yet neither of those should be used in place of an actual infobox for an article. Edit: that back-end template was created following this discussion:
Template_talk:Addiction_glossary#"Glossary skeleton" template.
Seppi333 (
Insert 2¢)
06:54, 16 August 2019 (UTC)
class=infobox
(as {{Infobox}} does}}). class
defines loads of behaviour, layout, formatting, presentation (responsive even). Our intentions do not count in a browser. We do not want those effects, that would be bad coding and bad information handling. -
DePiep (
talk)
09:24, 16 August 2019 (UTC){{
Drugbox external links}}
instead of {{
Infobox drug/sandbox2}}
to generate the example.
Seppi333 (
Insert 2¢)
06:54, 16 August 2019 (UTC){{Drugbox external links|GoodRx= [https://www.goodrx.com/amphetamine-salt-combo Adderall, [https://www.goodrx.com/amphetamine-salt-combo-xr Adderall XR, [https://www.goodrx.com/amphetamine-sulfate Evekeo| MedlinePlus = a616004 | license_US = amphetamine | licence_EU = yes | INN_EMA = amphetamine | Drugs.com = {{Drugs.com|parent|amphetamine}}| ATC_prefix = N06| ATC_suffix = BA01| CAS_number_Ref = {{cascite|correct|CAS}} | CAS_number = 300-62-9 | PubChem = 3007 | IUPHAR_ligand = 4804 | DrugBank_Ref = {{drugbankcite|correct|drugbank}} | DrugBank = DB00182 | ChemSpiderID_Ref = {{chemspidercite|correct|chemspider}} | ChemSpiderID = 13852819 | UNII_Ref = {{fdacite|correct|FDA}} | UNII = CK833KGX7E | KEGG_Ref = {{keggcite|correct|kegg}} | KEGG = D07445 | ChEBI_Ref = {{ebicite|correct|EBI}} | ChEBI = 2679 | ChEMBL_Ref = {{ebicite|correct|EBI}} | ChEMBL = 405 | NIAID_ChemDB = 018564 | PDB_ligand = 1WE| smiles = NC(CC1=CC=CC=C1)C}}
class=infobox
, responsive behaviour). I therefor created:|align=right
would be desirable.
Seppi333 (
Insert 2¢)
10:43, 16 August 2019 (UTC)
@ Primefac, DMacks, Doc James, Seppi333, DePiep, and Sceptre: Recent editors: Greetings and felicitations. In both the Australian and the US "Pregnancy category" fields, there is a space between the category and the comment, e.g. in the Ibuprofen article, at least when it is used to add a reference. Unfortunately, I can't see where the problem is, even after checking the sub-templates. Would someone please be so kind as to fix this, or tell what other change should be made? — DocWatson42 ( talk) 04:38, 2 August 2020 (UTC)
|pregnancy_AU_comment=
(and so |pregnancy_US_comment=
) can be used for comment (=add space) and reference (=no space). At the moment, distinguishing between those options is not possible or implemented.|pregnancy_AU_ref=
(cumbersom for editor), or enter like |pregnancy_AU=C<ref>...</ref>
. -
DePiep (
talk)
09:30, 2 August 2020 (UTC)
|pregnancy_AU_comment=
used for anything other than as a reference? If not, then the space should be removed. If so, it might be worth looking into having a "comment" para and a "ref" para.
Primefac (
talk)
14:44, 2 August 2020 (UTC)
/^<ref/
to decide whether to render it without vs with space?|pregnancy_XX=
and |pregnancy_XX_comment=
is so that we can link to a country-specific section of
Pregnancy category. Given that the label already does that, we're just duplicating links. I say we drop the linking for |pregnancy_XX=
, and convert |pregnancy_XX_comment=
into |pregnancy_XX_ref=
for sole use as a reference.
Primefac (
talk)
21:28, 2 August 2020 (UTC)why it matters&tc: you lost me. What do yoo actually say or propose? - DePiep ( talk) 23:24, 2 August 2020 (UTC)
|pregnancy_US_comment=
to |pregnancy_US_ref=
and modify the subpage to avoid overlinking.
Primefac (
talk)
17:13, 5 August 2020 (UTC)
Primefac Are there plans to expand the letters when other text exists in the field? The recent edits that moved the text from the |pregnancy_US_comment=
field into the |pregnancy_US=
field prevent the expansion of the specified letter. For example,
this edit:
before
Pregnancy category
AU: A(when used topically)
US: C (Risk not ruled out)(for topical use)
after
Pregnancy category
AU: A (when used topically)
US: C (for topical use)
There were other edits that eliminated the expansion of one of the letters. for example -- Whywhenwhohow ( talk) 01:28, 21 August 2020 (UTC)
The following change log (here with more standardized date formatting) was originally being kept inside the template code itself:
Changes:
<br />
, use /formatX subtemplates, use standard formatting, rename some index params (hard removal)I've moved it to the talk page, since injecting material like this directly into templates is abnormal and not useful, as well being a parsing burden. Talk pages (in which one can link and format) exist for a reason, and so does the edit-history feature. @
DePiep and
Primefac: pinging known-interested editors. PS: If it is desired to keep this as a perpetual running list, see similar solution at the top of
WT:MOS, including "archive bot defeater". Another solution is using {{
To do}}
:
{{To do |To-do=Log of significant changes |collapsed=yes |inner= * List * Items * Here }}
— SMcCandlish ☏ ¢ 😼 16:40, 5 August 2020 (UTC) Pinging also Izno, who chimed in on the original thread, but I didn't notice until now. Has related tracking ideas for the citation templates. — SMcCandlish ☏ ¢ 😼 16:50, 5 August 2020 (UTC)
Off-topic behavioral discussion that belongs in userspace and has already been hashed out there.
|
---|
|
I have copied the Log to header, thread be archived as usual. - DePiep ( talk) 19:11, 12 September 2020 (UTC)
The CA, EU, and US FDA license links are broken. It looks like the CA one is no longer displayed. We should disable or fix the others. What about adding one for AU?
Are there plans to fix |licence_CA=
? It not, the documentation should be updated to remove |licence_CA=
and/or indicate that it is disabled.
It looks like the link for |licence_US=
needs to be implemented as a POST request. Can that be done in a Wikipedia template? See
US license Drugs@FDA links no longer work in the archives.
The EMA can be searched using something like https://www.ema.europa.eu/en/medicines/ema_group_types/ema_medicine/search_api_aggregation_ema_active_substance_and_inn_common_name/tadalafil and EPARs can be directly accessed using the brand name https://www.ema.europa.eu/en/medicines/human/EPAR/cialis
There are CA search options at https://health-products.canada.ca/dpd-bdpp/index-eng.jsp and https://health-products.canada.ca/noc-ac/index-eng.jsp but it looks like they require using POST.
The AU ARTG can be searched using something like https://tga-search.clients.funnelback.com/s/search.html?query=Tadalafil&collection=tga-artg or just the PI and CMI can be searched using something like https://www.ebs.tga.gov.au/ebs/picmi/picmirepository.nsf/PICMI?OpenForm&t=pi&q=Tadalafil
-- Whywhenwhohow ( talk) 05:57, 21 August 2020 (UTC)
|licence_US=
with the application number in the infobox.|licence_UK=
too. It uses an ID in the URL|licence_XX=
, |license_XX=
(so -c- and -s- are equally usable, whatever the formal ENGVAR)|DailyMedID=
related to the license? Or is it consumer info? IOW, do we have to keep |DailyMedID=
within this discussion? -
DePiep (
talk)
20:22, 12 September 2020 (UTC)The AU ARTG can be searched using something like https://tga-search.clients.funnelback.com/s/search.html?query=Tadalafil&collection=tga-artg or just the PI and CMI can be searched using something like https://www.ebs.tga.gov.au/ebs/picmi/picmirepository.nsf/PICMI?OpenForm&t=pi&q=Tadalafil
— Whywhenwhohow
|license_AU=
). However, since neither
Australian Register of Therapeutic Goods nor
ARTG exist (redlinks now), there is no need to consider this. The question can be reopened when the article exists. (Then I will raise the question: by what criteria do we include any of the ~200 countries?). -
DePiep (
talk)
20:26, 12 September 2020 (UTC)There are CA search options at https://health-products.canada.ca/dpd-bdpp/index-eng.jsp and https://health-products.canada.ca/noc-ac/index-eng.jsp but it looks like they require using POST.
— Whywhenwhohow
The EMA can be searched using something like https://www.ema.europa.eu/en/medicines/ema_group_types/ema_medicine/search_api_aggregation_ema_active_substance_and_inn_common_name/tadalafil and EPARs can be directly accessed using the brand name https://www.ema.europa.eu/en/medicines/human/EPAR/cialis
— Whywhenwhohow
It looks like the link for
|licence_US=
needs to be implemented as a POST request. Can that be done in a Wikipedia template? See US license Drugs@FDA links no longer work in the archives.— Whywhenwhohow
AMLODIPINE BESYLATE AND ATORVASTATIN CALCIUM ATORVASTATIN CALCIUM CADUET EZETIMIBE AND ATORVASTATIN CALCIUM LIPITOR LIPTRUZET
The infobox does not recognize values like C1, C2, C3, C4 in the {{{legal_AU}}}
parameter for Class 1, 2, 3, or 4 biologicals.
https://www.tga.gov.au/classification-biologicals -- Whywhenwhohow ( talk) 21:58, 16 September 2020 (UTC)
The template doesn't accept more than five component/class parameters type=combo. It would be useful to support at least six. The hexavalent vaccine contains six components. -- Whywhenwhohow ( talk) 16:47, 1 October 2020 (UTC)
Error in template * unknown parameter name (Template:Infobox_drug): 'UNII3; UNII5; index3_label; index4_label; UNII4; UNII5_Ref; UNII3_Ref; index5_label; UNII4_Ref'
The RCSB PDB links appears to be broken.
For example, for F9E it generates the following URL which fails to work.
It looks like the correct URL should something like this
https://www.rcsb.org/ligand/F9E
or this
https://www.rcsb.org/search?request={"query"%3A{"parameters"%3A{"value"%3A"F9E"}%2C"service"%3A"text"%2C"type"%3A"terminal"%2C"node_id"%3A0}%2C"return_type"%3A"entry"%2C"request_options"%3A{"pager"%3A{"start"%3A0%2C"rows"%3A100}%2C"scoring_strategy"%3A"combined"%2C"sort"%3A[{"sort_by"%3A"score"%2C"direction"%3A"desc"}]}%2C"request_info"%3A{"src"%3A"ui"%2C"query_id"%3A"b02260d062ec5ebd59379efff3f54409"}}
-- Whywhenwhohow ( talk) 03:06, 24 October 2020 (UTC)
The F9E example I provided above is for
Valganciclovir. For MDMA, the second one (RCSB PDB) should be
https://www.rcsb.org/ligand/B41
or
https://www.rcsb.org/search?request={"query"%3A{"parameters"%3A{"value"%3A"B41"}%2C"type"%3A"terminal"%2C"service"%3A"text"%2C"node_id"%3A0}%2C"return_type"%3A"entry"%2C"request_options"%3A{"pager"%3A{"start"%3A0%2C"rows"%3A100}%2C"scoring_strategy"%3A"combined"%2C"sort"%3A[{"sort_by"%3A"score"%2C"direction"%3A"desc"}]}%2C"request_info"%3A{"src"%3A"ui"%2C"query_id"%3A"246d5e4721efa28968e77026dc51de67"}}
For Paracetamol, the second one (RCSB PDB) should be
https://www.rcsb.org/ligand/TYL
or
https://www.rcsb.org/search?request={"query"%3A{"parameters"%3A{"value"%3A"TYL"}%2C"type"%3A"terminal"%2C"service"%3A"text"%2C"node_id"%3A0}%2C"return_type"%3A"entry"%2C"request_options"%3A{"pager"%3A{"start"%3A0%2C"rows"%3A100}%2C"scoring_strategy"%3A"combined"%2C"sort"%3A[{"sort_by"%3A"score"%2C"direction"%3A"desc"}]}%2C"request_info"%3A{"src"%3A"ui"%2C"query_id"%3A"9228d1d289499c18e4c10fe3bb429ff3"}}
-- Whywhenwhohow ( talk) 08:44, 24 October 2020 (UTC)
https://www.rcsb.org/search?request={"query":{"parameters":{"value":"F9E"},"service":"text","type":"terminal","node_id":0},"return_type":"entry","request_options":{"pager":{"start":0,"rows":100},"scoring_strategy":"combined","sort":[{"sort_by":"score","direction":"desc"}]},"request_info":{"src":"ui","query_id":"b02260d062ec5ebd59379efff3f54409" }}
(
link)This
edit request to
Template:Infobox drug has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Please replace all live code with /sandbox code (two templates):
DePiep ( talk) 00:12, 27 October 2020 (UTC)
On articles that have both {{
Chembox}} and {{
Infobox drug}}, lots of the "chemical" fields are omitted from the drugbox to avoid duplication and keep content where it is most relevent. But drugbox also tracks certain missing fields, including some that get deffered to the chembox in these cases. That pollutes the tracking categories for things that are intentionally not to be done. For example,
Niacin has the chemical structure and CASNo in the chembox and therefore blank fields {{
Infobox drug|image=|CAS_number=}}
, which triggers the article to be listed in
Category:Infobox drug articles without a structure image and
Category:Chemical articles without CAS registry number, respectively.
We had a similar problem in Chembox when it was a secondary infobox, and in June,
User:DePiep implemented
{{
Chembox|container_only=yes}}
to stop whining about intentionally-missing fields (see
Template talk:Chembox#Field to indicate only partial infobox). I propose a similar flag here for the drugbox.
DMacks (
talk)
03:29, 2 October 2020 (UTC)
This
edit request to
Template:Infobox drug has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Please perform these two edits:
|container_only=
per
this talk; will populate new
Category:Infobox drug container onlyDiscussion & consensus: this talk (following {{ Chembox}} in this)
Tested: see /testcases9 and Niacin live (by preview)
Post-edit check: the demo article is Niacin. One can check this article, right after these edits, for any disruption.
|container_only=y
will inhibit all tracking of missing fields, which means |legal_*=
, |ATC_=
, and |license_*=
among others. I don't think that is the correct behavior, because those fields would not be covered by {{
chembox}}.
DMacks (
talk)
19:26, 18 October 2020 (UTC)
|container_only=yes
proposal here suppresses most if not all of the generic chemicals & CheMoBot trackings. Meanwhile, in Drugbox detailed cat reportings like "EMA" input issues are tracked, which seems OK to me.|container only=yes
. I cannot exactly reproduce the {{Chembox}} handling, because Chembox is more complicated and anyway, when using the template this way there is a bit of "you're on your own" consequence. {{Infobox drug}} however we can fine-tune. This is what the sandboxes have now:|container only=
.|Legal_US=
when there is an issue with its actual input).|CAS number_Ref=
: as intended, and not added anyway if CAS number is absent so no undesired effect).|container only=yes
. See the -xxx->
lines that cancelles (=comments out) categories.This
edit request to
Template:Infobox drug has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Please perform these two edits:
|container_only=
per
this talk; will populate new
Category:Infobox drug container onlyDiscussion & consensus: Following {{ Chembox}} in this. See #this talk and #this withdrawn request with extended discussion. @ DMacks:.
Tested: see /testcases9 and Niacin live (by preview)
Post-edit check: the demo article is Niacin. One can check this article, right after these edits, for any disruption. DePiep ( talk) 14:54, 7 November 2020 (UTC)
Hey. I know jack shit about this subject, but I noticed that the code for calculating whether to show the metabolism parameter checks for the parameters {sources} and {targets} despite neither appearing anywhere else in the infobox code. I'm 99% sure that it's the {source_tissues} and {target_tissues} parameters that someone just forget to rename thoroughly. I don't have editing permissions - can someone who has please confirm that this is the case and then fix the code? -- Metalindustrien ( talk) 19:59, 9 November 2020 (UTC)
Background: parameters involved
|
---|
<!-- type=mab: ----- ----- --> | type = mab | mab_type = | source = | target = <!-- Physiological data --> | source_tissues = | target_tissues = ... | metabolism = <!-- same parameter as in pharmacokinetic data -->
|
|source_tissues, target_tissues=
in there, lists 10 articles). It appears that, in spite of the two misnamed parameters, the #if-clause in |data58=
does fire correctly because of other parameters having data. So, at the moment no errors in articles. Of course, we will fix the issue. -
DePiep (
talk)
20:00, 10 November 2020 (UTC)This
edit request to
Template:Infobox drug has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Please replace all live code with /sandbox code:
Change: replace |
, sources=|
with targets=|source_tissues=
, |target_tissues=
. Replace non-existant parameter names.
Talk & test: Old code error. See above #Is sources ... source_tissues ... ?; F3 and visual checks. h/t @ Metalindustrien: DePiep ( talk) 23:10, 19 November 2020 (UTC)
This
edit request to
Template:Infobox drug has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Hi, could anyone with the ability to edit this template be so kind to add the legal statuses for legal_SG (Singapore)? I think it would be really useful and once added I will start adding the appropriate legal classes/schedules onto the most common drugs/medications. It will be based upon the Misuse of Drugs Act (OTC, Rx-only, Schedule I, II, III or Unscheduled) first enacted in 1973. Thank you! BelfastBrooks ( talk) 08:07, 2 December 2020 (UTC)
|legal_SG=
|legal_SG_comment=
|legal_SG=otc / prescription only, rx-only, rx only / s1, schedule i, schedule 1 / s2, schedule ii, schedule 2 / s3, schedule iii, schedule 3
. Not recognised →
Category:Drugs with non-standard legal status under "G".|legal_SG_comment=any text
, will show unedited after a space (consider using brackets).Meanwhile, editor can discuss appropriateness of this proposal (for example, which of the ~200 countries should be added this way?)I think this is an important point. I'm guessing we list options for the countries which are most popular amongst readers, but that's just a guess. Obviously we couldn't (and shouldn't) list it for every country on the map. Does an inclusion criteria for this label already exist? ProcrastinatingReader ( talk) 18:12, 3 December 2020 (UTC)
The {{ Infobox drug/formatUNII}} formatter URL currently differs from the UNII (P652) formatter URL. This infobox appears less correct. int21h ( talk · contribs · email) 04:42, 15 December 2020 (UTC)
Obviously, the enwiki url is redirected to the WD url, so the change is due. Will make the editrequest. - DePiep ( talk) 13:53, 16 December 2020 (UTC)
This
edit request to
Template:Infobox drug has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Please put all code from in {{ Infobox drug/formatUNII/sandbox}} into {{ Infobox drug/formatUNII}} (full replacement), diff.
Change, talk & test: External link URL format updated. See #UNII formatter URL above. ping @ Int21h: DePiep ( talk) 13:58, 16 December 2020 (UTC)
We should remove the |pregnancy_US=
parameter since the
FDA doesn't use letter categories any longer. They were replaced by the Pregnancy and Lactation Labeling Final Rule (PLLR). Here is an excerpt from Drugs.com:
Prescription drugs submitted for FDA approval after June 30, 2015 will use the new format immediately, while labeling for prescription drugs approved on or after June 30, 2001 will be phased in gradually. Medications approved prior to June 29, 2001 are not subject to the PLLR rule; however, the pregnancy letter category must be removed by June 29, 2018. For generic drugs, if the labeling of a reference listed drug is updated as a result of the final rule, the abbreviated new drug application (ANDA) labeling must also be revised. Labeling for over-the-counter (OTC) medicines will not change, as OTC drug products are not affected by the new FDA pregnancy labeling.
By the way, when 'N' is used for |pregnancy_US=
, the text "US: N (Not classified yet)" appears in the infobox. The "yet" should be removed. It is confusing to readers and some editors try to find the category to use to replace the 'N'. --
Whywhenwhohow (
talk)
20:35, 28 December 2020 (UTC)
|PLLR=
, free text input (
label link). Was added 2015, see also
this talk.|Pregnancy_US=
1315 articles (mainspace)|PLLR=
0 articles (mainspace)|pregnancy_category=
instead of |pregnancy_US=
. I think it makes sense to remove |pregnancy_US=
, |pregnancy_US_comment=
, |pregnancy_category=
, and |PLLR=
. Australia still assigns category letters to medicines. --
Whywhenwhohow (
talk)
00:12, 29 December 2020 (UTC)
|pregnancy_US=
, |pregnancy_US_comment=
, |PLLR=
. Their input will not be shown at all. The comment usually refers to the Code too. (Will not remove them from the infobox in articles). -
DePiep (
talk)
00:46, 29 December 2020 (UTC)
|pregnancy_US_comment=
is used as a reference input (added unspaced). Todo: {{
Chembox}} too. -
DePiep (
talk)
21:35, 29 December 2020 (UTC)This
edit request to
Template:Infobox drug has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Please replace all code with all sandbox code, in these two templates:
Changes, talk and test: See § Pregnancy US parameter; US pregnancy category code abolished, so no showing. /testcases3. DePiep ( talk) 11:42, 29 December 2020 (UTC)
FYI, DrugBank changed domains from drugbank.ca to drugbank.com. -- Whywhenwhohow ( talk) 04:21, 27 January 2021 (UTC)
The official website is now
https://www.drugbank.com/ and any drug detail pages using the hostname www.drugbank.ca
are redirected to use the hostname go.drugbank.com
. For example, Asprin was at
https://www.drugbank.ca/drugs/DB00945 and is now at
https://go.drugbank.com/drugs/DB00945. The only changes to the URL appear to be changing www.drugbank.ca
to go.drugbank.com
.
Do we support using |Drugbank=
for uses other than drugs? For example, here is a sample target and a sample indication.
The use of "r" for resolve appears to be old. For example, using https://www.drugbank.ca/r/DB00945 for Asprin is the same as using https://www.drugbank.ca/drugs/DB00945 and is now at https://go.drugbank.com/drugs/DB00945.
-- Whywhenwhohow ( talk) 05:05, 28 January 2021 (UTC)
Is |Drugbank=
used in the {{
Chembox}}? If so, it would need to be updated too. --
Whywhenwhohow (
talk)
05:09, 28 January 2021 (UTC)
Another use is for salts but using drugs in the URL redirects to the salts. Using any of these
redirects to here
-- Whywhenwhohow ( talk) 05:21, 28 January 2021 (UTC)
This
edit request to
Template:Infobox drug has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Please replace all code {{ Infobox drug}} ← {{ Infobox drug/sandbox}} ( diff).
Suppose I want to know more about Viagra, I search with the term viagra because that's the WP:COMMONNAME. I find that the title page is Sildenafil and it's the first name suggested in the first sentence, if I wish to find information about the origin of Sildenafil, the infobox shows that it is the name used by the FDA, and that it appears in the chemical nomenclature of its metabolite, but nothing else, I suspect the name comes from the FDA, but I cannot be sure. I assumes that Sildenafil is "the official name", but I might be skeptic about the notion of a single offical name.
I tried to add a line " INN = Sildenafil" but that just causes a tooltip to appear beneath the title of the infobox, since they are both the same, it looks weird.
I understand that by default, the policy is to name the article according to the INN, but this is not transparent to most users, who cannot navigate through wikipedia's policy to finally understand that the name comes from this thing called the INN.
If I could just add a field "INN= Sildenafil" to the infobox, it would make the naming convention explicit, and it would allow regular users to explore the concept of INN. It would also allow editors to add sources regarding INN nomenclature.
Thank you for your time.-- TZubiri ( talk) 05:15, 14 August 2020 (UTC)
See this discussion about redisigning {{Infobox drug}} at WT:MED: § A slimmer, more reader-friendly drugbox?. - DePiep ( talk) 22:24, 30 January 2021 (UTC)
<revived discussion;
It is extremely useful to know date that patents are issued. Please consider adding this to the drug box. — Preceding unsigned comment added by 63.247.31.113 ( talk) 23:50, 28 July 2011 (UTC)
is there no website that lists drugs patent date in the USA? then you could just link to it as an external link. The drug box is faster for doctors than reading a history. i hope you reconsider and add it to the drug box. — Preceding unsigned comment added by 63.247.31.123 ( talk) 22:04, 12 August 2011 (UTC)
What's going on with this? I search the page and there isn't even a mention of 'generic' or 'patent' to add this info manually. Let's do something that's better than nothing.
This
edit request to
Template:Infobox drug has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Add field year1stPatentEnds to the template. Feel free to be more ambitious, but I'm just requesting a simple static field that accepts a number. 50.201.195.170 ( talk) 20:22, 5 February 2021 (UTC)
{{
edit template-protected}}
template. From an inclusion standpoint, sure, patent status seems as encyclopedic as other legal status, i.e. whether controlled in various countries. Invention/discovery date seems important enough to feel like an omission to me. But it seems there are practical (evergreening) and possibly npov (worldwide point of view) considerations that need to be fleshed out in more detail.
Matt Fitzpatrick (
talk)
03:22, 20 February 2021 (UTC)Consider adding the other name fields too.
Australian Approved Name (AAN)
Australian Biological Name (ABN)
Australian Cell and Tissue Name (ACN)
A botanical name for a herb (AHN)
A herbal substance Name (AHS)
For example, the ABN for the newly approved COVID-19 Vaccine AstraZeneca is ChAdOx1-S. -- Whywhenwhohow ( talk) 05:50, 17 February 2021 (UTC)
|AAN=
, BAN, JAN, USAN.|synonyms=
field. In my mind that would typically be a better place to list national/regional names than having a separate field for each? That would give page editors a bit more flexibility to pick the relevant synonyms for each? But maybe an example or two would help make things clearer for me.|synonyms=
field may be used for those too. An ABN is just like an AAN and is assigned instead of an AAN for a specific class of therapeutic goods. COVID-19 Vaccine AstraZeneca has an ABN instead of an AAN. --
Whywhenwhohow (
talk)
05:57, 24 February 2021 (UTC)
|synonyms=
field, and then to update the documentation accordingly. Perhaps the documentation page could link to the gov't databases of names so an editor could quickly check the names from each when they're setting up an article on a new drug? I assume the AAN, BAN, JAN, etc. are sometimes the same?
Ajpolino (
talk)
06:36, 25 February 2021 (UTC)
The documentation examples state that the vaccine target is the antigen/bacteria/toxin/virus to protect against
in the comments but the infobox labels the field as Target disease
. The label in the infobox is incorrect since the vaccine targets the cause of the disease, not the disease itself. Please remove disease from the infobox label. Thank you. --
Whywhenwhohow (
talk)
04:21, 1 March 2021 (UTC)
@ DePiep: Alemtuzumab is not a vaccine. Here are some mixed examples
Target disease influenza virus
Target disease Cholera
Target disease Corynebacterium diphtheriae
Target disease Haemophilus influenzae type b
Target disease Neisseria meningitidis
Target disease Whooping cough
Target disease Ebola virus
Target disease Hepatitis A
Target disease Hepatitis B virus
Target disease Human papillomavirus (HPV)
Target disease Measles virus
Target disease Poliomyelitis
-- Whywhenwhohow ( talk) 02:08, 2 March 2021 (UTC)
This
edit request to
Template:Infobox drug has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Change: fix label5 text, per request #Vaccine target. DePiep ( talk) 13:13, 2 March 2021 (UTC)
I would like to propose these new fields for storage conditions:
| storage_conditions = | storage_temperature = | storage_humidity = | storage_dark =
To be rendered as:
| label1 = Storage conditions | data1 = {{{storage_conditions|}}} | header2 = {{#if:{{{storage_temperature|}}}{{{storage_humidity|}}}{{{storage_dark|}}}|Storage conditions}} | label3 = Temperature | data3 = {{{storage_temperature|}}} | label4 = Relative humidity | data4 = {{{storage_humidity|}}} | label5 = Light level | data5 = {{#switch:{{lc:{{{storage_dark|}}}}} | yes = Dark | no = Any | #default = {{{storage_dark}}} }}
The storage_conditions field would be used for short or non-standard descriptions, otherwise the other fields would be preferred. Usage examples:
Storage conditions | Cold, dry, dark |
---|
| storage_conditions = Cold, dry, dark
Storage conditions | 5 °C, 50% RH, dark |
---|
| storage_conditions = 5 °C, 50% RH, dark
Storage conditions | 2-8 °C, 40-60% RH, dark |
---|
| storage_conditions = 2-8 °C, 40-60% RH, dark
Storage conditions | Ambient |
---|
| storage_conditions = Ambient
Storage conditions | Dry |
---|
| storage_conditions = Dry
Storage conditions | |
---|---|
Temperature | Cold |
Relative humidity | Dry |
Light level | Dark |
| storage_temperature = Cold | storage_humidity = Dry | storage_dark = yes
Storage conditions | |
---|---|
Temperature | 2-8 °C |
Relative humidity | <60% |
Light level | No sunlight |
| storage_temperature = 2-8 °C | storage_humidity = <60% | storage_dark = No sunlight
Storage conditions | |
---|---|
Temperature | 2–8 °C (36–46 °F) |
Relative humidity | 40-60% |
Light level | Avoid light |
| storage_temperature = 2–8 °C (36–46 °F) | storage_humidity = 40-60% | storage_dark = Avoid light
Storage conditions | |
---|---|
Temperature | Ambient |
| storage_temperature = Ambient
Storage conditions | |
---|---|
Relative humidity | <60% |
| storage_humidity = <60%
Drug specifications vary slightly depending on the country. For example, it is unusual to specify a lower humidity limit, even when it has one, because low humidity is rare in many regions. For drugs with less stringent requirements, it is common to provide only a description instead of specific values for temperature and humidity. Most medications should be kept out of direct sunlight and light in general, so non-default values for storage_dark should be rare.
What do you think? -- Fernando Trebien ( talk) 16:11, 14 March 2021 (UTC)
This is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |
Archive 15 | Archive 16 | Archive 17 | Archive 18 | Archive 19 |
What is GoodRx and why should we add it to the drugbox?
| ||
---|---|---|
As for what GoodRx is, their support page probably explains it best:
As for why we should add it to the drugbox:
See this Google search for the string 'insulin cost United States death' and just pick any article (e.g., [1], [2] [3]) In a nutshell, they all say the same thing: the rising prices of insulin analogs in the United States has made it prohibitively costly for some people to fill a prescription for one of those drugs. The clinical efficacy of insulin analogs for diabetes is completely irrelevant if people can't afford to buy them. The news articles from the google search and the examples I provided all say that insulin analogs (nearly all of which cost >$300 out of pocket per the news articles and from checking every link in GoodRx's insulins drug category page; NB: the prices listed next to the drugs on that page are "GoodRx fair prices", not the lowest price with their coupons) are prohibitively costly for diabetics without health insurance; some ration their insulin and/or don't fill prescriptions, and in some cases doing that has led to diabetic ketoacidosis and resulted in death, as stated in those sources. The majority of those articles specifically mention prices for various dosage forms of brand name or generic Humalog (insulin lispro), which is the cheapest short-acting insulin analog (NB: none of those articles mention GoodRx or online drug coupons). If you compare the prices for brand name Humalog/generic insulin lispro mentioned in the sources to the retail prices on GoodRx's generic Humalog page, you'll notice they're more-or-less the same as what's listed there, but GoodRx's Coupons for generic Humalog discount the retail price by ~60% for all three dosage forms (i.e., the kwikpen, carton, and vial). In other words, if someone with diabetes lacks insurance and can only afford to pay a certain $ amount out of pocket for generic Humalog each month due to financial constraints, using GoodRx Coupons will more than double their purchasing power of insulin lispro at that $ amount (i.e., with GoodRx coupons, a consumer with a limited/fixed budget can buy approximately 2.5 times as much insulin lispro for the same total cost as they could without those coupons). That increase in purchasing power could very well obviate the need for a person to ration insulin or forego their prescriptions, thereby mitigating the ketoacidosis risk.
This is a study of prescription drug economics/cost-minimization conducted by USC that used GoodRx data+coupons; I've quoted all of the relevant content from this source on GoodRx below. [1] It's not the only pubmed-indexed article that used GoodRx data for research purposes (e.g., PMID 28895827, 30796990), but it's the only one I've come across that analyzed the utility of GoodRx for prescription drug cost minimization in the United States. It's worth reading the excerpts below IMO.
|
Following up on Talk:Epinephrine (medication)#Cost information in the United States, what do others think of placing a GoodRx link in the drugbox template? We could use a left-hand side field as "US consumer prices" and the RHS could just link directly to the corresponding GoodRx webpage(s) listed on Wikidata for an article (that'd require creating an identifier property for GoodRx). I'd be willing to add the corresponding identifiers to all of the Wikidata entries on prescription drugs listed on the GoodRx website with a bot if there's consensus to do add it to the drugbox. Seppi333 ( Insert 2¢) 18:49, 11 August 2019 (UTC)
Chemical and physical data | |
---|---|
Formula | C9H13NO |
Molar mass | 151.209 g·mol−1 |
[GoodRx_url Pagename_of_Drug_product]
; e.g.,
Amphetamine Salt Combo,
Amphetamine Salt Combo XR,
Mydayis,
Adzenys XR-ODT,
Dyanavel XR,
Amphetamine Sulfate,
Dexedrine Spansule,
Zenzedi,
Lisdexamfetamine. Those products and links are the same ones from this table:
Amphetamine#Pharmaceutical products.
Seppi333 (
Insert 2¢)
07:33, 12 August 2019 (UTC)The first is that I imagine a lot of readers will have no clue what happened to every drugbox on Wikipedia if we suddenly cut them in half without providing some kind of indication of what we did with the other half of the drugbox data (it's not like they're going to know we've moved it to an EL section and I doubt most of them will scroll all the way to the bottom of the article to try to find what we did with it). The second is that all of those links are still very much pertitent to the Drugbox even after being split out, so there should be a means of navigating to them quickly within the Drugbox (this is analogous to the "Supplementary data page" link in the chembox)." – I meant it at face value. We're going to cut the drugbox in two and keep the appearance identical; and, that's why that there's going to be a link from the drugbox at the top of the page to the External data half at the bottom. Seppi333 ( Insert 2¢) 22:58, 14 August 2019 (UTC)
Clinical data | |
---|---|
License data | |
../licence/sandbox | |
License data |
@ Bluerasberry and DePiep: I've added a lengthy explanation about what GoodRx is, the services it provides, the motivation for adding this link to the drugbox, and clearly illustrated the utility of GoodRx to consumers with 2 examples. I strongly suggest reading all of it; but, at the very least, just read the quoted excerpts from the journal citation.
Clinical data and identifiers parameters
|
---|
<!-- Clinical data --> | Drugs.com = | MedlinePlus = | licence_CA = <!-- Health Canada may use generic or brand name (generic name preferred) --> | licence_EU = <!-- EMA uses INN (or special INN_EMA) --> | DailyMedID = <!-- DailyMed may use generic or brand name (generic name preferred) --> | licence_US = <!-- FDA may use generic or brand name (generic name preferred) --> | ATC_prefix = <!-- 'none' if uncategorised --> | ATC_suffix = <!--Identifiers--> | CAS_number = | PubChem = | PubChemSubstance = | IUPHAR_ligand = | DrugBank = | ChemSpiderID = | UNII = | KEGG = | ChEBI = | ChEMBL = | NIAID_ChemDB = | PDB_ligand = |
oppose. I'd agree if the price was listed, with GoodRx as the reference but not with a straight up link. While I agree this is in the public good for US citizens (as already pointed out) I see a lot of dangers. (1) I can't find precedent for including a for-profit link in the infobox (I equate this (from a philosophical point of view) to having the IMDB or Rotten Tomato link in the infobox of a movie), but I think much of the general community would oppose. (2) Their profit model could change, without disclosure, and we could be giving bad and unverifiable information. (3) Their methods seem to be bit of a black box; we can't independently verify accuracy or that they're unbiased (4) There may be bias in the way information is presented (e.g. the referral fees or advertising that is not well marked as such) (5) very specific to the US. Overall; I like the idea as a public service but oppose it because it's easily corruptible by the company and it gives them a significant, and unfair advantage over anyone else that may be providing the same or similar services. Ian Furst ( talk) 19:06, 20 August 2019 (UTC)
{{External links list|GoodRx= [https://www.goodrx.com/amphetamine-salt-combo Adderall], [https://www.goodrx.com/amphetamine-salt-combo-xr Adderall XR], [https://www.goodrx.com/amphetamine-sulfate Evekeo]| MedlinePlus = a616004 | license_US = amphetamine | licence_EU = yes | INN_EMA = amphetamine | Drugs.com = {{Drugs.com|parent|amphetamine}}| ATC_prefix = N06| ATC_suffix = BA01| CAS_number_Ref = {{cascite|correct|CAS}} | CAS_number = 300-62-9 | PubChem = 3007 | IUPHAR_ligand = 4804 | DrugBank_Ref = {{drugbankcite|correct|drugbank}} | DrugBank = DB00182 | ChemSpiderID_Ref = {{chemspidercite|correct|chemspider}} | ChemSpiderID = 13852819 | UNII_Ref = {{fdacite|correct|FDA}} | UNII = CK833KGX7E | KEGG_Ref = {{keggcite|correct|kegg}} | KEGG = D07445 | ChEBI_Ref = {{ebicite|correct|EBI}} | ChEBI = 2679 | ChEMBL_Ref = {{ebicite|correct|EBI}} | ChEMBL = 405 | NIAID_ChemDB = 018564 | PDB_ligand = 1WE| smiles = NC(CC1=CC=CC=C1)C}}
[[#External links|External data]]
or [[#External data|External data]]
provided that I add {{
Anchor|External data}}
to the heading of the new template) at the bottom of the Drugbox for two reasons. The first is that I imagine a lot of readers will have no clue what happened to every drugbox on Wikipedia if we suddenly cut them in half without providing some kind of indication of what we did with the other half of the drugbox data (it's not like they're going to know we've moved it to an EL section and I doubt most of them will scroll all the way to the bottom of the article to try to find what we did with it). The second is that all of those links are still very much pertitent to the Drugbox even after being split out, so there should be a means of navigating to them quickly within the Drugbox (this is analogous to the "Supplementary data page" link in the chembox).In the end result, we should not use meta {{ Infobox}}.And why is that, exactly? I made it clear earlier that I still consider all of these external links to be part of the drugbox even after splitting them out, hence the use of an infobox with an identical appearance; we're simply moving them to the EL section since it's just as appropriate to place them there as it is in Drugbox template itself. Seppi333 ( Insert 2¢) 06:37, 16 August 2019 (UTC)
{{
Infobox}}
to style its contents does not make it an infobox. E.g., {{
Glossary infobox}}
is a back-end template for {{
Addiction glossary}}
and {{
Transcription factor glossary}}
, yet neither of those should be used in place of an actual infobox for an article. Edit: that back-end template was created following this discussion:
Template_talk:Addiction_glossary#"Glossary skeleton" template.
Seppi333 (
Insert 2¢)
06:54, 16 August 2019 (UTC)
class=infobox
(as {{Infobox}} does}}). class
defines loads of behaviour, layout, formatting, presentation (responsive even). Our intentions do not count in a browser. We do not want those effects, that would be bad coding and bad information handling. -
DePiep (
talk)
09:24, 16 August 2019 (UTC){{
Drugbox external links}}
instead of {{
Infobox drug/sandbox2}}
to generate the example.
Seppi333 (
Insert 2¢)
06:54, 16 August 2019 (UTC){{Drugbox external links|GoodRx= [https://www.goodrx.com/amphetamine-salt-combo Adderall, [https://www.goodrx.com/amphetamine-salt-combo-xr Adderall XR, [https://www.goodrx.com/amphetamine-sulfate Evekeo| MedlinePlus = a616004 | license_US = amphetamine | licence_EU = yes | INN_EMA = amphetamine | Drugs.com = {{Drugs.com|parent|amphetamine}}| ATC_prefix = N06| ATC_suffix = BA01| CAS_number_Ref = {{cascite|correct|CAS}} | CAS_number = 300-62-9 | PubChem = 3007 | IUPHAR_ligand = 4804 | DrugBank_Ref = {{drugbankcite|correct|drugbank}} | DrugBank = DB00182 | ChemSpiderID_Ref = {{chemspidercite|correct|chemspider}} | ChemSpiderID = 13852819 | UNII_Ref = {{fdacite|correct|FDA}} | UNII = CK833KGX7E | KEGG_Ref = {{keggcite|correct|kegg}} | KEGG = D07445 | ChEBI_Ref = {{ebicite|correct|EBI}} | ChEBI = 2679 | ChEMBL_Ref = {{ebicite|correct|EBI}} | ChEMBL = 405 | NIAID_ChemDB = 018564 | PDB_ligand = 1WE| smiles = NC(CC1=CC=CC=C1)C}}
class=infobox
, responsive behaviour). I therefor created:|align=right
would be desirable.
Seppi333 (
Insert 2¢)
10:43, 16 August 2019 (UTC)
@ Primefac, DMacks, Doc James, Seppi333, DePiep, and Sceptre: Recent editors: Greetings and felicitations. In both the Australian and the US "Pregnancy category" fields, there is a space between the category and the comment, e.g. in the Ibuprofen article, at least when it is used to add a reference. Unfortunately, I can't see where the problem is, even after checking the sub-templates. Would someone please be so kind as to fix this, or tell what other change should be made? — DocWatson42 ( talk) 04:38, 2 August 2020 (UTC)
|pregnancy_AU_comment=
(and so |pregnancy_US_comment=
) can be used for comment (=add space) and reference (=no space). At the moment, distinguishing between those options is not possible or implemented.|pregnancy_AU_ref=
(cumbersom for editor), or enter like |pregnancy_AU=C<ref>...</ref>
. -
DePiep (
talk)
09:30, 2 August 2020 (UTC)
|pregnancy_AU_comment=
used for anything other than as a reference? If not, then the space should be removed. If so, it might be worth looking into having a "comment" para and a "ref" para.
Primefac (
talk)
14:44, 2 August 2020 (UTC)
/^<ref/
to decide whether to render it without vs with space?|pregnancy_XX=
and |pregnancy_XX_comment=
is so that we can link to a country-specific section of
Pregnancy category. Given that the label already does that, we're just duplicating links. I say we drop the linking for |pregnancy_XX=
, and convert |pregnancy_XX_comment=
into |pregnancy_XX_ref=
for sole use as a reference.
Primefac (
talk)
21:28, 2 August 2020 (UTC)why it matters&tc: you lost me. What do yoo actually say or propose? - DePiep ( talk) 23:24, 2 August 2020 (UTC)
|pregnancy_US_comment=
to |pregnancy_US_ref=
and modify the subpage to avoid overlinking.
Primefac (
talk)
17:13, 5 August 2020 (UTC)
Primefac Are there plans to expand the letters when other text exists in the field? The recent edits that moved the text from the |pregnancy_US_comment=
field into the |pregnancy_US=
field prevent the expansion of the specified letter. For example,
this edit:
before
Pregnancy category
AU: A(when used topically)
US: C (Risk not ruled out)(for topical use)
after
Pregnancy category
AU: A (when used topically)
US: C (for topical use)
There were other edits that eliminated the expansion of one of the letters. for example -- Whywhenwhohow ( talk) 01:28, 21 August 2020 (UTC)
The following change log (here with more standardized date formatting) was originally being kept inside the template code itself:
Changes:
<br />
, use /formatX subtemplates, use standard formatting, rename some index params (hard removal)I've moved it to the talk page, since injecting material like this directly into templates is abnormal and not useful, as well being a parsing burden. Talk pages (in which one can link and format) exist for a reason, and so does the edit-history feature. @
DePiep and
Primefac: pinging known-interested editors. PS: If it is desired to keep this as a perpetual running list, see similar solution at the top of
WT:MOS, including "archive bot defeater". Another solution is using {{
To do}}
:
{{To do |To-do=Log of significant changes |collapsed=yes |inner= * List * Items * Here }}
— SMcCandlish ☏ ¢ 😼 16:40, 5 August 2020 (UTC) Pinging also Izno, who chimed in on the original thread, but I didn't notice until now. Has related tracking ideas for the citation templates. — SMcCandlish ☏ ¢ 😼 16:50, 5 August 2020 (UTC)
Off-topic behavioral discussion that belongs in userspace and has already been hashed out there.
|
---|
|
I have copied the Log to header, thread be archived as usual. - DePiep ( talk) 19:11, 12 September 2020 (UTC)
The CA, EU, and US FDA license links are broken. It looks like the CA one is no longer displayed. We should disable or fix the others. What about adding one for AU?
Are there plans to fix |licence_CA=
? It not, the documentation should be updated to remove |licence_CA=
and/or indicate that it is disabled.
It looks like the link for |licence_US=
needs to be implemented as a POST request. Can that be done in a Wikipedia template? See
US license Drugs@FDA links no longer work in the archives.
The EMA can be searched using something like https://www.ema.europa.eu/en/medicines/ema_group_types/ema_medicine/search_api_aggregation_ema_active_substance_and_inn_common_name/tadalafil and EPARs can be directly accessed using the brand name https://www.ema.europa.eu/en/medicines/human/EPAR/cialis
There are CA search options at https://health-products.canada.ca/dpd-bdpp/index-eng.jsp and https://health-products.canada.ca/noc-ac/index-eng.jsp but it looks like they require using POST.
The AU ARTG can be searched using something like https://tga-search.clients.funnelback.com/s/search.html?query=Tadalafil&collection=tga-artg or just the PI and CMI can be searched using something like https://www.ebs.tga.gov.au/ebs/picmi/picmirepository.nsf/PICMI?OpenForm&t=pi&q=Tadalafil
-- Whywhenwhohow ( talk) 05:57, 21 August 2020 (UTC)
|licence_US=
with the application number in the infobox.|licence_UK=
too. It uses an ID in the URL|licence_XX=
, |license_XX=
(so -c- and -s- are equally usable, whatever the formal ENGVAR)|DailyMedID=
related to the license? Or is it consumer info? IOW, do we have to keep |DailyMedID=
within this discussion? -
DePiep (
talk)
20:22, 12 September 2020 (UTC)The AU ARTG can be searched using something like https://tga-search.clients.funnelback.com/s/search.html?query=Tadalafil&collection=tga-artg or just the PI and CMI can be searched using something like https://www.ebs.tga.gov.au/ebs/picmi/picmirepository.nsf/PICMI?OpenForm&t=pi&q=Tadalafil
— Whywhenwhohow
|license_AU=
). However, since neither
Australian Register of Therapeutic Goods nor
ARTG exist (redlinks now), there is no need to consider this. The question can be reopened when the article exists. (Then I will raise the question: by what criteria do we include any of the ~200 countries?). -
DePiep (
talk)
20:26, 12 September 2020 (UTC)There are CA search options at https://health-products.canada.ca/dpd-bdpp/index-eng.jsp and https://health-products.canada.ca/noc-ac/index-eng.jsp but it looks like they require using POST.
— Whywhenwhohow
The EMA can be searched using something like https://www.ema.europa.eu/en/medicines/ema_group_types/ema_medicine/search_api_aggregation_ema_active_substance_and_inn_common_name/tadalafil and EPARs can be directly accessed using the brand name https://www.ema.europa.eu/en/medicines/human/EPAR/cialis
— Whywhenwhohow
It looks like the link for
|licence_US=
needs to be implemented as a POST request. Can that be done in a Wikipedia template? See US license Drugs@FDA links no longer work in the archives.— Whywhenwhohow
AMLODIPINE BESYLATE AND ATORVASTATIN CALCIUM ATORVASTATIN CALCIUM CADUET EZETIMIBE AND ATORVASTATIN CALCIUM LIPITOR LIPTRUZET
The infobox does not recognize values like C1, C2, C3, C4 in the {{{legal_AU}}}
parameter for Class 1, 2, 3, or 4 biologicals.
https://www.tga.gov.au/classification-biologicals -- Whywhenwhohow ( talk) 21:58, 16 September 2020 (UTC)
The template doesn't accept more than five component/class parameters type=combo. It would be useful to support at least six. The hexavalent vaccine contains six components. -- Whywhenwhohow ( talk) 16:47, 1 October 2020 (UTC)
Error in template * unknown parameter name (Template:Infobox_drug): 'UNII3; UNII5; index3_label; index4_label; UNII4; UNII5_Ref; UNII3_Ref; index5_label; UNII4_Ref'
The RCSB PDB links appears to be broken.
For example, for F9E it generates the following URL which fails to work.
It looks like the correct URL should something like this
https://www.rcsb.org/ligand/F9E
or this
https://www.rcsb.org/search?request={"query"%3A{"parameters"%3A{"value"%3A"F9E"}%2C"service"%3A"text"%2C"type"%3A"terminal"%2C"node_id"%3A0}%2C"return_type"%3A"entry"%2C"request_options"%3A{"pager"%3A{"start"%3A0%2C"rows"%3A100}%2C"scoring_strategy"%3A"combined"%2C"sort"%3A[{"sort_by"%3A"score"%2C"direction"%3A"desc"}]}%2C"request_info"%3A{"src"%3A"ui"%2C"query_id"%3A"b02260d062ec5ebd59379efff3f54409"}}
-- Whywhenwhohow ( talk) 03:06, 24 October 2020 (UTC)
The F9E example I provided above is for
Valganciclovir. For MDMA, the second one (RCSB PDB) should be
https://www.rcsb.org/ligand/B41
or
https://www.rcsb.org/search?request={"query"%3A{"parameters"%3A{"value"%3A"B41"}%2C"type"%3A"terminal"%2C"service"%3A"text"%2C"node_id"%3A0}%2C"return_type"%3A"entry"%2C"request_options"%3A{"pager"%3A{"start"%3A0%2C"rows"%3A100}%2C"scoring_strategy"%3A"combined"%2C"sort"%3A[{"sort_by"%3A"score"%2C"direction"%3A"desc"}]}%2C"request_info"%3A{"src"%3A"ui"%2C"query_id"%3A"246d5e4721efa28968e77026dc51de67"}}
For Paracetamol, the second one (RCSB PDB) should be
https://www.rcsb.org/ligand/TYL
or
https://www.rcsb.org/search?request={"query"%3A{"parameters"%3A{"value"%3A"TYL"}%2C"type"%3A"terminal"%2C"service"%3A"text"%2C"node_id"%3A0}%2C"return_type"%3A"entry"%2C"request_options"%3A{"pager"%3A{"start"%3A0%2C"rows"%3A100}%2C"scoring_strategy"%3A"combined"%2C"sort"%3A[{"sort_by"%3A"score"%2C"direction"%3A"desc"}]}%2C"request_info"%3A{"src"%3A"ui"%2C"query_id"%3A"9228d1d289499c18e4c10fe3bb429ff3"}}
-- Whywhenwhohow ( talk) 08:44, 24 October 2020 (UTC)
https://www.rcsb.org/search?request={"query":{"parameters":{"value":"F9E"},"service":"text","type":"terminal","node_id":0},"return_type":"entry","request_options":{"pager":{"start":0,"rows":100},"scoring_strategy":"combined","sort":[{"sort_by":"score","direction":"desc"}]},"request_info":{"src":"ui","query_id":"b02260d062ec5ebd59379efff3f54409" }}
(
link)This
edit request to
Template:Infobox drug has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Please replace all live code with /sandbox code (two templates):
DePiep ( talk) 00:12, 27 October 2020 (UTC)
On articles that have both {{
Chembox}} and {{
Infobox drug}}, lots of the "chemical" fields are omitted from the drugbox to avoid duplication and keep content where it is most relevent. But drugbox also tracks certain missing fields, including some that get deffered to the chembox in these cases. That pollutes the tracking categories for things that are intentionally not to be done. For example,
Niacin has the chemical structure and CASNo in the chembox and therefore blank fields {{
Infobox drug|image=|CAS_number=}}
, which triggers the article to be listed in
Category:Infobox drug articles without a structure image and
Category:Chemical articles without CAS registry number, respectively.
We had a similar problem in Chembox when it was a secondary infobox, and in June,
User:DePiep implemented
{{
Chembox|container_only=yes}}
to stop whining about intentionally-missing fields (see
Template talk:Chembox#Field to indicate only partial infobox). I propose a similar flag here for the drugbox.
DMacks (
talk)
03:29, 2 October 2020 (UTC)
This
edit request to
Template:Infobox drug has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Please perform these two edits:
|container_only=
per
this talk; will populate new
Category:Infobox drug container onlyDiscussion & consensus: this talk (following {{ Chembox}} in this)
Tested: see /testcases9 and Niacin live (by preview)
Post-edit check: the demo article is Niacin. One can check this article, right after these edits, for any disruption.
|container_only=y
will inhibit all tracking of missing fields, which means |legal_*=
, |ATC_=
, and |license_*=
among others. I don't think that is the correct behavior, because those fields would not be covered by {{
chembox}}.
DMacks (
talk)
19:26, 18 October 2020 (UTC)
|container_only=yes
proposal here suppresses most if not all of the generic chemicals & CheMoBot trackings. Meanwhile, in Drugbox detailed cat reportings like "EMA" input issues are tracked, which seems OK to me.|container only=yes
. I cannot exactly reproduce the {{Chembox}} handling, because Chembox is more complicated and anyway, when using the template this way there is a bit of "you're on your own" consequence. {{Infobox drug}} however we can fine-tune. This is what the sandboxes have now:|container only=
.|Legal_US=
when there is an issue with its actual input).|CAS number_Ref=
: as intended, and not added anyway if CAS number is absent so no undesired effect).|container only=yes
. See the -xxx->
lines that cancelles (=comments out) categories.This
edit request to
Template:Infobox drug has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Please perform these two edits:
|container_only=
per
this talk; will populate new
Category:Infobox drug container onlyDiscussion & consensus: Following {{ Chembox}} in this. See #this talk and #this withdrawn request with extended discussion. @ DMacks:.
Tested: see /testcases9 and Niacin live (by preview)
Post-edit check: the demo article is Niacin. One can check this article, right after these edits, for any disruption. DePiep ( talk) 14:54, 7 November 2020 (UTC)
Hey. I know jack shit about this subject, but I noticed that the code for calculating whether to show the metabolism parameter checks for the parameters {sources} and {targets} despite neither appearing anywhere else in the infobox code. I'm 99% sure that it's the {source_tissues} and {target_tissues} parameters that someone just forget to rename thoroughly. I don't have editing permissions - can someone who has please confirm that this is the case and then fix the code? -- Metalindustrien ( talk) 19:59, 9 November 2020 (UTC)
Background: parameters involved
|
---|
<!-- type=mab: ----- ----- --> | type = mab | mab_type = | source = | target = <!-- Physiological data --> | source_tissues = | target_tissues = ... | metabolism = <!-- same parameter as in pharmacokinetic data -->
|
|source_tissues, target_tissues=
in there, lists 10 articles). It appears that, in spite of the two misnamed parameters, the #if-clause in |data58=
does fire correctly because of other parameters having data. So, at the moment no errors in articles. Of course, we will fix the issue. -
DePiep (
talk)
20:00, 10 November 2020 (UTC)This
edit request to
Template:Infobox drug has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Please replace all live code with /sandbox code:
Change: replace |
, sources=|
with targets=|source_tissues=
, |target_tissues=
. Replace non-existant parameter names.
Talk & test: Old code error. See above #Is sources ... source_tissues ... ?; F3 and visual checks. h/t @ Metalindustrien: DePiep ( talk) 23:10, 19 November 2020 (UTC)
This
edit request to
Template:Infobox drug has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Hi, could anyone with the ability to edit this template be so kind to add the legal statuses for legal_SG (Singapore)? I think it would be really useful and once added I will start adding the appropriate legal classes/schedules onto the most common drugs/medications. It will be based upon the Misuse of Drugs Act (OTC, Rx-only, Schedule I, II, III or Unscheduled) first enacted in 1973. Thank you! BelfastBrooks ( talk) 08:07, 2 December 2020 (UTC)
|legal_SG=
|legal_SG_comment=
|legal_SG=otc / prescription only, rx-only, rx only / s1, schedule i, schedule 1 / s2, schedule ii, schedule 2 / s3, schedule iii, schedule 3
. Not recognised →
Category:Drugs with non-standard legal status under "G".|legal_SG_comment=any text
, will show unedited after a space (consider using brackets).Meanwhile, editor can discuss appropriateness of this proposal (for example, which of the ~200 countries should be added this way?)I think this is an important point. I'm guessing we list options for the countries which are most popular amongst readers, but that's just a guess. Obviously we couldn't (and shouldn't) list it for every country on the map. Does an inclusion criteria for this label already exist? ProcrastinatingReader ( talk) 18:12, 3 December 2020 (UTC)
The {{ Infobox drug/formatUNII}} formatter URL currently differs from the UNII (P652) formatter URL. This infobox appears less correct. int21h ( talk · contribs · email) 04:42, 15 December 2020 (UTC)
Obviously, the enwiki url is redirected to the WD url, so the change is due. Will make the editrequest. - DePiep ( talk) 13:53, 16 December 2020 (UTC)
This
edit request to
Template:Infobox drug has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Please put all code from in {{ Infobox drug/formatUNII/sandbox}} into {{ Infobox drug/formatUNII}} (full replacement), diff.
Change, talk & test: External link URL format updated. See #UNII formatter URL above. ping @ Int21h: DePiep ( talk) 13:58, 16 December 2020 (UTC)
We should remove the |pregnancy_US=
parameter since the
FDA doesn't use letter categories any longer. They were replaced by the Pregnancy and Lactation Labeling Final Rule (PLLR). Here is an excerpt from Drugs.com:
Prescription drugs submitted for FDA approval after June 30, 2015 will use the new format immediately, while labeling for prescription drugs approved on or after June 30, 2001 will be phased in gradually. Medications approved prior to June 29, 2001 are not subject to the PLLR rule; however, the pregnancy letter category must be removed by June 29, 2018. For generic drugs, if the labeling of a reference listed drug is updated as a result of the final rule, the abbreviated new drug application (ANDA) labeling must also be revised. Labeling for over-the-counter (OTC) medicines will not change, as OTC drug products are not affected by the new FDA pregnancy labeling.
By the way, when 'N' is used for |pregnancy_US=
, the text "US: N (Not classified yet)" appears in the infobox. The "yet" should be removed. It is confusing to readers and some editors try to find the category to use to replace the 'N'. --
Whywhenwhohow (
talk)
20:35, 28 December 2020 (UTC)
|PLLR=
, free text input (
label link). Was added 2015, see also
this talk.|Pregnancy_US=
1315 articles (mainspace)|PLLR=
0 articles (mainspace)|pregnancy_category=
instead of |pregnancy_US=
. I think it makes sense to remove |pregnancy_US=
, |pregnancy_US_comment=
, |pregnancy_category=
, and |PLLR=
. Australia still assigns category letters to medicines. --
Whywhenwhohow (
talk)
00:12, 29 December 2020 (UTC)
|pregnancy_US=
, |pregnancy_US_comment=
, |PLLR=
. Their input will not be shown at all. The comment usually refers to the Code too. (Will not remove them from the infobox in articles). -
DePiep (
talk)
00:46, 29 December 2020 (UTC)
|pregnancy_US_comment=
is used as a reference input (added unspaced). Todo: {{
Chembox}} too. -
DePiep (
talk)
21:35, 29 December 2020 (UTC)This
edit request to
Template:Infobox drug has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Please replace all code with all sandbox code, in these two templates:
Changes, talk and test: See § Pregnancy US parameter; US pregnancy category code abolished, so no showing. /testcases3. DePiep ( talk) 11:42, 29 December 2020 (UTC)
FYI, DrugBank changed domains from drugbank.ca to drugbank.com. -- Whywhenwhohow ( talk) 04:21, 27 January 2021 (UTC)
The official website is now
https://www.drugbank.com/ and any drug detail pages using the hostname www.drugbank.ca
are redirected to use the hostname go.drugbank.com
. For example, Asprin was at
https://www.drugbank.ca/drugs/DB00945 and is now at
https://go.drugbank.com/drugs/DB00945. The only changes to the URL appear to be changing www.drugbank.ca
to go.drugbank.com
.
Do we support using |Drugbank=
for uses other than drugs? For example, here is a sample target and a sample indication.
The use of "r" for resolve appears to be old. For example, using https://www.drugbank.ca/r/DB00945 for Asprin is the same as using https://www.drugbank.ca/drugs/DB00945 and is now at https://go.drugbank.com/drugs/DB00945.
-- Whywhenwhohow ( talk) 05:05, 28 January 2021 (UTC)
Is |Drugbank=
used in the {{
Chembox}}? If so, it would need to be updated too. --
Whywhenwhohow (
talk)
05:09, 28 January 2021 (UTC)
Another use is for salts but using drugs in the URL redirects to the salts. Using any of these
redirects to here
-- Whywhenwhohow ( talk) 05:21, 28 January 2021 (UTC)
This
edit request to
Template:Infobox drug has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Please replace all code {{ Infobox drug}} ← {{ Infobox drug/sandbox}} ( diff).
Suppose I want to know more about Viagra, I search with the term viagra because that's the WP:COMMONNAME. I find that the title page is Sildenafil and it's the first name suggested in the first sentence, if I wish to find information about the origin of Sildenafil, the infobox shows that it is the name used by the FDA, and that it appears in the chemical nomenclature of its metabolite, but nothing else, I suspect the name comes from the FDA, but I cannot be sure. I assumes that Sildenafil is "the official name", but I might be skeptic about the notion of a single offical name.
I tried to add a line " INN = Sildenafil" but that just causes a tooltip to appear beneath the title of the infobox, since they are both the same, it looks weird.
I understand that by default, the policy is to name the article according to the INN, but this is not transparent to most users, who cannot navigate through wikipedia's policy to finally understand that the name comes from this thing called the INN.
If I could just add a field "INN= Sildenafil" to the infobox, it would make the naming convention explicit, and it would allow regular users to explore the concept of INN. It would also allow editors to add sources regarding INN nomenclature.
Thank you for your time.-- TZubiri ( talk) 05:15, 14 August 2020 (UTC)
See this discussion about redisigning {{Infobox drug}} at WT:MED: § A slimmer, more reader-friendly drugbox?. - DePiep ( talk) 22:24, 30 January 2021 (UTC)
<revived discussion;
It is extremely useful to know date that patents are issued. Please consider adding this to the drug box. — Preceding unsigned comment added by 63.247.31.113 ( talk) 23:50, 28 July 2011 (UTC)
is there no website that lists drugs patent date in the USA? then you could just link to it as an external link. The drug box is faster for doctors than reading a history. i hope you reconsider and add it to the drug box. — Preceding unsigned comment added by 63.247.31.123 ( talk) 22:04, 12 August 2011 (UTC)
What's going on with this? I search the page and there isn't even a mention of 'generic' or 'patent' to add this info manually. Let's do something that's better than nothing.
This
edit request to
Template:Infobox drug has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Add field year1stPatentEnds to the template. Feel free to be more ambitious, but I'm just requesting a simple static field that accepts a number. 50.201.195.170 ( talk) 20:22, 5 February 2021 (UTC)
{{
edit template-protected}}
template. From an inclusion standpoint, sure, patent status seems as encyclopedic as other legal status, i.e. whether controlled in various countries. Invention/discovery date seems important enough to feel like an omission to me. But it seems there are practical (evergreening) and possibly npov (worldwide point of view) considerations that need to be fleshed out in more detail.
Matt Fitzpatrick (
talk)
03:22, 20 February 2021 (UTC)Consider adding the other name fields too.
Australian Approved Name (AAN)
Australian Biological Name (ABN)
Australian Cell and Tissue Name (ACN)
A botanical name for a herb (AHN)
A herbal substance Name (AHS)
For example, the ABN for the newly approved COVID-19 Vaccine AstraZeneca is ChAdOx1-S. -- Whywhenwhohow ( talk) 05:50, 17 February 2021 (UTC)
|AAN=
, BAN, JAN, USAN.|synonyms=
field. In my mind that would typically be a better place to list national/regional names than having a separate field for each? That would give page editors a bit more flexibility to pick the relevant synonyms for each? But maybe an example or two would help make things clearer for me.|synonyms=
field may be used for those too. An ABN is just like an AAN and is assigned instead of an AAN for a specific class of therapeutic goods. COVID-19 Vaccine AstraZeneca has an ABN instead of an AAN. --
Whywhenwhohow (
talk)
05:57, 24 February 2021 (UTC)
|synonyms=
field, and then to update the documentation accordingly. Perhaps the documentation page could link to the gov't databases of names so an editor could quickly check the names from each when they're setting up an article on a new drug? I assume the AAN, BAN, JAN, etc. are sometimes the same?
Ajpolino (
talk)
06:36, 25 February 2021 (UTC)
The documentation examples state that the vaccine target is the antigen/bacteria/toxin/virus to protect against
in the comments but the infobox labels the field as Target disease
. The label in the infobox is incorrect since the vaccine targets the cause of the disease, not the disease itself. Please remove disease from the infobox label. Thank you. --
Whywhenwhohow (
talk)
04:21, 1 March 2021 (UTC)
@ DePiep: Alemtuzumab is not a vaccine. Here are some mixed examples
Target disease influenza virus
Target disease Cholera
Target disease Corynebacterium diphtheriae
Target disease Haemophilus influenzae type b
Target disease Neisseria meningitidis
Target disease Whooping cough
Target disease Ebola virus
Target disease Hepatitis A
Target disease Hepatitis B virus
Target disease Human papillomavirus (HPV)
Target disease Measles virus
Target disease Poliomyelitis
-- Whywhenwhohow ( talk) 02:08, 2 March 2021 (UTC)
This
edit request to
Template:Infobox drug has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Change: fix label5 text, per request #Vaccine target. DePiep ( talk) 13:13, 2 March 2021 (UTC)
I would like to propose these new fields for storage conditions:
| storage_conditions = | storage_temperature = | storage_humidity = | storage_dark =
To be rendered as:
| label1 = Storage conditions | data1 = {{{storage_conditions|}}} | header2 = {{#if:{{{storage_temperature|}}}{{{storage_humidity|}}}{{{storage_dark|}}}|Storage conditions}} | label3 = Temperature | data3 = {{{storage_temperature|}}} | label4 = Relative humidity | data4 = {{{storage_humidity|}}} | label5 = Light level | data5 = {{#switch:{{lc:{{{storage_dark|}}}}} | yes = Dark | no = Any | #default = {{{storage_dark}}} }}
The storage_conditions field would be used for short or non-standard descriptions, otherwise the other fields would be preferred. Usage examples:
Storage conditions | Cold, dry, dark |
---|
| storage_conditions = Cold, dry, dark
Storage conditions | 5 °C, 50% RH, dark |
---|
| storage_conditions = 5 °C, 50% RH, dark
Storage conditions | 2-8 °C, 40-60% RH, dark |
---|
| storage_conditions = 2-8 °C, 40-60% RH, dark
Storage conditions | Ambient |
---|
| storage_conditions = Ambient
Storage conditions | Dry |
---|
| storage_conditions = Dry
Storage conditions | |
---|---|
Temperature | Cold |
Relative humidity | Dry |
Light level | Dark |
| storage_temperature = Cold | storage_humidity = Dry | storage_dark = yes
Storage conditions | |
---|---|
Temperature | 2-8 °C |
Relative humidity | <60% |
Light level | No sunlight |
| storage_temperature = 2-8 °C | storage_humidity = <60% | storage_dark = No sunlight
Storage conditions | |
---|---|
Temperature | 2–8 °C (36–46 °F) |
Relative humidity | 40-60% |
Light level | Avoid light |
| storage_temperature = 2–8 °C (36–46 °F) | storage_humidity = 40-60% | storage_dark = Avoid light
Storage conditions | |
---|---|
Temperature | Ambient |
| storage_temperature = Ambient
Storage conditions | |
---|---|
Relative humidity | <60% |
| storage_humidity = <60%
Drug specifications vary slightly depending on the country. For example, it is unusual to specify a lower humidity limit, even when it has one, because low humidity is rare in many regions. For drugs with less stringent requirements, it is common to provide only a description instead of specific values for temperature and humidity. Most medications should be kept out of direct sunlight and light in general, so non-default values for storage_dark should be rare.
What do you think? -- Fernando Trebien ( talk) 16:11, 14 March 2021 (UTC)