CTS2-LE Interoperability - Versionsgeschichte

Billig am 18. Januar 2022 um 16:58 Uhr

2022-01-18T16:58:09Z

Billig: /* CTS2 */

2020-12-16T10:20:22Z

‎CTS2

Billig: /* HL7 FHIR */

2020-09-04T12:26:29Z

‎HL7 FHIR

Billig: /* RDF */

2020-09-04T12:24:56Z

‎RDF

Billig: /* CTS2 */

2020-09-04T12:23:58Z

‎CTS2

Caumanns: /* HL7 FHIR */

2015-06-11T08:26:49Z

‎HL7 FHIR

Caumanns am 11. Juni 2015 um 07:47 Uhr

2015-06-11T07:47:12Z

Caumanns am 11. Juni 2015 um 07:08 Uhr

2015-06-11T07:08:47Z

Caumanns: /* RDF */

2015-06-05T13:22:00Z

‎RDF

Caumanns: /* CTS2 */

2015-06-05T13:06:06Z

‎CTS2

@@ Zeile 7: / Zeile 7: @@
 * [[#HL7 FHIR|Fast Healthcare Interoperability Resources (FHIR)]]: CTS2-LE external terminology exchange format
 == CTS2 ==
 The Common Terminology Services Version 2 is a joint standardization effort from HL7 and OMG. The objective was to provide a standardized model for all terminological resources. CTS2 served as a blueprint for CTS2-LE in order to support a wide range of applications.
 While HL7 defined the functional model for managing terminology artifacts, OMG mapped this abstract model onto a concrete information model and service interfaces, which again can be bound to various standards (e.g. SOAP, REST, RDF). Even though CTS2 was developed with healthcare use cases in mind, it can as well be used for managing and distributing terminology resources from other domains.
 -->
@@ Zeile 51: / Zeile 58: @@
 === Interoperability with 3rd-Party Solutions ===
 Third-Party-Solutions have full access to the complete CTS2-LE terminology base through the [[CTS2-LE REST API: SPARQL Query|CTS2-LE SPARQL REST API]]. Queries must comply to the [http://semantik.fokus.fraunhofer.de/WebCts2LE/main3/systemData.jsp CTS2-LE CTS2 RDF-Binding].
 <!--

@@ Zeile 8: / Zeile 8: @@
 == CTS2 ==
-The Common Terminology Services Version 2 is a joint standardization effort from HL7 and OMG. The objective was to provide a model and specification for discovering, accessing, distributing and updating terminological resources. CTS2 served as a blueprint for CTS2-LE in order to support a wide range of applications.
+The Common Terminology Services Version 2 is a joint standardization effort from HL7 and OMG. The objective was to provide a standardized model for all terminological resources. CTS2 served as a blueprint for CTS2-LE in order to support a wide range of applications.
 <!--

@@ Zeile 58: / Zeile 58: @@
 * [http://www.fhirabend.de/ German FHIR Blog] von Simone Heckmann
 === Use of HL7 FHIR in CTS2-LE ===
 CTS2-LE uses the [http://www.hl7.org/fhir/valueset.html FHIR value set resource definiton] as its standard format for externalizing terminologies and value sets. In particular terminology artifacts can be uploaded and retrieved using this standard.
@@ Zeile 68: / Zeile 69: @@
 An example for using these APIs in conjunction with web forms can be found [[CTS2-LE REST API Example: Loading a Value Set into a HTML Form DropDown-Box|here]].

@@ Zeile 26: / Zeile 26: @@
 == RDF ==
-Modern semantic (web) technologies have its root in mature knowledge representation (KR) methods and techniques. They can be seen as a “Webification” of KR languages such as the Frame Language and Description Logics (DL). In fact, the Resource Description Language (RDF) standard can be considered as a simple frame language as well as a language for semantic nets and OWL has its direct foundation in a certain DL dialect. The semantics of these languages are the theoretical backbone of controlled vocabularies and are widely used to define concrete vocabularies. For instance, SNOMED-CT has the expressivity of the OWL EL++ dialect and even LOINC can be proper represented and processed by means of DL.
+Modern semantic (web) technologies have its root in mature knowledge representation (KR) methods and techniques. They can be seen as a “Webification” of KR languages such as the Frame Language and Description Logics (DL). In fact, the Resource Description Language (RDF) standard can be considered as a simple frame language as well as a language for semantic nets and OWL has its direct foundation in a certain DL dialect. The semantics of these languages are the theoretical backbone of controlled vocabularies and are widely used to define concrete vocabularies. For instance, SNOMED-CT has the expressivity of the OWL EL++ dialect
 Another important aspect is the utilization of RDF for storing and querying linked (big) data. So far many RDF stores (Jena TDB, Virtuoso, etc.) are available and able to hold data in the range of several hundred million triples. Compared to object stores and assuming an average number of 10 object attributes, one can easily store and retrieve several million objects. These capabilities gives CTS2-LE the opportunity to “weave” instance nets for arbitrary medical data objects together with referenced vocabularies.
@@ Zeile 37: / Zeile 39: @@
 By default the CTS2-LE distribution uses [https://jena.apache.org/documentation/tdb/ Jena TDB] for storing terminology data. This component can easily be exchanged by any other triple store solution (e.g. [http://virtuoso.openlinksw.com/ Virtuoso]).
 == SPARQL ==

@@ Zeile 8: / Zeile 8: @@
 == CTS2 ==
-The Common Terminology Services Version 2 is a joint standardization effort from HL7 and OMG. The objective was to provide a model and specification for discovering, accessing, distributing and updating terminological resources. While HL7 defined the functional model for managing terminology artifacts, OMG mapped this abstract model onto a concrete information model and service interfaces, which again can be bound to various standards (e.g. SOAP, REST, RDF). Even though CTS2 was developed with healthcare use cases in mind, it can as well be used for managing and distributing terminology resources from other domains.
+The Common Terminology Services Version 2 is a joint standardization effort from HL7 and OMG. The objective was to provide a model and specification for discovering, accessing, distributing and updating terminological resources. CTS2 served as a blueprint for CTS2-LE in order to support a wide range of applications.
 For further information on CTS2 see:
 * [http://www.omg.org/spec/CTS2/ OMG CTS2 Homepage] (contains links to all published versions of the CTS2 standard)
 * [http://de.slideshare.net/cts2/cts2-introduction Introduction to CTS2] (Presentation from Harold Solbrig, Mayo Clinic)
@@ Zeile 19: / Zeile 23: @@
 === Interoperability with 3rd-Party Solutions ===
 CTS2-LE can manage any semantic resource that complies to the CTS2 functional model. This not only includes terminologies but even networked ontologies and structured knowledge bases. Owners of such semantic resources can easily load these into CTS2-LE and by this utilize the standard SPARQL and REST interfaces of CTS2-LE to provide users access to these resources.
 == RDF ==

@@ Zeile 48: / Zeile 48: @@
 * [http://www.hl7.org/fhir/ HL7 FHIR homepage] with links to the full FHIR documentation and the [http://www.hl7.org/fhir/resourcelist.html FHIR catalogue of standard resource definitions]
 * [http://hl7.de/themen/hl7-fhir-standard-fuer-mobile-kommunikation/ Introduction to FHIR] (German)
-* [http://www.fhirabend.de/ German FHIR Blog] (Simone Heckmann)
+* [http://www.fhirabend.de/ German FHIR Blog] von Simone Heckmann
 === Use of HL7 FHIR in CTS2-LE ===
 === Interoperability with 3rd-Party Solutions ===

← Nächstältere Version		Version vom 11. Juni 2015, 07:08 Uhr
Zeile 1:		Zeile 1:
		+	__NOTOC__
		+
		+	This section describes the set of standards that provide solution developers with standard interfaces for extending the functionality of CTS2-LE and for utilizing CTS2-LE terminology services within their own solutions:
		+	* [[#CTS2\|Common Terminology Services (CTS2)]]: CTS2-LE functional model
		+	* [[#RDF\|Resource Description Framework (RDF)]]: CTS2-LE internal terminology data format
		+	* [[#SPARQL\|SPARQL Protocol And RDF Query Language (SPARQL)]]: CTS2-LE terminology query language
		+	* [[#HL7 FHIR\|Fast Healthcare Interoperability Resources (FHIR)]]: CTS2-LE external terminology exchange format

	== CTS2 ==		== CTS2 ==

@@ Zeile 9: / Zeile 9: @@
 === Use of CTS2 in CTS2-LE ===
-CTS2-LE's internal data model is an RDF-Binding to version 1.0 of the CTS2 standard. By this CTS2-LE supports all terminology resources defined in the CTS2 standard and follows the CTS2 service functional model for discovering and sharing these resources.
+CTS2-LE's internal data model is an RDF-Binding to version 1.0 of the CTS2 standard. By this CTS2-LE supports all terminology resources defined in the CTS2 standard and follows the CTS2 service functional model for discovering and sharing these resources. The full RDF mapping onto the CTS2 model can be found [http://semantik.fokus.fraunhofer.de/WebCts2LE/main3/systemData.jsp here].
 === Interoperability with 3rd-Party Solutions ===
+CTS2-LE can manage any semantic resource that complies to the CTS2 functional model. This not only includes terminologies but even networked ontologies and structured knowledge bases. Owners of such semantic resources can easily load these into CTS2-LE and by this utilize the standard SPARQL and REST interfaces of CTS2-LE to provide users access to these resources.
 == RDF ==