VIEW THIS AS

Auto mode follows the Route Engine until you choose a viewpoint.

YOU ARE HERE

ROUTE CHECK

CONNECTED TO

WHAT NEXT

Use the canonical route for this room, or HELP if you are unsure.

Why Science? | Pathogen Transmission Ontology and Traceable Transmission Routes

Three students sit around open books and worksheets at a classroom table, reading, writing and discussing the work together.

eduKateSG · Why Science?

Describe how a pathogen may move—without turning a route category into proof of who infected whom

Begin with source, host, pathogen and route evidence, then trace timing, vector or vehicle, observations and alternatives before drawing a transmission conclusion.

Full section index · Science Learning Hub

“It spreads through the air” or “it came from food” can sound simple, yet a defensible transmission record needs to identify pathogen, source, host, route, time and evidence. The Pathogen Transmission Ontology, or TRANS, represents processes through which human disease pathogens move directly or indirectly from a reservoir, source or susceptible host to a new host. The OBO Foundry notes that transmission may involve animate vectors or inanimate vehicles, and that the Human Disease Ontology uses TRANS to describe methods of transmission. The official project remained active in 2026. TRANS can make route categories searchable and interoperable, but a route class does not prove a particular transmission event, direction, source or outbreak link. This guide supports Primary Science, PSLE Science, Secondary Science, O-Level Biology, public-health literacy, computing and STEM education; it is educational and not medical, diagnostic, infection-control, outbreak-management, admission or career advice.

Related eduKate reading: Infectious Disease Ontology; Genomic Epidemiology Ontology; NCBI Taxonomy; Environment Ontology; Science Learning Hub; Education Hub; STEM Education; Careers by Subject Capability.

Primary and official sources checked on 13 October 2026: OBO Foundry Pathogen Transmission Ontology overview, checked 13 October 2026; Official Pathogen Transmission Ontology repository; Canonical TRANS OWL release; Official Human Disease Ontology project; 2026 Singapore–Cambridge O-Level Biology syllabus; MOE G2/G3 Lower Secondary Science teaching and learning syllabus; 2026 MOE G2 Computing syllabus. Ontologies, definitions and release products can change, so preserve dated documentation, exact source records and file versions.

How a possible transmission route becomes traceable evidence

Transmission is a process linking a pathogen, a source or reservoir, a route and a new host. Each component can be uncertain, and the evidence for one component should not be borrowed automatically by another.

The official OBO Foundry page distinguishes direct and indirect transmission and notes that indirect routes may involve animate vectors or inanimate vehicles.

Direct transmission can include contact or short-range processes without an intermediate vehicle, but practical classification still depends on definitions and evidence for the event.

Indirect transmission can involve air, water, food, surfaces, blood products, equipment or other vehicles. The vehicle category should name the material or object actually supported by evidence.

Vector-borne transmission involves a living carrier such as an arthropod. Mechanical carriage and biological development within a vector describe different mechanisms.

A reservoir is an ecological context in which a pathogen is normally maintained, while a source is the immediate origin for a particular exposure. The same entity need not fill both roles.

The Human Disease Ontology uses TRANS route concepts to describe human diseases. This supports consistent disease knowledge without proving any individual case history.

Genomic similarity can support relatedness, yet sampling coverage, mutation rate, within-host diversity and epidemiological context determine what it means for transmission.

Time orders the story. Infectious period, exposure opportunity, incubation, symptoms, sampling and reporting must be compatible before direction is plausible.

The optimistic value is careful coordination: route categories help people search and compare evidence while uncertainty, alternatives and public-health judgement remain explicit.

Begin with the exact claim. “This disease is commonly vector-borne” is a general property; “this person acquired it from this vector” is an event-level causal assertion.

Identify the pathogen at the resolution supported by laboratory evidence. Species, strain and lineage should not be inferred from a broad positive test.

Identify source and destination hosts separately and preserve uncertain direction. Co-occurrence cannot decide who infected whom.

Record contact type, distance, duration and setting only when collected. Unknown exposure details should not be filled from assumptions about the disease.

For vehicle routes, preserve batch, handling, location and sampling chain. Detection in one item does not automatically establish it as the transmission vehicle.

For vector routes, record species, life stage, infection evidence and competence separately. Finding a pathogen near a vector is not proof of transmission.

