Introduction

A discussion paper from the Content Managers Advisory Group, entitled Discussion Paper - Allowance of Extensions to Modify Core Content was submitted to SNOMED International management to resolve issues surrounding the interpretation of the allowable changes national extensions may make to the International release of SNOMED CT.  The discussion paper outlines a number of proposed clarifications to the interpretation of what is allowed and details the requirements for those changes.  This response proposes a set of policy statements that explicitly state what can and cannot be done to content of the International release by national extensions.

While this response is principality focused on the needs of national extensions, the general policies discussed here will apply to all extensions, regardless if they are directly dependent on the International release or another edition.  

Background

The primary concern expressed is the interpretation of Clause 4.1 of the SNOMED CT® AFFILIATE LICENSE AGREEMENT, which states: 

“Subject to clause 2.1.4, the Licensee may not modify any part of the SNOMED CT Core distributed as part of the International Release or as part of a Member’s National Release.”

Clause 2.1.4 states:

 “(The Licensor grants the Licensee, license to) modify the manner of formatting of the copy of the SNOMED CT Core distributed to the Licensee as part of the International Release or as part of a Member’s National Release”

 According to the discussion paper, there are two primary issues associated with this clause:

 "This restriction on modifications has been interpreted generally in two ways. 

1. The RF2 distribution must not be modified, beyond appending additional rows. Overwriting data in the distribution files - such that an extension violates the append only model is not allowed (editor's addition). Additionally, the full history provided by the international release must provided, i.e. extensions may not omit anything;

2. International components must not be modified.
   Overriding the international content through either:

• the addition of new versions for international components within extensions; or

• the addition of relationships to international concepts and changing their DL definition.

Restrictions covered by B have been shown to be impractical and prohibit proper quality terminology authoring."

Proposed actions allowed for National Extensions

The discussion paper proposes seven actions that national extensions may want to perform in the course of their content development and maintenance:

1. Create new concepts.

2. Fully define concepts they create.

3. Classify terminology extensions.

4. State additional IS A relationships against core (international) concepts.

5. Retire (redundant) IS A relationships (not necessarily stated).

6. Add additional defining (non-IS A) relationships to primitive international concepts.

7. Retire content considered "inappropriate" - concepts, descriptions or relationships

The paper then goes into substantial detail justifying the need to perform each of these actions.  A request was forwarded to SNOMED International management for review and clarification of the interpretation of clause 4.1 and acceptance of the allowable proposed actions available to national extension managers.

This document attempts to clarify the feasibility of each of the proposed actions and provides justification for the acceptance or rejection of each, in order to make the interpretation of Clause 4.1 more clear.

Evaluation of proposed allowable actions for national extensions

The initial draft of this policy document was extensively discussed at the Editorial Advisory Group face-to-face meeting in London, 2017. The consensus at the conclusion of this discussion topic was:

• The interpretation by the EAG of section 2.1.4 was that of option A, i.e. "The RF2 distribution [of the International release] must not be modified... Overwriting data in the distribution files - such that an extension violates the append only model is not allowed...the full history [of] ...the international release must provided.
• Conversely, the full content of the original RF2 International release distribution must be extractable from any RF2 distribution of a national edition (combination of International and national content), without the need for any data transformation.
• The use cases for modifications to core international content were recognized as generally valid and recognized as potentially causing classification changes to inferred views of international content in a national release.
  
• All modifications to the International release must be appended to the RF2 files within a Module ID owned by the extension.  Addition of changes in the SNOMED International Module are not allowed.
• Substantive errors in or improvement to content in the International release that are mitigated by content in an extension should be forwarded to SNOMED International in a timely fashion to improve the quality of the International release.
  
  

In light of these conclusions, there are very few changes that an extension may NOT make to the International release provided the following are adhered to:

• These allowances are ONLY applicable to RF2 releases, where a full history of content changes is distributed
• RF1 distributions that are derived from RF2 extensions that involve changes to inferences in the International release are in violation of Clause 4.1 of the affiliate license (source of the changes cannot be tracked, original International release cannot be extracted)
• Classification inferences in an edition that result in differences from the International release must not be represented as SNOMED International content.
• Due to the changes to International classifications caused by modifications by national extensions, a disclaimer notifying users of the differences between the extension release and the International release must accompany the national extension distribution files.
  
  

To address the specific use cases listed above, the following policies are proposed:

Create new concepts

The creation of intermediate concepts necessarily results in changes to the inferred relationships of intenational concepts.  These changes can be of almost any type including: assignment of new parent(s), retirement of inferred or stated parents, inheritance of new/additional defining relationships, removal of inferred relationships by the classifier, etc. There are (at least) 2 ways in which an extension concept can become an "intermediate" concept in an edition:

1. The creation of a new fully defined extension concept as a subtype of an international concept.  The extension concept's definition may result in it being classified as a supertype of an international concept. In this case, the transitive closure of the international edition stays the same, except for the addition of the new inferred |is a| relationships for the extension concept. The defining attribute relationships of the international subtypes stay the same; however, results in a redundant inferred |is a| relationship in the national edition.
   
2. A new extension concept (fully defined or primitive) is created and used as the destination of a stated |is a| relationship from an international concept, meaning that the new extension concept is a supertype of an international concept. An example of this might be the creation of an "A or B" concept, where the relationships "A is a 'A or B'" and "B is a 'A or B'" are stated. In this case, the extension is changing the stated definition of an existing international concept (the subtypes), which is more likely to lead to significant consequences.

Proposed policy

1. SNOMED International recognizes that SNOMED CT is not always comprehensive in its terminological coverage in particular domains and that there exist "gaps" in the hierarchies.  It is proposed that intermediate concepts may be added to extensions as long as direct changes to content within the international module are not made.
2. If the intermediate concepts are identified as being of international value, these should be promoted to the International release.

Fully define concepts they create

Full definition of intermediate concepts will in many cases result in the reassignment of international relationship due to inferences assigned from the classifier (see next section).  Likewise, any subtypes that are inferred under this concept may have their inferred defintions changed (depending on the modeling pattern applied to the extension concept). 

Proposed policy

1. The creation of intermediate fully defined concepts within an extension is allowed, contingent on compliance with the proposed policy for creation of new concepts above.

Classify terminology extensions

The ability to classify extensions is an essential part of leveraging the description logics represented in the International Release for the proper maintenance of extension content.  However, in some cases the results of classification may change the inferred relationships of existing international content.  

Proposed policy

1. In cases where the classification results in an inferred IS A relationship from the core to be changed from the Internationakl distribtution, it is incumbent upon the extension publisher to provide a warning to users that there are differences in inferences from the International distribution.  
   

State additional IS A relationships against core (international) concepts

Missing stated IS A relationships for international content is usually the result of the existence of intermediate primitive concepts that editors are unaware of.  These intermediate primitive concepts are under review, but the volume makes it unlikely that all will be identified and resolved in the very near future.  Identification of these missing stated relationships by national extensions provides an opportunity for incremental improvement of the international terminology.   

Proposed policy

1. Where a needed IS A relationship has been identified, it may be added to the extension, but a request to SNOMED International for addition of this relationship should be submitted as soon as possible.  These will be handled as high priority by the editorial staff. 

Retire (redundant) IS A relationships (not necessarily stated)

Redundant IS A relationship exist in SNOMED CT where variations in modeling style have been used and hierarchically related terms have been assigned as stated relationships. These are considered internal quality errors in the and are being incrementally addressed through the SNOMED CT Internal quality improvement program.  Many of these are already identified (See: https://dailybuild.ihtsdotools.org/qa/  Pattern 1) and are being addressed by SNOMED editors as resources allow.  Redundant relationships that impact extension structure should be reported to SNOMED International for prioritized disposition.  

Proposed policy

1. Inactivation of International release stated IS A relationships is discouraged unless required to meet a particular use case. 
2. Relationships identified as redundant and impacting extension content should be reported to SNOMED Int'l as soon as possible.
   

Add additional defining (non-IS A) relationships to primitive international concepts

The incomplete modeling of international content resulting in a plethora of primitive content is well-recognized.  However, correction of these deficiencies within a national extension can lead to a number of unintended consequences including: 1) the impact on the classification process and the potential change in meaning of descendant concepts (e.g. loss of subtypes) 2) eventual remodeling of the primitive concept in the International release could lead to conflicts between the national edition and the International release.

