5.3.2 Null Flavor
Prev | 5.3 Encoding | Next

### 5.3.2 Null Flavor

Information technology solutions store and manage data, but sometimes data are not available: an item may be unknown, not relevant, or not computable or measurable. In HL7 v3, a flavor of null, or nullFlavor, describes the reason for missing data.

For example, if a patient arrives at an Emergency Department unconscious and with no identification, a null flavor is used to represent the lack of information. The patient's birth date could be represented with a null flavor of "NAV", which is the code for "temporarily unavailable". When the patient regains consciousness or a relative arrives, we expect to be able to obtain the patient's birth date.

Example 5.3.2-1. nullFlavor example

    <birthTime nullFlavor="NAV"/> <!--coding an unknown birthdate-->

Use null flavors for unknown, required, or optional attributes:

NI

  No information. This is the most general and default null flavor.

NA

  Not applicable. Known to have no proper value (e.g., last menstrual period for a male).

UNK

  Unknown. A proper value is applicable, but is not known.

ASKU

  Asked, but not known. Information was sought, but not found (e.g., the patient was asked but did not know).

NAV

  Temporarily unavailable. The information is not available, but is expected to be available later.

NASK

  Not asked. The patient was not asked.

MSK

  Masked. 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.

OTH

  Other. The actual value is not an element in the value domain of a variable. (e.g., concept not provided by required code system).

The above null flavors are commonly used in clinical documents. For the full list and descriptions, see the nullFlavor vocabulary domain in the HL7 v3 Vocabulary referenced by the CDA specification.

Any SHALL conformance requirement on an element may use nullFlavor, unless nullFlavor is explicitly disallowed (as indicated by noNull, see Section 5.2.7 Value Conformance). SHOULD and MAY conformance requirements may also use nullFlavor. nullFlavor does not apply to conformance requirements on attributes.

The encoding of nullFlavor as an attribute of the data type element is not shown in the templates, hence there is no business name associated with the attribute.

### Note

Production logic based on Business Names needs to provide a mechanism for assignment of a value to the nullFlavor attribute as an alternative for a value for the element. Specification of such production logic is outside the scope of this Standard.

Example 5.3.2-2. XML example of allowed nullFlavors when element is required

    <entry>
        <observation classCode="OBS" moodCode="EVN">
            <id nullFlavor="NI"/>
            <code nullFlavor="OTH">
                <originalText>New Grading system</originalText>
            </code>
            <statusCode code="completed"/>
            <effectiveTime nullFlavor="UNK"/>
            <value xsi:type="CD" nullFlavor="NAV">
                <originalText>Spiculated mass grade 5</originalText>
            </value>
        </observation>
    </entry>

Prev | Up | Next
5.3 Encoding | Home | 5.3.3 Unknown Information