Elation Health connector for AI agents

Tools your clinical agent reaches for on Elation Health, scoped per user.

CALL ANY TOOL

52 read-only tools for clinical records in Elation Health over FHIR: search and read patients, conditions, medications, observations, encounters, documents, care plans, coverage, and orders.

elation_allergy_intolerance_read

Read allergy intolerance

Get one AllergyIntolerance resource from Elation by its ID. Returns the AllergyIntolerance with code (RxNorm or SNOMED CT substance), clinicalStatus, verificationStatus, category, criticality, reaction (manifestation and severity), onsetDateTime, recordedDate and patient reference. Use this to open one allergy by ID. Use elation_allergy_intolerance_search to list a patient's allergies.

Parameters

Name

Type

Required

Description

allergy_intolerance_id

string

Required

Elation logical ID of the AllergyIntolerance resource (the id element, without the 'AllergyIntolerance/' prefix). Example: 12345.

elation_allergy_intolerance_search

Search allergy intolerance

elation_binary_read

Read binary

elation_care_plan_search

Search care plan

elation_care_team_read

Read care team

elation_condition_search

Search condition

Search a patient's conditions in Elation: problem list items, health concerns and encounter diagnoses, filtered by category, status, code, encounter or date. Returns a FHIR searchset Bundle whose entry array holds matching Condition resources (code, category, clinicalStatus, onsetDateTime, recordedDate and encounter) and a 'next' link when more pages exist. Use category problem-list-item for the problem list, health-concern for health concerns, or encounter-diagnosis with an encounter ID for one visit's diagnoses. Use elation_condition_read for one condition by ID. Requires an Elation patient ID: run elation_patient_search first. If the result has a 'next' link, use elation_next_page to get more.

Parameters

Name

Type

Required

Description

patient

string

Required

Elation patient ID (the Patient resource id) whose conditions to return. Accepts the bare id or the reference form Patient/<id>. Example: 12345.

_count

integer

Optional

Maximum number of resources to return in one page. The server picks a default when omitted. Example: 20.

abatement_date

string

Optional

Filter by abatement (resolution) date. Use YYYY-MM-DD (or a full date-time), optionally prefixed with a comparator: ge (on or after), le (on or before), gt, lt. Example: ge2024-01-01.

asserted_date

string

Optional

Filter by asserted date. Use YYYY-MM-DD (or a full date-time), optionally prefixed with a comparator: ge (on or after), le (on or before), gt, lt. Example: ge2024-01-01.

category

string

Optional

Filter by condition category, as a FHIR token: code or system|code. Valid codes: problem-list-item, health-concern, encounter-diagnosis. Example: problem-list-item.

clinical_status

string

Optional

