Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Page properties


StatusDraftReady for review
Version

0.15


Descriptions:

Termdescription typeLanguage/acceptabilityLanguage/acceptabilityCase significance

At [qualifier] risk of [event or finding] (finding)

FSNus:Pgb:Pci

At [qualifier] risk of [event or finding]

SYNus:Pgb:Pci

Concept model:

Attribute Group CardinalityAttribute CardinalityAttribute in Group CardinalityAttributeValue
0..01..1


Scg expression
116680003 |Is a (attribute)|



Scg expression
404684003 |Clinical finding (finding)|


0..11..11..1


Scg expression
42752001 |Due to (attribute)|



Scg expression
<<404684003 |Clinical finding (finding)|


0..11..11..1


Scg expression
719722006 |Has realization (attribute)|



Scg expression
[finding or event] < 404684003 |Clinical finding (finding)| OR <272379006 |Event (event)|


1..11..11..1


Scg expression
363714003 |Interprets (attribute)|



Scg expression
1255619009 |Risk level (observable entity)|



1..11..1


Scg expression
363713009 |Has interpretation (attribute)|



Scg expression
[qualifier] <272520006 |Degree findings (qualifier value)|


0..10..11..1


Scg expression
246454002 |Occurrence (attribute)|



Scg expression
<<282032007 |Periods of life (qualifier value)|


0..11..1


Scg expression
246075003|Causative agent (attribute)|



Scg expression
<< 105590001|Substance (substance)|


Definition status:  

Scg expression
900000000000073002|Defined (core metadata concept)|

Applies to:

Scg expression
<<281694009 |Finding of at risk (finding)|

Template Language

Scg expression
404684003 |Clinical finding (finding)|: 
[[~0..1]] {[[~1..1]] 42752001 |Due to (attribute)| = [[+id (<<404684003 |Clinical finding (finding)|)]]}, 
[[~0..1]] {[[~1..1]] 719722006 |Has realization (attribute)| = [[+id (< 404684003 |Clinical finding (finding)| OR <272379006 |Event (event)|)]]}, 
[[~1..1]] {
[[~1..1]] 363714003 |Interprets (attribute)| = [[+id (1255619009 |Risk level (observable entity)|)]],
[[~1..1]] 363713009 |Has interpretation (attribute)| = [[+id (<<272520006 |Degree findings (qualifier value)|)]]}
[[~0..1]] {
[[~0..1]] 246454002 |Occurrence (attribute)| = [[+id(<<282032007 |Periods of life (qualifier value)|)]],
[[~0..1]] 246075003 |Causative agent (attribute)| = [[+id (< 105590001 |Substance (substance)|)]]}

Link to the misaligned concept report

Overdose misaligned concept report 2021-Dec-14

Rules for generating descriptions:

  1. Apply General rules for generating descriptions for templates

Editorial guidelines for selection of Causative agent attribute value:

The following editorial guidelines apply to concepts in the International Release; editorial guidelines for concepts in national extensions may vary.

...

Example:

  • 295184007 |Morphine overdose (disorder)|

...

Concepts representing substance modifications are exceptions and may be included if the overdose profile is significantly different from the substance base.

Exception examples:

  • Liposome or lipid complex substances (e.g. 412088006 |Amphotericin B liposome (substance)|, 426490000 |Vincristine liposome (substance)|)
  • Pegylated substance (e.g. 385544005 |Pegfilgrastim (substance)|, 770965008 |Pegvaliase (substance)|)
  • Salt forms (e.g. 273948005 |Chloral hydrate (substance)|, 396063006 |Fluphenazine decanoate (substance)|)

Example:

  • 296136008 |Chloral hydrate overdose (disorder)|
  • 296213007 |Fluphenazine decanoate overdose (disorder)|

...

Overdose concepts representing a disposition grouper should be modeled using a Causative agent that is a descendant of 105590001 |Substance (substance)|.

Example:

  • 297053006 |Overdose of angiotensin-converting-enzyme inhibitors (disorder)|
  • 296515004 |Opiate antagonist overdose (disorder)|

...

Overdose concepts representing a role grouper should be modeled using a Causative agent that is a descendant of 105590001 |Substance (substance)|. Role groupers will be transitioned to the 763158003 |Medicinal product (product)| hierarchy in a future release.

Example:

  • 297006008 |Diuretic overdose (disorder)|
  • 295217003 |Non-steroidal anti-inflammatory overdose (disorder)|

...

Overdose concepts representing a structure grouper should be modeled using a Causative agent that is a descendant of 105590001 |Substance (substance)|.

Example:

  • 295188005 |Pethidine analog overdose (disorder)|
  • 1155996000 |Phenothiazine and/or phenothiazine derivative overdose (disorder)|

...

Overdose concepts representing a role grouper should be modeled using a Causative agent that is a descendant of 105590001 |Substance (substance)|. Role groupers will be transitioned to the 763158003 |Medicinal product (product)| hierarchy in a future release.

...

...

The following types of groupers are out of scope; existing concepts have been inactivated or will be addressed in future release:

  • Groupers based on more than one role (e.g. 292722006 |Chelating agents and antidotes adverse reaction (disorder)|)
  • Groupers based on body system or intended site or route of administration (e.g. 292548001 |Drug groups primarily affecting respiratory system adverse reaction (disorder)|) or 417895009 |Topical agent adverse reaction (disorder)|)
  • Groupers based on disposition, role, or structure combined with an individual substance (e.g. 287177000 |Sulfonamide/trimethoprim reaction (disorder)| or 292513008 |Methyldopa and diuretic adverse reaction (disorder)|)
  • Groupers based on "combined" or "compound" substances (e.g. 292983008 |Combined penicillin preparation adverse reaction (disorder)| or 293358005 |Compound iron preparations adverse reaction (disorder)|)
  • Groupers based on disposition or structure combined with intended site or route of administration (e.g. 433494006 |Adverse effect of oral diphosphonate (disorder)|)

Rules for description generation:

  1. 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. 
  2. For the PT, align terming and case sensitivity with the US and GB PT for the 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.

JIRA ticket for implementation:

...