Page tree

StatusReady for implementation

Version

3.0
Version in Prod2.0

Descriptions:

Termdescription typeLanguage/acceptabilityLanguage/acceptabilityCase significance

Allergic [morphology] of [body structure] caused by [substance and/or product] (disorder)

FSNus:Pgb:Pci

Allergic [morphology] of [body structure] caused by [substance and or product]

SYNus:Pgb:Pci

Concept model:

Definition status:  


900000000000073002 |Defined (core metadata concept)|

Applies to

<<  781474001 | Allergic disorder (disorder)|

Template language:

 

Rules for generating descriptions:

  1. Apply General rules for generating descriptions for templates

JIRA tickets:

INFRA-8677 - Getting issue details... STATUS

EDITORIAL GUIDELINES for Causative agent (attribute):

Hierarchy

Concept type

Allowed

Exception

Examples and Notes

SubstanceBaseyesnone

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.

SubstanceModificationnonone

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

SubstanceStructure grouperyesnone

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.

SubstanceDisposition grouperyesnone

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.

SubstanceRole groupernonone

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.

ProductStructure groupernonone

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.

ProductDisposition groupernononeNo 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.
ProductRole grouperyesnone

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.
ProductMedicinal product-containingyesnone

Examples to be added - pending implementation of roles and products as causative agents

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.
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.
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.
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.



11 Comments

  1. Hi Yongsheng Gao

    This template is created as the result of QI + Substance/product enhancement project and is an update of an older template (v 2.0) currently in production:

    https://confluence.ihtsdotools.org/display/SCTEMPLATES/Allergic+%5Bdisease%5D+caused+by+%5Bsubstance%5D+%28disorder%29+-+v2.0

    Please let me know if any modification is required. 

    Thanks,

    Farzaneh

    1. Hi Farzaneh Ashrafi, the current domain can be extended to 781474001 |Allergic disorder (disorder)| because the causative agent allows medicinal product now. This template can be more generic if the cardinality of causative agent is 0..1 to cover those conditions without causative agents. The reported allergic disorders without causative agents can be found at https://docs.google.com/spreadsheets/d/1_mI5z55Nzpwi3CLzfclDeV2pFuT4_XzEcpYCbvg2Iq8/edit#gid=0

      Peter G. Williams I think something is not right with the misalignment report. The above report should include all misaligned concepts that do not have a causative agent. For example, 420373003 |Allergic disorder of digestive system (disorder)| is in the report. However, its subconcepts without causative agent are missing from the report, e.g. 1824008 |Allergic gastritis (disorder)|. Could you please have a look?

  2. Hi Yongsheng Gao

    Thanks for the review. I was focused on the disorders caused by substance for the Product/Substance enhancement project. But I see your point. I apply the changes as suggested.  

    Cheers,

    Farzaneh

    1. Cheers, I added a ticket to the technical team. 

  3. Hi Yongsheng Gao

    As discussed, I expanded the range of the causative agent attribute to include organism, physical force and physical object. Please can you update the JIRA ticket for the tech team?

    Thanks,

    Farzaneh

    1. Hi Farzaneh Ashrafi, we are okay with the updates because the development of template has not started yet.  

  4. Hi Yongsheng Gao

    I reviewed the updated Misaligned report and while the majority of the concepts are fixed, there are a few remaining that may result in changes in the template. I would like to discuss those with you before proceeding. Is it okay to put the ticket for this template on-hold until after our discussion? Apologies for the inconvenience, but the change in the scope resulting in additional misaligned concepts requires some reconsiderations.

    Thanks,

    Farzaneh

    1. Hi Farzaneh Ashrafi I have updated the JIRA ticket and the status of this template.

      1. Hi Yongsheng Gao

        The template is updated and ready for implementation.

        Thanks,

        Farzaneh

        1. Cheers Farzaneh Ashrafi it is handed over to the technical team now.

          1. Many thanks. I will close the associated tickets.