Load Elation Health data to DuckDB

Elation Health API v2.0 provides a RESTful interface for accessing clinical, administrative, and scheduling data within the Elation EHR platform. Everything needed to build a working Elation Health → DuckDB pipeline is on this page: the API's base URL, authentication, endpoints, pagination and incremental field — plus a prompt that hands the whole job to your coding agent.

---

Build your Elation Health to DuckDB pipeline

Paste this prompt into Claude, Codex, or Cursor. The agent does the rest.

PromptCopy prompt
Run uvx dlthub-init@latest to build a pipeline from Elation Health to DuckDB and run it on dltHub

That scaffolds a dltHub workspace and installs the dltHub AI harness — the project rules, the secrets-management skill, and the dlt MCP server your agent needs to work safely. From there it reads the Elation Health API, proposes the endpoints to load, then writes, runs and validates the pipeline while you review rather than type. Credentials are inspected through MCP tools, so your agent never reads secrets.toml itself. How the LLM-native workflow works →

Prefer to write it yourself? Every fact the agent uses is below.

---

Elation Health API at a glance

These values come from the Elation Health API reference — the authoritative source if anything here looks out of date.

---

How do I authenticate with the Elation Health API?

All requests must be authenticated with an OAuth2 access token passed in the Authorization header as a Bearer token (e.g., 'Authorization: Bearer <access_token>').

1. Get your credentials

To obtain API credentials, log in to your Elation EHR account. Navigate to Settings, then click on API Access. Within this section, click on + Create API Key. Provide a Name for the key, select the API type (either Elation APIv2 or FHIR), and click Create. You will be provided with a Client ID and Client Secret, which must be saved immediately as the secret is not displayed again. Note: Self-service credential management is primarily available for sandbox environments; production credentials often require contacting Elation Support.

2. Add them to .dlt/secrets.toml

Copy
[sources.elation_health_source]
client_id = "your_client_id_here"
client_secret = "your_client_secret_here"
grant_type = "client_credentials"

dlt reads this file automatically at runtime. With the harness, the setup-secrets skill prompts you for the values and never handles the raw credential in chat. For production, see setting up credentials with dlt.

---

What Elation Health data can I load into DuckDB?

These are the Elation Health endpoints dlt can load into DuckDB:

---

How do I load only new Elation Health records?

The Elation Health API reference does not document a timestamp or sequence field for these endpoints, so there is nothing to advertise here as verified. Pick a field from the endpoints table above that increases with every write, then set it as the cursor_path.

Copy
{"name": "patients", "endpoint": {
    "path": "api/2.0/patients/",
    # Replace with a field that increases on every write.
    "incremental": {"cursor_path": "REPLACE_ME", "initial_value": "2024-01-01T00:00:00Z"},
}}

On the first run dlt loads everything from initial_value; on every run after that it requests only what changed and appends with write_disposition="merge" if you set a primary key. See incremental loading.

---

What does the generated Elation Health pipeline look like?

A standard dlt REST API pipeline — the same code you would write by hand, loading /oauth2/token/ and /patients/ from the Elation Health API into DuckDB:

Copy
import dlt
from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources

@dlt.source
def elation_health_source(token=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://api.app.elationemr.com/api/2.0/",
            "auth": {"type": "bearer", "token": token},
        },
        "resources": [
            {"name": "patients", "endpoint": {"path": "api/2.0/patients/", "data_selector": "results"}},
            {"name": "appointments", "endpoint": {"path": "api/2.0/appointments/", "data_selector": "results"}}
        ],
    }
    yield from rest_api_resources(config)


def load_elation_health_to_duckdb() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="elation_health_pipeline",
        destination="duckdb",
        dataset_name="elation_health_data",
    )
    load_info = pipeline.run(elation_health_source())
    print(load_info)


if __name__ == "__main__":
    load_elation_health_to_duckdb()

Run it with python elation_health_pipeline.py. The agent iterates on this until it loads cleanly — you review and approve, rather than write it from scratch.

---

How do I query Elation Health data in DuckDB?

dlt creates one table per resource. Query the loaded data with Python or SQL — or ask your agent to, through the MCP server's execute_sql_query tool.

Python (pandas DataFrame):

Copy
import dlt

data = dlt.pipeline("elation_health_pipeline").dataset()
df = data.patients.df()
print(df.head())

SQL:

Copy
SELECT * FROM elation_health_data.patients LIMIT 10;

See querying your data with dataset and exploring it in marimo notebooks.

---

How do I deploy the Elation Health to DuckDB pipeline in production?

The pipeline runs locally, which is ideal for prototyping and one-off analysis. When you need it on a schedule, monitored on every load, and shared with your team, deploy the same dlt code on the dltHub platform — no infrastructure to maintain. The prompt above already ends with "run it on dltHub", so your agent can take it there directly.

• Deploy & schedule — run the pipeline as a managed job with automatic retries.
• Monitor — observable job queues, alerting, and load metrics for every run.
• Transform — promote raw Elation Health loads into governed, documented models.
• Visualize & share — explore data in notebooks and publish live dashboards instead of static screenshots.

Book a demo →

---

What other destinations can I load Elation Health data to?

dlt loads into any of these — only the destination argument changes:

Set dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. On the dltHub platform the same pipeline runs against a managed Iceberg lakehouse. See the full destinations list.

---

Next steps

• Ready for production? Book a demo of the dltHub platform →
• dlt LLM-native workflow docs
• REST API source reference
• Join the dlt community on Slack