This page is part of the FHIR Specification (v1.1.0: STU 3 Ballot 1). 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
This is a frozen snapshot of the FHIR specification created for the purpose of balloting the GAO implementation Guide. It includes draft changes that may be part of the future DSTU 2.1 release but further change is expected. Readers should focus solely on the GAO implementation content, and FHIR DSTU 2 for other purposes.
Definition for Value SetContactEntityType
<ValueSet xmlns="http://hl7.org/fhir"> <id value="contactentity-type"/> <meta> <lastUpdated value="2015-12-03T09:57:31.744+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 has an inline code system http://hl7.org/fhir/contactentity-type, which defines the following codes:</p> <table class="codes"> <tr> <td> <b>Code</b> </td> <td> <b>Display</b> </td> <td> <b>Definition</b> </td> </tr> <tr> <td>BILL <a name="BILL"> </a> </td> <td>Billing</td> <td>Contact details for information regarding to billing/general finance enquiries.</td> </tr> <tr> <td>ADMIN <a name="ADMIN"> </a> </td> <td>Administrative</td> <td>Contact details for administrative enquiries.</td> </tr> <tr> <td>HR <a name="HR"> </a> </td> <td>Human Resource</td> <td>Contact details for issues related to Human Resources, such as staff matters, OH&S etc.</td> </tr> <tr> <td>PAYOR <a name="PAYOR"> </a> </td> <td>Payor</td> <td>Contact details for dealing with issues related to insurance claims/adjudication/payment.</td> </tr> <tr> <td>PATINF <a name="PATINF"> </a> </td> <td>Patient</td> <td>Generic information contact for patients.</td> </tr> <tr> <td>PRESS <a name="PRESS"> </a> </td> <td>Press</td> <td>Dedicated contact point for matters relating to press enquiries.</td> </tr> </table> </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.1.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="2015-12-03T09:57:31+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."/> <codeSystem> <extension url="http://hl7.org/fhir/StructureDefinition/valueset-oid"> <valueUri value="urn:oid:2.16.840.1.113883.4.642.1.229"/> </extension> <system value="http://hl7.org/fhir/contactentity-type"/> <caseSensitive value="true"/> <concept> <code value="BILL"/> <display value="Billing"/> <definition value="Contact details for information regarding to billing/general finance enquiries."/> </concept> <concept> <code value="ADMIN"/> <display value="Administrative"/> <definition value="Contact details for administrative enquiries."/> </concept> <concept> <code value="HR"/> <display value="Human Resource"/> <definition value="Contact details for issues related to Human Resources, such as staff matters, OH&S etc."/> </concept> <concept> <code value="PAYOR"/> <display value="Payor"/> <definition value="Contact details for dealing with issues related to insurance claims/adjudication/payment."/> </concept> <concept> <code value="PATINF"/> <display value="Patient"/> <definition value="Generic information contact for patients."/> </concept> <concept> <code value="PRESS"/> <display value="Press"/> <definition value="Dedicated contact point for matters relating to press enquiries."/> </concept> </codeSystem> </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.