FHIR Cross-Version Extensions package for FHIR R4 from FHIR R5 - Version 0.0.1-snapshot-2. See the Directory of published versions
| Official URL: http://hl7.org/fhir/5.0/ValueSet/R5-contactentity-type-for-R4 | Version: 0.0.1-snapshot-2 | |||
| Standards status: Informative | Maturity Level: 3 | Responsible: Patient Administration | Computable Name: R5_contactentity_type_for_R4 | |
| This cross-version ValueSet represents concepts from http://terminology.hl7.org/ValueSet/contactentity-type | 0.5.0 for use in FHIR R4. Concepts not present here have direct equivalent mappings crossing all versions from R5 to R4. |
References
http://terminology.hl7.org/CodeSystem/contactentity-type version 0.5.0| Code | Display | Definition |
| ADMIN | Administrative | Contact details for administrative enquiries. |
| PAYOR | Payor | Contact details for dealing with issues related to insurance claims/adjudication/payment. |
| PRESS | Press | Dedicated contact point for matters relating to press enquiries. |
This value set expansion contains 3 concepts.
| Code | System | Display | Definition |
| ADMIN | http://terminology.hl7.org/CodeSystem/contactentity-type | Administrative | Contact details for administrative enquiries. |
| PAYOR | http://terminology.hl7.org/CodeSystem/contactentity-type | Payor | Contact details for dealing with issues related to insurance claims/adjudication/payment. |
| PRESS | http://terminology.hl7.org/CodeSystem/contactentity-type | Press | Dedicated 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 |
| System | 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 |