NHS Digital Data Release Register - reformatted
NHS Mid And South Essex Icb - 07g projects
4 data files in total were disseminated unsafely (information about files used safely is missing for TRE/"system access" projects).
DSfC - NHS Thurrock CCG - IV — DARS-NIC-198119-X9P3J
Opt outs honoured: Yes - patient objections upheld, Identifiable (Section 251, Section 251 NHS Act 2006)
Legal basis: Section 251 approval is in place for the flow of identifiable data, National Health Service Act 2006 - s251 - 'Control of patient information'. , Health and Social Care Act 2012 s261(7); National Health Service Act 2006 - s251 - 'Control of patient information'.
Purposes: No (Clinical Commissioning Group (CCG), Sub ICB Location)
When:DSA runs 2019-05-13 — 2022-05-12 2018.06 — 2021.05.
Access method: Frequent adhoc flow, Frequent Adhoc Flow, One-Off
Data-controller type: NHS THURROCK CCG, NHS MID AND SOUTH ESSEX ICB - 07G
Sublicensing allowed: No
- SUS for Commissioners
Invoice validation is part of a process by which providers of care or services get paid for the work they do.
Invoices are submitted to the Clinical Commissioning Group (CCG) so they are able to ensure that the activity claimed for each patient is their responsibility. This is done by processing and analysing Secondary User Services (SUS+) data, which is received into a secure Controlled Environment for Finance (CEfF). The SUS+ data is identifiable at the level of NHS number. The NHS number is only used to confirm the accuracy of backing-data sets and will not be used further.
Invoice Validation with be conducted by the CCG
1. Financial validation of activity
2. CCG Budget control
3. Commissioning and performance management
4. Meeting commissioning objectives without compromising patient confidentiality
5. The avoidance of misappropriation of public funds to ensure the ongoing delivery of patient care
1. Addressing poor data quality issues
2. Production of reports for business intelligence
3. Budget reporting
4. Validation of invoices for non-contracted events
Data must only be used as stipulated within this Data Sharing Agreement.
Data Processors must only act upon specific instructions from the Data Controller.
Data can only be stored at the addresses listed under storage addresses.
The Data Controller and any Data Processor will only have access to records of patients of residence and registration within the CCG.
Patient level data will not be shared outside of the CCG unless it is for the purpose of Direct Care, where it may be shared only with those health professionals who have a legitimate relationship with the patient and a legitimate reason to access the data.
All access to data is managed under Roles-Based Access Controls
No patient level data will be linked other than as specifically detailed within this agreement. Data will only be shared with those parties listed and will only be used for the purposes laid out in the application/agreement. The data to be released from NHS Digital will not be national data, but only that data relating to the specific locality and that data required by the applicant.
NHS Digital reminds all organisations party to this agreement of the need to comply with the Data Sharing Framework Contract requirements, including those regarding the use (and purposes of that use) by “Personnel” (as defined within the Data Sharing Framework Contract ie: employees, agents and contractors of the Data Recipient who may have access to that data)
Where the Data Processor and/or the Data Controller hold both identifiable and pseudonymised data, the data will be held separately so data cannot be linked.
All access to data is auditable by NHS Digital.
Data for the purpose of Invoice Validation is kept within the CEfF, and only used by staff properly trained and authorised for the activity. Only CEfF staff are able to access data in the CEfF and only CEfF staff operate the invoice validation process within the CEfF. Data flows in to the CEfF and from the providers – it does not flow through any other processors.
1. Identifiable SUS+ Data is obtained from the SUS+ Repository to the Data Services for Commissioners Regional Office (DSCRO).
2. The DSCRO pushes a one-way data flow of SUS+ data into the Controlled Environment for Finance (CEfF) located in the CCG.
3. The CEfF conduct the following processing activities for invoice validation purposes:
a. Validating that the Clinical Commissioning Group is responsible for payment for the care of the individual by using SUS+ and/or backing flow data.
b. Once the backing information is received, this will be checked against national NHS and local commissioning policies as well as being checked against system access and reports provided by NHS Digital to confirm the payments are:
i. In line with Payment by Results tariffs
ii. In relation to a patient registered with the CCG GP or resident within the CCG area.
iii. The health care provided should be paid by the CCG in line with CCG guidance.
4. The CCG are notified by the CEfF that the invoice has been validated and can be paid. Any discrepancies or non-validated invoices are investigated and resolved