Filter by clinical status, as a FHIR token: code or system|code. Valid codes: active, recurrence, relapse, inactive, remission, resolved (system http://terminology.hl7.org/CodeSystem/condition-clinical). Separate several with commas. Example: active.

code

string

Optional

Filter by condition code (SNOMED CT or ICD-10-CM), as a FHIR token: code or system|code. Example: http://snomed.info/sct|44054006.

encounter

string

Optional

Return only diagnoses recorded for this Elation encounter ID. Elation documents it combined with category encounter-diagnosis. Example: 67890.

onset_date

string

Optional

Filter by onset date. Use YYYY-MM-DD (or a full date-time), optionally prefixed with a comparator: ge (on or after), le (on or before), gt, lt. Example: ge2024-01-01.

recorded_date

string

Optional

Filter by date the condition was recorded. Use YYYY-MM-DD (or a full date-time), optionally prefixed with a comparator: ge (on or after), le (on or before), gt, lt. Example: ge2024-01-01.

elation_coverage_read

Read coverage

elation_device_search

Search device

elation_diagnostic_report_read

Read diagnostic report

elation_diagnostic_report_search

Search diagnostic report

elation_encounter_read

Read encounter

elation_encounter_search

Search encounter

Search Elation encounters (visits) for a patient by date, class, type, status or location, or look one up by identifier. Returns a FHIR searchset Bundle whose entry array holds matching Encounter resources (status, class, type, period, participant and location) and a 'next' link when more pages exist. Use this to list a patient's visits. Pass an encounter ID to elation_condition_search (category encounter-diagnosis) or elation_medication_request_search to see what happened at a visit. Use elation_encounter_read for one encounter by ID. Requires an Elation patient ID (run elation_patient_search first) unless you search by Identifier or Resource ID. If the result has a 'next' link, use elation_next_page to get more.

Parameters

Name

Type

Required

Description

_count

integer

Optional

Maximum number of resources to return in one page. The server picks a default when omitted. Example: 20.

_id

string

Optional

Return only the resource with this logical id, wrapped in a searchset Bundle. Example: 12345.

class

string

Optional

Filter by encounter class, as a FHIR token: code or system|code. Codes come from http://terminology.hl7.org/CodeSystem/v3-ActCode, e.g. AMB (ambulatory), VR (virtual). Example: AMB.

date

string

Optional

Filter by encounter date. Use YYYY-MM-DD (or a full date-time), optionally prefixed with a comparator: ge (on or after), le (on or before), gt, lt. Example: ge2024-01-01.

identifier

string

Optional

Filter by an encounter identifier, as a FHIR token: code or system|code. Example: 67890.

location

string

Optional

Return only encounters at this Elation Location ID. Example: 2468.

patient

string

Optional

Elation patient ID (the Patient resource id) whose encounters to return. Accepts the bare id or the reference form Patient/<id>. Example: 12345.

status

string

Optional

Filter by status. One value or a comma-separated list. Valid values: planned, arrived, triaged, in-progress, onleave, finished, cancelled, entered-in-error, unknown. Example: finished.

type

string

Optional

Filter by encounter type, as a FHIR token: code or system|code. Example: http://snomed.info/sct|185349003.

elation_goal_read

Read goal

elation_immunization_search

Search immunization

elation_location_read

Read location

elation_medication_dispense_search

Search medication dispense

elation_medication_read

Read medication

elation_medication_request_search

Search medication request

elation_next_page

elation_observation_read

Read observation

elation_organization_search

Search organization

elation_patient_read

Read patient

elation_practitioner_read

Read practitioner

elation_practitioner_role_search

Search practitioner role

elation_practitioner_search

Search practitioner

elation_procedure_read

Read procedure

elation_questionnaire_response_read

Read questionnaire response

elation_questionnaire_response_search

Search questionnaire response

elation_service_request_read

Read service request

elation_service_request_search

Search service request

For more tools, view docs.

Build your Agent

Same auth pattern across LangChain, OpenAI, Anthropic, and Google ADK.

import { ScalekitClient } from "@scalekit-sdk/node";
import { createReactAgent } from "@langchain/langgraph/prebuilt";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

// Elation Health tools scoped to this user
const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["elation"], toolNames: [
    "elation_patient_search",
    "elation_condition_search",
    "elation_medication_request_search"] },
  pageSize: 100,
});

const agent = createReactAgent({ llm, tools });
await agent.invoke({ messages: [{ role: "user", content: "Find Maria Lopez and list her active conditions and medications" }] });

import OpenAI from "openai";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);
const openai = new OpenAI();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["elation"] }, pageSize: 100,
});

const res = await openai.chat.completions.create({
  model: "gpt-5",
  messages: [{ role: "user", content: "Find Maria Lopez and list her active conditions and medications" }],
  tools,
});

// Execute the tool call with the user's vaulted Elation Health OAuth token
await sk.tools.executeTool(res.choices[0].message.tool_calls[0], "user_123");

import Anthropic from "@anthropic-ai/sdk";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);
const anthropic = new Anthropic();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["elation"] }, pageSize: 100,
});

const msg = await anthropic.messages.create({
  model: "claude-sonnet-5",
  max_tokens: 1024,
  messages: [{ role: "user", content: "Find Maria Lopez and list her active conditions and medications" }],
  tools,
});

