Page tree

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

Compare with Current View Page History

« Previous Version 30 Next »

Descriptions:

Termdescription typeLanguage/acceptabilityLangauge/acceptabilityCase significance

Adverse [finding site] reaction caused by [agent] (disorder)

Existing content has two different terming patterns - need agreement on which is preferred:

  • 292350008 |Alprazolam adverse reaction (disorder)|
  • 218620007 |Adverse reaction caused by naproxen (disorder)|
FSNus:Pgb:Pci

Adverse reaction caused by [agent]

See FSN re: existing patterns

SYNus:Pgb:Pci


Concept model:

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:

HierarchyConcept typeAllowedExceptionExamples and Notes - update examples to reflect final decision re: terming pattern
SubstanceBaseyesnone292350008 |Alprazolam adverse reaction (disorder)|
SubstanceModificationno, unless explicitly documented as exceptionTBDTBD
SubstanceDisposition grouperyesnone292736001 |Opioid antagonist adverse reaction (disorder)|
ProductDisposition groupernononeNote: Existing 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.
SubstanceRole groupernononeNote: Existing role groupers in the Substance hierarchy will be inactivated in a future release and should no longer be used for modeling in this hierarchy.
ProductRole grouperyesnone

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.

SubstanceStructure grouperyesnone218638005 |Adverse reaction caused by hydantoin derivative (disorder)|
ProductStructure groupernononeNote: Existing 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 SubstanceBody system groupernononeNote: Existing 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
ProductMedicinal product-containingyesnone

EXPECTED CLASSIFICATION:

ProductMedicinal product-onlynononeNote: Medicinal product-containing should be used for modeling in the Adverse reaction caused by X subhierarchy.
ProductMedicinal product form-containingyesnoneEXPECTED CLASSIFICATION:
ProductMedicinal product form-onlynononeNote: Medicinal product form-containing should be used for modeling in the Adverse reaction caused by X subhierarchy.
ProductClinical drugnononen/a


Rules for description generation:

  1. For the FSN, align terming and case sensitivity with the FSN for the Substance concept that is selected as the attribute value, excluding the semantic tag. 
  2. For the PT, align terming and case sensitivity with the US and GB PTs for the Substance concept that is selected as the attribute value.
  3. 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.
  4. Additional synonyms are not allowed unless explicitly identified as an exception.

JIRA ticket for implementation:


  • No labels