SNOMED International Release Management

Page tree

Date of Initial Handover meeting: 11th March 2022

Date of Final Handover meeting: 15th March 2022

Attendees

Handover Status

HANDOVER COMPLETE 

Agenda

 

Items to be discussed

Actions

1

Prerelease Content Management Activities:

  1. Inactivate the root concept synonym referencing previous release, and add synonym to reference current release.
  2. Update copyright date on synonym (January releases only)
  3. Generate + Validate SEP Refsets
  4. Generate + Validate Lateralizable Refset
  5. Content Team to confirm to Release Manager that 4x MRCM refset files are complete and ready to be released (they are then extracted from the termServer during release builds via the termServer Export)


  1. MBR - done https://jira.ihtsdotools.org/browse/INFRA-8380
  2. MBR - not required as only required in January releases...
  3. Process has generated the data - AAT to cross check against report MBR sent (post close of editing report):

    1. https://docs.google.com/spreadsheets/d/1exC9bdvFHx_63_EDj_FADsFWgeRyuyvHXB0B7f153gk/edit#gid=0

  4. Process has generated the data - AAT to cross check against report MBR sent (post close of editing report):

    1. https://docs.google.com/spreadsheets/d/1exC9bdvFHx_63_EDj_FADsFWgeRyuyvHXB0B7f153gk/edit#gid=0

  5. Yong confirmed he will try to follow the deadlines for the monthly releases - 
    1. No MRCM changes for the March 2022 release - as confirmed by MBR
2

Discussion of existing Known Issues from the previous Release

  1. INFRA-8402 / FRI-376 - RefsetDescriptor - RDA confirmed we should just remove them from scope for now, so we’ve raised Dev ticket to fix automated process whilst we continue to generate them manually in the interim...
3

Content Validation 

  1. Instead of usual manual Content validation, we now just need confirmation that all Projects had automated validation run against them, and were clean before promotion.
  2. New Issues identified by the community from the previous Monthly Release.
    1. Decision on whether to fix the issues:
      1. VERY QUICKLY in time for this upcoming release?
      2. In good time for the next monthly release?


  1. Content Release Lead confirms to Release Manager that all Projects had automated validation run against them, and all issues identified were resolved before promotion - MBR confirmed all done 

  2. Note: large number of inactivations for ICD10 maps: assertionText: "All active records in extended map refset are valid.", failureCount: 349,

    1. Donna confirmed large amount of intentional inactivations by Farzaneh - no impact to Rick either
  3. Still have traceability failures: All components in the branch traceability summary must also be in the RF2 export. All components in the RF2 export must also be in the branch traceability summary. confirmed false positives see  INFRA-8515 - Getting issue details... STATUS
  4. False positive failed assertions in daily build RVF report  INFRA-8593 - Getting issue details... STATUS   INFRA-8595 - Getting issue details... STATUS  RESOLVED
4Mapping schedule

Terance confirmed today that we would not be able to get the new automated process up and running for this release cycle - therefore need to confirm that everyone is ready to continue with the old manual process for one more cycle?

Ready for testing but no need to rush this cycle - will be ready for April release...

    1.  First rundeck job will pickup the right date from the Release schedule, and then run the data import

    2. Second rundeck job will be run by Maria (once Mapping tasks are complete), to add 2x new task id's into the job and generate the maps

Donna confirmed she's happy with the schedule, and they're also already up to date with the final content.

Mapping process delivered ICD-0 + ICD10 files to AAT on time this cycle

Did mapping process work well this time??   Yes, process was good

HOWEVER, the counts don't match Donna's manual counts exactly, so we will investigate further:

  • ICD-0 = Manual mapping count = 4 new records, only 3 new records coming through in Delta files
  • ICD-10 = Manual mapping count = 477 new records, 485 new records coming through in Delta files
    • Donna sent report:
    • Compared Delta file changes to report:
      • Delta file showed most differences were due to 47 updated records in the Delta, in addition to that there was only one missing concept:
        • 1196866006
      • Confirmed with Rick that this was a concept that was added to the content (therefore came through to mapping in the drip feed), and was then removed from the content before the monthly release! 
      • Therefore should be missing from the Delta files - just should also be removed from Donna's manual counts (based on the drip feed) - she will work with Rick to get visibility of the Mapping QA report to remove these concepts from her counts
      • (see email trail at 16:24 on 15/2/2022)

Maria confirmed manual process went well again this month

5Brief run through of the known issues already identified by the content team during the QA batch process, to ensure that technical team are aware of them, and can either resolve them in time for the release, or confirm as known issues.

Maria confirmed all tickets complete


6DevOps resource confirmedJoe will be the resource for the March release...
7Versioning and Change Freeze

Plan is to follow the new processes as now defined: 

AAT walked through and agreed new process with DevOps already, so unless there are any further questions/issues??

AAT to sign off PreProduction (unversioned) build before 11:00 on 15th March, and then:

  • Versioning + related issues to be completed and resolved as of  - DONE!
8Stats Report

Reports run via the reporting platform (post close report 14 March 2022)

9Risks
  1. Donna raised the concern that there's still one concept (from the previous cycle) that doesn't resolve correctly in the tool:
  • 1196866006

Rick confirmed this will be resolved by the Finalise mapping process, which will be run later tonight...

AAT to add a note onto the post-Prod Published comms to WCI to request Finalise mapping process well in advance from now on...

2.  Donna confirmed ZERO ICD-0 map changes expected this cycle - AAT to be aware for validation purposes


3.  Donna confirmed 343 inactivations expected in ICD-10 maps this cycle - higher than normal  - AAT to be aware for validation purposes


****** MAPPING ISSUE FOUND LATE (morning of 15th) CAN'T BE FIXED BECAUSE WCI AREN'T AROUND TO RE-EXPORT THE MAPPING TOOL DATA AND IMPORT INTO THE TERMSERVER.  THEREFORE BOTH Mark + Donna CONFIRMED THIS IS NOT A CLINICAL RISK AND CAN THEREFORE BE CARRIED OVER AS A KNOWN ISSUE TO BE FIXED IN THE APRIL RELEASE

  1. AAT to add this into the Release Notes as a Known Issue
  2. Rick Woodto add new check into the Release validation in the Mapping Tool to catch these issues earlier on from now on
10AOB

Chris will kindly create a Slack channel with all of us on it to discuss issues, provide high level updates, etc






  • No labels