Environmental persistence affects plausibility but depends on temperature, humidity, medium and time. Laboratory survival does not translate directly to real-world risk.

Negative results have limits. Timing, specimen type, sampling coverage and test performance shape what “not detected” can exclude.

For classroom work, fictional outbreak cards can let students sort observations, route hypotheses and evidence needs safely.

Reader-ready summaries use calibrated verbs such as detected, compatible with, supports and confirmed according to the strength of evidence.

Route classification and event attribution are separate tasks. TRANS may represent a known mode for a disease while a particular case remains unexplained.

Mixed routes are possible. An outbreak may involve a contaminated source followed by person-to-person spread, so one label can hide a changing process.

Sampling bias can overstate a visible route. Severe cases, accessible locations and routinely tested vehicles may dominate the evidence.

Network diagrams need uncertainty and missing nodes. A neat chain can be a model assembled from incomplete contacts rather than an observed sequence.

Genomic thresholds are context-dependent. The same genetic distance can imply different time or linkage under different organisms, mutation rates and sampling designs.

Behaviour and environmental data are sensitive. Minimum necessary detail and governed access protect people and communities while supporting legitimate review.

Public communication should distinguish a precaution from a confirmed route. Protective action may be justified under uncertainty without presenting the hypothesis as fact.

Release migration should test parent-child route classifications and Human Disease Ontology imports so disease queries do not shift silently.

A reproducible TRANS bundle includes case definitions, host and pathogen identities, route annotations, contacts, environmental records, assays, sequences, timelines and review notes.

Students can compare two plausible routes and list evidence that would favour or weaken each. This builds healthy scepticism without fear.

Science tuition can connect infectious disease content with variables, graphs, probability and responsible evidence language.

Before publication, benchmark direct, indirect, vector, vehicle, mixed, unknown and contradicted cases and check that the pipeline never invents a source.

A final audit asks whether the route, event, source and causal language are all supported at the same level—and whether alternatives remain visible.

A practical TRANS investigation can use a fictional school-camp outbreak with deliberately incomplete clues. Several learners became ill after a shared event; food, water, direct contact and a local vector are all plausible at the beginning. Students receive a timeline, a small contact table, environmental samples and simplified laboratory results. Their first job is not to choose a culprit. It is to label pathogen evidence, possible sources, host events, vehicles, vectors and unknowns, then test whether each route is compatible with time. A food sample that tests positive supports contamination of that sample; it does not by itself establish that it caused every illness. Two related sequences support biological relatedness; they do not alone reveal direction or exclude an unsampled intermediary. A contact during a possible infectious period supports opportunity; it does not prove a direct event. Learners can update their route graph as evidence arrives and explain why confidence changes. The same logic should govern production systems. Build fixtures for direct, airborne, vector-borne, foodborne, waterborne, mixed-route, unknown and contradicted scenarios. Include reversed timelines, uncertain onset, negative late samples, contaminated controls, duplicated cases and incomplete contact data. A route classifier should be allowed to return unresolved instead of forcing the nearest category. Store whether a TRANS term describes a disease’s generally recognised mode, a particular exposure hypothesis or a reviewed case-level conclusion. These layers must not inherit certainty from one another. Review genomic thresholds with organism-specific mutation rates, within-host variation and sampling density. Review environmental persistence under the observed medium, temperature and duration rather than an unrelated laboratory condition. Protect people and communities by minimising exact locations, rare-event details and linkable genomic metadata in public outputs. Communication should distinguish why precautions were taken from what the investigation ultimately established; sensible action under uncertainty is not an admission that the route was proven. For students and readers, this is a hopeful model of science in action: competing explanations are not a weakness. They are how careful investigators keep options open until the evidence supports a stronger, accountable conclusion.

Before publishing a transmission map, perform a claim-language audit. Each edge should state whether it represents opportunity, compatibility, support, probable linkage or a conclusion reached under named criteria. Show the evidence type beside the edge and distinguish missing evidence from evidence against the route. Remove arrowheads when direction is unresolved. Test the map after omitting the most influential case or sample; if the story changes sharply, disclose that sensitivity. Compare observed cases with the population and time window at risk so a cluster is not defined only by the cases investigators happened to find. Route-specific preventive advice should come from current qualified authorities, while the ontology article should explain the evidence model rather than improvise instructions. In the classroom, let groups defend different route hypotheses using the same evidence, then reward the team that most clearly names uncertainty and the next useful test. This shows that careful disagreement can improve science. The final data release should include TRANS version, mapping rules, timeline assumptions, sampling gaps, review decisions and a plain statement of what was not established. A graph becomes trustworthy when its uncertainty is as visible as its connections.

