Hauptseite: Unterschied zwischen den Versionen

Aus CTS2-LE
Zur Navigation springen Zur Suche springen
K (→‎Core Web Services)
 
(217 dazwischenliegende Versionen von 6 Benutzern werden nicht angezeigt)
Zeile 1: Zeile 1:
−
<inputbox>
+
{{DISPLAYTITLE:CTS2 Linked Data Edition Terminology Server}}
−
type=create
+
 
−
buttonlabel=Seite anlegen / create page
+
Controlled vocabularies (also known as code systems or terminologies) are common information artefacts in healthcare. They allow for univocally and precisely referencing of concepts and are core foundation of any semantic processing of health data. In particular all electronic communication in healthcare relies on coded concepts for semantic interoperability and automated data processing. The Object Management Group's [[OMG/HL7 CTS2 Standard|Common Terminology Services Version 2 (CTS2) standard]] defines an accepted industry standard representation to share, query and maintain value sets and other terminology artifacts. '''CTS2 was the conceptual background/blueprint for the development of the terminology resource structure of FHIR'''. Therefore CTS2-LE is FHIR-enabled in order to support this standard that will be the main standard in electronic healthcare.
−
width=50
+
 
−
break=no
+
One method to achieve compliance with the structural profiles of FHIR terminologies and value sets is to use semantic web technologies that are widely used for vocabularies. In this way, artifacts such as code systems, code system elements (i.e., codes and their designations), associations and value sets (i.e., sets of code system elements) can be processed with semantic technologies. The '''CTS2 Linked Data Edition (CTS2-LE)''' terminology server provided by Fraunhofer FOKUS follows that foundation. It relies on the the [http://www.w3.org/standards/techs/rdf#w3c_all Resource Description Framework (RDF)] in conjunction with a [http://www.w3.org/TR/2014/REC-rdf-schema-20140225/ RDFS]-based schema vocabulary oriented towards the Frame Logic. So-called RDF signatures, based on this schema vocabulary, describe structural constraints according to the information model. Likewise, arbitrary object graphs can be processed and stored with these RDF signatures.
−
</inputbox>
+
 
 +
 
 +
== Overview ==
 +
This section provides an overview about CTS2-LE. It introduces the building blocks and summarizes the most important functional features.
 +
;[[CTS2-LE Fact Sheet]] (German)
 +
:The Fact Sheet provides an overview considering the implemented functionalities and additional usability related features.
 +
;[[CTS2-LE Building Blocks]]
 +
:Building blocks feature a structural compliance to the Information Model, is linked-data ready by the means of W3C RDF, and is accessible through a HL7 FHIR and REST API as well as supporting the definition, composition and import of value sets. The knowledge base functionality is implemented with RDF as the representation language providing linkage capabilities for terminological entities. This section describes the architecture and internal design.
 +
;[[CTS2-LE Interoperability]]
 +
:The system is build upon international standards and provides multiple standard interfaces for connecting to external services. This section gives an overview on the standards supported and how these can be utilized for integrating with third party products.
 +
;[[Further Information Sources for CTS2-LE]]
 +
:Fraunhofer FOKUS has published various papers and brochures about CTS2-LE in particular and terminology services in general.
 +
 
 +
== Installation, Deployment, and Setup ==
 +
This section covers the installation and initial setup of CTS-LE within an organization. The installation is performed via a deployment to a Kubernetes system. 
 +
<!--
 +
;[[Prerequisites V2|Prerequisites]]
 +
:This section describes the hardware, OS and network requirements for installing CTS2-LE.
 +
-->
 +
 
 +
;[[Installation and Setup V3|Installation, Deployment, and Setup V3]]
 +
: '''DEPRECATED'''
 +
 
 +
;[[Installation and Setup V3 (2020 versions)|Installation, Deployment, and Setup V3 (2020 versions)]]
 +
<!-- :V3 is designed to run in embedded mode (jena TDB quadstore, Lucene) and in distributed mode (Fuseki, Solr). -->
 +
: '''DEPRECATED'''
 +
 
 +
;[[Installation and Setup V3 (2021 versions)|Installation, Deployment, and Setup V3 (2021 versions)]]
 +
: '''DEPRECATED'''
 +
 
 +
;[[Installation and Setup V4 (2025)|Installation, Deployment, and Setup V4 (2025)]]
 +
:V4 (version >= 4.0.0) with full HELM and BfArM support.
 +
 
 +
;[[CTS2-LE Supported Terminologies|Supported Terminologies]]
 +
:Overview of the '''main''' standard vocabularies/versions.
 +
 
 +
<!--
 +
;[[BfArM Terminologies|BfArM Terminologies]]
 +
:Terminologies of BfArM (Bundesinstitut für Arzneimittel und Medizinprodukte).
 +
 
 +
 
 +
== Navigator ==
 +
The CTS2-LE Navigator provides a graphical user interface for online browsing. This sections describes the functionalites of the CTS2-LE Navigator and how to use these.
 +
;[[CTS2-LE Navigator: Browsing through Terminologies|Browsing through Terminologies]]
 +
:This section describes how CTS2-LE Navigator can be used for browsing through hierarchal and networked termonologies.
 +
;[[CTS2-LE Navigator: Searching for Concepts and Terms|Searching for Concepts and Terms]]
 +
:CTS2-LE allows to search for concepts and terms either with a single or within multiple terminologies. This section describes how CTS2-LE Navigator's search features can be used and configured.
 +
;[[CTS2-LE Navigator: Searching for Similar Concepts|Searching for Similar Concepts]]
 +
:Whenever a concept is selected in CTS2-LE, the Navigator can be triggered to perform a full-text search across the full terminology base to discover concepts which are similar to the selected concept. This feature can e.g. used to ease the manual definition of mappings across terminologies. This section describes how such enhanced search features can be used and configured within CTS2-LE Navigator.
 +
;[[CTS2-LE Navigator: Resolving and Displaying Value Sets|Resolving and Displaying Value Sets]]
 +
:CTS2 compliant value sets are defined as sets of references into terminologies. This section describes how such reference sets can be resolved into concept lists and how such lists can be displayed and exported in a standard format.
 +
DEFERRED
 +
;[[CTS2-LE Navigator: Managing Terminologies|Managing Terminologies and Value Sets]]
 +
:This section describes how CTS2-LE Navigator can be used for manging the lifecycle of code systems and value sets (loading, deleting, updating and versioning)
 +
;[[CTS2-LE Navigator: Semantic Full Text Classification|Semantic Full Text Classification]]
 +
:CTS2-LE allows users to upload full texts into the CTS2-LE Navigator for indexing this text with concepts from one or multiple terminologies. This section describes the resprctive user interface and how the resulting index can be used for semantic text processing.
 +
-->
 +
 
 +
== Core Web Services ==
 +
CTS2-LE provides a REST interface for integrating terminology services with custom and third-party applications. This section provides the technical specification of the REST Application Programming Interface.
 +
 
 +
 
 +
=== General ===
 +
 
 +
* [[CTS2-LE REST API: General#GET_service.2Fmanage.2Findex.2Fsuggester.2Fupdate|Suggester update]]
 +
: The suggester '''has to be updated''' whenever a code system is loaded. The suggester is used for searches within the navigation frontend.
 +
* [[CTS2-LE REST API: General#GET_service.2Fmanage.2Findex.2Fupdate|Search index update]]
 +
: Update only has to be invoked for RDF triple loading or if elements of a resource are modified via editing. The search index '''is automatically updated''' whenever a code system is loaded.
 +
* [[CTS2-LE REST API: General#GET_service.2Fcrud.2Fcts2.2Fresources|List resources]]
 +
: List all rersources (code systems, value sets, concept maps).
 +
* [[CTS2-LE REST API: General#DELETE_service.2Fcrud.2Fcts2.2Fresource|Delete resource]] by uri and version
 +
 
 +
=== FHIR R4 ===
 +
 
 +
CTS2-LE supports essential parts of the FHIR REST API for
 +
* [https://www.hl7.org/fhir/codesystem.html code systems]
 +
* [https://www.hl7.org/fhir/valueset.html value sets] and
 +
* [https://www.hl7.org/fhir/conceptmap.html concept maps]
 +
<!-- that will deprecate most of the [[#FHIR-oriented_.28deprecated.2C_use_FHIR_R4_instead.29|API below]]. -->
 +
 
 +
Not all parameters are supported, but in the context of customization for a project it will be enhanced. The following operations are supported.
 +
 
 +
The fhir base path is <code><host>/WebCts2LE/hapi-fhir</code>.
 +
 
 +
==== Resource-type-independent ====
 +
 
 +
* [https://www.hl7.org/fhir/http.html#read read]
 +
* [https://www.hl7.org/fhir/http.html#update update]
 +
* [https://www.hl7.org/fhir/http.html#delete delete] by resource id (unconditional)
 +
 
 +
==== Code Systems ====
 +
 
 +
* [https://www.hl7.org/fhir/codesystem-operation-lookup.html lookup]
 +
: supported parameters: ''code'', ''system'', ''version'', ''coding'', ''displayLanguage''
 +
* [https://www.hl7.org/fhir/codesystem-operation-validate-code.html validate-code]
 +
: supported parameters: ''url'', ''code'', ''version'', ''display'', ''coding'', ''codeableConcept'', ''displayLanguage''
 +
* [https://www.hl7.org/fhir/codesystem-operation-subsumes.html subsumes]
 +
: supported parameters: ''codeA'', ''codeB'', ''system'', ''version'', ''codingA'', ''codingB''
 +
 
 +
==== Value Sets ====
 +
 
 +
* [https://www.hl7.org/fhir/valueset-operation-expand.html expand]
 +
: supported parameters: ''url'', ''valueSetVersion'', ''includeDesignations''
 +
* [https://www.hl7.org/fhir/valueset-operation-validate-code.html validate-code]
 +
: supported parameters: ''url'', ''valueSetVersion'', ''code'', ''system'', ''systemVersion'', ''display'', ''coding'', ''codeableConcept'', ''displayLanguage''
 +
 
 +
==== Concept Maps ====
 +
 
 +
* [https://www.hl7.org/fhir/conceptmap-operation-translate.html translate]
 +
: supported parameters: ''url'', ''code'', ''system'', ''version'', ''coding'', ''codeableConcept'', ''targetsystem''
 +
 
 +
=== OWL ===
 +
 
 +
* [[CTS2-LE REST API: OWL TBOX Update|update]]
 +
For index updating and deletion see [[#General|General]]
 +
 
 +
 
 +
<!--
 +
=== FHIR-oriented ''(deprecated, use [[#FHIR_R4|FHIR R4]] instead)'' ===
 +
 
 +
;[[CTS2-LE REST API: Read Code System|Read Code System]]
 +
:reads a code system.
 +
;[[CTS2-LE REST API: Resolve Value Set MM|Resolve Value Set (multi-modal)]]
 +
:provides means to resolve and/or fetch an FHIR origined value set (or code system).
 +
;[[CTS2-LE REST API: Resolve Value Set|Resolve Complete Value Set]]
 +
:provides means to resolve and/or fetch an FHIR origined value set (or code system) which is identified by it's URI.
 +
;[[CTS2-LE REST API: Requesting Concept Details|Request Concept Details]]
 +
:used for fetching the details of a concept which is identified through a codesystem and code.
 +
;[[CTS2-LE REST API: Check Value Set Containment|Check Value Set Containment]]
 +
:allows to check wether a code (from a code system) is contained in a Value Set.
 +
;[[CTS2-LE REST API: Update Value Set|Update Value Set / Code System]]
 +
:allows to create or update a FHIR coded value set (or code system).
 +
;[[CTS2-LE REST API: Delete Value Set / Code System|Delete Value Set / Code System]]
 +
:allows to delete a FHIR coded value set (or code system).
 +
 
 +
-->
 +
 
 +
=== SPARQL ===
 +
 
 +
;[[CTS2-LE REST API: SPARQL Query|SPARQL Query]]
 +
:Due to the full RDF-encoding of all terminology artifacts, CTS2-LE allows for arbitrary queries within and across terminologies, value sets, concepts, and concept relationships. This API provides means to transmit a standard [http://www.w3.org/TR/2008/REC-rdf-sparql-query-20080115/ SPARQL query] to CTS2-LE. The query result is provided in standard [http://www.w3.org/TR/rdf-sparql-XMLres/ SPARQL Query Results XML Format].
 +
 
 +
<!--
 +
=== CTS2 REST-API ''(deprecated, use [[#FHIR_R4|FHIR R4]] instead)'' ===
 +
 
 +
Most of the API below is supported by the FHIR R4 API. FHIR is emerging as a modern standard to cover all aspects of interoperable communication between all agents (human or machine) in eHealth.
 +
 
 +
'''The below services mainly implement the standard services as specified in the documents provided by OMG/HL7. For further references (to the normative documents or XML schema files) please visit this [http://www.omg.org/spec/CTS2/1.1/ site].'''
 +
'''Please note that these services are not fully tested at this time. Hence, they are not available on any machine.'''
 +
;[[CTS2-LE REST API: Read Code Systems and Code System Versions| Read Code Systems and Code System Versions]]
 +
;[[CTS2-LE REST API: Read Entity Descriptions | Read Entity Descriptions]]
 +
;[[CTS2-LE REST API: Read Maps and Map Versions | Read Maps and Map Versions]]
 +
;[[CTS2-LE REST API: Read Value Set Definitions | Read Value Set Definitions]]
 +
 
 +
 
 +
=== Classification Markup Language (ClaML) ===
 +
;[[CTS2-LE ClaML API: Update|Update Codesystem]]
 +
;[[CTS2-LE ClaML API: Retrieve Codesystem|Retrieve Codesystem]]
 +
-->
 +
 
 +
<!--
 +
== CTS2-LE-Addon for Freeplane ==
 +
CTS2-LE provides a free plugin to the Freeplane Mindmap Editor for the interactive creation and maintenance of custom terminologies and value sets. Major features provided by this tool include:
 +
* Author offline, share later with your working group.
 +
* Author code systems hierarchically instead of in flat tables.
 +
* For value set composition, look up codes in CTS2-LE, using it’s cross terminology search.
 +
* Include codes already published on CTS2-LE in your value set without error-prone typewriting.
 +
* In the authoring view, navigate to CTS2-LE code definition page for looking up code details.
 +
 
 +
;[[Freeplane CTS2-LE Plugin: Installation|Installation and Configuration]]
 +
:This section describes how to install Freeplane with the CTS2-2 Plugin and how to configure the plugin to connect to a CTS2-LE-Server.
 +
;[[Freeplane CTS2-LE Plugin: Editing Terminologies|Creating and Editing Terminologies]]
 +
:The Freeplane CTS2-LE plugin allows to model terminologies as mind maps and to upload them to a CTS2-LE server. This section describes how to define a terminology using freeplane and how to upload or update this terminology to CTS2-LE.
 +
;[[Freeplane CTS2-LE Plugin: Editing Value Sets|Creating and Editing Value Sets]]
 +
:The Freeplane CTS2-LE plugin allows to model value sets as mind maps on top of existing terminologies and to upload these value sets to a CTS2-LE server. This section describes how to define a value sets using freeplane, how to use CTS2-LE's online concept search features for finding value set candidate concepts, and how to upload or update a value set to CTS2-LE.
 +
-->
 +
 
 +
=== Futher Services ===
 +
;[[CTS2-LE REST API: Concept Suggestion| Concept Suggestion]]
 +
:retrieve results from suggestion (plain, restricted)
 +
;[[CTS2-LE REST API: Concept Search| Concept Search]]
 +
:perform search operations (plain, restricted, similar)
 +
 
 +
<!--
 +
;[[CTS2-LE EXCEL/CSV Services: Import Value Set Catalog|EXCEL/CSV Value Set Catalog Import]]
 +
 
 +
 
 +
== CTS2-LE Terminology Loading ==
 +
CTS2-LE can be used to manage and provide any kind of flat, hierarchical, poly-hierarchical or even networked terminology. To ease the integration of widely used terminologies into CTS2-LE Fraunhofer FOKUS provides various loaders for standard import formats and dedicated terminologies.
 +
Loading terminologies and value sets is achieved by applying one of the following modes:
 +
# an ''online'' mode which allows to integrate resources into a running CTS2-LE server instance and
 +
# an ''offline'' mode which integrates resources into a shut down CTS2-LE server instance.
 +
 
 +
Choosing one of these options is not arbitrary but dependent on the provided format. In order to load terminologies on the fly, they have to be structured according to the '''FHIR value set definition'''. These files can then be integrated by means of the CTS2-LE [[Hauptseite#CTS2-LE_REST-API|REST-API]], For any other representation of a terminology, a specific loader has to be prepared.
 +
 
 +
;[[CTS2-LE Loading Core Terminologies]]
 +
:CTS2-LE provides standard interfaces for importing terminologies and value sets. While some terminologies are distributed in such standard formats <!(e.g. ICD-10 is provided by WHO in ClaML format)>, many widely used terminologies are only available in a proprietary format and therefore need specific loaders that map this proprietary format onto the CTS2 data model. This section lists all terminologies which are recently supported by CTS2-LE together with information on how to obtain and import each terminology.
 +
 
 +
;[[CTS2-LE Loader: FHIR|CTS2-LE FHIR Loader]]
 +
:HL7 FHIR provides a standard format for encoding value sets and terminologies. The CTS2-LE FHIR Loader allows to upload terminology resources to CTS2-LE using the standard FHIR value set resource definiton. In order to integrate a value set or terminology the usage of our [[CTS2-LE REST API: Update Value Set|FHIR REST API]] is recommended.
 +
 
 +
<![[CTS2-LE Loader: ClaML|CTS2-LE ClaML Loader]]
 +
:''(Franziska)''
 +
:The ISO 13102 Classification Markup Language (ClaML) standard is a common format for sharing terminologies. It is e.g. used by WHO for their ICD-10 distribution. The CTS2-LE ClaML Loader described in this section allows to upload ClaML encoded terminology resources to CTS2-LE.>
 +
 
 +
CTS2-LE can be used to manage and provide any kind of flat, hierarchical, poly-hierarchical or even networked terminology. To ease the integration of widely used terminologies into CTS2-LE Fraunhofer FOKUS provides various loaders for dedicated terminologies. These loaders always perform a mapping onto the CTS2 information model. The following links provide information on the general approach as well as on decicated mappings of certain terminologies.
 +
 
 +
;[[Mapping Terminologies to CTS2-LE]]
 +
<! ;[[Loading Terminologies into CTS2-LE|Mapping Terminologies to CTS2-LE]] >
 +
:This section describes the general approach for mapping a standard terminology to CTS2-LE.
 +
<! :Example: [[Mapping and Loading epSOS Terminologies]] >
 +
;Proprietary CTS2-LE Terminology Loaders
 +
:Please see the list below for links to descriptions of CTS2-LE loaders for terminologies which are not available in FHIR format. The description of each loader includes information on the loader's input and output format together with a description on how to use the loader to import a terminology into CTS2-LE.
 +
:* [[CTS2-LE SNOMED-CT Loader|Systematized Nomenclature of Human and Veterinary Medicine - Clinical Terms (SNOMED-CT)]]
 +
:* [[CTS2-LE LOINC Loader|Logical Observation Identifiers Names and Codes (LOINC)]]
 +
:* [[CTS2-LE MeSH Loader|Medical Subject Headings (MeSH)]]
 +
:* [[CTS2-LE Alpha-ID Loader|Alpha-ID]]
 +
:* Anatomical Therapeutic Chemical Classification (ATC) [[CTS2-LE ATC-DDD Loader|Defined Daily Dose (DDD) und Darreichungsformen]]
 +
<!
 +
:* [[CTS2-LE HL7v3 Loader|HL7v3 Terminologien]] ''(- - > Andreas)''
 +
>
 +
:* [[CTS2-LE ICD-10 Loader|International Statistical Classification of Diseases and Related Health Problems Revision 10 (ICD-10)]]
 +
:* [[CTS2-LE OPS Loader|Operationen- und Prozedurenschlüssel (OPS)]]
 +
:* [[CTS2-LE UCUM Loader|Unified Code for Units of Measure (UCUM)]]
 +
:* [[CTS2-LE KTL Loader|Klassifikation therapeutischer Leistungen in der medizinischen Rehabilitation (KTL)]]
 +
-->
 +
 
 +
== Navigator ==
 +
 
 +
;[[Grouping|Grouping]]
 +
:Grouping of terminologies in the navigator
 +
 
 +
<!--
 +
== Solution Management ==
 +
;[[Licence and Availability Notes|CTS2-LE Licensing]]
 +
:CTS2-LE is distributed by Fraunhofer FOKUS under a commercial license. This section provides information about the licensing terms and conditions for various CTS2-LE usage scenarios.
 +
 
 +
;[[CTS2-LE Release Management]]
 +
:Fraunhofer FOKUS is continuosly maintaining and further developing CTS2-LE. This section gives insight into the CTS2-LE development roadmap by sketching CTS2-LE add-ons and improvements which are under development at Fraunhofer FOKUS.
 +
-->
 +
 
 +
<!--
 +
;[[CTS2-LE Wish List]]
 +
:You have an idea for a cool new feature for CTS2-LE? There is some interface you desperately need for your terminology consuming solution? You have discovered a useful terminology that should be distributed through the public CTS2-LE?  The CTS2-LE Wish List summarizes all ideas for new CTS2-LE featurs and acts as a major input to the CTS2-LE development roadmap.
 +
-->

Aktuelle Version vom 8. Januar 2026, 14:31 Uhr


Controlled vocabularies (also known as code systems or terminologies) are common information artefacts in healthcare. They allow for univocally and precisely referencing of concepts and are core foundation of any semantic processing of health data. In particular all electronic communication in healthcare relies on coded concepts for semantic interoperability and automated data processing. The Object Management Group's Common Terminology Services Version 2 (CTS2) standard defines an accepted industry standard representation to share, query and maintain value sets and other terminology artifacts. CTS2 was the conceptual background/blueprint for the development of the terminology resource structure of FHIR. Therefore CTS2-LE is FHIR-enabled in order to support this standard that will be the main standard in electronic healthcare.

One method to achieve compliance with the structural profiles of FHIR terminologies and value sets is to use semantic web technologies that are widely used for vocabularies. In this way, artifacts such as code systems, code system elements (i.e., codes and their designations), associations and value sets (i.e., sets of code system elements) can be processed with semantic technologies. The CTS2 Linked Data Edition (CTS2-LE) terminology server provided by Fraunhofer FOKUS follows that foundation. It relies on the the Resource Description Framework (RDF) in conjunction with a RDFS-based schema vocabulary oriented towards the Frame Logic. So-called RDF signatures, based on this schema vocabulary, describe structural constraints according to the information model. Likewise, arbitrary object graphs can be processed and stored with these RDF signatures.


Overview

This section provides an overview about CTS2-LE. It introduces the building blocks and summarizes the most important functional features.

CTS2-LE Fact Sheet (German)
The Fact Sheet provides an overview considering the implemented functionalities and additional usability related features.
CTS2-LE Building Blocks
Building blocks feature a structural compliance to the Information Model, is linked-data ready by the means of W3C RDF, and is accessible through a HL7 FHIR and REST API as well as supporting the definition, composition and import of value sets. The knowledge base functionality is implemented with RDF as the representation language providing linkage capabilities for terminological entities. This section describes the architecture and internal design.
CTS2-LE Interoperability
The system is build upon international standards and provides multiple standard interfaces for connecting to external services. This section gives an overview on the standards supported and how these can be utilized for integrating with third party products.
Further Information Sources for CTS2-LE
Fraunhofer FOKUS has published various papers and brochures about CTS2-LE in particular and terminology services in general.

Installation, Deployment, and Setup

This section covers the installation and initial setup of CTS-LE within an organization. The installation is performed via a deployment to a Kubernetes system.

Installation, Deployment, and Setup V3
DEPRECATED
Installation, Deployment, and Setup V3 (2020 versions)
DEPRECATED
Installation, Deployment, and Setup V3 (2021 versions)
DEPRECATED
Installation, Deployment, and Setup V4 (2025)
V4 (version >= 4.0.0) with full HELM and BfArM support.
Supported Terminologies
Overview of the main standard vocabularies/versions.


Core Web Services

CTS2-LE provides a REST interface for integrating terminology services with custom and third-party applications. This section provides the technical specification of the REST Application Programming Interface.


General

The suggester has to be updated whenever a code system is loaded. The suggester is used for searches within the navigation frontend.
Update only has to be invoked for RDF triple loading or if elements of a resource are modified via editing. The search index is automatically updated whenever a code system is loaded.
List all rersources (code systems, value sets, concept maps).

FHIR R4

CTS2-LE supports essential parts of the FHIR REST API for

Not all parameters are supported, but in the context of customization for a project it will be enhanced. The following operations are supported.

The fhir base path is <host>/WebCts2LE/hapi-fhir.

Resource-type-independent

Code Systems

supported parameters: code, system, version, coding, displayLanguage
supported parameters: url, code, version, display, coding, codeableConcept, displayLanguage
supported parameters: codeA, codeB, system, version, codingA, codingB

Value Sets

supported parameters: url, valueSetVersion, includeDesignations
supported parameters: url, valueSetVersion, code, system, systemVersion, display, coding, codeableConcept, displayLanguage

Concept Maps

supported parameters: url, code, system, version, coding, codeableConcept, targetsystem

OWL

For index updating and deletion see General


SPARQL

SPARQL Query
Due to the full RDF-encoding of all terminology artifacts, CTS2-LE allows for arbitrary queries within and across terminologies, value sets, concepts, and concept relationships. This API provides means to transmit a standard SPARQL query to CTS2-LE. The query result is provided in standard SPARQL Query Results XML Format.


Futher Services

Concept Suggestion
retrieve results from suggestion (plain, restricted)
Concept Search
perform search operations (plain, restricted, similar)


Navigator

Grouping
Grouping of terminologies in the navigator


Abgerufen von „https://websites.fraunhofer.de/CTS2-LE/index.php?title=Hauptseite&oldid=1387“