This page is part of the FHIR Specification (v5.0.0: R5 - STU). This is the current published version. For a full list of available versions, see the Directory of published versions
http://hl7.org/fhir/ValueSet/additional-binding-purpose
Version: 5.0.0
This value set is used in the following places:
Additional Binding Purpose
http://hl7.org/fhir/CodeSystem/additional-binding-purpose This expansion generated 26 Mar 2023
This value set contains 10 concepts
Expansion based on Additional Binding Purpose Codes v5.0.0 (CodeSystem)
A required binding, for use when the binding strength is 'extensible' or 'preferred'
The minimum allowable value set - any conformant system SHALL support all these codes
This value set is used as a required binding (in addition to the base binding (not a replacement), usually in a particular usage context)
This value set is used as an extensible binding (in addition to the base binding (not a replacement), usually in a particular usage context)
This value set is a candidate to substitute for the overall conformance value set in some situations; usually these are defined in the documentation
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
This is the value set that is preferred in a given context (documentation should explain why)
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
This value set is a good set of codes to start with when designing your system
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: