Editing a Release in Simplex

Overview

In Simplex, the Editing cycle represents the phase in which extension content is created and prepared for release. While Simplex manages the overall lifecycle of an extension, the actual content development and editing activities take place outside of Simplex, using SNOMED International’s open authoring tools.

The Editing cycle brings together content produced by contributors and prepares it for validation and release through Simplex.

---

Content Development Outside Simplex

Simplex does not function as a primary authoring tool. Instead, it acts as an integration and release management platform that consumes content developed in external systems.

During the Editing cycle, content may be created and maintained using the following tools:

• Snap2SNOMED

  Used for creating and maintaining maps. Please see Manage Maps in Simplex

• Refset and Translation Tool

  Used for creating SNOMED CT subsets, including simple reference sets within the extension. Please see Manage Subsets in Simplex

• SNOMED CT Translation Tool

  Used for creating and maintaining translations of SNOMED CT content. Please see Manage Translations in Simplex

• Spreadsheets

  Used for creating new concepts, including simple modelled concepts required for the extension. Please see Manage Extension Concepts in Simplex

These activities are typically carried out by extension contributors including subject matter experts (clinical and terminological), and members of the National Release Center.

Integrating Content into Simplex

The purpose of the Editing cycle in Simplex is to bring externally created content together so that it can be validated and prepared for release.

At the end of the Editing cycle:

• Content must be in a format suitable for import into Simplex

• All required content types must be complete

• Dependencies must be correctly configured. This means that the content of the various derivatives and extension content should depend on the version of International Edition specified as the dependency for this release, please see Dependency Configuration)

• The extension must be ready to move into release validation and review

Once content has been successfully integrated and validated, the Editing cycle is considered complete and the extension can progress to release preparation.