DSTU2

This page is part of the FHIR Specification (v1.0.2: DSTU 2). 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

1.25.2.1.229 Value Set http://hl7.org/fhir/ValueSet/contactentity-type

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.
OID:2.16.840.1.113883.4.642.2.229 (for OID based terminology systems)
System URL:http://hl7.org/fhir/contactentity-type
System OID:2.16.840.1.113883.4.642.1.229
Source ResourceXML / JSON

This value set is used in the following places:

1.25.2.1.229.1 Content Logical Definition

This value set has an inline code system http://hl7.org/fhir/contactentity-type, which defines the following codes:

CodeDisplayDefinition
BILL BillingContact details for information regarding to billing/general finance enquiries.
ADMIN AdministrativeContact details for administrative enquiries.
HR Human ResourceContact details for issues related to Human Resources, such as staff matters, OH&S etc.
PAYOR PayorContact details for dealing with issues related to insurance claims/adjudication/payment.
PATINF PatientGeneric information contact for patients.
PRESS PressDedicated 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:

LevelA 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
SourceThe source of the definition of the code (when the value set draws in codes defined elsewhere)
CodeThe code (used as the code in the resource instance)
DisplayThe 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
DefinitionAn explanation of the meaning of the concept
CommentsAdditional notes about how to use the code