Counter Fraud


Counter Fraud Service "4 D's" Strategy

  1. Deter - By raising awareness of the impact of financial crime and of the sanctions applied to those who commit such offences against NHS Scotland
  2. Disable - By improving NHS Scotland’s long-term capability to prevent financial crime
  3. Detect - By improving sharing knowledge and intelligence about financial crime, enhanced data mining and a proactive approach to countering financial crime
  4. Deal with - By investigating the most serious and harmful threats and seeking to apply all relevant sanctions

Click here to go to the CFS Web site

This authority is required by law to protect the public funds it administers.  It may share information provided to it with other bodies responsible for auditing or administering public funds, in order to prevent and detect fraud and other crime.  On behalf of the Auditor General for Scotland, Audit Scotland appoints the auditor to audit the accounts of this authority.  It is also responsible for carrying out data matching exercises.

Data matching involves comparing sets of data, such as the payroll held by one body against other records held by the same or another body to see how far they match.  This is usually personal information.  Computerised data matching allows potentially fraudulent claims and payments to be identified but the inclusion of personal data within a data matching exercise does not mean that any specific individual is under suspicion.  Where a match is found it indicates that there is an inconsistency which requires further investigation.  No assumption can be made as to whether there is fraud, error or other explanation until an investigation is carried out.  The exercise can also help bodies to ensure that their records are up to date.

Audit Scotland currently requires us to participate in a data matching exercise to assist in the prevention and detection of fraud.  We are required to provide particular sets of data to Audit Scotland for matching for each exercise, and these are set out in Audit Scotland’s instructions, which can be found at: http://www.audit-scotland.gov.uk/our-work/national-fraud-initiative

The processing of data by Audit Scotland (in practice the processing is undertaken by the Cabinet Office on Audit Scotland’s behalf) in a data matching exercise is carried out under the powers in Part 2A of the Public Finance and Accountability (Scotland) Act 2000.  It does not require the consent of the individuals concerned under the Data Protection Act 2018.  Data matching by Audit Scotland is subject to a Code of Practice.  This can also be found at: http://www.audit-scotland.gov.uk/our-work/national-fraud-initiative

For further information on Audit Scotland’s legal powers and the reasons why it matches particular information, see the full text privacy notice at: http://www.audit-scotland.gov.uk/our-work/national-fraud-initiative or contact Monica Halcro, Acting Senior Manager (Governance and Operations) Finance, NHS Education for Scotland (Tel: 0131 656 4354; Email: monica.halcro@nes.scot.nhs.uk)

Fraud Liaison Officer  (FLO)

Acting Head of Finance and Fraud Liaison Officer
Janice Sinclair
Head of Financial Services
Westport 102
West Port 
Edinburgh EH3 9DN
Tel: 0131 656 3281

 

HR – Local HR Business Partner or
Christine McCole
Depute Director of HR
Westport 102
West Port 
Edinburgh EH3 9DN
Tel: 0131 656 3302

CFS
Tel: 08000 151628
website: http://www.cfs.scot.nhs.uk

 

Counter Fraud Champion
Audrey McColl
Director of Finance
Westport 102
West Port 
Edinburgh EH3 9DN
Tel: 0131 656 3281

Counter Fraud training within NES

To access the training, please follow the steps below:

  1. Log into LearnPro: http://nhs.learnprouk.com
  2. Select 'More Learning' and then the ‘Specialist Subjects' tab
  3. Check the box next to NHS Scotland Counter Fraud Services e-Learning and select 'Save'
  4. To launch the module, select 'Learn', then ‘Specialist Subjects' and click on the NHS Scotland Counter Fraud Services e-Learning icon
  5. Click ‘Launch’
  6. The assessment for the module can be accessed via the same process and selecting 'Launch assessment' instead of 'Launch module'