Property talk:P2175
Documentation
disease that this pharmaceutical drug, procedure, or therapy is used to treat
Data type | Item | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Template parameter | Use (Therapeutic use) en:Template:Infobox_drug_mechanism | ||||||||||||
Domain | According to this template:
pharmaceutical drugs, chemical compounds, proteins, nucleic acids
According to statements in the property:
When possible, data should only be stored as statementstype of chemical entity (Q113145171), medical procedure (Q796194), clinical trial (Q30612), pharmaceutical product (Q28885102), medical specialty (Q930752), medical device (Q6554101) or type of mixture of chemical entities (Q119892838) | ||||||||||||
Allowed values | Wikidata items (note: this should be moved to the property statements) | ||||||||||||
Example | dabrafenib (Q3011604) → skin melanoma (Q18558032) | ||||||||||||
Source | According to this template:
National Drug File (https://rxnav.nlm.nih.gov)
According to statements in the property:
When possible, data should only be stored as statementshttps://rxnav.nlm.nih.gov | ||||||||||||
Robot and gadget jobs | Will be added and maintained by User:ProteinBoxBot/Drug_items | ||||||||||||
Tracking: usage | Category:Pages using Wikidata property P2175 (Q26250013) | ||||||||||||
See also | negative therapeutic predictor for (P3355) | ||||||||||||
Lists |
| ||||||||||||
Proposal discussion | Proposal discussion | ||||||||||||
Current uses |
| ||||||||||||
Search for values |
List of violations of this constraint: Database reports/Constraint violations/P2175#Type Q113145171, Q796194, Q30612, Q28885102, Q930752, Q6554101, Q119892838, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P2175#Value type Q2057971, SPARQL
if [item A] has this property (medical condition treated (P2175)) linked to [item B],
then [item B] should also have property “drug or therapy used for treatment (P2176)” linked to [item A]. (Help)
List of violations of this constraint: Database reports/Constraint violations/P2175#inverse, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P2175#Entity types
List of violations of this constraint: Database reports/Constraint violations/P2175#Scope, SPARQL
This property is being used by:
Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.) |
Every item with medical condition treated (P2175) statement and instance of (P31)type of chemical entity (Q113145171) that has no has use (P366)medication (Q12140). In combination with other constraints it would allow in the future to properly move pharmacology-related statements from items about groups of isomers to items about specific isomer or to items about mixtures of isomers. (Help)
Violations query:
SELECT DISTINCT ?item WHERE { ?item wdt:P2175 ?value. ?item wdt:P31 wd:Q113145171. MINUS { ?item wdt:P366 wd:Q12140 . } }
List of this constraint violations: Database reports/Complex constraint violations/P2175#Chemical entities with no indication of use as a drug
label
editThe label "medical condition treated" reads rather awkwardly in English. I would prefer "treats" or "treats medical condition" to be the default EN label. --I9606 (talk) 21:52, 5 October 2015 (UTC)
- 'may_treat" might be even better, because for every medication, there is a certain chance that treatment will not work. Sebotic (talk) 23:49, 5 October 2015 (UTC)
- In that regard, I think "used to treat" is the right expression to use to record the fact that doctors prescribe a particular medication for a particular disease. Not the same thing as "cures" for sure. Need to eb careful there. --I9606 (talk) 23:52, 5 October 2015 (UTC)
what about treating symptoms?
editFor example, Ibuprofen treats pain.
Pain isn't a disease of course so that statement would violate your constraint. Do we introduce a new property "treats symptom" or do we relax that constraint? I would vote for the latter for now. --I9606 (talk) 21:52, 5 October 2015 (UTC)
- @I9606: Another way to model this could be to have all symptoms as WD items. Drugs just point to diseases or symptoms, whatever they are working for. The link of disease to symptom could then be established on a WD disease item with a property 'has symptom'. What has also not been considered yet is that taking certain drugs can have a preventive effect. E.g Aspirin may prevent stroke (but it is not used to treat stroke). And drugs can also cause diseases, (e.g. Vemurafenib may cause Keratoacanthoma). So two more properties, may_prevent and may_cause, will also be required to describe drug to disease relationships. Sebotic (talk) 23:47, 5 October 2015 (UTC)
- WikiProject Molecular biology has more than 50 participants and couldn't be pinged. Please post on the WikiProject's talk page instead. --Tobias1984 (talk) 20:51, 5 October 2015 (UTC)
- Simple fix: change the range of the property to health problem (Q15281399), of which symptom (Q169872) and disease (Q12136) are subclasses. Also, medication (Q12140), the current domain of this property, is rather narrow for something labeled "medical condition treated" (or "disease treated", "treats", etc.). This property thus excludes any medical procedure (Q796194), which is a vast swath of medicine, including but not limited to all surgeries. (Also excluded by limiting this property to pharmaceutical drugs: everyday objects like water, which treats dehydration.)
- It's worth noting that drugs and medical procedures are two fundamentally different things -- the former is an object (a continuant) and the latter is an process (an occurent). If we wanted to be precise and enable constraint checking, then we would exclude would pharmaceutical drug and its subclasses from this property's range.
- Precisely speaking, it is not ibuprofen that treats pain, but the molecular actions of ibuprofen that treats pain. Treatments are processes, not objects. Administration of ibuprofen treats pain (obviously up the causal chain from ibuprofen's molecular action). But referring to processes as objects is very common and convenient shorthand. It's a kind of metonymy.
- This semantic issue pervades talk of cause and effect. I suspect it will be a major obstacle to interesting applications based on inference. See Help:Modeling_causes#Not_completely_precise.
- For now, I agree with I9606: relax the constraint. Emw (talk) 03:05, 9 October 2015 (UTC)
This constraint fails with diseases
editThere is a warning at adaptive radiation therapy (Q180507) that the statement that it treats a tumor (Q133212) is a violation of the constraint. This makes us a laughing stock and needs to be fixed. We can see that tumor (Q133212) is a subclass of (P279) neoplasm (Q1216998), which is a subclass of (P279) disease (Q12136). When we have a constraint that objects to a statement that a treatment treats a disease, then something has gone badly wrong. --RexxS (talk) 13:12, 14 October 2018 (UTC)