FHIR Tooling Extensions IG
1.2.0 - Release 1.2 International bandera

FHIR Tooling Extensions IG, published by HL7 International / FHIR Infrastructure. This guide is not an authorized publication; it is the continuous build for version 1.2.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/FHIR/fhir-tools-ig/ and changes regularly. See the Directory of published versions

CodeSystem: Additional Binding Purpose Codes

URL oficial: http://hl7.org/fhir/tools/CodeSystem/additional-binding-purpose Versión: 1.2.0
Standards status: Informative Nivel de madurez: 4 Nombre computable: AdditionalBindingPurposeCodes
Otros identificadores: OID:2.16.840.1.113883.4.642.40.1.16.5

Additional Binding Purpose

Se hace referencia a este sistema de códigos en la definición de los siguientes conjuntos de valores:

Properties

This code system defines the following properties for its concepts

NameCodeURITypeDescription
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/tools/CodeSystem/additional-binding-purpose defines the following codes in a Is-A hierarchy:

LvlCodeDisplayDefinitionNot SelectableStatus
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

Descripción de los cuadros anteriores.