Mapping Editor - Versionsgeschichte

Krebs am 11. Februar 2016 um 14:43 Uhr

2016-02-11T14:43:15Z

Krebs am 11. Februar 2016 um 14:21 Uhr

2016-02-11T14:21:47Z

Krebs am 11. Februar 2016 um 12:57 Uhr

2016-02-11T12:57:25Z

Krebs am 11. Februar 2016 um 12:55 Uhr

2016-02-11T12:55:54Z

Krebs am 11. Februar 2016 um 12:07 Uhr

2016-02-11T12:07:53Z

Krebs am 10. Februar 2016 um 08:46 Uhr

2016-02-10T08:46:40Z

Krebs am 10. Februar 2016 um 08:31 Uhr

2016-02-10T08:31:31Z

Krebs am 10. Februar 2016 um 07:59 Uhr

2016-02-10T07:59:10Z

Krebs am 10. Februar 2016 um 07:56 Uhr

2016-02-10T07:56:19Z

Krebs: Schützte „Mapping Editor“ ([Verschieben=Nur automatisch bestätigten Benutzern erlauben] (unbeschränkt) [Read=Nur automatisch bestätigten Benutzern erlauben] (unbeschränkt))

2016-02-09T08:34:54Z

Schützte „Mapping Editor“ ([Verschieben=Nur automatisch bestätigten Benutzern erlauben] (unbeschränkt) [Read=Nur automatisch bestätigten Benutzern erlauben] (unbeschränkt))

@@ Zeile 54: / Zeile 54: @@
 ** product
 * Enabling bidirectional mappings on the fly would result in building a new mapping (since source and target resources are switched consequently). This may cause semantic inconsistencies because FHIR does not specify reverse correlations (e.g. reverse(wider) == narrower?). From a technological point of view metadata of the new mapping (identifier, url, name..) would have to be generated automatically and without any authorization.
 * [to be discussed] An "active" mapping should not be modified anymore since it may already be in a productive use.
 * [to be discussed] FHIR provides 9 equivalence relations that are arranged in a two-level hierarchy. CTS2 represents these codes in their meta-model which does not consider a hierarchical structure.
@@ Zeile 60: / Zeile 61: @@
 == Technical Implementation ==
-The application will be created with AngularJS (version 1.3.15) and UI bootstrap components (0.13.1) written in AngularJS. As of 10.02.16, the mapping editor has not been made available.
+The application will be created with AngularJS (version 1.3.15) and UI bootstrap components (0.13.1) written in AngularJS. As of 10.02.16, the mapping editor has not been made available. <br />
 Ideas:
 * use drag&drop to allocate source and target mapping entries

@@ Zeile 37: / Zeile 37: @@
 | element.target.equivalence [code] || MapVersion.entry.target.correlation || only codes from the FHIR ConceptMapEquivalence value set can be used; acc. to FHIR "The equivalence is read from target to source (e.g. the target is 'wider' than the source)."
 |-
-| element.target.comments || ???? ||
+| element.target.comments || MapVersion.entry.target.comments ||
 |-
 |}

@@ Zeile 64: / Zeile 64: @@
 * use drag&drop to allocate source and target mapping entries
 * use URL blocking to prevent unauthorized users from executing create, modify or delete operations.
 <references/>

@@ Zeile 53: / Zeile 53: @@
 ** dependsOn
 ** product
-* Enabling bidirectional mappings on the fly would result in building a new mapping (since source and target are switched consequently). This may cause semantic inconsistencies because FHIR does not specify reverse correlations (e.g. reverse(wider) == narrower?). From a technological point of view metadata of the new mapping (identifier, url, name..) would have to be generated automatically and without any authorization.
+* Enabling bidirectional mappings on the fly would result in building a new mapping (since source and target resources are switched consequently). This may cause semantic inconsistencies because FHIR does not specify reverse correlations (e.g. reverse(wider) == narrower?). From a technological point of view metadata of the new mapping (identifier, url, name..) would have to be generated automatically and without any authorization.
 * [to be discussed] An "active" mapping should not be modified anymore since it may already be in a productive use.
 * [to be discussed] FHIR provides 9 equivalence relations that are arranged in a two-level hierarchy. CTS2 represents these codes in their meta-model which does not consider a hierarchical structure.
