Page tree

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »


Time:

0100 - 0430 PST

0900-1230 UTC


Zoom Meeting Details

Hi there, 

Jim Case is inviting you to a scheduled SNOMED International Zoom meeting. 

Topic: SNOMED Editorial Advisory Group Conference Call
Time: May 22, 2023 09:00 Pacific Time (US and Canada)

Join from PC, Mac, Linux, iOS or Android: 
https://snomed.zoom.us/j/83714568251?pwd=cEtNSFhNL0UwWWdmc0ovTG5hYStjQT09
    Password: 983972

    Meeting ID: 837 1456 8251

    Password: 983972
    International numbers available: https://snomed.zoom.us/u/kfbamO8U3

Or Skype for Business (Lync):
    https://snomed.zoom.us/skype/83714568251


Meeting Files:



Meeting minutes:

The call recording is located here.


Objectives

  • Obtain consensus on agenda items

Discussion items

ItemDescriptionOwnerNotesAction
1Call 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


  • Recording of meeting approved by participants.
2

Conflicts of interest and agenda review



3

Inactivation of Navigational concept hierarchy

At the 2023-02-27 EAG conference call, the EAG approved the inactivation of the Navigational concept hierarchy. The EAG members requested a Briefing Note for the Community of Practice outlining the rationale and steps for inactivation.  The briefing note is attached for review.

Update 4/4/2023:

In discussions with the UK, it was discovered that the current use of Navigational concepts are the result of maps from Read version 2 to SNOMED provided to primary care vendors.  The erroneous nature of the maps may be a result of the movement of concepts from their original location in the taxonomy to the Navigational concept hierarchy at variable times in the past.  

The UK will provide SNOMED International with a list of mappings to navigational concepts and their current use cases.  SNOMED will provide replacement concepts for these prior to inactivation of the navigational concept.  Briefing note will be revised to reflect this new information.

Update 2023-05-08:

The following concepts have been identified as high usage concepts by the UK:

CONCEPTID    FSN
394617004    Result (navigational concept)
160237006    History/symptoms (navigational concept)
309157004    Normal laboratory finding (navigational concept)
267368005    Endocrine, nutritional, metabolic and immunity disorders (navigational concept)
243800003    Test categorized by action status (navigational concept)
250541005    Biochemical finding (navigational concept)
309230008    Borderline laboratory finding (navigational concept)
309158009    Laboratory finding abnormal (navigational concept)
118246004    Laboratory test finding (navigational concept)
282465005    Physiological functions and activities (navigational concept)
165347009    Laboratory test result borderline (navigational concept)
309159001    Normal hematology finding (navigational concept)
250207003    Hematology finding (navigational concept)
370121008    Disorder of blood / lymphatics / immune system (navigational concept)
309194008    Hematology finding abnormal (navigational concept)
276437003    Skin, hair and nail finding (navigational concept)
243798005    Procedure categorized by action status (navigational concept)

An updated Briefing note listing these concepts and the proposed replacements is attached to this agenda. This draft has been sent to the UK for their input as they are the member primarily affected by this change.

Discussion:

Decision:  

  • Jim Case to update the BN and distribute to EAG, CMAG and Clinical Leads
4Inspection vs. exploration actionsJim Case 

A query was posed as to the difference between 129433002 |Inspection - action (qualifier value)| and 281615006 |Exploration - action (qualifier value)|, both subtypes of 302199004 |Examination - action (qualifier value)|. The internal consensus was that these are clinically different with the former limited to visual evaluation and the latter implying an active examination.  Various medical dictionary definitions concur with this view:

e.g. Exploration - "An active examination, usually involving endoscopy or a surgical procedure, to ascertain conditions present as an aid in diagnosis. - 
Medical Dictionary for the Health Professions and Nursing © Farlex 2012"

Inspection - "The visual examination of the body using the eyes and a lighted instrument if needed. The sense of smell may also be used. - Gale Encyclopedia of Medicine. Copyright 2008 The Gale Group, Inc. All rights reserved."

This would imply that surgical procedures would more frequently use exploration as the METHOD than inspection; however, this does not appear to be the case

<<387713003 |Surgical procedure|:260686004 |Method| = 129433002 |Inspection - action| = 306

<<387713003 |Surgical procedure|:260686004 |Method| = 281615006 |Exploration - action| = 150

For non-surgical procedures the difference is more extreme

(<<71388002 |Procedure| MINUS <<387713003 |Surgical procedure|):260686004 |Method| = 129433002 |Inspection - action| = 710

(<<71388002 |Procedure| MINUS <<387713003 |Surgical procedure|):260686004 |Method| = 281615006 |Exploration - action| = 220

Many of the non-surgical procedures modeled using inspection are some form of endoscopy.  Given the definitions above and the consensus of the internal content development team, should SI undertake a project replacing Inspection with Exploration for surgical and endoscopic procedures?  It is anticipated that much of this can be done automatically.

Discussion:

Need to review the definition associated with Inspection procedure and Exploration procedure. General consensus is that we do not change the modeling unless there is a clear distinction that can be applied other than what is expressed in the FSN. 

Explorations can be performed without visualization, but Inspections do require visualization.  The current definitions on both need clarification as they imply a supertype/subtype relationship:

122458006 |Exploration procedure (procedure)| -  An observation of the body or a body part done by inspection and/or palpation.

32750006 |Inspection (procedure)| - An exploration using the sense of sight, done with the eyes.

