Page tree

StatusArchived
Version

1.0

Descriptions:

Termdescription typeLanguage/acceptabilityLanguage/acceptabilityCase significance
[course] [morphology] of [body structure] caused by [agent] (disorder)FSNus:Pgb:Pci
[course] [morphology] of [body structure] caused by [agent]SYNus:Pgb:Pci


Concept model:

Definition status:  


900000000000073002 |Defined|

Applies to:

<<  417893002 |Deformity (finding)|


Template Language:

64572001 |Disease (disorder)|  : [[~0..1]] {[[~0..1]]  263502005 |Clinical course (attribute)|  = [[ +id (<  288524001 |Courses (qualifier value)|  ) @course]]}, [[~1..1 @rolegroup]]{ [[~1..1]]  116676008 |Associated morphology (attribute)|  = [[+id(<<  6081001 |Deformity (morphologic abnormality)|  ) @morphology ]], [[~0..1]]  363698007 |Finding site (attribute)|  = [[+id(<  123037004 |Body structure (body structure)|  )]], [[~0..1]]  246454002 |Occurrence (attribute)|  =  282032007 |Periods of life (qualifier value)|  , [[~0..1]]  370135005 |Pathological process (attribute)|  = [[ +id ( <<  308490002 |Pathological developmental process (qualifier value)|  ) @proc]], [[~0..1]]  246075003 |Causative agent (attribute)|  = [[ +id (<  410607006 |Organism (organism)| OR <  105590001 |Substance (substance)|  OR  <  78621006 |Physical force (physical force)| ) @agent]] }


Link to the misaligned concept report

https://docs.google.com/spreadsheets/d/1QGAnnSbAKdloO2QtsPbN7Y6oK27EY3taGTWmnE-gmdU/edit#gid=2

Simple - https://docs.google.com/spreadsheets/d/16vB8OozMuqIp_Z5rc0Wb7uyzFhWwHUT49m8gk1B2sKI/edit

Rules for description generation:

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

JIRA ticket:

QI-276 - Getting issue details... STATUS

INFRA-3462 - Getting issue details... STATUS

9 Comments

  1. Hi Suzanne Santamaria, |physical force| has been modelled for some concepts. You might want to include it as allowed range. If you were intended to review them, it is fine to leave the template as it is.

    Regarding attribute |interprets|, the |Contracture of joint| template provides a model that mandates |interprets|. If we include this attribute as optional in this template, it might have less non-conformance report. However, it does not provide any guidance that what condition would require |interprets|. If we remove this attribute,  it would help us to identify subdomains that need additional attributes. So, we can develop more templates that is similar to Contracture of joint to help authoring.  If you prefer to include |interprets|, we also need to include |has interpretation| as optional. Both |interprets| and |has interpretation| need to be placed in a separate role group. Thought?

    1. Hi Yongsheng Gao, thank you for the feedback. I have updated the template to include physical force and removed the interprets attribute. 

  2. Thanks Suzanne Santamaria  The template is ready for implementation. The link to the report is added. Cheers, Yong

    1. Yongsheng Gao I just updated the attribute cardinally for Occurrence. It had been 1..1 and I just changed it to 0..1. Please confirm this change is what we want.

      1. Suzanne Santamaria  Yes, the occurrence should be optional as 0..1. 

  3. I wonder if there's a case for splitting this into two templates, as much for the sake of the semantic tag as anything Suzanne Santamaria

    I use the focus concept to indicate the PPP when I come to normalize, and I believe for the (finding) concepts I'll be setting that to Clinical Finding rather than Disease?

    1. Hi Peter G. Williams, I'm not sure if your comment is still current. We already have two templates for deformities. The other one is here: https://confluence.ihtsdotools.org/x/wTcwBQ.

      1. Thanks Suzanne Santamaria, having 417893002 |Deformity (finding)| as the applicable range for this template threw me.   Yes, the other template is what I needed to be using.

  4. Archiving this template as the other template Deformity of [body structure] (disorder) V2 Ready for implementation

    is ready for implementation in PROD.