Page tree

Meeting day and time: Monday 26th September 2022, 1000 - 1130 UTC (Local time 1100-1230)

Note: The meeting will be hybrid. 


Meeting Details:  :https://snomed.zoom.us/j/95069855707?pwd=dndhRDlaWEZGOWtCa2tqSmczU291Zz09

Passcode:039823

Information on using Zoom: Starting with ZOOM

Agenda and minutes

ItemDescriptionOwnerNotesAction
1Welcome
  • Attendees list
  • Note: Meeting will be recorded for the purpose of creating minutes. The recording will be deleted once the minutes have been approved. 

5 mins

2Apologies/conflicts of interest
  • Apologies - nil
  • Declarations of Interest:
    • None at meeting.
    • Request to CMAG reps to review and update DOI page by 31st October
5 mins
3Symptom contentMonica Harry 

Potential inactivation: << Finding reported by subject or history provider (finding)

See slide 6 for examples. Issues include broadness, vagueness. 

Similar content - Complaining of concepts previously inactivated. 

Discussion: 

  • Subtypes: Some concepts have.
    • Impact of removing groupers on searching raised.
    • Concepts did come from READ version 2 and would have had subtypes in the past. Changes since that time have resulted in these subtypes moving to other places in the hierarchy.  
  • Symptom vs sign
    • Symptom - a finding reported by the patient, can't be objectively evaluated
    • Sign - a finding that can objectively seen and evaluated by a clinician
  • Normally difference managed in an information model. 
    • Concepts very old - from the time of impoverished information models where the ability to note this wasn't available. 
  • Part of QI work.
  • Impact of this work on the |Finding informer| attribute? Something for the information model?
    • Attribute is infrequently and inconsistently used. 
  • Impact on OHDSI
  • Used by one member in their GP refset. Comments will be added to the confluence page.
  • Usage data from UK available. 

Feedback due: 30th November

Confluence link: Symptom Content - Potential Inactivation

15 mins
4At Risk move Finding to SituationALL

Background provided:

Work stems from a freshdesk ticket asking about the presence of this content in both the finding and situation hierarchies. Most is in the finding hierarchy.  

Discussed at EAG in April: 2022-04-05 SNOMED Editorial Advisory Group Meeting

Objection to move presented by Nursing CRG. Please see documents attached to this page:

  1. Original discussion at EAG in April 2022
  2. Response from Chief Terminologist

Current content includes type of risk e.g. increased, decreased and also concepts without specification of level of risk. The latter are usually understood to mean increased risk.  

Main issues: Ambiguity of at risk of <x> and content is primitive.

Options to manage content presented to CMAG (yet to be presented to EAG). Examples were shown using authoring platform. 

  • Keep in Finding hierarchy with new concept model to support defining of content. Includes using the Has realisation attribute and extending the range of values permitted. 
  • Move to Situation and use model to represent to type of risk. Would require additional concepts as subtypes of 410519009 |At risk context (qualifier value)| 

Ability to express the idea of quantifying risk was raised in discussion. Concrete domains could be used for numbers but not for ranges. 

Question raised on using the information model re degree of risk- how far should SNOMED go in that area? 

Some content is highly used in nursing community. 

EAG to discuss options following input from users. A proposal will sent out to the CMAG, MF Community of Practice prior to changes being made. 

Straw poll on which solution:  10 for findings, 8 for situations.

20 mins
5Review documentsALL
  1. Briefing note: Delivered/ not delivered concepts - plan for inactivation
    • Background: Obstetric content from ICD-9-CM, where discharge note included if patient had delivered or not. Focus on discharge not management. ICD-10 and ICD-11 do not include this content. Difficult to define in SNOMED. 
    • Inactivations:
      • Concepts which include delivered would have two historical associations - Mother delivered (finding) and the base concept representing the disorder.
      • Concepts where delivery had not occurred would have one historical association to the base concept representing the disorder.
    • Approximately 250 concepts. 
    • Looking for feedback or concerns. Please provide prior to 23rd October.
    • Discussion:
      • Question on mapping re ICD-9 retrospective data.  SNOMED International does not provide an ICD-9 mapping. Understand that the issue relates to ICD-9-CM specifically. 
        • For one country, they can manage this in their own extension. 
  2. Terms of reference - review by group due 31st October. 
  3. 2023 work plan -review by group due 31st October
  4. CRS guideline updates - updated promotion process discussed. See slide 10. Template for use between extensions is present in the CRS Customer Guidance Appendix B. 
    • New automated process for managed service customers a way forward.
    • For those with 6 monthly releases the system doesn't account for needing to hold (concept needs to be publish in extension first) before submitting the automated requests. Causes an issue with keeping track of concepts needing promotion and storing of reference material/re-finding reference material to support request to international. Issue has been raised with Managed Service by two countries. One suggestion raised by Terrence from Managed Service was the creation of a draft CRS. Elaine Wooler advised she hasn't found an issue with that.
20 mins
6Release Notes DiscussionMonica Harry 
  • Discussion on what is being provided e.g. what is useful, how much is too much etc.
  • Comments from meeting:
    • From SNOMED:
      • Release notes can now be created in the authoring platform.
      • Information on changes not just in release notes. Briefing notes, early visibility, advisory groups e.g. CMAG, EAG also used. 
      • Considering having stock phrases for use by Content Team in development of the release notes. Looking for thoughts from CMAG on that.
    • Group:
      • Move to monthly means release notes are scattered across releases. Need to be available by view by domain/topic so users can see what has been done over the last <x> months. To be raised with Tech Team Monica Harry 
      • Improved search functionality for the document, like what is available in the Editorial Guide.
  • Please email Monica Harry  with any further comments. 
10 mins
7Any other businessALL
  • Malignancy
  • No future meetings scheduled at this point in time. 
    • Will look at the potential to have a meeting at the April business meetings, if required.

8



Actions: 

DateRequested actionRequester(s)Response required by:

 

Please review the September meeting minutes and advise of any changes required.  

Note: Only CMAG members attending the meeting are listed in the response column.

Previous Meetings

TitleCreatorModified
No content found.


2 Comments

  1. For those interested in the at risk issue, please see the EAG discussion that followed:2022-09-26 SNOMED Editorial Advisory Group Meeting

  2. No feedback received. Action item to review minutes closed. Page updated to note minutes no longer draft.