Detect Cancer Early (DCE)

Transcription

1 Detect Cancer Early (DCE) Data Submissions & Error Reporting Guide Version 1.6

2 Document Control Version 1.6 Date Issued Author(s) Jenni Munro Leigh Brown Other Related Documents Comments to Document History Version Date Comment Author(s) /08/ st Draft Created Jenni Munro /08/2013 Updated with comments from Brian Murray Jenni Munro /10/2013 Updated to reflect changes made to format of error reporting and other minor changes /10/2013 Updated with comments following external submissions. Jenni Munro Jenni Munro /10/2013 Minor amendments and document finalised Jenni Munro /11/2013 Updated following comments from initial data submissions and added Section 5 Error Reporting Added Jenni Munro /12/2013 Sub section added for Re-submissions Jenni Munro /10/2014 Updated section and Appendix 1 to reflect additional data item for Source of Cancer Referral Jenni Munro Updated section 4.2 to reflect changes in the format of the DCE File Submission Error Report /02/2016 Updated Section 4.2 to reflect changes in the error report recipients /03/2016 Updated Section 5 to reflect update to BI4 (Business Objects) /07/2017 Updated references from DCE Datamarts team to DCE submissions team Leigh Brown Leigh Brown Brendan Craig

3 Contents 1. Introduction Background Purpose Data Submission Resubmissions Submitting Data Getting the data Amending the excel file Checking the Data Saving the extract/converting to CSV Amending the CSV file Submission Number Submitting DCE data using SWIFT Accessing SWIFT Changing your password Submitting a File Successful Upload File Processing & Error Reporting Data Validations Errors Warnings DCE File Submission Datamart Load Notification Error Reporting Logging into Business Objects Error Report Saving Error Reports Appendix 1 Data Submission Template Appendix 2 Data Validation... 26

4 1. Introduction 1.1 Background In February 2012, the SGHSCD Cabinet Secretary for Health, Wellbeing and Cities Strategy announced a programme whose aim is to achieve earlier diagnosis of cancer. The programme will concentrate on breast, colorectal and lung cancer in the first instance. The Scottish Government Detect Cancer Early (DCE) initiative objectives 1 are:- Contributing to the aim of improving 5 year survival rates for people in Scotland diagnosed with cancer By raising cancer awareness and significantly increasing diagnostic capacity in the NHS, the plan is to increase by 25% the number of Scots diagnosed in the first stage of cancer. This plan will start with the three big cancers - lung cancer, breast cancer and colorectal cancer. To support the Detect Cancer Early Initiative ISD have developed a Business Objects Universe i.e the DCE datamart, which can receive and store data submitted by NHS Boards. Appropriately trained and authorised NHS Board staff can securely access and analyse and export the data to compare results against anonymised national data. 1.2 Purpose The purpose of this document is to provide guidance on submitting DCE data to Information Services Division (ISD), this includes: Creating/exporting files Formatting files Uploading files using SWIFT Data validations and loads Error reporting 1 Scottish Government Detect cancer Early Final Implementation Plan cerearly/finalimplementationplan 4

5 2. Data Submission DCE data should be submitted to ISD quarterly, based on patients diagnosed within a defined three month period. Separate files should be submitted for breast, colorectal and lung cancer per Board within four months following diagnosis. Period of diagnosis Last Submission 01 January to 31 March 1 st August 01 April to 30 June 1 st November 01 July to 30 September 1 st February 01 October to 31 December 1 st May Where the submission date falls on a weekend or Statutory Holiday, the next business day will be the submission date. If a submission deadline is not met then ISD will contact the board and ask them to provide a footnote which will be added to the management report. A submission of a quarter must be successfully loaded before the next quarter can be submitted i.e. Quarter 1 must be successfully submitted and loaded before Quarter 2 for the same year can be submitted. 2.1 Resubmissions Data can be resubmitted at any point prior to the yearly publication sign off (this will be communicated to boards via from the Detect Cancer Early Team in ISD). It may be necessary to resubmit data; either because an extra patient has been identified, or a record has been amended. If you need to resubmit data then the whole submission for that treatment quarter must be uploaded. Any submission queries should be directed to nss.dcesubmissions@nhs.net 5

