Property talk:P636
Jump to navigation
Jump to search
Documentation
route of administration
path by which a drug, fluid, poison, or other substance is taken into the body
path by which a drug, fluid, poison, or other substance is taken into the body
| Description | route of administration (Q621636) A route of administration in pharmacology and toxicology is the path by which a drug, fluid, poison, or other substance is taken into the body. | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Represents | route of administration (Q621636) | |||||||||
| Data type | Item | |||||||||
| Template parameter | Template:Infobox medical condition (old) (Q6436840) routes_of_administration | |||||||||
| Domain | According to this template:
chemical compound (Q11173)
According to statements in the property:
When possible, data should only be stored as statementstype of chemical entity (Q113145171), pharmaceutical product (Q28885102) or medication (Q12140) | |||||||||
| Allowed values | instances of route of administration (Q621636) (note: this should be moved to the property statements) | |||||||||
| Example | aspirin (Q18216) → intramuscular injection (Q432083) nitrous oxide exposure (Q21175013) → eye contact (Q21074571) skin absorption (Q4669896) inhalation administration (Q4010888) diazepam (Q210402) → intramuscular injection (Q432083) | |||||||||
| Source | Scientific literature (note: this information should be moved to a property statement; use property source website for the property (P1896)) | |||||||||
| Tracking: usage | Category:Pages using Wikidata property P636 (Q124982339) | |||||||||
| Lists |
| |||||||||
| Proposal discussion | Proposal discussion | |||||||||
| Current 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), pharmaceutical product (Q28885102), medication (Q12140)”: item must contain property “instance of (P31), subclass of (P279)” with classes “type of chemical entity (Q113145171), pharmaceutical product (Q28885102), medication (Q12140)” 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/P636#Type Q113145171, Q28885102, Q12140, SPARQL
Value type “route of administration (Q621636)”: 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 route of administration (Q621636) (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/P636#Value type Q621636, SPARQL
|
This property is being used by:
Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.) |
|
Value parenteral administration (Q638634) will be automatically replaced to value parenteral route of administration (Q29954029). Testing: TODO list |
Sample values
[edit]- oral administration (Q285166)
- endobronchial (Q1340651)
- enteral administration (Q1344580)
- intra-arterial (Q1431898)
- intracardiac injection (Q366155)
- intramuscular injection (Q432083)
- intraosseous infusion (Q573068)
- intraperitoneal injection (Q1400536)
- Intrapulmonary administration (Q1671565)
- intrathecal administration (Q1320251)
- intravenous injection (Q1369403)
- intravitreal administration (Q180609)
- parenteral administration (Q638634)
- percutaneous procedure (Q2071287)
- sublingual administration (Q784720)
- systemic administration (Q2377086)
- intravenous infusion and defusion (Q640448)
- rectal administration (Q419892)
- transdermal administration (Q7833952)
- topical medication (Q420054)
- insufflation (Q3153701)
- eye contact (Q21074571)
- inhalation administration (Q10268830)
- skin absorption (Q4669896)
The difference between the concepts of route (path) and administration (procedure).
[edit]route of administration (Q621636) and drug administration (Q29914073) are different concept. This is because the former is the kind of conceptual structure, while the latter is the kind of procedure performed by humans. There are subclasses corresponding to both classes, such as enteral route of administration (Q29953996) and enteral administration (Q1344580), hence the confusion. Some subclasses may have incorrect class-instance relationships. Which subclasses should be used for the value of this property? Are both acceptable? --Okkn (talk) 02:30, 7 June 2023 (UTC)
- @Okkn: I understand what you're trying to do, but please, don't make such edits without any attempt to fix the constraint violations. I spent some time trying to figure out what has happened. E.g. oral administration (Q285166) – there was no proper item that can be used to migrate previous uses of route of administration (P636) to. In the case of parenteral administration there is – so the best option is to properly disambiguate parenteral administration (Q638634) and parenteral route of administration (Q29954029) AND add an autofix template [1]. Wostr (talk) 17:19, 8 June 2023 (UTC) PS It would be good to leave autofix templates after this in case someone mistakenly add one item (type of administration) instead of another (route of administration). Wostr (talk) 17:22, 8 June 2023 (UTC)
- @Wostr: Thank you for your comment. I would rather change the class constraint on the value of this property to a subclass of (subclass of (P279)) drug administration (Q29914073) to match the actual usage, rather than to match the current label name ("route of administration"). For example, intramuscular injection (Q432083) is also properly a type of medical procedure, not a route. Alternatively, even if the value of this property were to be a child of route of administration (Q621636), the appropriate relationship would be subclass of (P279), not instance of (P31). The instances of the route of administration (Q621636) class would refer to the actual route in each individual. How do you feel about that? --Okkn (talk) 07:29, 9 June 2023 (UTC)
- @Okkn: I agree that specific routes of administration would better be modelled using subclass of (P279). About whether the values of this property should be subclasses of route of administration (Q621636) or drug administration (Q29914073) – I'm not sure which option would be better and I see that labels in different languages differ in exact meaning. E.g. English or Polish labels suggest that the value should be specifically a route of administration (→ route of administration (Q621636)), but e.g. Russian label suggests that the value should be a method of administration (→ drug administration (Q29914073)). This may require just an arbitrary decision which way to go, but I'm a chemist and maybe there is some medical aspect which I do not see, and which may be important in this choice. Wostr (talk) 19:16, 9 June 2023 (UTC)
- @Wostr: Thank you for your comment. I would rather change the class constraint on the value of this property to a subclass of (subclass of (P279)) drug administration (Q29914073) to match the actual usage, rather than to match the current label name ("route of administration"). For example, intramuscular injection (Q432083) is also properly a type of medical procedure, not a route. Alternatively, even if the value of this property were to be a child of route of administration (Q621636), the appropriate relationship would be subclass of (P279), not instance of (P31). The instances of the route of administration (Q621636) class would refer to the actual route in each individual. How do you feel about that? --Okkn (talk) 07:29, 9 June 2023 (UTC)