Projects to date have found it extremely difficult to keep the target system up to date with operational changes that have to be made in the legacy system during the deployment phase.

Projects teams' experiences to date are: For Deployment Teams - Difficult to keep track of Data Collection Worksheets (DCW) versions, ownership and changes - Project teams had to spend unplanned time managing inconsistencies between DCW, Build and trust expectations

For Build Teams - Trust teams inserted columns and rows invalidating benefits of standard formats - Invalid data items were often presented - It was difficult to issue new validation rules to DCWs that were already in circulation - It was not possible to automate build from spreadsheets.

For Trust Teams - Frustration that the test environments were out of date, and out of synch with data migration - Lots of time spent on manual entry of DCW - Lots of time spent updating DM mapping tables - Anxiety about getting ‘go live’ codes built in the go live window. Master Data Manager can be used to improve the speed, accuracy and communication flows of the data required by the build team, especially clinics, personnel and locations which have proven to be the most volatile.

Written by Shaun Regan (Director, Avoca Systems LTD) following experiences in 23 major data migration projects for the NHS.

These problems can be overcome by deploying the Avoca Master Data Manager tool in 2 ways: -

Option A: use of the standard functionality, to capture and manage DCW data presented by the Trust. -

Option B: extends the standard functionality by providing an additional module which automatically creates the ESM, Location and Personnel DCW required fields from source data presented by the Trust.

Contact Us to find out more.