// Tool call runs with the user's vaulted Elation Health OAuth token
await sk.tools.executeTool(msg.content, "user_123");

import { Agent } from "@google/adk/agents";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["elation"] }, pageSize: 100,
});

const agent = new Agent({
  name: "clinical_agent",
  model: "gemini-2.5-pro",
  instruction: "Elation Health tools scoped to this user",
  tools,
});

await agent.run("Find Maria Lopez and list her active conditions and medications");

Try these prompts

Copy any prompt into your agent. Each maps directly to a Elation Health tool. Click to copy, paste into your agent, done.

Patient records

Copy the prompt

Copied

Search for patients named Maria Lopez born in 1984.

Copy the prompt

Copied

List the active conditions on this patient's problem list.

Copy the prompt

Copied

Show this patient's insurance coverage.

Clinical data

Copy the prompt

Copied

Get this patient's vital signs from the last 3 visits.

Copy the prompt

Copied

List lab and imaging reports for this patient from the last 6 months.

Copy the prompt

Copied

Show this patient's immunization history.

Visits and documents

Copy the prompt

Copied

List this patient's encounters from this year.

Copy the prompt

Copied

Find the clinical notes from this patient's last visit.

Copy the prompt

Copied

Show open lab and imaging orders for this patient.

SEE HOW AUTH WORKS

Each user signs in to Elation Health once, and Scalekit stores and refreshes their tokens. Credentials stay vaulted, every call is scope checked, and every action is logged.

Authorize

Your user connects

Elation Health

once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access

Who:

user ‘A’

when:

Once per user

access:

Limited to user

Store

Their

Elation Health

token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection

vault:

encrypted

scope:

per-user

tokens:

auto-refreshed

Resolve

When your agent calls a

Elation Health

tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs

speed:

~40ms

check:

before every call

seen by:

nobody

Audit

Every

Elation Health

tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it

history:

90 days

export:

SIEM-ready

logged:

every call

Test other agents

See the same per-user auth pattern across other healthcare connectors.

Support and Ops Teams

Meeting prep

Pulls agenda, participant context, and open action items before every meeting.

Engineering Teams

Slack triage

Polls Slack for new messages, classifies bugs and support requests with a LangGraph router, files GitHub issues or Zendesk tickets, and confirms in the thread.

Why Scalekit

Secure your agent's access. Connectors ship in minutes

01.

Shared tokens break per-user analytics

A shared Elation Health token looks fine in a demo. In production every chart read looks like one service account, and you cannot tell which user triggered it. Scalekit resolves the credential of the actual user who triggered the agent, never a shared bot.

// shared token
audit → bot_service_account

// scalekit
audit → user_abc ✓

02.

Authentication is not authorization

03.

Multi-tenancy is architectural

04.

Elation Health today. Ten connectors tomorrow.

“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”

Venu Madhav Kattagoni

Head of Engineering / Von

FAQs

Frequently Asked Questions

Does the agent access Elation Health as the user or through a shared service account?

As the user. Each user signs in to Elation Health once with SMART on FHIR, and Scalekit stores and refreshes their tokens. Every chart read in your audit trail is attributed to that user, not a shared service account.

Where is the Elation Health OAuth token stored?

In Scalekit's managed AES-256 token vault, namespaced per tenant. Refresh is automatic. Revocation is a single dashboard action. Credentials never appear in prompts, logs, or LLM context.

Can I limit what the agent does in Elation Health?

Yes. Every Elation Health tool is read-only, so the agent can search and read chart data but cannot change it. Filter by tool name in listScopedTools to narrow it further, for example to patient, condition, and medication tools only. Scalekit also enforces scope checks before every API call.

What happens when a user revokes Elation Health access?

The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.

How does the agent page through long results in Elation Health?

Search tools return a FHIR searchset Bundle. When there are more results, elation_next_page follows the next link in that Bundle to fetch the next page.