Page tree

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 51 Next »


StatusFor review
Version

0.7

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

Concept model:

Definition status:  


900000000000073002 |Defined (core metadata concept)|

Applies to

Poisoning caused by substance or product, excluding concepts of types: "Food poisoning" and "Poisoning by organism" (the applicability of this template for these concepts needs to be evaluated) as well as "Overdose", and "Intoxication" (which will have their own templates):


(((<<  7895008 |Poisoning caused by drug AND/OR medicinal substance (disorder)| ) : [0..0]  42752001 |Due to (attribute)|  =  781249001 |Consumption of contaminated food (event)|  AND [0..0]  246075003 |Causative agent (attribute)|  = <<  410607006 |Organism (organism)|  ) OR (( <<  441952005 |Poisoning caused by chemical substance (disorder)|  ) : [0..0]  42752001 |Due to (attribute)|  =  781249001 |Consumption of contaminated food (event)|  AND [0..0]  246075003 |Causative agent (attribute)|  = <<  410607006 |Organism (organism)|  )) MINUS (<<  1149322001 |Intoxication (disorder)|  OR <<  1149222004 |Overdose (disorder)| )

Template Language

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 ( <<  1148742001 |Intentional event (event)|  OR <<  418019003 |Accidental event (event)| OR << 418715001 |Exposure to potentially harmful entity (event)) @dueto ]]}, [[~1..1 @rolegroup]]{ [[~1..1]] 246075003| Causative agent (attribute) |= [[+id ( << 105590001| Substance (substance) |OR << 373873005| Pharmaceutical / biologic product (product) |) @agent]], [[~0..1]] 363698007| Finding site (attribute) |= [[+id ( < 123037004| Body structure (body structure) |) ]], [[~0..1]] 116676008| Associated morphology (attribute) |= [[+id ( < 49755003| Morphologically abnormal structure (morphologic abnormality) |) ]]}|

Link to the misaligned concept report

Rules for generating descriptions:

  1. Apply General rules for generating descriptions for templates
  2. Remove the word 'event' and semantic tag from the value of |Due to|


EDITORIAL GUIDELINES for Causative agent (attribute):

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:

  • Chemical element with multiple modifications (e.g. 422232005 |Calcium lactate gluconate (substance)|
  • Liposome or lipid complex substances (e.g. 412088006 |Amphotericin B liposome (substance)|, 426490000 |Vincristine liposome (substance)|)
  • Pegylated substance (e.g. 385544005 |Pegfilgrastim (substance)|, 770965008 |Pegvaliase (substance)|)
  • Salt forms (e.g. 273948005 |Chloral hydrate (substance)|, 396063006 |Fluphenazine decanoate (substance)|)

Examples of exception:

  • 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 concepts representing a role grouper are 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.


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.
  • No labels