...
Hierarchy | Concept type | Allowed | Exception | Examples and Notes |
---|---|---|---|---|
Substance | Base | yes | none | Example:
Expected classification: NEEDS INTERNAL AGREEMENT - Agreed
|
Substance | Modification | no | yes | 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 - 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 |
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 - Agreed Insert examples of role grouper. |
Product | Role grouper | yes | none | Example: 294367002 |Allergy to antiviral agent (finding)| Expected classification results: NEEDS INTERNAL AGREEMENT
|
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 |
Product | Medicinal product-containing | yes | none | Example:
Expected classification results: NEEDS INTERNAL AGREEMENT - to be further discussed with the Drug project re: expected classification
|
Product | Medicinal product-only | no | none | No use case has been identified for use of this concept type for modeling in this subhierarchy. NEEDS INTERNAL AGREEMENT - Agreed |
Product | Medicinal product form-containing | no | none | No use case has been identified for use of this concept type for modeling in this subhierarchy. NEEDS INTERNAL AGREEMENT - Agreed |
Product | Medicinal product form-only | no | none | No use case has been identified for use of this concept type for modeling in this subhierarchy. NEEDS INTERNAL AGREEMENT - Agreed |
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 |
...