Release 4

This page is part of the FHIR Specification (v4.0.1: R4 - Mixed Normative and STU) in it's permanent home (it will always be available at this URL). 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

V3-CommunicationFunctionType.cs.xml

Vocabulary Work GroupMaturity Level: N/AStandards Status: Informative

Raw XML (canonical form + also see XML Format Specification)

Describes the type of communication function that the associated entity plays in the associated transmission.

<?xml version="1.0" encoding="UTF-8"?>

<CodeSystem xmlns="http://hl7.org/fhir">
  <id value="v3-CommunicationFunctionType"/> 
  <meta> 
    <lastUpdated value="2018-08-12T00:00:00.000+10:00"/> 
  </meta> 
  <text> 
    <status value="generated"/> 
    <div xmlns="http://www.w3.org/1999/xhtml">
      <p> Release Date: 2018-08-12</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> RCV
            <a name="v3-CommunicationFunctionType-RCV"> </a> 
          </td> 
          <td> receiver</td> 
          <td> 
                        The entity is the receiver of the transmission.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 1</td> 
          <td> RSP
            <a name="v3-CommunicationFunctionType-RSP"> </a> 
          </td> 
          <td> respond to</td> 
          <td> 
                        The entity is the one to which the response or reply to the transmission
               should be sent.
            <br/>  

                     
          </td> 
        </tr> 
 
        <tr> 
          <td> 1</td> 
          <td> SND
            <a name="v3-CommunicationFunctionType-SND"> </a> 
          </td> 
          <td> sender</td> 
          <td> 
                        The entity is the sender of the transmission.
            <br/>  

                     
          </td> 
        </tr> 

      </table> 

    </div> 
  </text> 
  <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status">
    <valueCode value="external"/> 
  </extension> 
  <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
    <valueInteger value="0"/> 
  </extension> 
  <url value="http://terminology.hl7.org/CodeSystem/v3-CommunicationFunctionType"/> 
  <identifier> 
    <system value="urn:ietf:rfc:3986"/> 
    <value value="urn:oid:2.16.840.1.113883.5.1056"/> 
  </identifier> 
  <version value="2018-08-12"/> 
  <name value="v3.CommunicationFunctionType"/> 
  <title value="v3 Code System CommunicationFunctionType"/> 
  <status value="active"/> 
  <experimental value="false"/> 
  <date value="2018-08-12T00:00:00+10:00"/> 
  <publisher value="HL7, Inc"/> 
  <contact> 
    <telecom> 
      <system value="url"/> 
      <value value="http://hl7.org"/> 
    </telecom> 
  </contact> 
  <description value=" Describes the type of communication function that the associated entity plays in the
     associated transmission."/> 
  <caseSensitive value="true"/> 
  <valueSet value="http://terminology.hl7.org/ValueSet/v3-CommunicationFunctionType"/> 
  <hierarchyMeaning value="is-a"/> 
  <content value="complete"/> 
  <concept> 
    <code value="RCV"/> 
    <display value="receiver"/> 
    <definition value="The entity is the receiver of the transmission."/> 
  </concept> 
  <concept> 
    <code value="RSP"/> 
    <display value="respond to"/> 
    <definition value="The entity is the one to which the response or reply to the transmission should be sent."/> 
  </concept> 
  <concept> 
    <code value="SND"/> 
    <display value="sender"/> 
    <definition value="The entity is the sender of the transmission."/> 
  </concept> 
</CodeSystem> 

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.