Skip to content
Start free
← All industries

Healthcare applications

Connect the records
around each encounter.

Build record exploration and knowledge workflows with encounter data, documents and care-team relationships.

Start with your data model Discuss your workflow

A record with a way back to its context.

Choose an encounter to see the source documents and team references connected to it.

Encounter context explorerConceptual application data
One patient recordConnected by a stable ID
patient:07
Selected encounter

Visit record

encounter:12

Open the encounter fields and follow its document and team references.

SQL · fieldsGraph · relationships
Linked document
Visit summary
document:31Revision 2
Care-team reference
Encounter team
team:08Assigned in the source record

Illustrative records. The application loads related data by ID and retains its source context.

Model the relationships

5 use cases / Healthcare

The right modalities for your workflow.

Start with the combination that fits your question. These are recommended starting points; the best fit depends on your data and query patterns.

Healthcare: use cases, recommended query modalities and why each combination fits.
Use caseRecommended modalitiesWhy this combination fits
Encounter workspaces

Connect an encounter to its document and care-team references.
SQL Graph

SQL retrieves encounter fields and dates. Graph follows the declared links to documents, teams and related operational records.
Referral coordination

Track referral status alongside its assigned team and follow-up tasks.
SQL Graph

SQL filters referral and task status. Graph connects the encounter, receiving service and responsible team.
Connected document retrieval

Find specific wording in the documents linked to an encounter.
SQL Graph FTS

SQL selects encounter records, Graph resolves associated documents, and FTS searches their indexed text for relevant terms.
Service knowledge retrieval

Find intake procedures and operational guidance for staff.
SQL FTS Vector

FTS matches service terminology, Vector retrieves related guidance, and SQL supplies the source revision and service metadata.
Service capacity reporting

Inspect appointment, queue and referral workloads.
SQL

SQL filters dates and service locations, joins operational records and groups workloads by status or team.

Combine query results in your application using shared record IDs. Keep text indexes and embeddings updated as the source data changes.

Four complementary query models

Fields. Relationships.
Meaning. Words.

Choose the query for the task, then load the original records by ID.

Explore the data models
SQL Encounter fields and status

Filter source, time and workflow attributes.

 Graph Document and team links

Traverse the relations your schema declares.

 Vector Related reference material

Search embeddings from your chosen model.

 Full-text Exact document language

Match titles, phrases and reference codes.

Implementation path

Preserve the source
as you connect the data.

Start with one operational workflow and a clear model for record identity, updates and access.

Follow an ingestion example
  1. 01

    Keep stable references.

    Register source IDs, encounter dates, document revisions and team relations in your schemas.

  2. 02

    Index explicitly.

    Write rows, supply embeddings and index selected text through separate calls; track updates and retries.

  3. 03

    Control what the application shows.

    Apply access rules before presenting records or retrieved text, and retain their source metadata.

    Read the access guide

Start with an encounter.
Build out the context.

Build a first example Explore other industries