@@ Zeile 62: / Zeile 63: @@
 Ideas:
 * use drag&drop to allocate source and target mapping entries
+* use URL blocking to prevent unauthorized users from executing create, modify or delete operations.
 <references/>

@@ Zeile 10: / Zeile 10: @@
 |-
 | url [uri] || MapVersion.aboutUri, MapVersion.alternateAboutUri || uniqueness within the server instance in wich the mapping is stored is guaranteed
 |-
 | version [string] || MapVersion.versionID ||
@@ Zeile 18: / Zeile 16: @@
 |-
 | status [code] || ResourceDescription.status || only codes from the FHIR ConformanceResourceStatus value set can be used
 |-
 | description [string] || MapVersion.note ||
 |-
-| useContext [Codeable Concept] || - ||
+| sourceUri [uri] || MapVersion.source.aboutUri || should be equal to element.codeSystem; according to FHIR "Should be a version specific reference. URIs SHOULD be absolute."
 |-
-| copyright || - ||
+| targetUri [uri] || MapVersion.target.aboutUri || should be equal to element.target.codeSystem; according to FHIR "Should be a version specific reference. URIs SHOULD be absolute."
 |-
 | element || MapVersion.entry ||
@@ Zeile 51: / Zeile 35: @@
 | element.target.code [code] || MapVersion.entry.target.name ||
 |-
-| element.target.equivalence [code] || MapVersion.entry.target.correlation || only codes from the FHIR ConceptMapEquivalence value set can be used
+| element.target.equivalence [code] || MapVersion.entry.target.correlation || only codes from the FHIR ConceptMapEquivalence value set can be used; acc. to FHIR "The equivalence is read from target to source (e.g. the target is 'wider' than the source)."
 |-
 | element.target.comments || ???? ||
 |-
 |}
-The following constraints and limitations have been formulated or noticed:
+The following constraints and limitations have been formulated or noticed:<br />
 * There are a couple of FHIR elements that are currently not represented by means of CTS2, among these are
 == Technical Implementation ==
 The application will be created with AngularJS (version 1.3.15) and UI bootstrap components (0.13.1) written in AngularJS. As of 10.02.16, the mapping editor has not been made available.
+Ideas:
 <references/>

@@ Zeile 3: / Zeile 3: @@
 == FHIR Concept Map ==
 The conceptual background is given by means of the FHIR ConceptMap - which defines a mapping as a "statement of relationships from one set of concepts to one or more other concepts - either code systems or data elements, or classes in class models."<ref>http://www.hl7.org/FHIR/conceptmap.html FHIR Concept Map v1.0.2</ref>
-In order to represent a mapping that is conformant to both the CTS2- and the FHIR specification, a transformation between the given meta-models is necessary. The following table outlines how FHIR ConceptMap elements are represented by CTS2 elements.
+In order to represent a mapping that is conformant to both the CTS2- and the FHIR specification, a transformation between the given meta-models is necessary. The following table outlines how FHIR ConceptMap elements are represented by [[Mapping Terminologies to CTS2-LE|CTS2 elements]].
 {| class="wikitable"
@@ Zeile 61: / Zeile 61: @@
 |}
 == Technical Implementation ==

← Nächstältere Version		Version vom 10. Februar 2016, 07:56 Uhr
Zeile 1:		Zeile 1:
	CTS2-LE provides a web interface that enables a user to create, update or delete a mapping. This section describes both the conceptual background and technical aspects concerning this mapping editor.		CTS2-LE provides a web interface that enables a user to create, update or delete a mapping. This section describes both the conceptual background and technical aspects concerning this mapping editor.
		+
		+	== FHIR Concept Map ==
		+	The conceptual background is given by means of the FHIR ConceptMap - which defines a mapping as a "statement of relationships from one set of concepts to one or more other concepts - either code systems or data elements, or classes in class models."<ref>http://www.hl7.org/FHIR/conceptmap.html FHIR Concept Map v1.0.2</ref>
		+	In order to represent a mapping that is conformant to both the CTS2- and the FHIR specification, a transformation between the given meta-models is necessary.
		+
		+
		+	== Technical Implementation ==
		+
		+
		+	<references/>

← Nächstältere Version	Version vom 9. Februar 2016, 08:34 Uhr
(kein Unterschied)