TELUS Health

TELUS CHR Enterprise API

GraphQL API for the TELUS Collaborative Health Record (CHR) that lets partners build integrations against clinic data. Queries retrieve and mutations create or update CHR records (patients, appointments, encounters, clinical documents and more), exposed as a data graph following the GraphQL Cursor Connections spec (page size defaults to 50, max 100). Authenticated with RS512-signed JSON Web Tokens presented as Bearer tokens, with tokens expiring within 15 minutes. The GraphQL endpoint URL is provisioned per CHR domain in Settings, so no single fixed base host is published.

GitHub

Documentation

📖
Documentation
https://help.inputhealth.com/en/articles/6483215-chr-enterprise-api
📖
APIReference
http://apidocs.inputhealth.com/voyager.html
📖
GettingStarted
https://help.inputhealth.com/en/articles/6368814-enterprise-api-onboarding-overview
📖
Authentication
https://help.inputhealth.com/en/articles/6483223-making-requests-to-the-api

Other Resources

🔗
GraphQL
http://apidocs.inputhealth.com/voyager.html
🔗
GraphQL
https://raw.githubusercontent.com/api-evangelist/telus-health/refs/heads/main/graphql/telus-health-chr-enterprise.graphql
🔗
GraphQL
https://raw.githubusercontent.com/api-evangelist/telus-health/refs/heads/main/graphql/telus-health-chr-enterprise-introspection.json
🔗
MCPServer
https://raw.githubusercontent.com/api-evangelist/telus-health/refs/heads/main/mcp/telus-health-mcp.yml
🔗
DataModel
https://raw.githubusercontent.com/api-evangelist/telus-health/refs/heads/main/data-model/telus-health-data-model.yml
🔗
Sandbox
https://raw.githubusercontent.com/api-evangelist/telus-health/refs/heads/main/sandbox/telus-health-sandbox.yml
🔗
APIsJSON
https://raw.githubusercontent.com/api-evangelist/telus-health/refs/heads/main/apis.yml

API entry from apis.yml

apis.yml Raw ↑ 
aid: telus-health:telus-chr-enterprise-api
name: TELUS CHR Enterprise API
description: GraphQL API for the TELUS Collaborative Health Record (CHR) that lets partners build integrations
  against clinic data. Queries retrieve and mutations create or update CHR records (patients, appointments,
  encounters, clinical documents and more), exposed as a data graph following the GraphQL Cursor Connections
  spec (page size defaults to 50, max 100). Authenticated with RS512-signed JSON Web Tokens presented
  as Bearer tokens, with tokens expiring within 15 minutes. The GraphQL endpoint URL is provisioned per
  CHR domain in Settings, so no single fixed base host is published.
humanURL: https://help.inputhealth.com/en/articles/6483215-chr-enterprise-api
tags:
- GraphQL
- EMR
- Healthcare
- Interoperability
properties:
- type: Documentation
  url: https://help.inputhealth.com/en/articles/6483215-chr-enterprise-api
- type: APIReference
  url: http://apidocs.inputhealth.com/voyager.html
- type: GraphQL
  url: http://apidocs.inputhealth.com/voyager.html
- type: GraphQL
  url: graphql/telus-health-chr-enterprise.graphql
- type: GraphQL
  url: graphql/telus-health-chr-enterprise-introspection.json
- type: MCPServer
  url: mcp/telus-health-mcp.yml
- type: DataModel
  url: data-model/telus-health-data-model.yml
- type: Sandbox
  url: sandbox/telus-health-sandbox.yml
- type: GettingStarted
  url: https://help.inputhealth.com/en/articles/6368814-enterprise-api-onboarding-overview
- type: Authentication
  url: https://help.inputhealth.com/en/articles/6483223-making-requests-to-the-api