Skip to main content
Health Atlas Clinical knowledge graph search

Provider

Clinicians with specialty and care-site affiliation through graph relationships.

881 records · 9 data fields · 2 relationships

Explore records
Relationship map — Provider 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 Provider.

Field definitions

searched as a name searched as an address searched as an identifier searched as prose feeds the semantic embedding points at another record, named under Links to

Field Type Description Links to
name folded into this row’s embedding string First and last name of the Provider.
gender folded into this row’s embedding string Gender. M is male, F is female.
specialty folded into this row’s embedding string Provider speciality.
organization_id Practices at string Foreign key to the Organization that employs this provider. Each provider has exactly one care site; each care site has one or many providers. Care site Pages only
address folded into this row’s embedding option<string> Provider's street address without commas or newlines.
city Folded into this row’s embedding — kept because clinicians span many cities across the metro, so a search like “clinic in Edina” can find them string Street address city.
state string Street address state abbreviation.
zip option<string> Street address zip or postal code.
record_id string This provider's source id, stored verbatim — the record's identity. Not a search term — find providers by name. Not shown on the record's own page: the page's address already carries this id.

Referenced by

Records that hold this record’s id

  • Each provider has zero or many visits; each visit has exactly one provider. Visit foreign key encounter.provider_id on each visit

Semantic search

Each provider stores embedding: a vector of 384 numbers computed at import from name, specialty, city, gender and address — the fields marked as folded into the embedding above. Search’s Vector and Hybrid tabs match a query against it by meaning, through the index hnsw_provider.

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

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

Try asking

Real values from Provider records. Click to search.

Margarite Harvey Lea Turcotte

Beyond text search

providers who treated Alzheimer's patients

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