STU 3 Candidate

This page is part of the FHIR Specification (v1.4.0: STU 3 Ballot 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: R4B R4 R3 R2

Valueset-contactentity-type.xml

Raw XML (canonical form)

Definition for Value SetContactEntityType

<ValueSet xmlns="http://hl7.org/fhir">
  <id value="contactentity-type"/>
  <meta>
    <lastUpdated value="2016-03-31T08:01:25.570+11:00"/>
    <profile value="http://hl7.org/fhir/StructureDefinition/valueset-shareable-definition"/>
  </meta>
  <text>
    <status value="generated"/>
    <div xmlns="http://www.w3.org/1999/xhtml">
      <h2>ContactEntityType</h2>
      <p>This example value set defines a set of codes that can be used to indicate the purpose
         for which you would contact a contact party.</p>
      <p>This value set includes codes from the following code systems:</p>
      <ul>
        <li>Include all codes defined in 
          <a href="codesystem-contactentity-type.html">http://hl7.org/fhir/contactentity-type</a>
        </li>
      </ul>
    </div>
  </text>
  <extension url="http://hl7.org/fhir/StructureDefinition/valueset-oid">
    <valueUri value="urn:oid:2.16.840.1.113883.4.642.2.229"/>
  </extension>
  <url value="http://hl7.org/fhir/ValueSet/contactentity-type"/>
  <version value="1.4.0"/>
  <name value="ContactEntityType"/>
  <status value="draft"/>
  <experimental value="true"/>
  <publisher value="FHIR Project team"/>
  <contact>
    <telecom>
      <system value="other"/>
      <value value="http://hl7.org/fhir"/>
    </telecom>
  </contact>
  <date value="2016-03-31T08:01:25+11:00"/>
  <description value="This example value set defines a set of codes that can be used to indicate the purpose
   for which you would contact a contact party."/>
  <compose>
    <include>
      <system value="http://hl7.org/fhir/contactentity-type"/>
    </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.