SNOMED International Release Management

Page tree

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 12 Next »

Date of Initial Handover meeting: 13th May 2022

Date of Final Handover meeting: 17th May 2022

Attendees

Handover Status

INITIAL 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


  1. MBR - changed manually in this task ORPHANET-3042 verified new description is present 13 May.
  2. MBR - not required as only required in January releases...
  3. Process has generated the data -  pre-close of editing report 13 May 2022

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

  4. Process has generated the data - pre-close of editing report 13 May 2022

    1. https://docs.google.com/spreadsheets/d/1pfmCEgvzflB8ZikxKEK5jJZufjDDuOMMYe2h6jZ0cHE/edit#gid=2

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...

  2. Mapping failures checked by Donna and then exceptions listed  INFRA-8874 - Getting issue details... STATUS

  3. INFRA-8675 - Getting issue details... STATUS  May ticket for failed traceability assertions  INFRA-8889 - Getting issue details... STATUS

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. 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-8675 - Getting issue details... STATUS May ticket for failed traceability assertions all false positives  INFRA-8889 - Getting issue details... STATUS
4Mapping schedule

Chris 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 May 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 = ???? new records, only ???? new records coming through in Delta files
  • ICD-10 = Manual mapping count = ???? 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

April 2022:

  • Donna ran new report that Rick created to double check no invalid mappings, all clean now
  • Mark/Donna to complete mapping on Sunday/Monday
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 confirmedChris will be the resource for the April 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 10:00 on 12th April, and then:

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

Reports run via the reporting platform:

9Risks

  1. Timing of the Release validation on 12th in order to allow enough time after sign off to complete re-opening tasks for the AP before 5pm on 12th April as planned
10AOB



  • No labels