Terminology Release AG Meeting [October 2015]




Discussion items

1WelcomeRTUAround the table 
2Review of AgendaRTU  
3Review of MinutesRTUFrom Previous Meeting 
4Review of TORRTU  

Conflicts of interest

6Items for discussionAAT/RTU  
7Meeting format/frequencyRTU  

Next meeting




Items for discussion


Review of IHTSDO Release configuration document

  • Proposal to simplify/standardise the statuses of the Releases (section 2)
  • Renaming the International Edition Beta release package as “x….” (section 2)
  • Versioning of Release files (section 3)
  • Proposed move of Release notes from inside the release package to a Confluence page (section 4)
  • Review of authentication for new release distribution system (section 5)

Discussion of a new Release-specific critical incident policy

A process for responding to issues related to a release (edition, terminology product) that would require the recall and redistribution of a release. Scope includes communication content, steps to be taken, stakeholders to be notified… Are all incidents critical?  We also need to agree on what level of service is required (eg) if a critical incident occurs within 1 month of a Production release, what response time is reasonable/expected to

  • Agree what needs to be done, and the urgency level

  • Resolve it and implement a amended Release accordingly

  • Communicate decisions/actions to everyone (plus who this needs to be communicated to)

  • Post-release follow up of release notes or other means of communicating new known issues to the user base.


Module distribution

A recent error with the release of the GP/FP subsets and map from SNOMED CT to ICPC-2 edition has highlighted the following issues with regard to module distribution:

  • segregation of derivative products into distinct modules?
  • if so, do we bundle in dependencies (dependent components), or call out the dependency on the International edition? 
  • what does an initial release contain? Which files are populated, and not populated? 
  • In a final release of a product - how do we remove data from the International Edition? (the last remaining product in the Int. Ed. is the ICD-O map)
  • Inclusion in the release notes of an explanation of how to use the derivative release on top of the International release?
  • How to release subsequent derivative releases?  Is the Delta then relative to the previous derivative release, or the previous International edition?
  • Delta files - no machine readable way to say what they’re relative to - resolve with naming convention?
  • Transitive tree for Module Dependency Refset
4Modularization of the core terminology (known use case: AMT) 

Release reviews

The review process for Releases should be analysed to ensure that we’re targeting the most appropriate users to help with the Technical side of reviews - this is at Tech Preview, Candidate Baseline and Pre-Production stages.


Spanish extension

Decision between "Castellano" and "Espanol" in Spanish extension edition wording

7Value set distribution format 

Release packaging conventions

The structure of the Release packages themselves

9Expressions as a means to pre-coordinated “codes” 
10Review of document "SNOMED CT Identifiers v1 0.pdf" 

Continuous Delivery

Identification of potential issues (for ourselves, and for members/affiliates) inherent with our proposed move to continuous delivery (eg) Release containing multiple effective times, etc

Also requirements for producing roll up releases.


Removal of product(s) from a Release edition

Discussion of the creation of a Process for the removal of a product/subset from an edition - for example, the removal of a subset of the International Edition into it’s own separate package (guidance, etc.)


Member request

Recent Member request - "In connection with the January release Denmark suggested that it could be useful to have the content divided into those groups of changes that IHTSDO describes in chapter 2 of the SNOMED CT International Release - July 2015 Release Notes e.g. 2.2.10 Diagnostic Imaging Procedures and 2.2.11 Convergent Medical Terminologies (CMT) to show the concrete concepts/descriptions that have been added.”