13
NHS Reorganisation & the Implications for the interfaces

NHS Reorganisation & the Implications for the interfaces

Embed Size (px)

Citation preview

Page 1: NHS Reorganisation & the Implications for the interfaces

NHS Reorganisation & the Implications for the interfaces

Page 2: NHS Reorganisation & the Implications for the interfaces

Overview

• ODS and Entity Codes• Costing – Cost centre/Subjective codes

• Mass updates• Mappings – Override codes• File Formats• Data History• Delivery Points• Other interfaces• Suppliers• Costs

2

Page 3: NHS Reorganisation & the Implications for the interfaces

ODS/NACS & Entity Codes

• ODS (previously NACS)– Stored at Authority Level

• Entity Code– Stored at Payroll Level– Sometimes same code as ODS, but often a

dummy code is used.

3

Page 4: NHS Reorganisation & the Implications for the interfaces

Entity Codes

• Do you require a separate Entity code• We can supply you with a temporary entity code• New codes require a new GL hub• Issues when duplicating entity codes

– Used by the hub to decide on the software required– Identifies which hub the file will live– Can / Cannot be seen by another organisations– Not easy to identify the origin of each file– Mapping on GL hub will override ESR mapping– Entity code is validated against a VPD

4

Page 5: NHS Reorganisation & the Implications for the interfaces

Costing

• Cost centres • Subjective codes • Sub Analysis codes

Do you need to make any changes??

5

Page 6: NHS Reorganisation & the Implications for the interfaces

Mass code update functionality issues

• Identify the codes that need changing and provide a spreadsheet

• Runs against a VPD – Changes all source codes to the target where

identified

Mass Update Process

6

Page 7: NHS Reorganisation & the Implications for the interfaces

• Mapping In ESR– Considerations

• VPD – Single Mapping table

• Entity code – Part of the lookup criteria

• Mapping on the GL Hub– Considerations

• Final Override

• Only allows a single set of override codes

Mapping Table

7

Page 8: NHS Reorganisation & the Implications for the interfaces

The software in the GL hub dictates the format

– Consider the GL system the file will be required to be loaded in to

File Format

Page 9: NHS Reorganisation & the Implications for the interfaces

Data History

• De-merger process– History moves to target organisation

• IAT process– History stays with Source organisation

• For Information:– The GL source file may contain some

history information required

Page 10: NHS Reorganisation & the Implications for the interfaces

Other Interfaces Non-Core

Interfaces run at VPD level

Identify if the source and target VPD’s have live non-core interfaces

– Rostering issues– Payment issues (Attendance interface)– Absence Recording issues – Identify if the staff should be included

on the target VPD interface file or not– Self Service access

Page 11: NHS Reorganisation & the Implications for the interfaces

3rd Party Suppliers

• Do any system suppliers need to be informed of large volumes of staff movements

• Notice periods – if a VPD will cease to exist after certain date please

inform the NHS Interface Team

Page 12: NHS Reorganisation & the Implications for the interfaces

Costs

• The interface team will be charging for any changes and set up required

• The cost will be agreed in advance of any commencement of services

• Logging an SR to identify if the interface team needs to be involved in your organisational changes will not be charged

Page 13: NHS Reorganisation & the Implications for the interfaces

Questions?