Mapping Terminologies to CTS2-LE: Unterschied zwischen den Versionen
Billig (Diskussion | Beiträge) (Die Seite wurde neu angelegt: „The process of loading basically comprises the mapping of terminological contents to the elements defined within the CTS2-standard. This section outlines a gen…“) |
Krebs (Diskussion | Beiträge) K (→Defining code systems, code system version, value sets and value set version) |
||
| Zeile 34: | Zeile 34: | ||
* note, that the value set portion is strongly aligned to the [http://www.hl7.org/implement/standards/fhir/ FHIR standard] but with most possible compliance to CTS2 | * note, that the value set portion is strongly aligned to the [http://www.hl7.org/implement/standards/fhir/ FHIR standard] but with most possible compliance to CTS2 | ||
|- | |- | ||
| − | | value set | + | | value set entry || ValueSetDefinitionEntry || |
* references a concept | * references a concept | ||
|} | |} | ||
Version vom 21. Juli 2015, 13:31 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 |
|