This page is a placeholder for an identified advanced service requirement for which a definitive set of detailed requirements are not yet available.
The detailed requirements are under discussion and this page will be updated based on the outcome of those discussions.
An expression is a structured combination of one or more concept identifiers that represents an idea. Expressions can be used to represent concept definitions. They can also be used to represent meanings that are not currently represented by a concept in the current SNOMED CT release.
When expressions are used, it is necessary to determine whether the meaning of a particular expression is a subtype of a specified concept or more generally is subsumed by a particular expression constraint. The terminology services required are similar to those described for testing concepts in sections Get and Test Concept Subtypes and Supertypes and Validate and Apply Expression Constraints. However, in this case the first step is to determine the meaning of the expression relative to existing defined concepts.
The required services are listed in the table below.
Services Required
Use Cases
(if entry of post-coordinated expressions is supported)
(if stored data includes post-coordinated expressions)
Notes
Language and/or dialect should be specified if the service returns terms associated with referenced concepts.
In the Snowstorm service requests [snowstorm] should be replaced by the URL to the Snowstorm server endpoint.
In the FHIR service requests [fhir] should be replaced by the URL to the FHIR terminology server endpoint. FHIR® is a registered trademarks of ().
The SNOMED CT MySQL example database is not designed as a terminology server and is not intended for use in a live system . It is referenced in this guide as an illustration that some readers may find helpful. For more information about the SNOMED CT example database see the
Test subsumption of an expression minimal REQUIRED
...
...
...
...
...
The Snowstorm and FHIR examples are presented in plain text and URL encoded versions. Always use the "Encoded URL" when testing the example service requests. The plain text version is included to aid readability but using this version in a service request may result in errors. These errors result from characters that have to be encoded as they are not permitted in a URL (see ).