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.
Overview
<span class="conf-macro output-inline" data-hasbody="false" data-macro-name="glossary-include">
<span>An <a href="https://confluence.ihtsdotools.org/display/DOCGLOSS/expression" title="Glossary link: expression" rel="nofollow">expression</a> is </span>
a structured combination of one or more <a href="https://confluence.ihtsdotools.org/display/DOCGLOSS/concept+identifier" title="Glossary link: concept identifiers" rel="nofollow" class="conf-macro output-inline" data-hasbody="false" data-macro-name="gloss">concept identifiers</a> that represents an idea.
</span> 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 4.5 Get and Test Concept Subtypes and Supertypes and 4.7 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.
Requirements and Options
The required services are listed in Table 4.15-1.
Table 4.15-1: Services Required
| Service Name and Status | Input | Output |
|---|---|---|
Test subsumption of an expression minimal REQUIRED |
Interdependencies
Required By
- Use Cases
3.2.3 EHR Data Entry (if entry of post-coordinated expressions is supported)
3.4 EHR Reporting and Analytics (if stored data includes post-coordinated expressions)
Depends On
- 4.1 Select Edition and Version
- 4.4 Get Definition of a Concept
- 4.5 Get and Test Concept Subtypes and Supertypes
- 4.7 Validate and Apply Expression Constraints
Service Examples
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 IETF RFC1738).
Table 4.15-2: Snowstorm API
| Service Name | API Call2 | Result |
Get | ||
| Get |
Table 4.15-3: FHIR API (*to be added*)
| Service Name | API Call3 | Result |
| ... | ||
... |
Table 4.15-4: MySQL Example Database
| Service Name | SQL Query 4 | Result |
Get |
Footnotes
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 HL7 (www.hl7.org).
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 SNOMED CT - SQL Practical Guide. For instructions on how to build the example database refer to Appendix A: Building the SNOMED CT Example Database.
Feedback
Overview
Content Tools
Apps