6 2.2 Submitting Data There are 5 distinct steps involved in preparing your data for submission, these are: Getting the data Amending the excel file Checking the data Converting the file to CSV Amending the CSV file Getting the data Files are created by taking an extract from local systems (ecase or TRAK), please refer to local policies and guidance on how to produce an extract. Extracts from ecase must be taken using SSRS. Once the extract has been taken you will be asked which format you would like to export the data. We recommend exporting the data in excel, this will allow you to add the Header row and make any necessary changes prior to converting. If the extract is taken and saved in CSV format prior to making the changes then the file will need to be opened in excel, then changes made and the file reconverted. When the data is exported you will be prompted to either Open or Save the data, please select Open Amending the excel file The excel file extracted using the SSRS report in ecase, at this point only contains the extracted data. This needs to be amended to include a Header Row and a Column Headings row. Header Row Insert a blank row at the top of the worksheet; this will become your header row and must be in row 1. The header row consists of 8 columns and should contain the following information: 1) Project name i.e. DCE 2) Cancer Type Breast, Colorectal or Lung 3) Sending Location the 5 digit location code of the sending site 6

7 4) Quarter indication of which quarter the data relates to 5) Year the calendar year 6) Submission number indicates the sequential number for a file based on the sending location code and cancer type see note below for further information 7) Extract date the date the actual extract was taken in the format YYYYMMDD 8) Record number indicates the numbers of patient records contained within the file Example: The details within the Header Row must match the details recorded within the File Name. Column Headings Insert a blank row under the Header row, this will become your column headings and should be in row two of the file. Column headings vary for each cancer type; and need to be added to the excel extract. Column headings have been incorporated into the submission format to support error reporting and should be entered into row 2 of the submission file. Breast CHINUM, DIAGDATE, HOSPAUD, ct, cn, cm, FIRSTTREATMODE, FIRSTTREATDATE, BSURGDATE, FIRSTAXIL, FINALAXIL, TUMOUR, MAXPATH, TGRADE, EXNODES, INVNODES, MREFER Lung CHINUM,DIAGDATE,HOSP,ORIGIN,TLUNG,NLUNG,MLUNG,MODE1,FIRSTTREATDATE,D SURG,PTLUNG,PNLUNG,PMLUNG Colorectal CHINUM,DDIAG,HOSP,CXR,XDATE,LIVER,LIVERDATE,MODE,FIRSTTREATDATE,FSURG DATE,DIFFERENT,FINALT,FINALN,FINALM,DUKES,LNEXAMINE,LNINVOLVE, MREFER The column headings within a submission file must match exactly to the headings noted above i.e. Location of Diagnosis must be noted as HOSP or HOSPAUD and not HOSPREF. For more information and further details on the data items, including definitions please refer to the Quality Performance Indicator datasets available on the ISD website ( Examples submission files are available in Appendix 1. 7

8 2.2.3 Checking the Data There a couple of nuances when exporting data, therefore it is important to check the data at this point. CHI Numbers By extracting the data from ecase as excel this should retain any leading zeros in CHI numbers. If these have been removed highlight the data within the CHI column and select: Office Cell Format More Number Formats Custom Office 2003 Format Cells Custom In the Type box enter ten zeros ( ), then select OK. Default Dates In ecase some data items have default dates e.g. 09/09/1900 and 10/10/1900, these need to be changed inline with the recording guidance and validation rules i.e. amend all 09/09/1900 dates to 09/09/0909 and all 10/10/1900 dates to 10/10/1010. Blank Fields/Cells With the exception of the dates of surgery variable in the respective datasets there should be no blank cells or null values in the data submissions. If you have any blank cells please review the data and enter the appropriate values as per the guidance in the individual datasets. Please refer to the QPI datasets for further information ( Saving the extract/converting to CSV Once all the amendments have been made to the extracted excel file, it can now be saved as a CSV file. Select File and Save As and enter a file name ensuring it adheres to the naming convention detailed below and change the File Type to CSV. 8

9 The file name consists of 8 parts and it is important to ensure the details in the file name matches the details in the Header Row 1) Project name i.e. DCE 2) Cancer Type Breast, Colorectal or Lung 3) Sending Location the 5 digit location code of the sending site 4) Quarter indication of which quarter the data relates to i.e. Q1 5) Year the calendar year 6) Submission number indicates the sequential number for a file based on the sending location code and cancer type 7) Extract date the date the actual extract was taken in the format YYYYMMDD 8) File type must be a CSV (Comma Separated Values) file Example: dce_colorectal_a111h_q1_2012_1_ csv Amending the CSV file There are known nuances when files are converted from excel to CSV, some of these include the addition of extra commas which indicate additional columns or rows of data and blank fields. These need to be amended before attempting to submit your file, otherwise the submission will fail. To amend the CSV file: i) Source your file ii) Right click on the file name iii) Select Open With, and choose Notepad You will then be able to view your data in the CSV format. If you just open the file then MS Office will auto open the file in excel. Additional commas i) Look for additional commas at the end of the Header row and delete ii) Check for additional commas at the end of the file, these would indicate additional rows or patient records, and delete. 9

