Care site
organizationClinics and hospitals with address, coordinates, providers, and visits.
197 records · 8 data fields · 2 relationships
Source: organizations.csv → table organization → displayed as Care site why?
This data originates from Synthea as organizations (organizations.csv), is stored in the organization SurrealDB table, and displayed as Care site for clinical-domain familiarity.
Relationship map — Care site highlighted
Click any node to explore its schema. Highlighted relationships connect to or from Care site.
Field definitions
searched as a name searched as an address searched as an identifier searched as prose feeds the semantic embedding
| Field | Type | Description |
|---|---|---|
name
folded into this row’s embedding
|
string |
Name of the Organization. |
address
folded into this row’s embedding
|
option<string> |
Organization's street address without commas or newlines. |
city
Folded into this row’s embedding — kept because care sites 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. |
location
|
option<geometry<point>> |
Latitude and longitude of the organization's address, collapsed into one point. |
phone
|
option<string> |
Organization's phone number. Sometimes multiple numbers. |
record_id
|
string |
This care site's source id, stored verbatim — the record's identity. Where the source lists one place under several ids (same name, street and city), the import keeps the id with the most visits and merges the others into this record. Not a search term — find care sites 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
Semantic search
Each care site stores embedding: a vector of 384 numbers computed at import from name, city 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_organization.
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 care site means, not where one row came from — that question is the substance of every care site record's own Provenance page, reachable from any care site record.
Types are SurrealDB's own: option<T> means
the value may be absent. Full reference:
SurrealDB data types.
Try asking
Real values from Care site records. Click to search.
Beyond text search
Answering this means walking organization ← visit → procedure. The three shipped search arms — BM25, HNSW, RRF fusion — match text inside one table, so none can.