California Cancer Reporting System Standards, Volume III
A brief definition or description of the data item and its use.
Level(s) in which this element resides in the database. The primary data levels in the CCR database are:
Contains consolidated information about the patient based on all incoming abstracts, death clearance, corrections, and follow-up, regardless of tumor.
Contains consolidated information about each tumor based on all incoming abstracts, corrections, follow-up, and geocoding data for that tumor.
Contains one record per reporting facility containing information as reported on each incoming abstract (and its subsequent corrections and active follow-up) for a given tumor.
Number indicating the length of the field. If the number is followed by an asterisk (*) and another number, the first number indicates the length of the individual field while the second number indicates the number of occurrences of that field there are. For example, 1*20 X means 20 occurrences of a 1 character long alphanumeric field.
The acceptable data values for this item. Definitions of the valid data values are frequently shown. For information about coding instructions, refer to Volume I and Volume II. The CCR item edit number is shown in parentheses. If an automatic item edit exists in the CCR edits software, then the edit error number is shown in parentheses.
Either the software vendor item number and field name on the input record (see Volume II) and how to translate it if needed or instructions for computer generating the value.
These are the rules that the computer uses to consolidate/update this item when there is another incoming abstract pertaining to this patient/tumor set. If the stated conditions are not met, the database remains unchanged. Th2 conflicting data item values may be reported for manual resolution.
Whenever the word "updated" appears in the rules referring to a data item it means that the item should be evaluated for the condition documented after it has been through its consolidation routine. (For example, the death information fields may have as part of their update logic "if updated VITAL-STAT = 0 (patient is dead), then" do something. That means that whether the patient was originally alive or dead on the Main data base, if the patient is now on the data base as dead after the incoming abstract is applied, then the rules that follow are to be applied.)
These rules also apply for updating this item based on an on-line correction of an item at a more detailed level. (For example, an update may be made to a treatment at this hospital field, which may cause the treatment summary data to be updated automatically.)
When one hospital reports the same patient/tumor set more than once the incoming abstract is suspended; no change is made to the data on either database.
This designates whether or not this item is to be reported by SEER participants to the NCI SEER program.
Edits performed by programs for data integrity checks with other data elements. CCR software edit numbers and CCR edit names are shown in parentheses.
Edits performed between different records within a patient or tumor set or between admissions. CCR software edit numbers and CCR edit names are shown in parentheses.
Present for manual review the different values for this data item when an incoming record either does not match the record already on the Main database or when it differs enough that computerized consolidation rules (see Update) cannot resolve the discrepancies.