Purpose
A
900000000000512005 |Query specification type reference set|
allows a serialised query to represent the membership of a subset of
. A query contained in the
is run against the content of
to produce a subset of
,
or
. The query is referred to an intensional definition of the subset. It can be run
against future releases of
to generate an updated set of subset members.
The members of the resulting subset may also be represented in an enumerated form
as a
. An enumerated representation of a subset is referred to as an extensional definition.
Data structure
A
is a
String (data type)
containing
query (field) that represent intensional definitions of subsets of
. The result of running the query is an extensional representation of the subset of
which can be represented as a
. Its structure is shown in the following table.
|
Table 43. Query specification reference set - Data structure |
|
|
|---|---|---|
|
Field |
Data type |
Purpose |
|
A 128 bit unsigned
Integer (data type), uniquely identifying this
Different versions of a reference set member share the same id (field) but have different effectiveTime (field). This allows a reference set member to be modified or made active (field) (i.e. removed from the active set) at a specified time. |
||
|
The inclusive date or time at which this version of the identified
The current version of this
|
||
|
The state of the identified
If
active (field) = 1 (true) the
|
||
|
Identifies the
The value must be a
|
||
|
Identifies the
In this case, set to a subtype of 900000000000512005 |Query specification type| |
||
|
The identifier (
refsetId (field)) of the
|
||
|
The serialised query that can be used to (re-)generate the
A standard syntax for use in these queries is currently under development and is due for publication in late 2014. |
Metadata
The following metadata in the "Foundation metadata
"
supports this
:
Figure 14. Hierarchy of Foundation metadata concept
Descriptor template
The table below shows the descriptor that defines the structure of the 900000000000512005 |Query specification type reference set| pattern.
|
Table 44. Descriptor Template for Query Specification Reference Sets |
|
|
|
|
|
|---|---|---|---|---|---|
|
refsetId |
referencedComponentId |
attributeDescription |
attributeType |
attributeOrder |
|
|
0 |
|
||||
|
1 |
|
Note: The tables above omit the initial four columns of data present in the release
file. These follow the standards versioning pattern
id (field),
effectiveTime (field),
active (field),
active (field). Additionally, to aid understanding, the tables above also show the
from one of the
associated with each of the identified
. The release file only contains the
.
Example usage
In the example below, "serialised query 1" is a text string that can be used to generate members for
1, which is a simple member
(without any additional fields within its member records).
|
Table 45. Example rows from Query Specification Reference Set |
|
|
|---|---|---|
|
refsetId |
referencedComponentId |
query |
|
Serialized text of the query ... |
Query language specification
The specification of the query has yet to be defined / selected, but it should be capable of:
- Selecting
using primary fields, subsumption testing,
, relationshipGroup (field), set operators (
,
, excludes), and lexical query ; - Selecting
,
and
using similar mechanisms; - Calculation of values for the
's extended fields. Identifying the version of the syntax and any
syntax variations. - Queries that support definitions for terminologies other than
should also be supported. For example, queries to link or include codes in ICD-10, ICD-11, ICPC and
.
Note: During 2014 work is underway to develop and pilot a standard approach to representation
of queries including queries for generation of subset of
.
Feedback
Overview
Content Tools
Apps