Status | Ready for implementation |
Version | 1.0 |
Descriptions:
Term | description type | Language/acceptability | Language/acceptability | Case Significance |
---|---|---|---|---|
Irrigation of [body structure] (procedure) | FSN | us:P | gb:P | ci |
Irrigation of [body structure] | PT | us:P | gb:P | ci |
Concept model:
Attribute Group Cardinality | Attribute Cardinality | Attribute cardinality in role group | Attribute | Value |
---|---|---|---|---|
0..0 | 1..1 | 0..0 | ||
1..* | 1..1 | |||
0..1 | ||||
0..1 | ||||
0..1 | ||||
0..1 | ||||
0..1 | ||||
1..* | 1..1 | |||
0..1 | ||||
0..1 | ||||
0..1 | ||||
0..1 | ||||
0..1 |
Definition status:
Applies to:
<< 67889009 |Irrigation (procedure)|
Template language:
[[~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:
- Apply General rules for generating descriptions for templates;
- Apply Enhancements for the Template Language;
JIRA ticket:
- QI-1075Getting issue details... STATUS
- INFRA-10397Getting issue details... STATUS
7 Comments
Mark Banks
Hi Yongsheng Gao , could you review this template for me please?
Yongsheng Gao
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 ]]}
Mark Banks
Thanks Yongsheng Gao I've updated this above.
Yongsheng Gao
Thanks Mark Banks the ticket for implementation has been submitted to the technical team.
Penny Livesay
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
Yongsheng Gao
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?
Penny Livesay
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:
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.