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 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. This above list contains those null flavors that are commonly used in clinical documents. For the full list and descriptions, see the nullFlavor vocabulary domain in the CDA normative edition. Any SHALL conformance statement may use nullFlavor, unless the attribute is required or the nullFlavor is explicitly disallowed. SHOULD and MAY conformance statement may also use nullFlavor. Figure : Attribute required contain exactly one [1..1] Problem List (CodeSystem: 1. SHALL code/@code="11450-4" LOINC (CONF:7878) 2.16.840.1.113883.6.1) or 2. contain exactly one [1..1] (CONF:5256). SHALL effectiveTime/@value Figure : Allowed nullFlavors when element is required (with XML examples) 1. contain at least one SHALL [1..*] id 2. contain exactly one SHALL [1..1] code 3. contain exactly one SHALL [1..1] effectiveTime <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>
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 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. This above list contains those null flavors that are commonly used in clinical documents. For the full list and descriptions, see the nullFlavor vocabulary domain in the CDA normative edition. Any SHALL conformance statement may use nullFlavor, unless the attribute is required or the nullFlavor is explicitly disallowed. SHOULD and MAY conformance statement may also use nullFlavor. Figure : Attribute required 1. SHALL contain exactly one [1..1] code/@code="11450-4" Problem List (CodeSystem: LOINC 2.16.840.1.113883.6.1) (CONF:7878) or 2. SHALL contain exactly one [1..1] effectiveTime/@value (CONF:5256). Figure : Allowed nullFlavors when element is required (with XML examples) 1. SHALL contain at least one [1..*] id 2. SHALL contain exactly one [1..1] code 3. SHALL contain exactly one [1..1] effectiveTime <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>