SNOMED CT Content Release and Validation Service

Summary

The Service provides Members with the ability to request releases of their national extension, including QA and packaging, twice a year as standard or up to twelve times per year for an additional cost.

Description

This Service allows the Member the ability to request releases of a single Release Package, which can comprise of one or more Products within their national extension or edition, including the quality assurance (QA) of the Release Package, at an agreed frequency not exceeding once per calendar month. At the Service Provider's discretion, country specific QA rules may be used in addition to the standard SNOMED International QA rules during the release process.

Production of more than one Release Package can be requested as Additional Services, which will incur additional Service Charges equivalent to the current Annual Fee for each Release Package.

All national extensions or editions can be published on the SNOMED International Members Licensing and Distribution Service (MLDS) and/or the SNOMED International browser as part of this service, if requested.

Detailed Scope

Within Scope
Service Element	Notes
Production of national extension content published as either an Edition and/or Extension Only Release Package	Service includes one (1) Release Package per Member, however additional Release Packages are available for an additional fee
Production of a national extension or edition Release Package up to two times per calendar year	More frequent releases, up to once per calendar month are available as an additional service with an applicable fee, the “Frequent Release Fee”.
Availability of a “Daily Build” for download by the Member that contains a release of all content currently promoted to the extension Code System that is produced and validated automatically every 24 hours	The Daily Build files are made available on a reasonable endeavours basis and should not relied on or used in production systems Use of daily build is responsibility of NRC, it contains un-versioned content that is subject to change and should never be used in production healthcare systems
A validation function which allows various rules to be run as content is saved within the Authoring Platform. These rules are also triggered and checked during the release process
A Release Validation Framework (RVF) function which runs a pre-defined set of QA checks used to produce the International Edition.	The rules will be adapted to meet basic extension validation needs (e.g., languages and modules). Bespoke customisation for a single Member's specific, non-standard use case is not included
A Machine-Readable Concept Model (MRCM) validation function which ensures that the modelling of content in the Authoring Platform complies with the strict editorial rules for SNOMED CT
Upload of extension or edition for distribution via the Members Licensing and Distribution Service (MLDS) if required
Upload of extension or edition to the SNOMED CT Public Browser if required
Additional post packaging validation before release to allow intervention by the Member if required
Inclusion of Simple Reference Sets in a national extension or Edition authored via the Reference Set Management Service (RT2)	A maximum of one hundred and fifty (150) simple type reference sets are included within scope. Additional refsets are available as an additional service with the applicable fee attached.
Inclusion of externally maintained content provided they have been submitted in valid RF2 format before the agreed Authoring Freeze dates	QA or validation of external content by SNOMED International is not included and any external content MUST be quality assured and validated by the NRC before submission. Delays in submission of content or delays caused by issues related to inclusion of such external content are not the responsibility of the Service Provider A maximum of ten (10) externally maintained files are included within scope. Additional files are allowed with the applicable fee attached.
Inclusion of Simple Maps in a national extension or Editon provided they have been imported via RF2 within the release cycle	QA or validation of external content by SNOMED International is not included and MUST be quality assured and validated by the NRC before submission. A maximum of ten (10) simple maps are included within scope. Additional maps are allowed with the applicable fee attached. Limited to one update per release cycle
Preparation of standardised release notes, published in a shared online documentation platform in a format agreed by the Service Provider.

Out of Scope
Service Element	Notes
Extended or Complex Maps and Reference Sets
QA or validation of any externally authored or maintained content that has not been created or edited within the agreed SNOMED Tooling
Externally maintained content or components not specifically included in scope or previously agreed with the Service Provider

Within Scope
Service Element	Notes
Production of national extension content published as either an Edition and/or Extension Only Release Package	Service includes one (1) Release Package per Member, however additional Release Packages are available for an additional fee
Production of a national extension or edition Release Package up to two times per calendar year	More frequent releases, up to once per calendar month are available as an additional service with an applicable fee, the “Frequent Release Fee”.
Availability of a “Daily Build” for download by the Member that contains a release of all content currently promoted to the extension Code System that is produced and validated automatically every 24 hours	The Daily Build files are made available on a reasonable endeavours basis and should not relied on or used in production systems Use of daily build is responsibility of NRC, it contains un-versioned content that is subject to change and should never be used in production healthcare systems
A validation function which allows various rules to be run as content is saved within the Authoring Platform. These rules are also triggered and checked during the release process
A Release Validation Framework (RVF) function which runs a pre-defined set of QA checks used to produce the International Edition.	The rules will be adapted to meet basic extension validation needs (e.g., languages and modules). Bespoke customisation for a single Member's specific, non-standard use case is not included
A Machine-Readable Concept Model (MRCM) validation function which ensures that the modelling of content in the Authoring Platform complies with the strict editorial rules for SNOMED CT
Upload of extension or edition for distribution via the Members Licensing and Distribution Service (MLDS) if required
Upload of extension or edition to the SNOMED CT Public Browser if required
Additional post packaging validation before release to allow intervention by the Member if required
Inclusion of Simple Reference Sets in a national extension or Edition authored via the Reference Set Management Service (RT2)	A maximum of one hundred and fifty (150) simple type reference sets are included within scope. Additional refsets are available as an additional service with the applicable fee attached.
Inclusion of externally maintained content provided they have been submitted in valid RF2 format before the agreed Authoring Freeze dates	QA or validation of external content by SNOMED International is not included and any external content MUST be quality assured and validated by the NRC before submission. Delays in submission of content or delays caused by issues related to inclusion of such external content are not the responsibility of the Service Provider A maximum of ten (10) externally maintained files are included within scope. Additional files are allowed with the applicable fee attached.
Inclusion of Simple Maps in a national extension or Editon provided they have been imported via RF2 within the release cycle	QA or validation of external content by SNOMED International is not included and MUST be quality assured and validated by the NRC before submission. A maximum of ten (10) simple maps are included within scope. Additional maps are allowed with the applicable fee attached. Limited to one update per release cycle
Preparation of standardised release notes, published in a shared online documentation platform in a format agreed by the Service Provider.

Out of Scope
Service Element	Notes
Extended or Complex Maps and Reference Sets
QA or validation of any externally authored or maintained content that has not been created or edited within the agreed SNOMED Tooling
Externally maintained content or components not specifically included in scope or previously agreed with the Service Provider