SNOMED Spaces

Allergy to [substance/Product] (finding) - v3.0

2025-Sep-09

Status	Ready for implementation
Version	2.7
Version in PROD	2.0

Descriptions:

Term	description type	Language/acceptability	Language/acceptability	Case Significance

Term	description type	Language/acceptability	Language/acceptability	Case Significance
Allergy to [substance or product] (finding)	FSN	us:P	gb:P	ci
Allergy to [substance or product]	SYN	us:P	gb:P	ci
[substance or product] allergy	SYN	us:A	gb:A	ci

Concept model:

Attribute Group Cardinality	Attribute Cardinality	Attribute in Group Cardinality	Attribute	Value
	1..1	0..0
1..1		1..1
1..1		1..1

Definition status:

{"timestamp":1781567025522,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"}

Applies to:

{"timestamp":1781567025494,"msg":"A unknown Exception Occurred","errorMsg":"The provided AtlassianHostUser did not specify a user to act as.","code":"500"}

EDITORIAL GUIDELINES for Causative agent (attribute):

Hierarchy	Concept type	Allowed	Exception	Examples and Notes

Hierarchy	Concept type	Allowed	Exception	Examples and Notes
Substance	Base substance	yes	none	Allergy concepts representing a substance base should be modeled using a Causative agent that is a descendant of 105590001 \|Substance (substance)\|. 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.
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 (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)\|
Substance	Disposition grouper	yes	none	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.
Substance	Structure grouper	yes	none	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.
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. (Agreed 21-Jan-2020)
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. (Agreed 21-Jan-2020)
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. (Agreed 21-Jan-2020)
Product	Role grouper	yes	none	Example: 417930000 \|Allergy to adhesive agent (finding)\| Classification results are expected to be consistent with the modeling in the Substance hierarchy and with other existing concepts in the subhierarchy.
Product	Medicinal product-containing	yes	none	Example: 294522005 \|Allergy to ampicillin and cloxacillin (finding)\| Expected classification results: NEEDS INTERNAL AGREEMENT 294650000 \|Allergy to vaccine product containing Mumps orthorubulavirus antigen (finding)\| https://snomed.atlassian.net/wiki/display/IAP/Allergy+to+X+vaccine
Product	Medicinal product-only	no	none	No 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)
Product	Medicinal product form-containing	no	none	No 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)
Product	Medicinal product form-only	no	none	No 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)
Product	Clinical drug	no	none	No 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)

Comments