Skip to main content
Health Atlas Clinical knowledge graph search

Procedure

procedure_record

One procedure performed at one visit: its code and system, when it started and stopped, its base cost, and the reason recorded for it.

1,383,605 records · 11 data fields · 3 relationships

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

This data originates from Synthea as procedures (procedures.csv), one row per row, is stored in the procedure_record SurrealDB table, and displayed as Procedure for clinical-domain familiarity.

Relationship map — Procedure 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.

Field definitions

opens the record when pasted into search points at another record, named under Links to

Field Type Description Links to
patient_id Procedure of string Foreign key to the Patient. Each procedure has exactly one patient; each patient has zero or many procedures. Patient
encounter_id Performed during string Foreign key to the Encounter where the procedure was performed. Each procedure has exactly one visit; each visit has zero or many procedures. Visit
code Coded as string Procedure code from SNOMED-CT, or from CDT for dental procedures. Each procedure has exactly one procedure concept; each procedure concept has one or many procedures. Procedure concept Pages only
system string Specifies the code system — SNOMED-CT or CDT.
description string Description of the procedure.
start datetime The date and time the procedure was performed.
stop option<datetime> The date and time the procedure was completed, if applicable.
reason_code option<string> Diagnosis code from SNOMED-CT specifying why this procedure was performed.
reason_description option<string> Description of the reason code.
base_cost option<float> The line item cost of the procedure.
record_id string This procedure's identity, built at import from its visit's id, its code and its start and stop times — the source export gives the row no id of its own.

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

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

Not searchable

A procedure is reached from its visit, its patient or its procedure concept, or by pasting its id; search finds the concept.

Beyond text search

what else happened at this procedure's visit

Answering this means walking procedure → performed during → visit. The three shipped search arms — BM25, HNSW, RRF fusion — match text inside one table, so none can.