This is not yet formalised, but is incoming:
-
-
v3.1 is Outdated with limited scope and therefore limited use cases
- There is therefore a clear benefit to Members for deprecating v3.1, as it presents a potential Clinical safety risk.
-
v3.2 is saturated and we would very quickly get back to the same point as we’re at with v3.1
-
v4.0 might be feasible, but no solid use cases identified so far within the community
-
Given the lack of feedback from the consultations (2022 + 2024) on whether anyone is still using v3.1 , this is considered to be a low Impact deprecation
-
ANY FEEDBACK ON THIS?? ANY KNOWN USE CASES AROUND THE ROOM??
-
-
.
-
Provisional thinking is to therefore deprecate with no replacement, until strong business cases are put forward by members.
- We don’t want to plough resources into constructing and publishing a new product, if it bring no benefit to members - so we need visibility on whether or not this is the case?
-
Provisional timelines would be to target:
-
January 2026 for inactivation in the International Edition.
-
January 2028 for full deprecation from the International Edition.
-
-
.
-
Formal deprecation proposal to follow, but any initial feedback?
-