Skip to end of metadata
Go to start of metadata

Dear all

SNOMED International are currently considering moving towards more frequent delivery of the SNOMED CT International Release package.

The move towards more frequent releases of SNOMED CT would realise several benefits, including:

  • The potential to be able to get content changes into the terminology in a shorter time frame.
  • The fostering of better interoperability, as a result of entities being able to consume release content that is more aligned with other organisations.
  • The prevention of circular dependencies that occur in longer projects, due to the move towards smaller, more manageable authoring projects.
  • More automated validation services, as a result of the inherent removal of the Alpha and Beta stages in the Release cycle.

The only significant change for most users will be the removal of Delta files from SNOMED CT release packages. They will instead be available via an on-demand service, which will allow the creation of bespoke Delta files, relative to a given previously published release. This will inherently mean that some Delta files may start to contain multiple effectiveTimes.

We would therefore encourage any users who feel like they might have feedback on this proposal to complete the following survey:

If you would like your feedback to be considered in the discussions please complete the survey as soon as possible, and certainly before the 30th April 2019.

Thank you very much in advance for your time,

Kind regards

Andrew Atkinson  |  Release Manager

  • No labels


  1. Hi Andrew,

    This is great news for the SNOMED CT Global community! 

    Although this topic as been discussed since many years, I'm not sure I understand your statement around the delta files changes. I would suggest you explain this better, for instance, what is meant by the "creation of bespoke Delta files..."

    Before diving in one specific scenario, we have many questions from an NRC and an implementation perspective:

    • When is SI planning to implement this change?
    • What will be the frequency? 
    • What will be the SI process for delivery?
    • What should be the NRC process for delivery?
    • What should be the stakeholder process for implementation and maintenance?
    • What would be the update mechanism?

    We would like to be involved in these discussions. Perhaps a communication plan should be developed to inform on the progress of this topic.

    Thank you!

    1. Hi Linda Parisien

      You're absolutely right, once we have an agreement on this proposal we will create formal communication plans and discuss this with a much wider audience - for now whilst we're still in the analysis stage we're looking for more targeted feedback from release experts such as yourself. 

      These questions are all better talked through in person if at all possible - we'll be discussing this in more detail at the conference in various forums.  Would you like to come along to one of the Release AG meetings (I can ensure this agenda item is discussed in whichever of the two meetings that you can attend)?  Or if you're not able to make it to London this time, I could send you the dial in details for the remote attendance of the meeting?

      Thanks very much, look forward to discussing this in more detail with you soon,

      Kind regards


  2. Hi Andrew,

    I will be attending the London meetings. Yes we can certainly discuss further in person. Thank you!