<status value="draft" /> <experimental value="true" /> <date value="2019-02-10T00:11:08+00:00" /> <publisher value="HL7 FHIR Standard" /> <contact> <telecom> <system value="url" /> <value value="http://hl7.org/fhir" /> </telecom> </contact> <description value="Data Element for ElementDefinition.mustSupport" /> <purpose value="Data Elements are defined for each element to assist in questionnaire construction etc" /> <fhirVersion value="4.0.0" /> <mapping> <identity value="v2" /> <uri value="http://hl7.org/v2" /> <name value="HL7 v2 Mapping" /> </mapping> <mapping> <identity value="rim" /> <uri value="http://hl7.org/v3" /> <name value="RIM Mapping" /> </mapping> <mapping> <identity value="iso11179" /> <uri value="http://metadata-standards.org/11179/" /> <name value="ISO 11179" /> </mapping> <mapping> <identity value="dex" /> <uri value="http://ihe.net/data-element-exchange" /> <name value="IHE Data Element Exchange (DEX)" /> </mapping> <mapping> <identity value="loinc" /> <uri value="http://loinc.org" /> <name value="LOINC code for the element" /> </mapping> <kind value="logical" /> <abstract value="false" /> <type value="ElementDefinition.mustSupport" /> <baseDefinition value="http://hl7.org/fhir/StructureDefinition/Element" /> <derivation value="specialization" /> <snapshot> <element id="ElementDefinition.mustSupport"> <path value="ElementDefinition.mustSupport" /> <short value="If the element must be supported" /> <definition value="If true, implementations that produce or consume resources SHALL provide "support" for the element in some meaningful way. If false, the element may be ignored and not supported. If false, whether to populate or use the data element in any way is at the discretion of the implementation." /> <comment value=""Something useful" is context dependent and impossible to describe in the base FHIR specification. For this reason, tue mustSupport flag is never set to true by the FHIR specification itself - it is only set to true in profiles. A profile on a type can always make musSupport = true if it is false in the base type but cannot make mustSupport = false if it is true in the base type. This is done in [Resource Profiles](profiling.html#mustsupport), where the profile labels an element as mustSupport=true. When a profile does this, it SHALL also make clear exactly what kind of "support" is required, as this can mean many things. Note that an element that has the property IsModifier is not necessarily a "key" element (e.g. one of the important elements to make use of the resource), nor is it automatically mustSupport - however both of these things are more likely to be true for IsModifier elements than for other elements." /> <requirements value="Allows a profile to set expectations for system capabilities beyond merely respecting cardinality constraints." /> <min value="0" /> <max value="1" /> <base> <path value="ElementDefinition.mustSupport" /> <min value="0" /> <max value="1" /> </base> <type> <code value="boolean" /> </type> <meaningWhenMissing value="In a base type, where the element is being defined for the first time, the element is assumed to be mustSupport = false. In a profile (a constraint on an existing type), if mustSupport is not specific in either the differentil or the snapshot, the mustSupport value is not changed fro the base definition. Not, though, that the snapshot SHOULD always populate the mustSuppot value" /> <isModifier value="false" /> <isSummary value="true" /> <mapping> <identity value="rim" /> <map value="N/A (MIF territory)" /> </mapping> <mapping> <identity value="iso11179" /> <map value="??" /> </mapping> </element> </snapshot> </StructureDefinition>