Page tree

Date  20170425

0900-1700 UTC 

GoToMeeting Details

SNOMED Int'l Editorial Advisory group  

SNOMED International - Editorial advisory group conference call  
Tuesday Apr 25, 2017 9:00 AM - 17:00 PM UTC  

Please join my meeting from your computer, tablet or smartphone.  
https://global.gotomeeting.com/join/465895349  

You can also dial in using your phone.  
United States: +1 (224) 501-3318  

Access Code: 465-895-349  

More phone numbers  
Australia: +61 2 8355 1038  
Belgium: +32 28 93 7002  
Canada: +1 (647) 497-9373  
Denmark: +45 32 72 03 69  
Netherlands: +31 707 709 520  
New Zealand: +64 9 913 2226  
Spain: +34 932 75 1230  
Sweden: +46 775 757 471  
United Kingdom: +44 20 3713 5011  

Objectives

  • Obtain consensus on agenda items

Discussion items

ItemDescriptionOwnerNotesAction
1Call to order and role callJCA

Technical issues prevented sound from being added to the Go To Meeting recording

 

2Conflicts of interestJCANone. 
3Approval of minutes from 02/17/2017; 03/30/2017JCA

EAG Agenda and Minutes 2/17/2017

Editorial advisory group conference call 3-30-2017

  • Minutes 20170217 approved
  • Minutes 20190330 approved
4Drug Model and Substance Redesign status updateTMO

Actual and planned changes for the July 2017 International release

Planned changes for the Jan 2018 release

Discussion topics:

  • Potential approaches for resolving “roles”.  It impacts what extensions will be allowed to do.
  • Necessary but not sufficient sets
    • Technical approach needs to be discussed with the editorial group
  • Dose forms and concept model for dose forms – needed for the January release
  • Routes of administration – how it is used in the International release and how it might be expected to be used in extensions

 

5ECE UpdateBGO

Update on ongoing issues with ECE:

  • Complications and sequela including new/approved temporal relationships

  • Revised model for hypersensitivity/allergy/pseudoallergy
  • Intolerance model proposal
  • Complication of pregnancy, childbirth and/or the puerperium (disorder)

Discussion

The primary question on the hypersensitivity model was the benefit of adding a number of primitive concepts to accomplish the organizational structure. It was stated that while suboptimal, it was the "best" solution to accomplish the remodeling with a single model pattern rather than having to have multiple patterns for dispositions and diseases.

The EAG recognized that while this was a substantial improvement in the content representation in spite of the need to add intermediate primitives. Clear guidance on the use of the HAS REALIZATION attribute would be needed to avoid it inconsistent or improper use.

It was suggested that the group may want to investigate the use of multiple sufficient sets to define these top-level concepts that are disjunctive (i.e. allergic condition). This will be discussed at the MAG in more detail.

Clear editorial guidance is needed for the use of disposition-related concepts so HAS DISPOSITION is not used inappropriately

Intolerance

Discussed in detail at the ECE meeting. Proposal to add a new PATHOLOGICAL PROCESS = Intolerance was not agreed to, requiring Intolerance to substance to remain primitive. Consideration of the severity of the intolerance was brought up but not resolved. Referred back to the ECE for final proposed resolution.

Complications and Sequella

  • The EAG agreed on keeping the current primitive concepts "Complication" and "Sequella" due to their widespread common clinical use. It was asked that future attempts to fully define these concepts be considered.
  • Implication is that nearly all combined disorders would be a child of Complication or Sequella or both.
  • Suggested that the FSN for 26634005 - During AND/OR after (attribute) be changed to "During OR after (attribute) - generally approved.

 

  •  Approve final design of hypersensitivity predisposition model
  • Jim Case Request addition of HAS REALIZATION attribute to MRCM for clinical findings hierarchy

 

6

Genomics updateIGR

Plans for working group meeting. Goals and objectives.

Discussion

  • In general the EAG is happy that this area is being developed. While the focus was on clinical genomics, PAM asked why the scoep of SNOMED CT was not all of genomics, i.e. provide the genomics community with an environment to develop a comprehensive genomics model in the context of SNOMED CT.
  • What are the use cases being addressed so we know what is needed to be supported? Adding concepts for everything creates a maintenance burden and may not meet the needs.
  • Are there IP issues? Will be addressed by the genomics group as they recognize that IP and licensing are a remaining obstacle to open access to the needed data.
 
