Descriptions:
| Term | description type | Language/acceptability | Langauge/acceptability | Case significance |
|---|---|---|---|---|
Adverse [finding site] reaction caused by [agent] (disorder) Existing content has two different terming patterns - need agreement on which is preferred:
| FSN | us:P | gb:P | ci |
Adverse reaction caused by [agent] See FSN re: existing patterns | 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)|) @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 - update examples to reflect final decision re: terming pattern |
|---|---|---|---|---|
| Substance | Base | yes | none | Example:
Expected classification: |
| Substance | Modification | no, unless explicitly documented as exception | TBD | Example: Expected classification: |
| Substance | Disposition grouper | yes | none | Example:
Expected classification: |
| Product | Disposition grouper | no | none | Note: Disposition 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 Adverse reaction to disposition grouper concepts. |
| Substance | Role grouper | no | none | Note: Role groupers in the Substance hierarchy will be inactivated in a future release and should no longer be used for modeling in this hierarchy. |
| Product | Role grouper | yes | none | Example: Expected classification: TBD if there are any restrictions on which product roles can be used in modeling in this subhierarchy Grouper concepts should represent only a single role; groupers that represent multiple roles (e.g. hypnotic AND/OR sedative or Chelating agents and antidotes) are out of scope. |
| Substance | Structure grouper | yes | none | Example:
Expected classification: |
| Product | Structure grouper | no | none | Note: 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 Adverse reaction to structure grouper concepts. |
| Product or Substance | Body system grouper | no | none | Note: 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. ADD EXAMPLES |
| Product | Medicinal product-containing | yes | none | Example: Expected classification |
| Product | Medicinal product-only | no | none | Note: Medicinal product-containing can be used for modeling in the Adverse reaction caused by X subhierarchy. |
| Product | Medicinal product form-containing | yes | none | Example: Expected classification: |
| Product | Medicinal product form-only | no | none | Note: Medicinal product form-containing can be used for modeling in the Adverse reaction caused by X subhierarchy. |
| Product | Clinical drug | no | none | n/a |
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 are not allowed unless explicitly identified as an exception.