A four-stage evidence ladder for TRANS-backed transmission data
StageQuestionEvidenceResponsible output
DefineWhich transmission process is being considered?TRANS class, definition, source and destinationA stable route hypothesis
ObserveWhat direct evidence was collected?Specimen, assay, contact, vector or vehicle recordA bounded observation
IntegrateWhich timeline and alternative routes fit?Epidemiology, genomics, environment and uncertaintyA traceable explanation
ConcludeWhat level of linkage is justified?Criteria, review, competing hypotheses and provenanceA calibrated transmission statement

Section 1 of 36

1. Begin with the transmission claim

A general route, an exposure and a confirmed event require different evidence.

Working checkpoint — TRANS identifier: State the level of claim. Keep pathogen, source, host, route, time, method and uncertainty together.

For mathematics, keep denominators, time windows and sampling coverage visible.

Contents · Next section

Section 2 of 36

2. Use the TRANS identifier

A stable class connects local language to a maintained route definition.

Working checkpoint — transmission process: Store IRI, label and release. Separate a general disease route from a case-level transmission event.

For computing, make unknown directions and missing contacts explicit.

Contents · Previous section · Next section

Section 3 of 36

3. Read the definition

Everyday route words can overlap or hide intermediate hosts and vehicles.

Working checkpoint — source host: Compare definition with the event record. Preserve vector or vehicle evidence without upgrading detection to causation.

For writing, choose verbs that match the strength of transmission evidence.

Contents · Previous section · Next section

Section 4 of 36

4. Identify the pathogen

Taxonomic resolution should match the assay or sequence evidence.

Working checkpoint — reservoir: Do not invent strain precision. Test timelines, sampling gaps and alternative routes before attribution.

For students, ask what was observed and what route was inferred.

Contents · Previous section · Next section

Section 5 of 36

5. Identify the source

The immediate origin of exposure may be a host, material, object or environment.

Working checkpoint — vector: Record evidence and uncertainty. Use qualified clinical and public-health guidance for real situations.

For parents, the calm checkpoint is whether the learner can name an alternative explanation.

Contents · Previous section · Next section

Section 6 of 36

6. Identify the reservoir

Long-term ecological maintenance is not automatically the same as the immediate source.

Working checkpoint — vehicle: Keep roles distinct. Keep pathogen, source, host, route, time, method and uncertainty together.

For mathematics, keep denominators, time windows and sampling coverage visible.

Contents · Previous section · Next section

Section 7 of 36

7. Identify the new host

Susceptibility, exposure and infection are related but separate concepts.

Working checkpoint — TRANS identifier: Record host and evidence. Separate a general disease route from a case-level transmission event.

For computing, make unknown directions and missing contacts explicit.

Contents · Previous section · Next section

Section 8 of 36

8. Model direct transmission

Direct routes connect source and host without an intermediate vehicle under the chosen definition.

Working checkpoint — transmission process: Preserve contact context. Preserve vector or vehicle evidence without upgrading detection to causation.

For writing, choose verbs that match the strength of transmission evidence.

Contents · Previous section · Next section

Section 9 of 36

9. Model indirect transmission

Indirect routes involve an intermediate vehicle, vector or environmental medium.

Working checkpoint — source host: Name the supported intermediary. Test timelines, sampling gaps and alternative routes before attribution.

For students, ask what was observed and what route was inferred.

Contents · Previous section · Next section

Section 10 of 36

10. Model contact transmission

Physical contact and contaminated-surface pathways may require different categories.

Working checkpoint — reservoir: Record touch and sampling evidence. Use qualified clinical and public-health guidance for real situations.

For parents, the calm checkpoint is whether the learner can name an alternative explanation.

Contents · Previous section · Next section

Section 11 of 36

11. Model airborne processes

Particle size, distance, ventilation and time affect interpretation of airborne hypotheses.

Working checkpoint — vector: Keep measurements and model assumptions. Keep pathogen, source, host, route, time, method and uncertainty together.

