Skip to main content
Health Atlas Clinical knowledge graph search

Diagnosis concept

condition

Diagnosis codes, each shared across patients, with the diagnoses filed under it.

778 records · 4 data fields · 2 relationships

Explore records
Source: conditions.csv → table condition → displayed as Diagnosis concept why?

This data originates from Synthea as conditions (conditions.csv), folded to one row per code, is stored in the condition SurrealDB table, and displayed as Diagnosis concept: the code that every diagnosis made with it is filed under.

Relationship map — Diagnosis concept highlighted
Has visit Attended by At care site Recorded diagnosis Prescribed Included procedure Has care plan Addresses diagnosis Practices at Started care plan Billed as Has claim Billed to Primary Secondary Has expense year Covered by Has diagnosis Has medication Has procedure PatientDIM · ACTOR GRAIN VisitFACT · EVENT GRAIN Diagnosis conceptDIM · CODE GRAIN DiagnosisFACT · EVENT GRAIN Medication conceptDIM · CODE GRAIN MedicationFACT · EVENT GRAIN Procedure conceptDIM · CODE GRAIN ProcedureFACT · EVENT GRAIN ProviderDIM · ACTOR GRAIN Care planFACT · EVENT GRAIN Care siteDIM · ACTOR GRAIN ClaimFACT · EVENT GRAIN PayerDIM · ACTOR GRAIN Expense yearFACT · YEAR ROLLUP Coded as Coded as Coded as

Click any node to explore its schema. Highlighted relationships connect to or from Diagnosis concept.

Field definitions

searched as a name searched as an address searched as an identifier searched as prose feeds the semantic embedding

Field Type Description
code string Diagnosis code from SNOMED-CT or ICD10.
system string Specifies the code system — SNOMED-CT or ICD10.
description folded into this row’s embedding string Description of the condition.
record_id string The clinical code this record represents, same value as the code column — the natural key every row sharing this code was deduplicated onto.

Referenced by

Records that hold this record’s id, or are linked through an edge table

  • Each diagnosis concept has one or many patients; each patient has one or many diagnosis concepts. Patient edge table has_condition — one row per patient and diagnosis concept
  • Each diagnosis concept has one or many diagnoses; each diagnosis has exactly one diagnosis concept. Diagnosis code diagnosis.code on each diagnosis

Semantic search

Each diagnosis concept stores embedding: a vector of 384 numbers computed at import from description — the field marked as folded into the embedding above. Search’s Vector and Hybrid tabs match a query against it by meaning, through the index hnsw_condition.

Provenance where this row came from · 7 fields
Field Type Description
source_table string Synthea CSV this row was read from.
source_snapshot_id string Corpus generation this row belongs to.
ingest_run_id string Import run that wrote the row.
generation_run_id string Synthea run that produced the source CSV.
load_timestamp datetime When the row was written.
source_role string Role this source played for the record.
contributing_sources option<array<string>> Other rows that contributed to this record.

Collapsed here because a reader came for what diagnosis concept means, not where one row came from — that question is the substance of every diagnosis concept record's own Provenance page, reachable from any diagnosis concept record.

Types are SurrealDB's own: option<T> means the value may be absent. Full reference: SurrealDB data types.

Try asking

Real values from Diagnosis concept records. Click to search.

Osteoporosis Epilepsy Atrial fibrillation

Beyond text search

which patients have Alzheimer's

Answering this means walking condition ← has diagnosis concept ← patient. The three shipped search arms — BM25, HNSW, RRF fusion — match text inside one table, so none can.