eClinicalWorks Python API Docs | dltHub

eClinicalWorks is a cloud-based EHR and practice management platform that provides FHIR R4-compliant APIs for accessing clinical, patient, and billing data. The REST API base URL is https://fhir4.eclinicalworks.com/fhir/r4/{practice_code} and all requests require a Bearer token via OAuth 2.0 SMART on FHIR.

dlt is an open-source Python library that handles authentication, pagination, and schema evolution automatically. dlthub provides AI context files that enable code assistants to generate production-ready pipelines. Install with uv add "dlt[hub]" and start loading eClinicalWorks data in under 10 minutes.

---

What data can I load from eClinicalWorks?

Here are some of the endpoints you can load from eClinicalWorks:

---

How do I authenticate with the eClinicalWorks API?

Authentication is performed using OAuth 2.0 via the SMART on FHIR profile, requiring an access token obtained through authorization code or client credentials (backend services) flows. Authenticated requests must include an 'Authorization' header with the value 'Bearer <access_token>'.

1. Get your credentials

1. Create an account on the eClinicalWorks developer portal (typically accessible via https://fhir.eclinicalworks.com/ or https://developers.eclinicalworks.com/). 2. Register your application within the developer portal to define your app type (patient-facing vs. backend/server-to-server). 3. For backend services, register your JWKS URL or upload your public key in the portal. 4. Upon approval, retrieve your Client ID and (for symmetric authentication) Client Secret from your portal dashboard. 5. Have the target eClinicalWorks practice authorize your application within their administration portal to connect your credentials to their specific environment.

2. Add them to .dlt/secrets.toml

Copy
[sources.eclinicalworks_source]
client_id = "your_client_id_here"
client_secret = "your_client_secret_here"
# If using asymmetric (recommended) auth, provide your private key path or JWKS details
private_key_path = "/path/to/private_key.pem"
# Practice-specific base URL assigned after authorization
base_url = "https://fhir.eclinicalworks.com/fhir/r4/{practice_code}"

dlt reads this automatically at runtime — never hardcode tokens in your pipeline script. For production environments, see setting up credentials with dlt for environment variable and vault-based options.

---

How do I set up and run the pipeline?

Set up a virtual environment and install dlt:

Copy
uv init
uv add "dlt[hub]"

1. Install the dlt AI harness:

Copy
uv run dlthub ai init --agent <your-agent> # <agent>: claude | cursor | codex

This installs project rules, a secrets management skill, appropriate ignore files, and configures the dlt MCP server for your agent. Learn more →

2. Install the rest-api-pipeline toolkit:

Copy
uv run dlthub ai toolkit install rest-api-pipeline

This loads the skills and context about dlt the agent uses to build the pipeline iteratively, efficiently, and safely. The agent uses MCP tools to inspect credentials — it never needs to read your secrets.toml directly. Learn more →

3. Start LLM-assisted coding:

Use /find-source to load data from the eClinicalWorks API into DuckDB.

The rest-api-pipeline toolkit takes over from here — it reads relevant API documentation, presents you with options for which endpoints to load, and follows a structured workflow to scaffold, debug, and validate the pipeline step by step.

4. Run the pipeline:

Copy
uv run python eclinicalworks_pipeline.py

If everything is configured correctly, you'll see output like this:

Copy
Pipeline eclinicalworks_pipeline load step completed in 0.26 seconds
1 load package(s) were loaded to destination duckdb and into dataset eclinicalworks_data
The duckdb destination used duckdb:/eclinicalworks.duckdb location to store data
Load package 1749667187.541553 is LOADED and contains no failed jobs

Inspect your pipeline and data:

Copy
uv run dlthub show

This opens the Pipeline Dashboard where you can verify pipeline state, load metrics, schema (tables, columns, types), and query the loaded data directly.

---

Python pipeline example

This example loads /token and /authorize from the eClinicalWorks API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:

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

@dlt.source
def eclinicalworks_source(access_token=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://fhir4.eclinicalworks.com/fhir/r4/{practice_code}",
            "auth": {"type": "bearer", "token": access_token},
        },
        "resources": [
            {"name": "patient", "endpoint": {"path": "Patient", "data_selector": "entry"}},
            {"name": "encounter", "endpoint": {"path": "Encounter", "data_selector": "entry"}}
        ],
    }
    yield from rest_api_resources(config)


def get_data() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="eclinicalworks_pipeline",
        destination="duckdb",
        dataset_name="eclinicalworks_data",
    )
    load_info = pipeline.run(eclinicalworks_source())
    print(load_info)

To add more endpoints, append entries from the resource table to the "resources" list using the same name, path, and data_selector pattern.

---

How do I query the loaded data?

Once the pipeline runs, dlt creates one table per resource. You can query with Python or SQL.

Python (pandas DataFrame):

Copy
import dlt

data = dlt.pipeline("eclinicalworks_pipeline").dataset()
sessions_df = data.patient.df()
print(sessions_df.head())

SQL (DuckDB example):

Copy
SELECT * FROM eclinicalworks_data.patient LIMIT 10;

In a marimo or Jupyter notebook:

Copy
import dlt

data = dlt.pipeline("eclinicalworks_pipeline").dataset()
data.patient.df().head()

See how to explore your data in marimo Notebooks and how to query your data in Python with dataset.

---

What destinations can I load eClinicalWorks data to?

dlt supports loading into any of these destinations — only the destination parameter changes:

Change the destination in dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. See the full destinations list.

---

Next steps

Continue your data engineering journey with the other toolkits of the dltHub AI harness:

• data-exploration — Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.
• dlthub-platform — Deploy, schedule, and monitor your pipeline in production.

Copy
uv run dlthub ai toolkit install data-exploration
uv run dlthub ai toolkit install dlthub-platform

• How to deploy a pipeline
• How to explore your data in marimo Notebooks
• How to query your data in Python with dataset
• Join the dlt community on Slack