7Proposed policy on acceptance of "Patient-friendly terms" into the International releaseJCA

There have been multiple requests from members to consider the addition of "Patient-friendly vocabulary". A draft position document discussing the pros and cons and a proposed policy for inclusion of such terms in the International release is provided for discussion and input.

SNOMED International Position on the addition of “Patient-friendly terms” (PFT) to the International release of SNOMED CT

  • There are a number of private companies that have made a business of mapping or creating these types of descriptions.
  • A number of specific examples were given as to the difficulty of adding these in a way that is universally understood. The number of of localized terms is too large to be managed in the international release.
  • The notion of "degree of synonymy" did not make it into the RF2 specification and it was proposed that this be revisited.
  • Universal agreement that PFTs do not belong in the international release
  • If people ask about this, will be referred to the Education and Product support team
  • The position statement was simplified and revised and sent to the CEO for approval
 
8Proposed policy: Allowance of Extensions to Modify Core ContentJCA

A discussion document submitted to the Content Managers Advisory Group requested clarification on what national extensions were allowed to do re: modification of core content. The following draft document addresses the primary issues and proposes a more set of policy statements related to what is allowable and not allowable by extensions, which affect core content.

SNOMED International response to "Discussion paper - Allowance of Extensions to Modify Core Content"

Comments from AU:

https://confluence.ihtsdotools.org/download/attachments/40141577/Dion_SNOMED%2BInternational%2Bresponse%2Bto%2B%2522Discussion%2Bpaper%2B-%2BAllowance%2Bof%2BExtensions%2Bto%2BModify%2BCore%2BContent%2522.docx?api=v2

Discussion

  • Primary question is what is meant by the current license. After considerable discussion it was determined that as long as an extension did not modify the actual release files, (i.e. the original RF2 distribution files could be recreated from the extension/edition) then they were not in violation of the license.
  • The perceived use cases were deemed valid
    • Structural errors
    • Semantic errors
    • "Gaps" in the terminology
  • Is changing the stated relationships in the core considered a change of meaning? Only if the relationship is actually deleted from the distribution files. The following statement was agreed to: "If a descendant module overrides the activity of the ancestor module, it is not a change to the ancestor module".
  • It is important for extension to be able to override type 1 errors in the core in order to allow for proper inferences in the extension content that is dependent on the core content.
  • The license explicitly states that recognized errors in the core by extensions must be communicated to SNOMED International. (Section 2.6 "If the Licensee becomes aware of any material error or change or correction needed in the International Release, the Licensee agrees to advise the Licensor promptly of such error, change or correction by following the Licensor’s procedures for change notification that the Licensor prescribes by Regulations and notifies to the Licensee from time to time.")

  • Jim Case Develop a clear statement of interpretation of the license and what an extension is allowed to do. Revise existing document to reflect discussion at the EAG meeting.
9Editorial policy on relationship groupsJCA

Relationship group zero proposal (DKA, YGA)

Normative relationship grouping editorial guidance

Initial proposed grouping guidance has been added to the SNOMED International Editorial Guide for four hierarchies: Clinical findings (disease only), Procedures, Situation with explicit context, and Observable entity. As we begin developing concept models for additional top level hierarchies, there is a need for additional guidance on how to create relationship groups with approved attributes.

Discussion on this topic was not covered as it was in a timing conflict with the MAG.

 
10Clarification on "substantive change"JCA

When trying to apply quality improvement process, there are often a large number of changes applied to existing content. While the current policy refers to changes related to the FSN, there are other types of changes to content that may be construed as substantive. 7.3.1 Changes in the Fully Specified Name

Examples include:

  • Changes to modeling that alters the transitive closure
  • Batch changes to FSN terms to adhere to naming patterns
  • Bulk movement from one top level hierarchy to another (e.g. clinical finding to situation)

SNOMED Int'l needs to develop a more robust policy related to what is a substantive change and what is the notfication/approval process needed to be completed before the change can be released.

 

  • Jim Case Develop additional policy proposal to refer to additional notion of substantive change.
11EAG membership nominationsJCA

EAG members with ending terms of service:

Keith Campbell (may be reappointed)

Paul Amos (may be reappointed)

Proposal for addition of one more member to the EAG (pending approval by the MB)

Apply for an Advisory Group

Refer to skills matrix in SNOMED CT Editorial Advisory Group ToR v2.0.pdf

 
12Future meetingsJCA

TBA