Project background

NHS England’s Reporting, Insights, Publications and Transparency (RIPT) programme is improving how operational data is transformed into consistent, governed metrics and made available for internal reporting, insight and external publication.

Statement of Work 2 (SOW2) progresses the programme from the design and planning foundations established under SOW1 into implementation, domain adoption and preparation for wider scale. This includes delivery across the Central Metrics Library (CML), Master Metrics Asset (MMA), internal reporting and Data Gateway/publications, supported by integration and business change activities.

WS03 – Central Metrics Library transforms source data into analytically ready datasets and provides the authoritative source of metrics for internal and external use. CML creates and calculates metrics and supports their data quality and approval. Metrics identified in CML as externally publishable are detected by MMA, where Merge consolidates metrics as required before the MMA approval workflow. Approved outputs then progress through the downstream publication process.

CML delivery priorities include National Oversight Framework (NOF) metric refreshes, including Integrated Care Board (ICB) reporting; quality and executive reporting metrics; pre-publication processing; onboarding of priority domains such as Urgent and Emergency Care (UEC) and Planned Care; automation; and support for legacy metrics store migration and business-as-usual (BAU) handover. The engineer will contribute to these activities according to assigned work packages and project priorities.

Role

CML Data Engineer – WS03, RIPT SOW2

Deliver assigned data engineering work packages supporting the development, refresh and adoption of CML metrics within the Federated Data Platform (FDP), using Palantir Foundry.

The engineer will work with NHS England’s CML team, analysts and domain specialists, alongside supplier colleagues, to translate agreed requirements into working pipelines, metric assets and supporting delivery evidence.

Roles and responsibilities

• Develop and maintain CML pipelines: Build and update data pipelines and transformation code to produce agreed CML datasets and metric assets from available source data.
• Implement agreed metric requirements: Apply defined calculation logic, dimensions and data structures, working with analysts and domain specialists to resolve requirement gaps.
• Support metric refreshes: Deliver assigned engineering activities for NOF refreshes, including ICB reporting, and quality and executive metrics in line with workstream priorities.
• Support domain adoption: Implement allocated CML metrics for priority domains, including UEC and Planned Care, and subsequent domains as agreed.
• Support pre-publication processing: Undertake assigned engineering activities to ingest pre-release datasets and develop the associated metrics within CML.
• Improve automation: Automate agreed metric refresh and transformation processes, supporting repeatable processing and reduced manual intervention.
• Maintain data quality: Implement validation and reconciliation checks, investigate discrepancies and resolve engineering defects with the relevant analysts and data owners.
• Maintain metadata and lineage: Record source dependencies, transformation logic and metric metadata, including agreed externally publishable flags required for MMA consumption.
• Support testing and acceptance: Complete engineering tests, provide testing and reconciliation evidence, and support defect resolution and acceptance of assigned outputs.
• Support integration: Work with MMA and other relevant teams to ensure assigned CML outputs meet agreed downstream requirements and contribute to the CML → MMA → Azure → Publication/Data Gateway flow.
• Document and hand over: Maintain technical documentation and provide knowledge transfer and BAU handover support for delivered assets.
• Report delivery progress: Provide estimates and status updates, raise blockers and dependencies promptly, and submit outputs through the agreed internal review process.

Delivery scope

The Data Engineer is responsible for completing assigned activities to agreed quality standards, timescales and acceptance criteria. Work will be allocated according to project priorities, taking account of capacity, source data availability and dependencies.

The role’s allocation, focus and responsibilities may be adjusted during the engagement to meet changing delivery requirements, including assignment across RIPT workstreams. Changes will be communicated by the delivery manager and aligned with the individual’s skills and experience and the agreed scope of the engagement.