PointClickCare Python API Docs | dltHub
Build a PointClickCare-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.
Last updated:
PointClickCare is a healthcare EHR platform for long-term care and post-acute facilities that exposes RESTful APIs (including a FHIR R4 USCDI API and proprietary APIs) for accessing patient, facility, and clinical data. The REST API base URL is https://connect.pointclickcare.com and all API requests require an OAuth 2.0 access token sent as a Bearer token in the Authorization header.
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 PointClickCare data in under 10 minutes.
What data can I load from PointClickCare?
Here are some of the endpoints you can load from PointClickCare:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| facilities | orgs/{orgId}/facs | GET | data | List facilities for an organization (connect.pointclickcare.com/api/public/preview1); response includes paging object with hasMore, page, pageSize |
| patients | orgs/{orgId}/patients | GET | data | List residents/patients; supports facId and patientStatus query filters; records keyed by patientId |
| observations | orgs/{orgId}/observations | GET | data | Pull vitals/observations by patient, date range (startDate/endDate), type filter; supports pagination |
| diagnostic_reports | orgs/{orgId}/diagnostic-reports | GET | data | List lab/diagnostic reports; supports patientId and reportType filters; records keyed by observationId |
| conditions | orgs/{orgId}/conditions | GET | data | List patient conditions/diagnoses; supports patientId filter; records keyed by conditionId |
| patients (v2) | patients | GET | (not documented) | List residents/patients on api.pointclickcare.com/v2 base URL (6 params) |
| patient (v2) | patients/{patientId} | GET | (not documented) | Get a single resident/patient on api.pointclickcare.com/v2 base URL |
| patient_vitals (v2) | patients/{patientId}/vitals | GET | (not documented) | Get patient vitals on api.pointclickcare.com/v2 base URL |
| patient_diagnoses (v2) | patients/{patientId}/diagnoses | GET | (not documented) | Get patient diagnoses/condition records on api.pointclickcare.com/v2 base URL |
How do I authenticate with the PointClickCare API?
PointClickCare uses OAuth 2.0 (SMART on FHIR / authorization code flow); access tokens are obtained from the token endpoint (e.g. https://connect.pointclickcare.com/auth/token or https://login.pointclickcare.com/oauth2/token) using registered app client credentials, and every API request must include the header 'Authorization: Bearer <access_token>'. FHIR API calls also use 'Accept: application/fhir+json' and the tenant ID is appended to the base URL path (e.g. https://connect2.pointclickcare.com/fhir/R4/{tenantId}).
1. Get your credentials
- Contact PointClickCare's Partnership team via the 'Apply for Partnership' form on pointclickcare.com; once the developer program (USCDI Connector or Marketplace) is determined, you receive an email link to create a Developer Portal account at developer.pointclickcare.com. 2. Create your Developer Portal account (select 'USCDI Connector' if applicable) and fill out the form with the details shared with your PCC Partner Manager; the account must be approved by PointClickCare, after which you receive an email verification. 3. Set up 2-Factor Authentication on your account (required to register an App; instructions are under the Documentation tab in the Developer Portal). 4. Click your user profile button in the top right corner and open the 'My Apps' tab to create your App: enter an App name (the first App must be of type 'Development' so you can test against the PCC Sandbox), choose an App Type (Patient, Provider, or Bulk), describe functionality, select the authentication method, provide required URLs, FHIR scopes, and the Common Name of your SSL certificate (required for approval). 5. Development Apps are auto-approved and enabled in the PCC Sandbox; Production Apps require PointClickCare approval. 6. Your App Client ID and Client Secret are then available in your App listing under 'My Apps' in the Developer Portal. Sandbox test credentials are available under 'My Sandboxes' (patient apps use credentials beginning with 'ConnecterCareCenterUser', provider apps with 'vendortest').
2. Add them to .dlt/secrets.toml
[sources.pointclickcare_source] client_id = "your_client_id_here" client_secret = "your_client_secret_here"
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:
uv init uv add "dlt[hub]"
1. Install the dlt AI harness:
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:
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 PointClickCare 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:
uv run python pointclickcare_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline pointclickcare_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset pointclickcare_data The duckdb destination used duckdb:/pointclickcare.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
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 patients and facilities from the PointClickCare API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:
import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def pointclickcare_source(access_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://connect.pointclickcare.com", "auth": {"type": "bearer", "token": access_token}, }, "resources": [ {"name": "patients", "endpoint": {"path": "orgs/{orgId}/patients", "data_selector": "data"}}, {"name": "observations", "endpoint": {"path": "orgs/{orgId}/observations", "data_selector": "data"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="pointclickcare_pipeline", destination="duckdb", dataset_name="pointclickcare_data", ) load_info = pipeline.run(pointclickcare_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):
import dlt data = dlt.pipeline("pointclickcare_pipeline").dataset() sessions_df = data.patients.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM pointclickcare_data.patients LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("pointclickcare_pipeline").dataset() data.patients.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 PointClickCare data to?
dlt supports loading into any of these destinations — only the destination parameter changes:
| Destination | Example value |
|---|---|
| DuckDB (local, default) | "duckdb" |
| PostgreSQL | "postgres" |
| BigQuery | "bigquery" |
| Snowflake | "snowflake" |
| Redshift | "redshift" |
| Databricks | "databricks" |
| Filesystem (S3, GCS, Azure) | "filesystem" |
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.
uv run dlthub ai toolkit install data-exploration uv run dlthub ai toolkit install dlthub-platform
Was this page helpful?
Community Hub
Need more dlt context for PointClickCare?
Request dlt skills, commands, AGENT.md files, and AI-native context.