Redesign of the Map Reference Set formats

SNOMED Groups Terminology Release AG
1

Original proposal for redesigning the map reference sets to support maps in either direction:

https://docs.google.com/document/d/14bmRaVQYI7-Kz2EPgv00muGqdO6wRrMycCPCJqp5W2s

We have now successfully migrated MedDRA over to the new Map formats:

We now, therefore, need to start work on standardising this new format across our Product portfolio:

    • International Edition:

      • File naming conventions for Simple + Complex maps may need to change (eg)

        • SIMPLE MAPS:

          • der2_sRefset_SimpleMapSnapshot_INT_20240701.txt

            • NOW WOULD NEED TO BECOME 2x FILES:

              • der2_sRefset_SimpleMapToSNOMEDSnapshot_INT_20240701.txt +

              • der2_sRefset_SNOMEDtoSimpleMapSnapshot_INT_20240701.txt

          • Map content would then need to be split into the relevant files (eg)

            • Content in module 446608001 |SNOMED CT to ICD-O simple map reference set| would be held in:

              • der2_sRefset_SNOMEDtoSimpleMapSnapshot_INT_20240701.txt

            • Content in module 900000000000497000 |CTV3 to SNOMED CT simple map reference set| would be held in:

              • der2_sRefset_SimpleMapToSNOMEDSnapshot_INT_20240701.txt

          • Would the refsetID’s also need to change??

            • (eg) with MedDRA we had to create a new refsetID for MedDRA to SNOMED (1193497006) as the old refsetID (816209002) was not compatible with the new format

            • IF SO, the refsetDescriptor records will also need to be changed in order to describe the new format.

        • EXTENDED MAPS:

          • DO WE NEED TO CHANGE THE RELEASE FILE SPEC IN A SIMILAR WAY THAT WE DID TO THE SIMPLE MAPS (in order to add in the directionality to the format - see above)??

          • OR DO WE SEE A DIMINISHING RETURN ON EXTENDED MAPS LIKE ICD-10 THAT RENDERS THIS REDUNDANT?

          • .

          • Internally, SNOMED International can’t see many (if any) strong use cases for reverse directionality Extended Maps, as our intention is usually to map from SNOMED to external classifications when it comes to Complex maps.

            • However if you can foresee use cases then please let us know now!

            • Even if the use case is a local one (because you would like to develop your own complex/extended maps in the other direction), we can still update the overall spec in order to allow support for your local use cases in the global SNOMED standard…

    • .

    • Derivatives:

      • ORPHANET - Need to align this and plan transition for next year

      • GMDN - already aligned? (is the refset under the correct new refsetID?)

      • EDQM - already aligned? (is the refset under the correct new refsetID?)

      • .

      • FUTURE:

        • HPO Map…

QUESTIONS:

  • How much notice should we be providing for changing the International Edition map files?

  • Comms scope?

  • Any impact to existing systems?

    • (eg)

      • Mapping tools (WCI)

      • SnaptoSnomed

      • Simplex?

      • Browser