FHIR Release 3 (STU)

This page is part of the FHIR Specification (v3.0.2: STU 3). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R4 R3 R2

V3-RoleLinkType.xml

Vocabulary Work GroupMaturity Level: N/ABallot Status: Informative

Raw XML (canonical form)

**** MISSING DEFINITIONS ****

<ValueSet xmlns="http://hl7.org/fhir">
  <id value="v3-RoleLinkType"/> 
  <meta> 
    <lastUpdated value="2016-11-11T00:00:00.000+11:00"/> 
    <profile value="http://hl7.org/fhir/StructureDefinition/shareablevalueset"/> 
  </meta> 
  <text> 
    <status value="generated"/> 
    <div xmlns="http://www.w3.org/1999/xhtml">
      <p> Release Date: 2016-11-11</p> 

      <table class="grid">
 
        <tr> 
          <td> 
            <b> Level</b> 
          </td> 
          <td> 
            <b> Code</b> 
          </td> 
          <td> 
            <b> Display</b> 
          </td> 
          <td> 
            <b> Definition</b> 
          </td> 
        </tr> 
 
        <tr> 
          <td> 1</td> 
          <td> REL
            <a name="REL"> </a> 
          </td> 
          <td> related</td> 
          <td> 
                        An action taken with respect to a subject Entity by a regulatory
               or authoritative body with supervisory capacity over that entity. The action is taken
               in response to behavior by the subject Entity that body finds to be undesirable.
            <br/>  

                        Suspension, license restrictions, monetary fine, letter of reprimand,
               mandated training, mandated supervision, etc.Examples:
                        
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 2</td> 
          <td>   BACKUP
            <a name="BACKUP"> </a> 
          </td> 
          <td> is backup for</td> 
          <td> 
                        This relationship indicates the source Role is available to the
               target Role as a backup. An entity in a backup role will be available as a substitute
               or replacement in the event that the entity assigned the role is unavailable. In medical
               roles where it is critical that the function be performed and there is a possibility that
               the individual assigned may be ill or otherwise indisposed, another individual is assigned
               to cover for the individual originally assigned the role. A backup may be required to
               be identified, but unless the backup is actually used, he/she would not assume the assigned
               entity role.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 2</td> 
          <td>   CONT
            <a name="CONT"> </a> 
          </td> 
          <td> has contact</td> 
          <td> This relationship indicates the target Role provides or receives information regarding
               the target role.  For example, AssignedEntity is a contact for a ServiceDeliveryLocation.</td> 
        </tr> 
 
        <tr> 
          <td> 2</td> 
          <td>   DIRAUTH
            <a name="DIRAUTH"> </a> 
          </td> 
          <td> has direct authority over</td> 
          <td> 
                        The source Role has direct authority over the target role in a
               chain of authority.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 2</td> 
          <td>   IDENT
            <a name="IDENT"> </a> 
          </td> 
          <td> Identification</td> 
          <td> 
                        
                           Description: The source role provides identification for the
               target role. The source role must be IDENT. The player entity of the source role is constrained
               to be the same as (i.e. the equivalent of, or equal to) the player of the target role
               if present. If the player is absent from the source role, then it is assumed to be the
               same as the player of the target role.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 2</td> 
          <td>   INDAUTH
            <a name="INDAUTH"> </a> 
          </td> 
          <td> has indirect authority over</td> 
          <td> 
                        The source Role has indirect authority over the target role in
               a chain of authority.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 2</td> 
          <td>   PART
            <a name="PART"> </a> 
          </td> 
          <td> has part</td> 
          <td> 
                        The target Role is part of the Source Role.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 2</td> 
          <td>   REPL
            <a name="REPL"> </a> 
          </td> 
          <td> replaces</td> 
          <td> 
                        This relationship indicates that the source Role replaces (or
               subsumes) the target Role.  Allows for new identifiers and/or new effective time for a
               registry entry or a certification, etc.
            <br/>  

                     
          </td> 
        </tr> 

      </table> 

    </div> 
  </text> 
  <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-ballot-status">
    <valueString value="External"/> 
  </extension> 
  <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
    <valueInteger value="1"/> 
  </extension> 
  <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
    <valueCode value="sec"/> 
  </extension> 
  <url value="http://hl7.org/fhir/ValueSet/v3-RoleLinkType"/> 
  <identifier> 
    <system value="urn:ietf:rfc:3986"/> 
    <value value="urn:oid:2.16.840.1.113883.1.11.11603"/> 
  </identifier> 
  <version value="2016-11-11"/> 
  <name value="v3 Code System RoleLinkType"/> 
  <status value="active"/> 
  <experimental value="false"/> 
  <date value="2016-11-11"/> 
  <publisher value="HL7, Inc"/> 
  <contact> 
    <telecom> 
      <system value="url"/> 
      <value value="http://hl7.org"/> 
    </telecom> 
  </contact> 
  <description value="**** MISSING DEFINITIONS ****"/> 
  <immutable value="true"/> 
  <compose> 
    <include> 
      <system value="http://hl7.org/fhir/v3/RoleLinkType"/> 
    </include> 
  </compose> 
</ValueSet> 

Usage note: every effort has been made to ensure that the examples are correct and useful, but they are not a normative part of the specification.