TELUS Health CHR Enterprise API

The TELUS Health Collaborative Health Record (CHR) Enterprise API is a GraphQL interface onto the CHR ambulatory-care platform used by Canadian clinics and allied health professionals. Its published introspection document describes 505 types, 64 root queries and 49 mutations spanning patients, appointments and availability, encounters, referrals, cases, tasks, group visits, attachments, letters, lab results (including OLIS lab messages), allergy and medication records, health profiles, facilities, providers and work hours. Pagination follows the GraphQL Cursor Connections specification (default 50, maximum 100 records per page). Authentication is unusual and notably strong: the consumer generates a 2048-bit RSA key pair, registers the public key on an API Consumer inside the CHR account, and signs its own RS512 JWT that must carry a matching iss claim and expire within 900 seconds — there is no authorization server, no token endpoint and no client secret. A companion Event Notification Service pushes 21 signed webhook topics carrying identifiers only, with no personal or personal-health information in the payload. Every API action is audit-logged for 90 days. The API ships on a bi-weekly release train with a dated public changelog going back to 2022, but it is a paid feature available to select customers, and the executable endpoint is issued per clinic account rather than published.

Documentation

Other Resources

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/telus-health-chr-enterprise-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

A second provider on the same verified email joins the account you already have.

API entry from apis.yml

apis.yml Raw ↑
aid: telus:telus-health-chr-enterprise-api
name: TELUS Health CHR Enterprise API
description: 'The TELUS Health Collaborative Health Record (CHR) Enterprise API is a GraphQL interface
  onto the CHR ambulatory-care platform used by Canadian clinics and allied health professionals. Its
  published introspection document describes 505 types, 64 root queries and 49 mutations spanning patients,
  appointments and availability, encounters, referrals, cases, tasks, group visits, attachments, letters,
  lab results (including OLIS lab messages), allergy and medication records, health profiles, facilities,
  providers and work hours. Pagination follows the GraphQL Cursor Connections specification (default 50,
  maximum 100 records per page). Authentication is unusual and notably strong: the consumer generates
  a 2048-bit RSA key pair, registers the public key on an API Consumer inside the CHR account, and signs
  its own RS512 JWT that must carry a matching iss claim and expire within 900 seconds — there is no authorization
  server, no token endpoint and no client secret. A companion Event Notification Service pushes 21 signed
  webhook topics carrying identifiers only, with no personal or personal-health information in the payload.
  Every API action is audit-logged for 90 days. The API ships on a bi-weekly release train with a dated
  public changelog going back to 2022, but it is a paid feature available to select customers, and the
  executable endpoint is issued per clinic account rather than published.'
humanURL: https://help.inputhealth.com/en/collections/3317215-chr-enterprise-api
baseURL: https://apidocs.ca.inputhealth.com/enterprise-api
baseURLNote: The live GraphQL endpoint is issued per CHR account domain and is read from Settings > Enterprise
  API inside the account; TELUS does not publish it. The URL recorded here is the public, anonymously
  reachable schema surface for the same API — the GraphQL Voyager explorer, whose introspection document
  at /enterprise-api/introspection.json was harvested verbatim into graphql/.
tags:
- Healthcare
- Electronic Medical Records
- GraphQL
- Appointments
- Referrals
- Canada
- Webhook
tags_raw:
- Healthcare
- Electronic Medical Records
- GraphQL
- Appointments
- Referrals
- Canada
- Webhooks
properties:
- type: GraphQL
  url: graphql/telus-chr-enterprise-api.graphql
- type: GraphQLIntrospection
  url: graphql/telus-chr-enterprise-api-introspection.json
- type: Documentation
  url: https://help.inputhealth.com/en/collections/3317215-chr-enterprise-api
- type: APIReference
  url: https://help.inputhealth.com/en/articles/5941595-api-reference-documentation
- type: GettingStarted
  url: https://help.inputhealth.com/en/articles/6368814-enterprise-api-onboarding-overview
- type: SchemaExplorer
  url: https://apidocs.ca.inputhealth.com/enterprise-api
  note: GraphQL Voyager rendering of the published introspection document.
- type: Authentication
  url: authentication/telus-authentication.yml
- type: Webhooks
  url: asyncapi/telus-chr-event-notifications.yml
- type: ChangeLog
  url: https://help.inputhealth.com/en/articles/13391004-what-s-new-in-the-api-2026
- type: ErrorCatalog
  url: errors/telus-problem-types.yml
- type: DataModel
  url: data-model/telus-data-model.yml
- type: Sandbox
  url: sandbox/telus-sandbox.yml