layout.fixed.naaccr.doc.naaccr13.dateConclusiveDxFlag.html Maven / Gradle / Ivy
Go to download
Show more of this group Show more artifacts with this name
Show all versions of layout Show documentation
Show all versions of layout Show documentation
Framework that allows defining file formats (layouts) and use them to read and write data files.
Alternate Name
Item#
Length
Source of Standard
Column #
448
2
NAACCR
575-576
Description
This flag explains why no appropriate value is in the field, Date Conclusive DX [443]. This data item was first available in Volume II Version 12.
Rationale
Before Version 12, date fields included codes that provided information other than dates. As part of an initiative to standardize date fields, new fields were introduced to accommodate non-date information that had previously been transmitted in date fields.
Codes (See Appendix H for the complete Flavors of Null table, which includes the NAACCR codes, HL7 codes and definitions.)
10
No information whatsoever can be inferred from this exceptional (non-date) value. (e.g., unknown if the diagnosis was initially based on ambiguous terminology).
11
No proper value is applicable in this context. (e.g., not applicable, initial diagnosis made by unambiguous terminology (Code 0 in data item Ambiguous Terminology DX [442]).
12
A proper value is applicable but not known (e.g., the initial ambiguous diagnosis was followed by a conclusive term, but the date of the conclusive term is unknown).
15
Information is not available at this time, but it is expected that it will be available later (e.g., accessioned based on ambiguous terminology only (Code 1 in data item Ambiguous Terminology DX [442]).
Blank
A valid date value is provided in item Date Conclusive DX [443], or the date was not expected to have been transmitted.
Comment: This is part of the initiative of the transformation from the old NAACCR date standards to interoperable dates.