Release Validation
Overview
Validation is a key step in the Editing Cycle in Simplex. Its purpose is to ensure that all content incorporated into the extension forms a technically valid SNOMED CT Edition package before release preparation can begin.
Simplex runs the full set of SNOMED CT validations provided by SNOMED International. These validations are applied after content from multiple external authoring tools has been compiled into a release structure within Simplex.
Validation helps identify issues early, ensures consistency across content types, and protects the quality of the final release.
Please refer to the following page of the Extensions Practical Guide for general advice regarding the review and validation of an extension: Review and Validation
Video
Running Validation
Validation is initiated directly from the Editing stage.
To run validation:
Navigate to Manage Edition.
In the Editing stage, locate the Validation box.
Click Run validation.
Once started, Simplex executes the full validation suite against the current state of the compiled extension content.
The Editing cycle cannot progress until validation has completed and all blocking issues have been resolved.
What is Validated?
Simplex applies the standard SNOMED CT validation rules, also applied for the International Edition of SNOMED CT: This includes checks that:
Assert referential integrity between components (for example, ensuring references point to valid concepts)
Validate terms and descriptions, including:
Detection of duplicate terms within a hierarchy
Identification of invalid characters or formatting issues
Ensure consistency and correctness across release files
Some validation rules also assert Machine Readable Concept Model (MRCM) constraints. While Simplex does not support stated modelling directly, these rules are still be included as part of the standard validation set and applied where relevant.
Validation Results and Issue Types
Once validation completes, the results are displayed in the right-hand panel of the screen.
Validation issues are categorised as:
Errors
Issues that prevent the release from progressing. All errors must be fixed before release preparation can be completed.
Warnings
Issues that do not necessarily block the release but should be addressed to improve content quality.
A summary count of errors and warnings is shown at the top of the results panel.
Understanding Validation Results
The validation results panel provides a detailed, actionable view of identified issues.
For each issue, Simplex displays:
The component identifier (for example, a Concept ID)
The assertion text, which is a human-readable explanation of the issue
Links that allow the user to explore the affected component in context
Users can click on component IDs to open the Simplex Browser, making it easier to understand where and why the issue occurs.
A help link titled “How to fix these errors and warnings?” is available to provide additional guidance on interpreting and resolving validation findings.
Fixing Validation Issues
Simplex acts as a validation and coordination platform; it does not directly edit content.
All validation issues must be fixed in the original authoring tool where the content was created, for example:
Subset issues are fixed in the Refset and Translation Tool Editor
Mapping issues are fixed in Snap2SNOMED
Translation issues are fixed in the SNOMED CT Translation Tool
Concept or spreadsheet-based content is corrected at source
Simplex clearly identifies which components are affected, helping contributors locate and correct issues efficiently.
Re-running Validation After Fixes
After issues have been fixed in the source tools:
Updated content must be re-imported into Simplex.
Validation must be run again from the Editing stage.
This cycle continues until all errors are resolved and the content meets the required quality threshold.
Downloading and Sharing Validation Results
Validation results can be downloaded directly from the results panel.
Downloaded reports can be shared with:
Content editors
Subject matter experts
External contributors
This supports collaborative issue resolution and ensures that all stakeholders have clear visibility of required fixes.
Completion of the Validation Step
The Validation step in the Editing Cycle is considered complete when:
Validation has run successfully
All errors have been resolved
Any remaining warnings have been reviewed and addressed where appropriate.
Once validation is complete, the extension is ready to progress to release preparation.
Last updated