SNOMED International Mapping Tool

Space shortcuts

Child pages
  • Mapping Tool Release Process

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Overview

Documents the release process details.  There is an admin page already that indicates how to run the mojo.  See Release Processing Tool for more information.

Assumptions

  • Source terminology is SNOMED CT
  • Release is in RF2 delta format
  • QA of overall release is done by an external system (though project-specific validation rules are processed here)
  • That editing was done in conjunction with a "drip feed" system that brought emerging content into the system as it was being developed, so it could be mapped.
  • That the mapping files are part of the source terminology release

Details

The mapping tool supports a release process that takes into account end-of-editing cycle activities, some quality assurance, production of data files, and upgrading terminology versions when the time comes.  The release processing is specifically tailored to the needs of IHTSDO and maintenance of the RF2 complex and extended map refsets that are part of the SNOMED CT distribution.

 TODO: flowchart

The steps are:

  • Finish all editing - assumes drip feed has been processing along the way
  • "Begin" a release
    • Verify all "in scope" concepts are mapped
    • Validate all existing map records against current rules
    • Remove map records for concepts that are retired, deleted, or out of scope. 
  • Generate release files
    • Create an RF2 delta file
    • Create human readable file
    • Create module dependency file (if needed)
  • "Finish" a release
    • Create complex map refset entries for all delta entries (replacing any there with the same identifiers)
    • Mark all map records for the project that are READY_FOR_PUBLICATION as PUBLISHED.
  • Upgrade to latest version - there are two forms of this and it assumes that the version of the map and the "source terminology" are coordinated.
    • Load a definitive delta release and update the version of all terminology components to latest version.
    • Remove and reload an entire definitive snapshot release.

Creating Custom Release Processing

If the process above is not needed or desired, alternative release processing can be built as a custom development task.  Things to consider are:

  • The release format
  • Whether the release is part of the source/target terminologies of the map
  • Whether the mapping versioning itself is coordinated with the source/target terminology versioning
  • Whether map records were built completely from scratch or were generated from terminology data
  • Whether a "delta" release is needed - e.g. a release that compares to the previous release and publishes only the changes.

These things are very project specific and are not the same for all projects.

Custom release processing can be implemented via an outside package, or in the mapping-custom project (see Custom Release Process).

  • n/a

 

  • No labels