This is the Continuous Integration Build of FHIR (will be incorrect/inconsistent at times).
See the Directory of published versions
Financial Management Work Group | Maturity Level: 4 | Trial Use | Use Context: Country: World |
Official URL: http://hl7.org/fhir/ValueSet/payment-type
|
Version: 6.0.0-ballot2 | |||
draft as of 2024-12-10 | Computable Name: PaymentTypeCodes | |||
Flags: | OID: 2.16.840.1.113883.4.642.3.641 |
This value set is used in the following places:
This value set includes sample Payment Type codes.
Generated Narrative: ValueSet payment-type
Last updated: 2024-12-10T20:05:15.367Z
Profile: Shareable ValueSet
http://terminology.hl7.org/CodeSystem/payment-type
This expansion generated 10 Dec 2024
Generated Narrative: ValueSet
Last updated: 2024-12-10T20:05:15.367Z
Profile: Shareable ValueSet
Expansion based on codesystem Payment Type Codes v1.0.1 (CodeSystem)
This value set contains 3 concepts
Code | System | Display | Definition |
payment | http://terminology.hl7.org/CodeSystem/payment-type | Payment | The amount is partial or complete settlement of the amounts due. |
adjustment | http://terminology.hl7.org/CodeSystem/payment-type | Adjustment | The amount is an adjustment regarding claims already paid. |
advance | http://terminology.hl7.org/CodeSystem/payment-type | Advance | The amount is an advance against future claims. |
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 |