It is recognized that there may be cases where proper structuring of a national extension requires the full definition of currently primitive international content and that the immediate needs of an extension do not coincide with the timing of International releases. The potential dangers of content divergence in national extensions by allowing definition of international primitive content must be recognized by extension managers prior to undertaking such an effort. It must also be recognized that allowing the definition of international concepts to be changed in an extension makes cross-border, cross-organisation exchange/management/querying of health records more difficult than it already is.

Proposed policy

1. When needed to support national extension requirements, the addition of defining |non- IS A| relationships to existing primitive international content is allowed, providing:
   1. the additions are consistent with the current International Machine readable concept model
   2. the additions are submitted to SNOMED International as soon as possible for inclusion in the International release

Retire content considered "inappropriate" - concepts, descriptions or relationships

It is recognized that there are components within the International release that are erroneous. These is a current issue tracker IHTSDO-724 - Retire inappropriate synonyms, that will address the presence of inappropriate synonyms. The existence of other components deemed inappropriate by a national extension are often context or realm dependent.  The inactivation of international release components within a national extension can result in substantial deviation from the International release and thus an alternative representation of SNOMED international content.  The integrity of SNOMED as an internationally consistent terminology would thus be compromised. 

Proposed policy

1. 1. Inactivation of components (concepts, descriptions, stated relationships) originating in the International release, by a national extension, is allowed.
   2. The identification of issues in the international edition that impact a national extension must be added to a Content Request to escalate its priority for resolution by the SNOMED International editorial team