syndrome
Let an agent handle syndromes as clinical categories with codes, features and causes, give only general information, and direct individual questions to clinicians.
Research draft, second pass
A second pass drafted this model: the structure a model of this thing needs, and what is known about it in the world. The line under this one says how the second half was obtained - researched against sources, or recalled without web access, in which case nothing here was read anywhere and every claim is a lead to verify. Unreviewed either way.
written by Claude from model knowledge without web access - no source was read, every claim is a lead to verify
Researched by: Claude
Purpose and description
Let an agent handle syndromes as clinical categories with codes, features and causes, give only general information, and direct individual questions to clinicians.
A set of medical signs and symptoms that occur together and characterise a particular condition, sometimes with a known cause (such as a genetic syndrome) and sometimes not.
What it is for: Recognising patterns of symptoms to guide diagnosis, care and research.
It can be diagnose it, by clinicians; classify it, with codes; support affected people and families; research its causes.
Distinguishing features
A pattern of features occurring together
Cause may be known or unknown
Many are rare diseases
Features vary between individuals
What it looks like
No single appearance; features vary by syndrome and person.
How it is recognised
Only clinical assessment establishes a syndrome
Codes in ICD-11 or Orphanet
Named syndromes such as Bloom syndrome
Related models
is a kind of - condition
is made of - features
can be caused by - genetic
is classified by - codes
In practice
Families and kinds
genetic syndromes
syndromes of unknown cause
neurocutaneous syndromes
tumour predisposition syndromes
Identifiers
ORPHAcode numeric rare diseases
OMIM number six digits genetic conditions
ICD-11 code alphanumeric WHO
Standards and regulation
WHO ICD-11
EU rare disease policies and European Reference Networks
Health data protection law
Failure modes and hazards
Self-diagnosis from lists of features
Stigmatising descriptions
Outdated names
Also called
+849
Where this came from
wikidata · CC0 1.0
Also registered as vr.tr.syndrome
Drafted structure
Bundle to layer to finding to question, as the second pass will find it: 4 bundles · 8 layers · 8 findings · 16 questions.
Classification Which syndrome.
Codes identify syndromes.
Codes
ORPHA, OMIM, ICD.
Codes
Codes.
- Which codes identify this syndrome? provenance
- Has its name changed? provenance
Cause
Known or unknown.
Cause
Cause.
- What is known about its cause? provenance
- Is it inherited? boundary
Features Signs and symptoms.
Features vary.
Common features
Typical signs.
Features
Typical features.
- What are its typical features? definition
- How variable are they? measurement
Diagnosis
How it is diagnosed.
Diagnosis
Diagnostic approach.
- How is it diagnosed? definition
- Who should the person see? action
Care Management and support.
Care is coordinated by specialists.
Management
Guidelines.
Management
Care guidelines.
- What do care guidelines recommend? provenance
- Which specialist centres exist? provenance
Support
Patient groups.
Support
Support organisations.
- Which patient organisations support people with it? action
- How can families connect? action
Handling Language and privacy.
Respect and privacy matter.
Language
Respectful terms.
Language
Respectful description.
- Is the description respectful and person-first? boundary
- Is the name current? provenance
Privacy
Health data.
Privacy
Data rules.
- Is health information being shared lawfully? boundary
- Could it identify a person? boundary
What the second pass must settle
- Should syndromes be instances with Orphanet and OMIM codes?
- How should naming changes be tracked?
- How should agents signpost rare disease support?