Page History

...

where [sctid] is the concept id that identifies the given SNOMED CT edition (based on the identifier of the most dependent module), and "YYYYMMDD" is the date of release. Examples of sctids that identify a specific edition arelisted here.

4.2.1.0.3 Display

Any number of terms in additional languages and dialects can be specified for a given code in the "Designation" field (eg ValueSet.compose.include.concept.designation ) where the particular language refset to be referred to can be mapped from the language code field  "Language"(eg ValueSet.compose.include.concept.designation.language)  and the type of the term (ie FSN, Synonym, Definition) is held in the "Use" field ValueSet.compose.include.concept.designation.use.

The ExpansionProfile resource can be used to augment information supplied in ValueSet elements on request.   Michael Lawley Reuben Daniels - can you help out here?   Also suggestion that the ValueSet is not the correct place to making language reference set available.   Rather it should be augmented locally in the specific implementation.   Suggestion that the display element should specify the language code, but perhaps this is better done in an extension rather than forcing everyone to deal with it (ie core).   Also since ValueSets can be defined using filters (ie intesionally) that display terms would not be relevant in this case.

TODO: CodeSystem Supplement.  Peter Jordan?

4.2.1.0.4 SNOMED CT Expressions

A SNOMED CT Expression is a structured combination of one or more clinical concepts, stated using Compositional Grammar Syntax.

Expressions may optionally contain display terms.

4.2.1.0.5 4 Copyright and Licenses Note that many implementations are in the habit of simply using the date of release in the form YYYYMMDD (e.g. "20140531"), and assuming that the edition is known. However this is not always safe, so implementations that populate the version element must use the URI form.

This specification includes content from SNOMED Clinical Terms® (SNOMED CT®) which is copyright of the International Health Terminology Standards Development Organisation (IHTSDO). Implementers of these specifications must have the appropriate SNOMED CT Affiliate license - for more information contact http://www.snomed.org/snomed-ct/get-snomed-ct  or info@snomed.org.

4.2.1.0.

...

5 RDF Image Modified

The SNOMED International URI specifications use the namespace http://snomed.info/sct for the code system, and the URI http://snomed.info/id for the individual concepts in the code system. This means that when a SNOMED CT concept is converted from the system::code pair, where the system is http://snomed.info/sct, to the RDF ontological form, the representation is http://snomed.info/id/[concept-id]. Expressions are represented using the URI pattern http://snomed.info/scg/[expression]. Expressions represented in this way SHALL not contain whitespace, terms, or comments.

4.2.1.0.

...

6 SNOMED CT Properties Image Modified

In addition to the standard properties, the following properties are defined for SNOMED CT:

...

Note that when a $lookup operation is performed on a SNOMED CT concept, servers SHALL return the full URI for the edition and version being used (see above) in the version property. Other properties are at the discretion of the server and the client.

4.2.1.0.

...

7 SNOMED CT Filters Image Modified

This section documents the property filters that can be used with the SNOMED CT code system in value set composition statements.

For implementer convenience, some of the property filters are documented in terms of the SNOMED CT Expression Constraint Language, but this does not imply that its use is required.

4.2.1.0.

...

7.1 By Subsumption Image Modified

Description	Select a set of concepts based on subsumption testing
Property Name	concept
Operations Allowed	is-a
Values Allowed	[concept id]
Comments	Includes all concept ids that have a transitive is-a relationship with the concept Id provided as the value (including the concept itself)
Example	Administration Methods
SCT ECL	<< [concept] (Long syntax: descendantOrSelfOf [concept])

4.2.1.0.

...

7.2 By Reference Set Image Modified

Description	Select a set of concepts based on their membership of a SNOMED CT reference set
Property Name	concept
Operations Allowed	in
Values Allowed	[concept id]
Comments	Includes all concept ids that are active members of the reference set identified by the concept Id provided as the value
SCT ECL	^ [concept] (Long syntax: memberOf [concept])

4.2.1.0.

...

7.3 By SNOMED Expression Constraint Image Modified

 "compose": {
  "include": [
    {
      "system": "http://snomed.info/sct",
      "filter": [
        {
          "property": "constraint",
          "op": "=",
          "value": "<< 30506011000036107 |Australian product|: 700000101000036108 |hasTP| = 17311000168105 |Panadol|"
        }
      ]
    }
  ]
}

   

4.2.1.0.

...

7.4 By whether postcoordination is allowed Image Modified

Description	Specify whether postcoordination is allowed or not
Property Name	expressions
Operations Allowed	=
Values Allowed	true or false
Comments	Expressions, if allowed, are subject to the same rules as precoordinated concepts. (Note: simple reference sets do not include expressions).
Example	Administration Methods
SCT ECL	n/a

4.2.1.0.

...

8 Implicit Value Sets Image Modified

Implicit value sets are those whose specification can be predicted based on the grammar of the underlying code system, and the known structure of the URL that identifies them. SNOMED CT has two common sets of implicit value sets defined: By Subsumption, and By Reference Set. These implicit value sets do not use complex queries. This allows a single URL to serve as a value set definition that defines a value set, and can serve as the basis for the $expansion operation.

...

New Sections

...

- works in progress

These have been removed into their own pages while the text is agreed.   Since they are additional guidance, there is no reason to think that anything being added will 'break' the above.

4.2.1.0.3 3 Display