Page tree


Status Ready for implementation
Version1.0


Descriptions:

Term

description type

Language/acceptability

Language/acceptability

Case Significance

Irrigation of [body structure] (procedure)

FSNus:Pgb:Pci
Irrigation of [body structure]PTus:Pgb:Pci

  

Concept model:

Definition status:  

900000000000073002 |Sufficiently defined by necessary conditions definition status (core metadata concept)|

Applies to:

<<  67889009 |Irrigation (procedure)|

Template language:


71388002 |Procedure (procedure)|  :
[[~1..* @IrrigationRoleGroup]]{
[[~1..1]]  
260686004 |Method (attribute)|   = [[ +id (   129332006 |Irrigation - action (qualifier value)|  ) @IrrigationAction ]] ,
[[~0..1]]  
405813007 |Procedure site - Direct (attribute)|   = [[ +id ( <   91723000 |Anatomical structure (body structure)|  ) @AnatomicalStructure ]] ,
[[~0..1]]  [[ +id (<< 
405815000 |Procedure device (attribute)| ) ]]  = [[ +id ( <   49062001 |Device (physical object)|  ) @Device ]] ,
[[~0..1]]  
424361007 |Using substance (attribute)|   = [[ +id ( <   105590001 |Substance (substance)|  ) @Substance ]] ,
[[~0..1]]  
363700003 |Direct morphology (attribute)|   = [[ +id ( <   49755003 |Morphologically abnormal structure (morphologic abnormality)|  ) @Morphology ]] ,
[[~0..1]]  
260507000 |Access (attribute)|   = [[ +id ( <   309795001 |Surgical access values (qualifier value)|  ) @Access ]]}


71388002 |Procedure (procedure)|  :
[[~1..* @IrrigationRoleGroup]]{
[[~1..1]]  
260686004 |Method (attribute)|   = [[ +id (   129332006 |Irrigation - action (qualifier value)|  ) @IrrigationAction ]] ,
[[~0..1]]  
405814001 |Procedure site - Indirect (attribute)|   = [[ +id ( <   91723000 |Anatomical structure (body structure)|  ) @AnatomicalStructure ]] ,
[[~0..1]]  [[ +id (<< 
405815000 |Procedure device (attribute)| ) ]]  = [[ +id ( <   49062001 |Device (physical object)|  ) @Device ]] ,
[[~0..1]]  
424361007 |Using substance (attribute)|   = [[ +id ( <   105590001 |Substance (substance)|  ) @Substance ]] ,
[[~0..1]]  
363700003 |Direct morphology (attribute)|   = [[ +id ( <   49755003 |Morphologically abnormal structure (morphologic abnormality)|  ) @Morphology ]] ,
[[~0..1]]  
260507000 |Access (attribute)|   = [[ +id ( <   309795001 |Surgical access values (qualifier value)|  ) @Access ]]}


Link to the misaligned concept report:

https://docs.google.com/spreadsheets/d/11Y5lqsEjMeFlk4-xz2JpADFcRSrQt4tP3GjvroBxsQA/edit#gid=0

Rules for generating descriptions:

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

JIRA ticket:

QI-1075 - Getting issue details... STATUS

INFRA-10397 - Getting issue details... STATUS



