HL7 Terminology
2.1.0 - Publication

This page is part of the HL7 Terminology (v2.1.0: Release) based on FHIR R4. This is the current published version in it's permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions

: NullFlavor - XML Representation

Raw xml | Download



<CodeSystem xmlns="http://hl7.org/fhir">
  <id value="v3-NullFlavor"/>
  <language value="en"/>
  <text>
    <status value="generated"/>
    <div xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"><p><b>Properties</b></p><table class="grid"><tr><td><b>Code</b></td><td><b>URL</b></td><td><b>Description</b></td><td><b>Type</b></td></tr><tr><td>Specializes</td><td/><td>The child code is a more narrow version of the concept represented by the parent code.  I.e. Every child concept is also a valid parent concept.  Used to allow determination of subsumption.  Must be transitive, irreflexive, antisymmetric.</td><td>Coding</td></tr><tr><td>Generalizes</td><td/><td>Inverse of Specializes.  Only included as a derived relationship.</td><td>Coding</td></tr><tr><td>internalId</td><td>http://terminology.hl7.org/CodeSystem/utg-concept-properties#v3-internal-id</td><td>The internal identifier for the concept in the HL7 Access database repository.</td><td>code</td></tr><tr><td>status</td><td>http://hl7.org/fhir/concept-properties#status</td><td>Designation of a concept's state.  Normally is not populated unless the state is retired..</td><td>code</td></tr><tr><td>HL7usageNotes</td><td>http://terminology.hl7.org/CodeSystem/utg-concept-properties#HL7usageNotes</td><td>HL7 Concept Usage Notes</td><td>string</td></tr><tr><td>subsumedBy</td><td>http://hl7.org/fhir/concept-properties#parent</td><td>The concept code of a parent concept</td><td>code</td></tr></table><p>This code system http://terminology.hl7.org/CodeSystem/v3-NullFlavor defines the following codes:</p><table class="codes"><tr><td><b>Lvl</b></td><td style="white-space:nowrap"><b>Code</b></td><td><b>Display</b></td><td><b>Definition</b></td><td><b>internalId</b></td><td><b>status</b></td><td><b>HL7 Concept Usage Notes</b></td><td><b>Parent</b></td></tr><tr><td>1</td><td style="white-space:nowrap">NI<a name="v3-NullFlavor-NI"> </a></td><td>NoInformation</td><td>**Description:**The value is exceptional (missing, omitted, incomplete, improper). No information as to the reason for being an exceptional value is provided. This is the most general exceptional value. It is also the default exceptional value.</td><td>10610</td><td>active</td><td/><td/></tr><tr><td>2</td><td style="white-space:nowrap">  INV<a name="v3-NullFlavor-INV"> </a></td><td>invalid</td><td>**Description:**The value as represented in the instance is not a member of the set of permitted data values in the constrained value domain of a variable.</td><td>22656</td><td>active</td><td/><td>NI</td></tr><tr><td>3</td><td style="white-space:nowrap">    DER<a name="v3-NullFlavor-DER"> </a></td><td>derived</td><td>**Description:**An actual value may exist, but it must be derived from the provided information (usually an EXPR generic data type extension will be used to convey the derivation expressionexpression .</td><td>22657</td><td>active</td><td/><td>INV</td></tr><tr><td>3</td><td style="white-space:nowrap">    OTH<a name="v3-NullFlavor-OTH"> </a></td><td>other</td><td>**Description:**The actual value is not a member of the set of permitted data values in the constrained value domain of a variable. (e.g., concept not provided by required code system).

**Usage Notes**: This flavor and its specializations are most commonly used with the CD datatype and its flavors. However, it may apply to \*any\* datatype where the constraints of the type are tighter than can be conveyed. For example, a PQ that is for a true measured amount whose units are not supported in UCUM, a need to convey a REAL when the type has been constrained to INT, etc.

