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

• Contenido narrativo
• XML
• JSON
• TTL

: Type Profile Constraints Codes

xml bruto | Descargar

<CodeSystem xmlns="http://hl7.org/fhir">
  <id value="type-profile-constraints"/>
  <language value="es"/>
  <text>
    <status value="generated"/>
    <div xml:lang="es" lang="es"><hr/><p><b>Spanish</b></p><hr/><p class="res-header-id"><b>Generated Narrative: CodeSystem type-profile-constraints</b></p><a name="es-type-profile-constraints"> </a><a name="es-hctype-profile-constraints"> </a><p>This case-sensitive code system <code>http://hl7.org/fhir/tools/CodeSystem/type-profile-constraints</code> defines the following codes:</p><table class="codes"><tr><td style="white-space:nowrap"><b>Code</b></td><td><b>Display</b></td><td><b>Definition</b></td></tr><tr><td style="white-space:nowrap">full<a name="es-type-profile-constraints-full"> </a></td><td>Fully merged</td><td>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</td></tr><tr><td style="white-space:nowrap">partial<a name="es-type-profile-constraints-partial"> </a></td><td>Partially merged</td><td>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</td></tr><tr><td style="white-space:nowrap">none<a name="es-type-profile-constraints-none"> </a></td><td>Not merged</td><td>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</td></tr></table></div>
  </text>
  <extension
             url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
    <valueInteger value="1"/>
  </extension>
  <extension
             url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
    <valueCode value="fhir"/>
  </extension>
  <extension
             url="http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status">
    <valueCode value="informative">
      <extension
                 url="http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom">
        <valueCanonical
                        value="http://hl7.org/fhir/tools/ImplementationGuide/hl7.fhir.uv.tools"/>
      </extension>
    </valueCode>
  </extension>
  <url value="http://hl7.org/fhir/tools/CodeSystem/type-profile-constraints"/>
  <identifier>
    <system value="urn:ietf:rfc:3986"/>
    <value value="urn:oid:2.16.840.1.113883.4.642.40.1.16.17"/>
  </identifier>
  <version value="1.3.0"/>
  <name value="TypeProfileConstraintsCS"/>
  <title value="Type Profile Constraints Codes"/>
  <status value="active"/>
  <experimental value="false"/>
  <date value="2026-10-05T19:03:47+00:00"/>
  <publisher value="HL7 International / FHIR Infrastructure"/>
  <contact>
    <telecom>
      <system value="url"/>
      <value value="http://www.hl7.org/Special/committees/fiwg"/>
    </telecom>
  </contact>
  <description
               value="How much of what a type profile says on its root element has been merged into the snapshot element that uses the profile"/>
  <jurisdiction>
    <coding>
      <system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/>
      <code value="001"/>
    </coding>
  </jurisdiction>
  <caseSensitive value="true"/>
  <content value="complete"/>
  <concept>
    <code value="full"/>
    <display value="Fully merged"/>
    <definition
                value="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"/>
  </concept>
  <concept>
    <code value="partial"/>
    <display value="Partially merged"/>
    <definition
                value="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"/>
  </concept>
  <concept>
    <code value="none"/>
    <display value="Not merged"/>
    <definition
                value="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"/>
  </concept>
</CodeSystem>