Connect diseases to what treats them
Publish relationships linking existing Disease entities to Drug, Treatment, Procedure, and Symptom entities in the Health space. All entities already exist and this bounty joins them to enable richer queries.
Why it matters
The Health space holds 401 diseases, 278 drugs, 38 treatments, 75 procedures, and 400 symptoms. Almost none of them are connected. In a sample of 40 diseases, only 2 had a link to a treatment. The Treatments slot on Disease is defined in the schema but populated on zero entities. The Treats slot on Procedure is defined but populated on zero entities. Treatments and procedures sit as orphan name-lists with no relations to anything.
The drugs are in better condition but still inconsistent. Some drugs carry Treats and Related diseases relations. Others have nothing. The only consistent relation is Indications.
By contrast, Supplements in the same space carry 20+ relations per entity using the shared Treats property. A supplement is better connected than a drug.
This bounty joins diseases to the things that treat them. After it, a user can traverse from any disease to its drugs, treatments, procedures, and symptoms — and back from each to the diseases they relate to. The core question any person asks about a disease — what treats it? — becomes answerable.
What to publish
The relation properties already exist in the schema. Most are empty. This bounty fills them.
For each Disease entity, populate:
Treatments — link to Treatment entities that address this disease
Related drugs — link to Drug entities used to treat this disease
Common procedures — link to Procedure entities used to treat or manage this disease
Symptoms — link to Symptom entities associated with this disease
For each Treatment entity, populate:
Treats — link back to the Disease entities it addresses (this property is already used by Supplement, Endocrine hormone, and Procedure — attaching it to Treatment is the only schema change on this side)
For each Procedure entity, populate:
Treats — link to the Disease entities it addresses (slot already exists, currently 0% populated)
For each Drug entity, populate:
Related diseases — link to Disease entities it treats (slot exists, partially populated — complete and standardize)
For each Symptom entity, populate:
Associated diseases — link to Disease entities where this symptom appears (slot exists, partially populated — complete and standardize)
All relationships go both directions. Geo relations are unidirectional — setting Disease.Treatments to a Treatment does not automatically create Treatment.Treats back to that Disease. Both sides must be set manually.
Every target entity already exists in the space. Nothing needs inventing. Link to existing entities by ID, never create duplicates.
Scope
Four bidirectional relationship pairs across many diseases, drugs, treatments, procedures, and ~200+ symptoms. Prioritize diseases with the highest clinical relevance first (heart disease, diabetes, hypertension, cancer, depression, asthma, COPD, stroke, arthritis, infectious diseases). All 38 treatments and all 75 procedures should receive at least one Treats relationship. Drugs and symptoms with existing partial relationships should be completed and standardized, not overwritten.
Two existing property entities need to be attached to new types (no new properties created):
Treats → attached to Treatment type (already used by Supplement, Endocrine hormone, Procedure)
Common procedures → attached to Disease type (already used by Organ)
Potential sources
FDA labels (DailyMed, NLM) for drug-disease treatment relationships
Clinical practice guidelines (NICE, WHO, USPSTF) for treatment and procedure indications
ICD-10 (WHO 2019) for disease classification cross-referencing
Existing entity descriptions in the Health space for established relationships