With coded datatypes, this null flavor may only be used if the vocabulary binding has a coding strength of CNE. By definition, all local codes and original text are part of the value set if the coding strength is CWE.</td><td>10616</td><td>active</td><td>This flavor and its specializations are most commonly used with the CD datatype and its flavors.  However, it may apply to *any* datatype where the constraints of the type are tighter than can be conveyed.  For example, a PQ that is for a true measured amount whose units are not supported in UCUM, a need to convey a REAL when the type has been constrained to INT, etc. With coded datatypes, this null flavor may only be used if the vocabulary binding has a coding strength of CNE.  By definition, all local codes and original text are part of the value set if the coding strength is CWE.</td><td>INV</td></tr><tr><td>4</td><td style="white-space:nowrap">      NINF<a name="v3-NullFlavor-NINF"> </a></td><td>negative infinity</td><td>Negative infinity of numbers.</td><td>10618</td><td>active</td><td/><td>OTH</td></tr><tr><td>4</td><td style="white-space:nowrap">      PINF<a name="v3-NullFlavor-PINF"> </a></td><td>positive infinity</td><td>Positive infinity of numbers.</td><td>10617</td><td>active</td><td/><td>OTH</td></tr><tr><td>3</td><td style="white-space:nowrap">    UNC<a name="v3-NullFlavor-UNC"> </a></td><td>un-encoded</td><td>**Description:** The actual value has not yet been encoded within the approved value domain.

**Example**: Original text or a local code has been specified but translation or encoding to the approved value set has not yet occurred due to limitations of the sending system. Original text has been captured for a PQ, but not attempt has been made to split the value and unit or to encode the unit in UCUM.

**Usage Notes**: If it is known that it is not possible to encode the concept, OTH should be used instead. However, use of UNC does not necessarily guarantee the concept will be encodable, only that encoding has not been attempted.

Data type properties such as original text and translations may be present when this null flavor is included.</td><td>22185</td><td>active</td><td>If it is known that it is not possible to encode the concept, OTH should be used instead.  However, use of UNC does not necessarily guarantee the concept will be encodable, only that encoding has not been attempted. Data type properties such as original text and translations may be present when this null flavor is included.</td><td>INV</td></tr><tr><td>2</td><td style="white-space:nowrap">  MSK<a name="v3-NullFlavor-MSK"> </a></td><td>masked</td><td>There is information on this item available but it has not been provided by the sender due to security, privacy or other reasons. There may be an alternate mechanism for gaining access to this information.

Note: using this null flavor does provide information that may be a breach of confidentiality, even though no detail data is provided. Its primary purpose is for those circumstances where it is necessary to inform the receiver that the information does exist without providing any detail.</td><td>17932</td><td>active</td><td/><td>NI</td></tr><tr><td>2</td><td style="white-space:nowrap">  NA<a name="v3-NullFlavor-NA"> </a></td><td>not applicable</td><td>Known to have no proper value (e.g., last menstrual period for a male).</td><td>10611</td><td>active</td><td/><td>NI</td></tr><tr><td>2</td><td style="white-space:nowrap">  UNK<a name="v3-NullFlavor-UNK"> </a></td><td>unknown</td><td>**Description:**A proper value is applicable, but not known.

**Usage Notes**: This means the actual value is not known. If the only thing that is unknown is how to properly express the value in the necessary constraints (value set, datatype, etc.), then the OTH or UNC flavor should be used. No properties should be included for a datatype with this property unless:

