Page tree

StatusIn PROD
Version

1.0

Descriptions:

Termdescription typeLanguage/acceptabilityLanguage/acceptabilityCase significance

[course] [periods of life][morphology] of [body structure] caused by [organism] (disorder)

FSNus:Pgb:Pci

[course] [periods of life][morphology] of [body structure] caused by [organism]

SYNus:Pgb:Pci


Concept model:

Definition status:  


900000000000073002 |Defined (core metadata concept)|

Applies to

<< 441457006 |Cyst (disorder)|

Template Language

Link to misalignment reports:

Iterations:

Rules for generating descriptions:

  1. Apply General rules for generating descriptions for templates
  2. Appy Enhancements for the Template Language;


Jira ticket:

QI-178 - Getting issue details... STATUS

INFRA-3244 - Getting issue details... STATUS

7 Comments

  1. 234988003 |Lateral radicular cyst (disorder)| is one example of many concepts in this subhierarchy which have been modelled with 370135005 |Pathological process (attribute)| -> 308490002 |Pathological developmental process (qualifier value)|  and the template specifies we should use exactly 308489006 |Pathological process (qualifier value)|

    I think we should allow that in the template, unless you disagree?   Penni Hernandez Yongsheng Gao

  2. If you are including the PATHOLOGICAL PROCESS relationship, then there is the potential for the need for a CAUSATIVE AGENT if we get into infected cysts such as 236376009 |Infected renal cyst (disorder)|.  This would extend the FSN description to include the notion of "infected".  What other PATHOLOGICAL PROCESSES were considered here (Pathological development process?).  If Congenital cysts were being included here, then that also has to be part of the FSN naming, as well as "embryonic cysts".  I would also consider inactivating 441457006 |Cyst (disorder)| as it is not very useful clinically and cysts are morphologic characteristics of body structures.  

  3. Would the congenital disorders fall under the "Congenital [morphology] of [body structure]" template?  Can congenital cysts be excluded from this template, or maybe create a second template? 

    I will look at inactivating 441457006|Cyst (disorder)|. 

    There are 17 concepts using "causative agent" and most are from Parasitic cyst (morphologic abnormality) and then the associated organism, I was going to look at inactivating a few that use "exudate", it doesn't seem like that actually causes the cyst, but have not looked at that closely as of yet. Jim Case Peter G. Williams Yongsheng Gao

    1. Penni Hernandez , we can segregate out the congenital cysts if you want, but this template has the OCCURRENCE attribute already, so how would you distinguish them?

      1. Yes I did that because of adult/childhood, I can try and change the FSN terming to accommodate more variants.

  4. I made finding site optional because this is a big hierarchy and I attempted to inactivate disorders that were simply the morphology with no finding sites.  Apparently, there is a "disorder" concept for just about every cyst "morphology" and as you inactivate some there is nothing to point to, tried creating a grouper of "784309007 |Cyst of body structure (disorder)|" to point inactivated concepts like 441457006 |Cyst (disorder)| to during inactivation.  But in the end this seemed to pull a threat too large to complete here.  That is why I made the finding site optional.

  5. Penni Hernandez  I have updated the template to have a more restrict ranges. It is not a problem to have some overlaps with other templates. These templates have different mandate fields. Since 441457006|Cyst (disorder)| is not a primitive concept, it should not be a problem to leave for organisation and navigation. Otherwise, we will have to use an ECL expression to specify the domain for this template.