MedTechLabel WP2 T1.1 Information Model Guide
0.4.3 - ci-build
MedTechLabel WP2 T1.1 Information Model Guide
0.4.3 - ci-build
MedTechLabel WP2 T1.1 Information Model Guide, published by HL7 Europe. This guide is not an authorized publication; it is the continuous build for version 0.4.3 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/hl7-eu/medtechlabel-wp2-im/ and changes regularly. See the Directory of published versions
| Active as of 2026-09-29 |
<CodeSystem xmlns="http://hl7.org/fhir">
<id value="Relationship"/>
<text>
<status value="generated"/>
<div xmlns="http://www.w3.org/1999/xhtml"><p class="res-header-id"><b>Generated Narrative: CodeSystem Relationship</b></p><a name="Relationship"> </a><a name="hcRelationship"> </a><p>This case-sensitive code system <code>http://www.hl7europe.org/medtechlabel/CodeSystem/Relationship</code> defines the following codes in a Is-A hierarchy:</p><table class="codes"><tr><td style="white-space:nowrap"><b>Code</b></td><td><b>Display</b></td><td><b>Definition</b></td></tr><tr><td style="white-space:nowrap">derivedFrom<a name="Relationship-derivedFrom"> </a></td><td>derived from</td><td>data element from which it is derived</td></tr><tr><td style="white-space:nowrap">supportedBy<a name="Relationship-supportedBy"> </a></td><td>supported by</td><td>the source is supported by the target item in some way</td></tr><tr><td style="white-space:nowrap">addresses<a name="Relationship-addresses"> </a></td><td>addresses</td><td>what issue is solved, and how?</td></tr><tr><td style="white-space:nowrap">hasComponent<a name="Relationship-hasComponent"> </a></td><td>has component</td><td>reference to parts of the source item; reverse of partOf</td></tr><tr><td style="white-space:nowrap">appliesTo<a name="Relationship-appliesTo"> </a></td><td>applies to</td><td>the source applies to the target</td></tr><tr><td style="white-space:nowrap">constrains<a name="Relationship-constrains"> </a></td><td>constrains</td><td>the source constrains the target element</td></tr><tr><td style="white-space:nowrap">conformsTo<a name="Relationship-conformsTo"> </a></td><td>conforms to</td><td>is conformant to certain regularities</td></tr><tr><td style="white-space:nowrap">mapsTo<a name="Relationship-mapsTo"> </a></td><td>maps to</td><td>maps to</td></tr><tr><td style="white-space:nowrap">equivalentTo<a name="Relationship-equivalentTo"> </a></td><td>equivalent to</td><td>the source concept is equivalent to the target concept</td></tr><tr><td style="white-space:nowrap">broaderThan<a name="Relationship-broaderThan"> </a></td><td>broader than</td><td>the source concept is broader, i.e. more general, in its meaning than the equivalent to the target concept</td></tr><tr><td style="white-space:nowrap">narrowerThan<a name="Relationship-narrowerThan"> </a></td><td>narrower than</td><td>the source concept is narrower, i.e. more specialized, in its meaning than the to the target concept</td></tr><tr><td style="white-space:nowrap">overlapsWith<a name="Relationship-overlapsWith"> </a></td><td>overlaps with</td><td>the source concept overlaps in the meaning with the target concept</td></tr><tr><td style="white-space:nowrap">conflictsWith<a name="Relationship-conflictsWith"> </a></td><td>conflicts with</td><td>the source concept is in conflict with the target concept</td></tr><tr><td style="white-space:nowrap">supersedes<a name="Relationship-supersedes"> </a></td><td>supersedes</td><td>supersedes</td></tr><tr><td style="white-space:nowrap">hasFormat<a name="Relationship-hasFormat"> </a></td><td>has format</td><td>the provided information has to fulfill certain representation formats</td></tr><tr><td style="white-space:nowrap">hasValue<a name="Relationship-hasValue"> </a></td><td>has Value</td><td>a specific data element must (or can) have a certain value</td></tr><tr><td style="white-space:nowrap">hasDifferentValue<a name="Relationship-hasDifferentValue"> </a></td><td>has a different value</td><td>a specific data element must (or can) have a different value</td></tr><tr><td style="white-space:nowrap">mentions<a name="Relationship-mentions"> </a></td><td>mentions</td><td>an unqualified relationship that something is mentioned from somewhere</td></tr><tr><td style="white-space:nowrap">defines<a name="Relationship-defines"> </a></td><td>defines</td><td>provides a formal definition</td></tr><tr><td style="white-space:nowrap">provides<a name="Relationship-provides"> </a></td><td>provides</td><td>who is providing which information</td></tr><tr><td style="white-space:nowrap">is-a<a name="Relationship-is-a"> </a></td><td>specialisation</td><td>identifies a more general element</td></tr><tr><td style="white-space:nowrap">synonym<a name="Relationship-synonym"> </a></td><td>is a synonym</td><td>is a synonym for another term</td></tr><tr><td style="white-space:nowrap">identifiedBy<a name="Relationship-identifiedBy"> </a></td><td>identified by</td><td>can be identified by</td></tr><tr><td style="white-space:nowrap">identifies<a name="Relationship-identifies"> </a></td><td>identfies</td><td>identifies</td></tr><tr><td style="white-space:nowrap">executes<a name="Relationship-executes"> </a></td><td>execute a procedure</td><td>who is executing a specific procedure</td></tr><tr><td style="white-space:nowrap">differsFrom<a name="Relationship-differsFrom"> </a></td><td>differs from</td><td>the two concepts are different</td></tr><tr><td style="white-space:nowrap">implies<a name="Relationship-implies"> </a></td><td>implies</td><td>imply, may require</td></tr></table></div>
</text>
<url value="http://www.hl7europe.org/medtechlabel/CodeSystem/Relationship"/>
<identifier>
<system value="urn:ietf:rfc:3986"/>
<value value="urn:oid:1.2.3.4.5.6.7.8.9.20"/>
</identifier>
<version value="0.4.3"/>
<name value="RelationshipCS"/>
<title value="Relationship"/>
<status value="active"/>
<experimental value="true"/>
<date value="2026-09-29T20:54:24+00:00"/>
<publisher value="HL7 Europe"/>
<contact>
<name value="HL7 Europe"/>
<telecom>
<system value="url"/>
<value value="http://www.hl7europe.org"/>
</telecom>
</contact>
<description value="**Relationship**"/>
<caseSensitive value="true"/>
<valueSet
value="http://www.hl7europe.org/medtechlabel/ValueSet/Relationship"/>
<hierarchyMeaning value="is-a"/>
<compositional value="false"/>
<content value="complete"/>
<count value="27"/>
<concept>
<code value="derivedFrom"/>
<display value="derived from"/>
<definition value="data element from which it is derived"/>
</concept>
<concept>
<code value="supportedBy"/>
<display value="supported by"/>
<definition
value="the source is supported by the target item in some way"/>
</concept>
<concept>
<code value="addresses"/>
<display value="addresses"/>
<definition value="what issue is solved, and how?"/>
</concept>
<concept>
<code value="hasComponent"/>
<display value="has component"/>
<definition
value="reference to parts of the source item; reverse of partOf"/>
</concept>
<concept>
<code value="appliesTo"/>
<display value="applies to"/>
<definition value="the source applies to the target"/>
</concept>
<concept>
<code value="constrains"/>
<display value="constrains"/>
<definition value="the source constrains the target element"/>
</concept>
<concept>
<code value="conformsTo"/>
<display value="conforms to"/>
<definition value="is conformant to certain regularities"/>
</concept>
<concept>
<code value="mapsTo"/>
<display value="maps to"/>
<definition value="maps to"/>
</concept>
<concept>
<code value="equivalentTo"/>
<display value="equivalent to"/>
<definition
value="the source concept is equivalent to the target concept"/>
</concept>
<concept>
<code value="broaderThan"/>
<display value="broader than"/>
<definition
value="the source concept is broader, i.e. more general, in its meaning than the equivalent to the target concept"/>
</concept>
<concept>
<code value="narrowerThan"/>
<display value="narrower than"/>
<definition
value="the source concept is narrower, i.e. more specialized, in its meaning than the to the target concept"/>
</concept>
<concept>
<code value="overlapsWith"/>
<display value="overlaps with"/>
<definition
value="the source concept overlaps in the meaning with the target concept"/>
</concept>
<concept>
<code value="conflictsWith"/>
<display value="conflicts with"/>
<definition
value="the source concept is in conflict with the target concept"/>
</concept>
<concept>
<code value="supersedes"/>
<display value="supersedes"/>
<definition value="supersedes"/>
</concept>
<concept>
<code value="hasFormat"/>
<display value="has format"/>
<definition
value="the provided information has to fulfill certain representation formats"/>
</concept>
<concept>
<code value="hasValue"/>
<display value="has Value"/>
<definition
value="a specific data element must (or can) have a certain value"/>
</concept>
<concept>
<code value="hasDifferentValue"/>
<display value="has a different value"/>
<definition
value="a specific data element must (or can) have a different value"/>
</concept>
<concept>
<code value="mentions"/>
<display value="mentions"/>
<definition
value="an unqualified relationship that something is mentioned from somewhere"/>
</concept>
<concept>
<code value="defines"/>
<display value="defines"/>
<definition value="provides a formal definition"/>
</concept>
<concept>
<code value="provides"/>
<display value="provides"/>
<definition value="who is providing which information"/>
</concept>
<concept>
<code value="is-a"/>
<display value="specialisation"/>
<definition value="identifies a more general element"/>
</concept>
<concept>
<code value="synonym"/>
<display value="is a synonym"/>
<definition value="is a synonym for another term"/>
</concept>
<concept>
<code value="identifiedBy"/>
<display value="identified by"/>
<definition value="can be identified by"/>
</concept>
<concept>
<code value="identifies"/>
<display value="identfies"/>
<definition value="identifies"/>
</concept>
<concept>
<code value="executes"/>
<display value="execute a procedure"/>
<definition value="who is executing a specific procedure"/>
</concept>
<concept>
<code value="differsFrom"/>
<display value="differs from"/>
<definition value="the two concepts are different"/>
</concept>
<concept>
<code value="implies"/>
<display value="implies"/>
<definition value="imply, may require"/>
</concept>
</CodeSystem>