Skip to main content

Procedure concept

procedure

Procedure codes, each shared across patients, with the procedures filed under it.

879 records · 8 data fields · 2 relationships

Explore records
Source: procedures.csv → table procedure → displayed as Procedure concept why?

This data originates from Synthea as procedures (procedures.csv), folded to one row per code, is stored in the procedure SurrealDB table, and displayed as Procedure concept: the code that every procedure performed with it is filed under.

Relationship map — Procedure 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 Procedure 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 Procedure code from SNOMED-CT, or from CDT for dental procedures.
system string Terminology system for the code, typically SNOMED-CT.
description folded into this row’s embedding string Description of the procedure.
base_cost_median option<float> Median line-item cost across every occurrence of this procedure — a concept-grain summary of BASE_COST, computed at import time rather than one representative row.
base_cost_min option<float> Lowest line-item cost observed for this procedure, across every occurrence.
base_cost_max option<float> Highest line-item cost observed for this procedure, across every occurrence.
base_cost_samples option<int> The number of occurrences the median/min/max above are computed over.
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 procedure concept has one or many patients; each patient has zero or many procedure concepts. Patient edge table has_procedure — one row per patient and procedure concept
  • Each procedure concept has one or many procedures; each procedure has exactly one procedure concept. Procedure code procedure_record.code on each procedure

Semantic search

Each procedure 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_procedure.

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 procedure concept means, not where one row came from — that question is the substance of every procedure concept record's own Provenance page, reachable from any procedure 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 Procedure concept records. Click to search.

Beyond text search

which providers performed dialysis

Answering this means walking procedure concept ← procedure ← visit → seen by → provider. The three shipped search arms — BM25, HNSW, RRF fusion — match text inside one table, so none can.