through
Description | Owner | Notes | Action | |
---|---|---|---|---|
1 | Welcome | RTU | Around the table | |
2 | Review of Agenda | RTU | ||
3 | Review of Minutes | RTU | From Previous Meeting | |
4 | Review of TOR | RTU | ||
5 | Conflicts of interest | RTU | ||
6 | Items for discussion | AAT/RTU | ||
7 | Meeting format/frequency | RTU | ||
8 | AOB | RTU | ||
9 | Next meeting | RTU |
No | Item | Action(s) |
---|---|---|
1 | Review of IHTSDO Release configuration document
| |
2 | Discussion of a new Release-specific critical incident policy A process for responding to issues related to a release (edition, terminology product) that would require the recall and redistribution of a release. Scope includes communication content, steps to be taken, stakeholders to be notified… Are all incidents critical? We also need to agree on what level of service is required (eg) if a critical incident occurs within 1 month of a Production release, what response time is reasonable/expected to
| |
3 | Module distribution A recent error with the release of the GP/FP subsets and map from SNOMED CT to ICPC-2 edition has highlighted the following issues with regard to module distribution:
| |
4 | Modularization of the core terminology (known use case: AMT) | |
5 | Release reviews The review process for Releases should be analysed to ensure that we’re targeting the most appropriate users to help with the Technical side of reviews - this is at Tech Preview, Candidate Baseline and Pre-Production stages. | |
6 | Spanish extension Decision between "Castellano" and "Espanol" in Spanish extension edition wording | |
7 | Value set distribution format | |
8 | Release packaging conventions The structure of the Release packages themselves | |
9 | Expressions as a means to pre-coordinated “codes” | |
10 | Review of document "SNOMED CT Identifiers v1 0.pdf" | |
11 | Continuous Delivery Identification of potential issues (for ourselves, and for members/affiliates) inherent with our proposed move to continuous delivery (eg) Release containing multiple effective times, etc Also requirements for producing roll up releases. | |
12 | Removal of product(s) from a Release edition Discussion of the creation of a Process for the removal of a product/subset from an edition - for example, the removal of a subset of the International Edition into it’s own separate package (guidance, etc.) | |
13 | Member request Recent Member request - "In connection with the January release Denmark suggested that it could be useful to have the content divided into those groups of changes that IHTSDO describes in chapter 2 of the SNOMED CT International Release - July 2015 Release Notes e.g. 2.2.10 Diagnostic Imaging Procedures and 2.2.11 Convergent Medical Terminologies (CMT) to show the concrete concepts/descriptions that have been added.” |