phs_dz2001_hb¶
health board PHS assigned to the 2001 data zone when computing within-geography bands
| Table | Type | Nullable | Category | In the CSV export | SQL Server type |
|---|---|---|---|---|---|
history table (postcode_simd_history, SPD) |
string | no | PHS SIMD, population-weighted | yes | nvarchar(200) |
main table (postcode_simd, SSPL) |
string | no | PHS SIMD, population-weighted | yes | nvarchar(200) |
Provenance (the same in both tables)¶
Each table runs its own copy of the table-level checks, named .history. and .main..
Where it comes from
| Input | Field | Condition | Reaches the row by |
|---|---|---|---|
PHS/simd2004_02042020.csv (pinned, SHA256 dcc871e88353…) |
HB |
DataZone2001Code = DataZone |
Scope: the row itself.
What was done to it: copied. The code PHS assigned to the 2001 data zone, from the first PHS edition of that vintage (2004); identical across the vintage's editions. (code: simd_ingest/core/join.py: join_edition)
How it is checked (what each check tests; whether a build passed it is in that build's manifest.json["checks"])
phs.2006.shared_geography: this edition's PHS geography codes equal those of the first edition of its vintagephs.2009v2.shared_geography: this edition's PHS geography codes equal those of the first edition of its vintagephs.2012.shared_geography: this edition's PHS geography codes equal those of the first edition of its vintagejoin.<table>.geography_nonnull: every PHS geography code is filledreadback.<table>.attached_values: every attached value in the saved file is looked up again from the sources and equal