Extensions for Using Data Elements from FHIR R5 in FHIR R4 - Downloaded Version null See the Directory of published versions
| Official URL: http://hl7.org/fhir/uv/xver/ValueSet/R5-additional-binding-purpose-for-R4 | Version: 0.1.0 | |||
| Standards status: Trial-use | Maturity Level: 5 | Computable Name: R5AdditionalBindingPurposeForR4 | ||
This cross-version ValueSet represents content from http://hl7.org/fhir/ValueSet/additional-binding-purpose|5.0.0 for use in FHIR R4.
This value set is part of the cross-version definitions generated to enable use of the
value set http://hl7.org/fhir/ValueSet/additional-binding-purpose|5.0.0 as defined in FHIR R5
in FHIR R4.
The source value set is bound to the following FHIR R5 elements:
ElementDefinition.binding.additional.purposeNote that all concepts are included in this cross-version definition because no concepts have compatible representations
Following are the generation technical comments:
FHIR ValueSet http://hl7.org/fhir/ValueSet/additional-binding-purpose|5.0.0, defined in FHIR R5 does not have any mapping to FHIR R4
References
This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)
http://hl7.org/fhir/CodeSystem/additional-binding-purpose version 📍5.0.0| Code | Display | Definition |
| 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 |
| 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 |
| 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 |
| 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) |
| maximum | Maximum Binding | A required binding, for use when the binding strength is 'extensible' or 'preferred' |
| minimum | Minimum Binding | The minimum allowable value set - any conformant system SHALL support all these codes |
| preferred | Preferred Binding | This is the value set that is preferred in a given context (documentation should explain why) |
| 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) |
| starter | Starter Binding | This value set is a good set of codes to start with when designing your system |
| 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 |
This value set expansion contains 10 concepts.
| System | Version | Code | Display | Definition | JSON | XML |
http://hl7.org/fhir/CodeSystem/additional-binding-purpose | 5.0.0 | 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 | ||
http://hl7.org/fhir/CodeSystem/additional-binding-purpose | 5.0.0 | 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 | ||
http://hl7.org/fhir/CodeSystem/additional-binding-purpose | 5.0.0 | 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 | ||
http://hl7.org/fhir/CodeSystem/additional-binding-purpose | 5.0.0 | 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) | ||
http://hl7.org/fhir/CodeSystem/additional-binding-purpose | 5.0.0 | maximum | Maximum Binding | A required binding, for use when the binding strength is 'extensible' or 'preferred' | ||
http://hl7.org/fhir/CodeSystem/additional-binding-purpose | 5.0.0 | minimum | Minimum Binding | The minimum allowable value set - any conformant system SHALL support all these codes | ||
http://hl7.org/fhir/CodeSystem/additional-binding-purpose | 5.0.0 | preferred | Preferred Binding | This is the value set that is preferred in a given context (documentation should explain why) | ||
http://hl7.org/fhir/CodeSystem/additional-binding-purpose | 5.0.0 | 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) | ||
http://hl7.org/fhir/CodeSystem/additional-binding-purpose | 5.0.0 | starter | Starter Binding | This value set is a good set of codes to start with when designing your system | ||
http://hl7.org/fhir/CodeSystem/additional-binding-purpose | 5.0.0 | 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 |
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. In this scheme, some codes are under other codes, and imply that the code they are under also applies |
| System | 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) |
| 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 |