TELUS Health

TELUS Health is the digital-health division of TELUS, one of Canada's largest telecommunications and technology companies, and the country's leading health-IT provider. It operates the PS Suite, Med Access, and cloud-native Collaborative Health Record (CHR) electronic medical records used across Canadian primary care, along with pharmacy management, virtual care, and employer/benefits health services. Its documented public integration surface is the CHR Enterprise API, a GraphQL endpoint secured with RS512-signed JWT bearer tokens that exposes clinic data (patients, appointments, encounters, clinical documents and more) for partner-built add-ons, complemented by the TELUS Patient Chart FHIR R4 implementation guide, a package of 89 published StructureDefinition profiles under the http://telus.com/fhir/patientChart canonical for standards-based patient-record exchange out of TELUS EMRs, and the Omara Health Exchange FHIR interoperability platform. Home market is Canada, where healthcare is province-fragmented and FHIR interoperability is stewarded federally by Canada Health Infoway. Both API surfaces are documented but gated behind a partner or CHR-domain agreement.

TELUS Health publishes 2 APIs on the APIs.io network. Tagged areas include Healthcare, Canada, EMR, EHR, and FHIR.

TELUS Health’s developer surface includes documentation, API reference, getting-started guide, authentication, and 12 more developer resources.

🌐 Visit website 📡 Source on GitHub
21.8/100 emerging ▬ flat Agent 18/100 agent aware Full breakdown ↓
scored 2026-07-27 · rubric v0.5
2 APIs 1 MCP Servers
HealthcareCanadaEMREHRFHIRHL7InteroperabilityGraphQLe-PrescribingPharmacyDigital HealthClinical Data

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 21.8/100 · emerging
Contract Quality 0.0 / 25
Developer Ergonomics 10.4 / 20
Commercial Clarity 0.0 / 20
Operational Transparency 0.7 / 13
Governance 0.0 / 12
Discoverability 8.0 / 10
Agent readiness — 18/100 · agent aware
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 15
MCP Server 0 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 6
Agent Skills 5 / 5
Well-Known Catalog 4 / 4
Consent & Bot Identity 0 / 3
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/telus-health: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

APIs 2

Individual APIs this provider publishes, each with its own machine-readable definition.

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 record...

TELUS Patient Chart FHIR API

TELUS Patient Chart FHIR R4 implementation guide, published by TELUS, containing 89 StructureDefinition profiles and extensions under the http://telus.com/fhir/patientChart cano...

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

telus-health-mcp.yml

MCP SERVER

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Telus Health Authentication

http · 1 scheme

SECURITY

Telus Health Domain Security

TLSv1.3 · DMARC

SECURITY

Resources

Get Started 2

Portal, sign-up, and the first successful call

DeveloperPortal
DeveloperPortal
 GettingStarted
GettingStarted

Documentation 2

Reference material describing how the API behaves

Documentation
Documentation
 APIReference
APIReference

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

WellKnown
WellKnown
 AgentSkill
AgentSkill
 LLMsTxt
LLMsTxt

Design & Contract 3

Pagination, idempotency, versioning, errors, and events

Conventions
Conventions
 Conformance
Conformance
 Lifecycle
Lifecycle

Build 2

SDKs, sample code, and the tooling you integrate with

GitHubOrganization
GitHubOrganization
 Packages
Packages

Access & Security 2

Authentication, authorization, and security posture

DomainSecurity
DomainSecurity
 Authentication
Authentication

Company 2

The organization behind the API

Website
Website
 LinkedIn
LinkedIn

Source (apis.yml)

apis.yml Raw ↑ 
aid: telus-health
url: https://raw.githubusercontent.com/api-evangelist/telus-health/refs/heads/main/apis.yml
name: TELUS Health
kind: company
description: TELUS Health is the digital-health division of TELUS, one of Canada's largest telecommunications and technology
  companies, and the country's leading health-IT provider. It operates the PS Suite, Med Access, and cloud-native Collaborative
  Health Record (CHR) electronic medical records used across Canadian primary care, along with pharmacy management, virtual
  care, and employer/benefits health services. Its documented public integration surface is the CHR Enterprise API, a GraphQL
  endpoint secured with RS512-signed JWT bearer tokens that exposes clinic data (patients, appointments, encounters, clinical
  documents and more) for partner-built add-ons, complemented by the TELUS Patient Chart FHIR R4 implementation guide, a package
  of 89 published StructureDefinition profiles under the http://telus.com/fhir/patientChart canonical for standards-based
  patient-record exchange out of TELUS EMRs, and the Omara Health Exchange FHIR interoperability platform. Home market is
  Canada, where healthcare is province-fragmented and FHIR interoperability is stewarded federally by Canada Health Infoway.
  Both API surfaces are documented but gated behind a partner or CHR-domain agreement.
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
tags:
- Healthcare
- Canada
- EMR
- EHR
- FHIR
- HL7
- Interoperability
- GraphQL
- e-Prescribing
- Pharmacy
- Digital Health
- Clinical Data
created: '2026-07-24'
modified: '2026-07-24'
specificationVersion: '0.19'
apis:
- 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
- aid: telus-health:telus-patient-chart-fhir-api
  name: TELUS Patient Chart FHIR API
  description: TELUS Patient Chart FHIR R4 implementation guide, published by TELUS, containing 89 StructureDefinition profiles
    and extensions under the http://telus.com/fhir/patientChart canonical. Profiles cover patient-chart resources including
    AllergyIntolerance, CarePlan, ClinicalImpression, Composition, Condition, DiagnosticReport, DocumentReference, Encounter,
    MedicationRequest and a large set of medication/prescribing extensions, used to exchange patient-record data exported
    from TELUS EMRs. This is a conformance package (profiles/extensions); no TELUS CapabilityStatement or SMART-on-FHIR configuration
    is published.
  humanURL: https://simplifier.net/teluspatientchart
  baseURL: https://fhir.simplifier.net/TELUSPatientChart
  tags:
  - FHIR
  - HL7
  - Interoperability
  - Healthcare
  properties:
  - type: Documentation
    url: https://simplifier.net/teluspatientchart
  - type: FHIR
    url: fhir/telus-patient-chart-structuredefinitions.json
common:
- type: DomainSecurity
  url: security/telus-health-domain-security.yml
- type: Website
  url: https://www.telus.com/en/health
- type: DeveloperPortal
  url: https://help.inputhealth.com/en/articles/6483215-chr-enterprise-api
- type: Documentation
  url: https://help.inputhealth.com/en/articles/6483215-chr-enterprise-api
- type: APIReference
  url: http://apidocs.inputhealth.com/voyager.html
- type: GettingStarted
  url: https://help.inputhealth.com/en/articles/6368814-enterprise-api-onboarding-overview
- type: LinkedIn
  url: https://www.linkedin.com/company/telus-health
- type: GitHubOrganization
  url: https://github.com/telus-health-chr
- type: Authentication
  url: authentication/telus-health-authentication.yml
- type: Conventions
  url: conventions/telus-health-conventions.yml
- type: Conformance
  url: conformance/telus-health-conformance.yml
- type: Lifecycle
  url: lifecycle/telus-health-lifecycle.yml
- type: Packages
  url: packages/telus-health-packages.yml
- type: WellKnown
  url: well-known/telus-health-well-known.yml
- type: AgentSkill
  url: skills/_index.yml
- type: LLMsTxt
  url: llms/telus-health-llms.txt
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com