This is the Continuous Integration Build of FHIR (will be incorrect/inconsistent at times).
See the Directory of published versions
FHIR Infrastructure Work Group | Maturity Level: 5 | Trial Use | Use Context: Country: Global (Whole world), Not yet ready for Production use |
Official URL: http://hl7.org/fhir/ValueSet/additional-binding-purpose
|
Version: 6.0.0-ballot2 | |||
active as of 2024-11-22 | Computable Name: AdditionalBindingPurposeVS | |||
Flags: Experimental, Immutable | OID: |
This value set is used in the following places:
Additional Binding Purpose
Generated Narrative: ValueSet additional-binding-purpose
Last updated: 2024-11-22T12:02:07.167Z
Profile: Shareable ValueSet
http://hl7.org/fhir/CodeSystem/additional-binding-purpose
This expansion generated 22 Nov 2024
Generated Narrative: ValueSet
Last updated: 2024-11-22T12:02:07.167Z
Profile: Shareable ValueSet
Expansion based on codesystem Additional Binding Purpose Codes v6.0.0-ballot2 (CodeSystem)
This value set contains 10 concepts
Code | System | Display | Definition |
maximum | http://hl7.org/fhir/CodeSystem/additional-binding-purpose | Maximum Binding | A required binding, for use when the binding strength is 'extensible' or 'preferred' |
minimum | http://hl7.org/fhir/CodeSystem/additional-binding-purpose | Minimum Binding | The minimum allowable value set - any conformant system SHALL support all these codes |
required | http://hl7.org/fhir/CodeSystem/additional-binding-purpose | Required Binding | This value set is used as a required binding (in addition to the base binding (not a replacement), usually in a particular usage context) |
extensible | http://hl7.org/fhir/CodeSystem/additional-binding-purpose | Conformance Binding | This value set is used as an extensible binding (in addition to the base binding (not a replacement), usually in a particular usage context) |
candidate | http://hl7.org/fhir/CodeSystem/additional-binding-purpose | Candidate Binding | This value set is a candidate to substitute for the overall conformance value set in some situations; usually these are defined in the documentation |
current | http://hl7.org/fhir/CodeSystem/additional-binding-purpose | Current Binding | New records are required to use this value set, but legacy records may use other codes. The definition of 'new record' is difficult, since systems often create new records based on pre-existing data. Usually 'current' bindings are mandated by an external authority that makes clear rules around this |
preferred | http://hl7.org/fhir/CodeSystem/additional-binding-purpose | Preferred Binding | This is the value set that is preferred in a given context (documentation should explain why) |
ui | http://hl7.org/fhir/CodeSystem/additional-binding-purpose | UI Suggested Binding | This value set is provided for user look up in a given context. Typically, these valuesets only include a subset of codes relevant for input in a context |
starter | http://hl7.org/fhir/CodeSystem/additional-binding-purpose | Starter Binding | This value set is a good set of codes to start with when designing your system |
component | http://hl7.org/fhir/CodeSystem/additional-binding-purpose | Component Binding | This value set is a component of the base value set. Usually this is called out so that documentation can be written about a portion of the value set |
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 |