/
Continual Improvement to the Frequent Delivery process

Continual Improvement to the Frequent Delivery process

2022-Sep-24

This is an area where we can consider, discuss and agree new improvements to the various Processes that support the Frequent Delivery of our products.


Potential Improvements:

  • USER DOCUMENTATION
    1. Several end users have contacted Guillermo to request more information on the transition to more frequent delivery (and/or more frequent updates to the dependent content of both extensions and derivatives).
      1. It would be great if we could provide people with a white paper or presentation (both from a Content and Technical perspective) on 
        1. How the transition went
        2. Benefits realised
        3. Lessons learned
        4. Risks
        5. etc
    2. This should be targeted at both the Supplier level + the end users level for max effect
    3. Does the presentation myself and Maria gave cover this?  Or could we add an area on the website??


  • RELEASE NOTES
    1. Can translators please have more detailed release notes - automated to the extent of having EACH component change listed out?
    2. NEW REQUIREMENTS FOR SONJA:
      1. Option for detailed release notes as well as the standard level for all Releases (as per Guillermo's requirement above) - either in the RNMS (preferable) or in the Delta Generation Tool?
      2. It would be great to also link each Component change to the relevant high level change note in the official Release Notes as well (eg)
      3. Release Notes March 2023:
        1. Drugs Changes:
          1. Component 1 changed
        2. Anatomy changes:
          1. Component 1 added
          2. Component 2 removed
          3. Component 3 changed
        3. Quality Initiative:
          1. Component 1 changed
          2. Component 2 inactivated
      4. INFRA-8739 - Getting issue details... STATUS RAISED
        1. RNMS-65 created to track development
      5.  
      6. Explicit annotations in the Release Notes to that each component change in the Delta period is linked to a specific Template
      7. INFRA-8740 - Getting issue details... STATUS RAISED 
        1. MAINT-1958 created to track development
  • Has anyone trialled the Delta File Generation Tool as yet?
    • 1.  Any feedback?
    • YES GABOR HAS TRIED IT AND FED BACK ISSUES TO PETER - PETER IS STILL WORKING ON IMPROVEMENTS SUCH AS THE Snowstorm issue whereby if there are multiple different states for the same component withint the Delta period, snowstorm loses the history of all those changes and just spits out a (random) one line state!  So if a concept has started active, been inactivated and then reactivated in the Delta timeframe, snowstorm might decide to spit out active or inactive as the latest state!  It will also lose those 3 changes and only export one change!
    • UPDATE ON THIS WORK????
    •  

  • VALIDATION advances:

    • OWL testing - anyone worked on this as yet?

    • Template validation - thoughts?

    • Implementation testing feasible? (see Implementation Load Test topic below)

    • Need to identify Modelling areas that need improving - for example where concepts have 2x parents, this is usually an indication of areas that need re-modelling
    • Need automation of the QA system itself - so some quick way to validate RVF + DROOLS Assertions, both old + especially new!
    • Whitelisting - API required?
  •  
  •  


Copyright © 2025, SNOMED International