Allergic disease (disorder) - v3.0

Status	Ready for implementation
Version	3.0
Version in Prod	2.0

Descriptions:

Term	description type	Language/acceptability	Language/acceptability	Case significance

Term	description type	Language/acceptability	Language/acceptability	Case significance
Allergic [morphology] of [body structure] caused by [substance and/or product] (disorder)	FSN	us:P	gb:P	ci
Allergic [morphology] of [body structure] caused by [substance and or product]	SYN	us:P	gb:P	ci

Concept model:

Attribute cardinality	Attribute cardinality in role group	Attribute	Value

Attribute cardinality	Attribute cardinality in role group	Attribute	Value
1..1	0..0
0..1	0..1
0..1	0..1
0..1	0..1
1..*	0..1
	1..1
	1..1
	1..1

Definition status:

Applies to

<<

Template language:

Rules for generating descriptions:

Apply General rules for generating descriptions for templates

JIRA tickets:

https://projects.jira.snomed.org/browse/INFRA-8677

EDITORIAL GUIDELINES for Causative agent (attribute):

Hierarchy	Concept type	Allowed	Exception	Examples and Notes

Hierarchy	Concept type	Allowed	Exception	Examples and Notes
Substance	Base	yes	none	Concepts representing a substance base should be modeled using a Causative agent that is a descendant of 105590001 \|Substance (substance)\|. Examples: 91926002 \|Allergic rhinitis caused by grass pollen (disorder)\| Classification results are expected to be consistent with the modeling of the concept selected as the Causative agent in the Substance hierarchy.
Substance	Modification	no	none	No use case has been identified for use of this concept type for modeling in this subhierarchy.
Substance	Structure grouper	yes	none	Concepts representing a structure grouper should be modeled using a Causative agent that is a descendant of 105590001 \|Substance (substance)\|. 1155943009 \|Allergic contact dermatitis caused by metal and/or metal compound (disorder)\| Classification results are expected to be consistent with the modeling of the concept selected as the Causative agent in the Substance hierarchy.
Substance	Disposition grouper	yes	none	Concepts representing a disposition grouper should be modeled using a Causative agent that is a descendant of 105590001 \|Substance (substance)\|. Classification results are expected to reflect that the adverse reaction concepts are descendants of the appropriate disposition grouper based on the modeling of the 726542003 \|Has disposition (attribute)\| attribute in the substance hierarchy.
Substance	Role grouper	no	none	Currently concepts representing a role grouper are modeled using a Causative agent that is a descendant of 105590001 \|Substance (substance)\|. Note that role groupers will be transitioned to the 763158003 \|Medicinal product (product)\| hierarchy in a future release.
Product	Structure grouper	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.
Product	Disposition grouper	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.
Product	Role grouper	yes	none	Concepts representing a substance base should be modeled using a Causative agent that is a descendant of 105590001 \|Substance (substance)\|. Example: 200842003 \|Allergic contact dermatitis caused by adhesive (disorder)\| 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	Examples to be added - pending implementation of roles and products as causative agents
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.
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.
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.
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.