Descriptions:
Term | description type | Language/acceptability | Langauge/acceptability | Case significance |
---|---|---|---|---|
Adverse [finding site] reaction to [agent] (disorder) | FSN | us:P | gb:P | ci |
Adverse [finding site] reaction to [agent] | SYN | us:P | gb:P | ci |
Concept model:
Attribute Cardinality | Attribute | Value | role group number | Role group cardinality |
---|---|---|---|---|
1..1 | 0 | N/A | ||
1..1 | 1 | 1..1 | ||
0..1 | [finding site] < 123037004 |Body structure (body structure)| |
Definition status:
900000000000073002 |Defined (core metadata concept)|
Template Language
281647001 |Adverse reaction (disorder)|: [[~1..1]] { [[~0..1]] 363698007 |Finding site (attribute)| = [[+id(< 123037004 |Body structure (body structure)|) @site]], [[~1..1]] 246075003 |Causative agent (attribute)| = [[+id( << 105590001 |Substance (substance)| OR << 373873005 |Pharmaceutical / biologic product (product)| OR << 260787004 |Physical object (physical object)| OR << 78621006 |Physical force (physical force)|) @agent]] }
Applies to:
<< 282100009 |Adverse reaction caused by substance (disorder)|
Editorial guidelines for selection of Causative agent attribute value:
Hierarchy | Concept type | Allowed | Exception | Examples and Notes (Note: Examples are existing concepts and may not reflect the terming patterns described in the template.) |
---|---|---|---|---|
Substance | Base | yes | none | Adverse reaction concepts should preferentially be modeled using a Causative agent that is a descendant of 373873005 |Pharmaceutical / biologic product (product)|. In cases where that is not possible, then a concept from the 105590001 |Substance (substance)| may be used. Example:
Expected classification (Agreed 21-Jan-2020):
|
Substance | Modification | no | TBD | Adverse reaction concepts should preferentially be modeled using a Causative agent that is a descendant of 373873005 |Pharmaceutical / biologic product (product)|. In cases where that is not possible, then a concept from the 105590001 |Substance (substance)| may be used. Example:
Expected classification (Agreed 21-Jan-2020):
|
Substance | Disposition grouper | yes | none | Adverse reaction concepts should preferentially be modeled using a Causative agent that is a descendant of 373873005 |Pharmaceutical / biologic product (product)|. In cases where that is not possible, then a concept from the 105590001 |Substance (substance)| may be used. Example:
Expected classification results (Agreed 21-Jan-2020):
|
Product | Disposition grouper | no | none | |
Substance | Role grouper | no | none | Role groupers in the Substance hierarchy will be inactivated in a future release and should not be used for modeling in this subhierarchy. (Agreed 21-Jan-2020) Insert examples of role grouper. |
Product | Role grouper | yes | none | Example: Expected classification results: TBD if there are any restrictions on which product roles can be used in modeling in this subhierarchy |
Product | Role + Structure grouper | no | TBD | No use case has been identified for use of this concept type for modeling in this subhierarchy. Existing groupers representing role + structure will be inactivated and replaced with structure grouper. (Agreed 11-Feb-2020) Example:
|
Substance | Structure grouper | yes | none | Example:
Expected classification (Agreed 21-Jan-2020):
|
Product | Structure grouper | no | none | No use case has been identified for use of this concept type for modeling in this subhierarchy. Structure groupers in the Product hierarchy should only exist as SD concepts with a corresponding concept in the Substance hierarchy; the corresponding concept in the Substance hierarchy should be used for modeling in this subhierarchy. (Agreed 21-Jan-2020) |
Product or Substance | Body system grouper | no | none | Body system groupers in both the Substance and Product hierarchies will be inactivated in a future release and should no longer be used for modeling in this hierarchy. (Agreed 21-Jan-2020) Example:
|
Product | Medicinal product-containing | yes | none | Example:
Expected classification results: Needs input from Drugs WG - see DRUGS-865
|
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. (Agreed 21-Jan-2020) |
Product | Medicinal product form-containing | yes | none | Example:
Expected classification results: Needs input from Drugs WG - see DRUGS-866
|
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. (Agreed 21-Jan-2020) |
Product | Clinical drug | no | none | No use case has been identified for use of this concept type for modeling in this subhierarchy. Extension model may provide sufficient use case for this. |
Rules for description generation:
- For the FSN, align terming and case sensitivity with the FSN for the concept that is selected as the attribute value, excluding the semantic tag.
- For the PT, align terming and case sensitivity with the US and GB PT for the concept that is selected as the attribute value.
- In cases where neither the US or GB PT matches the FSN, excluding the semantic tag, a synonym corresponding to the FSN is required unless explicitly identified as an exception.
- Additional synonyms "[agent] adverse reaction" should be added. Other synonyms are not allowed unless explicitly identified as an exception.