This is the Continuous Integration Build of FHIR (will be incorrect/inconsistent at times).
See the Directory of published versions

4.3.2.58 CodeSystem http://hl7.org/fhir/CodeSystem/additional-binding-purpose

Responsible Owner: FHIR Infrastructure Work Group

Normative

Use Context: Country: Global (Whole world)

• Narrative
• XML
• JSON
• TTL

"This Code system is used in the following FHIR core-defined or referenced value sets:

• ValueSet: Additional Binding Purpose ValueSet (Additional Binding Purpose)

4.3.2.58.1 Definition

Additional Binding Purpose

4.3.2.58.2 Content

Generated Narrative: CodeSystem additional-binding-purpose

Last updated: 2025-11-03T21:06:08.628Z

Profile: Shareable CodeSystem

Properties

This code system defines the following properties for its concepts

Name	Code	URI	Type	Description
Not Selectable	abstract	http://hl7.org/fhir/concept-properties#notSelectable	boolean
Status	status	http://hl7.org/fhir/concept-properties#status	code	A code that indicates the status of the concept. Typical values are active, experimental, deprecated, and retired

Concepts

This case-sensitive code system http://hl7.org/fhir/CodeSystem/additional-binding-purpose defines the following codes in a Is-A hierarchy:

Lvl	Code	Display	Definition	Not Selectable	Status	Copy
1	maximum	Maximum Binding	A required binding, for use when the binding strength is 'extensible' or 'preferred'. This is deprecated - it is equivalent to `required`		deprecated
1	minimum	Minimum Binding	The minimum allowable value set - any conformant system SHALL support all these codes
1	required	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)
1	extensible	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)
1	candidate	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
1	current	Current Binding (required)	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
1	current-extensible	Current Binding (extensible)	New records are required to use this value set if a concept applies, 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
1	best-practice	Best practice Binding	Instances are strongly encouraged to have a code from this value set and, if they enable 'best practice' validation mode, they will receive a 'best practice violation' message for data elements that do not include a code from this value set. This might be part of an overall best practice scoring profile, or advice on a more general profile.
1	open	Open Binding	A Binding that doesn't make any restrictions on use, but is provided for other purposes	true
2	preferred	Preferred Binding	This is the value set that is preferred in a given context (documentation should explain why)
2	ui	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
2	starter	Starter Binding	This value set is a good set of codes to start with when designing your system
2	component	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 code systems defined as part of FHIR.

Explanation of the columns that may appear on this page: