FHIR Tooling Extensions IG
1.3.0 - Release 1.3 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.3.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: Type Profile Constraints Codes

URL oficial: http://hl7.org/fhir/tools/CodeSystem/type-profile-constraints Versión: 1.3.0
Standards status: Informative Nivel de madurez: 1 Nombre computable: TypeProfileConstraintsCS
Otros identificadores: OID:2.16.840.1.113883.4.642.40.1.16.17

How much of what a type profile says on its root element has been merged into the snapshot element that uses the profile

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

This case-sensitive code system http://hl7.org/fhir/tools/CodeSystem/type-profile-constraints defines the following codes:

CodeDisplayDefinition
full Fully merged Everything the type profile constrains on its root element (over and above the underlying type) has been merged into this element in the snapshot: cardinality, value ranges, fixed and pattern values, invariants, bindings, mappings and the must-support and must-have-value flags. A consumer can rely on the snapshot element and does not need to check the root of the type profile separately
partial Partially merged Some of the constraints on the root of the type profile have been merged into this element, but not all of them - for example, the invariants on the root of a resource profile (whose meaning changes when the resource is treated as an element), or a value range that could not be compared. A consumer must still check the root of the type profile
none Not merged None of the constraints on the root of the type profile have been merged into this element - for example, because the element has more than one type profile (any one of which may apply), or more than one type, or because the profile could not be found. A consumer must check the root of the type profile

Descripción de los cuadros anteriores.