Page tree

StatusIn PROD
Version

1.0

Descriptions:

Termdescription typeLanguage/acceptabilityLanguage/acceptabilityCase significance

[Course] contusion of [X body structure] (disorder)

FSNus:Pgb:Pci

[Course] contusion of [X body structure]

SYNus:Pgb:Pci
[Course] bruise of [X body structure] SYNus:Agb:Aci


Concept model:

Definition status:  


900000000000073002 |Defined (core metadata concept)|

Applies to

<<  125667009 |Contusion (disorder)|

Template language:


Link to the misaligned concept report:

https://docs.google.com/spreadsheets/d/1-SX7NzyUUEltjYmDvIO56t408wbYfOIDBqGNt66ZXR8/edit#gid=0

Rules for generating descriptions:

  1. Apply General rules for generating descriptions for templates


JIRA tickets:

INFRA-5278 - Getting issue details... STATUS


10 Comments

  1. Hi Jim CaseI said I'd check out contusion for you and I assume this was the one since you've been in here recently.   I filled in the report above.  46 misaligned and it seems to be nearly all concepts which have some secondary morphology - a wound, fracture or focal damage - as well as the contusion in another role group.

  2. Many thanks Peter G. Williams for the quick action.  I will get right on it.  Looks like the template may need to be updated to reflect the second morphology, which would not be a subtype of contusion.  Would that be the right approach?

    1. Yes I think so, a 2nd optional role group where the morphology is << 49755003 |Morphologically abnormal structure (morphologic abnormality)| MINUS << 308492005 |Contusion - lesion (morphologic abnormality)|   to ensure that the 2nd role group contains a different morphology from the 1st.   Would we want the 2nd role group to always use the same finding site as the 1st role group?   We'd give that 2nd slot the same name as the 1st (eg @fsite) in that case to indicate they're expected to contain the same value - they're effectively the same thing in two different places.


      1. Peter G. Williams, no, the finding site could be different.

        See the proposed edits to make sure I got the cardinalities correct

  3. Hi Jim Case, I have updated the template language and included the clinical course in the description pattern. The term pattern for additional morphology and site would not be easy. It could be improved in future. The cardinality for the additional morphology is changed to optional to align with the role group cardinality. If you do not have any further changes, this template is ready for implementation. 

  4. Hi Yongsheng Gao, I have noticed that both the 363698007 |Finding site (attribute)| attributes in the Template Language are body structures and the FSN/SYN themselves require a body structure slot; can you confirm which finding site attribute should contain the body structure slot name? Thanks. 

    1. Hi Darryn McGaw, the finding site for contusion morphology should be used. I added @bodyStructure in the template. The finding site for the optional role group should have the same value. However, we could not express this at the moment. It will be possible after we implement the enhanced features in the draft template language later this year. Cheers, Yong

      1. Oh, in fact I have coded a rule into the QI project code that says if two slots have the same name, then the values set must be the same.     However I don't know that that's ever been used or tested and I'm not at all sure what the Template Service would think of that (FYI Michael Chu )    I'll put something down for next week to test that functionality.