PDF: Force Page Break

1 Introduction

2 Background

2.1 Scope

The purpose...

2.2 Use cases:

PDF: Force Page Break

3 Motivation

PDF: Force Page Break

4 Content

PDF: Force Page Break

5 Design

5.1 Version

The dependent version of SNOMED CT is the January 2017 International Edition release.

5.2 Ownership

5.3 Frequency

The Production version of the SNOMED CT® Starter Set Translation package will be published after the July 2017 International Edition release of SNOMED CT, based on the Alpha and Beta feedback content changes. Subsequently it will be maintained in line with each release of SNOMED CT International Edition.

PDF: Force Page Break

6 Implementation

PDF: Force Page Break

7 Obtaining the Release

The SNOMED CT® Starter Set Translation package is available from the IHTSDO and is maintained and updated in line with the SNOMED CT International release which is currently 6 monthly.

Access within IHTSDO member countries is provided by the Member National Release Centre in each country, via the relevant Member page. Affiliates of IHTSDO in non-member countries can access the refset through their Member Licensing and Distribution SERVICE (MLDS) account. Please contact info@ihtsdo.org for more information if required.

PDF: Force Page Break

8 Feedback

PDF: Force Page Break

9 Technical Notes

RF2 package format

The RF2 package convention dictates that it contains all relevant files, regardless of whether or not there is content to be included in each particular release.  Therefore, the package contains a mixture of files which contain both header rows and content data, and also files that are intentionally left blank (including only a header record).  The reason that these files are not removed from the package is to draw a clear distinction between:

1. ...files that have been deprecated (and therefore removed from the package completely), due to the content no longer being relevant to RF2 in this or future releases, and 
2. ...files that just happen to contain no data in this particular release (and are therefore included in the package but left blank, with only a header record), but are still relevant to RF2, and could therefore potentially contain data in future releases.

This allows users to easily distinguish between files that have purposefully been removed or not, as otherwise if files in option 2 above were left out of the package it could be interpreted as an error, rather than an intentional lack of content in that release.