ESR integration
WeHub takes the ESR files as they land, parses them, and lets you run SQL to pull exactly the data you need. Validation, cross-Trust matching and a reconciliation report happen in the same pass.
For NHS workforce, HR, digital and ICS teams who need ESR data somewhere else.
The problem
ESR delivers extracts, not answers: delta .DAT files shaped for a machine, not for the system that has to read them. Every destination needs a different subset in a different format, so someone builds and maintains a separate route to each one by hand.
Then something changes. A new field, a vendor upgrade, another Trust, and every route has to be reworked. Records that do not fit are dropped in silence: a duplicated person, a manager in another Trust, an organisation reference the receiving system has never seen. Nothing tells you what went missing.
Solution
ESR exports arrive once. WeHub parses them, validates them, and delivers exactly the data each system needs, with execution history and failure drill-down behind every run.
The same flow serves every team that needs the workforce record somewhere other than ESR.
What we do
For the technical reader: the four things that happen between the file landing and the data being usable.
01
Files land on the channel you agreed. WeHub lists what arrived, works out which files belong to this run, and records when they came and from where.
02
The ESR file structure is read directly by a native parser, not by a bespoke script that has to be rewritten every time a format changes.
03
Once parsed, the data is queryable. You pull exactly the records each destination needs instead of shipping everything and filtering it downstream.
04
Mapped, validated, and delivered as CSV over SFTP, in the shape the receiving system takes. Anything that could not be placed comes out categorised with a reason.
Insights
Engineering notes on ESR extracts, workforce data and the integrations around them, from the team that builds WeHub.