7 Comments

  1. Hi Yongsheng Gao , could you review this template for me please? 

    1. Hi Mark Banks , the direct and indirect procedure site attributes are not presented in the same role group currently. The draft template would allow users to have both attributes in a role group. It would be good to have separate templates for direct and indirect procedure sites. 

      Three device attributes for procedures could be simplified to a slot expression [[ +id (<< 405815000 |Procedure device (attribute)|) ]] with the range restriction to the device only. Of course, it could be < 405815000 |Procedure device (attribute)|) if we want to exclude the option for 'Procedure device'.

      The following are two templates and they can be combined together for the template compliance report. The report shows that there is only one expectation (234934008 Irrigation of periodontal pocket) for 'pure' irrigation procedures because of its "Has focus" attribute.  I think we can treat it as an except without adding this attribute. 

      71388002 |Procedure (procedure)| :
      [[~1..* @IrrigationRoleGroup]]{
      [[~1..1]]  260686004 |Method (attribute)|  = [[ +id (  129332006 |Irrigation - action (qualifier value)| ) @IrrigationAction ]] ,
      [[~0..1]]  405813007 |Procedure site - Direct (attribute)|  = [[ +id ( <  91723000 |Anatomical structure (body structure)| ) @AnatomicalStructure ]] ,
      [[~0..1]]  [[ +id (<< 405815000 |Procedure device (attribute)|) ]]  = [[ +id ( <  49062001 |Device (physical object)| ) @Device ]] ,
      [[~0..1]]  424361007 |Using substance (attribute)|  = [[ +id ( <  105590001 |Substance (substance)| ) @Substance ]] ,
      [[~0..1]]  363700003 |Direct morphology (attribute)|  = [[ +id ( <  49755003 |Morphologically abnormal structure (morphologic abnormality)| ) @Morphology ]] ,
      [[~0..1]]  260507000 |Access (attribute)|  = [[ +id ( <  309795001 |Surgical access values (qualifier value)| ) @Access ]]}


      71388002 |Procedure (procedure)| :
      [[~1..* @IrrigationRoleGroup]]{
      [[~1..1]]  260686004 |Method (attribute)|  = [[ +id (  129332006 |Irrigation - action (qualifier value)| ) @IrrigationAction ]] ,
      [[~0..1]]  405814001 |Procedure site - Indirect (attribute)|  = [[ +id ( <  91723000 |Anatomical structure (body structure)| ) @AnatomicalStructure ]] ,
      [[~0..1]]  [[ +id (<< 405815000 |Procedure device (attribute)|) ]]  = [[ +id ( <  49062001 |Device (physical object)| ) @Device ]] ,
      [[~0..1]]  424361007 |Using substance (attribute)|  = [[ +id ( <  105590001 |Substance (substance)| ) @Substance ]] ,
      [[~0..1]]  363700003 |Direct morphology (attribute)|  = [[ +id ( <  49755003 |Morphologically abnormal structure (morphologic abnormality)| ) @Morphology ]] ,
      [[~0..1]]  260507000 |Access (attribute)|  = [[ +id ( <  309795001 |Surgical access values (qualifier value)| ) @Access ]]}


  2. Thanks Yongsheng Gao I've updated this above.

    1. Thanks Mark Banks  the ticket for implementation has been submitted to the technical team. 


  3. The previous discussion in GC-1199 states "Discussed whether irrigation should actually follow the injection model and decided that it shouldn't. The conceptual difference being that in an injection the thing being injected is the substance, so direct substance is correct. In irrigations you are not irrigating the substance but rather irrigating a site/device but using a substance to do the irrigation."

    However, this approach, as adopted in this template, seems problematic since Irrigation - action is a still a subtype of Administration - action, which in turn is a subtype of Introduction.  This necessarily implies that the irrigating liquid is the direct object of the Method Irrigation - action,  since it (and not the recipient site) is the thing being introduced.  Irrigation (procedure) still infers under Introduction (procedure) and  has a text definition of "Administration that washes with a stream of liquid." 

    To align with the template, both the parent of Irrigation - action and the text definition of the procedure would have to be revised.  The latter would be simple enough - it could be reworded as "Washing with a stream of liquid."  If Irrigation - action is not considered a kind of introduction or administration of substance, then the most proximate parent seems to be the top-level Action (qualifier value).  (Conceivably one could argue for a parent of Removal - action,  if irrigation is considered a form of washing and therefore "removes" dirt or contamination, but this is a bit of a stretch).liquid

    Yongsheng Gao 




    1. Hi Penny LivesayThanks for the feedback. It looks like the issue could be addressed by the changes in the action hierarchy without modification to the model of this template. Is it right?

  4. Hi Yongsheng Gao 

    I think the template can remain as-is provided that Irrigation - action is made a subtype of Action (qualifier value) and the text definition for Irrigation (procedure) is also changed from "Administration that washes with a stream of liquid" to "Washing with a stream of liquid," to remove both connections between irrigation and administration.

    I can see the logic of including Procedure device in the template, since in an irrigation procedure, the device might be considered the direct object of irrigation (as in Irrigation of tube (procedure) or might be Using device (as in Irrigation with syringe (procedure), or even Access device as in Bronchoscopic lavage (procedure) (SYN Bronchoscopic irrigation).

     I am wondering, though, if it wouldn't be a good idea to add some explanation in the template and/or in the EG to clarify when the different device attributes should be used in irrigation procedures, and when a procedure site should be included. There is a lot of confusion about the use of the various "direct" and "indirect" procedure attributes, especially in combination, so I do think additional, explicit guidance on these points would be helpful:

    • Should a procedure site relationship should be added when the FSN specifies irrigation of a device that is defined in terms of its anatomic location . There is inconsistency in the modeling of existing concepts:

      Irrigation of biliary tube (procedure) is currently modeled with a RG of Method Irrigation + Procedure site Indirect Biliary tract + Direct device Tube

      Nasoenteric tube irrigation (procedure) is modeled with a RG of Method Irrigation + Direct device Nasoenteral tube, with no procedure site. 

      I think the identification of the tube itself by where it is placed does necessarily implies a procedure site, but there isn't any clear guidance or consistent precedence to indicate which of the above approaches should be used.
    • If a procedure site should be included, it would also be helpful to provide clear guidance on whether the body structure is the direct or indirect site.  If the intent is to irrigate (wash out) the lumen of the device, the body structure would be considered the indirect procedure site, and perhaps it is reasonable to infer that this is the intended meaning if the FSN is Irrigation (or lavage) of <device> (I think  <Device> irrigation is a bit more ambiguous, but would probably be reasonable to interpret the same way. Conversely, If the intent is to irrigate the body structure in which the tube or other device is placed, the FSN should be phrased to make that clear and the Method Irrigation would be grouped with a Procedure site Direct and Using device relationships, e..g. the clearly named and modeled  Irrigation of colon via cecostomy tube (procedure).