Get and Test Concept Subtypes and Supertypes

Get subtype descendants of a concept

• conceptId

• Optionally, language or dialect code

• Set of conceptIds of all concepts with a direct or transitive 116680003 | is a | relationship to the specified concept.

• Optionally additional information such as the fully specified name or preferred term of each concept in the set.

Get supertype ancestors of a concept

• conceptId

• Optionally, language or dialect code

• Set of conceptIds of all concepts with a direct or transitive 116680003 | is a | relationship from the specified concept.

• Optionally additional information such as the fully specified name or preferred term of each concept in the set.

Test subsumption between two concepts 3

• Predicate.conceptId

• Candidate.conceptId

• If Candidate concept is a subtype descendant of the predicate concept: TRUE

• Otherwise: FALSE

Test a set of concepts for subsumption 3

• Predicate.conceptId

• Set of candidate.conceptIds

• Set of conceptIds of all concepts in the candidate set that have a direct or transitive 116680003 | is a | relationship from the specified concept.

Get subtype descendants of a concept

for example

Encoded URL

Returns a JSON representation of data about each of the descendant concepts.

The data returned for each concept includes:

• All concept release file data

• The preferred term and fully specified name.

Also returns the total number of descendant concepts.

As some concepts have very large numbers of descendants, this service is paged. Requests parameters include:

Get supertype ancestors of a concept

for example

Encoded URL

Returns a JSON representation of data about each of the ancestor concepts.

The data returned for each concept includes:

• All concept release file data

• The preferred term and fully specified name.

Also returns the total number of ancestor concepts.

Test subsumption between two concepts

Snowstorm does not provide a specific service for this test, but the test can be accomplished using the Get Concepts service (see ) with a combination of an expression constraint to represent the subsumption requirement and a list of concept identifiers.

For example

Encoded URL

Returns a JSON object with contents that depend on whether the candidate concept is a subtype of the predicate concept:

• If it is a subtype descendant the returned object contains:

  • The property total with value 1; and

  • An item array that contains data about the candidate concept (as it is the only concept that is both a subtype of the predicate and equal to the candidate concept).

Test a set of concepts for subsumption

Snowstorm does not provide a specific service for this test but the technique used in the row above can be used with all the candidate concept identifiers included in the comma separated list.

For example

Encoded URL

Returns a JSON representation of the candidate concepts that are subtypes descendants of the predicate concept.

• If one or more of the predicate concepts are subtypes of the candidate concept the returned object contains:

  • The property total with value equal to the number of candidate concepts that are subtypes of the predicate concept; and

  • For each candidate concept that is a subtype of the predicate concept a an item array that contain data about that candidate concept .

Get subtype descendants of a concept

Option 1)

for example:

Option 2)

Returns a JSON representation of data about each of the descendant concepts.

The data returned for each concept includes:

• code: the code for each descendant

• display: the preferred term for each descendant

Also returns the total number of descendant concepts.

As some concepts have very large numbers of descendants, this service is paged. Requests parameters include:

Get supertype ancestors of a concept

FHIR does not provide a specific operation for this service, but the supports that retrieval of the ancestors of SNOMED CT concept, and can thus be used to enable this service through the ValueSet/$expand operation.

for example:

Returns a JSON representation of data about each of the ancestor concepts.

The data returned for each concept includes:

• code: the code for each descendant

• display: the preferred term for each descendant

Also returns the total number of descendant concepts.

As some concepts have very large numbers of ancestors, this service is paged. Requests parameters include:

Test subsumption between two concepts

for example:

Returns a JSON representation of information about the subsumption relation between the two concepts:

• subsumed-by indicates that the concept provided as the value for codeA is a subtype of the concept provided as the value for codeB

• subsumes indicates that the concept provided as the value for codeA is a supertype of the concept provided as the value for codeB

• not-subsumed indicates that there is no subsumption relationship between the concepts provided as values for codeA and codeB

Get subtype descendants of a concept

for example

Returns rows containing the id and term for each subtype descendant of the specified concept.

• The query shown return the preferred term for each concept

• Replace the view suffix _pref with _fsn to return the fully specified name for each concept

Get supertype ancestors of a concept

for example

Returns rows containing the id and term for each supertype ancestor of the specified concept.

• The query shown return the preferred term for each concept

• Replace the view suffix _pref with _fsn to return the fully specified name for each concept

Test subsumption between two concepts

for example

Returns 1 if the candidate concept is a subtype of the supertype concept.

Test a set of concept for subsumption

Different approaches can be used depending on the specific requirement. As with the options for

1. Use the get descendants service to generate the list of descendants of the predicate concept and use this list as part of a query for records containing subtypes of that concept;

2. Individually, apply the test for subsumption between two concepts to each candidate concept;

3. Extend the ECL query to include all the candidate concepts as illustrated below.

Option 3 will return the ids of concepts in the bracketed list that are subtypes descendants of the predicate concept.