...
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:
Adverse reaction to X | FSN | us:P | gb:P | ci |
Adverse [finding site] reaction caused by [agent] Adverse reaction to X Synonym X adverse reactionSee FSN re: existing patterns | SYN | us:P | gb:P | ci |
Concept model:
...
Hierarchy | Concept type | Allowed | Exception | Examples and Notes - update examples to reflect final decision re: terming pattern |
---|---|---|---|---|
Substance | Base | yes | none | Example:
Expected classification: NEEDS INTERNAL AGREEMENT - agreed
|
Substance | Modification | no | TBD | Example: 292392003 |Fluphenazine adverse reaction (disorder)| 292389002 |Fluphenazine decanoate adverse reaction (disorder)| 292390006 |Fluphenazine enanthate adverse reaction (disorder)| Expected classification: NEEDS INTERNAL AGREEMENT - agreed
|
Substance | Disposition grouper | yes | none | Example:
Expected classification results: NEEDS INTERNAL AGREEMENT - agreed
|
Product | Disposition grouper | no | none | No use case has been identified for use of this concept type for modeling in this subhierarchy. 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 in this subhierarchy.NEEDS INTERNAL AGREEMENT - agreed until use case appears |
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. NEEDS INTERNAL AGREEMENT 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 |
Substance | Structure grouper | yes | none | Example:
Expected classification: NEEDS INTERNAL AGREEMENT - agreed
|
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. NEEDS INTERNAL AGREEMENT - agreed |
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. NEEDS INTERNAL AGREEMENT - agreed to inactivate these concepts. Example:
|
Product | Medicinal product-containing | yes | none | Example:
Expected classification results: NEEDS INTERNAL AGREEMENT - further discussion needed with Drug Project Group re: expectations for classification
|
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. NEEDS INTERNAL AGREEMENT - agreed till use case appears |
Product | Medicinal product form-containing | yes | none | Example:
Expected classification results: NEEDS INTERNAL AGREEMENT - further discussion needed with Drug Project Group re: expectations for classification
|
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. NEEDS INTERNAL AGREEMENT - agreed till use case appears |
Product | Clinical drug | no | none | No use case has been identified for use of this concept type for modeling in this subhierarchy. NEEDS INTERNAL AGREEMENT - agreed till use case appears Extension model may provide sufficient use case for this. |
Rules for description generation:
...