Property talk:P2175

Documentation

• Start a query
• Current uses
• Statistics by class
• List of values
• List of qualifiers
• Count

medical condition treated
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: type of chemical entity (Q113145171), medical procedure (Q796194), clinical trial (Q30612), pharmaceutical product (Q28885102), medical specialty (Q930752) or medical device (Q6554101) When possible, data should only be stored as statements
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: https://rxnav.nlm.nih.gov When possible, data should only be stored as statements
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	Items with the most statements of this property Count of items by number of statements (chart) Items with the most statements Items with the fewest statements Count of items by number of sitelinks (chart) Items with the most sitelinks Items with the most sitelinks, but no link to one Wikipedia (sample: Welsh Wikipedia, cywiki) Items with the fewest sitelinks Most linked wikis Items with the most identifier properties By value of property Most statements Fewest statements Most sitelinks Most linked wikis Total of sitelinks on items Most identifiers Fewest identifiers Items with no other statements Most recently created items Items with novalue claims Items with unknown value claims Usage history (total) Usage history (main statement) Chart by item creation date Database reports/Complex constraint violations/P2175 Database reports/Constraint violations/P2175 Map Random list
Proposal discussion	Proposal discussion
Current uses	Total 9,430 Main statement 7,118 75.5% of uses Qualifier 2,307 24.5% of uses Reference 5 <0.1% of uses
Search for values

[create Create a translatable help page (preferably in English) for this property to be included here]

Type “type of chemical entity (Q113145171), medical procedure (Q796194), clinical trial (Q30612), pharmaceutical product (Q28885102), medical specialty (Q930752), medical device (Q6554101)”: item must contain property “instance of (P31), subclass of (P279)” with classes “type of chemical entity (Q113145171), medical procedure (Q796194), clinical trial (Q30612), pharmaceutical product (Q28885102), medical specialty (Q930752), medical device (Q6554101)” or their subclasses (defined using subclass of (P279)). (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P2175#Type Q113145171, Q796194, Q30612, Q28885102, Q930752, Q6554101, SPARQL

Value type “health problem (Q2057971)”: This property should use items as value that contain property “instance of (P31), subclass of (P279)”. On these, the value for instance of (P31), subclass of (P279) should be an item that uses subclass of (P279) with value health problem (Q2057971) (or a subclass thereof). (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P2175#Value type Q2057971, SPARQL

Inverse property of “drug or therapy used for treatment (P2176)”:
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)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P2175#inverse, SPARQL

Allowed entity types are Wikibase item (Q29934200): the property may only be used on a certain entity type (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P2175#Entity types

Scope is as main value (Q54828448), as qualifier (Q54828449): the property must be used by specified way only (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P2175#Scope, SPARQL

This property is being used by: cy:Nodyn:Cyffuriau ca:Plantilla:Infotaula de fàrmac, ca:Plantilla:Amadalvarez/traduccions 2, ca:Plantilla:Infotaula de fàrmac/prova cs:Šablona:Infobox - léčivá látka d:Template:List of medical treatments/Row eu:Txantiloi:Konposatu kimiko infotaula ar:قالب:معلومات تدخل طبي, ar:قالب:صندوق معلومات تدخل طبي arz:قالب:معلومات دواء ga:Teimpléad:WD Bosca Sonraí Druga Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.)

Chemical entities with no indication of use as a drug
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

The 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?

For 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

There is a warning at 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)