Page properties | ||||
---|---|---|---|---|
|
Descriptions:
Term | description type | Language/acceptability | Language/acceptability | Case Significance |
---|---|---|---|---|
[Accidental/Intentional] Poisoning caused by [agent] due to [event] (disorder) | FSN | us:P | gb:P | ci |
[Accidental/Intentional] Poisoning caused by [agent] due to [event] | SYN | us:P | gb:P | ci |
[Accidental/Intentional] [Agent] poisoning due to [event] | SYN | us:A | gb:A | ci |
...
- Pathological process is added so that the template includes 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 are 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
...
Hierarchy | Concept type | Allowed | Exception | Examples and Notes |
---|---|---|---|---|
Substance | Base | yes | none | Poisoning concepts representing a substance base should be modeled using a Causative agent that is a descendant of 105590001 |Substance (substance)|. Examples:
Classification results are expected to be consistent with the modeling of the concept selected as the Causative agent in the Substance hierarchy. |
Substance | Modification | no | yes | 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:
Examples:
|
Substance | Structure grouper | yes | none | Poisoning concepts representing a structure grouper should be modeled using a Causative agent that is a descendant of 105590001 |Substance (substance)|. Examples:
Classification results are expected to be consistent with the modeling of the concept selected as the Causative agent in the Substance hierarchy. |
Substance | Disposition grouper | yes | none | Poisoning concepts representing a disposition grouper should be modeled using a Causative agent that is a descendant of 105590001 |Substance (substance)|. Examples:
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. |
Substance | Role grouper | no | none | 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)|. Example:
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. |
Product | Structure grouper | no | none | 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. |
Product | Disposition grouper | no | none | 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. |
Product | Role grouper | yes | none | Examples to be added - pending implementation of roles and products as causative agents |
Product | Medicinal product-containing | yes | none | Examples to be added - pending implementation of roles and products as causative agents |
Product | Medicinal product-only | no | none | 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. |
Product | Medicinal product form-containing | no | none | No 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. |
Product | Medicinal product form-only | no | none | No 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. |
Product | Clinical drug | no | none | No 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. |
...