Items to be discussed
Prerelease Content Management Activities:
Discussion of existing Known Issues from the previous Release
3. Association Records not transferring through to the RF2 files as expected https://jira.ihtsdotools.org/browse/ISRS-1271
4. Ref set description changes July 2022 release:
733900009 |SNOMED CT to Unified Code for Units of Measure simple map reference set (foundation metadata concept)|
741814003 |SNOMED CT to Unified Code for Units of Measure simple map reference set module (core metadata concept)|
735233007 |European Directorate for the Quality of Medicines & HealthCare simple map reference set module (core metadata concept)|
762959004 |European Directorate for the Quality of Medicines & HealthCare to SNOMED CT simple map reference set (foundation metadata concept)|
741068007 |SNOMED CT to European Directorate for the Quality of Medicines & HealthCare simple map reference set (foundation metadata concept)|
5. For information, large number of inactivations for ICD-10 maps
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:
Maria confirmed manual process went well again this month
|5||Brief 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.|
|6||DevOps resource confirmed||Chris will be the resource for the July release... (though Joe will cover last few days of cycle whilst Chris is on leave)|
|7||Versioning 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 1012:00 on 21st June19th July, and then:
Reports run via the reporting platform: