Page tree

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

Compare with Current View Page History

« Previous Version 12 Next »

Descriptions:

Termdescription typeLanguage/acceptabilityLangauge/acceptabilityCase significance

Allergy to [substance] (finding)

FSNus:Pgb:Pci

Allergy to [substance]

SYNus:Pgb:Pci


Concept model:

Definition status:  


900000000000073002 |Defined (core metadata concept)|

Applies to:

<<  419199007 |Allergy to substance (disorder)|

EDITORIAL GUIDELINES for Causative agent (attribute):

Hierarchy

Concept type

Allowed

Exception

Examples and Notes

SubstanceBaseyesnone

Example:

  • 294418003 |Allergy to phenol (finding)|

Expected classification (Agreed 21-Jan-2020):

  • Classification results are expected to be consistent with the modeling in the Substance hierarchy.
SubstanceModificationnoyes

Example:

293908005 |Allergy to chloral hydrate (finding)|

Chloral hydrate is a sedative and may not be well-represented by "Chloral derivative".

Expected classification (Agreed 21-Jan-2020):

  • Classification results are expected to be consistent with the modeling in the Substance hierarchy and with other existing concepts in the subhierarchy. Concepts modeled using a modification should have the concept modeled using the base as an inferred parent if such a concept exists.
    • 782530003 |Allergy to chloral derivative (finding)| will be modeled with Causative agent = 418037002 |Chloral derivative (substance)| and will have the following inferred descendants:
      • 293908005 |Allergy to chloral hydrate (finding)|
SubstanceDisposition grouperyesnone

Example:

  • 294275005 |Allergy to opioid receptor antagonist (finding)|

Expected classification results (Agreed 21-Jan-2020):

  • Classification results are expected to be consistent with the modeling in the Substance hierarchy for concepts modeled with an attribute value from the Substance hierarchy.
ProductDisposition groupernononeNo 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. (Agreed 21-Jan-2020)
SubstanceRole groupernonone

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)


The following will be modelled with product role groupres

  • 294606001 Allergy to antituberculosis agent (finding)
  • 294605002 Allergy to antimycobacterial agent (finding)
  • 294450008 Allergy to anthelmintic agent (finding)
  • 294367002 Allergy to antiviral agent (finding)
  • 294461000 Allergy to antibacterial drug (finding)
ProductRole grouperyesnone

Example:

294367002 |Allergy to antiviral agent (finding)|

Expected classification results: NEEDS INTERNAL AGREEMENT

  • Classification results are expected to be consistent with the modeling in the Substance hierarchy.
  • TBD if there are any restrictions on which product roles can be used in modeling in this subhierarchy
SubstanceStructure grouperyesnone

Example:

  • 782607004 |Allergy to phenothiazine derivative (finding)|

Expected classification (Agreed 21-Jan-2020):

  • Classification results are expected to be consistent with the modeling in the Substance hierarchy and with other existing concepts in the subhierarchy.
ProductStructure groupernonone

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 SubstanceBody system groupernonone


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)

ProductMedicinal product-containingyesnone

Example:

  • 294522005 |Allergy to ampicillin and cloxacillin (finding)|

Expected classification results: Needs input from Drugs WG - see DRUGS-865

  • 294522005 |Allergy to ampicillin and cloxacillin (finding)| will be modeled with Causative agent = 346320003 |Product containing ampicillin and cloxacillin (medicinal product)| and will have the the following inferred parents:
    • 294506009 |Allergy to ampicillin (finding)| with Causative agent = 387170002 |Ampicillin (substance)|
    • 294501004 |Allergy to cloxacillin (finding)| with Causative agent = 373276005 |Cloxacillin (substance)|
ProductMedicinal product-onlynononeNo 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)
ProductMedicinal product form-containingnononeNo 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)
ProductMedicinal product form-onlynononeNo 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)
ProductClinical drugnononeNo 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)

Template language

419199007 |Allergy to substance (finding)|  : [[~1..1 @rolegroup]] { [[~1..1]]  719722006 |Has realization (attribute)|  =  472964009 |Allergic process (qualifier value)| , [[~1..1]]  246075003 |Causative agent (attribute)|  = [[ +id (<  105590001 |Substance (substance)|  ) @causative]] }

 Misalignment report:

https://docs.google.com/spreadsheets/d/1CUWI2KYdfjj2MuFTLif1AzCk8BaFYpNN0738F5gJvdk/edit#gid=0

Rules for description generation:

  1. Remove the semantic tag, e.g. (body structure)
  2. Remove 'Structure of' from [body structure] if term starts with 'Structure of'   e.g. 709530002|Structure of phalanx of hand (body structure)|
  3. Remove 'structure' from [body structure] if term contains 'structure', e.g. 69536005|Head structure (body structure)|   24097009|Bone structure of hand (body structure)|

JIRA ticket for implementation:


  • No labels