Mapping Terminologies to CTS2-LE: Unterschied zwischen den Versionen
Krebs (Diskussion | Beiträge) K |
Billig (Diskussion | Beiträge) (→Defining associations) |
||
| (Eine dazwischenliegende Version von einem anderen Benutzer wird nicht angezeigt) | |||
| Zeile 48: | Zeile 48: | ||
|- | |- | ||
| concept || ClassDescription || | | concept || ClassDescription || | ||
| − | * elements of a code system | + | * elements of a code system version |
* the attribute ''name'' is the concept's code | * the attribute ''name'' is the concept's code | ||
|- | |- | ||
| Zeile 81: | Zeile 81: | ||
* the attribute ''subject'' references a concept (''ClassDescription'') | * the attribute ''subject'' references a concept (''ClassDescription'') | ||
* the attribute ''predicate'' references a ''PredicateDescription'' (just like a ''ClassDescription'' represents a concept, a ''PredicateDescription'' represents a relation, such as subClassOf) | * the attribute ''predicate'' references a ''PredicateDescription'' (just like a ''ClassDescription'' represents a concept, a ''PredicateDescription'' represents a relation, such as subClassOf) | ||
| − | * the attribute ''target'' either references a | + | * the attribute ''target'' either references a concept via the identificator (code system uri, version, code) or a literal |
* the attribute ''deviation'' is used to indicate that an association has been added manually (''ASSERTED'') or that is was derived automatically (''INFERRED'') | * the attribute ''deviation'' is used to indicate that an association has been added manually (''ASSERTED'') or that is was derived automatically (''INFERRED'') | ||
|- | |- | ||
|} | |} | ||
Aktuelle Version vom 25. März 2019, 14:49 Uhr
The process of loading basically comprises the mapping of terminological contents to the elements defined within the CTS2-standard. This section outlines a generic method for mapping terminological resources to the entities of the CTS2-information model. In most cases, there will be a need for fine adjustment depending on structural and semantical features of a code system/value set.
The below figure shows the underlying model which is aligned to a slightly modified subset of the original CTS2 information model. To increase the readability of the diagram, a dashed line is used for generalization. Furthermore, the usual EBNF notation was used for UML-multiplicity, so
- ? stands for 0..1
- * stands for 0..*
- + stands for 1..*
For the sake of clarity, not all elements will be described in detail. Instead, we define 3 levels when representing a terminology resource by means of CTS2-LE:
- code systems, code system version, value sets and value set version
- concepts, along with synonyms, definitions, notes, etc.
- associations between concepts
The following tables outline the mapping and provide information regarding the intended usage of the elements. It is recommended to have the above diagram in mind when studying the tables, since it outlines the overall structure and thus shows how entities and attributes are connected.
Defining code systems, code system version, value sets and value set version
| Terminological element | CTS2 mapping | Scope |
|---|---|---|
| code system and code system version | CodeSystemVersionCatalogEntry |
|
| value set and value set version | ValueSetDefinition |
|
| value set entry | ValueSetDefinitionEntry |
|
Defining concepts and designations
| Terminological element | CTS2 mapping | Scope |
|---|---|---|
| concept | ClassDescription |
|
| terms, concept naming | Designation |
|
| preferred term | PreferredTerm |
|
| explanations and similar | Definition |
|
| notes | Note |
|
Defining associations
| Terminological element | CTS2 mapping | Scope |
|---|---|---|
| association | Association |
|