HL7 Terminology
1.0.0 - Publication

This page is part of the HL7 Terminology (v1.0.0: Release) based on FHIR R4. The current version which supercedes this version is 5.2.0. For a full list of available versions, see the Directory of published versions

Contact entity type

Summary

Defining URL:http://terminology.hl7.org/ValueSet/contactentity-type
Version:4.1.0
Name:ContactEntityType
Status:draft
Title:Contact entity type
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.

Publisher:FHIR Project team
Committee:Patient Administration
OID:2.16.840.1.113883.4.642.3.416 (for OID based terminology systems)
Maturity:3
Source Resource:XML / JSON / Turtle

References

This value set is not used

Content Logical Definition

Logical Definition (CLD)

 

Expansion

This value set contains 6 concepts

Expansion based on Contact entity type v4.2.0 (CodeSystem)

All codes from system http://terminology.hl7.org/CodeSystem/contactentity-type

CodeDisplayDefinition
BILLBillingContact details for information regarding to billing/general finance enquiries.
ADMINAdministrativeContact details for administrative enquiries.
HRHuman ResourceContact details for issues related to Human Resources, such as staff matters, OH&S etc.
PAYORPayorContact details for dealing with issues related to insurance claims/adjudication/payment.
PATINFPatientGeneric information contact for patients.
PRESSPressDedicated contact point for matters relating to press enquiries.

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

History

DateActionAuthorCustodianComment
2020-05-06reviseTed KleinVocabulary WGMigrated to the UTG maintenance environment and publishing tooling.