Time:
1330-1700 KST
2130 - 0100 PDT
Zoom Meeting Details
Join meeting:https://snomed.zoom.us/j/84115133271?pwd=69A6geBbO5WnmkUnOyDpz9AQcVNj15.1
Password: 264013
View more on Confluence:
https://confluence.ihtsdotools.org/display/editorialag/SNOMED+CT+Editorial+Advisory+Group
Meeting Files:
Objectives
- Obtain consensus on agenda items
Discussion items
Item | Description | Owner | Notes | Action |
---|---|---|---|---|
1 | Call to order and role call | This meeting is being recorded to ensure that important discussion points are not missed in the minutes. The recording will be available to the SNOMED International community. Joining the meeting by accepting the Zoom prompt declares that you have no objection to your comments being recorded | ||
2 | Conflicts of interest and agenda review | None recorded | ||
3 | New member and appreciation for service | The EAG welcomes Dr. Jeremy Rogers back to the EAG after a hiatus and expresses their gratitude to Dr. Jeff Pierson for his service on the EAG for the last 6 years. | ||
4 | Update on progress from EAG discussions | Status of EAG discussed topics since April 2024: Completed, In progress
| ||
5 | Transplantation update | At the September EAG call, it was suggested by the group that normal body structures be used instead of the transplanted body structures and that the direct substance relationship be removed unless it was necessary to sufficiently define the concept. These changes have been made and are currently ready for review by the EAG in the TS browser (project QININ and tasks QININ-270, QININ-271). It was also noticed that the top level concept 77465005 |Transplantation (procedure)| had lost a substantial number of subtypes following the remodeling efforts. The EAG asked for more details on this loss of subtypes. A worksheet detailing these changes for 89 affected concepts is attached. (Please download before trying to review the content) Discussion: Decision: | ||
6 | Container modeling | At the November 2023 EAG call, a proposal to update the Physical object MRCM to allow for the modeling of containers was presented. The EAG requested additional information as well as examples of the proposed modeling. Feikje Hielkema-Raadsveld and Daniel Karlsson were provided with access to the SNOMED authoring platform to test their proposed model. Questions that arose from this testing include:
Discussion: Comment from Matt Cordell Container modelling – “intended content should be specimen”, substance seems more accurate. If becomes a “specimen” in the container. General comments: Discussion on the use of substance vs. specimen. The purpose of the model is to create models for pre-manufactured specimen specific containers. The reason for the project is to address the need from some members to create a hierarchy of specimen containers to support European data projects and to allow for subsumption testing. An issue that it would resolve is to allow specification of a container based on its characteristics in a FHIR model. There are currently about 100 concepts that would be affected by this model. This would allow for a cleanup of the container hierarchy as well. Many of the concepts will require renaming or replacement. What is the difference between a collection tube and a transfer tube? May need to go back to GMDN to get definitions. Their definitions may not be consistent with SNOMED. Need more information on clot activators. How to represent. Evacuated or non-evacuated containers. Jim Case stated this is an intrinsic characteristic of the container and should be represented. Concern expressed about the complexity of the model and its relationship to other attributes that are already defined for devices. Specific editorial guidance will be necessary to allow for proper and consistent use of a physical object concept model that needs to represent such a wide variety of objects. 2024-10-21 From Feikje Hielkema-Raadsveld
Decision: Further discussion will be held at the October face-to-face meeting in Korea. | ||
7 | Age-related events modeling | Current and prior editorial policy for modeling of Events (<<272379006 |Event (event)|) stated that while the allowed attributes for events closely aligned with the Clinical finding concept model, editorial policy for using these attributes to model events were still under development. However, one restriction has been applied and that is: "The Event hierarchy should not precoordinate periods of life/occurrence within the event concept." It has been brought to our attention that there are a number of event concepts that do reference periods of life in which the event occurred. Examples:
A few of these have been modeled using the OCCURRENCE attribute in spite of the editorial guidance. A member request has asked that we look at this policy as modeling of other concepts is being affected due to this restriction on modeling of events. Q: As the OCCURRENCE attribute is currently an allowed attribute for EVENTS, should there be any restrictions on the use of these attributes. If they should not be used, should the MRCM be modified to remove them from the allowed attributes set? Discussion: Comment from Matt Cordell
Do we have a policy for the use of events or finding in definition of situations? Decision: Agree that the removal of the restriction on the use of OCCURRENCE for events. This should be applied to the entire event hierarchy WRT the application of OCCURRENCE. A review of abuse modeling will be undertaken. | ||
8 | Bypass graft revision proposal | As requested from the EAG, a list of definitions has been developed that will guide content authors in the correct modeling of concepts related to bypass, bypass graft, shunt, etc.: The relevant Briefing note is attached above. Proposal for definition of concepts under 48537004 |Bypass graft (procedure)|.
Discussion: James R. Campbell - Definition of ANASTOMOSIS: While the proposed definition is technically sound, I think it is not clinically correct. I know of no surgical anastomoses that are constructed between fibers. The structures involved are always tubular or channels, both with a lumen. The purpose of the anastomosis is to connect the lumens for flow of gas or fluids between the two structures. There were a few comments around the definitions. What is meant by "cross-connection"? Definitions will be revised based on these comments (to be included). Replace "cross-connection" with "connection". Shunts and bypass will be subtypes of anastomosis. Why is an interposition graft considered a repair instead of a construction? What is the difference between construction and repair? Will be discussed in the next agenda item. Will revise this definition based on the decisions from that item. How does proximal and distal anastomosis apply to non-tubular structures? Can we just use the term "repair" for these concepts? Jeff Pierson - I would suggest that tendon is not relevant to anastomosis. It would be either a repair, transfer, or a graft. we will need to determine whether this applies to nerves well. There needs to be more editorial guidance with examples to correctly apply these definitions. Can we determine whether it is beneficial to use anastomosis for all of these and adding a repair RG where needed. The clinical usage of the term anastomosis complicates the interpretation of its use in some domains, such as neurosurgery. For non-tubular structures, may want to keep the term "anastomosis" in the description, but not use the term in the METHOD, and focus on the repair aspect. This will require very specific editorial guidance for how to name and model this type of term. Decision: 2024-03-11 Comments will be added to the document by the EAG members. 2024-04-16: Proposed definitions will be revised based on input and resubmitted to the EAG for review. 2024-08-19: Postponed 2024-09-23: Postponed to later meeting 2024-10-21: Definitions will be updated based on comments. Agree that we can use proximal and distal anastomosis actions for anastomosis concepts. |
| |
9 | Revision of Construction - action and | Victor Medina | 410614008 |Construction (procedure)| is currently a subtype of 4365001 |Surgical repair (procedure)|. It is recognized that not all construction procedures involve a repair (although reconstruction procedures do). A briefing note (attached) outlines the proposal to rectify this issue. Discussion: Decision: | |
10 | Review of percutaneous transluminal angioplasty changes | Monica Harry | Changes have been made to the hierarchy and is ready for review by the EAG on the SNOMED CT Terminology server. The SNOMED tech team will provide access to the project for review. Comments must be sent to Monica Harry (mha@snomed.org) prior to October 31, 2024 for consideration. Discussion: Recognized that many of these procedures may be performed by methods other than fluoroscopy Decision: Request to make a working definition of what is meant by Angioplasty that can be applied to existing and future concepts. Monica Harry will follow up with a revised BN. An online vote will be taken from the EAG to avoid delaying moving forward with this project over the holidays. | |
11 | AOB | EAG | Guillermo Reynoso What is the plan for modeling measurement procedures? Suggested that SI create a new model for measurement procedures. A new project group? Project proposal? What is the priority? Need to align with Observables. Recommended to inactivate the existing attributes and build a new model. There is agreement that there is a need for two hierarchies for multiple member countries, but an approach to make the measurement procedure fit for purpose has not been determined. Also needed is a review of the international and extension drug models. | |
12 | Next meeting | TBD |
16 Comments
James R. Campbell
Item 8; Definition of ANASTOMOSIS: While the proposed definition is technically sound, I think it is not clinically correct. I know of no surgical anastomoses that are constructed between fibers. The structures involved are always tubular or channels, both with a lumen. The purpose of the anastomosis is to connect the lumens for flow of gas or fluids between the two structures.
Jeremy Rogers
The clue is of course in the name:
ana- (again, anew) -stoma- (opening, mouth) -osis (state of)
So if it ain't hollow it ain't an anastomosis. Any other use of the term in the context of the abutting/reconnection of two cut ends of a solid structure (and possible microsurgical suture of same in layers) is a plain and simple catachresis and "you know what I mean" terminological laziness by some of our surgical brethren!
Matt Cordell
Do we get around this by separating the modelling and the naming? For example reserving the |Anastomosis - action| to only be used for structures with a lumen? Everything uses the less specific Repair/Construction action.
And preferred term can be Anastomosis for either (even if semantically inaccurate).
The other thing to consider is that often these actions are either doing a lot of work (inplace of alternate modelling) or unnecessarily specific (this actually applies to much of the qualifier hierarchy). The clue is also in the variety of terms used.
For example: 312407006|Anastomosis of sigmoid colon to anal canal (procedure)|
It's nice and simple to model it like it currently is - two role groups with each with a site, and anastomosis action. (can't post images)
However, could it also be modelled as "Construction of internal stoma between sigmoid colon to anal canal"? (or some more appropriate morphology).
Do these procedures necessarily involve two sites? Are all those modelled with a single site groupers?
Jeremy Rogers
There's always something of a tension with "anastomoses" (and shunts and bypasses) as to whether you model them primarily in terms of the surgical technique used during the procedure (ie in terms of an "anastomosing" method) or in terms of the new anatomical structure that results at its end (ie in terms of an "anastomosis structure" associated morphology).
Whilst modelling the initial construction of an anastomosis using an "anastomosing method" is a superficially intuitive choice, how do you then model subsequent repairs, revisions or reversals of the anastomosis - or leaks and other diseases at the anastomosis site itself - if you don't have the "anastomosis as a morphological structure" to point at in modelling? And if you DO have the anastomosis structure in the ontology separately from the anastomosing method, how do you avoid the simple mistake of postcoordinating their initial construction as "construction of morphology" in the manner you suggest?
My train of logic would be:
1) the anastomosis/shunt/bypass morph structure HAS to exist in order that you can model disorders of one
and therefore, if we are to avoid introducing semantic redundancy into the ontology, the knock-on consequence of this primary ontological necessity is:
(2) the procedures to create them in the first place - and then later to reverse them - must all be modelled fundamentally as the creation or destruction of such anastomotic/bypass/shunt structures, and not as the creation of <some unnamed structure> by means of some fancy (de)anastomosing/bypassing/shunting techniques.
Victor Medina
There are many references to anastomosis between non-tubular structures: Nerve anastomosis, as in https://www.sciencedirect.com/topics/medicine-and-dentistry/nerve-anastomosis, and Tendon anastomosis as in https://pmc.ncbi.nlm.nih.gov/articles/PMC3838333/. In SCT, we have 56438006 |Neuroanastomosis (procedure)|.
Monica Harry
Matt Cordell Jim Case James R. Campbell Feikje Hielkema-Raadsveld John SnyderMonique van Berkum Jeremy Rogers
Dear EAG members,
As discussed at the last meeting Oct. 21st, I am attaching an xls with the Angioplasty inactivations and replacement concepts for your review. The inactivations were actioned after previous agreement by this group. This is intended to be the final review before promotion to ensure that the inactivation reason and replacement values are correct. I need to ask for a quick turnaround in order to promote for Dec.. 1st release. Please respond by EOD Tuesday Oct. 29th. Many thanks, Monica
Apologies, here is the file, omitted in the first message:
Angioplasty inactivations 20240918.xlsx
Apologies all, I omitted the spreadsheet, here it is now:
Feikje Hielkema-Raadsveld
Monica Harry Apologies, I only saw your email today... Do you have a link for me to the working definitions you used for angioplasty and its variants (if there is any difference) of balloon, percutaneous, transluminal and fluoroscopic? Or do you retire and replace them?
Monica Harry
Hi Feikje,
Sorry, you did ask for definitions and I overlooked that... Hope below is helpful. At the top level, we retained this grouper:
446878003 |Transluminal angioplasty of blood vessel (procedure)| defined as:
Definition otherwise, items in BLUE can be specified as per FSN:
We are making a distinction between procedures based on device and imaging modality so for example, where the device is named in the FSN, we define accordingly as in these examples:
Defined with: 410817004 |Dilation repair - action (qualifier value)|; 310362005 |Angioplasty catheter (physical object)| and 59820001 |Blood vessel structure (body structure)|
Defined with:102319006 |Percutaneous transluminal angioplasty balloon, device (physical object)| and 59820001 |Blood vessel structure (body structure)|
Defined with:360168002 |Rotablator (physical object)| and 51114001 |Arterial structure (body structure)|
Although literature suggests balloon catheter is most often used, we did not agree, so unless the FSN states balloon, it is not assumed. If the FSN says balloon etc. the device is then balloon.
We also have a mixup with rotablation that ought to be named Atherectomy with METHOD ABLATION rather than Dilatation - repair but to date in SNOMED they are mostly angioplasty using rotablator.
As for imaging, for those older concepts that did not state imaging explicitly we assume at the time these were originally authored they would have been fluoroscopic. Again if the FSN states other than fluoro, then model with specific imaging modality.
I think I could do more clean up, for example:
431727003 |Fluoroscopic angiography of graft using contrast with insertion of stent (procedure)| or vague concepts eg. 710132004 |Insertion of catheter into artery using fluoroscopic guidance with contrast (procedure)|.
Feikje Hielkema-Raadsveld
Thank you Monica Harry that helps me a lot! One question: those older concepts for which you assume they are meant to be fluoroscopic: does that mean you will change the FSN on those concepts to include 'using fluoroscopic guidance with contrast'?
Feikje Hielkema-Raadsveld
Looking at the concepts being retired, I'm confused about the choice between duplicate and ambiguous. I think I understand why 'angioplasty of abdominal aorta' is retired as ambiguous: it does not specify the guidance used. But 'angioplasty of X using fluoroscopic guidance with contrast' is sometimes retired as duplicate with 'percutaneous transluminal angioplasty of X using fluoroscopic guidance with contrast' (e.g. rows 3 & 5) and sometimes as ambiguous (e.g. rows 4 & 8). What makes these cases different?
In your working definitions, you have transluminal angioplasty as a grouper which then divides into percutaneous transluminal angioplasty & intraoperative transluminal angioplasty.
Angioplasty would then be duplicate with transluminal angioplasty, but those concepts presumably do not exist for many structures and would not be very useful either - who would record that grouper? The most common meaning intended is presumed to be percutaneous transluminal angioplasty using fluoroscopic guidance with contrast, is that right? And so that is the replacement concept we point to.
I would argue that angioplasty is (in SNOMED) ambiguous because it can refer to transluminal angioplasty or to percutaneous transluminal angioplasty using fluoroscopic guidance with contrast, so we can retire those as ambiguous and as replacement concepts we use both those concepts if they exist. If there is no concept for transluminal angioplasty of X, I entirely agree that we do not want to create that only for the sake of having multiple replacement concepts.
On a different note:
is retired as ambiguous, replaced by the grouper transluminal angioplasty. Does peroperative not indicate here that it is not percutaneous but intraoperative? It might be worth replacing this concept with a new grouper for intraoperative transluminal angioplasty.
James R. Campbell
Monica,
I received this via email and found no attachment there nor here in the minutes. Where do I find the spreadsheet?
Jim
Monica Harry
Apologies Jim, I omitted the spreadsheet, here it is now:
Angioplasty inactivations 20240918.xlsx
Monica
Jeremy Rogers
Thanks Monica.
There's obviously a lot of history and discussion leading up to this spreadsheet that I haven't seen and probably would strongly disagree with if I had!
But at this late stage it seems unhelpful to reopen prior debates, so I will mostly keep my counsel...
Having said that, where a code to be inactivated is being badged as "AMIGUOUS" but has only a single explicitly stated POSS_EQUIV_TO association, then it is not "ambiguous" in my book. Half of all the codes being inactivated are in this camp. But to my eyes they all look like perfectly unambiguous grouper codes that could easily be suitable for data retrieval queries: the exact meaning and scope of the query class isn't in any sense in doubt or subject to more than one valid interpretation, However, if many of these codes were to be added to a real patient record as a coded instance then I would agree that it would then be inherently unclear (but not actually "ambiguous") as to exactly what procedures had actually been performed on the patients involved.
If that's the main problem at stake here - of deliberately underspecified grouper codes that are perfectly suitable for data retrieval being used inappropriately by clinicians for the purposes of primary clinical data capture - then the solution being proposed seems to mostly involve retiring the codes that are proving to be too tempting to clinicians, and redirecting them to one (or occasionally more than one) codes of greater semantic and clinical specificity, in which clinically normative but previously only implied surgical methods become explicit in the FSN of the code on the end of the redirect.
If that's what is going on in this piece of work then I understand the fundamental motivation .. but I think I would have strongly opposed the particulars of the approach being pursued.
Too late now though!
Jim Case
Jeremy Rogers
The purpose of the work is as you suspected, i.e. remove vague concepts that might be used by a clinician. It is true that many of the inactivation reasons using ambiguous have only one historical relationship, but that is because we do not want to proactively add concepts for alternative image guidance if it is not yet in current clinical use; whereas we also cannot assume that leaving out the specific guidance methodology implies one type and that is the only one that is now and will ever be used. As for them being unambiguous grouper codes, with the advent of ECL as the primary way to identify specific sets of concepts, what is the need for these groupers, given the chance that they might be (incorrectly) used or selected for clinical records. We are striving for including clinically useful concepts and not including groupers if they are not needed.
Jeremy Rogers
Thanks for confirming the underlying problem, Jim.
Its certainly a very familiar problem; in our code usage data from UK Primary Care, the 20 most commonly recorded coded diagnoses of them all include clinically underspecified terms such as:
35489007 Depressive disorder (disorder) - reactive or endogenous? Isolated or recurrent?
43116000 Eczema (disorder) - acute or chronic? atopic or drug induced? where?
195967001 Asthma (disorder) - atopic, drug-induced, exercise-induced or occupational?
95324001 Skin lesion (disorder) - what kind of lesion and on which bit of skin?
271807003 Eruption of skin (disorder) - what kind of eruption and on which bit of skin?
34014006 Viral disease (disorder) - of what?
...whilst the 30 most commonly recorded surgical procedures include:
45595009 Laparoscopic cholecystectomy (procedure) - with or without intraoperative cholangiography? Robot assisted? Total or subtotal?
80146002 Excision of appendix (procedure) - open or laparoscopic? elective or emergency?
35646002 Excision of lesion of skin (procedure) - what kind of lesion and from which bit of skin??
302396003 Cryotherapy to skin lesion (procedure) - ditto
177860007 Primary repair of inguinal hernia (procedure) - open or endoscopic? with or without synthetic mesh
68265005 Operation on the ear (procedure) - what kind of operation, and on which bit of the ear?
13714004 Arthroscopy (procedure) - of which joint?
But if we're simply trying to prune SNOMED so that the only codes remaining for selection into real patient records by clinicians are those considered to be sufficiently medicolegally clinically specific, then the reason for pruning each insufficiently specific code out would I think more correctly always be "non conformant with editorial principles" and, in most cases, there will be no plausible active substitute code with a directly equivalent semantic meaning (because we inactivated them all).
However, inactivating codes because they're being used inappropriately isn't actually a solution anyway: in very many clinical systems, making a SNOMED code inactive has no effect at all on whether it can or will be selected by clinicians going forward. If anything, code inactivation actually compounds the data quality problem: because inactive codes exist in limbo outside the main reporting taxonomy, they become even harder to report on.
I would have preferred a solution in which all the codes - groupers included - remained exactly where they are in the taxonomy of active codes, and instead one or more refsets were used to enumerate the set of all active (grouper) codes considered to be insufficiently clinically precise for real patient data. System vendors could then use this and other filters in order to guide and constrain SNOMED primary coded data capture rather more than they currently typically do.
Victor Medina
As discussed at last meeting, Oct. 21st. the new definition for ANASTOMOSIS will be: Surgical procedure to create a connection between
channels, tubes, fibers, or other parts of a network. Where the term cross-connection was eliminated.
Alongside with the agreement that we can use proximal and distal anastomosis actions for anastomosis concepts, was also agreed the inactivation of 424208002 |Shunt - action (qualifier value)| and 360021005 |Bypass - action (qualifier value)|.
Additionally, subtypes of 257741005 |Anastomosis - action (qualifier value)| and the 78817002 |Construction of anastomosis (procedure)| hierarchy will be reviewed as part of this project.
The 410614008 |Construction (procedure)| hierarchy will be reviewed for testing of the newly proposed model and classification, where the position of the 129376004 |Construction - action (qualifier value)| will be changed to be a direct subtype of 129284003 |Surgical action (qualifier value)|.
All changes will be tested in a new dedicated project and it will be visible for EAG members for follow up.