Cancer dict v2_0

307 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
307
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
1
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Cancer dict v2_0

  1. 1. NEW ZEALAND CANCER REGISTRY DATA DICTIONARY Version 2.0 October 2008
  2. 2. NZCR Data Dictionary Front PagesReproduction of materialThe Ministry of Health (‘the Ministry’) permits the reproduction of material from this publication withoutprior notification, providing all the following conditions are met: the information must not be used forcommercial gain, must not be distorted or changed, and the Ministry must be acknowledged as thesource.DisclaimerThe Ministry of Health gives no indemnity as to the correctness of the information or data supplied. TheMinistry of Health shall not be liable for any loss or damage arising directly or indirectly from the supplyof this publication.All care has been taken in the preparation of this publication. The data presented was deemed to beaccurate at the time of publication, but may be subject to change. It is advisable to check for updates tothis publication on the Ministry’s web site at http://www.moh.govt.nz.Reporting environmentsReporting environments such as Business Objects and data extracts will not necessarily contain all datadescribed in this Data Dictionary.PublicationsA complete list of the Ministry’s publications is available from Ministry of Health, PO Box 5013,Wellington, or on the Ministy’s web site.Any enquiries about or comments on this publication should be directed to:Information Services Statistics and ReportingSector ServicesInformation DirectorateMinistry of HealthPO Box 5013WellingtonPhone: (04) 922 1800 Fax: (04) 922-1899Email: publications@moh.govt.nzPublished by the Ministry of Health© 2008, Ministry of HealthVersion: 2.0 Ministry of HealthOctober 2008
  3. 3. NZCR Data Dictionary Front PagesIntroductionObjectives The objectives of the Ministry of Health (‘the Ministry’) Data Dictionaries are to: • describe the information available within the National Collections • promote uniformity, availability and consistency across the National Collections • support the use of nationally agreed protocols and standards wherever possible • promote national standard definitions and make them available to users. It is hoped that the greater level of detail along with clear definitions of the business rules around each element will assist with providing and using the data.Audiences The target audiences for Data Dictionaries are data providers, software developers, and data users.Format All data element definitions in the Data Dictionaries are presented in a format based on the Australian Institute of Health and Welfare National Health Data Dictionary. This dictionary is based on the ISO/IEC Standard 11179 Specification and Standardization of Data Elements—the international standard for defining data elements issued by the International Organization for Standardization and the International Electrotechnical Commission. The format is described in detail in Appendix A of this dictionary.Version: 2.0 Ministry of HealthOctober 2008
  4. 4. NZCR Data Dictionary Front PagesTable of ContentsNew Zealand Cancer Registry (NZCR) ............................................................................ front pagesBreast Detail table............................................................................................................................... 1Cancer event ID .................................................................................................................................... 1Cancer group ........................................................................................................................................ 2ER status .............................................................................................................................................. 3Her2 status............................................................................................................................................ 4Her2 test type........................................................................................................................................ 5Histopathology code ............................................................................................................................. 6Lymphovascular invasion flag ............................................................................................................... 7Multicentric or multifocal tumour flag..................................................................................................... 8Positive sentinel nodes ......................................................................................................................... 9PR status ............................................................................................................................................ 10Resection margin ................................................................................................................................ 11Sentinel nodes sampled...................................................................................................................... 12Size of tumour..................................................................................................................................... 13Cancer Event table............................................................................................................................ 14Address city/town................................................................................................................................ 14Address country .................................................................................................................................. 15Address date....................................................................................................................................... 16Address street line 1 ........................................................................................................................... 17Address street line 2 ........................................................................................................................... 18Address suburb................................................................................................................................... 19Assessment decision code.................................................................................................................. 20Basis of diagnosis code ...................................................................................................................... 21Behaviour code ................................................................................................................................... 22Cancer comments............................................................................................................................... 23Cancer event ID .................................................................................................................................. 24Cancer group ...................................................................................................................................... 25Clinical code version ........................................................................................................................... 26Clinical notes....................................................................................................................................... 27Clinician name .................................................................................................................................... 28Coding review flag .............................................................................................................................. 29Country of birth code........................................................................................................................... 30Country of diagnosis code................................................................................................................... 31Date modified...................................................................................................................................... 32Date of birth ........................................................................................................................................ 33Date of histology ................................................................................................................................. 34Date received...................................................................................................................................... 35Deletion reason code .......................................................................................................................... 36Diagnosis date .................................................................................................................................... 37Documentation status ......................................................................................................................... 38Domicile code ..................................................................................................................................... 39Extent of disease code........................................................................................................................ 41Facility code ........................................................................................................................................ 42Family name ....................................................................................................................................... 43First name ........................................................................................................................................... 44Grade of tumour code ......................................................................................................................... 45Grade of tumour description................................................................................................................ 46HCU ID................................................................................................................................................ 47ICD9 site code .................................................................................................................................... 48Laboratory code .................................................................................................................................. 49Laterality code..................................................................................................................................... 50Morphology code ................................................................................................................................ 51Morphology description ....................................................................................................................... 52Multiple tumours flag........................................................................................................................... 53New information flag ........................................................................................................................... 54Nodes tested flag ................................................................................................................................ 55Occupation code ................................................................................................................................. 56Occupation description........................................................................................................................ 57Positive nodes..................................................................................................................................... 58QA OK flag.......................................................................................................................................... 59Version: 2.0 Ministry of HealthOctober 2008
  5. 5. NZCR Data Dictionary Front PagesRecord version.................................................................................................................................... 60Registration date................................................................................................................................. 61Registration source ............................................................................................................................. 62Registration status .............................................................................................................................. 63Second name...................................................................................................................................... 64Sex...................................................................................................................................................... 65Site code ............................................................................................................................................. 66Site description ................................................................................................................................... 67Smoking history flag............................................................................................................................ 68Third name.......................................................................................................................................... 69TNM-M ................................................................................................................................................ 70TNM-N ................................................................................................................................................ 71TNM-T................................................................................................................................................. 72Total nodes sampled........................................................................................................................... 73User modifying record......................................................................................................................... 74User registering record........................................................................................................................ 75Cervix Detail table............................................................................................................................. 76Additional information.......................................................................................................................... 76Cancer event ID .................................................................................................................................. 77Cancer group ...................................................................................................................................... 78Cervix FIGO staging code................................................................................................................... 79Colorectal Detail table ...................................................................................................................... 80ACPS system code ............................................................................................................................. 80Astler and Coller staging system code................................................................................................ 81Cancer event ID .................................................................................................................................. 82Cancer group ...................................................................................................................................... 83Dukes staging system code................................................................................................................ 84Level of direct spread.......................................................................................................................... 85Gleason Detail table.......................................................................................................................... 86Cancer event ID .................................................................................................................................. 86Gleason score..................................................................................................................................... 87Gleason test code ............................................................................................................................... 88Gleason test date................................................................................................................................ 89Primary pattern code........................................................................................................................... 90Record version.................................................................................................................................... 91Secondary pattern code ...................................................................................................................... 92Gynaecology Detail table ................................................................................................................. 93Cancer event ID .................................................................................................................................. 93Cancer group ...................................................................................................................................... 94Corpus FIGO staging code ................................................................................................................. 95Ovary FIGO staging code ................................................................................................................... 96Vagina FIGO staging code.................................................................................................................. 97Vulva FIGO staging code .................................................................................................................... 98Melanoma Detail table ...................................................................................................................... 99Breslows availability code .................................................................................................................. 99Breslows thickness........................................................................................................................... 100Cancer event ID ................................................................................................................................ 101Cancer group .................................................................................................................................... 102Clarks level code .............................................................................................................................. 103Ulceration code ................................................................................................................................. 104Prostate Detail table........................................................................................................................ 105Cancer event ID ................................................................................................................................ 105Cancer group .................................................................................................................................... 106Version: 2.0 Ministry of HealthOctober 2008
  6. 6. NZCR Data Dictionary Front PagesAppendix A: Data Dictionary Template .............................................................................................. iAppendix B: Schemas ....................................................................................................................... iiiAppendix C: Logical Groups of Elements ....................................................................................... ivAppendix D: Code Table Index .......................................................................................................... vAppendix E: Alphabetical Index of Data Elements ........................................................................ viiVersion: 2.0 Ministry of HealthOctober 2008
  7. 7. NZCR Data Dictionary Front PagesNew Zealand Cancer Registry (NZCR)Scope Purpose The New Zealand Cancer Registry is a population-based register of all primary malignant diseases diagnosed in New Zealand, excluding squamous cell and basal cell skin cancers. Data is used in research, and in monitoring and evaluating cancer screening programmes. Content A summary of the variables to be reported is contained in the Cancer Registry Regulations 1994.Start date The NZCR was set up in 1948 primarily using information sent by public hospitals to the NMDS. The Cancer Registry Act 1993 and Cancer Registry Regulations 1994 were introduced to increase reporting of primary cancers in New Zealand. Since the Cancer Registry Regulations 1994 came into effect, laboratory test results have been collected and the data quality and completeness have significantly improved.Guide for use The tumours are classified using the WHO International Statistical Classification of Diseases and Related Health Problems (ICD), and the WHO International Classification of Diseases for Oncology (ICD-O). Before 1997, there was inadequate staging information (ie, reporting of the extent of the disease) and morphology information. The Ministry is now working with clinicians to improve this.Contact information For further information about this collection or to request specific datasets or reports, contact the Ministry of Health’s Analytical Services team on ph 04 496 2000 or e-mail data- inquiries@moh.govt.nz, or visit the Ministy’s web site www.moh.govt.nz.Collection methods – guide for Laboratories are the primary source of cancer data to the NZCR.providers They are required by law to report any new diagnosis of cancer in New Zealand, excluding squamous and basal cell skin cancers. Additional data sources include: Medical Certificates of Causes of Death, Coroners’ Findings, hospital discharge data on the National Minimum Dataset (NMDS), and private hospital discharge returns.Frequency of updates Data is loaded on an ongoing basis. Some types/sites of cancer are of particular interest to researchers and the processing of these cancers is treated as a priority. These types/sites include: melanoma, prostate, breast, cervix, colorectal, and childhood cancers. The processing of data for these priority cancers is kept up to date to within three months of receipt of laboratory reports.Security of data The NZCR is only accessed by authorised Ministry staff for maintenance, data quality, analytical and audit purposes.Version: 2.0 Ministry of HealthOctober 2008
  8. 8. NZCR Data Dictionary Front PagesPrivacy issues The Ministry of Health is required to ensure that the release of information recognises any legislation related to the privacy of health information, in particular the Official Information Act 1982, the Privacy Act 1993 and the Health Information Privacy Code 1994. Information available to the general public is of a statistical and non-identifiable nature. Researchers requiring identifiable data will usually need approval from an Ethics Committee.National reports and The Ministry publishes an annual report Cancer – Newpublications Registrations and Deaths in hard copy and on the Ministry’s web site www.moh.govt.nz. This publication contains detailed information on numbers and rates of cancers according to year of diagnosis. More timely provisional cancer data for the priority sites is posted on the Ministry’s web site www.moh.govt.nz.Data provision Customised datasets or summary reports are available on request, either electronically or on paper. Staff from the Ministry’s Analytical Services team can help to define the specifications for a request and are familiar with the strengths and weaknesses of the data. The Analytical Services team also offers a peer review service to ensure that Minstry of Heatlh data is reported appropriately when published by other organisations. There may be charges associated with data extracts.Version: 2.0 Ministry of HealthOctober 2008
  9. 9. NZCR Data Dictionary Breast Detail tableBreast Detail tableTable name: Breast Detail tableName in database: can.breast_detail Version: 2.0 Version date: 01-Oct-2008Definition: Contains information specific to breast cancer.Guide for Use: Introduced in 2001.Primary Key: Cancer event IDBusiness Key:Relational Rules: A cancer event belonging to the breast cancer group has one breast detail record.Cancer event IDAdministrative statusReference ID: A0261 Version: 2.0 Version date: 01-Oct-2008Identifying and defining attributesName: Cancer event IDName in database: cancer_event_idOther names: Unique cancer record IDElement type: Data elementDefinition: The unique identifier of the cancer event, assigned by the Cancer Registry systemContext: Used by the Cancer Registry system to identify a cancer event and to link it to associated records from other tables. Also used by Cancer Registry staff, to identify and search for an individual cancer event.Relational and representational attributes MandatoryData type: integer Field size: 10 Layout:Data domain:Guide for use: Has been assigned as follows: - for events that had a registered status as at September 2008, the cancer_event_id = unique_cancer_record_id, from the legacy CRS system - for events that were provisional as at September 2008, the cancer_event_id = unique_cancer_temp_id + 1,000,000, from the legacy CRS system - for events created since September 2008, the Cancer Registry system assigns a sequential number (starting at 2,000,001).Verification rules:Collection method:Related data:Administrative attributesSource document:Source organisation:Version: 2.0 Ministry of Health Page 1October 2008
  10. 10. NZCR Data Dictionary Breast Detail tableCancer groupAdministrative statusReference ID: A0281 Version: 2.0 Version date: 01-Oct-2008Identifying and defining attributesName: Cancer groupName in database: cancer_group_codeOther names: Specialist group codeElement type: Data elementDefinition: A code for the speciality group to which the cancer event belongs.Context: Used by Cancer Registry staff to allocate and prioritise processing of cancer registrations. Used by the Cancer Registry system to ensure that an appropriate specialist details record exists for a cancer event. For example, a cancer event belonging to the melanoma group needs a record in the Melanoma Details table.Relational and representational attributes MandatoryData type: char Field size: 2 Layout:Data domain: BR Breast CR Colorectal CX Cervix GN General GY Gynaecology HM Haematology & Lymphoid MN Melanoma PR Prostate RP RespiratoryGuide for use: Introduced in 2001.Verification rules:A registered cancer event must belong to a cancer group that is consistent with the site (the Site code table indicates the allowable cancer group for each site).Collection method: Sourced from pathology reports, hospital discharge event diagnosis codes (from NMDS) or mortality event diagnosis codes (from Mortality).Related data: Site code Site tableAdministrative attributesSource document:Source organisation:Version: 2.0 Ministry of Health Page 2October 2008
  11. 11. NZCR Data Dictionary Breast Detail tableER statusAdministrative statusReference ID: A0290 Version: 1.1 Version date: 01-Oct-2008Identifying and defining attributesName: ER statusName in database: er_status_codeOther names: Oestrogen receptor statusElement type: Data elementDefinition: A code that specifies whether the tumour is oestrogen receptive (ER) or not.Context:Relational and representational attributesData type: varchar Field size: 3 Layout:Data domain: POS Tumour is oestrogen receptive NEG Tumour is not receptive U UnknownGuide for use: Introduced in 2001.Verification rules:Collection method: Sourced from pathology reports.Related data: PR statusAdministrative attributesSource document:Source organisation:Version: 2.0 Ministry of Health Page 3October 2008
  12. 12. NZCR Data Dictionary Breast Detail tableHer2 statusAdministrative statusReference ID: A0293 Version: 1.1 Version date: 01-Oct-2008Identifying and defining attributesName: Her2 statusName in database: her2_status_codeOther names: Serb2, c-erbB-2.Element type: Data elementDefinition: A code for the Her2 status of the tumour.Context: HER2 is an abbreviation for human epidermal growth factor receptor 2.Relational and representational attributesData type: varchar Field size: 3 Layout:Data domain: POS Positive NEG Negative EQU Equivocal U UnknownGuide for use: The value Equivocal was introduced in September 2008, and has been available for use since then.Verification rules:Collection method: Sourced from pathology reports.Related data:Administrative attributesSource document:Source organisation:Version: 2.0 Ministry of Health Page 4October 2008
  13. 13. NZCR Data Dictionary Breast Detail tableHer2 test typeAdministrative statusReference ID: Version: 1.0 Version date: 01-Oct-2008Identifying and defining attributesName: Her2 test typeName in database: her2_test_type_codeOther names:Element type: Data elementDefinition: A code for the Her2 test that was used to determine the Her2 status of the tumour.Context:Relational and representational attributesData type: varchar Field size: 4 Layout:Data domain: IHC Immunohistochemistry FISH Fluorescence in situ hybridization OTH Other U UnknownGuide for use: Only meaningful if Her2 status is POS, NEG or EQU. Introduced in September 2008. For earlier data, the default of U (Unknown) has been used.Verification rules: Mandatory if Her2 status is POS, NEG or EQU.Collection method: Sourced from pathology reports.Related data: Her2 statusAdministrative attributesSource document:Source organisation:Version: 2.0 Ministry of Health Page 5October 2008
  14. 14. NZCR Data Dictionary Breast Detail tableHistopathology codeAdministrative statusReference ID: A0287 Version: 1.1 Version date: 01-Oct-2008Identifying and defining attributesName: Histopathology codeName in database: histopathology_codeOther names:Element type: Data elementDefinition: A code for the type of malignant breast lesion.Context: Used for data-matching with BreastScreen Aotearoa.Relational and representational attributesData type: varchar Field size: 2 Layout:Data domain: 1 Invasive duct not otherwise specified 2 Invasive tubular 3 Invasive cribriform 4 Invasive mucinous (colloid) 5 Invasive medullary 6 Invasive lobular; classical and variant 8 Mixed invasive ductal/lobular 9 Other primary invasive malignancy 10 Other secondary invasive malignancy 11 Non-high-grade DCIS without necrosis 12 Non-high-grade DCIS with necrosis 13 High-grade DCIS with or without necrosis 14 Lobular carcinoma in situ LCIS 19 Other DCIS U Not available/unknown/unsureGuide for use: Introduced in 1998. Mandatory since 2002.Verification rules: Must be consistent with Site, Morphology and Grade of tumour, for registered events.Collection method: Sourced from pathology reports.Related data: Morphology codeAdministrative attributesSource document: BreastScreen Aotearoa Data Management Manual, Version 3.0, 2003Source organisation:Version: 2.0 Ministry of Health Page 6October 2008
  15. 15. NZCR Data Dictionary Breast Detail tableLymphovascular invasion flagAdministrative statusReference ID: A0294 Version: 1.1 Version date: 01-Oct-2008Identifying and defining attributesName: Lymphovascular invasion flagName in database: lymphovascular_invasion_flagOther names: LV invasionElement type: Data elementDefinition: A flag to indicate lymphovascular invasion by the tumour.Context:Relational and representational attributesData type: char Field size: 1 Layout:Data domain: Y Yes N No U UnknownGuide for use: Introduced in 2001.Verification rules:Collection method: Sourced from pathology reports.Related data:Administrative attributesSource document:Source organisation:Version: 2.0 Ministry of Health Page 7October 2008
  16. 16. NZCR Data Dictionary Breast Detail tableMulticentric or multifocal tumour flagAdministrative statusReference ID: A0295 Version: 1.1 Version date: 01-Oct-2008Identifying and defining attributesName: Multicentric or multifocal tumour flagName in database: multi_centric_focal_tumor_flagOther names:Element type: Data elementDefinition: A flag to indicate that the tumour is either multicentric or multifocal.Context:Relational and representational attributesData type: char Field size: 1 Layout:Data domain: Y Yes (tumour is multicentric or multifocal) N No (tumour is neither multicentric nor multifocal) U UnknownGuide for use: Introduced in 2001.Verification rules:Collection method: Sourced from pathology reports.Related data:Administrative attributesSource document:Source organisation:Version: 2.0 Ministry of Health Page 8October 2008
  17. 17. NZCR Data Dictionary Breast Detail tablePositive sentinel nodesAdministrative statusReference ID: Version: 1.0 Version date: 01-Oct-2008Identifying and defining attributesName: Positive sentinel nodesName in database: positive_sentinel_nodes_nbrOther names: Sentinel nodes involvedElement type: Data elementDefinition: The number of sentinel nodes with metastases.Context: Positive sentinel nodes are a subset of the positive nodes.Relational and representational attributesData type: integer Field size: 2 Layout:Data domain: 0 to 99Guide for use: Introduced in September 2008. Only meaningful when Sentinel nodes sampled is populated.Verification rules: Must be less than or equal to the number of Sentinel nodes sampled for registered events.Collection method: Sourced from pathology reports.Related data: Sentinel nodes sampled Total nodes sampled Nodes TestedAdministrative attributesSource document:Source organisation:Version: 2.0 Ministry of Health Page 9October 2008
  18. 18. NZCR Data Dictionary Breast Detail tablePR statusAdministrative statusReference ID: A0291 Version: 1.1 Version date: 01-Oct-2008Identifying and defining attributesName: PR statusName in database: pr_status_codeOther names:Element type: Data elementDefinition: A code that specifies whether the tumour is progesterone receptive (PR) or not.Context: ER status and PR status can both be positive. PR status is not always testedRelational and representational attributesData type: varchar Field size: 3 Layout:Data domain: POS Tumour is progesterone receptive NEG Tumour is not receptive U UnknownGuide for use: Introduced in 2001.Verification rules:Collection method: Sourced from pathology reports.Related data: ER statusAdministrative attributesSource document:Source organisation:Version: 2.0 Ministry of Health Page 10October 2008
  19. 19. NZCR Data Dictionary Breast Detail tableResection marginAdministrative statusReference ID: A0284 Version: 2.0 Version date: 01-Oct-2008Identifying and defining attributesName: Resection marginName in database: resection_marginOther names:Element type: Data elementDefinition: The distance in millimetres between the tumour and the closest resection margin.Context:Relational and representational attributesData type: numeric Field size: Layout:Data domain: 0.00 to 99.99Guide for use: Introduced in 1998. Data entered before September 2008 was rounded to the nearest millimetre.Verification rules:Collection method: Sourced from pathology reports.Related data:Administrative attributesSource document:Source organisation:Version: 2.0 Ministry of Health Page 11October 2008
  20. 20. NZCR Data Dictionary Breast Detail tableSentinel nodes sampledAdministrative statusReference ID: Version: 1.0 Version date: 01-Oct-2008Identifying and defining attributesName: Sentinel nodes sampledName in database: sentinel_nodes_sampled_nbrOther names:Element type: Data elementDefinition: The number of sentinel nodes sampled.Context: Sentinel nodes sampled is a subset of the Total nodes sampled.Relational and representational attributesData type: integer Field size: 2 Layout:Data domain: 1 to 99Guide for use: Introduced in September 2008.Verification rules: Must be greater or equal to the number of Positive sentinel nodes for registered cancer events.Collection method: Sourced from pathology reports.Related data: Positive sentinel nodes Total nodes sampled Positive nodesAdministrative attributesSource document:Source organisation:Version: 2.0 Ministry of Health Page 12October 2008
  21. 21. NZCR Data Dictionary Breast Detail tableSize of tumourAdministrative statusReference ID: A0283 Version: 2.0 Version date: 01-Oct-2008Identifying and defining attributesName: Size of tumourName in database: tumour_sizeOther names:Element type: Data elementDefinition: The size of the tumour at widest point, expressed in millimetres.Context:Relational and representational attributesData type: numeric Field size: Layout:Data domain: 0.01 to 999.99Guide for use: Introduced in 1998. Data entered before September 2008 was rounded to the nearest millimetre.Verification rules:Collection method: Sourced from pathology reports. Where more than one dimension is provided, the largest dimension is recorded.Related data:Administrative attributesSource document:Source organisation:Version: 2.0 Ministry of Health Page 13October 2008
  22. 22. NZCR Data Dictionary Cancer Event tableCancer Event tableTable name: Cancer Event tableName in database: can.cancer_event Version: 2.0 Version date: 01-Oct-2008Definition: Describes a cancer event. It contains demographic and administrative information as well as the main clinical details common to all tumours.Guide for Use: Most cancer events are created and updated manually by Cancer Registry staff using information from pathology reports, death certificates, NMDS health events, Mortality events, NHI records and other cancer events for the same healthcare user. Some cancer events are created automatically by the NMDS and Mortality sweeps, based on recently created events in those systems. These cancer events are then updated manually by Cancer Registry staff using all sources of information.Primary Key: Cancer event IDBusiness Key:Relational Rules: May have a detail record, depending on the cancer group this cancer event belongs to. For example, a cancer event belonging to the melanoma group has a record in the Melanoma Details table.Address city/townAdministrative statusReference ID: A0021 Version: 2.0 Version date: 01-Oct-2008Identifying and defining attributesName: City/townName in database: hcu_cityOther names: Address line 4Element type: Data elementDefinition: The city or town of an address. The healthcare user is believed to have lived at this address around the date of diagnosis of the cancer event.Context: Used to determine the domicile code.Relational and representational attributesData type: varchar Field size: 30 Layout:Data domain: Free textGuide for use:Verification rules: Address suburb and Address city/town may not both be blank.Collection method: Address information is sourced from NHI, pathology reports and other cancer events for the healthcare user. Cancer registry staff determine which of these is the most appropriate.Related data: Address street line 1 Address street line 2 Address suburb Address country Address date Domicile codeAdministrative attributesSource document:Source organisation:Version: 2.0 Ministry of Health Page 14October 2008
  23. 23. NZCR Data Dictionary Cancer Event tableAddress countryAdministrative statusReference ID: A0022 Version: 2.0 Version date: 01-Oct-2008Identifying and defining attributesName: Country/regionName in database: hcu_countryOther names: Address line 5Element type: Data elementDefinition: The external region or country of an address. The healthcare user is believed to have lived at this address around the date of diagnosis of the cancer event.Context: Used to determine the domicile code.Relational and representational attributesData type: varchar Field size: 30 Layout:Data domain: Free textGuide for use:Verification rules:Collection method: Address information is sourced from NHI, pathology reports and other events for the healthcare user. Cancer registry staff determine which of these is the most appropriate.Related data: Address street line 1 Address street line 2 Address suburb Address city/town Address date Domicile codeAdministrative attributesSource document:Source organisation:Version: 2.0 Ministry of Health Page 15October 2008
  24. 24. NZCR Data Dictionary Cancer Event tableAddress dateAdministrative statusReference ID: Version: 1.0 Version date: 01-Oct-2008Identifying and defining attributesName: Address dateName in database: hcu_address_dateOther names:Element type: Data elementDefinition: Possible date at which the health care user lived at the address.Context: Cancer Registry staff need to decide which address is most likely to have been applicable at the date of diagnosis. The address date aids this decisionRelational and representational attributes MandatoryData type: date Field size: Layout:Data domain:Guide for use: Introduced in September 2008. For earlier data, the address date has been set to the Diagnosis date.Verification rules:Collection method: Sourced from the same place as the address, which can be either: - NHI - the last modification date of the current hcu record - Pathology report - the received date of the report - another cancer event - the address date of that cancer event.Related data: Address street line 1 Address street line 2 Address suburb Address city/town Address country Domicile codeAdministrative attributesSource document:Source organisation:Version: 2.0 Ministry of Health Page 16October 2008
  25. 25. NZCR Data Dictionary Cancer Event tableAddress street line 1Administrative statusReference ID: A0018 Version: 1.1 Version date: 01-Oct-2008Identifying and defining attributesName: Address line 1Name in database: hcu_street_addressOther names:Element type: Data elementDefinition: The first line of the street portion of an address. The healthcare user is believed to have lived at this address around the date of diagnosis of the cancer event.Context: Used to determine the domicile code.Relational and representational attributesData type: varchar Field size: 35 Layout:Data domain: Free textGuide for use:Verification rules: Address street line 1 and Address street line 2 may not both be blank.Collection method: Address information is sourced from NHI, pathology reports and other events for the healthcare user. Cancer registry staff determine which of these is the most appropriate.Related data: Address street line 1 Address suburb Address city/town Address country Address date Domicile codeAdministrative attributesSource document:Source organisation:Version: 2.0 Ministry of Health Page 17October 2008
  26. 26. NZCR Data Dictionary Cancer Event tableAddress street line 2Administrative statusReference ID: A0019 Version: 1.1 Version date: 01-Oct-2008Identifying and defining attributesName: Address line 2Name in database: hcu_extra_street_addressOther names:Element type: Data elementDefinition: The second line of the street portion of an address. The healthcare user is believed to have lived at this address around the date of diagnosis of the cancer event.Context: Used to determine the domicile code.Relational and representational attributesData type: varchar Field size: 30 Layout:Data domain: Free textGuide for use:Verification rules: Address street line 1 and Address street line 2 may not both be blank.Collection method: Address information is sourced from NHI, pathology reports and other cancer events for the healthcare user. Cancer registry staff determine which of these is the most appropriate.Related data: Address street line 2 Address suburb Address city/town Address country Address date Domicile codeAdministrative attributesSource document:Source organisation:Version: 2.0 Ministry of Health Page 18October 2008
  27. 27. NZCR Data Dictionary Cancer Event tableAddress suburbAdministrative statusReference ID: A0020 Version: 2.0 Version date: 01-Oct-2008Identifying and defining attributesName: Address suburbName in database: hcu_suburbOther names: Address line 3Element type: Data elementDefinition: The suburb of an address. The healthcare user is believed to have lived at this address around the date of diagnosis of the cancer event.Context: Used to determine the domicile code.Relational and representational attributesData type: varchar Field size: 30 Layout:Data domain: Free textGuide for use:Verification rules: Address suburb and Address city/town cannot both be blank.Collection method: Address information is sourced from NHI, pathology reports and other events for the healthcare user. Cancer registry staff determine which of these is the most appropriate.Related data: Address street line 1 Address street line 2 Address city/town Address country Address date Domicile codeAdministrative attributesSource document:Source organisation:Version: 2.0 Ministry of Health Page 19October 2008
  28. 28. NZCR Data Dictionary Cancer Event tableAssessment decision codeAdministrative statusReference ID: Version: 1.0 Version date: 01-Oct-2008Identifying and defining attributesName: Assessment decision codeName in database: assessment_decision_codeOther names: Decision codeElement type: Data elementDefinition: A code representing an action taken during the processing of the cancer event.Context: Whenever a Cancer Registry user saves a new or modified cancer event, they are prompted to specify an assessment decision. This is used by the system to determine the next status.Relational and representational attributes MandatoryData type: char Field size: 2 Layout:Data domain: DR Delete registered event JP Reject provisional event PP Create provisional event PR Create registered event RR Register provisional event UP Update event CH Checked RS Restore ME Migrate event CU Last CRS updateGuide for use: Introduced in September 2008.Verification rules: The subset of assessment decision codes made available by the Cancer Registry system depends on the users role and the current status of the cancer event.Collection method:Related data: Registration statusAdministrative attributesSource document:Source organisation:Version: 2.0 Ministry of Health Page 20October 2008
  29. 29. NZCR Data Dictionary Cancer Event tableBasis of diagnosis codeAdministrative statusReference ID: A0120 Version: 2.0 Version date: 01-Oct-2008Identifying and defining attributesName: Basis of diagnosis codeName in database: diagnosis_basis_codeOther names: Diagnosis BasisElement type: Data elementDefinition: A code used to describe the single, most valid basis of diagnosis for a primary malignant tumour, or a secondary tumour if the primary tumour site is unknown or cannot be determined.Context:Relational and representational attributesData type: char Field size: 1 Layout:Data domain: 0 Death certificate only 1 Clinical only 2 Clinical investigation 3 Exploratory surgery / autopsy 4 Specific tests 5 Cytology or haematology 6 Histology of metastases 7 Histology of primary 8 Autopsy with histology 9 UnknownGuide for use:Verification rules: Mandatory for registered cancer events. Must be consistent with the Site, Morphology, Extent of disease, and Registration source, for registered cancer events. Must be consistent with Breslows availability, Ulceration and Clarks level for registered melanoma cancer events.Collection method: Sourced from pathology reports, or inferred from the Registration source code.Related data: Site code Morphology code Extent of disease code Registration source codeAdministrative attributesSource document: World Health Organization Manual for Cancer Registry PersonnelSource organisation: World Health Organization/International Association of Cancer Registries (IACR)Version: 2.0 Ministry of Health Page 21October 2008
  30. 30. NZCR Data Dictionary Cancer Event tableBehaviour codeAdministrative statusReference ID: Version: 1.0 Version date: 01-Oct-2008Identifying and defining attributesName: Behaviour codeName in database: behaviour_codeOther names:Element type: Data elementDefinition: A code specifying the behaviour of the tumour, in terms of its malignancy and metastasis.Context:Relational and representational attributes MandatoryData type: char Field size: 1 Layout:Data domain: 0 Benign 1 Uncertain if benign or malignant 2 Carcinoma In Situ 3 Malignant, primary site 6 Malignant, metastatic site 9 Malignant, uncertain if primary or metastatic siteGuide for use: Introduced in September 2008.Verification rules: Benign cancer events must be either rejected or deleted. Must be consistent with Site, for registered cancer events.Collection method: Sourced from pathology reports, hospital discharge event diagnosis codes (from NMDS) or mortality event diagnosis codes (from Mortality).Related data: Site code Morphology code Extent of disease codeAdministrative attributesSource document: International Classification of Diseases for Oncology, Third Edition, 2000Source organisation: World Health OrganizationVersion: 2.0 Ministry of Health Page 22October 2008
  31. 31. NZCR Data Dictionary Cancer Event tableCancer commentsAdministrative statusReference ID: A0271 Version: 2.0 Version date: 01-Oct-2008Identifying and defining attributesName: Cancer commentsName in database: cancer_commentsOther names:Element type: Data elementDefinition: A multi line text field containing notes related to processing the cancer event.Context: Used by Cancer Registry staff.Relational and representational attributesData type: varchar Field size: 2000 Layout:Data domain:Guide for use:Verification rules:Collection method:Related data:Administrative attributesSource document:Source organisation:Version: 2.0 Ministry of Health Page 23October 2008
  32. 32. NZCR Data Dictionary Cancer Event tableCancer event IDAdministrative statusReference ID: A0261 Version: 2.0 Version date: 01-Oct-2008Identifying and defining attributesName: Cancer event IDName in database: cancer_event_idOther names: Unique cancer record IDElement type: Data elementDefinition: The unique identifier of the cancer event, assigned by the Cancer Registry systemContext: Used by the Cancer Registry system to identify a cancer event and to link it to associated records from other tables. Also used by Cancer Registry staff, to identify and search for an individual cancer event.Relational and representational attributes MandatoryData type: integer Field size: 10 Layout:Data domain:Guide for use: Has been assigned as follows: - for events that had a registered status as at September 2008, the cancer_event_id = unique_cancer_record_id, from the legacy CRS system - for events that were provisional as at September 2008, the cancer_event_id = unique_cancer_temp_id + 1,000,000, from the legacy CRS system - for events created since September 2008, the Cancer Registry system assigns a sequential number (starting at 2,000,001).Verification rules:Collection method:Related data:Administrative attributesSource document:Source organisation:Version: 2.0 Ministry of Health Page 24October 2008
  33. 33. NZCR Data Dictionary Cancer Event tableCancer groupAdministrative statusReference ID: A0281 Version: 2.0 Version date: 01-Oct-2008Identifying and defining attributesName: Cancer groupName in database: cancer_group_codeOther names: Specialist group codeElement type: Data elementDefinition: A code for the speciality group to which the cancer event belongs.Context: Used by Cancer Registry staff to allocate and prioritise processing of cancer registrations. Used by the Cancer Registry system to ensure that an appropriate specialist details record exists for a cancer event. For example, a cancer event belonging to the melanoma group needs a record in the Melanoma Details table.Relational and representational attributes MandatoryData type: char Field size: 2 Layout:Data domain: BR Breast CR Colorectal CX Cervix GN General GY Gynaecology HM Haematology & Lymphoid MN Melanoma PR Prostate RP RespiratoryGuide for use: Introduced in 2001.Verification rules:A registered cancer event must belong to a cancer group that is consistent with the site (the Site code table indicates the allowable cancer group for each site).Collection method: Sourced from pathology reports, hospital discharge event diagnosis codes (from NMDS) or mortality event diagnosis codes (from Mortality).Related data: Site code Site tableAdministrative attributesSource document:Source organisation:Version: 2.0 Ministry of Health Page 25October 2008
  34. 34. NZCR Data Dictionary Cancer Event tableClinical code versionAdministrative statusReference ID: Version: 2.0 Version date: 01-Oct-2008Identifying and defining attributesName: Clinical code versionName in database: clinical_coding_system_codeOther names: Diagnosis coding system code, Clinical codes versionElement type: Derived data elementDefinition: An ID for the system of clinical codes used for site and morphology codes.Context: The Cancer Registry uses a subset of clinical coding systems from the Clinical Coding System code table stored in Shared Objects. This subset is listed in the Clinical Coding System table stored in the Cancer Registry. The Cancer Registry system derives the Clinical code system ID from the diagnosis date, using the date ranges specified in the Clinical Coding System table stored in the Cancer Registry.Relational and representational attributesData type: char Field size: 2 Layout:Data domain: 10 ICD-10-AM 1st Edition ICD-O 2nd Edition 11 ICD-10-AM 2nd Edition ICD-O 2nd Edition 12 ICD-10-AM 3rd Edition ICD-O 3rd Edition 13 ICD-10-AM 6th Edition ICD-O 3rd EditionGuide for use: A cancer event record uses the same Clinical code version for both the site code and the morphology code.Verification rules: Must exist in the Clinical Coding System table. Must be in force at the date of diagnosis.Collection method:Related data: Site code Morphology codeAdministrative attributesSource document:Source organisation:Version: 2.0 Ministry of Health Page 26October 2008
  35. 35. NZCR Data Dictionary Cancer Event tableClinical notesAdministrative statusReference ID: A0270 Version: 2.0 Version date: 01-Oct-2008Identifying and defining attributesName: Clinical notesName in database: clinical_notesOther names: Cancer notesElement type: Data elementDefinition: A multi line text field containing supplementary information about the tumour registration.Context:Relational and representational attributesData type: varchar Field size: 2000 Layout:Data domain:Guide for use: Used by the Cancer Registry staff for notes such as recording requests for additional histology reports.Verification rules:Collection method:Related data:Administrative attributesSource document:Source organisation:Version: 2.0 Ministry of Health Page 27October 2008
  36. 36. NZCR Data Dictionary Cancer Event tableClinician nameAdministrative statusReference ID: A0297 Version: 2.0 Version date: 01-Oct-2008Identifying and defining attributesName: Clinician nameName in database: clinician_nameOther names:Element type: Data elementDefinition: The name of the clinician responsible for the treatment of the healthcare user.Context:Relational and representational attributesData type: varchar Field size: 50 Layout:Data domain: Free textGuide for use: Collected for audit and research purposes. Introduced in 2001 for cervical cancers. Introduced in September 2008 for all other cancers.Verification rules:Collection method: Sourced from pathology reports.Related data:Administrative attributesSource document:Source organisation:Version: 2.0 Ministry of Health Page 28October 2008
  37. 37. NZCR Data Dictionary Cancer Event tableCoding review flagAdministrative statusReference ID: Version: 1.0 Version date: 01-Oct-2008Identifying and defining attributesName: Coding review flagName in database: coding_review_flagOther names:Element type: Data elementDefinition: A flag to indicate that the cancer event information should be reviewed.Context: Used by Cancer Registry staff to request a review of the cancer event information by another staff member.Relational and representational attributes MandatoryData type: char Field size: 1 Layout:Data domain: Y Yes N NoGuide for use:Verification rules:Collection method:Related data:Administrative attributesSource document:Source organisation:Version: 2.0 Ministry of Health Page 29October 2008
  38. 38. NZCR Data Dictionary Cancer Event tableCountry of birth codeAdministrative statusReference ID: A0198 Version: 2.0 Version date: 01-Oct-2008Identifying and defining attributesName: Country codeName in database: birth_country_codeOther names:Element type: Data elementDefinition: A code for the country of birth of the healthcare user.Context: Primarily used for epidemiological studies.Relational and representational attributesData type: char Field size: 3 Layout:Data domain: 004 - 999. See the Country of Birth code table on the NZHIS web site at http://www.nzhis.govt.nz/moh.nsf/pagesns/47Guide for use: This is not the latest Statistics NZ country list. Note that the NMDS and Mortality collections are better sources of information about the country of birth of healthcare users than is the Cancer Registry. This is because the Cancer Registry obtains this data while automatically creating cancer events from hospital discharge events or mortality events, but most of these cancer events are subsequently rejected rather than registered.Verification rules:Collection method: Sourced from hospital discharge events (from NMDS) or mortality events (from Mortality).Related data:Administrative attributesSource document: Statistics NZ Country Code list (NZSCC86).Source organisation:Version: 2.0 Ministry of Health Page 30October 2008
  39. 39. NZCR Data Dictionary Cancer Event tableCountry of diagnosis codeAdministrative statusReference ID: A0198 Version: 2.0 Version date: 01-Oct-2008Identifying and defining attributesName: Country codeName in database: diagnosis_country_codeOther names:Element type: Data elementDefinition: A code for the country in which the cancer event was diagnosed.Context: The Cancer Registry occasionally receives information about cancer events that were diagnosed overseas. These cancer events may still be captured, but are treated differently to those diagnosed in New Zealand. Only cancer events diagnosed in New Zealand are included in the core dataset.Relational and representational attributes MandatoryData type: char Field size: 3 Layout: NNNData domain: 004 - 999. See the Country of Birth code table on the NZHIS web site at http://www.nzhis.govt.nz/moh.nsf/pagesns/47Guide for use: Introduced in September 2008. This is not the latest Statistics NZ country list. This field uses the same code table as the country of birth.Verification rules:Collection method: Sourced from pathology reports.Related data:Administrative attributesSource document: Statistics NZ Country Code list (NZSCC86)Source organisation:Version: 2.0 Ministry of Health Page 31October 2008
  40. 40. NZCR Data Dictionary Cancer Event tableDate modifiedAdministrative statusReference ID: A0265 Version: 2.0 Version date: 01-Oct-2008Identifying and defining attributesName: Date modifiedName in database: updated_tsOther names: Updated timestampElement type: Data elementDefinition: The date and time at which any information about the cancer event was saved to the database.Context: Used by Cancer Registry staff to identify when a cancer event was last worked on. This field is automatically populated by the Cancer Registry system when a cancer event is first created, and is updated whenever the cancer event information is changed. This includes changes to the Cancer Event record, changes to its specialist details (e.g. a Breast Details record), and changes to its list of problems (i.e. Cancer Event Problem records). Updates performed automatically by the system (e.g. creating provisional cancer events during an NMDS sweep) are assigned a pseudo-username (e.g. sysNmds).Relational and representational attributes MandatoryData type: datetime Field size: Layout:Data domain:Guide for use:Verification rules:Collection method:Related data: User modifying recordAdministrative attributesSource document:Source organisation:Version: 2.0 Ministry of Health Page 32October 2008
  41. 41. NZCR Data Dictionary Cancer Event tableDate of birthAdministrative statusReference ID: A0025 Version: 1.1 Version date: 01-Oct-2008Identifying and defining attributesName: Date of birthName in database: hcu_birth_dateOther names: DOB, HCU date of birth, Birth dateElement type: Data elementDefinition: The date on which the healthcare user was born.Context: Required to derive age for demographic analyses. The Cancer Registry stores its own copy of the date of birth, because some of its historical data differs from the NHI. Unlike NHI, partial dates are not supported in the Cancer Registry system.Relational and representational attributes MandatoryData type: date Field size: Layout:Data domain: Valid datesGuide for use: For some events before 1993, the 15/6 or 15/month (if the month was known) default date model still exists where there was no way to establish if the date is real or a default.Verification rules: Must be on or before the Diagnosis date. Should be the same as the date of birth in NHI. Age at diagnosis, which is derived from Date of birth, should be consistent with the Site for registered cancer events.Collection method: Sourced from NHI for new cancer events.Related data: Diagnosis date Date of birth flagAdministrative attributesSource document:Source organisation:Version: 2.0 Ministry of Health Page 33October 2008
  42. 42. NZCR Data Dictionary Cancer Event tableDate of histologyAdministrative statusReference ID: Version: 1.0 Version date: 01-Oct-2008Identifying and defining attributesName: Date of histologyName in database: histology_dateOther names:Element type: Data elementDefinition: The date of the histology report for the definitive procedure, or for cervical cancer events, the date of the first biopsy.Context: Used for audit purposes.Relational and representational attributesData type: date Field size: Layout:Data domain:Guide for use: Introduced in September 2008.Verification rules: Must be between the Diagnosis date and the Date of death inclusive.Collection method: Sourced from pathology reports.Related data:Administrative attributesSource document:Source organisation:Version: 2.0 Ministry of Health Page 34October 2008
  43. 43. NZCR Data Dictionary Cancer Event tableDate receivedAdministrative statusReference ID: Version: 2.0 Version date: 01-Oct-2008Identifying and defining attributesName: Date receivedName in database: received_dateOther names:Element type: Data elementDefinition: The date when the source information about the cancer event was received by the Cancer Registry.Context:Relational and representational attributes MandatoryData type: date Field size: Layout:Data domain:Guide for use: Introduced in September 2008.Verification rules:Collection method: Sourced from the date the pathology report was received by the Ministry of Health. For cancer events sourced from hospital discharge events (from NMDS) or mortality events (from Mortality), it is usually set to the date the cancer event record was created in the Cancer Registry system.Related data: Registration sourceAdministrative attributesSource document:Source organisation:Version: 2.0 Ministry of Health Page 35October 2008
  44. 44. NZCR Data Dictionary Cancer Event tableDeletion reason codeAdministrative statusReference ID: A0272 Version: 2.0 Version date: 01-Oct-2008Identifying and defining attributesName: Deletion reason codeName in database: deletion_reason_codeOther names:Element type: Data elementDefinition: The reason for deleting a registered record in the Cancer Registry.Context:Relational and representational attributesData type: char Field size: 1 Layout:Data domain: 1 Registered in error 2 Primary already registered 3 Squamous cell carcinoma of skin 4 Duplicate Registration/Merged HCU 5 Other - see clinical notesGuide for use: Used by Cancer Registry staff. Introduced in September 2008. Prior to then, the reason for deletion was captured as text, which now appears in the clinical notes, along with a deletion reason code of 5.Verification rules: Required for cancer events with a status of Deleted.Collection method:Related data:Administrative attributesSource document:Source organisation:Version: 2.0 Ministry of Health Page 36October 2008
  45. 45. NZCR Data Dictionary Cancer Event tableDiagnosis dateAdministrative statusReference ID: A0233 Version: 1.1 Version date: 01-Oct-2008Identifying and defining attributesName: Diagnosis dateName in database: diagnosis_dateOther names: Date of diagnosisElement type: Data elementDefinition: The date the tumour was diagnosed.Context: Used as the primary date for reporting purposes.Relational and representational attributes MandatoryData type: date Field size: Layout:Data domain: Valid datesGuide for use:Verification rules: Must be between the Date of birth and the Date of death inclusive. Must be no later than the Date of histology. Must not be in the future.Collection method: Sourced from pathology reports, hospital discharge event start date (from NMDS) or mortality event date of death (from Mortality). This is the same as the earliest Date of operation/biopsy or the Date of admission (in a hospital event) or the Date of death if diagnosed on autopsy. If registering from a histology report, this should be the earliest pathology report date. If the only notification of a cancer comes from a Medical Certificate of Causes of Death, the diagnosis date is estimated from the Approximate time between onset and death as reported by the certifying doctor alongside the cancer diagnosis on the certificate.Related data:Administrative attributesSource document:Source organisation:Version: 2.0 Ministry of Health Page 37October 2008
  46. 46. NZCR Data Dictionary Cancer Event tableDocumentation statusAdministrative statusReference ID: A0314 Version: 2.0 Version date: 01-Oct-2008Identifying and defining attributesName: Documentation statusName in database: documentation_status_codeOther names: Document statusElement type: Data elementDefinition: A code to describe documentation available for the cancer registration.Context: Used by Cancer Registry staff to track whether all relevant documentation has been received.Relational and representational attributes MandatoryData type: varchar Field size: 2 Layout:Data domain: 1 All documents received 2 Awaiting pathology report 4 Awaiting other documents 8 No supporting documents 9 No applicable documents 10 Refer to Mortality CollectionGuide for use: Introduced in 2001.Verification rules: Must not be 9 for registered cancer events. Should not be 8 for registered cancer events that have a date of death.Collection method:Related data:Administrative attributesSource document:Source organisation:Version: 2.0 Ministry of Health Page 38October 2008
  47. 47. NZCR Data Dictionary Cancer Event tableDomicile codeAdministrative statusReference ID: A0023 Version: 1.1 Version date: 01-Oct-2008Identifying and defining attributesName: Domicile codeName in database: hcu_domicile_codeOther names:Element type: Data elementDefinition: The Statistics NZ Health Domicile Code based on an address. The healthcare user is believed to have lived at this address around the date of diagnosis of the cancer event.Context: Based on the address fields. Required for demographic analyses. Domicile codes are key variables for determining the characteristics of the population that are using the health sector.Relational and representational attributes MandatoryData type: char Field size: 4 Layout: XXNNData domain: See the Domicile code table on the NZHIS web site at http://www.nzhis.govt.nz/moh.nsf/pagesns/47. For further information or a printed copy of the code table, contact the Publications Officer. Contact details are given at the front of this dictionary.Guide for use: The Domicile code used for health collections is a four-digit Health Domicile Code specially created by Statistics NZ from their six-digit Census Area Unit Code. This field contains 4 versions of the Health Domicile code, one for each of the 1991, 1996, 2001 and 2006 censuses. The series of Domicile codes used depends on the Diagnosis date. No Domicile codes were migrated for registrations before 1976, as the data is unreliable for those records. Before July 1993 Domicile was coded using the 1986 Census Domicile codes. This data has been mapped to the 1991 codes. The 1991 code is used from 1 July 1993 to 31 December 1997. The 1996 code is used from 1 January 1998 to 31 December 2002. The 2001 code is used from 1 January 2003 to 31 December 2007 The 2006 code is used from 1 January 2008 For retrospective cancer registrations (ie, late notifications) the Domicile code is assigned from the appropriate census code table relating to the year of diagnosis. In such cases, the Domicile code may not truly represent the domicile at the time of diagnosis, as the address at the time of diagnosis may not be reported. Care needs to be exercised when analysing pre-1993 data in terms of population, as the 1991 census split a large number of the 1986 codes into two or more new Domicile codes. As it was not possible to accurately attribute particular registrations to the correct new code, only one of the new multiple codes could be chosen for each old code. This can result in some areas showing no registrations for one code and an over-representation of registrations for the other domicile. Since 1996, Domicile code has been automatically assigned on the NHI database using the address provided. This can result in rural addresses being assigned to an urban Domicile code where there is insufficient data to generate the correct code. This is because the automated software relies on generating a post code in order to determine where in a related table it should look to find the code.Verification rules: The code must be one that was in force at the diagnosis date.Collection method: For addresses sourced from NHI, the Domicile code is also sourced from NHI. For addresses sourced from pathology reports, the Domicile code is manually determined using a Statistics NZ Streets database.Related data: Address street line 1 Address street line 2 Address suburb Address city/town Address country Address dateVersion: 2.0 Ministry of Health Page 39October 2008
  48. 48. NZCR Data Dictionary Cancer Event tableAdministrative attributesSource document:Source organisation: Statistics NZVersion: 2.0 Ministry of Health Page 40October 2008

×