Vehicle accident (event) content
Summary
This proposal highlights 255 concepts of the 2794 descendants of 418019003 |Accidental event (event)| that seem appropriate to inactivate. There may be others with similar issues that have yet to be reviewed.
These concepts appear to be classification constructs and use:
negation via the use of the term “except”,
excessive pre-coordination,
“or”,
nonsensical descriptions.
The CMAG is being asked if inactivation of these concepts will cause an issue for any members.
https://snomed.atlassian.net/browse/IHTSDO-1071
Actions:
Date | Requested action | Requester(s) | Response required by: | Comments |
|---|---|---|---|---|
Requested 11th April 2018 | Please advise if inactivation of this content would cause an issue for your country. | @Cathy Richardson, @Krista Lilly | @Camilla Wiberg Danielsen May 4, 2018 Please advise if inactivation of the identified subtypes of Vehicle accident (event) as noted in the content tracker IHTSDO-1071 would cause an issue for your country. @Daniel Karlsson May 4, 2018 Please advise if inactivation of the identified subtypes of Vehicle accident (event) as noted in the content tracker IHTSDO-1071 would cause an issue for your country. @Elaine Wooler May 4, 2018 Please advise if inactivation of the identified subtypes of Vehicle accident (event) as noted in the content tracker IHTSDO-1071 would cause an issue for your country. @Elze de Groot May 4, 2018 Please advise if inactivation of the identified subtypes of Vehicle accident (event) as noted in the content tracker IHTSDO-1071 would cause an issue for your country. @Former user (Deleted) May 4, 2018 Please advise if inactivation of the identified subtypes of Vehicle accident (event) as noted in the content tracker IHTSDO-1071 would cause an issue for your country. @Linda Parisien May 4, 2018 Please advise if inactivation of the identified subtypes of Vehicle accident (event) as noted in the content tracker IHTSDO-1071 would cause an issue for your country. @Matt Cordell May 4, 2018 Please advise if inactivation of the identified subtypes of Vehicle accident (event) as noted in the content tracker IHTSDO-1071 would cause an issue for your country. @Former user (Deleted) May 4, 2018 Please advise if inactivation of the identified subtypes of Vehicle accident (event) as noted in the content tracker IHTSDO-1071 would cause an issue for your country. @Jostein Ven May 4, 2018 Please advise if inactivation of the identified subtypes of Vehicle accident (event) as noted in the content tracker IHTSDO-1071 would cause an issue for your country. @Former user (Deleted) May 4, 2018 Please advise if inactivation of the identified subtypes of Vehicle accident (event) as noted in the content tracker IHTSDO-1071 would cause an issue for your country. @Theresa Barry May 4, 2018 Please advise if inactivation of the identified subtypes of Vehicle accident (event) as noted in the content tracker IHTSDO-1071 would cause an issue for your country. | Please post your final responses in the Country response table below. Discussion comments can be made as comments. |
Relevant documents
Actions
Links
Country response
Country | Date | Response |
|---|---|---|
US | 20APR2018 | OK in principle to remove nonsensical content. The excessive pre-coordination dogma does not have to be invoked here (and should probably be put to rest – the only thing that matters is the right level of pre-coordination, as required by use cases. This is a bit of a personal crusade, but I think it is good to reaffirm once in a while.) Unclear how this could impact analytics, but probably very little if these concepts are nonsensical to start with. |
Sweden | 2018-04-23 | No content <<418161006 |Vehicle accident (event)| in out extension nor in any maintained or in-development refsets. Go ahead! |
Denmark | 2018-04-25 | Not in use in Denmark. |
UK | 2018-04-30 | In principle inactivating this content will not cause any issues. However to faciliate data repair we would like to see these inactivated with a MAYBE A relationship or similar. |
NZ | 2018-05-01 | No objections raised in New Zealand |
AU | 2018-05-03 | As mentioned elsewhere, we fully support retiring these concepts. Although the initial item seems to be to address the mapping issues, a larger task should also be undertaken to remove all similar concepts in both event and finding hierarchies. Sometimes it's not even clear what role the subject of record would have in a concept: 216234009|Poisoning caused by carbon monoxide from aircraft while in transit, without accident to aircraft, occupant of spacecraft injured (disorder)| |
CA | 2018-05-04 | Not in use in Canada. |
|
|
|
Member countries without a CMAG rep |
|
|
CMAG response
Date | CMAG Response | Next steps |
|---|---|---|
|
|
|
|
|
|
|
|
|
Final outcome:
Date:
Copyright © 2025, SNOMED International