Naming Conventions for Refsets

Hi all

We're considering a minor change to the naming conventions of refsets in some extensions, to allow for more flexibility with changing the names/descriptions of the refsets. This would start with a trial for the New Zealand extension, and potentially also the Estonian and Swedish extensions.

Currently the naming convention includes a human readable description in the filename, explaining roughly what the refset is. However, not only are these now frequently subject to change (which causes problems with both maintenance and consumption of the files), but also many of them are becoming far too long to be fit for purpose.

The Release File Spec (https://snomed.atlassian.net/wiki/display/DOCRELFMT/3.3.2+Release+File+Naming+Convention) states that this is an "optional" summary of the usage of the file, and so isn't a requirement.

The proposal would be to replace the description with the RefsetID instead - thus

a) removing all of the problems (described above) that long descriptions entail, plus
b) still retaining a link through to the Refset (and to the description if users simply plug it into the browser) for those wanting to know what the file contains before opening it.

We have identified a few potential minor drawbacks:

a) the fact that the naming convention would differ from the other extensions, and also to files within the same NZ extension (such as their Lang refset files, etc) leaves room for confusion for users +

b) users might have already hard coded import routines +

c) If the file contains MULTIPLE refset of the same RefsetType (but different RefsetID's), then which refsetID do we use in the name of the file?

d) Will we do this for Map files too? (as they're technically just a type of Refset) 

• If so, then:
  
  

  • Same issue as c) above - For example, the SimpleMap refset file in the INT Edition contains multiple Maps (ICD-0 + CTV-3)

  • We may need to consider splitting the INT Map files into 2x separate files:

    • In which case would we need to consult with the community for such as a change?

    • Check with Implementation Team regarding any potential impact to the Simplex rollout if we DON'T change the Map file naming conventions now?

However, the benefits still appear to significantly outweigh the potential issues.

The plan would be to make the changes in the NZ (and potentially other) extensions in the Q4 cycle of 2024, and therefore we would need to communicate this out several months in advance in order to provide sufficient notice for users.

Therefore, if you can see any other potential problems, or have a strong opinion either way, please can you let us know ASAP?

Thanks very much!
Andrew