HL7 Terminology (THO)
6.0.0 - Publication International flag

This page is part of the HL7 Terminology (v6.0.0: Release) based on FHIR (HL7® FHIR® Standard) v5.0.0. This is the current published version in its permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions

ValueSet: RoleClassAdjacency

Official URL: http://terminology.hl7.org/ValueSet/v3-RoleClassAdjacency Version: 3.0.0
Active as of 2014-03-26 Responsible: Health Level Seven International Computable Name: RoleClassAdjacency
Other Identifiers: OID:2.16.840.1.113883.1.11.20397

Copyright/Legal: This material derives from the HL7 Terminology THO. THO is copyright ©1989+ Health Level Seven International and is made available under the CC0 designation. For more licensing information see: https://terminology.hl7.org/license.html

No description

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)

Generated Narrative: ValueSet v3-RoleClassAdjacency

Language: en

 

Expansion

Generated Narrative: ValueSet

Language: en

Expansion based on codesystem RoleClass v4.0.0 (CodeSystem)

This value set contains 4 concepts

LevelCodeSystemDisplayDefinition
1  ADJYhttp://terminology.hl7.org/CodeSystem/v3-RoleClassadjacency

A physical association whereby two Entities are in some (even lose) spatial relationship with each other such that they touch each other in some way.

Examples: the colon is connected (and therefore adjacent) to the jejunum; the colon is adjacent to the liver (even if not actually connected.)

UsageConstraints: Adjacency is in principle a symmetrical connection, but scoper and player of the role should, where applicable, be assigned to have scoper be the larger, more central Entity and player the smaller, more distant, appendage.

2    CONChttp://terminology.hl7.org/CodeSystem/v3-RoleClassconnection

An adjacency of two Entities held together by a bond which attaches to each of the two entities.

Examples: biceps brachii muscle connected to the radius bone, port 3 on a network switch connected to port 5 on a patch panel.

UsageConstraints: See Adjacency for the assignment of scoper (larger, more central) and player (smaller, more distant).

3      BONDhttp://terminology.hl7.org/CodeSystem/v3-RoleClassmolecular bond

A connection between two atoms of a molecule.

Examples: double bond between first and second C in ethane, peptide bond between two amino-acid, disulfide bridge between two proteins, chelate and ion associations, even the much weaker van-der-Waals bonds can be considered molecular bonds.

UsageConstraints: See connection and adjacency for the assignment of player and scoper.

3      CONYhttp://terminology.hl7.org/CodeSystem/v3-RoleClasscontinuity

A connection between two regional parts.

Examples: the connection between ascending aorta and the aortic arc, connection between descending colon and sigmoid.

UsageConstraints: See connection and adjacency for the assignment of player and scoper.


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

History

DateActionAuthorCustodianComment
2023-11-14reviseMarc DuteauTSMGAdd standard copyright and contact to internal content; up-476
2022-10-18reviseMarc DuteauTSMGFixing missing metadata; up-349
2020-05-06reviseTed KleinVocabulary WGMigrated to the UTG maintenance environment and publishing tooling.
2014-03-26reviseVocabulary (Woody Beeler) (no record of original request)2014T1_2014-03-26_001283 (RIM release ID)Lock all vaue sets untouched since 2014-03-26 to trackingId 2014T1_2014_03_26