California Cancer Reporting System Standards, Volume III
Data Item | CCR ID | NAACCR ID |
Date Surg Proc 1 | E1591 |
None. State Requestor |
Date Surg Proc 2 | E1596 |
None. State Requestor |
Date Surg Proc 3 | E1601 |
None. State Requestor |
Date each surgical procedure was performed. Data items displayed but not visually edited in central system in CP 22.
Admissions
3 * 8
Date fields are recorded in the D1 date format of year, month, day (CCYYMMDD). Month and day must have leading zeros for values 01...09.
General Date Editing Rules:
Date fields are recorded in the D1 date format of year, month, day (CCYYMMDD). Month and day must have leading zeros for values 01...09.
The following date format is allowed:
CCYYMMDD Century+Year, Month and Day are provided.
Dates are checked first to ensure they conform to one of these formats, then for errors in the components. Checking stops on the first non-valid situation.
Range Checking:
Lowest allowed value: January 1, 1850 (or in D1 format: 18500101).
Highest allowed value: current system date.
The month is checked to ensure it falls within range 01...12.
The day is checked to ensure it falls within range for that specific month. Accommodation is made for leap years.
If the record version is version 12 or later, then upload with no conversion.
If the record version is earlier than 12, then perform the following conversions in this order:
Right-justify and zero-fill the date to 8 digits.
Convert MMDDYYYY to YYYYMMDD.
Convert Date Surg Proc 1 - 3 and Date Surg Proc 1 - 3 Flag in the same manner as described in the Eureka Process Specification: 2010 Data Conversions document.
If steps 1 and 2 are the only changes made to the date, then DO NOT record them in the audit log.
Manual Update or Correction applied to a date or its associated date flag *, **
*If a full or partial date is entered in the date field, then automatically change the associated flag to blank; If a numeric associated flag code is selected/entered, then automatically change the date to blank
**If the date is changed, it is now later*** than Date of Last Contact, and Vital Status is alive(1), then automatically update Date of Last Contact with the new date and reset Date of Last Contact Flag to blank (this update applies to the patient and admission’s Date of Last Contact and Vital Status). In addition, if one or more of these dates is changed, the corresponding admission automatic updates and consolidation procedures upon manual update to Date Surg Proc1-3 required for RX Date—Surgery, RX Date—Most Defin Surg, Hosp_Surg_Prim_Sum, Surg_Prim_First, Date_Surg_Prim_First, and Hosp_Surg_Prim_First must be performed.
*** With year, month, and/or day potentially blank, a completely known date could appear to be later because it is a larger number than a partial later date. Thus, to test for the latest date among known full or partial dates, use these tests in this order:
If one of the known dates’ years is later than (greater than) the other date's year being compared or if it is the only known year/date, then that date is the latest known date
If multiple known dates have the same latest year, but only one of them has a latest known month, then that is the latest known date
If multiple known dates have the same latest year & month, but only one of them has a latest known day, then that is the latest known date
Yes
IF879 Date Surg Proc 3, Date Flag
IF881 Date Surg Proc 2, Date Flag
IF883 Date Surg Proc 1, Date Flag
IF1144: Class of Case 20-22, Treatment
1/1/98 |
DATE-SURG-PROC (1) initialized to 99999999 for 1998 data changes. |
3/26/03 |
Updated the C/N #s in Source to the correct numbers. Allowable Values changed for DC Only cases to code 9’s instead of 0’s. Added logic to Interfield edit 4) for DC Only cases. |
3/03/04 |
Removed IF 1-4) and Admission Update logic that pertains to Proc 1-3. |
1/08/07 |
Added Update text. |
2010 |
2010 Data Item Changes: Updated Allowable Values, Source and Update logic to match NAACCRv12 date changes. |
7/8/2011 |
General Date Editing Rules and Range Checking updated for additional clarity. However, the intent of the date rules remain the same as the 2010 update. |