Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Page properties


StatusIn progressReady for implementation
Version1.0


Descriptions:

Termdescription typeLanguage/acceptabilityLanguage/acceptabilityCase Significance
[Accidental/Intentional] Poisoning caused by [agent] due to [event] (disorder)FSNus:Pgb:Pci
[Accidental/Intentional] Poisoning caused by [agent] due to [event] 
SYNus:Pgb:Pci
[Accidental/Intentional] [Agent] poisoning due to [event]SYNus:Agb:Aci

...

Scg expression
75478009 |Poisoning (disorder)|: 
[[~0..1]] {[[~0..1]] 263502005 |Clinical course (attribute)| = [[ +id ( < 288524001 |Courses (qualifier value)| ) @course]]}, 
[[~0..1]] {[[~0..1]] 42752001 |Due to (attribute)| = [[ +id ( < 272379006 |Event (event)| ) @dueto ]]}, 
[[~0..2 @rolegroup]] { 
[[~1..1]] 246075003 |Causative agent (attribute)| = [[+id (( << 105590001 |Substance (substance)| OR << 373873005 |Pharmaceutical / biologic product (product)|) OR << 410607006 |Organism (organism)| ) @causative]], 
[[~0..1]] 363698007 |Finding site (attribute)| = [[+id ( << 123037004 |Body structure (body structure)| ) ]], 
[[~0..1]] 370135005 |Pathological process (attribute)| = [[+id ( <<  308489006 |Pathological process (qualifier value)| ) ]], 
[[~0..1]] 116676008 |Associated morphology (attribute)| = [[+id ( << 49755003 |Morphologically abnormal structure (morphologic abnormality)| ) ]]}

Note:

  • Pathological process is added to include content under food poisoning.
  • Addition of other attributes such as "246454002 |Occurrence (attribute)|, 363714003 |Interprets (attribute)|, and 363713009 |Has interpretation (attribute)| was considered. However, they were not added due to the very low number of concepts defined by them. Same consideration was applied to expanding the range for 42752001 |Due to (attribute)| to include 71388002 |Procedure (procedure)|, 
     and/or 64572001 |Disease (disorder)| i.e. they were not added as valid values for due to attribute because only a very small number of concepts are defined by them.

Link to the misaligned concept report

https://docs.google.com/spreadsheets/u/0/d/1hL_nRtRpDkK2Ws4VkzbmV5lISyw6CnZ_ZTL781poG7I/edit#gid=01G-cOv78CFHDprzBYWvb8b2WRCu-PsNxp-0vlzG716nQ/edit

Rules for generating descriptions:

...

Hierarchy

Concept type

Allowed

Exception

Examples and Notes

SubstanceBaseyesnone

Poisoning concepts representing a substance base should be modeled using a Causative agent that is a descendant of 105590001 |Substance (substance)|.

Examples:

  • 13503000 |Poisoning caused by naloxone (disorder)|
  • 30138004 |Poisoning caused by ether (disorder)|

Classification results are expected to be consistent with the modeling of the concept selected as the Causative agent in the Substance hierarchy.

SubstanceModificationnoyes

Poisoning concepts representing a substance modification should be modeled using a Causative agent that is a descendant of 105590001 |Substance (substance)|. Concepts representing substance modifications are exceptions and may be included if the poisoning profile is significantly different from the substance base.

Exception examples:

  • Salt forms (e.g. 273948005 |Chloral hydrate (substance)|, 396063006 |Fluphenazine decanoate (substance)|)

Examples:

  • 62942003 |Tetraethyl pyrophosphate poisoning (disorder)|
SubstanceStructure grouperyesnone

Poisoning concepts representing a structure grouper should be modeled using a Causative agent that is a descendant of 105590001 |Substance (substance)|.

Examples:

  • 1153528004 |Poisoning caused by substance with ether structure (disorder)|

Classification results are expected to be consistent with the modeling of the concept selected as the Causative agent in the Substance hierarchy.

SubstanceDisposition grouperyesnone

Poisoning concepts representing a disposition grouper should be modeled using a Causative agent that is a descendant of 105590001 |Substance (substance)|.

Examples:

  • 9291000 |Poisoning caused by monoamine oxidase inhibitor (disorder)|

Classification results are expected to reflect that the adverse reaction concepts are descendants of the appropriate disposition grouper based on the modeling of the 726542003 |Has disposition (attribute)| attribute in the substance hierarchy.

SubstanceRole groupernonone

Currently poisoning Poisoning concepts representing a role Role grouper are should be modeled using a Causative agent that is a descendant of 105590001 |Substance (substance)|. Note that role groupers will be transitioned to the 763158003 |Medicinal product (product)| hierarchy in a future release

Example:

  • 241748001 |Poisoning caused by analgesic drug (disorder)|

Classification results are expected to reflect that the adverse reaction concepts are descendants of the appropriate disposition grouper based on the modeling of the 726542003 |Has disposition (attribute)| attribute in the substance hierarchy.

ProductStructure groupernonone

No use case has been identified for use of this concept type for modeling in this subhierarchy. Medicinal product-containing concepts can be used for modeling in this subhierarchy.


ProductDisposition groupernononeNo use case has been identified for use of this concept type for modeling in this subhierarchy. Medicinal product-containing concepts can be used for modeling in this subhierarchy.
ProductRole grouperyesnone

Examples to be added - pending implementation of roles and products as causative agents

ProductMedicinal product-containingyesnone

Examples to be added - pending implementation of roles and products as causative agents

ProductMedicinal product-onlynononeNo use case has been identified for use of this concept type for modeling in this subhierarchy. Medicinal product-containing concepts can be used for modeling in this subhierarchy.
ProductMedicinal product form-containingnononeNo use case has been identified for use of this concept type for modeling in this subhierarchy. Medicinal product form-containing concepts can be used for modeling in this subhierarchy.
ProductMedicinal product form-onlynononeNo use case has been identified for use of this concept type for modeling in this subhierarchy. Medicinal product form-containing concepts can be used for modeling in this subhierarchy.
ProductClinical drugnononeNo use case has been identified for use of this concept type for modeling in this subhierarchy. Medicinal product form-containing concepts can be used for modeling in this subhierarchy.

...