Page tree

Versions Compared

Key

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

...

Hierarchy

Concept type

Allowed

Exception

Examples and Notes - update examples to reflect final decision re: terming pattern

Hierarchy

Concept type

Allowed

Exception

Examples and Notes - update examples to reflect final decision re: terming pattern

SubstanceBaseyesnone

Example:

  • 294418003 |Allergy to phenol (finding)|

Expected classification: NEEDS INTERNAL AGREEMENT

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

Example:

293908005 |Allergy to chloral hydrate (finding)|

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

Expected classification: NEEDS INTERNAL AGREEMENT

  • 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.
SubstanceDisposition grouperyesnone

Example:

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

Expected classification results: NEEDS INTERNAL AGREEMENT

  • Classification results are expected to be consistent with the modeling in the Substance hierarchy and with other existing concepts in the subhierarchy.
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. NEEDS INTERNAL AGREEMENT
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. NEEDS INTERNAL AGREEMENT

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 and with other existing concepts in the subhierarchy.
  • 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: NEEDS INTERNAL AGREEMENT

  • Classification results are expected to be consistent with the modeling in the Substance hierarchy and with other existing concepts in the subhierarchy.
ProductStructure groupernononeNo 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
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. NEEDS INTERNAL AGREEMENT

ProductMedicinal product-containingyesnone

Example:

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

Expected classification results: NEEDS INTERNAL AGREEMENT

  • 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. NEEDS INTERNAL AGREEMENT
ProductMedicinal product form-containingyesnone

No use case has been identified for use of this concept type for modeling in this subhierarchy. NEEDS INTERNAL AGREEMENT


ProductMedicinal product form-onlynononeNo use case has been identified for use of this concept type for modeling in this subhierarchy. NEEDS INTERNAL AGREEMENT
ProductClinical drugnononeNo use case has been identified for use of this concept type for modeling in this subhierarchy. NEEDS INTERNAL AGREEMENT

...