diff --git a/README.md b/README.md
index 0cac4d8386e..93b8c52fc89 100644
--- a/README.md
+++ b/README.md
@@ -55,9 +55,10 @@ The IBM FHIR Server is modular and extensible. The following tables provide an o
|------|-----------|----------|
|fhir-model|An object model generated from the FHIR R4 specification and corresponding parsers and generators for XML and JSON|true|
|fhir-registry|A resource registry, registry provider interfaces, and pre-registered resources shipped with the FHIR specification|false|
-|fhir-term|A terminology service provider interface with a default implementation that implements terminology services from fully-defined CodeSystems in the registry|false|
-|fhir-term-graph|A terminology service provider that implements terminology services using JanusGraph|false|
-|fhir-term-remote|A terminology service provider that connects to an external service using a REST client to access code system content|false|
+|term/fhir-term|A terminology service provider interface with a default implementation that implements terminology services from fully-defined CodeSystems in the registry|false|
+|term/fhir-term-graph|A terminology service provider that implements terminology services using JanusGraph|false|
+|term/fhir-term-graph-loader|Populates the terminology service backend when using JanusGraph|false|
+|term/fhir-term-remote|A terminology service provider that connects to an external service using a REST client to access code system content|false|
|fhir-profile|Helper methods for validating ValueSet membership and Profile conformance|false|
|fhir-path|An implementation of version 2.0.0 of the FHIRPath specification assumed by FHIR R4|false|
|fhir-validation|Validation utility for validating resource instances against the base specification and/or configured profiles|false|
diff --git a/build/audit/kafka/pre-integration-test.sh b/build/audit/kafka/pre-integration-test.sh
index fe57602e6cc..e15ae1ad1df 100644
--- a/build/audit/kafka/pre-integration-test.sh
+++ b/build/audit/kafka/pre-integration-test.sh
@@ -38,8 +38,8 @@ config(){
USERLIB="${DIST}/userlib"
mkdir -p $USERLIB
find ${WORKSPACE}/conformance -iname 'fhir-ig*.jar' -not -iname 'fhir*-tests.jar' -not -iname 'fhir*-test-*.jar' -exec cp -f {} ${USERLIB} \;
- cp -pr ${WORKSPACE}/operation/fhir-operation-test/target/fhir-operation-*-tests.jar ${USERLIB}
- cp -pr ${WORKSPACE}/operation/fhir-operation-term-cache/target/fhir-operation-*.jar ${USERLIB}
+ cp -pr ${WORKSPACE}/fhir-operation-test/target/fhir-operation-*-tests.jar ${USERLIB}
+ cp -pr ${WORKSPACE}/term/operation/fhir-operation-term-cache/target/fhir-operation-*.jar ${USERLIB}
echo "Finished copying fhir-server dependencies..."
# Move over the test configurations
diff --git a/build/docker/copy-test-operations.sh b/build/docker/copy-test-operations.sh
index c8fdcfc548a..dbae4291388 100755
--- a/build/docker/copy-test-operations.sh
+++ b/build/docker/copy-test-operations.sh
@@ -19,6 +19,6 @@ mkdir -p $USERLIB
echo "Copying test artifacts to install location..."
find ${WORKSPACE}/conformance -iname 'fhir-ig*.jar' -not -iname 'fhir*-tests.jar' -not -iname 'fhir*-test-*.jar' -exec cp -f {} ${USERLIB} \;
cp -pr ${WORKSPACE}/operation/fhir-operation-test/target/fhir-operation-*-tests.jar ${USERLIB}
-cp -pr ${WORKSPACE}/operation/fhir-operation-term-cache/target/fhir-operation-*.jar ${USERLIB}
+cp -pr ${WORKSPACE}/term/operation/fhir-operation-term-cache/target/fhir-operation-*.jar ${USERLIB}
echo "Finished copying test operations."
diff --git a/build/migration/db2/2_compose.sh b/build/migration/db2/2_compose.sh
index c18f40b0770..debcde09c61 100644
--- a/build/migration/db2/2_compose.sh
+++ b/build/migration/db2/2_compose.sh
@@ -49,6 +49,10 @@ config(){
then
find ${WORKSPACE}/prev/operation/fhir-operation-term-cache/target -iname '*.jar' -exec cp -f {} ${USERLIB} \;
fi
+ if [ -d ${WORKSPACE}/prev/term/operation/fhir-operation-term-cache/target ]
+ then
+ find ${WORKSPACE}/prev/term/operation/fhir-operation-term-cache/target -iname '*.jar' -exec cp -f {} ${USERLIB} \;
+ fi
echo "Copying over the overrides for the datasource"
mkdir -p ${DIST}/overrides
diff --git a/build/migration/db2/5_current-pre-integration-test.sh b/build/migration/db2/5_current-pre-integration-test.sh
index c2eb64e64e3..1244df390ea 100644
--- a/build/migration/db2/5_current-pre-integration-test.sh
+++ b/build/migration/db2/5_current-pre-integration-test.sh
@@ -38,6 +38,10 @@ config(){
then
find ${WORKSPACE}/fhir/operation/fhir-operation-term-cache/target -iname '*.jar' -exec cp -f {} ${USERLIB} \;
fi
+ if [ -d ${WORKSPACE}/fhir/term/operation/fhir-operation-term-cache/target ]
+ then
+ find ${WORKSPACE}/fhir/term/operation/fhir-operation-term-cache/target -iname '*.jar' -exec cp -f {} ${USERLIB} \;
+ fi
echo "Remove the old overrides, and copy the current overrides for the datasource"
rm -rf ${DIST}/overrides
diff --git a/build/migration/postgres/2_compose.sh b/build/migration/postgres/2_compose.sh
index 1ee6da0ba82..530fc472567 100644
--- a/build/migration/postgres/2_compose.sh
+++ b/build/migration/postgres/2_compose.sh
@@ -55,6 +55,10 @@ config(){
then
find ${WORKSPACE}/prev/operation/fhir-operation-term-cache/target -iname '*.jar' -exec cp -f {} ${USERLIB} \;
fi
+ if [ -d ${WORKSPACE}/prev/term/operation/fhir-operation-term-cache/target ]
+ then
+ find ${WORKSPACE}/prev/term/operation/fhir-operation-term-cache/target -iname '*.jar' -exec cp -f {} ${USERLIB} \;
+ fi
# Move over the test configurations
echo "Copying over the fhir-server-config.json and updating publishing"
cp -f ${DIST}/config/default/fhir-server-config-postgresql.json ${DIST}/config/default/fhir-server-config.json
diff --git a/build/migration/postgres/5_current-pre-integration-test.sh b/build/migration/postgres/5_current-pre-integration-test.sh
index 011eedadd97..48d5dbd28fb 100644
--- a/build/migration/postgres/5_current-pre-integration-test.sh
+++ b/build/migration/postgres/5_current-pre-integration-test.sh
@@ -34,6 +34,7 @@ config(){
mkdir -p "${USERLIB}"
find ${WORKSPACE}/fhir/conformance -iname 'fhir-ig*.jar' -not -iname 'fhir*-tests.jar' -not -iname 'fhir*-test-*.jar' -exec cp -f {} ${USERLIB} \;
find ${WORKSPACE}/fhir/operation/fhir-operation-test/target -iname '*.jar' -exec cp -f {} ${USERLIB} \;
+ find ${WORKSPACE}/fhir/operation/fhir-operation-test/target -iname '*.jar' -exec cp -f {} ${USERLIB} \;
echo "Copying over the overrides for the datasource"
mkdir -p ${DIST}/overrides
@@ -43,6 +44,11 @@ config(){
then
find ${WORKSPACE}/fhir/operation/fhir-operation-term-cache/target -iname '*.jar' -exec cp -f {} ${USERLIB} \;
fi
+
+ if [ -d ${WORKSPACE}/fhir/term/operation/fhir-operation-term-cache/target ]
+ then
+ find ${WORKSPACE}/fhir/term/operation/fhir-operation-term-cache/target -iname '*.jar' -exec cp -f {} ${USERLIB} \;
+ fi
# Move over the test configurations
echo "Copying over the fhir-server-config.json and updating publishing"
cp -f ${DIST}/config/default/fhir-server-config-postgresql.json ${DIST}/config/default/fhir-server-config.json
diff --git a/build/notifications/kafka/pre-integration-test.sh b/build/notifications/kafka/pre-integration-test.sh
index 8687fbec4d7..cd05fd88658 100644
--- a/build/notifications/kafka/pre-integration-test.sh
+++ b/build/notifications/kafka/pre-integration-test.sh
@@ -38,7 +38,7 @@ config(){
mkdir -p $USERLIB
find ${WORKSPACE}/conformance -iname 'fhir-ig*.jar' -not -iname 'fhir*-tests.jar' -not -iname 'fhir*-test-*.jar' -exec cp -f {} ${USERLIB} \;
cp -pr ${WORKSPACE}/operation/fhir-operation-test/target/fhir-operation-*-tests.jar ${USERLIB}
- cp -pr ${WORKSPACE}/operation/fhir-operation-term-cache/target/fhir-operation-*.jar ${USERLIB}
+ cp -pr ${WORKSPACE}/term/operation/fhir-operation-term-cache/target/fhir-operation-*.jar ${USERLIB}
echo "Finished copying fhir-server dependencies..."
# Move over the test configurations
diff --git a/build/persistence/postgres/pre-integration-test.sh b/build/persistence/postgres/pre-integration-test.sh
index 81d7a2b5222..34e165f6396 100644
--- a/build/persistence/postgres/pre-integration-test.sh
+++ b/build/persistence/postgres/pre-integration-test.sh
@@ -64,7 +64,7 @@ copy_server_config(){
echo "Copying test artifacts to install location..."
find ${WORKSPACE}/conformance -iname 'fhir-ig*.jar' -not -iname 'fhir*-tests.jar' -not -iname 'fhir*-test-*.jar' -exec cp -f {} ${USERLIB} \;
cp -pr ${WORKSPACE}/operation/fhir-operation-test/target/fhir-operation-*-tests.jar ${USERLIB}
- cp -pr ${WORKSPACE}/operation/fhir-operation-term-cache/target/fhir-operation-*.jar ${USERLIB}
+ cp -pr ${WORKSPACE}/term/operation/fhir-operation-term-cache/target/fhir-operation-*.jar ${USERLIB}
echo "Finished copying fhir-server dependencies..."
}
diff --git a/build/pre-integration-test.ps1 b/build/pre-integration-test.ps1
index 2550bf8282d..807c906e131 100644
--- a/build/pre-integration-test.ps1
+++ b/build/pre-integration-test.ps1
@@ -118,7 +118,7 @@ If (!(Test-Path -Path $USERLIB_DIR) ) {
}
Copy-Item $CP_ITEM -Destination $USERLIB_DST
-$CP_ITEM=[string]$DIR_WORKSPACE + '\operation\fhir-operation-term-cache\target\fhir-operation-term-cache-*.jar'
+$CP_ITEM=[string]$DIR_WORKSPACE + '\term\operation\fhir-operation-term-cache\target\fhir-operation-term-cache-*.jar'
Copy-Item $CP_ITEM -Destination $USERLIB_DST
# Start up the fhir server
diff --git a/build/pre-integration-test.sh b/build/pre-integration-test.sh
index 71c74d2b880..32a4b8629ad 100755
--- a/build/pre-integration-test.sh
+++ b/build/pre-integration-test.sh
@@ -75,7 +75,7 @@ echo "Copying test artifacts to install location..."
USERLIB=${SIT}/wlp/usr/servers/fhir-server/userlib
rm -rf ${USERLIB}/fhir-operation-*-tests.jar
cp -pr ${WORKSPACE}/operation/fhir-operation-test/target/fhir-operation-*-tests.jar ${USERLIB}/
-cp -pr ${WORKSPACE}/operation/fhir-operation-term-cache/target/fhir-operation-*.jar ${USERLIB}/
+cp -pr ${WORKSPACE}/term/operation/fhir-operation-term-cache/target/fhir-operation-*.jar ${USERLIB}/
find ${WORKSPACE}/conformance -iname 'fhir-ig*.jar' -not -iname 'fhir*-tests.jar' -not -iname 'fhir*-test-*.jar' -exec cp -f {} ${USERLIB} \;
# Start up the fhir server
diff --git a/docs/src/pages/guides/FHIRTerminologyGuide.md b/docs/src/pages/guides/FHIRTerminologyGuide.md
index 17ad5091522..9e0489c0a96 100644
--- a/docs/src/pages/guides/FHIRTerminologyGuide.md
+++ b/docs/src/pages/guides/FHIRTerminologyGuide.md
@@ -6,7 +6,7 @@ date: "2021-04-23"
## Overview
-The IBM FHIR Server Terminology module ([fhir-term](https://github.com/IBM/FHIR/tree/main/fhir-term)) provides a FHIR terminology service provider interface (SPI) and a default implementation that implements terminology services using `CodeSystem`, `ValueSet`, and `ConceptMap` resources that have been made available through the FHIR registry module ([fhir-registry](https://github.com/IBM/FHIR/tree/main/fhir-registry)).
+The IBM FHIR Server Terminology module ([fhir-term](https://github.com/IBM/FHIR/tree/main/term/fhir-term)) provides a FHIR terminology service provider interface (SPI) and a default implementation that implements terminology services using `CodeSystem`, `ValueSet`, and `ConceptMap` resources that have been made available through the FHIR registry module ([fhir-registry](https://github.com/IBM/FHIR/tree/main/fhir-registry)).
## FHIR Terminology Service Diagram
@@ -36,11 +36,11 @@ NOTE: `closure(CodeSystem, Set)`, `getConcepts(CodeSystem, Function)`, `getConce
## Registry Terminology Service Provider Implementation
-The default implementation of `FHIRTermServiceProvider` ([RegistryTermServiceProvider](https://github.com/IBM/FHIR/blob/main/fhir-term/src/main/java/com/ibm/fhir/term/service/provider/RegistryTermServiceProvider.java)) leverages terminology resources (`CodeSystem`, `ValueSet`, and `ConceptMap`) that have been made available through the FHIR registry module ([fhir-registry](https://github.com/IBM/FHIR/tree/main/fhir-registry)). It supports `CodeSystem` resources with *complete* content (`CodeSystem.content = 'complete'`) and `ValueSet` resources that reference `CodeSystem` resources that have complete content.
+The default implementation of `FHIRTermServiceProvider` ([RegistryTermServiceProvider](https://github.com/IBM/FHIR/blob/main/term/fhir-term/src/main/java/com/ibm/fhir/term/service/provider/RegistryTermServiceProvider.java)) leverages terminology resources (`CodeSystem`, `ValueSet`, and `ConceptMap`) that have been made available through the FHIR registry module ([fhir-registry](https://github.com/IBM/FHIR/tree/main/fhir-registry)). It supports `CodeSystem` resources with *complete* content (`CodeSystem.content = 'complete'`) and `ValueSet` resources that reference `CodeSystem` resources that have complete content.
## FHIR Terminology Service Singleton Facade
-The FHIR Terminology Service Singleton facade ([FHIRTermService](https://github.com/IBM/FHIR/blob/main/fhir-term/src/main/java/com/ibm/fhir/term/service/FHIRTermService.java)) loads a list of `FHIRTermServiceProvider` instances from the ServiceLoader and includes an instance of the `RegistryTermServiceProvider`. Client code (Java) that requires terminology capabilities should access them via the `FHIRTermService` singleton facade. Here is an example:
+The FHIR Terminology Service Singleton facade ([FHIRTermService](https://github.com/IBM/FHIR/blob/main/term/fhir-term/src/main/java/com/ibm/fhir/term/service/FHIRTermService.java)) loads a list of `FHIRTermServiceProvider` instances from the ServiceLoader and includes an instance of the `RegistryTermServiceProvider`. Client code (Java) that requires terminology capabilities should access them via the `FHIRTermService` singleton facade. Here is an example:
```java
ValueSet valueSet = ValueSetSupport.getValueSet("http://ibm.com/fhir/ValueSet/vs1");
@@ -73,7 +73,7 @@ NOTE: The current implementation of `FHIRTermService` does not support optional
## FHIR Server Terminology Extended Operations
-The FHIR terminology operations module ([fhir-operation-term](https://github.com/IBM/FHIR/tree/main/operation/fhir-operation-term)) connects the FHIR Server REST layer to the FHIR terminology module via the operations framework. This module implements the terminology operations as defined in the FHIR terminology service specification [http://hl7.org/fhir/terminology-service.html](http://hl7.org/fhir/terminology-service.html). One exception is the `$closure` operation. The `$closure` operation is experimental and does not support versioning or replay. This means that the `$closure` operation will always return the set of closure table entries for the given input concepts and does not store client state.
+The FHIR terminology operations module ([fhir-operation-term](https://github.com/IBM/FHIR/tree/main/term/operation/fhir-operation-term)) connects the FHIR Server REST layer to the FHIR terminology module via the operations framework. This module implements the terminology operations as defined in the FHIR terminology service specification [http://hl7.org/fhir/terminology-service.html](http://hl7.org/fhir/terminology-service.html). One exception is the `$closure` operation. The `$closure` operation is experimental and does not support versioning or replay. This means that the `$closure` operation will always return the set of closure table entries for the given input concepts and does not store client state.
## FHIRPath Terminology Functions
@@ -107,7 +107,7 @@ Additionally, the FHIRPath functions `subsumedBy` and `subsumes` have been imple
## Graph Terminology Service Provider Implementation (experimental)
-The FHIR term graph module [fhir-term-graph](https://github.com/IBM/FHIR/tree/main/fhir-term-graph) provides an implementation of `FHIRTermServiceProvider` that is backed by a graph database ([JanusGraph](https://janusgraph.org)). The module also contains term graph loaders for SNOMED-CT Release Format 2 (RF2) files (SnomedTermGraphLoader), UMLS Rich Release Format (RRF) files (UMLSTermGraphLoader), and FHIR CodeSystem resources (CodeSystemTermGraphLoader). Graph term service providers may be enabled / configured through the `fhir-server-config.json` file per the configuration properties specified in the [FHIR Server User's Guide](https://ibm.github.io/FHIR/guides/FHIRServerUsersGuide#51-configuration-properties-reference).
+The FHIR term graph module [fhir-term-graph](https://github.com/IBM/FHIR/tree/main/term/fhir-term-graph) provides an implementation of `FHIRTermServiceProvider` that is backed by a graph database ([JanusGraph](https://janusgraph.org)). The module also contains term graph loaders for SNOMED-CT Release Format 2 (RF2) files (SnomedTermGraphLoader), UMLS Rich Release Format (RRF) files (UMLSTermGraphLoader), and FHIR CodeSystem resources (CodeSystemTermGraphLoader). Graph term service providers may be enabled / configured through the `fhir-server-config.json` file per the configuration properties specified in the [FHIR Server User's Guide](https://ibm.github.io/FHIR/guides/FHIRServerUsersGuide#51-configuration-properties-reference).
Example configurations:
@@ -144,7 +144,7 @@ Example configurations:
## Remote Terminology Service Provider Implementation (experimental)
-The FHIR term remote module [fhir-term-remote](https://github.com/IBM/FHIR/tree/main/fhir-term-remote) provides an implementation of `FHIRTermServiceProvider` that connects to an external service using a REST client to access code system content. The external service must implement the FHIR REST terminology APIs documented [here](http://hl7.org/fhir/terminology-service.html). Remote term service providers may be enabled / configured through the `fhir-server-config.json` file per the configuration properties specified in the [FHIR Server User's Guide](https://ibm.github.io/FHIR/guides/FHIRServerUsersGuide#51-configuration-properties-reference).
+The FHIR term remote module [fhir-term-remote](https://github.com/IBM/FHIR/tree/main/term/fhir-term-remote) provides an implementation of `FHIRTermServiceProvider` that connects to an external service using a REST client to access code system content. The external service must implement the FHIR REST terminology APIs documented [here](http://hl7.org/fhir/terminology-service.html). Remote term service providers may be enabled / configured through the `fhir-server-config.json` file per the configuration properties specified in the [FHIR Server User's Guide](https://ibm.github.io/FHIR/guides/FHIRServerUsersGuide#51-configuration-properties-reference).
Example configurations:
diff --git a/fhir-parent/pom.xml b/fhir-parent/pom.xml
index a25704ee17c..dbe61ad0f05 100644
--- a/fhir-parent/pom.xml
+++ b/fhir-parent/pom.xml
@@ -81,9 +81,7 @@
SNOMED CT is the most comprehensive and precise clinical health terminology product in the world, owned and distributed around the world by The International Health Terminology Standards Development Organisation (IHTSDO).
\n\n\n Copyright Statement:\n
\n© 2002-2016 International Health Terminology Standards Development Organisation (IHTSDO). All rights reserved. SNOMED CT®, was originally created by The College of American Pathologists. "SNOMED" and "SNOMED CT" are registered trademarks of the IHTSDO http://www.ihtsdo.org/snomed-ct/get-snomed-ct
\n\n\n Properties\n
\n\n Code\n | \n\n URL\n | \n\n Description\n | \n\n Type\n | \n
inactive | \nhttp://snomed.info/field/Concept.active | \nWhether the code is active or not (defaults to false). Not the same as deprecated | \nboolean | \n
definitionStatusId | \nhttp://snomed.info/field/Concept.definitionStatusId | \nEither of the codes that are descendants of 900000000000444006 | \ncode | \n
parent | \nhttp://.........? | \nA SNOMED CT concept id that has the target of a direct is-a relationship from the concept | \ncode | \n
child | \nhttp://.........? | \nA SNOMED CT concept id that has a direct is-a relationship to the concept | \ncode | \n
moduleId | \nhttp://snomed.info/field/Concept.moduleId | \nThe SNOMED CT concept id of the module that the concept belongs to. | \ncode | \n
normalForm | \nhttp://.........? | \nGenerated Normal form expression for the provided code or expression, with terms | \nstring | \n
normalFormTerse | \nhttp://.........? | \nGenerated Normal form expression for the provided code or expression, conceptIds only | \nstring | \n
Due to | \nhttp://snomed.info/id/42752001 | \n\n | code | \n
Associated with | \nhttp://snomed.info/id/47429007 | \n\n | code | \n
Associated morphology | \nhttp://snomed.info/id/116676008 | \n\n | code | \n
Has specimen | \nhttp://snomed.info/id/116686009 | \n\n | code | \n
Specimen source morphology | \nhttp://snomed.info/id/118168003 | \n\n | code | \n
Specimen source topography | \nhttp://snomed.info/id/118169006 | \n\n | code | \n
Specimen source identity | \nhttp://snomed.info/id/118170007 | \n\n | code | \n
Specimen procedure | \nhttp://snomed.info/id/118171006 | \n\n | code | \n
Part of | \nhttp://snomed.info/id/123005000 | \n\n | code | \n
Has active ingredient | \nhttp://snomed.info/id/127489000 | \n\n | code | \n
Subject of information | \nhttp://snomed.info/id/131195008 | \n\n | code | \n
Causative agent | \nhttp://snomed.info/id/246075003 | \n\n | code | \n
Associated finding | \nhttp://snomed.info/id/246090004 | \n\n | code | \n
Component | \nhttp://snomed.info/id/246093002 | \n\n | code | \n
Severity | \nhttp://snomed.info/id/246112005 | \n\n | code | \n
Occurrence | \nhttp://snomed.info/id/246454002 | \n\n | code | \n
Episodicity | \nhttp://snomed.info/id/246456000 | \n\n | code | \n
Technique | \nhttp://snomed.info/id/246501002 | \n\n | code | \n
Revision status | \nhttp://snomed.info/id/246513007 | \n\n | code | \n
Units | \nhttp://snomed.info/id/246514001 | \n\n | code | \n
After | \nhttp://snomed.info/id/255234002 | \n\n | code | \n
Access | \nhttp://snomed.info/id/260507000 | \n\n | code | \n
Method | \nhttp://snomed.info/id/260686004 | \n\n | code | \n
Priority | \nhttp://snomed.info/id/260870009 | \n\n | code | \n
Clinical course | \nhttp://snomed.info/id/263502005 | \n\n | code | \n
Laterality | \nhttp://snomed.info/id/272741003 | \n\n | code | \n
Associated procedure | \nhttp://snomed.info/id/363589002 | \n\n | code | \n
Finding site | \nhttp://snomed.info/id/363698007 | \n\n | code | \n
Laterality | \nhttp://snomed.info/id/363699004 | \n\n | code | \n
Direct morphology | \nhttp://snomed.info/id/363700003 | \n\n | code | \n
Direct substance | \nhttp://snomed.info/id/363701004 | \n\n | code | \n
Has focus | \nhttp://snomed.info/id/363702006 | \n\n | code | \n
Has intent | \nhttp://snomed.info/id/363703001 | \n\n | code | \n
Procedure site | \nhttp://snomed.info/id/363704007 | \n\n | code | \n
Has definitional manifestation | \nhttp://snomed.info/id/363705008 | \n\n | code | \n
Indirect morphology | \nhttp://snomed.info/id/363709002 | \n\n | code | \n
Indirect device | \nhttp://snomed.info/id/363710007 | \n\n | code | \n
Has interpretation | \nhttp://snomed.info/id/363713009 | \n\n | code | \n
Interprets | \nhttp://snomed.info/id/363714003 | \n\n | code | \n
Measurement method | \nhttp://snomed.info/id/370129005 | \n\n | code | \n
Property | \nhttp://snomed.info/id/370130000 | \n\n | code | \n
Recipient category | \nhttp://snomed.info/id/370131001 | \n\n | code | \n
Scale type | \nhttp://snomed.info/id/370132008 | \n\n | code | \n
Specimen substance | \nhttp://snomed.info/id/370133003 | \n\n | code | \n
Time aspect | \nhttp://snomed.info/id/370134009 | \n\n | code | \n
Pathological process | \nhttp://snomed.info/id/370135005 | \n\n | code | \n
Procedure site - Direct | \nhttp://snomed.info/id/405813007 | \n\n | code | \n
Procedure site - Indirect | \nhttp://snomed.info/id/405814001 | \n\n | code | \n
Procedure device | \nhttp://snomed.info/id/405815000 | \n\n | code | \n
Procedure morphology | \nhttp://snomed.info/id/405816004 | \n\n | code | \n
Finding context | \nhttp://snomed.info/id/408729009 | \n\n | code | \n
Procedure context | \nhttp://snomed.info/id/408730004 | \n\n | code | \n
Temporal context | \nhttp://snomed.info/id/408731000 | \n\n | code | \n
Subject relationship context | \nhttp://snomed.info/id/408732007 | \n\n | code | \n
Route of administration | \nhttp://snomed.info/id/410675002 | \n\n | code | \n
Has dose form | \nhttp://snomed.info/id/411116001 | \n\n | code | \n
Finding method | \nhttp://snomed.info/id/418775008 | \n\n | code | \n
Finding informer | \nhttp://snomed.info/id/419066007 | \n\n | code | \n
Using device | \nhttp://snomed.info/id/424226004 | \n\n | code | \n
Using energy | \nhttp://snomed.info/id/424244007 | \n\n | code | \n
Using substance | \nhttp://snomed.info/id/424361007 | \n\n | code | \n
Surgical approach | \nhttp://snomed.info/id/424876005 | \n\n | code | \n
Using access device | \nhttp://snomed.info/id/425391005 | \n\n | code | \n
Role group | \nhttp://snomed.info/id/609096000 | \n\n | code | \n
Property type | \nhttp://snomed.info/id/704318007 | \n\n | code | \n
Inheres in | \nhttp://snomed.info/id/704319004 | \n\n | code | \n
Towards | \nhttp://snomed.info/id/704320005 | \n\n | code | \n
Characterizes | \nhttp://snomed.info/id/704321009 | \n\n | code | \n
Process agent | \nhttp://snomed.info/id/704322002 | \n\n | code | \n
Process duration | \nhttp://snomed.info/id/704323007 | \n\n | code | \n
Process output | \nhttp://snomed.info/id/704324001 | \n\n | code | \n
Relative to | \nhttp://snomed.info/id/704325000 | \n\n | code | \n
Precondition | \nhttp://snomed.info/id/704326004 | \n\n | code | \n
Direct site | \nhttp://snomed.info/id/704327008 | \n\n | code | \n
Specified by | \nhttp://snomed.info/id/704346009 | \n\n | code | \n
Observes | \nhttp://snomed.info/id/704347000 | \n\n | code | \n
Is about | \nhttp://snomed.info/id/704647008 | \n\n | code | \n
\n Filters\n
\n\n Code\n | \n\n Description\n | \n\n operator\n | \n\n Value\n | \n
concept | \nFilter that includes concepts based on their logical definition. e.g. [concept] [is-a] [x] - include all concepts with an is-a relationship to concept x, or [concept] [in] [x]- include all concepts in the reference set identified by concept x | \nis-a in | \nA SNOMED CT code | \n
expression | \nThe result of the filter is the result of executing the given SNOMED CT Expression Constraint | \n= | \nA SNOMED CT ECL expression (see http://snomed.org/ecl) | \n
expressions | \nWhether post-coordinated expressions are included in the value set | \n= | \ntrue or false | \n
This code system http://snomed.info/sct defines many codes, but they are not represented here
\n