Ongoing Technology Roadmap - an update as to what has happened and what will be happening in 2026
The SNOMED CT Identifier race - promotion of content to ensure a local identifier is used instead of another extension’s identifier
Community content use/distribution - how to wrap an external extension into a national edition (LOINC being the obvious first use case) covering packaging and module dependencies
Collaborative authoring proposals walkthrough - discussion on the presentations given in Oslo
Metadata for language refsets, maps, URIs, and around
If you have any other topics for discussion, please suggest them below.
It would be very useful to have a pragmatic discussion on negative deltas, RF2 history corrections (or removal of wrong entries to a separate resource) to avoid having some mistakes forever, or being forced to reboot history. Even if we don’t get consensus to establish direction, discarding dead ends would be useful as we will have to take action soon. I understand the deprecation policy work is something to consider, but our main use case is the correction or removal of wrong states that could not be resolved by other means (e.g. some extension new states on promotions already published on the IE)
And the ability to version by component rather than implementations, assuming that all effectiveTimes in a release match the release version, is necessary to enable more frequent or service-based continuous delivery. At least provide advance notification, since it is not forbidden but it certainly migth break some implementations or import routines.