SNOMED CT Implementation Guide for FHIR
0.0.1 - CI Build
SNOMED CT Implementation Guide for FHIR
0.0.1 - CI Build
SNOMED CT Implementation Guide for FHIR, published by SNOMED on FHIR project group. This guide is not an authorized publication; it is the continuous build for version 0.0.1 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/IHTSDO/snomed-ig/ and changes regularly. See the Directory of published versions
SNOMED CT ECL in FHIR =====================
Expression Constraint Language is a standardised way of selecting SNOMED CT concepts within a SNOMED CT code system.
Some of the most frequently used ECL operators are listed here:
| Symbol | Meaning |
|---|---|
| < | Descendants Of |
| << | Descendants and Self |
| : = | Where, Having Value |
| ^ | Member Of |
| * | Any |
| MINUS, AND, OR, ( ) | Logical Operations |
See also:
ECL can be used in the definition of ValueSets, either as part of the ValueSet definition or, at runtime, as part of an Implicit ValueSet where the ECL statement can be specified as part of an HTTP GET Request.
The great advantage of using ECL in the definition of a FHIR ValueSet is that the selection will evolve with successive releases of a particular SNOMED CT Edition. Inactivated concepts will be removed, and new ones will be added, as long as they continue to meet the ECL selection criteria.
So if it is desired that the set of concepts in a ValueSet should remain fixed for all time, then it is suggested that the include.version element should be populated so that the ValueSet would always be expanded against that particular release.
ECL can be specified in an HTTP Get request to provide a really lightweight way of selecting concepts. This allows developers to provide User Interface elements that are tightly bound to the context that they're used in. For example, only showing Surgical Procedures that start with the letters "APP".
GET /ValueSet/$expand?url=http://snomed.info/sct?fhir_vs=ecl/<<387713003&filter=APP