Load TELUS Collaborative Health Record data to DuckDB

TELUS Collaborative Health Record (CHR) Enterprise API is a GraphQL service used for accessing, creating, and updating clinical data within a CHR domain. Everything needed to build a working TELUS Collaborative Health Record → 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 TELUS Collaborative Health Record 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 TELUS Collaborative Health Record 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 TELUS Collaborative Health Record 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.

---

TELUS Collaborative Health Record API at a glance

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

---

How do I authenticate with the TELUS Collaborative Health Record API?

Authentication uses a self-signed JSON Web Token (JWT) signed with RS512, which must be provided in the 'Authorization' header using the 'Bearer' scheme. The token must include an issuer (iss) claim matching the configured API Consumer, and expire within 15 minutes of being issued.

1. Get your credentials

Access to the TELUS Collaborative Health Record (CHR) Enterprise API requires a formal onboarding process involving a signed contract, privacy and security reviews, and TELUS Health enabling API access for your specific CHR domain. Once enabled: 1) Log in to the CHR with a TELUS CHR Support account. 2) Navigate to Settings > Enterprise API. 3) Click '+ New Consumer' to create an API Consumer. 4) Provide a name and your 2048-bit RSA public key (in PEM format). 5) The API Consumer will provide an 'ISS' (Issuer) value, which you use to sign your own short-lived (max 15 minutes) RS512 JWTs locally. There is no central API key; you act as your own identity provider using this public/private key pair.

2. Add them to .dlt/secrets.toml

Copy
[sources.telus_collaborative_health_record_source]
token = "REPLACE_ME"

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 TELUS Collaborative Health Record data can I load into DuckDB?

These are the TELUS Collaborative Health Record endpoints dlt can load into DuckDB:

---

How do I load only new TELUS Collaborative Health Record records?

The TELUS Collaborative Health Record 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": "appointments", "endpoint": {
    "path": "/enterprise/graphql",
    # 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 TELUS Collaborative Health Record pipeline look like?

A standard dlt REST API pipeline — the same code you would write by hand, loading appointments and patients from the TELUS Collaborative Health Record API into DuckDB:

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

@dlt.source
def telus_collaborative_health_record_source(token=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "The API endpoint is domain-specific and must be copied from the CHR Settings > Enterprise API page for the specific CHR domain.",
            "auth": {"type": "bearer", "token": token},
        },
        "resources": [
            {"name": "appointments", "endpoint": {"path": "/enterprise/graphql", "data_selector": "data.appointments"}},
            {"name": "patients", "endpoint": {"path": "/enterprise/graphql", "data_selector": "data.patients"}}
        ],
    }
    yield from rest_api_resources(config)


def load_telus_collaborative_health_record_to_duckdb() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="telus_collaborative_health_record_pipeline",
        destination="duckdb",
        dataset_name="telus_collaborative_health_record_data",
    )
    load_info = pipeline.run(telus_collaborative_health_record_source())
    print(load_info)


if __name__ == "__main__":
    load_telus_collaborative_health_record_to_duckdb()

Run it with python telus_collaborative_health_record_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 TELUS Collaborative Health Record 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("telus_collaborative_health_record_pipeline").dataset()
df = data.appointments.df()
print(df.head())

SQL:

Copy
SELECT * FROM telus_collaborative_health_record_data.appointments LIMIT 10;

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

---

How do I deploy the TELUS Collaborative Health Record 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 TELUS Collaborative Health Record 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 TELUS Collaborative Health Record 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