This page is part of the FHIR Specification (v5.0.0-draft-final: Final QA Preview for R5 - see ballot notes). 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
Patient Administration Work Group | Maturity Level: 3 | Trial Use | Use Context: Country: World |
Official URL: http://terminology.hl7.org/ValueSet/contactentity-type
|
Version: 0.5.0 | |||
draft as of 2020-02-24 | Computable Name: ContactEntityType | |||
Flags: Immutable | OID: 2.16.840.1.113883.4.642.3.416 |
This value set is used in the following places:
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.
http://terminology.hl7.org/CodeSystem/contactentity-type
This expansion generated 01 Mar 2023
This value set contains 6 concepts
Expansion based on Contact entity type v0.5.0 (CodeSystem)
Code | System | Display | Definition |
BILL | http://terminology.hl7.org/CodeSystem/contactentity-type | Billing | Contact details for information regarding to billing/general finance enquiries. |
ADMIN | http://terminology.hl7.org/CodeSystem/contactentity-type | Administrative | Contact details for administrative enquiries. |
HR | http://terminology.hl7.org/CodeSystem/contactentity-type | Human Resource | Contact details for issues related to Human Resources, such as staff matters, OH&S etc. |
PAYOR | http://terminology.hl7.org/CodeSystem/contactentity-type | Payor | Contact details for dealing with issues related to insurance claims/adjudication/payment. |
PATINF | http://terminology.hl7.org/CodeSystem/contactentity-type | Patient | Generic information contact for patients. |
PRESS | http://terminology.hl7.org/CodeSystem/contactentity-type | 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:
Lvl | A few code lists that FHIR defines are hierarchical - each code is assigned a level. For value sets, levels are mostly used to organize codes for user convenience, but may follow code system hierarchy - see Code System for further information |
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). If the code is in italics, this indicates that the code is not selectable ('Abstract') |
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 |