Endoscopy/laparoscopy etc. all use a scope of some sort to visualize the body structures, so should use Inspection as the action. Almost all concepts that use Exploration - action have the word Exploration in the FSN. 

An associated question, based on the current definition in SNOMED of Exploratory procedure, should Palpation -action be a subtype of Exploration - action?  

Update 2023-04-30:


Exploration concepts were derived from the UK OPCS procedure terminology.  The terminology uses "exploration" almost exclusively, with only one procedure using the term "inspection" (K53.1 Inspection of valve of heart). All of their terms have existed in OPCS since at least 1990. 


The AHIMA coding guide states "Inspection is defined as visually and/or manually exploring a body part. Visual exploration may be performed with or without optical instrumentation. Manual exploration may be performed directly or through intervening body layers."  This suggests that AHIMA treats "inspection and "exploration" as synonymous; however, a classification expert from the UK states "I think an exploration in OPCS represents a procedure where there is some sort of entry of an organ/structure to have a look around whether that be with or without incision...I don’t think we can say that the terms ‘inspection’ and ‘exploration’ are synonymous in OPCS-4 and to do so would have the potential for up-coding."


They also state that there are no definitions in OPCS that would help in distinguishing between inspection and exploration.  It is possible that in this scenario, the UK has chosen to use the term "exploration" in favor of the term "inspection" as they state that the one inspection term they have is an anomaly. 


4Severity as a defining attributeJim Case 

The attribute 246112005 |Severity (attribute)| is an approved defining attribute for Clinical findings in the MRCM; however editorial guidance has been rather ill-defined in relation to the use of this attribute due to the subjectivity of assigning a severity to a clinical finding (i.e. "Severity is defined relative to the expected degree of intensity or hazard of the Clinical finding that is being qualified."

The use of the SEVERITY attribute is complicated by the lack of knowledge about the ordinal scale from which the selected severity originated.  For example, the source severity value set may have different sets of values such as: 

• mild / moderate / severe
• minimal / mild / moderate / severe / very severe
• mild / mild to moderate / moderate / moderate to severe / severe / life threatening / fatal

The current editorial guidance for the use of the SEVERITY attribute has a modeling note attached:

Modeling

Generally, 246112005 |Severity (attribute)| is not used to model concepts precoordinated in the International Release, but there are some exceptions. 

A valid exception requires an internationally accepted definition that can be consistently applied and used reliably for international comparison.  Even though a reference may be internationally sourced, its use may not always be uniformly applied by multiple countries. Classifications of severity that represent variation in clinical presentations and enact limitations with age ranges, sex, or pregnancy status, do not apply universally to all patients of all ages, prove problematic, and may not be generally useful. 

The requestor is responsible for obtaining permission for use in SNOMED CT if required by the international body.  

Issue

The issue to be discussed originated at the April 2023 business meeting where it was noticed that some diseases (e.g. Severe asthma) were primitive concepts and thus it is not possible to identify the duplications and subsumptions in postcoordinated expressions that use the severity attribute. 

As an alternative to precoordination in the international release, this attribute can be used as a qualifier in postcoordination.  However, beware that postcoordination of severity results in the same irreproducibility issues as pre-coordination. 

The question is whether the restrictions on the use of SEVERITY in the International release be relaxed, allowing for any concept that explicitly states severity in the FSN have a severity relationship assigned?  

Discussion:


Decision:


5Surgical action

In January, the EAG discussed the definition of "Surgical procedure" and revision of the current MRCM attribute was discussed (2023-01-23 SNOMED Editorial Advisory Group Conference Call).  In light of the fact that we are not able to come up with a standard definition for surgical procedure, we should eliminate the specific action methods under 129284003 |Surgical action (qualifier value)| to the more general 129264002 |Action (qualifier value)| concepts.  As we review the current 129264002 |Action (qualifier value)| hierarchy, we are finding that there are a number of actions that can be applied to either a surgical or non-surgical procedure.  

What we have found is that the definition of a surgical procedure depends primarily on who performs the procedure.  This is problematic as the same procedure may be performed by multiple categories of healthcare professionals. The current definition was broadened from the initial definition in 2021 and now represents an overarching meaning that overlaps with many types of procedures that would not normally be considered surgical (e.g. freezing of warts, reduction of nursemaid elbow). 

Retaining this distinction of surgical and non-surgical procedure will result in the need to create a number of specific surgical actions with unknown benefit in the classification of procedure concepts.  Elimination of the need to specify Surgical procedure as a specific subtype of procedure would obviate the need for the creation of these specific "surgical" actions. 



Abbreviations in FSN for drugs

SNOMED has received a request to add a clinical drug for which the FSN exceeds the limits of characters allowed (255). 

Product containing precisely dexamethasone 1 milligram/1 milliliter and neomycin (as neomycin sulfate) 3500 international unit/1 milliliter and polymyxin B sulfate 6000 international unit/1 milliliter conventional release suspension for eye drops (clinical drug)

Options to address this included:

  • Remove the word "international" from the numerator units 
  • Abbreviate the denominator unit to "ml"

It is anticipated that this is the first of a number of issues related to drug name length.  Whatever decision is made will need to be applied consistently for all future drug names.  Editorial policy will be developed to inform authors as to this exception to FSN terming.

Discussion:


Decision:


6AOBEAG



11Next meetingEAG

TBD based on holiday schedules




















  • No labels