eduKateSG · Why Science?
Keep the rare-disease concept, ORPHAcode, hierarchy, version and provenance together so systems can exchange meaning without erasing uncertainty
Choose the closest route, then return to the full index whenever you need the wider evidence chain.
Science learning becomes powerful when students can tell a measured pattern from a model, a statistical decision from a mechanism, and a useful lead from a finished conclusion. The Orphanet Rare Disease Ontology, ORDO, is the official ontology of rare diseases maintained by Orphanet. Derived from the expert-curated Orphanet knowledge base, it provides structured disease concepts, ORPHAcodes, labels, synonyms, classifications and selected relationships to support computational analysis and interoperability. ORDO is updated as rare-disease knowledge and nomenclature change. A code identifies a curated concept in a release; it does not by itself prove that a person has that disorder, that two coding systems are perfectly equivalent, or that the concept will never be revised. This guide supports Primary Science, PSLE Science, Secondary Science, O-Level Science and STEM education as a longform evidence-reading route; it is not medical advice, a laboratory protocol, an admission promise or a career guarantee.
Related eduKate reading: Human Phenotype Ontology and structured clinical phenotypes; ClinVar and evidence-aware variant classifications; GWAS Catalog and curated variant–trait associations; Science Learning Hub; Education Hub; STEM Education; Careers by Subject Capability.
Primary and official sources checked on 11 October 2026: Official Orphadata ORDO page; Official What Is ORDO guide; ORDO in EMBL-EBI Ontology Lookup Service; Official Orphanet information page; 2026 Singapore–Cambridge O-Level Biology syllabus; MOE G2/G3 Lower Secondary Science teaching and learning syllabus; 2026 MOE G2 Computing syllabus. Package interfaces and recommendations can change, so reproduce an analysis only with the documentation for the installed release.
| Stage | Question | Evidence | Responsible output |
|---|---|---|---|
| Identify | Which exact ORDO concept and release are intended? | ORPHAcode, preferred term, definition and status | A scoped disease concept |
| Position | Where does the concept sit in Orphanet classifications? | Parents, children, group/disorder/subtype level | A hierarchy-aware record |
| Map | How does it relate to another terminology? | Curated cross-references, match type and date | A qualified mapping |
| Validate | Does the code fit the documented clinical meaning? | Source record, expert review and current nomenclature | A bounded coding decision, not a diagnosis |
Inside this guide
1–12 · Foundations and design
- 1. Start with a rare-disease nomenclature
- 2. Understand ORDO and Orphanet
- 3. Keep the ORPHAcode
- 4. Read the entity level
- 5. Read definitions and scope
- 6. Use synonyms for discovery
- 7. Understand classification parents
- 8. Expect multiple parents
- 9. Keep concept identity separate from prevalence
- 10. Keep identity separate from diagnosis
- 11. Use cross-references cautiously
- 12. Avoid label-only joins
13–24 · Models and estimation
- 13. Separate disorder from gene
- 14. Separate phenotype from disease
- 15. Pin the release
- 16. Handle obsolete concepts
- 17. Read change logs
- 18. Do not count hierarchy nodes as cases
- 19. Design cohort queries deliberately
- 20. Audit double counting
- 21. Map local terminology transparently
- 22. Support multilingual exchange carefully
- 23. Use web and downloadable data differently
- 24. Validate machine reasoning
25–36 · Diagnostics and interpretation
- 25. Respect licensing and attribution
- 26. Protect rare-disease privacy
- 27. Use bounded clinical language
- 28. Connect to Primary Science
- 29. Connect to Secondary Science
- 30. Connect to mathematics
- 31. Connect to computing
- 32. Connect to pathways
- 33. Did you know?
- 34. Write a reader-ready result
- 35. Build a validation ladder
- 36. Finish with a reproducible bundle
Section 1 of 36
1. Start with a rare-disease nomenclature
ORDO gives rare-disease concepts stable identifiers and relationships so data can be compared across records and systems.
Working checkpoint — ORDO concept: Identify the concept before counting or joining records. Keep the independent sample, design, annotation and software version beside this decision so the evidence can be reconstructed.
For a classroom model, use invented counts and clearly label the activity as an analogy rather than a sequencing experiment.
Section 2 of 36
2. Understand ORDO and Orphanet
Orphanet is the knowledge base and information portal; ORDO is a computable ontology derived from its rare-disease nomenclature.
Working checkpoint — ORPHAcode: Cite the appropriate resource layer. Read the numerical result together with sample-level plots, effect size and a sensitivity check capable of weakening the headline.
For future study, connect the idea to biology, mathematics and computing while checking current official pathway information separately.
Section 3 of 36
3. Keep the ORPHAcode
A numerical ORPHAcode points to an Orphanet concept and should travel with the label and release.
Working checkpoint — rare-disease hierarchy: Store identifier, label, version and access date together. Preserve the complete tested family and every excluded feature; a polished shortlist is not a substitute for provenance.
For scientific writing, prefer “supports”, “is associated with” and “is predicted to” when stronger causal verbs are not justified.
Section 4 of 36
4. Read the entity level
Orphanet distinguishes groups of disorders, disorders and subtypes. Mixing levels can double-count or compare unlike concepts.
Working checkpoint — cross-reference: Record the concept type before aggregation. Separate what the model estimates from the biological story proposed afterward, then name the extra evidence that story would require.
For students, the transferable habit is to ask: What was measured? Compared with what? What alternative explanation remains?
Section 5 of 36
5. Read definitions and scope
A familiar disease name may cover a broader or narrower concept than expected. Definitions and inclusion boundaries guide interpretation.
Working checkpoint — obsolete term: Open the concept rather than relying on label text. Treat identifiers, denominators and factor levels as scientific quantities: a silent mismatch can reverse an otherwise correct calculation.
For parents, a calm checkpoint is to ask how many independent samples support the claim and which assumption matters most.
Section 6 of 36
6. Use synonyms for discovery
Synonyms help locate records written in different language or historical terminology, but they do not make every phrase an exact equivalent.
Working checkpoint — release provenance: Preserve the original name and mapped concept. Keep the independent sample, design, annotation and software version beside this decision so the evidence can be reconstructed.
For a classroom model, use invented counts and clearly label the activity as an analogy rather than a sequencing experiment.
Section 7 of 36
7. Understand classification parents
A concept can appear under clinically useful classification branches. Hierarchical location supports browsing but does not necessarily express one simple biological lineage.
Working checkpoint — ORDO concept: Name the classification branch used. Read the numerical result together with sample-level plots, effect size and a sensitivity check capable of weakening the headline.
For future study, connect the idea to biology, mathematics and computing while checking current official pathway information separately.
Section 8 of 36
8. Expect multiple parents
Rare diseases can be relevant to more than one specialty or mechanism, so ontology graphs need not be simple trees.
Working checkpoint — ORPHAcode: Use graph-aware traversal and deduplicate identifiers. Preserve the complete tested family and every excluded feature; a polished shortlist is not a substitute for provenance.
For scientific writing, prefer “supports”, “is associated with” and “is predicted to” when stronger causal verbs are not justified.
Section 9 of 36
9. Keep concept identity separate from prevalence
Being listed in a rare-disease ontology does not supply a universal prevalence figure for every country or period.
Working checkpoint — rare-disease hierarchy: Cite prevalence from its own dated source. Separate what the model estimates from the biological story proposed afterward, then name the extra evidence that story would require.
For students, the transferable habit is to ask: What was measured? Compared with what? What alternative explanation remains?
Section 10 of 36
10. Keep identity separate from diagnosis
An ORPHAcode supports consistent recording after suitable assessment; the code itself is not clinical evidence.
Working checkpoint — cross-reference: Trace the coding decision to the source record. Treat identifiers, denominators and factor levels as scientific quantities: a silent mismatch can reverse an otherwise correct calculation.
For parents, a calm checkpoint is to ask how many independent samples support the claim and which assumption matters most.
Section 11 of 36
11. Use cross-references cautiously
ORDO links to other terminologies, but a cross-reference can be exact, broader, narrower or historically inherited.
Working checkpoint — obsolete term: Inspect mapping semantics before automated conversion. Keep the independent sample, design, annotation and software version beside this decision so the evidence can be reconstructed.
For a classroom model, use invented counts and clearly label the activity as an analogy rather than a sequencing experiment.
Section 12 of 36
12. Avoid label-only joins
Identical strings can refer to different scopes, while different strings can refer to one concept.
Working checkpoint — release provenance: Join on reviewed identifiers and mapping records. Read the numerical result together with sample-level plots, effect size and a sensitivity check capable of weakening the headline.
For future study, connect the idea to biology, mathematics and computing while checking current official pathway information separately.
Section 13 of 36
13. Separate disorder from gene
A disease concept and a gene are different entity types. A relationship between them is evidence-bearing and can change.
Working checkpoint — ORDO concept: Keep concept, gene and relationship provenance distinct. Preserve the complete tested family and every excluded feature; a polished shortlist is not a substitute for provenance.
For scientific writing, prefer “supports”, “is associated with” and “is predicted to” when stronger causal verbs are not justified.
Section 14 of 36
14. Separate phenotype from disease
Phenotypic features describe observations; ORDO disease concepts summarise disorders. Converting one feature into a diagnosis is a category error.
Working checkpoint — ORPHAcode: Use HPO for findings and ORDO for disease concepts. Separate what the model estimates from the biological story proposed afterward, then name the extra evidence that story would require.
For students, the transferable habit is to ask: What was measured? Compared with what? What alternative explanation remains?
Section 15 of 36
15. Pin the release
Official guidance says ORDO is updated on a regular cycle, and concepts or mappings can change between releases.
Working checkpoint — rare-disease hierarchy: Archive the exact release used. Treat identifiers, denominators and factor levels as scientific quantities: a silent mismatch can reverse an otherwise correct calculation.
For parents, a calm checkpoint is to ask how many independent samples support the claim and which assumption matters most.
Section 16 of 36
16. Handle obsolete concepts
A concept may be obsoleted, merged or replaced as nomenclature improves. Historical data still needs an auditable path.
Working checkpoint — cross-reference: Follow replacement notes without erasing the original code. Keep the independent sample, design, annotation and software version beside this decision so the evidence can be reconstructed.
For a classroom model, use invented counts and clearly label the activity as an analogy rather than a sequencing experiment.
Section 17 of 36
17. Read change logs
Release notes reveal added, modified and deprecated content that can alter counts and cohort definitions.
Working checkpoint — obsolete term: Compare releases before reporting trends. Read the numerical result together with sample-level plots, effect size and a sensitivity check capable of weakening the headline.
For future study, connect the idea to biology, mathematics and computing while checking current official pathway information separately.
Section 18 of 36
18. Do not count hierarchy nodes as cases
An ontology enumerates concepts, not patients. Numbers of diseases, groups and subtypes depend on counting rules.
Working checkpoint — release provenance: State which entity types and release were counted. Preserve the complete tested family and every excluded feature; a polished shortlist is not a substitute for provenance.
For scientific writing, prefer “supports”, “is associated with” and “is predicted to” when stronger causal verbs are not justified.
Section 19 of 36
19. Design cohort queries deliberately
Including descendants can widen a cohort from one disorder to a whole family. That can be useful or misleading.
Working checkpoint — ORDO concept: Save the root concept and descendant rule. Separate what the model estimates from the biological story proposed afterward, then name the extra evidence that story would require.
For students, the transferable habit is to ask: What was measured? Compared with what? What alternative explanation remains?
Section 20 of 36
20. Audit double counting
A record coded to both a disorder and its subtype can be counted twice after hierarchy expansion.
Working checkpoint — ORPHAcode: Deduplicate at the intended person and concept level. Treat identifiers, denominators and factor levels as scientific quantities: a silent mismatch can reverse an otherwise correct calculation.
For parents, a calm checkpoint is to ask how many independent samples support the claim and which assumption matters most.
Section 21 of 36
21. Map local terminology transparently
Local labels may be incomplete or ambiguous. Automated mapping needs human review for high-impact use.
Working checkpoint — rare-disease hierarchy: Retain mapping confidence, method and reviewer. Keep the independent sample, design, annotation and software version beside this decision so the evidence can be reconstructed.
For a classroom model, use invented counts and clearly label the activity as an analogy rather than a sequencing experiment.
Section 22 of 36
22. Support multilingual exchange carefully
Orphanet provides multilingual nomenclature resources, but translation and local usage can evolve.
Working checkpoint — cross-reference: Keep language, release and preferred term visible. Read the numerical result together with sample-level plots, effect size and a sensitivity check capable of weakening the headline.
For future study, connect the idea to biology, mathematics and computing while checking current official pathway information separately.
Section 23 of 36
23. Use web and downloadable data differently
A portal supports browsing; downloadable ontology files support reproducible analysis. They may update on different schedules.
Working checkpoint — obsolete term: Record the retrieval route and checksum. Preserve the complete tested family and every excluded feature; a polished shortlist is not a substitute for provenance.
For scientific writing, prefer “supports”, “is associated with” and “is predicted to” when stronger causal verbs are not justified.
Section 24 of 36
24. Validate machine reasoning
A reasoner can infer hierarchy membership from ontology axioms, but it cannot repair a wrong input code.
Working checkpoint — release provenance: Test known inclusion and exclusion cases. Separate what the model estimates from the biological story proposed afterward, then name the extra evidence that story would require.
For students, the transferable habit is to ask: What was measured? Compared with what? What alternative explanation remains?
Section 25 of 36
25. Respect licensing and attribution
Orphadata publishes access and reuse terms that matter for downstream distribution.
Working checkpoint — ORDO concept: Retain source attribution and current terms. Treat identifiers, denominators and factor levels as scientific quantities: a silent mismatch can reverse an otherwise correct calculation.
For parents, a calm checkpoint is to ask how many independent samples support the claim and which assumption matters most.
Section 26 of 36
26. Protect rare-disease privacy
Even coded datasets can become identifying when combined with geography, age or detailed phenotype.
Working checkpoint — ORPHAcode: Apply minimisation and approved governance. Keep the independent sample, design, annotation and software version beside this decision so the evidence can be reconstructed.
For a classroom model, use invented counts and clearly label the activity as an analogy rather than a sequencing experiment.
Section 27 of 36
27. Use bounded clinical language
ORDO improves interoperability and research; it does not replace expert diagnosis or care.
Working checkpoint — rare-disease hierarchy: Say “coded to the current concept” rather than “confirmed by the ontology”. Read the numerical result together with sample-level plots, effect size and a sensitivity check capable of weakening the headline.
For future study, connect the idea to biology, mathematics and computing while checking current official pathway information separately.
Section 28 of 36
28. Connect to Primary Science
A library catalogue shows how one book can sit under several useful subjects while keeping one identifier.
Working checkpoint — cross-reference: Use fictional books and classifications. Preserve the complete tested family and every excluded feature; a polished shortlist is not a substitute for provenance.
For scientific writing, prefer “supports”, “is associated with” and “is predicted to” when stronger causal verbs are not justified.
Section 29 of 36
29. Connect to Secondary Science
Disease categories change as molecular and clinical evidence improves. Classification is a scientific model, not a fixed law of nature.
Working checkpoint — obsolete term: Compare two dated versions of a harmless taxonomy. Separate what the model estimates from the biological story proposed afterward, then name the extra evidence that story would require.
For students, the transferable habit is to ask: What was measured? Compared with what? What alternative explanation remains?
Section 30 of 36
30. Connect to mathematics
Sets, graphs, inheritance and deduplication determine how ontology-based counts behave.
Working checkpoint — release provenance: Predict the count before and after descendant expansion. Treat identifiers, denominators and factor levels as scientific quantities: a silent mismatch can reverse an otherwise correct calculation.
For parents, a calm checkpoint is to ask how many independent samples support the claim and which assumption matters most.
Section 31 of 36
31. Connect to computing
URIs, ontology files, versioning and mapping tables let systems share rare-disease concepts.
Working checkpoint — ORDO concept: Validate types and identifiers at every join. Keep the independent sample, design, annotation and software version beside this decision so the evidence can be reconstructed.
For a classroom model, use invented counts and clearly label the activity as an analogy rather than a sequencing experiment.
Section 32 of 36
32. Connect to pathways
Rare-disease informatics joins biology, terminology, medicine, software and governance and can illuminate STEM education and career pathways.
Working checkpoint — ORPHAcode: Check current official requirements for real decisions. Read the numerical result together with sample-level plots, effect size and a sensitivity check capable of weakening the headline.
For future study, connect the idea to biology, mathematics and computing while checking current official pathway information separately.
Section 33 of 36
33. Did you know?
A rare-disease concept may appear in several clinical classifications, so a graph can represent the same concept without duplicating its identity.
Working checkpoint — rare-disease hierarchy: Deduplicate by ORPHAcode, not by path count. Preserve the complete tested family and every excluded feature; a polished shortlist is not a substitute for provenance.
For scientific writing, prefer “supports”, “is associated with” and “is predicted to” when stronger causal verbs are not justified.
Section 34 of 36
34. Write a reader-ready result
A strong report names the ORPHAcode, preferred term, entity type, release, classification path, mappings and unresolved scope questions.
Working checkpoint — cross-reference: Make the counting and mapping rules visible. Separate what the model estimates from the biological story proposed afterward, then name the extra evidence that story would require.
For students, the transferable habit is to ask: What was measured? Compared with what? What alternative explanation remains?
Section 35 of 36
35. Build a validation ladder
Verify code and definition, inspect level and parents, review mappings and changes, test cohort expansion, then seek domain review.
Working checkpoint — obsolete term: Strengthen concept identity before analysis. Treat identifiers, denominators and factor levels as scientific quantities: a silent mismatch can reverse an otherwise correct calculation.
For parents, a calm checkpoint is to ask how many independent samples support the claim and which assumption matters most.
Section 36 of 36
36. Finish with a reproducible bundle
Deliver source codes, release files, checksums, mapping tables, hierarchy rules, change log, query code, exclusions and review notes.
Working checkpoint — release provenance: Make every ontology-based cohort reproducible. Keep the independent sample, design, annotation and software version beside this decision so the evidence can be reconstructed.
For a classroom model, use invented counts and clearly label the activity as an analogy rather than a sequencing experiment.
Contents · Previous section · Continue to the Science Learning Hub