1.  Those properties themselves directly translate to a semantic of &quot;unknown&quot;. (E.g. a local code sent as a translation that conveys 'unknown')
2.  Those properties further qualify the nature of what is unknown. (E.g. specifying a use code of &quot;H&quot; and a URL prefix of &quot;tel:&quot; to convey that it is the home phone number that is unknown.)</td><td>10612</td><td>active</td><td>This means the actual value is not known.  If the only thing that is unknown is how to properly express the value in the necessary constraints (value set, datatype, etc.), then the OTH or UNC flavor should be used.  No properties should be included for a datatype with this property unless:  Those properties themselves directly translate to a semantic of &quot;unknown&quot;.  (E.g. a local code sent as a translation that conveys 'unknown') Those properties further qualify the nature of what is unknown.  (E.g. specifying a use code of &quot;H&quot; and a URL prefix of &quot;tel:&quot; to convey that it is the home phone number that is unknown.)</td><td>NI</td></tr><tr><td>3</td><td style="white-space:nowrap">    ASKU<a name="v3-NullFlavor-ASKU"> </a></td><td>asked but unknown</td><td>Information was sought but not found (e.g., patient was asked but didn't know)</td><td>10614</td><td>active</td><td/><td>UNK</td></tr><tr><td>4</td><td style="white-space:nowrap">      NAV<a name="v3-NullFlavor-NAV"> </a></td><td>temporarily unavailable</td><td>Information is not available at this time but it is expected that it will be available later.</td><td>10615</td><td>active</td><td/><td>ASKU, NAVU</td></tr><tr><td>3</td><td style="white-space:nowrap">    NASK<a name="v3-NullFlavor-NASK"> </a></td><td>not asked</td><td>This information has not been sought (e.g., patient was not asked)</td><td>10613</td><td>active</td><td/><td>UNK</td></tr><tr><td>3</td><td style="white-space:nowrap">    NAVU<a name="v3-NullFlavor-NAVU"> </a></td><td>Not available</td><td>Information is not available at this time (with no expectation regarding whether it will or will not be available in the future).</td><td>23731</td><td>active</td><td/><td>UNK</td></tr><tr><td>4</td><td style="white-space:nowrap">      <a href="#v3-NullFlavor-NAV">NAV</a></td><td>temporarily unavailable</td><td colspan="5"/></tr><tr><td>3</td><td style="white-space:nowrap">    QS<a name="v3-NullFlavor-QS"> </a></td><td>Sufficient Quantity</td><td>**Description:**The specific quantity is not known, but is known to be non-zero and is not specified because it makes up the bulk of the material. e.g. 'Add 10mg of ingredient X, 50mg of ingredient Y, and sufficient quantity of water to 100mL.' The null flavor would be used to express the quantity of water.</td><td>21436</td><td>active</td><td/><td>UNK</td></tr><tr><td>3</td><td style="white-space:nowrap">    TRC<a name="v3-NullFlavor-TRC"> </a></td><td>trace</td><td>The content is greater than zero, but too small to be quantified.</td><td>21386</td><td>active</td><td/><td>UNK</td></tr><tr><td>1</td><td style="white-space:nowrap">NP<a name="v3-NullFlavor-NP"> </a></td><td>not present</td><td>Value is not present in a message. This is only defined in messages, never in application data! All values not present in the message must be replaced by the applicable default, or no-information (NI) as the default of all defaults.</td><td>10619</td><td>retired</td><td/><td/></tr></table></div>
  </text>
  <url value="http://terminology.hl7.org/CodeSystem/v3-NullFlavor"/>
  <identifier>
    <system value="urn:ietf:rfc:3986"/>
    <value value="urn:oid:2.16.840.1.113883.5.1008"/>
  </identifier>
  <version value="2.0.0"/>
  <name value="NullFlavor"/>
  <title value="NullFlavor"/>
  <status value="active"/>
  <date value="2019-03-20"/>
  <publisher value="Health Level 7"/>
  <contact>
    <name value="Health Level Seven"/>
  </contact>
  <description
               value="A collection of codes specifying why a valid value is not present."/>
  <hierarchyMeaning value="is-a"/>
  <content value="complete"/>
  <property>
    <extension
               url="http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-symmetry">
      <valueCode value="antisymmetric"/>
    </extension>
    <extension
               url="http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-transitivity">
      <valueCode value="transitive"/>
    </extension>
    <extension
               url="http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-reflexivity">
      <valueCode value="irreflexive"/>
    </extension>
    <extension
               url="http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-isNavigable">
      <valueBoolean value="true"/>
    </extension>
    <extension
               url="http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-relationshipKind">
      <valueCode value="Specializes"/>
    </extension>
    <extension
               url="http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-inverseName">
      <valueString value="Generalizes"/>
    </extension>
    <code value="Specializes"/>
    <description
                 value="The child code is a more narrow version of the concept represented by the parent code.  I.e. Every child concept is also a valid parent concept.  Used to allow determination of subsumption.  Must be transitive, irreflexive, antisymmetric."/>
    <type value="Coding"/>
  </property>
  <property>
    <extension
               url="http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-symmetry">
      <valueCode value="antisymmetric"/>
    </extension>
    <extension
               url="http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-transitivity">
      <valueCode value="transitive"/>
    </extension>
    <extension
               url="http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-reflexivity">
      <valueCode value="irreflexive"/>
    </extension>
    <extension
               url="http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-isNavigable">
      <valueBoolean value="true"/>
    </extension>
    <extension
               url="http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-relationshipKind">
      <valueCode value="Generalizes"/>
    </extension>
    <extension
               url="http://terminology.hl7.org/StructureDefinition/ext-mif-relationship-inverseName">
      <valueString value="Specializes"/>
    </extension>
    <code value="Generalizes"/>
    <description
                 value="Inverse of Specializes.  Only included as a derived relationship."/>
    <type value="Coding"/>
  </property>
  <property>
    <code value="internalId"/>
    <uri
         value="http://terminology.hl7.org/CodeSystem/utg-concept-properties#v3-internal-id"/>
    <description
                 value="The internal identifier for the concept in the HL7 Access database repository."/>
    <type value="code"/>
  </property>
  <property>
    <code value="status"/>
    <uri value="http://hl7.org/fhir/concept-properties#status"/>
    <description
                 value="Designation of a concept&#39;s state.  Normally is not populated unless the state is retired.."/>
    <type value="code"/>
  </property>
  <property>
    <code value="HL7usageNotes"/>
    <uri
         value="http://terminology.hl7.org/CodeSystem/utg-concept-properties#HL7usageNotes"/>
    <description value="HL7 Concept Usage Notes"/>
    <type value="string"/>
  </property>
  <property>
    <code value="subsumedBy"/>
    <uri value="http://hl7.org/fhir/concept-properties#parent"/>
    <description value="The concept code of a parent concept"/>
    <type value="code"/>
  </property>
  <concept>
    <code value="NI"/>
    <display value="NoInformation"/>
    <definition
                value="**Description:**The value is exceptional (missing, omitted, incomplete, improper). No information as to the reason for being an exceptional value is provided. This is the most general exceptional value. It is also the default exceptional value."/>
    <property>
      <code value="status"/>
      <valueCode value="active"/>
    </property>
    <property>
      <code value="internalId"/>
      <valueCode value="10610"/>
    </property>
  </concept>
  <concept>
    <code value="NP"/>
    <display value="not present"/>
    <definition
                value="Value is not present in a message. This is only defined in messages, never in application data! All values not present in the message must be replaced by the applicable default, or no-information (NI) as the default of all defaults."/>
    <property>
      <code value="status"/>
      <valueCode value="retired"/>
    </property>
    <property>
      <code value="internalId"/>
      <valueCode value="10619"/>
    </property>
  </concept>
  <concept>
    <code value="NAV"/>
    <display value="temporarily unavailable"/>
    <definition
                value="Information is not available at this time but it is expected that it will be available later."/>
    <property>
      <code value="status"/>
      <valueCode value="active"/>
    </property>
    <property>
      <code value="internalId"/>
      <valueCode value="10615"/>
    </property>
    <property>
      <code value="subsumedBy"/>
      <valueCode value="ASKU"/>
    </property>
    <property>
      <code value="subsumedBy"/>
      <valueCode value="NAVU"/>
    </property>
  </concept>
  <concept>
    <code value="DER"/>
    <display value="derived"/>
    <definition
                value="**Description:**An actual value may exist, but it must be derived from the provided information (usually an EXPR generic data type extension will be used to convey the derivation expressionexpression ."/>
    <property>
      <code value="status"/>
      <valueCode value="active"/>
    </property>
    <property>
      <code value="internalId"/>
      <valueCode value="22657"/>
    </property>
    <property>
      <code value="subsumedBy"/>
      <valueCode value="INV"/>
    </property>
  </concept>
  <concept>
    <code value="OTH"/>
    <display value="other"/>
    <definition
                value="**Description:**The actual value is not a member of the set of permitted data values in the constrained value domain of a variable. (e.g., concept not provided by required code system).

**Usage Notes**: This flavor and its specializations are most commonly used with the CD datatype and its flavors. However, it may apply to \*any\* datatype where the constraints of the type are tighter than can be conveyed. For example, a PQ that is for a true measured amount whose units are not supported in UCUM, a need to convey a REAL when the type has been constrained to INT, etc.

With coded datatypes, this null flavor may only be used if the vocabulary binding has a coding strength of CNE. By definition, all local codes and original text are part of the value set if the coding strength is CWE."/>
    <property>
      <code value="status"/>
      <valueCode value="active"/>
    </property>
    <property>
      <code value="HL7usageNotes"/>
      <valueString
                   value="This flavor and its specializations are most commonly used with the CD datatype and its flavors.  However, it may apply to *any* datatype where the constraints of the type are tighter than can be conveyed.  For example, a PQ that is for a true measured amount whose units are not supported in UCUM, a need to convey a REAL when the type has been constrained to INT, etc. With coded datatypes, this null flavor may only be used if the vocabulary binding has a coding strength of CNE.  By definition, all local codes and original text are part of the value set if the coding strength is CWE."/>
    </property>
    <property>
      <code value="internalId"/>
      <valueCode value="10616"/>
    </property>
    <property>
      <code value="subsumedBy"/>
      <valueCode value="INV"/>
    </property>
  </concept>
  <concept>
    <code value="UNC"/>
    <display value="un-encoded"/>
    <definition
                value="**Description:** The actual value has not yet been encoded within the approved value domain.

**Example**: Original text or a local code has been specified but translation or encoding to the approved value set has not yet occurred due to limitations of the sending system. Original text has been captured for a PQ, but not attempt has been made to split the value and unit or to encode the unit in UCUM.

**Usage Notes**: If it is known that it is not possible to encode the concept, OTH should be used instead. However, use of UNC does not necessarily guarantee the concept will be encodable, only that encoding has not been attempted.

Data type properties such as original text and translations may be present when this null flavor is included."/>
    <property>
      <code value="status"/>
      <valueCode value="active"/>
    </property>
    <property>
      <code value="HL7usageNotes"/>
      <valueString
                   value="If it is known that it is not possible to encode the concept, OTH should be used instead.  However, use of UNC does not necessarily guarantee the concept will be encodable, only that encoding has not been attempted. Data type properties such as original text and translations may be present when this null flavor is included."/>
    </property>
    <property>
      <code value="internalId"/>
      <valueCode value="22185"/>
    </property>
    <property>
      <code value="subsumedBy"/>
      <valueCode value="INV"/>
    </property>
  </concept>
  <concept>
    <code value="INV"/>
    <display value="invalid"/>
    <definition
                value="**Description:**The value as represented in the instance is not a member of the set of permitted data values in the constrained value domain of a variable."/>
    <property>
      <code value="status"/>
      <valueCode value="active"/>
    </property>
    <property>
      <code value="internalId"/>
      <valueCode value="22656"/>
    </property>
    <property>
      <code value="subsumedBy"/>
      <valueCode value="NI"/>
    </property>
  </concept>
  <concept>
    <code value="MSK"/>
    <display value="masked"/>
    <definition
                value="There is information on this item available but it has not been provided by the sender due to security, privacy or other reasons. There may be an alternate mechanism for gaining access to this information.

Note: using this null flavor does provide information that may be a breach of confidentiality, even though no detail data is provided. Its primary purpose is for those circumstances where it is necessary to inform the receiver that the information does exist without providing any detail."/>
    <property>
      <code value="status"/>
      <valueCode value="active"/>
    </property>
    <property>
      <code value="internalId"/>
      <valueCode value="17932"/>
    </property>
    <property>
      <code value="subsumedBy"/>
      <valueCode value="NI"/>
    </property>
  </concept>
  <concept>
    <code value="NA"/>
    <display value="not applicable"/>
    <definition
                value="Known to have no proper value (e.g., last menstrual period for a male)."/>
    <property>
      <code value="status"/>
      <valueCode value="active"/>
    </property>
    <property>
      <code value="internalId"/>
      <valueCode value="10611"/>
    </property>
    <property>
      <code value="subsumedBy"/>
      <valueCode value="NI"/>
    </property>
  </concept>
  <concept>
    <code value="UNK"/>
    <display value="unknown"/>
    <definition
                value="**Description:**A proper value is applicable, but not known.

**Usage Notes**: This means the actual value is not known. If the only thing that is unknown is how to properly express the value in the necessary constraints (value set, datatype, etc.), then the OTH or UNC flavor should be used. No properties should be included for a datatype with this property unless:

1.  Those properties themselves directly translate to a semantic of &quot;unknown&quot;. (E.g. a local code sent as a translation that conveys &#39;unknown&#39;)
2.  Those properties further qualify the nature of what is unknown. (E.g. specifying a use code of &quot;H&quot; and a URL prefix of &quot;tel:&quot; to convey that it is the home phone number that is unknown.)"/>
    <property>
      <code value="status"/>
      <valueCode value="active"/>
    </property>
    <property>
      <code value="HL7usageNotes"/>
      <valueString
                   value="This means the actual value is not known.  If the only thing that is unknown is how to properly express the value in the necessary constraints (value set, datatype, etc.), then the OTH or UNC flavor should be used.  No properties should be included for a datatype with this property unless:  Those properties themselves directly translate to a semantic of &quot;unknown&quot;.  (E.g. a local code sent as a translation that conveys &#39;unknown&#39;) Those properties further qualify the nature of what is unknown.  (E.g. specifying a use code of &quot;H&quot; and a URL prefix of &quot;tel:&quot; to convey that it is the home phone number that is unknown.)"/>
    </property>
    <property>
      <code value="internalId"/>
      <valueCode value="10612"/>
    </property>
    <property>
      <code value="subsumedBy"/>
      <valueCode value="NI"/>
    </property>
  </concept>
  <concept>
    <code value="NINF"/>
    <display value="negative infinity"/>
    <definition value="Negative infinity of numbers."/>
    <property>
      <code value="status"/>
      <valueCode value="active"/>
    </property>
    <property>
      <code value="internalId"/>
      <valueCode value="10618"/>
    </property>
    <property>
      <code value="subsumedBy"/>
      <valueCode value="OTH"/>
    </property>
  </concept>
  <concept>
    <code value="PINF"/>
    <display value="positive infinity"/>
    <definition value="Positive infinity of numbers."/>
    <property>
      <code value="status"/>
      <valueCode value="active"/>
    </property>
    <property>
      <code value="internalId"/>
      <valueCode value="10617"/>
    </property>
    <property>
      <code value="subsumedBy"/>
      <valueCode value="OTH"/>
    </property>
  </concept>
  <concept>
    <code value="ASKU"/>
    <display value="asked but unknown"/>
    <definition
                value="Information was sought but not found (e.g., patient was asked but didn&#39;t know)"/>
    <property>
      <code value="status"/>
      <valueCode value="active"/>
    </property>
    <property>
      <code value="internalId"/>
      <valueCode value="10614"/>
    </property>
    <property>
      <code value="subsumedBy"/>
      <valueCode value="UNK"/>
    </property>
  </concept>
  <concept>
    <code value="NASK"/>
    <display value="not asked"/>
    <definition
                value="This information has not been sought (e.g., patient was not asked)"/>
    <property>
      <code value="status"/>
      <valueCode value="active"/>
    </property>
    <property>
      <code value="internalId"/>
      <valueCode value="10613"/>
    </property>
    <property>
      <code value="subsumedBy"/>
      <valueCode value="UNK"/>
    </property>
  </concept>
  <concept>
    <code value="NAVU"/>
    <display value="Not available"/>
    <definition
                value="Information is not available at this time (with no expectation regarding whether it will or will not be available in the future)."/>
    <property>
      <code value="status"/>
      <valueCode value="active"/>
    </property>
    <property>
      <code value="internalId"/>
      <valueCode value="23731"/>
    </property>
    <property>
      <code value="subsumedBy"/>
      <valueCode value="UNK"/>
    </property>
  </concept>
  <concept>
    <code value="QS"/>
    <display value="Sufficient Quantity"/>
    <definition
                value="**Description:**The specific quantity is not known, but is known to be non-zero and is not specified because it makes up the bulk of the material. e.g. &#39;Add 10mg of ingredient X, 50mg of ingredient Y, and sufficient quantity of water to 100mL.&#39; The null flavor would be used to express the quantity of water."/>
    <property>
      <code value="status"/>
      <valueCode value="active"/>
    </property>
    <property>
      <code value="internalId"/>
      <valueCode value="21436"/>
    </property>
    <property>
      <code value="subsumedBy"/>
      <valueCode value="UNK"/>
    </property>
  </concept>
  <concept>
    <code value="TRC"/>
    <display value="trace"/>
    <definition
                value="The content is greater than zero, but too small to be quantified."/>
    <property>
      <code value="status"/>
      <valueCode value="active"/>
    </property>
    <property>
      <code value="internalId"/>
      <valueCode value="21386"/>
    </property>
    <property>
      <code value="subsumedBy"/>
      <valueCode value="UNK"/>
    </property>
  </concept>
</CodeSystem>