Mapping Editor: Unterschied zwischen den Versionen
Krebs (Diskussion | Beiträge) K |
Krebs (Diskussion | Beiträge) K |
||
| Zeile 3: | Zeile 3: | ||
== FHIR Concept Map == | == 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> | 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" | {| class="wikitable" | ||
| Zeile 61: | Zeile 61: | ||
|} | |} | ||
| + | The following constraints and limitations have been formulated or noticed: | ||
| + | * There are a couple of FHIR elements that are currently not represented by means of CTS2, among these are | ||
== Technical Implementation == | == Technical Implementation == | ||
Version vom 10. Februar 2016, 10:46 Uhr
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."[1] 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.
| FHIR element [datatype] | CTS2 mapping | Notes |
|---|---|---|
| url [uri] | MapVersion.aboutUri, MapVersion.alternateAboutUri | uniqueness within the server instance in wich the mapping is stored is guaranteed |
| identifier [identifier] | - | |
| version [string] | MapVersion.versionID | |
| name [string] | MapVersion.resourceID | uniqueness within the server instance in wich the mapping is stored is guaranteed |
| status [code] | ResourceDescription.status | only codes from the FHIR ConformanceResourceStatus value set can be used |
| experimental | - | |
| publisher | - | |
| contact | - | |
| date | - | |
| description [string] | MapVersion.note | |
| useContext [Codeable Concept] | - | |
| requirements | - | |
| copyright | - | |
| sourceUri [uri] | MapVersion.source.aboutUri | should be equal to element.codeSystem |
| targetUri [uri] | MapVersion.target.aboutUri | should be equal to element.target.codeSystem |
| element | MapVersion.entry | |
| element.codeSystem [uri] | MapVersion.entry.aboutUri | should be equal to sourceUri |
| element.code [code] | MapVersion.entry.name | |
| element.target | MapVersion.entry.target | |
| element.target.codeSystem [uri] | MapVersion.entry.target.aboutUri | should be equal to targetUri |
| 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.comments | ???? | |
| element.target.dependsOn | - | |
| element.target.product | - |
The following constraints and limitations have been formulated or noticed:
- 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.
- ↑ http://www.hl7.org/FHIR/conceptmap.html FHIR Concept Map v1.0.2