Data Validation Engine
The Data Validation Engine (DVE) is a configuration-driven data validation library created and used by NHS England. It lets users define validation rules once and apply them across multiple dataset collections - supporting consistent, accurate data checks.
The DVE offers:
- SQL configuration-based validations
- Format normalization to Parquet for a unified data representation
- Data modelling and typecasting
- Business-rule validations executed on supported backends such as Spark and DuckDB, with the option to add custom backends
- Validate and enforce referential integrity checks with minimal configuration
- Deriving new fields and entities
- Clear validation reporting, including summary insights and record-level error messages
As mentioned above, the DVE is "configuration driven" which means the majority of development for you as a user will be building a JSON document to describe how the data will be validated. The JSON document is known as a dischema (data ingest schema) file and example files can be accessed here ↗️. If you'd like to learn more about JSON document and how to build one from scratch, then please read the documentation here ↗️.
Installation and usage
Please see the documentation here ↗️.
Requesting new features and raising bug reports
Before creating new issues, please check to see if the same bug/feature has been created already. Where a duplicate is created, the ticket will be closed and referenced to an existing issue.
If you have spotted a bug with the DVE then please raise an issue here ↗️ using the "bug template".
If you have feature request then please follow the same process whilst using the "Feature request template".
Upcoming features
Below is a list of features that we would like to implement or have been requested.
| Feature | Release Version | Released? |
|---|---|---|
| Open source release | 0.1.0 | Yes |
| Uplift to Python 3.11 | 0.2.0 | Yes |
| Uplift Pyspark to 3.5 | 0.8.0 | Yes |
| Allow DVE to run on Python 3.12+ | 0.8.0 | Yes |
| Upgrade to Pydantic 2.0 | 0.9.0 | Yes |
| Upgrade DuckDB to v1.4 | 0.10.0 | Yes |
| Uplift Pyspark to 4.0+ | TBA | No |
| Polars upgrade to v1+ | TBA | No |
| DuckDB upgrade to v1.5+ | TBA | No |
| Python 3.13 & 3.14 upgrade | TBA | No |
| Create a more user friendly interface for building and modifying dischema files | TBA | No |
If you are interested in getting any of the unreleased features listed above available, then please read the Contributing section and then submit us a pull request.
Contributing
Please see guidance here ↗️.
Legal
This codebase is released under the MIT License. This covers both the codebase and any sample code in the documentation.
Any HTML or Markdown documentation is © Crown copyright and available under the terms of the Open Government 3.0 licence.
Metadata
Release files for data-validation-engine 0.10.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| data_validation_engine-0.10.2.tar.gz | 166.9 kB | With provenance | Details for data_validation_engine-0.10.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| data_validation_engine-0.10.2-py3-none-any.whl | Python 3 | none | any | Details for data_validation_engine-0.10.2-py3-none-any.whl |
Total release size: 384.5 kB
Release files / data_validation_engine-0.10.2.tar.gz
| Download URL | data_validation_engine-0.10.2.tar.gz |
|---|---|
| Size | 166.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
569b9c77584c529f4442d0bcf6d14acc78eef5acbb2599213b1d45bbc8434d89
|
|
BLAKE2b-256 checksum How to use checksums |
a2ef3b4ba0d3a8fddecfee214ffe14f3d383f55cf6e0d55784cd52c97ab59823
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 13, 2026.
Transparency logRelease files / data_validation_engine-0.10.2-py3-none-any.whl
| Download URL | data_validation_engine-0.10.2-py3-none-any.whl |
|---|---|
| Size | 217.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
cac019bc773997db5ac4acb7b190ca9449c6e51c175f3bd3064908cac4303643
|
|
BLAKE2b-256 checksum How to use checksums |
e706b0e257971e548439ec3ca271856bf42b6d46848b3f7ce4e704879070302e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 13, 2026.
Transparency logSecurity for data-validation-engine 0.10.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for data_validation_engine-0.10.2.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 13, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.