This page is part of the FHIR Specification (v1.6.0: STU 3 Ballot 4). 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 value set defined by the FHIR project.
Summary
Defining URL: | http://hl7.org/fhir/ValueSet/contactentity-type |
Name: | ContactEntityType |
Definition: | 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. |
Committee: | Patient Administration Work Group |
OID: | 2.16.840.1.113883.4.642.2.229 (for OID based terminology systems) |
Source Resource | XML / JSON |
This value set is used in the following places:
This value set includes codes from the following code systems:
This expansion generated 11 Aug 2016
This value set contains 6 concepts
All codes from system http://hl7.org/fhir/contactentity-type
Code | Display | Definition |
BILL | Billing | Contact details for information regarding to billing/general finance enquiries. |
ADMIN | Administrative | Contact details for administrative enquiries. |
HR | Human Resource | Contact details for issues related to Human Resources, such as staff matters, OH&S etc. |
PAYOR | Payor | Contact details for dealing with issues related to insurance claims/adjudication/payment. |
PATINF | Patient | Generic information contact for patients. |
PRESS | Press | Dedicated contact point for matters relating to press enquiries. |
See the full registry of value sets defined as part of FHIR.
Explanation of the columns that may appear on this page:
Level | A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies |
Source | The source of the definition of the code (when the value set draws in codes defined elsewhere) |
Code | The code (used as the code in the resource instance) |
Display | The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application |
Definition | An explanation of the meaning of the concept |
Comments | Additional notes about how to use the code |