Page History

An expression often consists only of a subExpression. However, in some cases a definition status is needed to state whether the clinical meaning being represented is equivalent to or a subtype of the subExpression. If no definition status is included, the clinical meaning being represented is assumed to be

‘equivalent to’ the subExpression.

A subexpression consists of one or more focus concepts, optionally followed by a refinement. The meaning of

the expression is a subtype of all the focus

concepts constrained by the refinement. Note that where there is a requirement for multiple separately

qualified concepts to be present these are expressed

in attribute groups within a refinement of a general concept such as " situation with explicit context ".

The definition status states whether the clinical meaning being expressed is equivalent to or a subtype of the given expression representation.

A definition status of equivalentTo (i.e.

“===

”) indicates that the clinical meaning being represented is semantically equivalent to the given expression. If no definition status is included in the expression, this definition status is assumed.

A definition status of subtypeOf (i.e.

“<<<”) indicates that the clinical meaning being represented is a semantic subtype (or subclass) of the given expression.

A focusConcept consists of one or more concept references separated by

‘plus’ signs.

A conceptReference is represented by a ConceptIdoptionally followed by

a term enclosed by a pair of "

|" characters. Whitespace before or after the ConceptIdis ignored as is any whitespace between the initial "

|" characters and the first non-whitespace character in

the term or between the last non-whitespace character and before second "

|" character.

The ConceptIdmust be a

valid SNOMED CT identifier for a concept. The initial digit may not be zero. The smallest number of digits is six, and the maximum is 18.

The term must be the term from any SNOMED CT description that is associated with

the concept identified by the

preceding concept identifier. For example,

the term could be the

preferred synonym for a given dialect.

The term may include valid UTF-8 characters except for the pipe "

|" character.

The term begins with the first non-whitespace character following the starting "

|" character and ends with the last non-whitespace character preceding the next "

|" character.

A refinement contains all the grouped and ungrouped attributes that refine the meaning of the

containing expression.

An attribute group contains a collection of attributes that operate together as part of

the refinement of the

containing expression.

An attribute set contains one or

more attribute name-value pairs, separated by commas.

An attribute is a name-value pair expressing a

single refinement of the

containing expression.

The attribute name is the name of an attribute (or relationship type) to which a value is applied to refine the meaning of a

containing expression.

The attribute name is represented in the same way as other concept references.

An attribute value is either an expression, a string-based concrete value enclosed in quotation marks, or a numeric concrete value (i.e. integer or decimal) preceded by a

“#”.

An expression value is either a single concept reference without brackets, or a more complex expression enclosed in round brackets.

A string value includes one or more printable ASCII characters (these are also valid UTF8 characters encoded as one octet) and/or UTF8 characters encoded as 2- 3- or 4-octet sequences. Quotes and backslash characters must be preceded by the escape character (

“\

”).

A numeric value is either an integer or a decimal.

An integer may be positive, negative or zero. Positive integers optionally start with a plus sign (

“+

”), followed by a non-zero digit followed by zero to many additional digits. Negative integers begin with a minus sign (

“-

”) followed by a non-zero digit and zero to many additional digits. 

A decimal value starts with an integer. This is followed by a decimal point and one to many digits.

A SNOMED CT id is used to represent an attribute id or

a concept id. The initial digit may not be zero. The smallest number of digits is six, and the maximum is 18.

Optional whitespace characters (space, tab, carriage return and linefeed) are ignored everywhere in

the expression except:

1. Whitespace within a conceptIdis an error.

Note: Whitespace before or after the last digit of a

valid Identifier is ignored.

1. Non-consecutive spaces within a term are treated as a significant character of the term.

Note: Whitespace before the first or after the last non-whitespace character of a term is ignored

1. Whitespace within the quotation marks of a concrete value is treated as a significant character.

Space character.

Tab character.

Carriage return character.

Line feed character.

Quotation mark character.

Back slash character.

Any digit 0 through 9.

The digit 0.

Digits 1 through 9, but excluding 0. The first character of

a concept identifier is constrained to a digit other than zero.

Non whitespace (and non pipe) includes printable ASCII characters (these are also valid UTF8 characters encoded as one octet) and also includes all UTF8 characters encoded as 2- 3- or 4-octet sequences. It excludes space (which is %x20) and the pipe character "

|" (which is %x7C), and excludes CR, LF, HTAB and other ASCII control codes. See RFC 3629 (

 UTF-8,

a transformation format of ISO 10646 authored by the Network Working Group).

anyNonEscapedChar includes any printable ASCII characters which do not need to be preceded by an escape character (i.e.

“\

”). This includes valid UTF8 characters encoded as one octet and all UTF8 characters encoded as 2, 3 or 4 octet sequences. It does, however, exclude the quotation mark (

“) and the backslash (\). See RFC 3629 (

 UTF-8,

a transformation format of ISO 10646 authored by the Network Working Group).

The double quotation mark and the back slash character must both be escaped within a string-based concrete value by preceding them with a back slash.

UTF8 characters encoded as 2-octet sequences.

UTF8 characters encoded as 3-octet sequences.

UTF8 characters encoded as 4-octet sequences.

UTF8 characters encoded as 8-octet sequences.