About this release
10 March 2022:
- SCT Browser 4.12.0: Release Notes
- This is a scheduled maintenance release for the Public SNOMED CT Browser, with 2 enhancements, and 1 defect fix, aligned to the AP 8.10.0 release.
9 March 2022:
- Authoring Platform 8.10.0: Release Notes
- SCT Browser (TS Browser) 4.12.0: Release Notes
- Reporting Platform 2.2.0: Release Notes
- Release Management Service 1.9.0: Release Notes
- Classification Service 6.2.1: Release Notes
- This is a scheduled maintenance release for the Authoring Platform and related services. This release delivers Frequent Release Implementation (FRI) project Phase 7 enhancements together with AP maintenance updates. AP 8.10.0 has 31 enhancements, and 20 defect fixes. This AP deployment includes the TS Browser, so the SCT Browser 4.12.0 release notes are included here, but these are dated for the 10 March Public SCT Browser release, with 2 enhancements and 1 defect fix. Reporting Platform 2.2.0 has 7 enhancements including 1 new and 5 updated reports, and 2 defect fixes. RMS 1.9.0 delivers 10 enhancements and 8 defect fixes supporting the frequent release process and validation services. Classification Service 6.2.1 delivers 1 defect fix related to frequent release dependencies aligned to the AP 8.10.0 release.
These are scheduled maintenance releases for the Authoring Platform coupled with the SNOMED CT Release Platform (RMS host) and the SCT Browser, all running on the Snowstorm Terminology Server and related services (notably the Classification Service which has an aligned release).
This page presents aggregated statistics of all related changes, including related Release Management Service (RMS) validation rules and reports, Reporting Platform updates, and other AP support services together with the SCT Browser (AP TS Browser). It shows changes by type, functional area, and reporter, to give further insight into the nature and focus of this feature release, to which have been added the proportion of tickets raised by Content Team Authors, Testing Team and Technical Development Team, along with the proportion of Technical tickets related to performance and stability.