A set of component versions and reference set member versions defined by characteristics of their effectiveTimes "Reference term: effectiveTime (field)").
Versioned views and release types are closely related. A release type is a physical representation of a particular versioned view.
Some versioned views are not instantiated as release types but all valid versioned views of a SNOMED CT edition can be generated from a full release of that edition.
A delta view is a view of SNOMED CT that contains only rows that represent changes to components and reference set members since a specified date or between two specified dates in the past.
A full view is a view of SNOMED CT that includes all versions of all components and reference set members in a full release.
A snapshot view is a view of SNOMED CT that includes the most recent version of all components and reference set members at a specified point in time.
View
This is an abbreviation for SNOMED CT versioned edition.
A SNOMED CT edition that is published on a specific date.
A new version of the International Edition of SNOMED CT is released twice a year (in January and July).
National extensions generally follow this cycle, however it is often with a three-month delay. Some extensions (notably those including medication-related concepts) are released more frequently.
The International Edition, 20180131 (dated January 31, 2018).
The US National Edition, 20180501.
SNOMED CT version
Version
Versioned edition
A uniquely identifiable set of valid concept representations, where any concept representation can be tested to determine whether or not it is a member of the value set.
This definition is used in HL7 Vocabulary Committee documents and FHIR specifications.
The role of a value set is to constrain the permissible content for a particular use (e.g. data entry into a particular field).
In SNOMED CT a concept representation may be a concept identifier or a SNOMED CT expression.
A reference set can be used to represent a value set of SNOMED CT concepts each of which is represented by a concept identifier in the referencedComponentId field.
This is an abbreviation for versioned view.
A set of component versions and reference set member versions defined by characteristics of their effectiveTimes "Reference term: effectiveTime (field)").
Versioned views and release types are closely related. A release type is a physical representation of a particular versioned view.
Some versioned views are not instantiated as release types but all valid versioned views of a SNOMED CT edition can be generated from a full release of that edition.
A delta view is a view of SNOMED CT that contains only rows that represent changes to components and reference set members since a specified date or between two specified dates in the past.
A full view is a view of SNOMED CT that includes all versions of all components and reference set members in a full release.
A snapshot view is a view of SNOMED CT that includes the most recent version of all components and reference set members at a specified point in time.
View
A SNOMED CT module as published on a specified date.
Versions of the module have no module dependencies.
All other versioned modules declare a module dependency on a version of the module and most versioned modules also declare module dependencies on one or more other versioned modules.
This may sometimes be used to refer to SNOMED CT versioned edition.
A SNOMED CT edition that is published on a specific date.
A new version of the International Edition of SNOMED CT is released twice a year (in January and July).
National extensions generally follow this cycle, however it is often with a three-month delay. Some extensions (notably those including medication-related concepts) are released more frequently.
The International Edition, 20180131 (dated January 31, 2018).
The US National Edition, 20180501.
SNOMED CT version
Version
Versioned edition
A terminology binding that represents the set of permitted values that can be used to populate a coded data item.
A value set binding can be defined using individual rules. For example concepts that are: in a list of included concept identifiers, members of a specified reference set or subtypes of a specified concept.
Expression constraints provide a more flexible way to represent value set bindings as they are able to represent and combine a range of different rules to determine the set of concepts or expressions that are part of a value set.
The following expression constraint defines a value set that includes all concepts that represent a defined as using an for access.
<< : = <<