| Lvl | Code | Display | Definition | Not Selectable | Status |
| 1 | maximum | Maximum Binding | A required binding, for use when the binding strength is 'extensible' or 'preferred' | | 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 | 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 | preferred | Preferred Binding | This is the value set that is preferred in a given context (documentation should explain why) | | |
| 1 | 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 | | |
| 1 | starter | Starter Binding | This value set is a good set of codes to start with when designing your system | | |
| 1 | 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 | | |
| 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 | | |