layout.fixed.naaccr.doc.naaccr22.rxDateOtherFlag.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.
Item #
Length
Source of Standard
Year Implemented
Version Implemented
Year Retired
Version Retired
1251
2
NAACCR
2010
12
NAACCR XML: Tumor.rxDateOtherFlag
Alternate Names
RX Date--Other Flag
Description
This flag explains why no appropriate value is in the field, RX Date Other [1250].
Formerly RX Date--Other Flag.
Rationale
Before Version 12 (through 2009 diagnosis), 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 value (e.g, unknown if other therapy administered).
11
No proper value is applicable in this context (e.g., no other treatment administered; autopsy only case).
12
A proper value is applicable but not known. This event occurred, but the date is unknown (e.g., other therapy administered but the date is unknown).
15
Information is not available at this time, but it is expected that it will be available later (e.g., other therapy is planned as part of the first course of therapy, but had not been started at the time of the most recent follow-up).
Blank
A valid date value is provided in item RX Date Other [1250], 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.