This page is part of the FHIR Specification (v5.0.0-ballot: R5 Ballot - 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
Financial Management Work Group | Maturity Level: 2 | Trial Use | Use Context: Any |
This is a value set defined by the FHIR project.
Summary
Defining URL: | http://hl7.org/fhir/ValueSet/payment-issuertype |
Version: | 5.0.0-ballot |
Name: | PaymentIssuerType |
Title: | Payment Issuer Type |
Status: | draft |
Definition: | The type of payment issuer. |
Committee: | Financial Management Work Group |
OID: | 2.16.840.1.113883.4.642.3.3208 (for OID based terminology systems) |
Flags: | Immutable |
This value set is used in the following places:
http://hl7.org/fhir/payment-issuertype
This expansion generated 10 Sep 2022
This value set contains 2 concepts
Expansion based on Payment Issuer Type Codes v5.0.0-ballot (CodeSystem)
Code | System | Display | Definition |
patient | http://hl7.org/fhir/payment-issuertype | Patient | The patient or a party issuing payment on behalf of the patient. |
insurance | http://hl7.org/fhir/payment-issuertype | Insurance | An insurer, or party acting on their behalf, which is making payment following a contract, direct or indirect, with the patient to pay for healthcare-related services. |
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 |