10 Blanks Blanks in a CSV file are different from blank values or cells in excel. As noted above with the exception of the date of surgery in each dataset blank cells or null values are not permitted. Again when converting an excel file to CSV the system can sometime put spaces between values, this would show in a CSV file as comma space comma (,,). To remove these: i) Click on Edit, Select all this should highlight all the data within the file ii) Click on Edit, Replace iii) In the Find what box enter a single space; leave the Replace with box blank iii) Click on Replace All Once these changes have been made resave the file ensuring it remains in CSV format. 10

11 2.3 Submission Number Before a file is submitted it is important to check the submission number. During the initial data submission process in November 2013 a number of queries were raised with regards to the submission number. The submission number is sequential and is based on the sending location code and the cancer type. This number should increment following a successful submission for a cancer type for a sending location i.e. each time Ayrshire & Arran successfully submit a Breast file then the submission number should increment for each file based on the previous successful loaded file. If submitting a file which has not passed validations or been loaded onto the datamart the submission number should not increment. Example: Submission File name Status Comments 1 dce_colorectal_a111h_q1_2012_1_ csv Passed This is the first colorectal file submitted from Ayrshire & Arran therefore the submission number is 1. 2 dce_colorectal_a111h_q2_2012_2_ csv Passed This is the second colorectal file from Ayrshire & Arran therefore the submission reference is 2. 3 dce_colorectal_a111h_q3_2012_3_ csv Failed This is the third colorectal file from Ayrshire & Arran therefore the submission reference is 3 4 dce_colorectal_a111h_q3_2012_3_ csv Passed This is the fourth colorectal submission from Ayrshire & Arran however the previous attempted failed therefore the submission reference remains as 3 5 dce_colorectal_a111h_q3_2012_4_ csv Passed This is the fifth colorectal submission from Ayrshire & Arran however they are resubmitting Q3 data. The submission number becomes 4 as the last successful submission reference was 3. As the rest of the file name (and Header record) contain the same details as a previously loaded file the system will overwrite the previous data with the data provided in this file. 11

12 3. Submitting DCE data using SWIFT ISD have a well established system for securely transmitting files from external locations called SWIFT, which stands for Submission With Internet File Transfer. It is designed to be fast, secure and easy to use. It is already utilised for data submissions from Boards for various ISD hosted applications, now including DCE. SWIFT allows Boards to submit data in two ways: Upload a simple facility used to securely transfer a file from the Board to ISD, or Data Validation & Load (DVL) as the name suggests, the data will also be validated as it is uploaded. DCE submissions will be submitted using the Upload functionality. All files will be validated prior to loading into the DCE datamart (see section 4 for further information). 3.1 Accessing SWIFT SWIFT can be accessed by going to i) Enter your username and password. If you do not have a username or password please contact nss.dcesubmissions@nhs.net ii) Click Login 12

13 3.2 Changing your password When logging into SWIFT for the first time it is recommended that you change your password to something more memorable. i) Click on CHANGE USER PASSWORD on the menu bar ii) Enter your existing password in the first text box iii) Enter a new password in the second text box iv) Confirm your new password by typing it again in the third text box v) Click on Submit 13

14 3.3 Submitting a File i) Click on UPLOAD FILE TO ISD on the menu bar ii) Select DCE from the Application drop down menu iii) Add a comment to the Comments box. Note: a file cannot be submitted without a comment iv) Click on Browse v) Source and select the file to be uploaded. Note: only one file can be submitted at a time. vi) Click on Submit An upload status will be displayed on screen When you can see the green status bar (as per image above) that file has been submitted, you can now click on Browse to select another file or click on Logout. 14

15 This confirms that the file transfer has been successful 3.4 Successful Upload Once the file has been submitted the user will receive an notification from SWIFT informing them of a successful upload. Example Note: this only confirms that the file has been successfully sent to ISD. Validation checks are then performed before the data is loaded into the DCE datamart. 15

