| Column |
Title |
Type |
Description |
| REPORTING_YEAR |
Reporting Year |
string |
The financial year which the activity relate to. Year-end methodology will include all activity data (including amendments) collected from FP17s scheduled in any of the fifteen schedule months from April to June, where the date of completion is on or between 1 April and 31 March of the year. For example 2019-20 will include all activity data (including amendments) collected from FP17s scheduled in any of the fifteen schedule months from April 2019 to June 2020, where the date of completion is on or between 1 April 2019 and 31 March 2020. Where FP17s do not have a date of completion, e.g. where the patient has failed to return to complete the treatment, the date of acceptance is used.
|
| CONTRACT_NUMBER |
Contract Number |
integer |
This is a unique 10 character number which identifies a contract
|
| LOCAL_AUTHORITY_CODE |
Local Authority Code |
string |
The local authority code in which the patient is resident, irrespective of where treatment took place. Based on the home postcode recorded in the personal details section of each FP17 submitted, therefore is dependent on this information being included and accurate in the records. This is not dependent on where the patient received treatment, so can either be in or outside the PCO.
|
| LOCAL_AUTHORITY_NAME |
Local Authority Name |
string |
The local authority name in which the patient is resident, irrespective of where treatment took place. Based on the home postcode recorded in the personal details section of each FP17 submitted, therefore is dependent on this information being included and accurate in the records. This is not dependent on where the patient received treatment, so can either be in or outside the PCO.
|
| UNIQUE_PATIENT_COUNT |
Unique Patient Count |
integer |
This is a count of the unique patient identities on forms scheduled. A patient may have attended more than once in the time period and received different treatment, so the total figure has been adjusted for duplicate patient IDs. Patient identities are counted for all valid FP17 transactions – including amendment, deletion and withdrawn records. Therefore, it is possible for the count of patient identities to be greater than the count of FP17s.
|
| UNIQUE_PATIENT_COUNT_(ADULTS) |
Unique Patient Count Adult |
integer |
This is a count of the unique patient identities on forms scheduled for adult patients. A patient may have attended more than once in the time period and received different treatment, so the total figure has been adjusted for duplicate patient IDs. Patient identities are counted for all valid FP17 transactions – including amendment, deletion and withdrawn records. Therefore, it is possible for the count of patient identities to be greater than the count of FP17s.
|
| UNIQUE_PATIENT_COUNT_(CHILDREN) |
Unique Patient Count Children |
integer |
This is a count of the unique patient identities on forms scheduled for child patients. A patient may have attended more than once in the time period and received different treatment, so the total figure has been adjusted for duplicate patient IDs. Patient identities are counted for all valid FP17 transactions – including amendment, deletion and withdrawn records. Therefore, it is possible for the count of patient identities to be greater than the count of FP17s.
|