Pietro Corona is a public-health professional and the founder and developer of Weavidence. He works as an Assistente Sanitario at ASL Cagliari. His professional background includes public-health practice, epidemiological surveillance, health information flows, and work focused on epidemiology and biostatistics.
On Weavidence Insights, he writes about public health, epidemiology, study design, research methodology, reproducibility, scientific learning, and AI-supported evidence workflows.
Pietro founded and develops Weavidence. Articles he authors are published by Weavidence Insights; Weavidence remains the publisher and publication identity.
A named human author remains accountable for the article. AI tools may assist with research, source discovery, structure, drafting, revision, editing, or checking under the editorial policy, but they are not authors, reviewers, or publishers.
When AI determines whether an exposure, outcome, phenotype or case is present, model error becomes epidemiological measurement error. Accuracy alone is not enough; validation must follow the variable's role in inference.
Public-health rates are often treated as observed facts, but AI-enabled population estimation can turn the denominator itself into a model output. The indicator then inherits the model's assumptions and uncertainty.
AI predictions can trigger public-health actions that alter the population and the data later used to evaluate the same model. Prediction, intervention and measurement then become causally coupled.
Shared foundation models can create hidden dependence across institutions that appear to be making independent judgments. Public-health resilience may require epistemic diversity, not only better average model accuracy.
AI-generated text, classifications and summaries can re-enter health-data and research systems as if they were ordinary observations. Without provenance, future models and analyses may learn from prior model outputs rather than from the world they are intended to represent.
Emergency-department data can reveal fast changes in health-care use and syndromic activity, but the population reaching an ED is selected by access, severity, behaviour, coding and service organization.
Vaccination coverage looks like a simple percentage, but its numerator and denominator depend on eligibility, population estimates, mobility, recording completeness and time.
A surveillance system can be technically sound and still fail public health if its information arrives at the wrong time, for the wrong population, or in a form that cannot support the decision at hand.
Sensitivity, specificity, predictive value, timeliness, completeness, representativeness and acceptability are not independent virtues. Improving one can worsen another or increase cost.
A disease notification is only the first state in a longer information chain. Validation, classification, deduplication, enrichment, aggregation and interpretation determine whether a report becomes usable epidemiological information.
Two populations can have the same final vaccination coverage while experiencing very different periods of susceptibility. Timeliness and catch-up require longitudinal thinking.
Mortality statistics are built through certification, ICD coding and rules for selecting an underlying cause. The final tabulation is standardized, but it is not a direct transcription of biological reality.
Mortality-data quality starts before ICD coding. Certificate content, registration completeness, temporal consistency and fitness for purpose determine what coding can preserve.
Public-health programmes become difficult to evaluate when indicators are chosen before the causal and implementation logic of the intervention is made explicit.
Activities and outputs can show that a programme operated. They cannot by themselves show that outcomes changed because of it.
Regression adjustment can estimate a conditional association under a specified model. It cannot decide the causal question, fix selection created by design, or determine whether a variable is a confounder, mediator or collider.
Computational reproducibility asks whether the same data and methods produce the same result. Validity asks whether the result supports the intended scientific inference.
Reconstructing an analysis requires more than saving scripts and datasets. The audit trail should preserve entities, transformations, versions, exclusions, parameters, alternatives and accountable decisions.
AI can accelerate retrieval, drafting, coding and analytical support. Decisions that define the epidemiological object, causal question, exclusions, interpretation and publication accountability require explicit human ownership.
AI can multiply drafts, analyses and candidate decisions faster than humans can remember how they were produced. Acceleration increases the value of provenance.
A surveillance system is useful only when it supports its stated decisions with data that are timely, sufficiently complete, interpretable, and sustainable. Evaluation is a purpose-led assessment of trade-offs, not a single score.
A finished-looking protocol and a protocol whose design reasoning survives review are different documents. Journey is built to produce the second one.
"AI-powered" describes what a system uses. It does not describe who is accountable for what it produces. Weavidence treats that as a design boundary, not a caveat.
A completion record and evidence of demonstrated competence are different claims about a learner. Weavidence Academy is built around keeping that difference visible.
A public-health concern becomes researchable only after its population, exposure or intervention, comparator, outcome, and time frame are explicit — and after the question is tested for feasibility, relevance, ethics, and decision value.
Competence cannot be inferred from attendance, completion, or one successful test. It requires evidence that knowledge can be selected and applied in unfamiliar situations, demonstrated across suitable tasks, and interpreted through a defensible assessment programme.
Reproducibility requires more than saved code. The exact data state, transformations, software environment, parameters, randomness, manual decisions, and expected outputs must be identifiable — and the workflow must be independently rerunnable within legitimate access constraints.
A software artifact that looks correct and a software artifact that is inspectable and independently checkable are different claims. Traceability is what turns the first into the second.
A single "run analysis" button that returns a chart hides more than it reveals. Lab keeps quality, computation, and review as distinct, inspectable stages instead.
Academy, Journey, and Lab could have been one bundled application. They are three connected products instead, and the separation is a deliberate design choice, not an accident of scope.