16 4. File Processing & Error Reporting Once a file has been submitted via SWIFT to ISD it is then passed through the data validation and load process. This process is automatic and the system performs sweeps at 15 minute intervals to check and pick up new files. The sweeps are performed Monday to Friday 7:00am to 7:00pm and are taken on the hour, quarter past the hour, half past the hour and quarter to the hour. Therefore a file submitted at 9:01 will not be picked up until 9:15. This means that the quickest turnaround for a successful file from submission to load is approximately 35minutes and an unsuccessful file from submission to error report is approximately 22minutes. At high times of activity it can take the system some time to catch up, however if you have not received any notifications within 50 minutes of submitting a file please contact nss.dcesubmissions@nhs.net and we will investigate. 4.1 Data Validations Data validations are performed on the 4 areas (as noted in section 2.2); any area that fails validation is recorded in the DCE Error Reporting Universe. The purpose of the Error Reporting datamart is to store information in relation to all error and warning messages generated when files are submitted Errors There are various reasons why a file may fail validation, some common errors include: Error Message Common Issues Guidance Invalid file name File name missing a component, incorrect cancer type i.e. Bowel instead of Colorectal or project Ensure files are saved following the naming convention e.g. dce_lung_a111h_q1_2012_1_ csv name noted wrongly i.e. DEC Incorrect Submission number See section 2.2 for guidance Invalid Header Record Header row missing a component, incorrect cancer type or invalid record count Ensure the header record is completed accurately and that the quarter within the Header record matches that in the file name 16

17 Data record could not be read Submitted file in excel (xls) format Additional commas in the CSV file at the end of columns and at end of file Ensure file format is CSV and that columns are in correct order See section for guidance Any file that contains errors and warnings will be rejected and will not be loaded into the datamart. Errors need to be fixed by the board and the data resubmitted. We recommend that data should be amended at source and not just within the extract. This will prevent users from repeatedly making changes to the data should there be a need to resubmit data for a quarter which has already loaded i.e. resubmission of quarter 1 data due to the identification of additional patients. A full list of validation codes and their related messages can be found in Appendix 2 and further information on errors and error reporting is detailed in section 5 - Error Reporting Warnings Warnings have been built into the validation process; files that contain only warnings will pass validation and will be loaded into the datamart. Warnings include: Multiple records multiple records have been submitted in the file with the same CHI number Location of diagnosis location of diagnosis/hospital of audit code is for a private hospital or the Golden Jubilee All warnings should be checked and qualified via Data Quality Assurance reporting before your data is signed off locally. 4.2 DCE File Submission Once a file has been passed through the validation process a DCE File Submissions Summary is generated and ed. All contacts within the health board will receive the for the three cancer types (Breast, Lung & Colorectal). 17

18 Example DCE file submission Error Report The provides a summary of any errors and/or warnings contained within the file. In the above example the file has generated a Filename error, and we can see from the file name contained within the subject line and in the body of the that the submission reference number is missing. Other errors may not be as easily identifiable; user can therefore log into Business Objects and run the DCE Error Report. This report provides a break down of all the errors and warning by row and by error code. See section 5 for more information on Error Reporting. An error report is generated for every file, even if the file passes validation and is loaded. Reports with a Failed status will need to be reviewed and the errors amended and the file resubmitted. 4.3 Datamart Load Notification Once a file has been successfully submitted and passes all validations it is then loaded into the DCE datamart and a DCE data mart load notification is sent. Example 18

19 19

20 5. Error Reporting An error report is generated for each file that is submitted and these can be viewed by opening the PDF attachment in the DCE Submission File Error Report (see section 4.2). User can also access an error report by logging into Business Objects. If you do not have an account or are having problems accessing your account please contact 5.1 Logging into Business Objects i) Open up internet explorer and enter the following web address: This will load the Business Objects login page. ii) Enter your username and password iii) Click on Log On iv) Click on the Document Tab at the top left hand side of the screen v) Click on Folders at the bottom left hand side of the screen 20

21 vi) Navigate to the Detect Cancer Early Standard Reports folder. Public Folders/Scotland/NHS/Detect Cancer Early/Standard Reports/(01) Data Submission vi) Find the report named DCE Error Report. To run the report double click on the report name. 21

22 The Prompt window will be presented, this is where you need to enter the File ID number, and this can be found in the Summary Validation . vii) Enter the File ID number in the input box and click OK to run the report. Or look for the File ID from the list, double click to choose and then click OK to run the report. Note: If the File ID does not appear, click the Refresh Values button ( ) and repeat the process. 22

23 5.2 Error Report Once the information for the error report has refreshed you will be presented with the following report. Example report: The report is has two tabs; the first broken down by error code, the second by row number. Each tab consists of three sections: File Status this displays the File ID, the sending location code, the file status, load date, time period for the submission, number of errors and number of warning File details the displays the file name, the file type, record count and submission reference number List of Errors & Warnings - broken down by either error code or row number depending on which tab is selected. 23

