Styxis
Company
Knowledge

Keep observed deaths separate from attributed climate-health estimates

Identical units do not make observations, exposure measures and model-attributed burden interchangeable.

Ask whether the numbers can be combined

Putting climate and health indicators on one screen can make a risk easier to discuss. It does not make the numbers additive or directly comparable. Observed deaths, population exposed to heat and a model-attributed burden answer different questions. Truthound can check a table that preserves those declared distinctions. It cannot decide medical causation, forecast health risk or establish the validity of an attribution model.

Publication year is not observation year

WHO introduced the 2026 Lancet Countdown report on 28 October 2026, describing 54 indicators connecting climate and health. Its account includes different reference periods and model-attributed estimates. Publication in 2026 does not make every figure a 2026 observation. Likewise, a recommendation to recognise a climate-health emergency must not be rewritten as evidence that a particular formal emergency determination has already occurred.

Different meanings can share a unit

A proposed working table would retain indicator identity, observation year, geographic unit, estimate type and uncertainty information. Even where two quantities use deaths as their unit, an all-cause observation and an attributed subset may overlap. The responsible indicator owner must define allowed combinations and explain overlap before the table is used. Software cannot recover that meaning from the numeric column alone.

Keep a counterexample in the workflow

Suppose two rows refer to the same geography and year, but one is an observation and the other estimates a component of that observation. Do not sum them. Nor should a missing estimate type default to observed. Hold the row until its source or methodology identifies the category. This counterexample makes the integration process test an interpretation instead of merely producing a neat collection of numbers.

Validate only the approved interpretation contract

Truthound Core Python SDK 3.3.4 (open-source SDK, Polars backend) documents ColumnPairInSetValidator for caller-supplied valid pairs. An operator could check approved indicator and estimate-type combinations, using a separate ColumnTypeValidator rule for fields such as reference year. Specify null handling and geographic classification versions explicitly. Passing these checks does not make a model estimate true; subject specialists still assess methods, coverage and any causal interpretation.

Respect an existing statistical validation process

Pandera 0.35.0 (MIT open-source Python DataFrame validation library; pandas, Polars and other supported backends) can retain declared types and custom checks when a team already maintains the equivalent contract. It also documents Polars support. Compare that workflow with Truthound’s pinned SDK interfaces through rule ownership and exception reporting, rather than assuming a migration improves the underlying evidence. Neither product should be expected to distinguish observations from attribution estimates without definitions supplied by the analyst.

Start with one interpretable indicator

Limit the first exercise to one indicator and one geography intended for a real analysis. Have its owner compare the source definition, stored category and dashboard explanation. Stop the aggregation if its attribution scope or reference year cannot be established. The useful result is a distinction between evidence that can enter the policy discussion and evidence that remains unresolved, rather than a table with every cell filled.

Conditions

Have the indicator owner confirm estimate type, geography and reference-year meaning.

Alternatives

Retain an equivalent Pandera 0.35.0 contract in the established statistical workflow.

Limitations

  • Valid categories do not establish an attribution method or make overlapping estimates additive.

Evidence

Event checked
Subject checked
Modified