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

ValueSet: Relationship

Official URL: http://www.hl7europe.org/medtechlabel/ValueSet/Relationship Version: 0.4.3
Active as of 2026-08-20 Computable Name: RelationshipVS
Other Identifiers: OID:1.2.3.4.5.6.7.8.10.20

Copyright/Legal: FO

Relationship

References

This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)

Logical Definition (CLD)

 

Expansion

Expansion performed internally based on codesystem Relationship v0.4.3 (CodeSystem)

This value set contains 27 concepts

SystemCodeDisplay (en)DefinitionJSONXML
http://www.hl7europe.org/medtechlabel/CodeSystem/Relationship  derivedFromderived fromdata element from which it is derived
http://www.hl7europe.org/medtechlabel/CodeSystem/Relationship  supportedBysupported bythe source is supported by the target item in some way
http://www.hl7europe.org/medtechlabel/CodeSystem/Relationship  addressesaddresseswhat issue is solved, and how?
http://www.hl7europe.org/medtechlabel/CodeSystem/Relationship  hasComponenthas componentreference to parts of the source item; reverse of partOf
http://www.hl7europe.org/medtechlabel/CodeSystem/Relationship  appliesToapplies tothe source applies to the target
http://www.hl7europe.org/medtechlabel/CodeSystem/Relationship  constrainsconstrainsthe source constrains the target element
http://www.hl7europe.org/medtechlabel/CodeSystem/Relationship  conformsToconforms tois conformant to certain regularities
http://www.hl7europe.org/medtechlabel/CodeSystem/Relationship  mapsTomaps tomaps to
http://www.hl7europe.org/medtechlabel/CodeSystem/Relationship  equivalentToequivalent tothe source concept is equivalent to the target concept
http://www.hl7europe.org/medtechlabel/CodeSystem/Relationship  broaderThanbroader thanthe source concept is broader, i.e. more general, in its meaning than the equivalent to the target concept
http://www.hl7europe.org/medtechlabel/CodeSystem/Relationship  narrowerThannarrower thanthe source concept is narrower, i.e. more specialized, in its meaning than the to the target concept
http://www.hl7europe.org/medtechlabel/CodeSystem/Relationship  overlapsWithoverlaps withthe source concept overlaps in the meaning with the target concept
http://www.hl7europe.org/medtechlabel/CodeSystem/Relationship  conflictsWithconflicts withthe source concept is in conflict with the target concept
http://www.hl7europe.org/medtechlabel/CodeSystem/Relationship  supersedessupersedessupersedes
http://www.hl7europe.org/medtechlabel/CodeSystem/Relationship  hasFormathas formatthe provided information has to fulfill certain representation formats
http://www.hl7europe.org/medtechlabel/CodeSystem/Relationship  hasValuehas Valuea specific data element must (or can) have a certain value
http://www.hl7europe.org/medtechlabel/CodeSystem/Relationship  hasDifferentValuehas a different valuea specific data element must (or can) have a different value
http://www.hl7europe.org/medtechlabel/CodeSystem/Relationship  mentionsmentionsan unqualified relationship that something is mentioned from somewhere
http://www.hl7europe.org/medtechlabel/CodeSystem/Relationship  definesdefinesprovides a formal definition
http://www.hl7europe.org/medtechlabel/CodeSystem/Relationship  providesprovideswho is providing which information
http://www.hl7europe.org/medtechlabel/CodeSystem/Relationship  is-aspecialisationidentifies a more general element
http://www.hl7europe.org/medtechlabel/CodeSystem/Relationship  synonymis a synonymis a synonym for another term
http://www.hl7europe.org/medtechlabel/CodeSystem/Relationship  identifiedByidentified bycan be identified by
http://www.hl7europe.org/medtechlabel/CodeSystem/Relationship  identifiesidentfiesidentifies
http://www.hl7europe.org/medtechlabel/CodeSystem/Relationship  executesexecute a procedurewho is executing a specific procedure
http://www.hl7europe.org/medtechlabel/CodeSystem/Relationship  differsFromdiffers fromthe two concepts are different
http://www.hl7europe.org/medtechlabel/CodeSystem/Relationship  impliesimpliesimply, may require

Explanation of the columns that may appear on this page:

Level A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies
System The source of the definition of the code (when the value set draws in codes defined elsewhere)
Code The code (used as the code in the resource instance)
Display The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application
Definition An explanation of the meaning of the concept
Comments Additional notes about how to use the code