Preferred Name

RoleClass

Definitions

<p>This table includes codes for the Role class hierarchy. The values in this hierarchy, represent a Role which is an association or relationship between two entities - the entity that plays the role and the entity that scopes the role. Roles names are derived from the name of the playing entity in that role.</p><p>The role hierarchy stems from three core concepts, or abstract domains:</p><ul><li><p><b>RoleClassOntological</b> is an abstract domain that collects roles in which the playing entity is defined or specified by the scoping entity.</p></li><li><p><b>RoleClassPartitive</b> collects roles in which the playing entity is in some sense a "part" of the scoping entity.</p></li><li><p><b>RoleClassAssociative</b> collects all of the remaining forms of association between the playing entity and the scoping entity. This set of roles is further partitioned between:</p><ul><li><p><b>RoleClassPassive</b> which are roles in which the playing entity is used, known, treated, handled, built, or destroyed, etc. under the auspices of the scoping entity. The playing entity is passive in these roles in that the role exists without an agreement from the playing entity.</p></li><li><p><b>RoleClassMutualRelationship</b> which are relationships based on mutual behavior of the two entities. The basis of these relationship may be formal agreements or they may be<i>de facto</i> behavior. Thus, this sub-domain is further divided into:</p><ul><li><p><b>RoleClassRelationshipFormal</b> in which the relationship is formally defined, frequently by a contract or agreement.</p></li><li><p><b>Personal relationship</b> which inks two people in a personal relationship.</p></li></ul></li></ul></li></ul><p>The hierarchy discussed above is represented In the current vocabulary tables as a set of abstract domains, with the exception of the "Personal relationship" which is a leaf concept.</p>

ID

http://purl.bioontology.org/ontology/HL7/C1553775

Context binding of

http://purl.bioontology.org/ontology/HL7/C1553775

cui

C1553775

definition

This table includes codes for the Role class hierarchy. The values in this hierarchy, represent a Role which is an association or relationship between two entities - the entity that plays the role and the entity that scopes the role. Roles names are derived from the name of the playing entity in that role.

The role hierarchy stems from three core concepts, or abstract domains:

  • RoleClassOntological is an abstract domain that collects roles in which the playing entity is defined or specified by the scoping entity.

  • RoleClassPartitive collects roles in which the playing entity is in some sense a "part" of the scoping entity.

  • RoleClassAssociative collects all of the remaining forms of association between the playing entity and the scoping entity. This set of roles is further partitioned between:

    • RoleClassPassive which are roles in which the playing entity is used, known, treated, handled, built, or destroyed, etc. under the auspices of the scoping entity. The playing entity is passive in these roles in that the role exists without an agreement from the playing entity.

    • RoleClassMutualRelationship which are relationships based on mutual behavior of the two entities. The basis of these relationship may be formal agreements or they may bede facto behavior. Thus, this sub-domain is further divided into:

      • RoleClassRelationshipFormal in which the relationship is formally defined, frequently by a contract or agreement.

      • Personal relationship which inks two people in a personal relationship.

The hierarchy discussed above is represented In the current vocabulary tables as a set of abstract domains, with the exception of the "Personal relationship" which is a leaf concept.

Codes for the Role class hierarchy. The values in this hierarchy, represent a Role which is an association or relationship between two entities - the entity that plays the role and the entity that scopes the role. Roles names are derived from the name of the playing entity in that role.

The role hierarchy stems from three core concepts, or abstract domains:

  • RoleClassOntological is an abstract domain that collects roles in which the playing entity is defined or specified by the scoping entity.

  • RoleClassPartitive collects roles in which the playing entity is in some sense a "part" of the scoping entity.

  • RoleClassAssociative collects all of the remaining forms of association between the playing entity and the scoping entity. This set of roles is further partitioned between:

    • RoleClassPassive which are roles in which the playing entity is used, known, treated, handled, built, or destroyed, etc. under the auspices of the scoping entity. The playing entity is passive in these roles in that the role exists without an agreement from the playing entity.

    • RoleClassMutualRelationship which are relationships based on mutual behavior of the two entities. The basis of these relationship may be formal agreements or they may bede facto behavior. Thus, this sub-domain is further divided into:

      • RoleClassRelationshipFormal in which the relationship is formally defined, frequently by a contract or agreement.

      • Personal relationship which inks two people in a personal relationship.

The hierarchy discussed above is represented In the current vocabulary tables as a set of abstract domains, with the exception of the "Personal relationship" which is a leaf concept.

OpenIssue:Description copied from Concept Domain of same name. Must be verified.

Has context binding

http://purl.bioontology.org/ontology/HL7/C1553775

Has supported concept property

http://purl.bioontology.org/ontology/HL7/C3242699

http://purl.bioontology.org/ontology/HL7/C3242700

http://purl.bioontology.org/ontology/HL7/C3242697

http://purl.bioontology.org/ontology/HL7/C3242696

http://purl.bioontology.org/ontology/HL7/C3242702

http://purl.bioontology.org/ontology/HL7/C3244072

http://purl.bioontology.org/ontology/HL7/C3242701

http://purl.bioontology.org/ontology/HL7/C3242698

http://purl.bioontology.org/ontology/HL7/C3244083

http://purl.bioontology.org/ontology/HL7/C0449438

Has supported concept relationship

http://purl.bioontology.org/ontology/HL7/C4520708

http://purl.bioontology.org/ontology/HL7/C3245443

HL7 code status

active

HL7 contributor

Sponsor

HL7 history item

Lock all vaue sets untouched since 2014-03-26 to trackingId 2014T1_2014_03_26

HL7 internal Id

19854

HL7 is immutable

true

HL7 notation

Is in UMLS.

HL7 OID

2.16.840.1.113883.5.110

HL7 release date

2019-03-20

HL7 version date

2014-03-26

HL7AI

true

HL7CC

true

HL7MI

true

HL7PL

true

HL7PV

134

HL7RG

Health Level 7

HL7SCS

2.16.840.1.113883.5.110

HL7SL

en

HL7VC

notation

C1553775

prefLabel

RoleClass

tui

T170

subClassOf

http://www.w3.org/2002/07/owl#Thing

http://purl.bioontology.org/ontology/HL7/C1610738

Delete Subject Author Type Created
No notes to display
Create New Mapping

Delete Mapping To Ontology Source
There are currently no mappings for this class.