For mathematics, keep denominators, time windows and sampling coverage visible.

Contents · Previous section · Next section

Section 12 of 36

12. Model droplet processes

Short-range respiratory exposure should not be inferred from disease label alone.

Working checkpoint — vehicle: Record setting and timing. Separate a general disease route from a case-level transmission event.

For computing, make unknown directions and missing contacts explicit.

Contents · Previous section · Next section

Section 13 of 36

13. Model foodborne routes

Food vehicle claims need product, batch, handling and laboratory or epidemiological support.

Working checkpoint — TRANS identifier: Preserve chain of custody. Preserve vector or vehicle evidence without upgrading detection to causation.

For writing, choose verbs that match the strength of transmission evidence.

Contents · Previous section · Next section

Section 14 of 36

14. Model waterborne routes

Water source, treatment, sampling and spatial distribution shape the evidence.

Working checkpoint — transmission process: Record environmental context. Test timelines, sampling gaps and alternative routes before attribution.

For students, ask what was observed and what route was inferred.

Contents · Previous section · Next section

Section 15 of 36

15. Model vector-borne routes

Vector identity, infection status and competence contribute different evidence.

Working checkpoint — source host: Keep each assertion separate. Use qualified clinical and public-health guidance for real situations.

For parents, the calm checkpoint is whether the learner can name an alternative explanation.

Contents · Previous section · Next section

Section 16 of 36

16. Connect taxonomy

Stable identifiers distinguish pathogen, host and vector taxa.

Working checkpoint — reservoir: Preserve taxon resolution and release. Keep pathogen, source, host, route, time, method and uncertainty together.

For mathematics, keep denominators, time windows and sampling coverage visible.

Contents · Previous section · Next section

Section 17 of 36

17. Connect IDO

IDO supplies broader infectious-disease processes and pathogen-neutral semantics around TRANS routes.

Working checkpoint — vector: Link without collapsing scope. Separate a general disease route from a case-level transmission event.

For computing, make unknown directions and missing contacts explicit.

Contents · Previous section · Next section

Section 18 of 36

18. Connect Disease Ontology

The Human Disease Ontology uses TRANS to represent disease transmission methods.

Working checkpoint — vehicle: Distinguish general knowledge from case evidence. Preserve vector or vehicle evidence without upgrading detection to causation.

For writing, choose verbs that match the strength of transmission evidence.

Contents · Previous section · Next section

Section 19 of 36

19. Connect GenEpiO

GenEpiO joins laboratory, sequence and epidemiological metadata for outbreak analysis.

Working checkpoint — TRANS identifier: Keep pipeline and sampling context. Test timelines, sampling gaps and alternative routes before attribution.

For students, ask what was observed and what route was inferred.

Contents · Previous section · Next section

Section 20 of 36

20. Connect ENVO

Environmental context can describe habitats and materials involved in route evidence.

Working checkpoint — transmission process: Record place, medium and conditions. Use qualified clinical and public-health guidance for real situations.

For parents, the calm checkpoint is whether the learner can name an alternative explanation.

Contents · Previous section · Next section

Section 21 of 36

21. Build a timeline

Exposure opportunity, infectious period, onset, sampling and result must be ordered.

Working checkpoint — source host: Use uncertain intervals. Keep pathogen, source, host, route, time, method and uncertainty together.

For mathematics, keep denominators, time windows and sampling coverage visible.

Contents · Previous section · Next section

Section 22 of 36

22. Challenge co-location

Sharing a place or event supports opportunity, not transmission by itself.

Working checkpoint — reservoir: List alternative contacts. Separate a general disease route from a case-level transmission event.

For computing, make unknown directions and missing contacts explicit.

Contents · Previous section · Next section

Section 23 of 36

23. Challenge genetic similarity

Closely related genomes do not alone establish direction or direct linkage.

Working checkpoint — vector: Review sampling and evolution. Preserve vector or vehicle evidence without upgrading detection to causation.

For writing, choose verbs that match the strength of transmission evidence.

Contents · Previous section · Next section

Section 24 of 36

24. Challenge environmental detection

Finding a pathogen in a vehicle or location does not prove it infected a particular host.

Working checkpoint — vehicle: Require event-level support. Test timelines, sampling gaps and alternative routes before attribution.

