EPR Programme - Data Migration Partner

NWAHC intend to publish the invitation to tender (ITT) documents under the NHS London Procurement Partnership (LPP) OneLondon Local Health and Care Record Dynamic Purchasing System (DPS), using sub-category 1.3 Supporting Data Standards & Normalisation, in April 2024.<br/><br/>If you would like to be invited to further competition, but are not presently awarded on to the DPS, you can apply to join by registering at - www.lppsourcing.org ↗ and completing the online selection questionnaire (SQ).<br/><br/>Upon completion of the SQ a supplier will be accepted within 10 working days, unless applying for a newly added category where a 30 day notice period is required before evaluation of apps takes place.<br/><br/>NWAHC intend to hold supplier information days in March.<br/>Please contact [email protected] for further details. Additional information: SCOPE OF REQUIREMENT <br/><br/>NWAHC will be looking for highly experienced support with the planning, analysis and implementation of the data migration and conversion requirements within the EPR Programme as part of the journey towards implementing Meditech Expanse. They will prepare a technical plan for data extraction and estimate of transformation effort for the base systems. Requirements and associated data sets required when mapped to the related Meditech Expanse IFF and associated import mechanism. The plan will include:<br/><br/>-A full analysis of all systems and proposal for management of each type of activity type and IFF. <br/>-The detailed data types are set out in below under Requirements but the data migration partner must have experience of working with Meditech or another major EPR vendor, specifically around the high-risk administrative pathway’s areas.<br/>-PAS MPI data – there are three separate PAS systems but there is currently a programme to ensure there is a single unique patient identifier however this is only based on known matches so there will need to be an on-going piece of work that will look to reduce the number of query matches.<br/>-Referral to Treatment (RTT), Non RTT, Diagnostic and Cancer pathways and associated periods – suppliers need to express their experience and credibility with case studies about how they have successfully supported NHS Trusts to migrate and convert RTT, Non RTT, diagnostic and cancer pathways and evidence how they have integrated all relevant periods into one overarching pathway and to include methodology for creating a unique pathway identifier which all relevant activity can be linked back to. <br/>-Specific outputs within defined timescales and responsibilities split between the trusts, collaborative and data migration partner.<br/>-The supplier will work with NWAHC to deliver the data migration plan in line with the overall Meditech Expanse implementation plan including:<br/><br/>

• Migration of data into Meditech Expanse<br/>o The scope of migrated data (i.e. IFFs to be populated and volumes of data to be included) including details of any data items that need to be excluded from the migration scope. <br/>o The tools to be used to generate each IFF. <br/>o All the source systems containing data to be migrated to the target system. <br/>o The number and full scope of each trial load (i.e., considering dependencies on configuration / mapping activity and environment availability). <br/>o Frequency / approach for importing source data into Meditech Expanse. <br/>o Load errors / warnings. <br/><br/>
• Data quality and source data validation<br/>o The approach(es) to be taken to resolve the following (potential) data issues: <br/>o Missing ‘mandatory’ data items (i.e., where there is no available source data, but the field is required within the supplier IFF) <br/>o Anticipated Data Quality / Data Integrity issues within the source data <br/>o Approach for managing duplicate patients (including the matching criteria and approach for identifying ‘near’ duplicates) and the management of physical notes following automated merges through the Transform and Load processes. <br/>o Approach to core issues such as Patient Numbering (i.e., defining what common numbering will be carried through into the target system and an assessment of the impacts on other teams e.g., Medical Records / Integration / 3rd Party Systems) <br/><br/>
• Transformation rules and data mapping<br/><br/>
• Cutover planning including anticipated ‘downtime’ during final cutover / go-live <br/><br/>
• Manual migration plan<br/><br/>
• Issue management process<br/><br/>
• Testing & reconciliation strategy<br/><br/>
• Support archiving of data in an accessible format<br/><br/>
• Purging of data<br/><br/>
• Enabling of legacy decommissioning<br/><br/>
• Monitoring and tracking against the plan<br/><br/>
• Entry and Exit criteria for each trial load, dress rehearsal and cutover. <br/><br/>
• Approach to validating / testing migrated data. <br/><br/>
• Roles and responsibilities for all teams. <br/><br/>
• Key risks, assumptions, issues and dependencies. <br/><br/>
• Timelines for key activity; aligned with the detailed Programme / Project Plan <br/><br/>There will be a separate tender to lead on and implement an archiving and clinical data repository solution. Any proposals should be considered in the context of these requirements.<br/><br/>Further information is contained in the attached documentation.