FHIR R4 Current Build
This page is part of FHIR R4 - the current version v4.0.0 - in it's permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions .

4.3.14.183 4.3.14.188 Code System http://hl7.org/fhir/asset-availability

Financial Management Work Group   Maturity Level : 1 Draft Use Context : Any

This is a code system defined by the FHIR project.

Summary

Defining URL: http://hl7.org/fhir/asset-availability
Version: 4.0.0 4.1.0
Name: ContractResourceAssetAvailiabilityCodes
Title: Contract Resource Asset Availiability codes
Definition:

This value set has asset availability codes.

Committee: Financial Management Work Group
OID: 2.16.840.1.113883.4.642.1.1296 (for OID based terminology systems)
Copyright: HL7 International.
Source Resource XML / JSON

This Code system is used in the following value sets:

Each definition includes usage notes explaining the precedence order in contract lifecycle - i.e., while only some stages are required, the order in which they may occur is deterministic; and a map to comparable FHIR and v.3 status codes. It follows guidance about use of status codes in FHIR at http://build.fhir.org/sc.html.

This value set has asset availability codes.

Copyright Statement: HL7 International.

This code system http://hl7.org/fhir/asset-availability defines the following codes:
Code Display Definition
lease Lease To be completed

 

See the full registry of code systems defined as part of FHIR.


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. 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