-
Notifications
You must be signed in to change notification settings - Fork 14
Releases : Loading published SNOMED CT content
This page explains the conventions used by RVF to support the notion of previously published SNOMED CT releases.
All test executed by RVF support the notion of a release - a specific timestamped version of a given SNOMED CT edition. For example, the July 2014 release of the International Edition of SNOMED CT is a 'release' within the RVF. Since tests performed within RVF execute validations against 'prospective' and 'current' releases, it is often necessary to load a release into a database as part of validation. Since loading a release takes times and since published releases do not change, a release once loaded can be reused within the RVF. So a release can be registered with the RVF as a 'known' release. A known release is a previously published release of SNOMED CT that can be reused with the RVF. For example, the July 2014 International release can be loaded as a 'known release'.
It is possible to register a known release with RVF by:
- Placing a release zip file in the RVF Data folder
- Importing/creating a database that follows the rvf_int_yyyyMMdd convention
The RVF provides a convenient feature that allows published releases to be uploaded and stored to a designated 'sct data' folder. During startup, the RVF unzips any published release in this folder and loads it into a database as a known release. The following conventions are used by this feature:
| File name | Schema name generated | Comment |
|---|---|---|
| SnomedCT_Release_INT_20140731.zip | rvf_int_20140731 | Created if database named rvf_int_20140731 does not exist |
| SnomedCT_Release_INT_20140731.txt | Not processed | Only zip files are processed |
RVF first verifies if a database following the rvf_int_yyyyMMdd convention exists, before loading a release zip file located in the RVF data folder. So if you would like to force a release to be processed from by the data folder, first drop the corresponding database or use the 'purgeExisting' parameter via the REST API.
RVF follows a convention when creating/loading SNOMED CT data into a database. The database that corresponds to a given release is usually named rvf_int_yyyyMMdd, where yyyyMMdd is the date the release has been published.
| Publication date of known release | Schema name |
|---|---|
| 20140731 | rvf_int_20140731 |
| 20150131 | rvf_int_20150131 |