<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.definition" /> <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.definition" /> <baseDefinition value="http://hl7.org/fhir/StructureDefinition/Element" /> <derivation value="specialization" /> <snapshot> <element id="ElementDefinition.definition"> <extension url="http://hl7.org/fhir/StructureDefinition/elementdefinition-translatable"> <valueBoolean value="true" /> </extension> <path value="ElementDefinition.definition" /> <short value="Full formal definition as narrative text" /> <definition value="Provides a complete explanation of the meaning of the data element for human readability. For the case of elements derived from existing elements (e.g. constraints), the definition SHALL be consistent with the base definition, but convey the meaning of the element in the particular context of use of the resource. (Note: The text you are reading is specified in ElementDefinition.definition)." /> <comment value="It is easy for a different definition to change the meaning of an element and this can have nasty downstream consequences. Please be careful when providing definitions in a profile." /> <requirements value="To allow a user to state the usage of an element in a particular context." /> <alias value="Description" /> <min value="0" /> <max value="1" /> <base> <path value="ElementDefinition.definition" /> <min value="0" /> <max value="1" /> </base> <type> <code value="markdown" /> </type> <isModifier value="false" /> <isSummary value="true" /> <mapping> <identity value="v2" /> <map value="OM1.6, OM1.41" /> </mapping> <mapping> <identity value="rim" /> <map value="./text" /> </mapping> <mapping> <identity value="iso11179" /> <map value="(Designatable_Item).definition.text acceptability=preferred in default context" /> </mapping> <mapping> <identity value="loinc" /> <map value="TERM DEFINITION/DESCRIPTION(S)" /> </mapping> </element> </snapshot> </StructureDefinition>