24 5.3 Saving Error Reports Copies of the error reports can be saved to your pc (or local network area), and can then be used to help identify errors in the submission file. i) Click on Export. Export Document As PDF You will then be presented with the following prompt. Choose Save As from the Save dropdown options. We recommend saving the report as PDF, however you can chose to save the report as an excel file. When all errors have been corrected the file can be resubmitted via SWIFT. 24

25 Appendix 1 Data Submission Template Breast Insert the number of patient records contained within the file Colorectal Lung Note: Row 1 contains the header row, Row 2 contains the column headings and row 3 onwards should contain the data 25

26 Appendix 2 Data Validation The table below includes details of the File Validation and Data Validation Errors. The validation will not be case sensitive when validating codes which contain characters. File Extract Type Error Code Error Type Error Severity Error Message ALL FE1 File Name Error Invalid File Name: Cannot identify project ALL FE2 File Name Error Invalid File Name: Cannot identify file extract type ALL FE3 File Name Error Invalid File Name: Sending location is missing or not recognised ALL FE4 File Name Error Invalid File Name: Quarter is missing or not recognised ALL FE5 File Name Error Invalid File Name: Year is missing or not recognised. The format must be YYYY ALL FE6 File Name Error Invalid File Name: Submission number is missing, not recognised or is not in sequence ALL FE7 File Name Error Invalid File Name: Extract date is missing or not recognised. The format must be YYYYMMDD ALL HE1 Header Error Invalid Header Record: Could not be read check file format ALL HE2 Header Error Invalid Header Record: Cannot identify the project ALL HE3 Header Error Invalid Header Record: Cannot identify the extract type ALL HE4 Header Error Invalid Header Record: Sending location is missing, not recognised or does not match the file name ALL HE5 Header Error Invalid Header Record: Quarter is missing, not 26

27 File Extract Type Error Code Error Type Error Severity Error Message recognised or does not match the file name ALL HE6 Header Error Invalid Header Record: Year is missing, not recognised or does not match the file name. The format must be YYYY ALL HE7 Header Error Invalid Header Record: Submission number is missing, not recognised, is not in sequence or does not match the file name ALL HE8 Header Error Invalid Header Record: Extract Date is missing, invalid or out of range. Should be a date in the format YYYYMMDD and have a value between 01 Jan 2010 and the current date ALL HE9 Header Error Invalid Header Record: Record count is invalid ALL SE1 Schema Error Data record could not be read check file format. File must be a csv file. ALL VE1 Data Error CHI number must be provided ALL VE2 Data Error CHI number must be valid ALL VE3 Data Warning Multiple records have been submitted in the file with the same CHI Number ALL VE4 Data Error Date of Diagnosis must be provided ALL VE5 Data Error Date of Diagnosis must be a valid date in the format DD/MM/YYYY ALL VE6 Data Error Date of Diagnosis must be in the Quarter specified ALL VE7 Data Error Location of Diagnosis/Hospital of 27

28 File Extract Type Error Code Error Type Error Severity Error Message Audit code must be provided ALL VE8 Data Error Location of Diagnosis/Hospital of Audit code must be valid ALL VE9 Data Warning Location of Diagnosis/Hospital of Audit code is for a private hospital or the Golden Jubilee ALL VE10 Data Error Type of First Cancer Treatment code must be provided ALL VE11 Data Error Type of First Cancer Treatment code must be valid ALL VE12 Data Error Date of First Cancer Treatment must be provided ALL VE13 Data Error Date of First Cancer Treatment must be a valid date in the format DD/MM/YYYY ALL VE14 Data Error Patient must be aged 16 or over at the Date of Diagnosis BREAST VE15 Data Error TNM Tumour Classification (Preoperative) code must be provided BREAST VE16 Data Error TNM Tumour Classification (Preoperative) code must be valid BREAST VE17 Data Error TNM Nodal Classification (Pre-operative) code must be provided BREAST VE18 Data Error TNM Nodal Classification (Pre-operative) code must be valid BREAST VE19 Data Error TNM Metastases Classification (Preoperative) code must be provided 28

