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

SNOMED Groups Terminology Release AG
1

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?

    • For example, it could be:
      • [countryCode][namespace]
      • (eg)
        • “NZ1000210” ?
      • Or, rather than use the arbitrary namespace (what if countries have more than 1 namespace for example?!), it might be better to use the moduleID as used in a FHIR version URI?
        • [countryCode][moduelID]
          • (eg)
            • “NZ21000210109”
    • We could then also consider removing the (then redundant) 4th element. Again, this would bring the naming conventions back in line with the spec: Release Package Naming Conventions | SNOMED International Documents

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
1 Like