Property talk:P1692
Jump to navigation
Jump to search
Documentation
ICD-9-CM
identifier in the ICD adaption assigning diagnostic and procedure codes
identifier in the ICD adaption assigning diagnostic and procedure codes
| Description | ICD adaption assigning diagnostic and procedure codes | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Represents | ICD-9-CM (Q5737131) | |||||||||||||
| Data type | String | |||||||||||||
| Template parameter | Interventions Infobox (also a few templates like: en:Template:Digestive_system_procedures) | |||||||||||||
| Domain | Medical topics (note: this should be moved to the property statements) | |||||||||||||
| Allowed values | ([\dA-Z]\d{2}(\.\d{1,3}|))|(\d{2}(\.\d{1,2}|)) | |||||||||||||
| Example | According to this template:
digestive system surgery (Q5275614) => 42; digestive system surgery (Q5275614) => 43; digestive system surgery (Q5275614) => 44; digestive system surgery (Q5275614) => 45
According to statements in the property:
When possible, data should only be stored as statementsdigestive system surgery (Q5275614) → 42 graphite pneumoconiosis (Q55790300) → 503 sarcoidosis, susceptibility to, 1 (Q55950306) → 135 | |||||||||||||
| Source | ICD (note: this information should be moved to a property statement; use property source website for the property (P1896)) | |||||||||||||
| Formatter URL | http://icd9cm.chrisendres.com/index.php?action=search&srchtext=$1 | |||||||||||||
| Tracking: usage | Category:Pages using Wikidata property P1692 (Q51719359) | |||||||||||||
| 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]
Distinct values: this property likely contains a value that is different from all other items. (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/P1692#Unique value, SPARQL (every item), SPARQL (by value)
Scope is as main value (Q54828448), as reference (Q54828450): the property must be used by specified way only (Help)
List of violations of this constraint: Database reports/Constraint violations/P1692#Scope, hourly updated report, SPARQL
Format “
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). ([\dA-Z]\d{2}(\.\d{1,3}|))|(\d{2}(\.\d{1,2}|))”: value must be formatted using this pattern (PCRE syntax). (Help)List of violations of this constraint: Database reports/Constraint violations/P1692#Format, 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/P1692#Entity types
|
This property is being used by:
Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.) |
| ||||||||||||||||||
Proposal - Change Data type of ICD-9-CM (P1692) from String to External identifier[edit]
I think String is the wrong type for ICD-9-CM (P1692). Can we please change it to be External identifier.
As per Help:Data_type#Changing_datatype please indicate support/opposition below. Iwan.Aucamp (talk)
Discussion[edit]
Support by analogy with the other ICD identifiers. ArthurPSmith (talk) 16:59, 15 October 2019 (UTC)- Support fast track, per reasoning @Wikisaurus: at MediaWiki_talk:Wikibase-SortedProperties/Archive_1#ICD-9-CM. @Epìdosis, ChristianKl: opinion? MrProperLawAndOrder (talk) 19:14, 5 June 2020 (UTC)
- Support, if it is technically possible. Wikisaurus (talk) 19:19, 5 June 2020 (UTC)
- Support, and yes, it is technically possible. --Epìdosis 19:22, 5 June 2020 (UTC)
- It's first worth understanding why ICD-9-CM (P1692) currently is String. The idea is that that if a property uses External identifier then if somebody queries for a given ID there should be exactly one Wikidata item that's the correct item for that ID. This property has 14,019 distinct value violations. For a property with lists 5,219 values that suggests that's a lot and the relationship we expect for external IDs doesn't really hold. I think there's a case to be made to change the general principle and also use external-id in cases like this where there are a lot of distinct value violations.
- Given that we have a bunch of properties that stayed string properties for this reason I think it would make more sense to have a general RfC to find consensus to move them to external-id together as package then to have the discussion on a bunch of individual properties. But I don't have strong feelings either way and don't oppose moving this property as a one-of.
- I think the default when changing properties should be to ping the people in the property creation discussion and the relevant WikiProject. So: @Tobias1984, Filceolaire, AmaryllisGardener:
Notified participants of WikiProject Medicine ChristianKl ❪✉❫ 19:34, 5 June 2020 (UTC)
Comment Please no en:WP:OR. WD should store them as what they are in the external source, and not what fits the modelling within some subproject in WD. Also, what does a value as string refer to, that it wouldn't refer to as external-id? Regarding management in WD and "This property has 14,019 distinct value violations." - either fix them or don't. Users of the data can find out how the values are stored, and see that WD isn't matching 1:1. MrProperLawAndOrder (talk) 00:44, 6 June 2020 (UTC)
- Imagine an external source that's that all PEOPLE-category according to which all dentists should be tagged with "X123". Then we have a property that we apply to people (Q5 instances) when we add "X123" to Bob the dentist and Dave the dentist. "X123" wouldn't be an external-id for either Bob or Dave. When an external source writes "X123" they are not intending to refer to Bob or Dave, so it makes more sense to use the string datatype then the external-id datatype for such usage.
- If say "X123" is an external-id for Bob you would engage in original research (and be wrong).
- To take on example 558 is named "Other and unspecified noninfectious gastroenteritis and colitis". If you say 558 is an external id, you are implying that "diversion colitis" and "chemical colitis" are both the same thing as "Other and unspecified noninfectious gastroenteritis and colitis" instead of implying that they are things that have the property of being examples of "Other and unspecified noninfectious gastroenteritis and colitis". ChristianKl ❪✉❫ 17:20, 6 June 2020 (UTC)
- What it implies doesn't depend on the datatype. Either an item is 558 or not. Create an item for 558 if it doesn't exist yet and make other items subclasses of it. MrProperLawAndOrder (talk) 00:40, 9 June 2020 (UTC)
Oppose given that it's used to classify, not to identify. --- Jura 18:03, 6 June 2020 (UTC)
- @Jura1: The class is used for classification but the ID is used to identify the class. The WD property is representing the ID, not the class. MrProperLawAndOrder (talk) 00:42, 9 June 2020 (UTC)
- Comment For this to be an identifier, Wikidata:Database_reports/Constraint_violations/P1692#Unique_value needs to be fixed first. --- Jura 10:19, 14 June 2020 (UTC)