29 File Extract Type Error Code Error Type Error Severity Error Message BREAST VE20 Data Error TNM Metastases Classification (Preoperative) code must be valid BREAST VE21 Data Warning Date of First Definitive Breast Surgery must be provided BREAST VE22 Data Error Date of First Definitive Breast Surgery must be a valid date in the format DD/MM/YYYY BREAST VE23 Data Error First Axillary Surgery code must be provided BREAST VE24 Data Error First Axillary Surgery code must be valid BREAST VE25 Data Error Final Axillary Surgery code must be provided BREAST VE26 Data Error Final Axillary Surgery code must be valid BREAST VE27 Data Error Type of Tumour code must be provided BREAST VE28 Data Error Type of Tumour code must be valid BREAST VE29 Data Error Tumour Grade code must be provided BREAST VE30 Data Error Tumour Grade code must be valid BREAST VE31 Data Error Maximum Invasive Pathological Diameter must be provided BREAST VE32 Data Error Maximum Invasive Pathological Diameter must be numeric BREAST COLORECTAL VE33 Data Error [Final Total] Number of Lymph Nodes Examined must be provided BREAST COLORECTAL VE34 Data Error [Final Total] Number of Lymph Nodes Examined must be numeric BREAST VE35 Data Error Total Number of Lymph Nodes Involved must be provided BREAST COLORECTAL VE36 Data Error Total Number of Lymph Nodes Involved must be 29

30 File Extract Type Error Code Error Type Error Severity Error Message numeric COLORECTAL VE37 Data Error Chest CT (Results) code must be provided COLORECTAL VE38 Data Error Chest CT (Results) code must be valid COLORECTAL VE39 Data Error Date of Chest CT (Results) must be provided COLORECTAL VE40 Data Error Date of Chest CT (Results) must be a valid date in the format DD/MM/YYYY COLORECTAL VE41 Data Error Liver Imaging (Results) code must be provided COLORECTAL VE42 Data Error Liver Imaging (Results) code must be valid COLORECTAL VE43 Data Error Date of Liver Imaging (Results) must be provided COLORECTAL VE44 Data Error Date of Liver Imaging (Results) must be a valid date in the format DD/MM/YYYY COLORECTAL VE45 Data Error Grade of Differentiation code must be provided COLORECTAL VE46 Data Error Grade of Differentiation code must be valid COLORECTAL VE47 Data Error TNM Tumour Classification (Final) code must be provided COLORECTAL VE48 Data Error TNM Tumour Classification (Final) code must be valid COLORECTAL VE49 Data Error TNM Nodal Classification (Final) code must be provided COLORECTAL VE50 Data Error TNM Nodal Classification (Final) code must be valid COLORECTAL VE51 Data Error TNM Metastases Classification (Final) code must be provided COLORECTAL VE52 Data Error TNM Metastases Classification (Final) code must be valid 30

31 File Extract Type Error Code Error Type Error Severity Error Message COLORECTAL VE53 Data Error Dukes Classification code must be provided COLORECTAL VE54 Data Error Dukes Classification code must be valid COLORECTAL LUNG VE55 Data Warning Date of [First] Surgery must be provided COLORECTAL LUNG VE56 Data Error Date of [First] Surgery must be a valid date in the format DD/MM/YYYY LUNG VE57 Data Error Origin of Tumour code must be provided LUNG VE58 Data Error Origin of Tumour code must be lung (code 01) LUNG VE59 Data Error TNM Tumour Classification (Clinical) code must be provided LUNG VE60 Data Error TNM Tumour Classification (Clinical) code must be valid LUNG VE61 Data Error TNM Nodal Classification (Clinical) code must be provided LUNG VE62 Data Error TNM Nodal Classification (Clinical) code must be valid LUNG VE63 Data Error TNM Metastases Classification (Clinical) code must be provided LUNG VE64 Data Error TNM Metastases Classification (Clinical) code must be valid LUNG VE65 Data Error TNM Tumour Classification (Pathological) code must be provided LUNG VE66 Data Error TNM Tumour Classification (Pathological) code must be valid LUNG VE67 Data Error TNM Nodal Classification (Pathological) code must be provided LUNG VE68 Data Error TNM Nodal Classification (Pathological) code must 31

32 File Extract Type Error Code Error Type Error Severity Error Message be valid LUNG VE69 Data Error TNM Metastases Classification (Pathological) code must be provided LUNG VE70 Data Error TNM Metastases Classification (Pathological) code must be valid BREAST VE71 Data Error Source of Cancer Referral code must be provided BREAST VE72 Data Error Source of Cancer Referral code must be valid COLORECTAL VE73 Data Error Source of Cancer Referral code must be provided COLORECTAL VE74 Data Error Source of Cancer Referral code must be valid 32