Page tree

StatusIn PROD


Latest version2.0


Termdescription typeLanguage/acceptabilityLanguage/acceptabilityCase significance
Burn of [body structure] (disorder)FSNus:Pgb:Pci

Burn of [body structure]


Concept model:

Definition status:  

900000000000073002 |Defined (core metadata concept)|

Applies To:

<<  125666000 |Burn (disorder)|

Rules for description generation:

  1. Apply General rules for generating descriptions for templates;

JIRA tickets

INFRA-3184 - Getting issue details... STATUS


  1. Should this have an ASSOCIATED MORPHOLOGY range of <<48333001 |Burn injury (morphologic abnormality)|? Or is this restricted to solely FSNs with just "burn" in it?

  2. I was trying to constrain it because there are other templates for subtypes of burn injury (e.g. full thickness; partial thickness), and I am deferring "types" of burns, e.g. (chemical, lightning).  But this may need to be reconsidered.

  3. Hi Penni Hernandez Do you know if there's a separate template or issue for first/second/third degree chemical burn? All I can find in IHTSDO-810 (artf6238) Burns is that they present a modelling challenge (in which I concur...).

  4. Hi, I did this burn work and the tracker stopped short of deciding what to do with "chemical burns" so that work has yet to done.   There are also challenges around burns of mucosa (e.g. eye, mouth). Feikje Hielkema-Raadsveld

  5. Hi Penni HernandezRight, I see. Should I submit a separate CRS concerning chemical burns? We've got a number of concepts in our extension for first/second/third degree chemical burns which we can't model properly. Or I could push a solution by creating morphologies for them, and then submitting them for promotion (smile)

  6. Monica Harry It looks like we're losing aligned concepts here because burns are now being defined as due to a traumatic event and this template doesn't allow for that.

    I'll add a topic to our QI call for discussing a policy of keeping templates in line with modeling decisions - and all the way to production.    This template is actually live in the template service but here it's showing "Ready for implementation".   

    CC Yongsheng Gao Michael Chu

  7. Peter G. Williams ,

    I'll take the hit on this.  The change to adding the DUE TO relationship came much after this template was created (and after much discussion about traumatic injuries) and I failed to go back and update it.  In this case, do we want to create new version and obsolete this one or just update?

    cc: Monica Harry

    1. Thanks Jim Case.   What do you say Yongsheng Gao?

      One of the things I struggle with, with Templates not being first class citizens that are versioned and published in a release is being able to look back in time and work out what our historic position was.     So my not-very-strong feeling is that we should create a new template version to allow us to track progression over time, but I don't know that we're quite at the level of maturity where it makes much difference.

  8. Hi Jim Case Peter G. Williams, This template has been implemented in the authoring platform. A new version template needs to be created separately. Then, this one will be archived after the new one is in PROD. 

    1. Yongsheng Gao and Peter G. Williams

      I will create a new one for review.