For students, ask what was observed and what route was inferred.

Contents · Previous section · Next section

Section 25 of 36

25. Challenge route stereotypes

A disease with a common route can sometimes spread through other supported mechanisms.

Working checkpoint — TRANS identifier: Use current case evidence. Use qualified clinical and public-health guidance for real situations.

For parents, the calm checkpoint is whether the learner can name an alternative explanation.

Contents · Previous section · Next section

Section 26 of 36

26. Challenge neat networks

Missing cases and contacts can make a clean diagram misleading.

Working checkpoint — transmission process: Show uncertainty and unsampled nodes. Keep pathogen, source, host, route, time, method and uncertainty together.

For mathematics, keep denominators, time windows and sampling coverage visible.

Contents · Previous section · Next section

Section 27 of 36

27. Review TRANS migrations

Changed route hierarchy or imports can alter disease queries and summaries.

Working checkpoint — source host: Run saved-query tests. Separate a general disease route from a case-level transmission event.

For computing, make unknown directions and missing contacts explicit.

Contents · Previous section · Next section

Section 28 of 36

28. Connect to Primary Science

Microorganisms, hygiene and environments can be taught through safe route examples.

Working checkpoint — reservoir: Separate prevention from proof. Preserve vector or vehicle evidence without upgrading detection to causation.

For writing, choose verbs that match the strength of transmission evidence.

Contents · Previous section · Next section

Section 29 of 36

29. Connect to Secondary Science

Infectious disease, ecosystems and experimental evidence form a connected route model.

Working checkpoint — vector: Compare two hypotheses. Test timelines, sampling gaps and alternative routes before attribution.

For students, ask what was observed and what route was inferred.

Contents · Previous section · Next section

Section 30 of 36

30. Connect to mathematics

Rates, conditional probability, networks and time intervals show why route evidence is uncertain.

Working checkpoint — vehicle: Calculate from valid denominators. Use qualified clinical and public-health guidance for real situations.

For parents, the calm checkpoint is whether the learner can name an alternative explanation.

Contents · Previous section · Next section

Section 31 of 36

31. Connect to computing

Ontologies, timelines, graphs and validation rules make route data auditable.

Working checkpoint — TRANS identifier: Test impossible sequences. Keep pathogen, source, host, route, time, method and uncertainty together.

For mathematics, keep denominators, time windows and sampling coverage visible.

Contents · Previous section · Next section

Section 32 of 36

32. Connect to pathways

TRANS-related skills appear in epidemiology, microbiology, bioinformatics, environmental health and data stewardship.

Working checkpoint — transmission process: Check current official routes separately. Separate a general disease route from a case-level transmission event.

For computing, make unknown directions and missing contacts explicit.

Contents · Previous section · Next section

Section 33 of 36

33. Did you know?

The official TRANS description separates animate vectors from inanimate vehicles within indirect pathogen transmission.

Working checkpoint — source host: Classify the intermediary before naming the route. Preserve vector or vehicle evidence without upgrading detection to causation.

For writing, choose verbs that match the strength of transmission evidence.

Contents · Previous section · Next section

Section 34 of 36

34. Write a reader-ready transmission note

Name pathogen, source, host, route, intermediary, time, evidence, release and uncertainty.

Working checkpoint — reservoir: Keep advice outside the coded summary. Test timelines, sampling gaps and alternative routes before attribution.

For students, ask what was observed and what route was inferred.

Contents · Previous section · Next section

Section 35 of 36

35. Build a validation ladder

Check identity, route definition, source, host, timeline, assay, alternatives, review and communication.

Working checkpoint — vector: Stop at the earliest unresolved rung. Use qualified clinical and public-health guidance for real situations.

For parents, the calm checkpoint is whether the learner can name an alternative explanation.

Contents · Previous section · Next section

Section 36 of 36

36. Finish with a reproducible TRANS bundle

Deliver source records, ontology files, case definitions, contacts, assays, sequences, timelines and limitations.

Working checkpoint — vehicle: Make every route claim traceable. Keep pathogen, source, host, route, time, method and uncertainty together.

For mathematics, keep denominators, time windows and sampling coverage visible.

Contents · Previous section · Continue to the Science Learning Hub

Discover more from eduKate Singapore

Subscribe now to keep reading and get access to the full archive.

Continue reading