Back to directory

Evidence profile

Partner-gated

Collaborative Health Record (CHR)

TELUS Health · Canadian ambulatory care

TELUS documents a CHR Enterprise API that reads and writes CHR data through GraphQL. Its public schema includes mutations that create patients, appointments, incoming referral records, and tasks. It's a paid feature, and TELUS turns it on for each CHR domain after a contract and a privacy and security review.

Evidence checks

Public documentation

Documented

TELUS publishes Enterprise API guides and a public schema viewer you can explore before you have access.

Documented write operations

Documented

The schema lists mutations such as createPatient, createAppointment, createIncomingReferralRecord, and createTask. CHR applies the account's own rules to API writes, such as an appointment type's booking times and a provider's working hours.

Access

Partner-gated

TELUS calls the API a paid feature that's currently limited to a select few customers. Access needs a signed contract, an intake questionnaire, and a privacy and security review before production.

Developer test path

Documented

After the contract is signed, TELUS's onboarding steps give you credentials for a sandbox CHR domain. You build and test there before you ask for production access.

Audit trail

Documented

CHR records every API action in its audit log under the API consumer that made it, and keeps API requests and responses for 90 days.

Referral network

Documented

Ocean lists TELUS Health CHR among its integrations.

Best next step

Check the exact mutation in the public schema, then confirm the clinic has, or will buy, CHR Enterprise API access for its domain.

Reviewed sources

Claims on this page are scoped to these public sources. Contracted capabilities and local configuration may differ.