# Proposal to remove the "ManagedService" tag from the package naming convention

**URL:** <https://forums.snomed.org/t/proposal-to-remove-the-managedservice-tag-from-the-package-naming-convention/362>\
**Category:** Terminology Release AG\
**Created:** [September 22, 2025, 7:14pm UTC](https://forums.snomed.org/t/proposal-to-remove-the-managedservice-tag-from-the-package-naming-convention/362 "2025-09-22T19:14:11Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![aatkinson](https://avatars.discourse-cdn.com/v4/letter/a/5daacb/32.png) [@aatkinson](https://forums.snomed.org/u/aatkinson)\
**Post date:** [September 22, 2025, 7:14pm UTC](https://forums.snomed.org/t/proposal-to-remove-the-managedservice-tag-from-the-package-naming-convention/362/1 "2025-09-22T19:14:11Z")

</div>

The proposal would be to drop “_ManagedService_” from the package naming convention for all Managed Service products published by SNOMED CT.

The rationale:

- This OPTIONAL Element started out being useful for members to distinguish between their old packages from other systems, and their new Managed Service packages. However, it’s differentiating between Managed Service and non Managed Service Extensions, which should in theory be no different to each other as we want to foster interoperability within the community.

- This implies the Product is tied to the tooling used, when we would like all Extension in the community to be standardised as far as possible.

- We would update the “Product” element to state that “ManagedService” is no longer an acceptable specialisation of this element

- Perhaps we could provide better guidance around what Product element should be?

So for example, an Australian MS release would no longer be called:

- SnomedCT\_ManagedServiceAU\_PRODUCTION\_AU1000036\_20241231T120000Z.zip

Instead, we would call it:

- SnomedCT\_ AU32506021000036107Edition\_PRODUCTION\_20241231T120000Z.zip